Broken Promise
A promise to pay that the customer failed to keep by the committed date, a key escalation trigger and risk signal in collections.
A broken promise is a promise to pay whose date has passed without the committed payment arriving. In a well-run collections operation it is a system event, not an anecdote: the promise record flips to broken, the covered invoices re-enter the work queue at elevated priority, and the account's next action escalates. Broken promises are tracked because they are doubly informative, about the account (its cash reality or good faith) and about the collector (whether promises are being taken firmly or accepted as brush-offs).
The correct response to a first broken promise is immediate, specific contact: the same day or next morning, referencing the exact commitment, asking what happened, and re-securing payment on a shorter leash, often a smaller amount, sooner, or an electronic payment scheduled on the call. What the response should not be is a silent restart of the dunning cycle, which converts the promise mechanism into a free delay tactic. Repeat breakage changes the account's character: two or more broken promises correlate strongly with eventual loss, and policy should hard-wire consequences, credit hold, security demands, final demand, or agency placement, rather than leaving each occurrence to collector discretion.
Kept-versus-broken promise analytics also calibrate the portfolio. Kept-promise rate by customer segments the past-due book into cash-timing accounts (high kept rates, reliable dates) and deteriorating accounts (falling kept rates), which is a sharper risk signal than aging alone because it measures forward-looking behavior, whether the customer does what it says, rather than the backward-looking fact of lateness.
Related terms
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.