Building an Audit-Ready Month-End Close Package

Most finance teams think about the close package the way they think about annual audit fieldwork: as something you assemble when someone asks for it. The result is a familiar situation — auditors or the board requests support for a specific account, and someone spends 2–3 hours pulling together reconciliations, journal entry approvals, and source documents that were never organized with review in mind. In our experience working with mid-market finance teams, building a close package as a natural output of each month-end close is a fundamentally different approach, and once a team has done it this way, going back is almost unthinkable.

What Auditors Actually Look for in Close Documentation

Before building a close package, it's worth being specific about what makes documentation audit-ready rather than just organized. External auditors and internal reviewers are looking for the same things, expressed differently depending on their scope.

At the account level, they want to see: a reconciliation that ties the GL balance to an independent source (bank statement, subledger, third-party confirmation), a list of any reconciling items with explanations, evidence that the reconciliation was reviewed and approved by someone other than the preparer, and the date the reconciliation was completed. That's the minimum for any material balance sheet account.

At the journal entry level, auditors want to see: the journal entry itself with the business purpose noted, the preparer and approver, and any supporting documentation (invoice, contract, allocation schedule) attached. For unusual or manual journal entries — the ones that aren't automated system postings — they'll look at these more closely. The risk assessment is simple: unusual manual journals with inadequate support are where errors and manipulation live.

For SOX-compliant companies specifically, the documentation requirements go further. SOX Section 404 requires evidence of internal controls operating effectively, which means your close package needs to demonstrate not just that the numbers are right, but that the process that produced them had appropriate review and approval at each stage. That's a higher bar than a financial audit alone.

The Six Components of a Complete Close Package

A close package that satisfies both internal review and external audit requests has six components. None of them are exotic — the challenge is producing them consistently and organizing them so they're useful to the person reviewing them.

1. Period-End Financial Statements (Draft)

The close package opens with the P&L, balance sheet, and statement of cash flows for the period — clearly marked as draft, with the period end date and the company name. These are the outputs that every other component is supporting. If the package is well-constructed, a reviewer can identify any question about any number and find the supporting documentation in the same package within two minutes.

2. Account Reconciliation Summary

A one-page summary showing every material account, the GL balance, the reconciled balance (from the independent source), whether they agree, and the status (certified / exception noted / in progress). This is the map that tells the reviewer which accounts are clean and which ones have open items. It shouldn't require reading every individual reconciliation to understand the overall close status.

3. Individual Account Reconciliations

The detailed reconciliation workpapers for each material account. These follow the account reconciliation summary and should be organized in the same account order. Each reconciliation includes the GL balance, the source balance (bank statement, sub ledger, confirmation), a list of reconciling items, and the approver sign-off with date. For accounts where the reconciliation was auto-certified (no manual intervention required), a note indicating auto-certification with the system timestamp is appropriate and sufficient.

4. Manual Journal Entry Log

A complete list of all manual journal entries posted during the close, with preparer, approver, business purpose, and posting date. For auditors, this is one of the first documents requested — it shows them where human judgment was applied to the books and helps them scope their testing. A clean journal entry log with consistent business purpose notes is a signal of a well-controlled close process.

5. Exception and Open Item List

Any reconciling items that couldn't be resolved before the close completed should be documented with an explanation, an owner, and a target resolution date. "Unexplained" is not an acceptable note — every open item needs at least a working hypothesis. This list also serves as the input to the following month's pre-close activities.

6. Close Sign-Off Documentation

The final element is evidence that the close was reviewed and approved by the appropriate levels of management — typically the controller and CFO or VP Finance. This can be as simple as a sign-off sheet with names, dates, and signatures, or as formal as a documented review process in your close management system. What matters is that there's a clear record of who declared the period closed and when.

Organizing the Package for Maximum Usability

A close package that exists but is hard to navigate will still generate 90-minute evidence-gathering exercises when auditors ask questions. Organization matters.

"The best close packages I've seen are built like a legal brief: the conclusion comes first, the evidence is clearly indexed, and you can find support for any specific claim in under two minutes. The worst ones are a folder of files named 'recon_FINAL_v2_revised.xlsx'."

Practical organization principles:

• Use a consistent naming convention: account number or name + period + "recon" or "support"
• Organize in financial statement order (balance sheet accounts first, then income statement)
• Keep a master index file that lists every document in the package and what it supports
• Version control: when a reconciliation is updated after an error is found, keep the original with a note and append the corrected version
• Store in a location accessible to the auditors without requiring an IT ticket or a personal request to the controller

How Long Should Package Assembly Take?

For a team with good close discipline and organized reconciliation workpapers, assembling the close package should take 30–60 minutes. This includes compiling the individual reconciliations, completing the summary sheet, collecting the journal entry log, and running a final review for completeness.

Teams that report 2–4 hours of package assembly time are typically dealing with one of three issues: reconciliations that were prepared throughout the close without a consistent format, journal entries that lack business purpose notes and need to be back-filled, or an approval process where sign-offs weren't documented as they happened and need to be reconstructed.

Each of these has a fix that lives earlier in the close process, not at package assembly time. Standardizing reconciliation templates, requiring business purpose notes at journal entry creation, and documenting approvals in real time are all close-process disciplines, not package-assembly disciplines. The package assembly step should feel like clicking "compile" — not like building the thing for the first time.

When the Package Needs to Be SOX-Ready

If your company is subject to SOX (public company or preparing to be), the close package is also audit evidence for your internal controls. That requires additional documentation: the specific control objective each reconciliation is satisfying, evidence that the control operated at the defined frequency (monthly, quarterly), and documentation of any control deficiencies identified and remediation steps taken.

SOX documentation is more structured than a standard close package, but it builds on the same foundation. Teams that already produce a complete, well-organized close package each month typically find the incremental SOX documentation requirement manageable. Teams that start from scratch at SOX readiness discover they're building two things at once.

The close package is not just an audit artifact. It's the most complete record your organization has of how a financial period was closed. Producing it consistently, accurately, and quickly is one of the higher-value disciplines a finance team can build.