Promise to Pay: How to Capture, Track, and Actually Collect on Payment Commitments

Ask most AR teams how collections went last week and you will hear about activity: calls made, emails sent, accounts touched. Ask what customers actually committed to, and the answer gets vague.

That gap matters because activity does not forecast cash. Commitments do. A collector who made forty calls and secured three firm commitments had a worse week than one who made twelve calls and secured nine — but most collections reporting cannot tell the difference.

The promise to pay is the artifact that closes this gap. It converts a conversation into something specific, trackable, and forecastable. This guide covers what makes a PTP valid, why so many are broken, how to measure kept rate, and how to handle commitments that fail.

Why the Promise to Pay Is the Real Output of Collections

A collections interaction can end in one of four states:

1. Payment made immediately — ideal, but uncommon in B2B where AP runs on payment cycles
2. A specific commitment — a named person agrees to pay a defined amount on a defined date
3. A blocker surfaced — a dispute, a missing invoice, or an approval problem now visible and actionable
4. Nothing — no contact, no commitment, no information

Only states 2 and 3 have value, and only state 2 produces forecastable cash. The purpose of a collections call is not to apply pressure; it is to reach one of these two outcomes.

This reframing changes how teams work. A collector optimising for call volume will accept “I’ll look into it” and move on, because the call is complete. A collector optimising for commitments will stay on the line until they have a date, an amount, and a name — or until they have surfaced the specific blocker preventing one.

What Makes a Promise to Pay Valid

A PTP worth recording has four attributes:

A named person with authority. “Accounts payable said it would go out” is not a commitment. A person who can actually release payment, identified by name and role, is. Commitments from people without payment authority are the most common source of broken PTPs, and the failure is usually invisible until the date passes.

A specific amount. “The outstanding balance” is ambiguous when there are fourteen open invoices and two under dispute. The amount should be stated, and where it differs from the full balance, the reason for the difference should be captured.

A specific date. Not “next week” or “end of month” — an actual date. Vague timing makes the commitment unmeasurable and gives both parties room to disagree later about whether it was kept.

The invoices covered. Which specific invoices this payment settles. Without this, cash application cannot match cleanly against the commitment when the payment arrives.

A commitment missing any of these is not a PTP. Recording it as one inflates your pipeline and destroys the credibility of your kept rate — which is the most common reason teams find their PTP data useless.

Why Promises Get Broken

Broken PTPs are usually a process failure rather than bad faith.

The commitment was never real. The customer said something agreeable to end an uncomfortable conversation. This is the most common cause, and the fix is at capture: pressing for a specific date and amount surfaces a soft commitment immediately, because a customer who cannot commit will say so when asked for specifics.

The person had no authority. Common where collectors reach a general AP inbox or a junior team member rather than the approver.

A blocker existed that neither party knew about. The invoice was never received, is missing a PO reference, sits unapproved, or is partially disputed. The customer intended to pay and then discovered they could not. This is why the first question in any collections conversation should confirm the invoice is received, approved, and scheduled — not request payment.

The payment run does not align with the promised date. The customer commits to the 20th; their AP cycle runs on the 25th and the 10th. The commitment was sincere and structurally impossible. Asking when the next payment run falls converts this into an accurate date.

Nobody followed up before the date. A promise made three weeks ago with no intervening contact is far less likely to be honoured than one confirmed 48 hours in advance.

Nothing happened when it was broken. If a missed commitment produces no consequence, customers learn that commitments are optional. This is the same escalation-credibility problem that undermines weak dunning sequences.

Measuring PTP Kept Rate

PTP Kept Rate = (PTPs honoured in full and on time / Total PTPs made) x 100

Kept rate is the clearest measure of collections quality available, because it is unaffected by sales volume and reflects whether outreach produces real commitments.

Benchmarks. Well-run B2B teams achieve 70–85%. Below 50% almost always indicates a capture problem — vague commitments recorded as firm ones — rather than uncooperative customers.

