An issued invoice should remain visible in accounts receivable when it is still open, but an email send or portal upload alone should not justify a collection week. Record whether the customer's payable system accepted, rejected, held, or has not confirmed the invoice, then use that status as operational evidence for the forecast and action queue.

Separate issuance from buyer acceptance

The accounting system can show a valid open invoice while the customer's process shows something else. A supplier portal may require a purchase-order reference, vendor identifier, tax field, attachment, or buyer approval. Coupa's supplier documentation exposes invoice statuses and explains how suppliers respond when an invoice is rejected or placed on a tolerance hold. Those states are evidence that the invoice has not completed the buyer's payable workflow.

Community accounting discussions use the same practical language: invoices can be emailed to the wrong destination, uploaded but not accepted, or silently rejected. Treat that language as discovery evidence, not as a benchmark for how often the problem occurs.

Use a small status model

Track one status for the invoice's customer-side path:

| Status | Forecast treatment | Internal action | | --- | --- | --- | | Not submitted | Keep open; timing unassigned unless other evidence exists | Submit through the required channel. | | Submitted, no confirmation | Keep visible; do not infer acceptance | Verify receipt or portal state. | | Accepted or approved | Eligible for timing review; acceptance does not establish cash | Add current payment evidence or commitment. | | Rejected | Remove unsupported timing | Correct the named rejection reason and resubmit. | | Hold or exception | Use a conditional or unassigned assumption | Assign the blocker to an owner. |

The undelivered-invoice guide covers failed email delivery. Portal rejection is distinct: the document may have reached the portal but failed a customer rule. The missing purchase-order workflow addresses one common prerequisite without assuming it is the only cause.

When the portal explicitly shows a rejected status, use the rejected supplier-portal invoice guide to preserve the correction chain, remove unsupported timing, and prevent a replacement invoice from being counted twice.

Preserve dated evidence

For material invoices, store the invoice number, customer, amount, due date, required submission channel, submission timestamp, portal reference, current status, rejection or hold reason, last verified date, internal owner, and next review date. Keep screenshots or portal messages only in the authorized operating system; do not place private customer details in public content.

When the status changes, append the new event rather than overwriting the prior one. A later acceptance can support a revised collection assumption, while a rejection should expire a timing assumption that depended on successful submission. The stale-evidence framework explains how to retire outdated status notes.

Decision rule

Keep the invoice in the receivables control total, but do not treat upload or email delivery as buyer acceptance. Use the customer-side status to rank the internal blocker and assign a collection week only when current evidence supports it. AR Pulse creates this kind of exception-first action view from an authorized QuickBooks receivables export; it does not contact customers or promise collection outcomes. Apply for AR Pulse.