A QuickBooks invoice that is pending internal approval can appear in the accounting record, but it is not yet collection-ready evidence. Keep its open balance visible for reconciliation, then place it in an approval exception queue instead of assigning a confident collection week.

Separate three statuses

Internal approval, customer delivery, and payment are different events. QuickBooks Online Advanced can mark an invoice Pending Approval before it becomes Approved and can then be sent to the customer. Separately, QuickBooks records unpaid invoices in Accounts Receivable. That means an export can contain a valid open balance while the operational path to customer payment is still blocked.

Use three fields rather than one overloaded status:

| Evidence field | Question it answers | Forecast use | | --- | --- | --- | | Accounting status | Is there a recorded open receivable? | Reconcile the invoice population and amount. | | Approval status | Has the internal approver released the invoice? | Identify the blocker, owner, and review date. | | Delivery status | Was the approved invoice sent or accepted by the buyer? | Assess when customer processing could begin. |

Do not infer delivery from approval or infer likely cash from either event. The undelivered-invoice guide covers the next boundary when an invoice exists but delivery evidence fails.

Preserve the dated export

Record the export timestamp, invoice ID, customer, invoice date, due date, open balance, approval status, approver, and last status-change time. If approval changes after the export, append the event rather than silently rewriting the source snapshot. The weekly AR snapshot change log shows how to bridge later changes into a current review.

An approval delay does not automatically change the contractual due date. Keep the recorded due date separate from the expected collection date. The due-date versus collection-date guide explains that distinction.

Assign the exception

For every pending-approval invoice, capture:

  • the named internal approver;
  • the evidence or correction still required;
  • the next action and review date;
  • whether the customer has received any version;
  • the current open balance; and
  • the rule for reassessing forecast timing after approval.

Avoid inventing a fixed delay such as “add seven days.” Approval duration depends on the actual workflow. Until the blocker clears, retain the receivable for reconciliation, label collection confidence as constrained, and keep the amount out of any week that lacks supporting evidence.

Decision rule

Treat Pending Approval as a workflow exception, not as proof that the invoice is invalid and not as proof that cash is coming. Preserve the open row, expose the blocker, and assign a collection week only after approval and delivery evidence support it. Finance teams can review the AR Pulse example output to see how invoice-level evidence becomes a ranked action list and four-week range.