When one customer promise covers several invoices, allocate the promised amount to named invoice rows only when the allocation is supported. Otherwise preserve one account-level promise, keep every invoice balance unchanged, and prevent the same amount from appearing in several expected-collection rows. The promise date is timing evidence, not observed cash, and any unpromised residual needs its own review.
Account-level evidence needs an invoice bridge
Oracle Receivables documentation describes promise-to-pay records with a promised amount and promise date and supports applying a request to multiple delinquent transactions. That workflow makes the account-level commitment visible, but an invoice-level cash forecast still needs a controlled allocation.
Without a bridge, a finance team can copy the full promise to each invoice or apply it automatically to the oldest balances. Either choice can overstate expected cash or hide the customer's actual intent. The correct population depends on the source: an email might name invoices, a remittance schedule might provide exact amounts, or the customer might promise only an account total.
Use the promise-to-pay tracking guide for the core evidence fields. If the promise covers only part of one balance, use the partial-promise workflow.
Allocate without duplicating the commitment
Create one promise record containing:
- customer, promise date, promised total, currency, and source;
- the invoice identifiers explicitly named by the customer;
- supported amount for each named invoice;
- residual promised amount not yet allocated;
- open balance not covered by the promise;
- owner, confirmation status, and next review trigger; and
- status after the promise date: fulfilled, partly fulfilled, broken, or unresolved.
The sum of invoice allocations should not exceed the account-level promised total. If the customer provides no allocation, keep the promise as a separate account-level evidence row and avoid assigning the same date to every invoice. A management view can still show the total commitment and the balances that might be affected.
When cash arrives, replace the promise with observed receipt evidence and use the supported remittance or application record to reduce invoice balances. The multiple-invoice payment guide covers that later cash-allocation step. If the promised date passes without supported payment, apply the broken-promise review once at the account record and update affected invoices deliberately.
Decision rule
One promise creates one expected amount. Allocate it to invoice rows only from documented evidence, preserve any residual separately, and do not let an account-level commitment multiply across the forecast. Keep timing confidence proportional to the quality and freshness of the promise.
AR Pulse analyzes an authorized QuickBooks receivables export and organizes invoice exceptions and four-week assumptions. It does not contact customers or perform collections. Finance teams can apply for AR Pulse.