A rejected supplier-portal invoice should remain visible as an accounts receivable exception, but it should not keep an unchanged collection week merely because the accounting export still shows an open balance. Separate four facts: the source-ledger balance, the portal rejection status, the corrective action required, and the next evidence that could support a new collection date.
SAP's invoice-status portal documentation distinguishes rejected invoices from invoices pending approval, approved invoices pending payment, overdue approved invoices, paid invoices, and remittances. Its invoice-rejection guidance also shows that a rejected invoice can require correction and resubmission. That workflow state is more specific than an aging bucket, but it is still not observed cash.
Keep the accounting and portal states side by side
Do not silently delete the invoice from the source population if the authorized accounting record still shows an open amount. Record the mismatch and route it for resolution. A useful exception row preserves:
- Customer, invoice number, invoice date, due date, and current open balance
- Portal name, portal invoice identifier, rejection date, and rejection reason
- Whether correction, cancellation, credit, or resubmission is expected
- Internal owner, next action, and next review date
- Replacement or resubmitted invoice identifier when one exists
- Current forecast treatment and the evidence required to change it
This structure prevents two different errors. Removing the source invoice too early can hide an unresolved ledger balance. Leaving the old collection date untouched can overstate near-term cash after the buyer has rejected the document.
Use a status matrix
| Observed state | AR control total | Four-week treatment | | --- | --- | --- | | Rejected in portal; still open in source | Keep and flag | Remove the unsupported week or mark conditional | | Corrected invoice prepared but not accepted | Keep linked records separate | Do not assign timing from preparation alone | | Resubmitted and pending approval | Keep the verified source balance | Use unconfirmed timing unless other evidence supports it | | Approved and pending payment | Keep the open balance | Assign a week only from dated payment evidence or a documented rule | | Paid with receipt applied | Reduce once | Record actual cash instead of forecast cash |
The supplier-portal acceptance guide explains why acceptance narrows the blocker without proving payment timing. Rejection moves the invoice in the opposite direction: the collection assumption needs a new evidence check.
Preserve the correction chain
If an invoice is canceled and reissued, connect the old document, correction, and replacement so the forecast cannot count both. If the same invoice number is resubmitted, preserve portal status history and the latest timestamp. If the accounting record changes later, reconcile the new export instead of back-editing the prior snapshot.
Do not infer the financial treatment from a portal label alone. The authorized accounting owner decides whether a credit, void, correction, or other book entry is required. The forecast review should expose the exception and its cash-timing consequence, not change the books.
Decision rule
Treat rejection as evidence that the prior collection date needs review. Keep the verified open balance visible, remove unsupported timing, name the corrective owner, and restore a collection week only when the resubmission and buyer-side status provide current support.
AR Pulse analyzes an authorized QuickBooks receivables export and turns source-linked exceptions into a ranked cash-action list and four-week collections range. It does not contact customers, change accounting records, or promise a payment outcome. Finance teams can apply for AR Pulse when they want a structured review of these invoice-state mismatches.