Three refinements make the metric considerably more useful:

Track partial keeps separately. A customer who commits $100,000 and pays $60,000 on time is not the same as one who pays nothing. Measuring value kept alongside count kept gives a truer picture.

Segment by cause of failure. Reason-code broken promises: no authority, blocker discovered, payment run mismatch, deliberate delay. The distribution tells you what to fix. A cluster of “blocker discovered” means your pre-due process is not surfacing problems early enough.

Segment by collector and by channel. Kept rate varies significantly between collectors and between email, phone, and portal commitments. Phone-captured commitments are typically kept at materially higher rates than email ones, because the conversation forces specificity.

Kept rate should sit alongside DSO and Collection Effectiveness Index in collections reporting — see the AR aging and metrics guide for how these fit together.

Handling a Broken Promise

A broken PTP should trigger a defined response, not a return to the general reminder queue.

Contact within 24–48 hours. Immediacy signals that commitments are tracked. A broken promise followed by silence for two weeks teaches the opposite.

Establish the cause before applying pressure. If a blocker emerged, the correct response is resolution, not escalation. If the payment run did not align, the fix is a better date.

Escalate the person, not just the tone. A second commitment from the same contact who broke the first is worth little. Move up — to their manager, to the account owner, or to a finance-to-finance conversation.

Apply a real consequence after repeated failures. Two or three broken commitments should trigger a credit review or hold, not a fourth reminder. Repeatedly broken promises are one of the strongest early indicators of genuine credit deterioration and frequently precede default.

Feed the pattern into risk scoring. PTP reliability is behavioural credit data that most businesses already generate and then discard. A customer whose kept rate has fallen from 90% to 40% over two quarters is signalling distress well before any bureau updates their score.

Automating Promise-to-Pay Management

PTP management fails at scale for a mundane reason: it depends on individuals remembering to log commitments and follow up on dates.

Automatic capture. AI voice agents conducting outbound collection calls capture commitments in the conversation — amount, date, invoices, and contact — and write them back against the invoice immediately, with no reliance on anyone logging notes afterwards.

Confirmation in writing. An automatic email confirming the commitment creates a record both parties have seen and materially increases kept rate.

Scheduled pre-date reminders. A confirmation 48 hours before the promised date is one of the highest-return automations in collections, because it catches the commitments that were sincere but forgotten.

Automatic verification. On the promised date, the system checks whether payment was received and applied. This only works when cash application is current — otherwise commitments are marked broken when the money has already arrived, which is worse than not tracking at all.

Broken-promise workflows. Automatic escalation, reason-coding, and ownership assignment through finance CRM task management.

Forecast integration. Aggregated open PTPs weighted by historical kept rate produce a near-term cash forecast grounded in actual customer commitments rather than payment-term assumptions.

How to Build a Promise-to-Pay Process

Step 1: Define what counts as a valid commitment. Name, amount, date, invoices — or it is not a PTP.

Step 2: Confirm the invoice is clear before requesting a date. Surface blockers before commitments.

Step 3: Align the date to the customer’s payment run. Removes an entire class of sincere failures.

Step 4: Confirm in writing and remind before the date. The highest-return automation available.

Step 5: Track kept rate and reason-code failures. The distribution tells you what to fix.

Step 6: Escalate broken promises into credit review. Declining reliability predicts default.

Our Verdict: Measure Commitments, Not Activity

The reason most collections reporting cannot distinguish a productive week from a busy one is that it counts contacts rather than commitments. Calls made and emails sent are inputs. A promise to pay with a named person, a specific amount, a specific date and identified invoices is an output, and it is the only collections artifact that reliably forecasts near-term cash.

The verdict that follows is uncomfortable for teams with weak kept rates: a PTP kept rate below 50% is almost always a capture problem rather than a customer problem. It means vague assurances are being recorded as firm commitments. Pressing for a specific date and amount surfaces a soft commitment immediately, because a customer who cannot commit will say so when asked for specifics — and a stated blocker is more valuable than an agreeable non-answer.

