A missing customer purchase-order number should not erase an issued invoice from accounts receivable. It should become a named billing exception that weakens near-term timing evidence until the buyer's requirement is resolved.
Separate the balance from the blocker
An invoice can remain recorded and open while the customer's payment workflow requires additional reference data. Keep the invoice amount, status, due date, and aging facts unchanged unless the accounting record itself changes. Track the missing PO as a separate exception rather than changing the balance to zero or assuming a new payment date.
QuickBooks supports custom fields on sales forms, which can be used for business-specific references. Invoice creation also includes dates, terms, customer, and line details. Those fields help document the handoff, but finance still needs customer-specific evidence that a PO is required and has been accepted.
The small SaaS enterprise invoice checklist shows how procurement requirements can be checked before relying on cash timing.
Build the exception record
Capture the invoice ID, customer, open amount, due date, required PO field, source of the requirement, request date, owner, buyer contact channel, submission status, acceptance evidence, and next review date.
Use clear statuses such as requirement unconfirmed, PO requested, PO received, corrected invoice submitted, accepted by buyer, or blocked for another reason. Do not mark the exception resolved merely because a PO value was typed into an internal note. The relevant evidence is the supported buyer workflow and the current invoice record.
If a valid PO exists but the invoice exceeds its remaining authorized amount, use the customer funding-limit framework to isolate supported and blocked amounts.
Change forecast timing carefully
If the missing PO prevents the invoice from entering the buyer's payment process, remove an unsupported precise collection week or move the invoice into a wider scenario. Do not invent an exact delay. When the buyer confirms acceptance, reassess timing using the due date, payment history, dated commitments, and any stated processing schedule.
The invoice due date versus expected collection date explains why terms alone do not determine the forecast. If the invoice must be corrected or reissued, preserve document lineage rather than counting both versions.
Prevention check
Before future invoices are issued, review the customer master and billing instructions for PO format, bill-to entity, submission destination, tax or vendor identifiers, and required attachments. This is an operational checklist, not a claim that every customer requires the same fields.
For the current invoice, assign one person to obtain or validate the reference and one date to revisit the forecast. Avoid broad reminder activity that does not resolve the specific blocker. The AR exceptions report template can keep the owner and next action visible.
Decision rule
Keep the receivable visible, label the missing PO, and forecast cash only from supported timing evidence. Teams can apply for AR Pulse for a ranked cash-action list and four-week collections forecast from an authorized QuickBooks export.