Blog · Board and management reporting · Finance and FP&A teams
A controller dashboard shows whether the accounting close is complete and which exceptions still need action. Work through completion, reconciliation differences, aging, ownership, and the checks that make the measures credible.
A controller dashboard shows whether the accounting close is ready for review and which exceptions could delay or change the results. It combines close completion, reconciliation differences, and aging with an owner and a next action for each unresolved item. Its purpose is to direct accounting work before financial results are released.
Start with separate views of completion and quality. Completion asks whether the required work has been prepared and reviewed. Quality asks whether the evidence supports the balances and whether unresolved differences have an acceptable explanation.
Do not collapse these into a single green status. A reviewed bank reconciliation can contain a documented timing item. A completed checklist can also sit beside an unexplained difference that needs escalation. The dashboard should preserve both facts.
For the financial results themselves, use the financial dashboard layout. The controller view should concentrate on the work and exceptions behind those results.
Write the definition beside each measure: its source, cutoff, inclusion rule, calculation, and accountable owner. The SEC's guidance on key performance indicators asks public-company disclosures to explain metric definitions, calculations, and management use. That disclosure guidance offers a useful discipline for an internal close report without making every internal measure a required SEC disclosure.
The close checklist needs a stable task identifier, workstream, accounting period, due date, preparer, reviewer, evidence reference, and status. Keep preparation and review separate. A file uploaded by the preparer is not automatically a reviewed task.
The exception register needs a stable item identifier, affected account, source balance, comparison balance, unresolved difference, first-open date, severity, owner, and next action. Retain the original first-open date when an item carries forward. Otherwise, a recurring exception appears new every close.
Use a dated snapshot for the review. Status changes after that cutoff belong to the next snapshot. Detailed financial data reconciliation establishes why the underlying sources differ; this dashboard summarizes which differences remain and who must resolve them.
Consider a US distributor reviewing its September close on October 8, 2026. A task counts as signed off only when the required evidence exists and the designated reviewer has accepted it. The checklist contains the following tasks due by the review cutoff.
| Workstream | Tasks due | Signed-off tasks | Tasks awaiting sign-off |
|---|---|---|---|
| Cash | 6 | 6 | 0 |
| Receivables | 5 | 4 | 1 |
| Payables | 5 | 4 | 1 |
| Inventory | 4 | 3 | 1 |
| Accruals | 5 | 3 | 2 |
| Total | 25 | 20 | 5 |
Close completion = Signed-off tasks due / All tasks due
Tasks awaiting sign-off = Tasks due − Signed-off tasks
Completion is 20 / 25 = 80.0%. The check is 20 + 5 = 25: every due task must be either signed off or awaiting sign-off. Percentages here are rounded to one decimal place, after calculating from the counts.
This is an unweighted measure. It does not say that the close has the same proportion of its risk resolved. An inventory valuation review may matter more to release than a routine reconciliation, so list blocking tasks alongside the percentage.
At the same cutoff, the register contains these unresolved items. Ages are elapsed calendar days since each item was first opened. Differences are shown as absolute amounts for the workload view; retain their signed values in the source reconciliation.
| Item | Workstream | Age in days | Absolute unresolved difference (USD) | Next action |
|---|---|---|---|---|
| C-01 | Cash | 1 | 3,000 | Obtain support for a bank timing item |
| R-01 | Receivables | 7 | 12,000 | Match a credit memo to the ledger |
| P-01 | Payables | 4 | 5,000 | Confirm the invoice posting period |
| I-01 | Inventory | 9 | 8,000 | Review the count adjustment |
| A-01 | Accruals | 12 | 2,000 | Resolve an unsupported estimate |
| Total | 30,000 |
For this review, the controller uses an internal escalation threshold of more than five calendar days. That is a local working rule, not an external benchmark. R-01, I-01, and A-01 exceed it.
| Aging measure | Calculation | Result |
|---|---|---|
| Open item count | Count the register rows | 5 |
| Items older than five days | Count R-01, I-01, A-01 | 3 |
| Aged share of item count | 3 / 5 | 60.0% |
| Aged share of absolute differences | 22,000 / 30,000 | 73.3% |
The aged absolute differences total 12,000 + 8,000 + 2,000 = $22,000, providing the numerator for the final percentage.
The amount total describes the reconciliation workload. It is not a proven financial statement misstatement. Differences may have offsetting signs, and separate controls can identify the same underlying posting. Deduplicate linked items before presenting an exposure total.
The controller owns the release decision and the definitions of blocking, accepted carryforward, and resolved. Accounting workstream leads own the next action and evidence. Reviewers confirm whether the explanation is adequate, rather than simply accepting a changed status.
In this example, the accruals lead has the largest unfinished task count. The aging view adds a different priority: the receivables credit memo carries the largest aged difference. The controller can assign review time to both without assuming that the largest number automatically presents the greatest risk.
The GAO Green Book, which sets federal internal control standards, describes management evaluation of issues and timely, documented corrective action. It is a useful control reference here, rather than a claim that a private distributor must follow federal agency standards.
Keep the reconciliation identity visible: summarized task and exception totals must tie to the underlying registers. A dashboard status cannot replace that evidence.
Bring a sample of your own close checklist and reconciliation register as files or a Google Sheet. Covirage maps the columns, its tools compute and check the figures, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account, which takes about a minute, then set up your business and bring your files.
See Covirage for finance teams for the broader finance context.
Include reviewed close tasks against tasks due, unresolved reconciliation differences, aging, severity, ownership, and the next action. Keep financial statement results available as context. A completion percentage alone cannot show whether the remaining work could change the reported results.
Divide tasks completed under the agreed evidence and review criteria by tasks due at the same cutoff. Keep the task list fixed during the comparison. If a task is excluded or deferred, show the reason rather than quietly removing it from the denominator.
No. A documented timing difference may remain open after a reconciliation is reviewed. The controller should distinguish accepted reconciling items from unexplained differences and items that block release. Record the decision, supporting evidence, owner, and expected resolution date.
The controller owns the definitions and escalation decisions. Accounting leads maintain task status and exception evidence, while reviewers confirm sign-off. The person preparing a reconciliation should not be the only person deciding whether its evidence is sufficient for completion.