A resolved dispute can return an invoice to ordinary forecast review only after finance identifies what the resolution changed. A `Resolved` label is not a collection date. The invoice may remain open at its original amount, receive a credit or adjustment, be rebilled, or gain new payment evidence. Each outcome requires a different cash assumption.
Microsoft's collections-status guidance distinguishes disputed transactions from resolved ones and describes resolved as the point where the identified problem has been addressed. Oracle's receivables documentation shows that dispute resolution can involve notes, approvals, credit memos, receipt reversals, and rebilling. Those artifacts—not the label alone—determine the revised open amount.
Ask what changed in the source
Start with four questions:
- Did the posted invoice amount change?
- Was a credit memo, adjustment, rebill, or replacement invoice recorded?
- Did the customer provide a dated payment commitment after resolution?
- Does the next authorized export reconcile the new state to the AR control total?
If none of these changed, the invoice can leave the dispute queue but should remain unassigned in the collections forecast until timing evidence exists.
Route the common resolution outcomes
| Resolution outcome | Amount treatment | Timing treatment | | --- | --- | --- | | Dispute rejected; invoice unchanged | Keep the supported open amount | Require new timing evidence | | Partial credit approved and posted | Reduce only the credited portion | Forecast the residual separately | | Full credit or cancellation posted | Remove the credited open amount | Do not forecast payment on the retired balance | | Credit-and-rebill completed | Link old and replacement records | Forecast only the supported current invoice | | Customer commits to a dated payment | Keep the source open amount | Use the commitment as one input with a confidence label |
Use the partial-dispute framework when only specific line items are contested. Use the pending-credit guide until the accounting source actually records an approved credit.
Preserve the decision trail
Record the prior dispute amount, resolution date, resolution type, source document, revised open amount, owner, next action, and forecast treatment. If the invoice is rebilled, keep the old and new identifiers linked so both are not counted. If receipts or adjustments were reversed during the process, reconcile them before rebuilding the four-week view.
The corrected-and-reissued invoice workflow provides a useful lineage pattern. When the outcome includes a new commitment, the promise-to-pay guide keeps amount, date, invoice scope, and status separate.
Do not confuse workflow completion with cash confidence
Resolving the underlying billing problem can remove a blocker, but it does not prove payment will follow. A clean source balance and a clear owner may justify moving the invoice back into routine review. A specific week still needs evidence that supports that timing.
Decision rule
Move a resolved dispute back into the forecast only after reconciling the resulting source state. Update the amount from posted records, preserve the resolution trail, and assign timing from current collection evidence rather than from the status change itself.
AR Pulse analyzes an authorized receivables export and produces a ranked cash-action list with a four-week range. It does not approve credits, resolve disputes, or promise a collections outcome. Apply for an AR Pulse review when resolution states need invoice-level reconciliation.