Month-End Close Checklist for Controllers

Your auditor asks for the bank reconciliation 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 GL by €11,400. The audit team flags it, the partner raises a control deficiency, and your close process is now a talking point in the management letter. All of this was preventable with a structured close that caught these 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, reclassifications), core reconciliations (bank, intercompany, subledger-to-GL), journal entry review, management reporting and variance analysis, and close certification with documented sign-off. Each task should have a named owner, a deadline relative to the close date, and a documented completion status that your auditor can inspect.

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 process sits at the intersection of multiple financial statement assertions: completeness (did everything get recorded?), cut-off (did it get recorded in the right period?), accuracy (do the subledgers agree to the GL?), and valuation (are the accruals and provisions reasonable?).

When your auditor walks through your close process 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 questions cleanly reduces the auditor’s assessed risk, which translates directly into less substantive testing, fewer PBC requests during fieldwork, and a shorter audit.

A close process that doesn’t answer these questions has the opposite effect. The auditor can’t rely on the close as a control, so they’ll design additional substantive procedures to compensate. That means larger samples, more document requests, and more of your team’s time spent supporting the audit instead of running the business. The month-end close is the single process where a small investment in structure pays back the most during audit season.

The checklist below is built for a mid-market European company with €10M to €150M revenue, a finance team of two to eight people, and 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 reconciliation 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 those 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, payroll-related costs that span the period. If these are set up as recurring journal entries in your ERP, verify that 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, which means the monthly management accounts 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.

Phase 2: Core reconciliations (days 2 through 4)

Reconciliations are the backbone of the close. Each one confirms that an external or independent data source agrees with the general ledger. Your auditor evaluates reconciliation controls under ISA 315.26 and will walk through at least one as part of their risk assessment. Make them easy to inspect.

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, a date it’s expected to clear, and a named person responsible for following up. Any reconciling item older than 30 days needs investigation, not just a carry-forward.

Accounts receivable subledger-to-GL reconciliation. Run the aged receivables report and agree the total to the GL control account. Investigate any difference. Then review the ageing itself: 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 subledger-to-GL reconciliation. 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 reconciliation programme, complete it for your top 10 suppliers by balance.

Intercompany reconciliations (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 reconciliations at month-end prevent a cascade of work at year-end.

Fixed asset register to GL reconciliation. 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 well-structured journal entry review within your close process demonstrates a control that 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, cash credited directly without going through receivables)
• Entries posted on the last day of the period or the first day of the next period

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: who performed it, the criteria applied, the entries investigated, and the outcome. This documentation is exactly what your auditor will request when they perform their ISA 240.32 journal entry testing.

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 your management team the financial information they need to run the business, and it functions as an analytical review that catches errors the reconciliation 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, by division, by customer segment. 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, anomalies, and one-off items. 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, confirms that all tasks are done, and signs 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 reconciliation 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.

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.

Step 1: 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), and payroll accrual (€186,000). All are verified against the prior month for reasonableness.

Documentation note: Record the GRNI clearing, the recurring journal amounts and the prior-month comparison, and the cancelled PO in the close checklist. Each task shows the owner, date, and completion status.

Step 2: Core reconciliations (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 reconciliation is saved as a separate workpaper with the GL balance, the subledger or bank balance, the reconciling items, and the preparer’s sign-off.

Step 3: 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 to reclassify an R&D cost from opex to capex (reviewed, supported by the capitalisation policy and project documentation), and 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.

Step 4: Management reporting (days 4 through 5)

The controller produces the monthly management pack. Revenue is €4.38M against a budget of €4.50M (variance of €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.

Step 5: 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 reconciliation has a preparer and reviewer sign-off. Every variance has an explanation. Every journal entry review is 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

1. Day 1: Clear all GRNI and GDNI items. Post or accrue every goods receipt without a matching invoice. Post all recurring journals (depreciation, prepaid releases, payroll accrual) and compare amounts to the prior month for reasonableness.
2. Days 2 through 4: Complete all core reconciliations. Bank, AR subledger-to-GL, AP subledger-to-GL, intercompany (if applicable), fixed assets, and prepayments and accruals. Every reconciling item older than 30 days gets investigated, not carried forward.
3. Day 4: Run the manual journal entry listing and review entries meeting your defined risk criteria (unusual users, round amounts above threshold, unusual account combinations, last-day and first-day entries). Document the review.
4. Days 4 through 5: Produce the management reporting pack with variance analysis. Explain every variance above your dual threshold (percentage and absolute amount). Compare to budget, prior month, and prior year same month.
5. Day 5: Sign the close certification. Lock the period in the ERP.

Common mistakes auditors flag

• 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 reconciliation must be as at the period-end date. Auditors testing under ISA 500 will check the reconciliation date against the GL balance date.
• Carrying forward reconciling items month after month without investigation. The AFM’s inspection guidance flags stale reconciling items as evidence of a weak control environment. A reconciling item that has appeared on the bank reconciliation for four consecutive months isn’t a timing difference. It’s an error or a missing entry.

Related Ciferi content

Related guides:

Put audit concepts into practice with these free tools:

Frequently asked questions

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 reconciliation requirements for group engagements.
• IAS 1, Presentation of Financial Statements: the offsetting prohibition (IAS 1.32) relevant to balance reclassifications in the close.