No—a promise to pay without a specific date does not support a specific collection week. Preserve it as customer-intent evidence and an owned follow-up item, but leave timing unassigned until finance has a dated commitment or another source supports a bounded collection range. An undated promise is stronger than silence and weaker than a schedulable cash assumption.

Oracle documents promise-to-pay records with a status, amount, and promise date. SAP's collections workflow also records promised amount and date and tracks whether the commitment is kept or broken. Both make the date part of the operational record rather than an optional forecasting detail.

Record what is known

For an undated commitment, preserve:

  • customer and invoice references;
  • current open balance;
  • amount the customer discussed, if explicit;
  • the exact source and date of the note;
  • who recorded it;
  • missing date flag;
  • internal owner and next action; and
  • next review date.

Do not convert phrases such as “soon,” “next run,” or “when approved” into a calendar date. Those phrases may identify a blocker or follow-up path, but they do not define Week 1 through Week 4.

Use an evidence ladder

Classify the timing evidence without inventing precision:

  1. **No timing evidence:** Keep the amount out of dated collection buckets.
  2. **Undated promise:** Preserve the commitment and request a date internally; timing remains unassigned.
  3. **Bounded window:** Use an earliest and latest supported date when the source provides a real range.
  4. **Specific dated promise:** Place the supported amount in the matching week while retaining invalidating events.
  5. **Observed receipt:** Move the amount out of expected collections and into actual cash only when the source confirms receipt.

The promise-to-pay tracking guide covers the full record. If the promise covers less than the invoice balance, use the partial-promise workflow so the residual stays visible.

Keep the action queue broader than the forecast

An undated promise still belongs in the weekly AR action queue. The owner can validate the amount, request a date through the company's authorized process, check whether a dispute or approval is blocking payment, and set the next review date. The four-week forecast should remain narrower: only supported timing belongs in a week.

If a later promise falls beyond the current horizon, the outside-horizon guide shows how to preserve it without pulling it into near-term cash. If the source only supports a range, use the date-range framework.

Decision rule

Treat an undated promise as a reason to follow up, not a reason to assign a date. The invoice remains open, the amount remains traceable, and the collection week remains unassigned until evidence improves.

AR Pulse analyzes an authorized QuickBooks receivables export and turns invoice evidence into a ranked action list and four-week collections range. It does not contact customers or promise payment outcomes. Continue with the promise-to-pay tracking workflow.