Know what the report includes
A useful report states its as-of date, currency, source and included invoice records. It also shows the last successful source update. Without that context, an overdue total can look precise while being out of date or covering only part of the business. Describe an agreed imported list as that list, rather than presenting it as the complete accounts receivable ledger.
Keep currencies separate unless a documented conversion method and exchange-rate date have been agreed. Translating a page into Danish does not turn pounds into kroner. The example remains in GBP in both languages. A future report should also identify excluded, voided or settled records so a reader understands why they do not appear in open balances.
Separate outstanding, overdue and not yet due
As of 3 October 2026, the four fictional invoices total £2,350 outstanding. EX-101 contributes £900 after its £300 part payment. EX-102 contributes £650. EX-104 contributes £800 and is not due until 10 October. EX-103 has no remaining balance after a £200 credit and £1,800 payment. Only the £900 and £650 balances are overdue, giving £1,550 overdue and £800 not yet due.
EX-102 is disputed. Its £650 remains included in both outstanding and overdue totals until the underlying accounting position changes. Show the dispute as a flagged subset of those totals, not another £650 added to them. The flag changes the appropriate next action to investigation; it does not remove the amount or justify a stronger reminder.
Use ageing to organise attention
Ageing groups open balances by how many days they are past their due date on the as-of date. The example uses non-overlapping groups: Not overdue, 1–30, 31–60, 61–90 and 91+ days overdue. EX-101 is 15 days overdue and EX-102 is 30 days overdue, so both sit in 1–30. That group totals £1,550; the later groups are £0.
Age alone does not decide who receives a message next. Add context: an unresolved query, a recent reply, an incorrect contact, a payment awaiting verification or a missing owner. A large old balance may need a phone discussion by the business rather than another email. The proposed view would help an owner choose the next task; it would not make collection or legal decisions.
Count activity without presenting it as money received
Drafts prepared, approvals reviewed, messages sent, replies received and open queries describe work. Each needs a clear definition and reporting period. A draft is not a sent reminder; a reply is not a resolved issue. If sending is not implemented, report no operational sending result. The public example can show illustrative states, but cannot provide customer performance evidence.
Verified allocated payments are a separate measure. A credit reduces the debt but is not collected cash. New sales and profit are different again: receiving payment for an existing invoice does not create another sale. Time released also needs evidence from the business’s actual process. We do not infer savings or claim a performance percentage from the demonstration.
Distinguish due dates, promises and forecasts
A schedule of due dates shows when invoices are contractually due. A customer-stated payment date records what that customer says they intend to do. A modelled forecast estimates receipts using an explained method and assumptions. These are three different views. A due-date chart is not a predictive cash-flow model, and a payment promise is not a guaranteed receipt.
Invoice receipts are only one part of a business’s cash position. Payroll, supplier payments, tax, borrowing and other income sit outside this section. Advanced forecasting is not advertised as available in Procora’s planned invoice service. Discuss the decisions you need to make before selecting a reporting measure, and avoid calling a list of expected invoice receipts a complete cash forecast.
Review changes and the work left open
When the example applies a simulated verified £900 payment to EX-101, outstanding falls to £1,450 and overdue to £650. EX-102 remains disputed and needs its owner’s attention. The example changes a single payment allocation; it does not show that a reminder caused the payment. A future report should let the owner trace a changed balance to the underlying source record.
Days sales outstanding, often called DSO, relates unpaid customer balances to sales over a defined period. A small imported overdue list is not enough to calculate a company-wide figure. Where the necessary complete data and method are absent, leave that metric out. Bring your current report and the questions it fails to answer to a scope discussion, without uploading customer-sensitive records here.
Explore the example
Illustrative workflow · sample data · no messages or payments are processed.
EX-101 has £900 remaining. Check the current balance and contact before preparing a reminder.
- Outstanding
- £2,350
- Overdue
- £1,550
- Not yet due
- £800
Disputed subset: £650 · already included above; never added again.
As of 3 Oct 2026 · GBP · due-date ageing, remaining balances only.
| Invoice / customer | Due date | Remaining | State / age | Next action / owner | Last update |
|---|---|---|---|---|---|
| EX-101Example A | 18 Sept 2026 | £900 | Part-paid15 days overdue | Review balanceOwner A | 3 Oct 202609:00 UTC · sample snapshot |
| EX-102Example B | 3 Sept 2026 | £650 | Disputed · reminders paused30 days overdue | Resolve queryOwner B | 3 Oct 202609:00 UTC · sample snapshot |
| EX-103Example C | 25 Sept 2026 | £0 | Settled— | Close recordOwner A | 3 Oct 202609:00 UTC · sample snapshot |
| EX-104Example D | 10 Oct 2026 | £800 | Not yet due— | Check contactOwner B | 3 Oct 202609:00 UTC · sample snapshot |