The fastest way to lose a Friday is to start the close without a prepared-by-client (PBC) list the finance director (FD) has already signed off on. Month-end at a mid-cap manufacturer is still the five days of the month where everyone remembers they don’t enjoy their job, and the controllers who land it in five business days do two things differently from the ones still stuck at ten. Neither has anything to do with software.
Your auditor asks for the bank reconciliation (recon) from September. It takes two hours to find. When it surfaces, the reconciling items include four entries from July that were never cleared, two entries with no description, and a balance that doesn’t match the general ledger (GL) by €11,400. The audit team flags it, the engagement partner (EP) raises a control deficiency, and your close process is now a talking point in the management letter. All of it was preventable with a structured close that caught the items in September, not in February during fieldwork.
A month-end close checklist should cover five phases in sequence. Pre-close preparation (cut-off, accruals, intercompany adjustments, reclassifications). Core recons (bank, intercompany, subledger-to-GL, fixed assets). Journal entry review. Management reporting and variance analysis. Close certification with documented sign-off. Each task needs a named owner, a deadline relative to the close date, a completion status, and an audit trail the team can inspect.
Key takeaways
- How to structure a month-end close into five phases with clear ownership and deadlines, so nothing falls through the gap between finance and operations
- Which recons your auditor checks first under ISA 315.26 when assessing the design of your close process as a control
- How to document your close so that audit fieldwork doesn’t become a reconstruction exercise
- What distinguishes a close process that generates audit findings from one that generates auditor confidence
Why the close process matters to your auditor
ISA 315.26 requires auditors to identify controls relevant to the audit. Your month-end close process is one of the first things they evaluate. The close sits at the intersection of four financial statement (FS) assertions: completeness (did everything get recorded?), cut-off (did it get recorded in the right period?), accuracy (does the subledger agree to the GL?), and valuation (are the accruals and provisions reasonable?).
When the audit team walks through your close under ISA 315 .A175, they’re asking five questions. Who performs each step. What data they use. When they perform it. What threshold triggers investigation. What evidence they produce. A close process that answers all five cleanly reduces the auditor’s assessed risk, which translates directly into less substantive testing and fewer PBC requests during fieldwork.
A close process that doesn’t answer those questions has the opposite effect. The auditor can’t rely on the close as a control, so they design additional substantive procedures to compensate. That means larger samples and more document requests, which pulls your team away from running the business.
The checklist below is built for a mid-market European company with €10M to €150M revenue and a finance team of two to eight people running an ERP system (Exact, SAP Business One, NetSuite, or similar). If your team is smaller, combine roles. If your team is larger, add segregation. The phases and tasks are the same regardless of team size.
Phase 1. Pre-close preparation (day 1 after period end)
The pre-close phase catches items that would otherwise contaminate the recon phase. Complete these before you start reconciling anything.
Cut-off procedures come first. Confirm that all goods received before the period end have corresponding purchase invoices recorded (or accrued). Confirm that all goods dispatched before the period end have corresponding sales invoices raised. If your operations team enters goods receipts and your finance team enters invoices, the gap between the two systems is where cut-off errors live. Run a report of goods received not invoiced (GRNI) and goods dispatched not invoiced (GDNI). Clear or accrue every item.
Post all recurring accruals (rent, insurance, depreciation, and any payroll-related costs that span the period). If these are set up as recurring journal entries in your ERP, verify they posted correctly. If they’re manual, prepare and post them now. A common source of audit findings is depreciation that posts only at year-end rather than monthly. The monthly management accounts then misrepresent the asset base and the year-end adjustment is large enough to attract auditor attention.
Review and post any reclassification entries. If a customer balance turned negative because of credit notes, reclassify it from receivables to payables. If a supplier has a debit balance because of prepayments or overpayments, reclassify it from payables to prepaid expenses. These reclassifications affect the presentation of the balance sheet and your auditor will check them under IAS 1.32 (the prohibition on offsetting assets and liabilities).
Cancel any open purchase orders or sales orders that are no longer valid. Stale open orders distort commitment reports and can create phantom accruals if your system generates automatic GRNI entries based on open POs. (This is the classic SALY trap, where the open-order list gets rolled forward month after month because no one owns cleaning it up.)
Phase 2. Core recons (days 2 through 4)
Recons are the backbone of the close. Each one confirms that an external or independent data source agrees with the general ledger. Your auditor evaluates recon controls under ISA 315.26 and will walk through at least one as part of their risk assessment. Make them easy to inspect (the file should tell a story, not read like a scavenger hunt).
Bank recon is the highest priority. Reconcile every bank account to the GL on the period-end date. Every reconciling item should have a description, an expected clearing date, a named follow-up owner, and a status indicating whether it has been investigated. Any reconciling item older than 30 days needs investigation, not just a carry-forward. The ciferi financial ratios calculator can flag unusual cash movement patterns that may indicate reconciling items you’ve missed.
Accounts receivable (AR) subledger-to-GL recon. Run the aged receivables report and agree the total to the GL control account. Investigate any difference. Then review the ageing. Any balance over 90 days without a documented collection action needs a provision assessment. Your auditor will test the AR ageing as part of their IFRS 9 expected credit loss assessment, so accuracy here prevents questions during fieldwork.
Accounts payable (AP) subledger-to-GL recon. Same principle: agree the AP subledger total to the GL control account. Review the ageing for any disputed or duplicate invoices. If you have a supplier statement recon programme, complete it for your top 10 suppliers by balance.
Intercompany recons (if applicable). Agree all intercompany balances with counterparties. Differences must be investigated and either corrected or documented with an explanation and expected resolution date. Intercompany is the area where auditors of group engagements under ISA 600 spend disproportionate time. Clean intercompany recons at month-end prevent a cascade of work at year-end.
Fixed asset register to GL recon. Agree the net book value on the fixed asset register to the GL. Verify that all additions during the month are supported by a purchase invoice or capitalisation memo. Verify that all disposals are recorded with the correct gain or loss. If your depreciation is calculated in the fixed asset module, verify that the depreciation charge posted to the GL matches the module output.
Prepayments and accruals review. Verify that each prepayment balance is still valid (the underlying contract hasn’t expired or been cancelled). Verify that each accrual has a documented basis and expected settlement date. Release any accruals where the underlying expense has been invoiced and recorded in the period.
Phase 3. Journal entry review (day 4)
ISA 240.32 requires auditors to test the appropriateness of journal entries as part of their fraud risk procedures. A structured journal entry review within your close process is the kind of control your auditor can evaluate under ISA 315.26 .
Run a listing of all manual journal entries posted during the period. Review for entries that meet any of these criteria. Entries posted by users who don’t normally post journals. Entries posted outside business hours. Entries with round-number amounts above a threshold you’ve defined (for example, any manual entry over €10,000). Entries to unusual account combinations (revenue debited and cash credited directly without going through receivables). Entries posted on the last day of the period or the first day of the next.
The review doesn’t require you to inspect every journal. It requires you to identify and investigate the ones that carry the highest fraud or error risk. Document the review. Record who performed it, the criteria applied, the entries investigated, and the outcome. That documentation is exactly what your auditor will request when they perform their ISA 240.32 journal entry testing.
If your ERP supports journal entry approval workflows, use them. An entry that requires a second person’s approval before posting is a preventive control. An entry reviewed after posting is a detective control. Both are useful, but the preventive control is stronger evidence for your auditor.
Phase 4. Management reporting and variance analysis (days 4 through 5)
Once the ledger is reconciled and the journals are reviewed, produce the management accounts and perform variance analysis. This phase serves two purposes. It gives the management team the financial information they need to run the business. It also functions as an analytical review that catches errors the recon process missed.
Compare actuals to budget for every material line item. ISA 520 .A11 notes that analytical procedures are more effective when applied to disaggregated data. The same principle applies to your internal review. Don’t just compare total revenue to budget. Compare by product line and by division. A 2% variance at entity level can hide a 15% shortfall in one segment offset by an overperformance elsewhere.
For every variance above your defined threshold (many mid-market companies use 5% and €25,000 as a dual threshold), document the cause. “Seasonal variation” is not an explanation. “Revenue from the logistics division was €180,000 below budget because the Antwerp port delays in the third week of the month shifted 12 container shipments to the following period” is an explanation. The level of specificity you apply to internal variance analysis is the same level your auditor applies when evaluating your analytical review controls.
Compare actuals to the prior month and to the same month in the prior year. Identify trends and anomalies. If an expense category doubled compared to last month, you want to know why before your auditor asks.
Produce the management reporting pack and distribute it to the relevant stakeholders with the variance commentary included. The reporting pack is evidence that management is actively monitoring the financial results, which is an entity-level control your auditor assesses under ISA 315.14 .
Phase 5. Close certification (day 5)
The final phase is the sign-off. The controller (or CFO, depending on your structure) reviews the completed checklist and confirms that all tasks are done before signing the close certification.
The certification should be a single document (or a single tab in your close tracking tool) that lists every task, the owner, the completion date, and the sign-off. If a task wasn’t completed (for example, one bank recon is pending because the bank statement wasn’t available), the certification should state that explicitly, with an expected completion date. Leaving incomplete items undocumented is worse than documenting them as open, because your auditor will find them either way and the undocumented version suggests a lack of oversight.
This document becomes part of your audit trail. When your auditor asks “was the September close completed on time?”, you can hand them the signed certification rather than assembling the evidence retrospectively. The difference between a structured close file and a reconstructed one is visible to any experienced auditor within minutes. (TGIF, on the days it actually foots first time.)
Lock the period in your ERP after sign-off. Posting to a closed period should require controller approval. This prevents backdated entries from corrupting reconciled balances and gives your auditor confidence that the financial data for a closed period hasn’t been altered after the close was certified.
Keep a log of any entries posted to locked periods. If you reopen October to post a correction in November, record why, what was posted, who approved the reopening, and when the period was re-locked. Your auditor will review post-close entries as part of their ISA 240.32 journal entry testing, and a clean log eliminates the need for them to investigate further.
Worked example: Bakker Industrial B.V.
Client profile. Bakker Industrial B.V. is a Dutch industrial components manufacturer. Revenue €54M. 120 employees. Finance team of four (controller, senior accountant, two staff accountants). ERP Exact Online. Monthly close target 5 working days after period end.
Pre-close (day 1)
The senior accountant runs the GRNI report from Exact. 8 items appear. 5 have matching invoices in the AP inbox (posted same day), 2 are accrued using the PO value, and 1 is a cancelled order that operations didn’t close in the system (cancelled and logged).
The staff accountant posts the recurring journals (depreciation €38,500, prepaid insurance release €4,200, payroll accrual €186,000, and accrued utilities €3,100). All are verified against the prior month for reasonableness.
Documentation note. Record the GRNI clearing and the cancelled PO in the close checklist. Include the recurring journal amounts with the prior-month comparison. Each task shows the owner, date, completion status, and reviewer sign-off.
Core recons (days 2 through 3)
The senior accountant reconciles the two bank accounts (ING and Rabobank). The ING account reconciles with €2,400 in outstanding cheques (all less than 15 days old). The Rabobank account shows a €6,800 difference traced to a direct debit that posted on the bank statement on the 1st of the following month. Timing difference documented, no correction needed.
The staff accountant reconciles AR (€4.2M subledger agrees to GL within €12, a rounding difference documented and accepted) and AP (€2.8M subledger agrees to GL exactly).
The controller reconciles the intercompany balance with Bakker Industrial GmbH (the German subsidiary). A €22,000 difference is traced to a management fee invoice posted by GmbH but not yet received by B.V. The invoice is accrued.
Documentation note. Each recon is saved as a separate WP with the GL balance, the subledger or bank balance, the reconciling items, and the preparer’s sign-off.
Journal entry review (day 4)
The controller runs the manual journal listing. 34 manual journals were posted in the month. 2 meet the review criteria. A €45,000 entry reclassifies an R&D cost from opex to capex (reviewed, supported by the capitalisation policy and project documentation). A €28,000 write-off of obsolete inventory (reviewed, supported by the stock count exception report signed by the warehouse manager).
Documentation note. Record the journal review criteria, the number of journals screened, the entries investigated, and the conclusion for each.
Management reporting (day 4 through 5)
The controller produces the monthly management pack. Revenue is €4.38M against a budget of €4.50M (variance €120,000, 2.7%). The variance is explained by a delayed delivery of industrial valves to the Antwerp customer (shipped on the 2nd of the following month, revenue recognised in the next period under IFRS 15.38 ). Cost of sales is in line with budget. Admin expenses are €18,000 above budget, driven by a one-off legal fee for the renewal of the GmbH intercompany transfer pricing agreement.
Documentation note. Variance analysis documented per line item, with explanations for all variances exceeding the dual threshold of 5% and €25,000.
Close certification (day 5)
The controller signs the close checklist confirming all tasks complete. The period is locked in Exact Online.
The audit team, when they arrive in February, receives a structured close file for each month. Every recon has a preparer and reviewer sign-off. Variances are explained. The journal entry reviews are documented. The auditor’s walkthrough of the close process under ISA 315 .A175 takes 45 minutes instead of four hours.
Your month-end close checklist
Common mistakes
- Reconciling to the bank statement date instead of the period-end date. The bank statement may cover a different date range depending on your bank’s reporting cycle. The recon must be as at the period-end date. Auditors testing under ISA 500 will check the recon date against the GL balance date.
Related content
- Internal controls (glossary) covers the ISA 315 framework for how auditors evaluate your close process as a control, including the five elements (who, what, when, input, evidence) they document during walkthroughs.
- Financial Ratio Calculator flags unusual patterns in your monthly financial data that your variance analysis should be catching, and produces working paper output your auditor can use directly.
- How to Document Internal Controls explains how your auditor documents and assesses the controls in your close process, so you can understand what they’re looking for and structure your close accordingly.
Related ciferi content
Related guides:
Put audit concepts into practice with these free tools:
Frequently asked questions
Why does the month-end close process matter to auditors?
ISA 315.26 requires auditors to identify controls relevant to the audit, and the month-end close process is one of the first things they evaluate. The close sits at the intersection of multiple financial statement assertions: completeness, cut-off, accuracy, and valuation. A structured close with documented sign-offs reduces the auditor’s assessed risk, which translates into less substantive testing, fewer PBC requests, and a shorter audit.
What are the five phases of a month-end close?
The five phases are: (1) pre-close preparation on day 1 (cut-off, accruals, reclassifications), (2) core reconciliations on days 2 through 4 (bank, intercompany, subledger-to-GL), (3) journal entry review on day 4, (4) management reporting and variance analysis on days 4 through 5, and (5) close certification with documented sign-off on day 5, followed by locking the period in the ERP.
Which reconciliation should be completed first during month-end close?
Bank reconciliation is the highest priority. Reconcile every bank account to the GL on the period-end date. Every reconciling item should have a description, an expected clearing date, and a named person responsible for follow-up. Any reconciling item older than 30 days needs investigation, not just a carry-forward.
What journal entries should be reviewed during the close process?
Review manual journal entries that meet risk criteria: entries posted by users who don’t normally post journals, entries posted outside business hours, entries with round-number amounts above a defined threshold, entries to unusual account combinations (such as revenue debited and cash credited directly), and entries posted on the last day of the period or the first day of the next. This review aligns with ISA 240.32 requirements that auditors test journal entry appropriateness.
What should the close certification document include?
The certification should list every close task, the owner, the completion date, and the sign-off. If a task was not completed, it should state that explicitly with an expected completion date. After sign-off, lock the period in the ERP so that posting to a closed period requires controller approval. Keep a log of any entries posted to locked periods, including why, what was posted, and who approved the reopening.
Further reading and source references
- ISA 315 (Revised 2019), Identifying and Assessing Risks of Material Misstatement: how auditors evaluate your close process as a control, including the five-element framework for understanding controls.
- ISA 240 , The Auditor’s Responsibilities Relating to Fraud: the journal entry testing requirements that align with your close-process journal review.
- ISA 520 , Analytical Procedures: the analytical framework that applies to your management reporting variance analysis.
- ISA 600 (Revised), Special Considerations (Audits of Group Financial Statements). Intercompany recon requirements for group engagements.
- IAS 1 , Presentation of Financial Statements: the offsetting prohibition ( IAS 1.32 ) relevant to balance reclassifications in the close.