An issued invoice that exceeds the customer's remaining purchase-order or project funding limit should remain visible in accounts receivable if it is posted, but it should not receive ordinary collection timing without resolution evidence. Split the supported amount from the blocked amount when the source permits it, assign an owner for the limit exception, and avoid treating an internal customer approval delay as observed cash timing.
A funding control can block payment readiness
Microsoft documents project funding limits as caps on the amount that can be billed and distinguishes committed amounts from spent amounts. The exact system and contract can differ by customer, but the operating lesson is consistent: submitted work, an issued invoice, customer approval, and payment readiness are separate states.
Accounting-community discussions describe invoices held for purchase-order mismatches, missing goods or service receipt, and delayed approval. Those discussions provide current workflow vocabulary rather than a universal rule. Contract terms and the customer's system remain the source for the specific invoice.
The missing-PO guide applies when the identifier is absent. A funding-limit exception is different: the PO or contract exists, but the remaining authorized amount may be below the invoice or line item.
Separate supported and blocked amounts
Build a control record with:
- invoice number, date, due date, currency, and posted open balance;
- customer PO, contract, project, or funding-source identifier;
- stated funding limit and its evidence date;
- amount already invoiced, committed, or consumed in the customer workflow;
- invoice amount accepted within the remaining limit;
- amount blocked or disputed because the limit is exhausted;
- required change, such as a PO increase, amendment, split invoice, or customer approval;
- customer-side approver and internal owner; and
- next review trigger and evidence source.
Do not mechanically reduce the accounting balance to the customer's current portal-approved amount. The books may still show the full invoice, while the forecast classifies a supported portion and a blocked exception. If the invoice must be corrected or reissued, preserve the transition with the corrected-invoice lineage workflow.
For a posted invoice, the blocked portion can remain in the source population with no expected week until an amendment, accepted split, or other current evidence supports timing. The supported portion can receive a separate assumption if the customer has accepted it and the amount reconciles. Recheck the supplier-portal acceptance framework when the customer system is the approval source.
Decision rule
Treat a funding-limit breach as an approval and amount exception, not as a reason to erase the receivable or promise cash. Keep the full source balance traceable, isolate the blocked amount, and change expected timing only when documented customer or contract evidence changes.
AR Pulse analyzes an authorized QuickBooks receivables export and ranks evidence-backed actions. It does not interpret contracts, amend purchase orders, or contact customers. Finance teams can apply for AR Pulse.