Treat a short-paid invoice as two observed amounts: cash already received and a residual balance that still needs classification. Do not automatically forecast the residual as a later receipt, and do not silently reduce it as though an approved credit already exists.
Microsoft's trade-allowance documentation describes registering a customer's short pay as a deduction and later reconciling it with the applicable claim. Microsoft's deduction-workbench guidance separately preserves the customer payment, invoice relationship, deduction type, and balance. These enterprise workflows illustrate a general control for a smaller finance team: the short-paid difference remains an owned exception until its source and disposition are verified.
Start with the source amounts
Preserve the original invoice amount, receipt amount, receipt date, amount applied, and remaining open balance from the authorized accounting source. Also retain the report date and source-row reference.
If the receipt has not been applied to the invoice in the source system, use the unapplied-payment review before calling the invoice short paid. A bank amount that resembles an invoice is not enough to establish the relationship.
Classify the residual before forecasting it
Use one evidence state:
- **Planned installment:** Current documentation supports another payment for the remainder.
- **Customer deduction:** The customer has identified an amount it withheld and a reason or claim reference exists.
- **Disputed residual:** Pricing, quantity, scope, delivery, tax, or another issue is unresolved.
- **Credit pending:** An internal review indicates a credit may be appropriate, but the source record has not yet been updated.
- **Unexplained difference:** The receipt and invoice do not yet reconcile to a supported reason.
These labels do not decide the accounting entry or legal validity of a customer claim. They decide how the working forecast should expose uncertainty while the authorized owner resolves the source issue.
Separate actual cash from expected cash
Close the received portion as an actual receipt using the defined cash cutoff. Keep the residual visible with its evidence state, owner, next action, and review date.
Assign the residual to a future forecast week only when current evidence supports both the remaining amount and timing. A planned installment with a dated agreement may support a week. An unexplained difference, pending credit, or open dispute should remain blocked or unconfirmed rather than being carried forward automatically.
The partial-payment forecast guide covers the broader residual-balance workflow. A short pay uses that same source control but adds a specific question: is the difference still expected cash, or is it an unresolved deduction or adjustment?
If the platform closes a small residual under a configured tolerance, the automatic reconciliation tolerance guide separates the received amount from the posted non-cash adjustment.
Give the exception a complete handoff
Record:
- invoice and receipt identifiers;
- original, received, and residual amounts;
- observed reason and evidence source;
- internal accounting, commercial, or delivery owner;
- next validation action and review date;
- current forecast treatment;
- later outcome and source update.
If the reason changes, preserve the earlier state and date. The history is useful for learning whether forecast misses came from unsupported carry-forwards, slow internal resolution, or incomplete source reconciliation.
The decision rule
Received cash is actual. The remaining balance is a separate decision. Forecast it only when the source amount and timing evidence are both supportable; otherwise keep it visible as a blocked or unconfirmed exception.
AR Pulse analyzes a customer-provided QuickBooks receivables export to create a ranked cash-action list and four-week collections forecast. It does not change accounting records, adjudicate deductions, contact customers, or promise payment outcomes. Finance owners can apply for AR Pulse for an invoice-level review.