Two refinements deliver most of the remaining value. Align the promised date to the customer’s actual payment run, which eliminates an entire class of sincere but structurally impossible commitments. And treat declining PTP reliability as credit data: a customer whose kept rate has fallen from 90% to 40% across two quarters is signalling distress well before any bureau updates their score. Collections practice guidance from the Chartered Institute of Credit Management and the National Association of Credit Management both treat commitment tracking as a core discipline, and Credit Research Foundation benchmarking is a reasonable external reference for kept-rate expectations. Credit control guidance from ACCA reaches a consistent conclusion — that forecastable collections performance depends on disciplined commitment capture rather than contact volume.

Conclusion

The difference between a collections team that reports activity and one that forecasts cash is whether conversations end in specific, tracked commitments. Capturing promises properly, confirming them, verifying them, and escalating failures turns collections from an effort metric into a predictive one — and makes declining PTP reliability visible as the credit warning it actually is.

Request a demo to see how Peakflo’s AI voice agents capture and track payment commitments automatically across accounts receivable.

Frequently Asked Questions

What is a promise to pay?

A promise to pay (PTP) is a commitment from a customer to pay a specific amount by a specific date. In B2B collections it is the primary output of a collections conversation and the basis for short-term cash forecasting, because it reflects an actual customer commitment rather than an assumption based on payment terms.

What makes a promise to pay valid?

A valid PTP has four attributes: a named person with authority to release payment, a specific amount, a specific calendar date, and identification of the invoices it covers. A commitment missing any of these — such as “we’ll process it soon” — should not be recorded, since doing so inflates the pipeline and corrupts kept-rate measurement.

What is a good PTP kept rate?

Well-run B2B collections teams typically achieve 70–85% of commitments honoured in full and on time. A kept rate below 50% usually indicates that vague assurances are being recorded as firm commitments, rather than that customers are uncooperative — making it a capture problem rather than a customer problem.

Why do customers break promises to pay?

The most common causes are that the commitment was never firm, the person lacked payment authority, a blocker such as a missing PO reference or unapproved invoice emerged afterwards, the promised date did not align with the customer’s payment run, or no one followed up before the date arrived.

What should you do when a promise to pay is broken?

Make contact within 24 to 48 hours, establish the cause before applying pressure, and escalate to a more senior contact rather than accepting a second promise from the same person. After repeated failures, trigger a credit review or hold instead of sending another reminder.

How is promise to pay different from a payment plan?

A promise to pay is a single commitment to pay a specific amount on a specific date. A payment plan is a negotiated schedule of multiple instalments over time, usually agreed where a customer cannot settle the full balance at once. A payment plan is effectively a series of linked promises to pay.

Can promise-to-pay tracking be automated?

Yes. AI voice agents capture commitments during outbound collection calls and write them back against the invoice automatically, written confirmations are issued without manual effort, reminders fire before the promised date, and payment is verified on the date so broken commitments escalate automatically with reason codes.

What should you record when a customer makes a promise to pay?

Record the named person and their authority to release payment, the specific amount committed, the specific calendar date, the invoices the payment will settle, and the channel the commitment was made on. Omitting any of the first four makes the commitment unmeasurable and corrupts kept-rate reporting.

How far in advance should you confirm a promise to pay?

Send a written confirmation immediately after the commitment is made, then a reminder roughly 48 hours before the promised date. Pre-date confirmation is among the highest-return automations in collections because it recovers commitments that were entirely sincere but simply forgotten in the customer’s payment cycle.

Are phone-captured promises to pay more reliable than email ones?

Generally yes. Phone conversations force specificity — a collector can press for a date, an amount and confirmation of authority in real time — whereas email commitments are frequently vague and made by someone without payment authority. Segmenting kept rate by channel usually shows a material difference.