What it is
Before recording, the live payments are summed and the true amount owed computed. A payment above that is trimmed to it; an order with nothing owing refuses the payment. The panel separately warns when the recorded payments already exceed the order total.
Also called: negative balance · overpaid the supplier · pay in full wrong amount
See it
How it works
- 1recordPayment reads listPayments rather than trusting amount_paid — 'exactly the number a bad write would have corrupted'
- 2owed = total − already paid; a payment is clamped to it
- 3An order with 0.009 or less owing returns null and records nothing
- 4The panel surfaces any historical overpayment with 'remove a payment to correct it'
Why we built it
'You cannot pay more than you owe. Without this the balance went negative and "Pay in full" started quoting a nonsense figure.'
The problem
- A negative balance makes every downstream figure nonsense
- A corrupted cache used to compute the next payment
Sound familiar?
What you get
The balance can never go below zero
Historical overpayments are surfaced rather than hidden
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →