Monthly Close Dashboard: Track Exceptions before Finalisation
A practical guide to monthly close dashboard, with a worked example, evidence checklist, common mistakes and steps to prepare a defensible working.
AI Summary
Eight reconciliation tasks are marked complete but three unresolved differences remain. The useful result is a working that explains the facts, the calculation or classification, and the evidence behind the conclusion. This guide shows how to prepare that working and where a reviewer should investigate before accepting the result.
Scope and applicable period
Practical software and accounts workflow. Features depend on the actual product, edition, subscription and version. The example illustrates a control or computation, not certification of an installation.
Verification date: 11 October 2026. Figures and rates identified as assumptions are teaching examples; apply the stated conditions and the actual facts to a real assignment.
The key principle
A monthly-close dashboard should track unresolved accounting issues, their effect and the evidence needed to close them. A green status is a conclusion supported by a reconciliation, not a substitute for one. Define owners, due dates and escalation rules, and separate task completion from financial accuracy. The dashboard can be a simple controlled register; no automatic software feature is assumed.
Worked example
| Item | Value or fact | What it means |
|---|---|---|
| Bank reconciliation | ₹25,000 unexplained | Owner: treasury |
| Receivable ageing | 12 invoices missing dates | Owner: collections |
| Payroll provision | ₹40,000 estimate pending | Owner: payroll |
| GST reconciliation | 2 unmatched invoices | Owner: tax |
| Release status | Review pending | Do not equate task count with readiness |
Prioritise the ₹25,000 unexplained bank difference by its nature and materiality, not only by the number of open tasks. An invoice-date gap can distort ageing even when the ledger total agrees. Record the proposed adjustment, supporting document and reviewer decision for each issue. Recheck affected totals after corrections, and identify any unresolved item carried forward with an explicit reason. A financial builder can support the resulting preparation workflow, while the dashboard preserves accountability for the evidence and judgement.
A practical sequence
List the close tasks and assign an owner, due date and evidence reference to each. Track the amount and nature of every exception so that material issues receive attention.
Escalate blocked decisions and record approved adjustments. Reconcile affected balances after changes and confirm reviewer closure before release.
Carry forward only explicitly assessed items with reasons and owners; a dashboard’s completed percentage should never conceal an unexplained financial difference.
Validate the output as well as the operation
Software can organise or calculate data quickly, but its result depends on the input population, configuration and the user’s decisions. Retain the original source, test a few known records and reconcile control totals after import or transformation. Check version support before distributing formulas or prescribing menu commands. Review missing, duplicated and unusually changed records rather than focusing only on a successful operation. When a workflow requires approval, access control or retention, confirm the actual product capability and supplement it with a documented team procedure where needed. A technically successful import is not the final accounting review.
Evidence checklist
Keep the following records linked to the same entity, period and working version. Identify missing items explicitly; a checked box should mean the document was examined and supports the stated conclusion.
- Close calendar
- Owner and exception register
- Reconciliation references
- Approved adjustments
- Release and carry-forward decisions
Common mistakes and how to avoid them
- Closing tasks without attaching evidence. Compare the conclusion with the close calendar and resolve any conflicting facts.
- Counting open items without assessing impact. Trace the affected item to the reconciliation references before finalising the working.
- Changing source data after release without renewed review. Use the release and carry-forward decisions to make the final position and remaining exceptions clear.
Before you finalise
Recheck the example’s assumptions against the actual assignment, resolve the identified exceptions and make the final figure or conclusion traceable to its source. Preserve the reviewed version and the reason for material changes. For this task, the release and carry-forward decisions should agree with the conclusion presented to the client, reviewer or authority.
Frequently asked question
Can accounts be released with open items? Assess materiality, required disclosures and approval; never hide unresolved differences just to complete a dashboard.
Sources and further reading
Related guide: Trial balance financial statements difference reconciliation.