A promise to pay should be recorded as dated evidence, not treated as certain cash. For a useful accounts receivable forecast, connect the commitment to specific open invoices, preserve the promised amount and date, record its current status, and schedule a review when the date passes. The forecast assumption can then reflect the strength and freshness of the evidence without turning a customer statement into certainty.
Oracle's receivables documentation treats a promise to pay as a record with a committed date, amount, related transactions, and status. That structure is useful even for a smaller QuickBooks-based finance team using a spreadsheet or weekly review rather than an enterprise collections system.
Fields to preserve
Keep the commitment record separate from the invoice source data. A practical tracker includes:
- Customer and invoice identifiers
- Open amount from the latest authorized export
- Promised amount and promised date
- Date the commitment was received
- Evidence source, such as an email or documented call note
- Status: pending, kept, broken, changed, or unverified
- Internal owner and next review date
- Forecast week and a short assumption rationale
Do not replace the contractual due date with the promised date. The due date remains a ledger fact; the promised date is later operational evidence. Keeping both prevents a revised expectation from rewriting history.
Translate status into a forecast review
**Pending:** The promised date is still ahead. The invoice may be assigned to the corresponding forecast week when the commitment is specific and current, but the assumption should remain reviewable.
**Kept:** A receipt has been observed and matched to the relevant invoice or commitment. Record the actual result rather than leaving the row as an expectation.
**Broken:** The promised date passed without the expected observed payment. Remove unsupported timing from the current forecast, record the variance, and assign the next internal action.
**Changed:** A new date or amount was supplied. Preserve the earlier commitment, add the revision, and explain why the forecast changed.
For a changed date, the revised promise-to-pay guide shows how to update the live forecast while keeping the prior snapshot and original commitment available for variance review.
**Unverified:** The source is ambiguous, the amount is unclear, or the commitment cannot be tied to an invoice. Keep the amount unassigned until the evidence is clarified.
The invoice collection assumptions template provides a broader framework for supported, tentative, and unconfirmed timing. The four-week forecast template shows where commitments, owners, and outcomes belong.
If the commitment covers less than the open balance, the partial-promise workflow separates the documented amount from the unpromised residual.
If one customer commitment covers several invoices, use the multiple-invoice promise allocation workflow so one promised amount cannot be copied into several forecast rows.
If the commitment has no specific date, the undated promise rule keeps it in the action queue without assigning an unsupported collection week.
Review commitments without false precision
At each weekly review, ask:
- Which promises fall inside the next four weeks?
- Which have enough evidence to support a weekly assumption?
- Which dates passed since the last review?
- Which revisions changed the amount or timing?
- Who owns the next evidence check for every broken or unclear promise?
A history of outcomes can improve the team's process, but it should not be turned into a universal payment probability without appropriate data and validation. The immediate goal is a transparent decision record.
AR Pulse uses supplied receivables evidence to produce a ranked cash-action list and four-week collections forecast. It does not contact customers or treat a promise as certain cash. View the one-page example to see how evidence and actions stay visible.