Four runs, one tied total
Money leaves in runs, and most teams stop reconciling at the bank file. May’s four runs sum to 816,800.00, the roll-forward’s paid line to the cent, and the discount score prices what stuck invoices cost: 1,230.00 that expired while bills waited.
◆ May, the four runssumming to the paid line exactly.
| Run | Paid |
|---|---|
| Run 1, week one | 198,400.00 |
| Run 2, week two | 224,750.00 |
| Run 3, week three | 187,300.00 |
| Run 4, week four | 206,350.00 |
| Paid in May | 816,800.00 |
The total is the roll-forward’s paid line to the cent, which is the reconciliation that keeps treasury and the subledger telling one story. Four runs, four files to the bank, one number the module already promised. Sample values are illustrative, never client data.
◆ The discount scoreoffered, taken, and the expensive kind of lost.
| Early-payment discounts, May | Amount |
|---|---|
| Taken | 4,890.00 |
| Lost | 1,230.00 |
| Offered | 6,120.00 |
The lost 1,230.00 has addresses: discounts expire on invoices stuck in the match queue or waiting on approvals. Pricing the loss monthly turns process friction into a number someone can be asked about, which is how friction actually gets fixed.
◆ The owned answerruns and terms as data.
Payments land on the supplier star with their run and applied invoices; terms live with the invoice lines. The run reconciliation and the discount score are both groupings, and the lost list names its invoices without anyone exporting anything.
- AP
- Accounts payable, the money owed to suppliers.
- payment run
- One batch settlement to the bank.
- paid line
- The roll-forward’s settlement flow; the runs must sum to it.
- discount taken
- Early-payment savings actually captured.
- discount lost
- Savings that expired, usually on stuck invoices.