Key takeaways
- An audit-ready month-end close captures each reconciliation, accrual, and cutoff decision as evidence while the work happens. It is not a second project run after the books lock.
- Audit-readiness and speed stop trading off once support is captured at the source. The same close that ships in five days answers most of a 140-item auditor request on day one.
- Reconstructing support later concentrates the cost inside the window. For one modeled engagement, rebuilding 45 of 140 items ran 36 hours, roughly 4.5 close days and $1,448 in labor that capture-at-source avoids.
- Materiality scopes the effort. AU-C 320 sets performance materiality below overall materiality, so a growing company documents the balances that move the opinion, not every $12 transaction.
- A retention schedule closes the loop: public-filer audit documentation runs seven years under SOX Section 802, and the IRS period of limitations runs three years for most business records.
An audit-ready month-end close carries its own evidence. Every reconciliation, accrual, and cutoff decision is documented as the work happens, not reconstructed weeks later for an auditor. Done that way, audit-readiness adds zero days to a fast close. Consider a $28M single-entity SaaS company preparing for its first financial-statement audit. Its auditor issues a PBC list, short for Prepared By Client, of roughly 140 items. A close that already captures support at the source answers most of that list the day the books lock.
What is an audit-ready month-end close?
It is a close where the support an auditor will request already exists, filed against the period, the moment the books lock. The governing standard is AU-C 500, which obligates an auditor to gather sufficient appropriate audit evidence before rendering an opinion. Sufficiency measures quantity. Appropriateness measures quality, meaning relevance and reliability.
Audit-readiness makes that evidence a byproduct of the close rather than a separate exercise. The reconciliation you perform on day one becomes the reconciliation the auditor tests in month four. The accrual you post from a saved schedule becomes the workpaper that explains the estimate. Nothing is recreated, because nothing was discarded. That single design choice is why speed and assurance stop competing.
Which evidence do auditors ask for, and where does it live?
The PBC list resolves into a handful of evidence classes, each tied to a source document the close already produces. The table maps every class to the standard behind the request and to the true cost of two paths: capturing support during the close, or reconstructing it for the auditor later. The right column is the tax an unprepared close pays.
| Evidence class | What the auditor requests | Standard | Captured at source (added close days) | Reconstructed later (window hours) |
|---|---|---|---|---|
| Bank & card reconciliations | Statement tie-out for every cash account | AU-C 500 | 0 | 9 |
| Cutoff support (AP/AR) | Invoice and receipt dates proving the period boundary | AU-C 500 | 0 | 6 |
| Accrual & estimate workpapers | The schedule and basis behind each posted estimate | AU-C 230 | 0 | 7 |
| Revenue recognition (ASC 606) | Contract terms and the deferred revenue rollforward | AU-C 500 | 0 | 8 |
| Reviewer sign-off | Who prepared and who reviewed each area, and when | AU-C 230 | 0 | 4 |
| Retention & access | Prior-period support, retrievable on request | SOX 802 | 0 | 2 |
Two entries deserve emphasis. Reviewer sign-off answers the AU-C 230 requirement that documentation let an experienced auditor understand who performed the work and who reviewed it. Revenue recognition under ASC 606 depends on a deferred revenue rollforward, $3.6M for the modeled client, that must tie to the general ledger before the number is defensible.
Why capture support at the source instead of reconstructing it?
Because reconstruction concentrates cost inside the close window, and capture-at-source distributes it to near zero. The hours in the table sum to 36 for a single close cycle. Run the arithmetic on the labor first. At the Bureau of Labor Statistics May 2025 median accountant wage of $40.23 hourly, 36 hours costs $1,448.28 per close. That figure recurs every month the support gets rebuilt rather than retained.
The schedule cost is larger. Compressed into the close, 36 hours divided by an 8-hour working day is 4.5 business days added to the calendar. A five-day close becomes a ten-day close the month an auditor arrives. Capture-at-source pays the same total differently. A reconciliation documented at the moment it clears adds about two minutes; across 12 monthly reconciliations that is 24 minutes, spread over a 20-business-day month, and it moves the lock date by zero days.
The comparison is not speed versus assurance. It is timing. The prepared close pays in seconds distributed through the month; the unprepared close pays in days concentrated at quarter-end, and pays the $1,448 again each cycle.
How does materiality decide what to document?
Materiality scopes the work, so audit-readiness never means documenting everything. Under AU-C 320, an auditor sets overall materiality for the statements as a whole, then sets performance materiality below it to keep undetected error within tolerance. Balances above that line carry the opinion; balances below it rarely do.
For the modeled company, that logic directs evidence toward cash, deferred revenue, receivables, and payroll, and away from a $12 software charge. The controller documents the accounts that can move a reader’s judgment and applies lighter support to the rest. Scoping this way keeps the close fast and the binder proportionate, which is the discipline an audit-ready close is built on.
How do you systematize an audit-ready close?
By moving evidence capture upstream, into routines that run before the close window opens. Reconcile bank and card accounts weekly, so the reconciliation cadence produces 52 tie-outs a year already filed as support. Template every recurring accrual, so the schedule and its basis save automatically. Require an e-signed reviewer sign-off at lock, so the who-and-when trail exists without a follow-up email.
This is the habit the Continuous Close Method™ formalizes: the ledger stays tied out through the month, and each entry retains the source file that proves it. The same rhythm powers a five-day close calendar, because the opening day verifies balances that already agree. Puzzle keeps the ledger current and attaches the underlying data; a controller supplies the judgment and the sign-off an auditor tests.
Close the loop with a retention schedule. Public-filer audit documentation runs seven years under the SOX Section 802 rules, and the IRS period of limitations is three years for most business records, four for employment tax. Filing support to a dated close binder satisfies both without a separate archival project. Aaron Ressel reviews that binder before Debit & Co. releases it to an auditor, the control layer this whole design exists to protect. For the day-by-day sequence underneath it, the month-end close process sets the frame.
Frequently asked questions
What makes a month-end close audit-ready?
A close is audit-ready when the support an auditor will request already exists at lock, filed against the period rather than reconstructed later. AU-C 500 requires the auditor to obtain sufficient appropriate audit evidence, where sufficiency is quantity and appropriateness is relevance and reliability. An audit-ready close produces that evidence as a byproduct of the reconciliations, accruals, and cutoff decisions it performs each month, so the PBC list is answered from records that are already on file.
What support schedules do auditors ask for at close?
Auditors request bank and card reconciliations, cutoff support proving the period boundary for accounts payable and receivable, accrual and estimate workpapers, the deferred revenue rollforward for ASC 606, and a reviewer sign-off showing who prepared and reviewed each area. Each maps to a source document the close already creates. AU-C 500 governs the evidence and AU-C 230 governs the documentation, which is why an audit-ready close files these schedules the same day the books lock.
Does audit-readiness have to make the close slower?
No, provided support is captured at the source rather than reconstructed for the auditor. Reconstructing 45 of 140 request items ran 36 hours in one modeled engagement, roughly 4.5 close days if crammed into the window. Capturing the same support as the work happens adds about two minutes per reconciliation, or 24 minutes across 12 monthly reconciliations, and moves the lock date by zero days. The tradeoff disappears once evidence becomes a byproduct of the close.
What reconciliation evidence should you retain each month?
Retain the reconciliation itself, the source statement it ties to, and the resolution note for any reconciling item, for every cash and card account. That package satisfies the AU-C 500 evidence request for cash, the balance auditors test first. Reconciling weekly produces 52 tie-outs a year that are already on file, so the opening day of the close verifies balances that agree instead of discovering them, and the auditor pulls finished support rather than a request for rework.
When should a growing company start closing to audit standard?
Start the cycle before the audit is required, typically once a financing, acquisition, or lender covenant puts a first audit within about 12 months. Building audit-ready habits into a live close costs almost nothing, while reconstructing a year of support under deadline costs days and dollars each month. A company that reconciles weekly and retains support at the source can meet a first-year PBC list from records it already keeps, without a scramble.
What close documentation should you keep each month, and how do you systematize it?
Keep reconciliations, cutoff evidence, accrual schedules, the ASC 606 deferred rollforward, and a reviewer sign-off, filed to a dated close binder. Systematize it with weekly reconciliation, templated accruals, and an e-signed sign-off at lock, so each item saves automatically rather than by follow-up. Set retention to the longest applicable rule: seven years for public-filer audit documentation under SOX Section 802, three years for most business records under the IRS period of limitations.
What tools can verify supporting documentation in the month-end close?
The verification layer is the general-ledger reconciliation tools inside QuickBooks Online or NetSuite, a document repository that attaches the source file to each journal entry, and a continuous-accounting platform such as Puzzle that keeps the ledger tied out daily. Puzzle keeps the data current and links the underlying records; a controller supplies the judgment and the sign-off an auditor relies on. Tools confirm that support exists and ties out, but the opinion still rests on human review under AU-C 230.
Audit-evidence and documentation standards cited from AICPA AU-C 230, 320, and 500. Retention rules from the SEC’s Sarbanes-Oxley Section 802 record-retention release and PCAOB AS 1215, and from IRS Publication 583. Wage data from the U.S. Bureau of Labor Statistics, May 2025. Figures verified as of August 2026.
