A small SaaS company should verify more than the invoice due date before placing a large enterprise invoice into a short-term cash forecast. Confirm that the invoice has the customer's required purchase-order reference, billing entity, delivery route, approval evidence, and internal owner. Then separate “submitted” from “accepted” and record the specific evidence behind the expected collection week.

Enterprise invoicing can add procurement steps that are less visible in the accounting export. Stripe's invoicing documentation lists purchase-order numbers among common invoice custom fields. Oracle's procurement documentation shows that purchase orders may route through multiple approvers and can be approved, rejected, reassigned, or sent back for more information. These product examples support a practical point: a valid open invoice can still be waiting inside a customer's process.

The pre-forecast checklist

For each material enterprise invoice, verify:

  • **Contracting entity:** The invoiced legal entity matches the customer's instruction.
  • **Purchase-order reference:** A required PO exists and the invoice carries the expected identifier.
  • **Billing destination:** The invoice reached the correct portal, mailbox, or customer process.
  • **Invoice acceptance:** Submission was acknowledged or its current status is visible.
  • **Service period or deliverable:** The invoice description aligns with the billed subscription period, implementation step, or approved work.
  • **Supporting documents:** Required attachments or customer forms are present.
  • **Dispute state:** Pricing, quantity, scope, tax, or service questions are recorded separately.
  • **Internal owner:** One person owns the next evidence check.
  • **Next review date:** Finance knows when the status will be checked again.

This is an operational completeness check, not legal or tax advice. Requirements vary by customer and agreement, so the customer's documented instructions remain the source of truth.

Use evidence states instead of vague notes

Assign one state to each invoice:

**Prepared:** The invoice exists but has not entered the customer process.

**Submitted:** Delivery is observed, but acceptance or approval is not confirmed.

**Accepted:** The customer process acknowledges the invoice with no known blocker.

**Blocked:** A specific requirement, dispute, or approval step is unresolved.

**Scheduled:** A credible payment commitment or schedule is documented.

Do not collapse these states into “sent.” A submitted invoice may be operationally different from an accepted one, and an accepted invoice may still lack evidence for a specific payment week.

Connect the checklist to the forecast

Copy invoice facts from the authorized accounting source, then add approval evidence in separate fields. Assign a forecast week only when the evidence supports it. Keep blocked or unsupported amounts visible but unassigned rather than forcing them into a total.

The four-week AR forecast guide explains the weekly structure. The forecast template provides fields for evidence, owners, assumptions, and observed outcomes.

Use the missing customer PO guide and vendor-setup blocker guide for distinct buyer prerequisites after issuance. If payment routing is the question, compare automatic charge and send-invoice evidence without treating either workflow as a receipt.

This page addresses the enterprise-procurement handoff for small SaaS; it does not replace a general AR prioritization workflow or a subscription revenue forecast.

AR Pulse analyzes an authorized QuickBooks receivables export and returns a ranked cash-action list plus a four-week collections forecast. It does not request accounting credentials, contact customers, or promise collection outcomes. A SaaS finance owner who needs a clearer invoice-level view can apply for AR Pulse.