“We will send payment next week” sounds encouraging, but it leaves several unanswered questions. How much will be paid? Which invoices are included? What does next week mean? Who should the collector contact if the payment does not arrive?
Promise-to-pay tracking turns a conversation into a specific commitment that can be monitored. For B2B collections teams, the discipline is straightforward: record the agreement accurately, verify the outcome, and take the next action consistently.
Capture the details that make a promise useful
Record the promised amount, currency, expected payment date, invoices covered, and the person making the commitment. Where relevant, note the payment method and expected receipt timing.
A promise should also identify its owner within your team. The customer may be speaking to one collector today and another next week. A clear record prevents the second employee from having to reconstruct the agreement from a vague note.
Do not record an uncertain statement as a firm commitment. “I will ask our controller” is an action to follow up, not a promise that funds will arrive.
Keep partial payments and disputes separate
A customer might commit to paying the undisputed invoices while a pricing issue is investigated. Record the amount and invoice allocation of that promise, then assign the dispute to the appropriate internal owner.
If a partial payment is agreed, state what remains open and whether any further arrangement has been authorized. Collectors should not imply revised contractual terms or concessions outside their authority.
When a promise changes, preserve the earlier commitment and the reason for revision. Replacing the date repeatedly can make an account appear current in the promise log while the invoice grows older.
A hypothetical account timeline
| Date | Event | Recorded action |
|---|---|---|
| March 2 | Customer promises $15,000 by March 9 against three invoices | Record invoices, contact, amount, and follow-up owner |
| March 9 | Receipt has not yet been identified | Check payment method and expected receipt timing |
| March 10 | $10,000 is located in unapplied cash | Reconcile the receipt and confirm allocation |
| March 10 | $5,000 remains outstanding | Contact the customer about the shortfall and next action |
| March 12 | Authorized revised commitment is recorded | Retain the original history and schedule review |
This fictional example shows why a promise should not be judged solely by a bank feed or a collector’s first glance at the ledger. Receipt verification and allocation are part of the process.
Define fulfillment before measuring it
A count-based kept-promise rate can be calculated as promises fulfilled by the agreed date divided by promises due during the measurement period, multiplied by 100. Define whether fulfillment requires the entire amount and how receipt timing is treated.
An amount-based measure can show the promised value received on time divided by the promised value due in the period. Keep its definition distinct from the count-based measure.
Neither metric should hide partial performance. A team can meet many small commitments while missing one large payment. Show the largest outstanding promises alongside aggregate percentages.
Avoid incentives that distort the record
If employees are evaluated only on their kept-promise percentage, they may hesitate to record difficult commitments or may revise dates too freely. Use the measures to understand follow-through and account behavior, not as a substitute for judgment.
Compare like portfolios. A collector managing distressed accounts or disputed balances faces different conditions from one handling routine reminders.
Review repeated revisions, unusually long promise periods, and promises that remain unresolved after receipts are posted. These patterns may reveal a workflow or data issue rather than a customer issue.
Make missed promises lead to a defined response
After checking receipts and credits, contact the customer with the facts. Ask whether payment was sent and request remittance information if needed. If the plan changed, establish the reason and an authorized next step.
Repeated missed commitments may justify credit manager review. Provide the overdue exposure, contact history, and current purchasing activity so management can consider the wider relationship.
- Record a specific amount and date.
- Identify invoices and the responsible contact.
- Assign an internal follow-up owner.
- Reconcile receipts before classifying the outcome.
- Preserve revisions and escalate repeated failures.
CMS Credit Suite supports recording collection outcomes, payment promises, follow-up dates, and dashboard reminders.
Contact Credit & Management Systems, Inc. to discuss making payment commitments part of a consistent B2B collection workflow.