CashRequirements
- Status
- Specified
- Family
- 11 of 13
CashRequirements 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
Due in 7 / 14 / 30 days against available cash, with payroll as a separate prominent line. The view AP managers actually plan from.
Lifted verbatim from Payables (AP). The doc and this page are the same paragraphs, so they cannot disagree.
Also in Payables (AP)
- BillFormPer-line coding, required evidence, discount ROI surfaced.Spec
- BillDetailSource document inline beside the coding.Spec
- BillRegisterAging and approval state.Spec
- DuplicateBillAlertBlocking. Duplicate payment is the most common AP loss.
- ThreeWayMatchLine-level variances, not header totals.
- MatchExceptionQueueThe clerk's worklist.Spec
- ApprovalChainSegregation of duties enforced. Approvals bind to a version.
- ApprovalInboxMobile-first, document inline.
- PaymentRunBuilderShows the cash balance remaining after the run.Spec
- PaymentRunPreviewHold-to-confirm. Partial failure is a first-class state.Spec
- VendorMasterBank details versioned, never overwritten.Spec
- BankDetailChangeAlertThe fraud-prevention surface.Spec
- ExpenseCaptureCamera-first, policy violations shown at entry.Spec
- CardTransactionMatchMatched to receipts, never re-entered.Spec
- UninvoicedReceiptsReportGR/IR aging. The evidence for the period-end accrual.Spec
See also
A component is specified in one place, defined in another, and running in a third. All three, from here.
Elsewhere in the system
Where CashRequirements 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 Payables (AP) 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.