What is month-end close (as an ERP health test)?

Month-end close is the accounting routine of finalising a month's transactions, reconciling bank and control accounts, posting adjustments and locking the period; used as an ERP health test, it asks how much of that work happens inside the ERP and how much in spreadsheets.

Every finance team closes the month: bank statements are reconciled, supplier bills and customer invoices for the period are posted, accruals, prepayments and depreciation are booked, stock is valued, intercompany balances are agreed, the period is locked and the management accounts are produced. The close has a duration, usually measured in working days after month end, and it has a method, which is either the ERP or a collection of exports and spreadsheets around it.

As a health test it is unusually honest, because it cannot be faked. If the accountant's first act on the first of the month is to export the general ledger to a spreadsheet, the ERP is not producing the accounts; a spreadsheet is, and the ERP is a data source for it. That tells you more about the state of the system than any feature checklist. It usually points to a specific cause: a costing method nobody trusts, a bank feed that was never set up, an intercompany process done by email, or a report the system cannot produce because a customisation broke it.

In practice I ask three questions. How many working days does the close take? Which steps happen outside the system, and why? And what would break if the spreadsheets were deleted? The answers become the first items on any ERP improvement list, ahead of new modules or dashboards.

The common mistake is treating a slow close as a finance problem to be solved with more finance staff. It is almost always a systems problem: a missing configuration, a broken automation, or data that was never cleaned, and each of those is cheaper to fix than a permanent extra day of every month.

Related terms

See it in practice