When an invoicing platform accepts a small payment difference and marks an invoice paid, record the amount actually received as cash and the residual as a separate posted credit or forgiveness adjustment. Do not inflate the receipt to the invoice total, and do not keep forecasting the residual after the source system has explicitly settled it.
A paid invoice can contain two value events
Stripe documents automatic reconciliation for bank-transfer invoices and a configurable option that can reconcile a partial payment when the difference falls within a chosen tolerance. The platform can apply a credit for the outstanding difference and then mark the invoice paid.
That status is operationally convenient, but it compresses two events into one label:
- cash received from the customer; and
- an adjustment that clears the remaining amount.
If a forecast imports only the final paid status and total invoice amount, it can overstate cash. If it imports only the partial receipt and ignores the posted adjustment, it can leave a false open residual.
The short-paid invoice guide covers a residual that still needs resolution. If a formal credit follows an earlier partial payment, use the partial-payment credit-note workflow.
Reconcile amount by event
Preserve:
- original invoice amount and currency;
- received amount and settlement date;
- configured tolerance at the decision time;
- residual amount;
- credit, adjustment, or forgiveness transaction identifier;
- final invoice status and timestamp;
- reviewer and policy owner; and
- whether the tolerance setting changed after the invoice was issued.
Then test:
`invoice amount = observed cash + posted residual adjustment + current open amount`
The equation is a control, not an accounting instruction. If a source transaction is missing, keep the residual as an exception until the system record explains the paid status. Never fill the gap with an assumed receipt.
Also preserve currency and processor context. A tolerance configured for one workflow should not be copied into another invoice population without evidence that the same rule applied at the settlement time.
During forecast variance review, classify the result as cash collected for the received amount and non-cash resolution for the tolerance adjustment. That keeps cash performance, AR settlement, and operational automation from being blended.
Decision rule
A tolerance can close an invoice without increasing the amount that reached the bank. Forecast and report only observed cash as cash; use the explicit system adjustment to explain why no residual remains collectible.
AR Pulse analyzes an authorized receivables export and produces an evidence-based action list and four-week collections view. It does not configure payment tolerances or change accounting systems. View the example report.