Skip to content

Promise to Pay

A customer's specific commitment to pay a stated amount by a stated date, recorded and tracked by the collections team.

A promise to pay (PTP) is the concrete outcome a collection contact should produce: the customer commits to pay a specific amount on a specific date by a specific method. It converts a vague "we'll take care of it" into a trackable object with a deadline. Collections systems treat PTPs as first-class records: the promise pauses further dunning on the covered invoices, schedules an automatic follow-up on the promise date, and marks the promise kept or broken when the date passes.

The quality of a promise depends on how it was taken. Strong practice pins down all four elements (amount, date, method, and which invoices), confirms the promisor actually has authority to release payment, and sends a same-day written confirmation summarizing the commitment, which both prevents misremembering and subtly raises the psychological cost of breaking it. Partial promises are fine and often realistic; open-ended ones ("sometime next month") should be pushed to a date or logged as a refusal to commit, which is itself information.

PTP metrics are among the most predictive signals in collections. The kept-promise rate by customer separates accounts with cash-timing problems (high kept rate, pay when they say) from accounts in real trouble or acting in bad faith (chronic broken promises). A broken promise should trigger immediate, firmer escalation rather than a polite restart of the cycle, because tolerating broken promises teaches customers that promises are a free way to buy thirty days of silence.

Worked example

A collector agrees a promise for $18,000 on the 15th, and $12,000 arrives. Whether that is kept or broken is worth deciding in advance: count every shortfall as broken and the signal disappears into noise; count it as kept and you stop noticing accounts that quietly pay less than they commit to. Most teams settle on a tolerance — kept within a defined percentage, broken outside it — and record which applied.

See SCREDIT on your own workflows.

A 30-minute walkthrough with the team that built it — using scenarios from your credit operation, not canned demo data.