Blog · Board and management reporting · Finance and FP&A teams
An accounts receivable dashboard connects unpaid invoices, overdue balances, collections, and customer concentration. Follow a worked US distributor example, reconcile the balance movement, and see how one additional payment changes the collection priorities.
An accounts receivable dashboard shows which customer balances remain unpaid, how much is overdue, and whether collections are keeping pace with new invoices. Put the reconciled closing balance beside overdue exposure and customer concentration so the team can choose who to contact and explain what changed.
Receivables are a balance at a point in time; collections are movements during a period. The SEC's financial statement guide explains this distinction between balance-sheet snapshots and cash flows over time. Show both the balance date and collection period on the dashboard.
Use an invoice export with invoice ID, customer ID, original amount, invoice date, due date, and open amount. Add payment applications with payment ID, invoice ID, application date, and amount, plus credit memos and other adjustments. Preserve customer and parent-group identifiers where they exist.
Organize the layout around these questions:
| Dashboard area | Measure | Decision it supports |
|---|---|---|
| Balance check | Opening-to-closing receivables movement | Whether the report is complete |
| Collection priority | Overdue amount and share | Which exposures need attention |
| Cash movement | Applied collections by month | Whether invoice settlement is rising or falling |
| Customer exposure | Largest customer and group shares | Where collection dependence is concentrated |
| Follow-up detail | Customer, invoice, dispute, owner | Who does what next |
This page covers measure selection and layout. The dedicated accounts receivable aging guide owns the detailed aging method and bucket construction.
A US industrial distributor reviews September 2026, using a September 30 balance cutoff. All balances below are gross trade receivables before any credit-loss allowance. New invoices, applied cash, and credit memos are September movements; there are no write-offs or other adjustments in this example.
Closing receivables = Opening receivables + New invoices - Applied cash - Credit memos
| Customer | Opening AR (USD) | New invoices (USD) | Applied cash (USD) | Credit memos (USD) | Closing AR (USD) |
|---|---|---|---|---|---|
| Atlas Manufacturing | 80,000 | 60,000 | 70,000 | 0 | 70,000 |
| Beacon Supply | 60,000 | 40,000 | 50,000 | 5,000 | 45,000 |
| Cedar Industrial | 40,000 | 50,000 | 30,000 | 0 | 60,000 |
| Delta Equipment | 20,000 | 30,000 | 25,000 | 0 | 25,000 |
| Total | 200,000 | 180,000 | 175,000 | 5,000 | 200,000 |
Atlas closes at 80,000 + 60,000 - 70,000 = $70,000. Beacon closes at 60,000 + 40,000 - 50,000 - 5,000 = $45,000. The company check is 200,000 + 180,000 - 175,000 - 5,000 = $200,000.
The total balance did not change, but the reason matters: $175,000 of applied cash and $5,000 of credits offset $180,000 of new invoices. Describing that as $180,000 collected would overstate cash collection. Tie the opening and closing totals to the trade receivables ledger, and keep allowance entries separate from the gross balance used here.
Use due dates and the same September 30 cutoff to divide the open invoice rows into current and overdue amounts. Here, an invoice becomes overdue after its due date; an invoice due on September 30 remains current for this snapshot.
The Microsoft Dynamics 365 customer aging documentation distinguishes the balance cutoff from the aging date and offers transaction-date, due-date, and document-date criteria. That distinction matters when comparing exports: an invoice's age since issue is not necessarily its lateness against payment terms. Covirage is not affiliated with Microsoft.
| Customer | Current AR (USD) | Overdue AR (USD) | Closing AR (USD) | Share of closing AR |
|---|---|---|---|---|
| Atlas Manufacturing | 25,000 | 45,000 | 70,000 | 35.0% |
| Beacon Supply | 30,000 | 15,000 | 45,000 | 22.5% |
| Cedar Industrial | 10,000 | 50,000 | 60,000 | 30.0% |
| Delta Equipment | 20,000 | 5,000 | 25,000 | 12.5% |
| Total | 85,000 | 115,000 | 200,000 | 100.0% |
Current plus overdue must equal closing AR: 85,000 + 115,000 = $200,000. The overdue share is 115,000 / 200,000 = 57.5%. Customer shares divide each closing balance by $200,000; percentages throughout this example are rounded to one decimal place.
Atlas is the largest balance, but Cedar is the largest overdue exposure. Cedar's $50,000 is 50,000 / 115,000 = 43.5% of all overdue receivables. Atlas and Cedar together represent (70,000 + 60,000) / 200,000 = 65.0% of closing AR. Collections should investigate Cedar's payment status while the credit manager reviews the combined exposure.
If customers belong to the same corporate group, use the account hierarchy guide to distinguish payer-level detail from parent-level concentration.
The payment-application export gives this monthly history for the same customer scope. These are applied collections, not a claim about all cash received into the bank.
| Customer | July applied cash (USD) | August applied cash (USD) | September applied cash (USD) |
|---|---|---|---|
| Atlas Manufacturing | 60,000 | 65,000 | 70,000 |
| Beacon Supply | 40,000 | 45,000 | 50,000 |
| Cedar Industrial | 25,000 | 25,000 | 30,000 |
| Delta Equipment | 25,000 | 25,000 | 25,000 |
| Total | 150,000 | 160,000 | 175,000 |
Applied cash rises by (160,000 - 150,000) / 150,000 = 6.7%, then by (175,000 - 160,000) / 160,000 = 9.4%. This is a dollar trend, not proof of better payment behavior: changes in billings, due dates, or application timing can affect it. For a defined percentage measure, use the separate accounts receivable collection rate method and retain its denominator consistently.
Now assume Cedar makes an additional $20,000 payment, applied against overdue invoices before the September cutoff. Everything else stays the same. This is an alternative outcome, not another month of actual results.
| Measure | Original outcome | Additional-payment outcome |
|---|---|---|
| September applied cash (USD) | 175,000 | 195,000 |
| Cedar closing AR (USD) | 60,000 | 40,000 |
| Cedar overdue AR (USD) | 50,000 | 30,000 |
| Total closing AR (USD) | 200,000 | 180,000 |
| Total overdue AR (USD) | 115,000 | 95,000 |
| Overdue share | 57.5% | 52.8% |
The revised balance check is 200,000 + 180,000 - 195,000 - 5,000 = $180,000. Overdue share becomes 95,000 / 180,000 = 52.8%. Atlas now has the largest overdue amount, so the next collection priority changes even though no new invoices or credits changed.
Bring invoice, payment-application, and credit-memo exports with a fixed cutoff. Covirage maps the columns; its tools compute and check the balance movements, overdue shares, and customer totals, while the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.
See how this fits FP&A reporting in Covirage.
Include closing trade receivables, current and overdue balances, applied cash collections, adjustments, and customer concentration. Show the reporting cutoff and reconciliation status. Add collection ownership and dispute context where available, so a large overdue balance has an identifiable next action.
No. Receivables can fall because of collections, credit memos, write-offs, or lower new billings. A balance movement table separates those causes. Compare applied cash with earlier periods and inspect the remaining overdue invoices before concluding that collection performance improved.
Keep unapplied cash visible as a separate reconciliation item until it has been matched to the appropriate invoice. Cash receipt and invoice settlement are different events. Otherwise the dashboard can show an invoice as overdue while simultaneously treating an unrelated payment as if it cleared that invoice.
Use the level at which the company manages the exposure, and label it. A subsidiary view helps collectors contact the right payer; a parent-group view shows combined dependence. Retain both identifiers when available and do not add the same balance twice.