A disputed invoice should remain visible in a four-week collections review, but its disputed amount should not be assigned to a payment week without specific evidence. Split the invoice into disputed and undisputed portions when the source supports that split, record the reason and owner, and give the dispute its own next review date.

Oracle's receivables documentation supports entering a dispute for all or part of a transaction and preserving its reason, amount, comments, approval information, and collections notes. The practical lesson is not to reduce a dispute to a single yes-or-no field.

Separate four layers

Keep ledger facts, dispute facts, operational ownership, and forecast assumptions distinct. The accounting export may show the full invoice as open even while only part is contested. Preserve the open balance while making the disputed slice visible.

Use a status that changes decisions

  • **Unverified:** a dispute is mentioned but the amount or source is unclear.
  • **Documented:** the disputed amount and reason are recorded.
  • **Under internal review:** finance or operations is validating the issue.
  • **Awaiting customer decision:** requested evidence was supplied and the next step is external.
  • **Credit or rebill pending:** an approved action has not appeared in the source data.
  • **Resolved:** the identified problem is addressed; the forecast still needs the resulting source state and fresh timing evidence.

These are operational labels, not legal conclusions. The governing agreement and authorized accounting record remain the sources of truth.

Decide what enters the weekly total

| Amount state | Forecast treatment | | --- | --- | | Undisputed with dated payment evidence | Assign only the supported amount and week | | Undisputed without timing evidence | Keep visible and unassigned | | Disputed and unresolved | Keep outside the weekly total | | Approved credit not yet recorded | Flag as a reconciliation exception | | Resolution reflected in the source | Rebuild amount and timing from current evidence |

When only part of the invoice is contested, use the line-item dispute framework. While a requested credit is pending, use the pending-credit framework instead of reducing the source amount early.

Re-enter the forecast after resolution

A resolved status alone does not establish the revised amount or collection week. The resolution may leave the invoice unchanged, create a partial or full credit, reverse receipts, or create a rebill. The resolved-dispute framework maps those outcomes back to the supported current invoice before timing is assigned.

Run the weekly review

Ask whether the amount changed, what evidence arrived, who owns the next action, when the status will be checked again, and whether any undisputed portion has separate collection evidence. Update source facts first, then the dispute state, and change the forecast only after those steps.

The invoice collection assumptions template preserves evidence, confidence, owner, and outcome fields. The AR exceptions template places disputes beside other management exceptions without hiding routine invoices.

Decision rule

Keep disputed balances visible, exclude unsupported timing, and restore ordinary forecast treatment only after the resolution's accounting effect and current collection evidence are reconciled.

AR Pulse analyzes an authorized QuickBooks receivables export, keeps findings traceable to supplied source rows, and produces a ranked action list plus a four-week collections view. It does not contact customers or promise collection outcomes. A finance owner can apply for AR Pulse for an invoice-level exception review.