- Record every promise with four parts: who committed, how much, by when, and for which invoice or installment.
- Define "broken" as a rule: the promised date plus a set grace period, checked against receipts.
- The reason for the miss (process gap, cash shortfall, dispute, already paid, silence) decides the next step and its owner.
- Write escalation triggers into policy, such as a second broken promise on the same plan.
- On a payment plan, track each installment as its own promise and watch the kept rate.
A broken promise to pay is a payment commitment, whether a date, an amount or an installment on a payment plan, that passes without the money arriving. What you do in the next 72 hours usually decides whether it stays a one-off slip or becomes a pattern. This playbook covers how to confirm the miss, reach out, find the reason, get a new commitment or plan, and set the trigger for escalation. It also covers how to track every installment so the next miss is noticed the day it happens.
Misses rarely announce themselves. A customer we worked with, a contingency-fee employment law firm, collects many of its settlements in monthly installments over a year. Its accounting software holds each settlement as one invoice, and the installment dates live in a spreadsheet. Follow-up runs on phone calls, and whenever a big project pulls the team away, the calls stop and receivables climb in waves. In a month like that, an installment can slip past without anyone seeing it: the single invoice already looks overdue in the system, so nothing new turns red. By the time someone opens the spreadsheet, the next installment may be late too. And the firm doesn't want to fix it by hiring. It would rather manage one more vendor than five more people.
If you collect from the other side of a case, our guide to law firm collections covers the wider process. This article is about the moment a promise is missed.
What Counts as a Broken Promise to Pay
A promise to pay has four parts: who committed, how much, by when, and for which invoice or installment. Record all four when the promise is made, along with the channel and the person on your side who owns the follow-up. "They said they'd pay soon" can't be broken, because it was never a promise.
"Broken" should be a rule, not a feeling: the promised date plus a short grace period has passed, and no payment has arrived. Confirm that against bank and receipt records, not against a customer's word that it's been sent. Many collections systems let you set grace days. Whatever number you choose, apply it the same way every time.
A promise doesn't change the invoice. The due date and status stay as they are; the promise only pauses the reminders that would contradict it, until the promised date. Your regular automated payment reminders handle the sequence around the due date. This playbook starts when a specific commitment is missed.
The First 72 Hours After a Missed Payment
Seventy-two hours is a working rhythm, not a research benchmark. The point is that each step has a deadline, so the miss doesn't wait for someone's next free afternoon.
Hours 0–24: Confirm It's Really Missed, Then Reach Out the Same Day
Before contacting anyone, make sure the money really isn't there. Look for unapplied cash, payments posted to the wrong invoice or customer, and payments in transit. Chasing someone who has already paid costs goodwill, especially with a counterparty you'll deal with again. (Our guide to cash application automation covers how payments get matched.)
If the payment is missing, make contact the same day, on the channel that worked when the promise was made. Be specific: the amount, the date they committed to, and which installment it was. Our collections call script and past-due invoice email guides give you wording for each channel.
Hours 24–48: Find Out Why
The reason decides the next step.
| Reason | What you'll hear | Next step | Owner |
|---|---|---|---|
| Forgot, or a process gap | "It never reached me" / "We didn't get the invoice" | Resend to the right person; confirm who receives it | Collector |
| Cash shortfall | "We can't make it this month" | Re-plan: new amount or date, recorded as a new version | Collector, with approval for changed terms |
| Dispute | "We don't think we owe that" | Move it to your dispute process | AR lead |
| Already paid | "We sent it Tuesday" | Get payment details; trace and apply | Cash application |
| No response | Silence | Set the escalation date now | Collector |
Don't record an internal blocker as a customer refusal. If the invoice went to the wrong person or the payment is sitting unapplied, that's yours to fix. For the dispute row, see invoice dispute management.
Hours 48–72: Re-Commit, Re-Plan, or Set the Trigger
By the end of day three, every missed promise should have one of three outcomes:
- Re-commit. A new, specific date, confirmed in writing. Log it as a new promise linked to the broken one and keep the history; a second miss on the same plan is an escalation trigger.
- Re-plan. If the original plan was unrealistic, change the amounts or dates and record why. A plan the customer can keep is worth more than one they'll break again.
- Set the trigger. If there's still no answer, write down the date the account escalates and who will act on it. "Follow up next week" is not a trigger.
When to Escalate (and What the Trigger Should Be)
Escalation works best when the triggers are written into your policy before you need them, so nobody has to decide case by case under pressure. Common triggers:
- A second broken promise on the same plan
- No response after a set number of attempts or days
- Missed installments reaching what the agreement treats as a default
- The customer denying that the money is owed
For a settlement payment plan, check with counsel what the agreement says about a missed payment, and whether those terms fit, before you escalate.
From there, escalation moves up a ladder: a more senior contact on their side, then a message signed by an attorney or executive (at some law firms, drafted by the finance team for the attorney's signature), then a formal letter. When it reaches that point, our guide to the demand letter covers what to include, and law firm collections lays out the full escalation ladder for firms collecting settlements.
Promise to Pay Tracking: Treat Every Installment as Its Own Promise
On a payment plan, each installment is a promise, with its own amount, due date, reminder and on-date check. Tracking the plan as one balance hides the misses. That's exactly what happens when a settlement is booked as one invoice: the invoice ages from the first due date, so a missed installment changes almost nothing in the aging. To make the ledger show each installment, see how to reconcile installment balances that don't match.
Promise to pay tracking needs only a few fields:
- Promise or installment ID, linked to the invoice or agreement
- Amount and promised date
- The contact who committed, and the channel
- The owner on your side
- Status: open, kept, broken or re-committed
- History of earlier promises on the same account
The number worth watching is the kept rate: promises kept on time divided by promises due, by customer or counterparty. A falling kept rate is an early warning, well before the balance looks bad. There's no universal benchmark, so compare each account with its own history.
Keep the Rhythm Without Adding People
Follow-up usually doesn't stop because a team stops caring. It stops because it depends on people remembering, and in a busy month they don't. The firm above was in exactly that spot: receivables weren't out of control, there just weren't enough hands, and more headcount wasn't the answer it wanted.
Split the work by what each side does best. Let rules and systems handle the dates: reminders before each installment, the on-date check against receipts, the broken-promise flag and the escalation date. Keep people on the conversations and the judgment calls, especially with counterparties you'll deal with again and again, where tone matters as much as timing. For the cost side of that choice, see AR automation vs. hiring; for why calls are the first thing to go when a team is stretched, see why the most effective collections channel gets skipped first.
Promise reminders and installment tracking in Daylit are coming soon.
The Short Version
A broken promise to pay is a signal, not yet a write-off. Confirm the money really isn't there, reach out the same day, find the reason, and end day three with a new commitment, a new plan or an escalation date. Then track every installment as its own promise, so the next miss is seen the day it happens rather than at month-end.
How many days late before a promise counts as broken?
There's no standard number. Set a grace period in your collections policy, long enough to allow for payments in transit, and apply it consistently.
Should I accept a new promise after a broken one?
Usually once, with a specific date and written confirmation. A second miss on the same plan should hit your escalation trigger rather than produce a third promise.



