An invoice sent to the wrong bill-to entity should remain visible as an open receivable and a high-priority approval exception, but it should not receive an ordinary collection date. Preserve the posted amount, identify the intended payer, confirm whether correction or reissue is required, and forecast cash only after the responsible entity has accepted a valid invoice or provided other credible payment evidence.
Order customer and invoice customer can differ
Microsoft documents that the customer associated with an order can differ from the customer account that receives and pays the invoice. It also notes that billing address, financial agreement, payment terms, and communication should align with the selected invoice account. That distinction matters in B2B service relationships with parent companies, subsidiaries, procurement entities, resellers, or shared-service payment teams.
A valid service relationship therefore does not prove that the posted invoice was addressed to the payable entity. The forecast should not solve the mismatch by assuming that one company in the group will pay on behalf of another.
Record the exception at invoice level
Capture these fields before assigning timing:
- posted customer and bill-to entity;
- intended payer and evidence for that conclusion;
- invoice number, amount, issue date, and due date;
- billing address, purchase-order reference, and tax or registration fields supplied;
- customer response or portal rejection reason;
- correction, credit, void, or reissue path;
- internal owner and next review date; and
- links between the original and any replacement invoice.
The customer setup blocker guide helps distinguish entity setup work from collection follow-up. If a purchase order names a different payer, also review the missing customer PO exception.
Keep amount and timing separate
The accounting system may continue to show the original invoice as open while the business resolves the payer. Keep that amount in the reconciliation population. In the four-week forecast, classify it as blocked or unassigned unless the intended bill-to entity has acknowledged the invoice and the correction path does not create duplicate receivables.
If the original is voided or credited and a replacement is issued, link both records and count only the valid open amount. The corrected and reissued invoice workflow provides the lineage control. Do not count the original and replacement in separate weeks.
A useful next-action sequence is: confirm contractual payer, confirm required billing identity, decide the documented correction method, deliver the valid invoice, obtain acceptance, then update timing. A customer group's size or prior payment behavior is not a substitute for entity-specific evidence.
AR Pulse analyzes an authorized QuickBooks receivables export and can surface bill-to mismatches as ranked actions with explicit forecast treatment. It does not change invoices, contact customers, provide legal advice, or promise a payment outcome. Apply for AR Pulse when a focused source-to-action review fits the problem.