DunningTimeline
- Status
- Specified
- Family
- 10 of 13
DunningTimeline is specified but not yet built. The spec below is the contract it will be built against — reviewed before the code, which is the order that makes the review worth doing. See the roadmap for where it lands.
The four-layer spec
Full communication history per customer, not per invoice — a collector needs one timeline. Shows sent, opened, and responded, with the next scheduled step and its pause conditions.
Lifted verbatim from Receivables (AR). The doc and this page are the same paragraphs, so they cannot disagree.
The accounting it encodes
Concepts this component renders. Each one is defined once, in the lexicon, and used identically in the code and the copy.
Also in Receivables (AR)
- InvoiceFormWith the revenue-recognition preview per line.
- InvoiceDetailBalance due as the hero, not total.Spec
- InvoiceRegisterGapless-numbering check surfaced.Spec
- CashApplicationThe highest-value screen in AR. Every case, not just the happy one.
- PaymentSuggestionInvoice combinations summing exactly to a lump sum.
- UnappliedCashPanelNever revenue; net credit balances flagged as liabilities.Spec
- CreditNoteFormDistinct from a refund and from a write-off.Spec
- CollectionsWorklistPromise-to-pay as a first-class object.Spec
- CustomerStatementPrintable. Print styles are first-class.Spec
- CustomerCreditPanelLimit and exposure together, with hierarchy roll-up.Spec
- SalesOrderTableBacklog, visually separated from ledger-derived numbers.Spec
- ArMetricsPanelDSO with its method stated.Spec
See also
A component is specified in one place, defined in another, and running in a third. All three, from here.
- Receivables (AR) — the family specThe four-layer specification this component was built against, before it was written.Doc
- Receivables — order to cashThe family running, with real figures in it, in both themes and at every density.Live
- CatalogAll 179 components, specified before they are written.Doc
- DunningThe sequence of collection communicationsTerm
Elsewhere in the system
Where DunningTimeline sits in the rest of the system — the live section it renders in, the calculators that compute what it displays, and the ledger payloads it is fed from.
Components are copied into your repository and meant to be edited — rounding policy, fiscal calendar and compliance copy differ per company.
Told when Receivables (AR) changes
Components are copied into your repo, so a fix here does not reach you on its own. One email when a component in this family changes in a way that needs a migration — and nothing when it does not.