Why dashboard numbers change after the month is closed

Open the closed trial balance and the dashboard side by side. The gap is rarely a formula error. Something was posted into the old month after the pack went out. Finance teams usually find the culprit by sorting the general ledger on entry date rather than posting date, which exposes every voucher keyed after the books were signed off.

The usual suspects are few. A supplier bill entered on the fifth carries an invoice date of the twenty-eighth. A credit note is raised against last month’s sale. A journal fixes a wrong cost centre. Each lands in a period someone already reported.

A live dashboard has no memory of what it showed on the day of close. It recalculates from whatever the tables hold right now, so every late touch changes a figure you thought was settled.

A transaction carries at least two dates. The document date is what the paper says. The posting date is when it hits the ledger and decides the month. Many systems let users pick either, and reports may group by the wrong one. Reports built by different people often group by different date fields, so the sales dashboard and the aged debtors statement can disagree even when both are perfectly accurate.

Then there is refresh time. A dashboard fed by a nightly extract shows yesterday’s ledger. Say the controller exports closed books at nine. The dashboard last refreshed at two that night. They differ by whatever was keyed in between. Nobody made a mistake.

Time zones add a smaller trap. An entry stamped just after midnight in one zone can fall into the next day on a server set to another. Store every timestamp in one zone, such as UTC, and convert only for display, so a midnight entry always lands in the month the user intended.

The cure is a period snapshot. When the controller marks a month closed, the pipeline copies that month’s balances and key totals into a frozen table with a close timestamp and a version number. The snapshot job should run once, immediately after the controller presses the close button, and write its totals to a table that no ordinary report user can edit.

Dashboards for closed months read the snapshot. The current month reads live data. Both can sit on one screen as long as each figure is labelled with its source.

A late correction goes in as a visible adjustment in the open period. Otherwise the snapshot is reissued as version two, with a note on who approved it and why.

A snapshot only holds if the source stops changing. Set a lock date in the accounting software so ordinary users cannot post, edit or delete anything dated on or before it. Most packages have this setting. It is often left off. A lock date alone does not stop a determined user, so pair it with permissions that remove edit and delete rights on vouchers dated inside any closed period.

Give one named person the right to reopen a period. Log each reopening. Late invoices then flow to the first open day, and the controller can see a short list of exceptions instead of a mystery.

Agree a cut-off calendar with purchasing and sales. Bills received by day three count for the old month. Anything later is accrued or moves forward. Staff stop guessing. A short written calendar, pinned where purchasing and sales staff can see it, will prevent more backdated postings than any warning message in the software.

Run a reconciliation between the snapshot and the closed trial balance on the day you freeze. Differences should be zero by account. Keep that check as a saved report.

Add a drift alert. Each night, compare the live total for every closed month with the snapshot and flag any gap. A gap means someone posted into a locked period or the lock is not working. Email the alert to the controller each morning with the account, month and size of the gap, so nobody must open a dashboard to learn the books moved.

This week, pick last month, find the three largest changes since close and trace each to a voucher. You will learn which habit causes most of them. Write down the cause beside each one, whether a late supplier bill, a sales return or a journal, and review that list at the next close meeting.