Records / Analysis workspace

Receivables ageing & collection priorities

Prioritise outstanding collections using due dates and conditional gap relief.

Read the results, assumptions and source references

On this page 4

As of ledger snapshot 2026-10-16. Ageing uses source-backed contractual due dates. Expected collection dates remain separate; missing due dates stay unknown. Each possible collection is a separate hypothetical calculation, not money on hand or a combined plan.

Review possible duplicate invoices first · Compare plans and owner-reviewed drafts

USD — outstanding balances

Not overdue (includes due today)USD 0.00

1–30 days overdueUSD 0.00

31–60 days overdueUSD 0.00

61–90 days overdueUSD 0.00

Over 90 days overdueUSD 0.00

Due date unknownUSD 8,000.00

1. inv-client-001

Counterparty unknown; external reference unknown.

OutstandingUSD 8,000.00

Contractual due: unknown; Due date unknown. Expected collection: 2026-10-20. Due evidence: ev-client-invoice; invoice source: ev-client-invoice.

If the entire remaining amount arrived on 2026-10-16: worst floor shortfall, baseline → conditionalUSD 0.00 → USD 0.00

Conditional cash-gap reductionUSD 0.00

Review contractual due date / party / reference · Review expected collection date

EUR — outstanding balances

Not overdue (includes due today)EUR 0.00

1–30 days overdueEUR 0.00

31–60 days overdueEUR 0.00

61–90 days overdueEUR 0.00

Over 90 days overdueEUR 0.00

Due date unknownEUR 0.00

Ranking assumptions

Each invoice is tested separately as if its entire remaining balance were collected on the ledger snapshot date. Outflows precede same-day inflows. This conditional ranking is not a collection promise, a combined plan, a probability or observed cash. Ageing uses contractual due date only; expected collection date never substitutes for it.

Order: conditional gap reduction, days overdue, outstanding amount, then stable invoice ID. This does not infer customer willingness or authorize messages.