Promise to Pay: How AR Teams Track Commitments and Follow Up When They Break

To track promises to pay in B2B collections, capture four details on every promise (amount, date, payment method and the person who made it), confirm them in writing the same day, log the promise where the whole AR team can see it, check for the payment on the next business day, and follow up within 24 hours when it does not arrive. A promise that nobody checks is just a delay with a date on it.

Short answer: a promise to pay only helps cash flow if someone verifies it. Write down the amount, date, method and payer, send a confirmation email, pause routine reminders on that invoice until the promised date, check the bank the next business day, and treat a second broken promise as a signal to escalate.

Promises matter because most overdue money is not in dispute. Atradius reports that 43% of credit-based B2B sales in the US were overdue in 2025, mainly because of customer cash flow pressure, and that bad debts hit 5% of long-overdue invoices. Customers under cash pressure rarely refuse to pay. They promise a date. PYMNTS Intelligence found that most businesses report up to 30% of their monthly invoiced sales are overdue, and that more than 75% of small to mid-sized businesses still chase collections by hand or over email. Put those together and a large share of what a collections team is owed sits behind a promise that lives in one collector's inbox or memory.

What Is a Promise to Pay in B2B Collections?

A promise to pay is a customer's commitment to pay a specific amount on a specific date, usually made in reply to a reminder or on a collections call. It is the most common outcome of a good collections conversation, and it is also the easiest one to lose.

What makes a promise usable

A usable promise has four parts:

• Amount: the exact dollar figure, and which invoices it covers.

• Date: a calendar date, not "end of the month" or "next week."

• Method: check, ACH, wire or card, because each one shows up in your bank on a different day.

• Payer: the name and role of the person who made the promise, and whether they can actually release the payment.

"We'll get it to you soon" is not a promise to pay. "Maria in accounts payable will send $14,200 by ACH on Thursday the 23rd for invoices 4471 and 4480" is. The gap between those two sentences is where most promises fail.

A promise is not a payment plan or a dispute

A promise to pay is a single commitment to clear a balance, or part of it, on one date. A payment plan is a series of promised amounts over time, agreed in advance, and each installment should be tracked as its own promise. A dispute is different again: the customer is not saying when they will pay, they are saying they do not agree they owe the amount yet. If a customer promises to pay "once you fix the invoice," you have a dispute, not a promise, and it needs a decision before a date means anything. For deductions taken at payment, see our guide to customer deductions and short payments.

Why Do Promises to Pay Get Lost on AR Teams?

Promises get lost for ordinary reasons, and almost none of them are about the customer.

The promise lives in one person's head

A collector takes a call, hears "we'll pay Friday," writes it on a sticky note or in a personal spreadsheet, and moves to the next account. If that collector is out on Monday, nobody checks whether Friday's payment came in. On a three to five person team, coverage gaps like this happen every week.

Nobody owns the day after

Most teams have a cadence for reminders before and after the due date (see what happens after the due date). Far fewer have a rule for the day after a promised date. The promise pauses the normal follow-up, and when the promise breaks, the account just sits there until the next aging review catches it, often weeks later.

Vague promises are never broken, only forgotten

"Early next month" cannot be missed, because there is no day to check. Vague promises feel like progress on the call and turn into silent aging afterward. If you cannot write the promise as a date and an amount, you do not have one yet.

Partial promises hide the rest of the balance

A customer promises to pay the oldest invoice and says nothing about the other three. The collector logs "promise received" on the account, and the remaining invoices quietly stop getting reminders. Every promise should name the invoices it covers, so the rest of the balance keeps moving.

How Do You Capture a Promise to Pay That Holds?

The best time to make a promise reliable is the moment it is made. A few habits on the call or in the reply turn a loose commitment into one you can verify.

Ask for the four details before you hang up

When a customer offers a date, ask the follow-up questions while you still have them:

• "Which invoices will that cover?"

• "Will that go out by check, ACH or wire?"

• "Are you the person who releases it, or does it need someone else's approval?"

• "If anything changes before then, who should I hear from?"

The approval question matters most. A promise from someone who cannot release funds is a forecast, not a commitment. When approval sits with a controller or owner, ask when that approval happens and log both dates.

Confirm the promise in writing the same day

Send a short confirmation within a few hours. It makes the promise visible to the customer's team and gives you a record if the date slips. For example:

"Hi Maria, thanks for your time today. To confirm: $14,200 by ACH on Thursday, October 23, covering invoices 4471 and 4480. Invoice 4502 ($3,850) is due on the 30th and is not part of this payment. Please let me know if anything changes before Thursday."

That one email does three jobs: it restates the commitment, it separates the invoices that are not covered, and it invites the customer to warn you early instead of going quiet.

Log it where the whole team can see it

Every promise belongs in one shared place, whether that is a field in your accounting system, your collections tool or a team spreadsheet. The log needs the four details, the date the promise was made, the person who logged it and the status. If a promise only exists in a collector's email, it does not exist for the rest of the team.

What Should Happen When a Promised Date Arrives?

The day after a promised date is where most of the cash is won or lost. A clear rule removes the guesswork.

Check for the payment on the next business day

On the business day after the promised date, check whether the money arrived. Allow for the method: an ACH or wire should be visible within a day or two, a mailed check can take several days, so ask for the check number when the promise is made. If the payment is in, mark the promise kept and confirm receipt to the customer. If it is not, the promise is broken, and the follow-up starts that day.

Follow up on a broken promise within 24 hours

The first follow-up after a missed date should be prompt, polite and specific. Do not lead with blame; lead with the facts and ask for a new date:

"Hi Maria, we had the $14,200 ACH for invoices 4471 and 4480 planned for yesterday and have not seen it come through. Can you check on it and let me know the new date it will go out?"

Most broken promises have a mundane cause: the payment run slipped, the approver was out, or the payment went out under a different reference. A quick message usually gets a new date or a remittance detail. Our guide to handling delayed payments from customers covers what to say when the reason is cash flow.

Escalate after the second broken promise

One broken promise is common. Two on the same invoices is a pattern. After a second miss, move the account up: involve the account owner or a senior person on the AR team, ask to speak with whoever releases payment, and consider whether new orders or credit terms should be reviewed. Our guide on when to escalate an invoice lays out the next steps and when to stop chasing.

Promise statuses and next actions

How Do You Measure Promise-to-Pay Performance?

Promises are measurable, and measuring them tells you a lot about both your customers and your process. These fit alongside the accounts receivable KPIs worth tracking.

Promise kept rate

The share of promises that were paid in full by the promised date. Track it by collector and by customer. A low rate for one customer is a credit signal; a low rate across the whole team usually means promises are being accepted without the four details.

Promised dollars versus collected dollars

Each week, total the dollars promised for that week and the dollars that actually arrived against those promises. The gap is your most honest short-term cash forecast. Controllers who build the weekly cash view from verified promises rather than from the aging report get fewer surprises.

Broken promises by customer

Keep a running count of broken promises per customer over the last 90 days. Customers with two or more should get closer attention on new orders and credit limits. Credit Pulse flags more than 20% of AR past 60 days as a warning sign, and repeat broken promises are usually how an account gets there.

How Should a 3 to 5 Person AR Team Run Promises to Pay?

On a small team, the process matters more than any single collector's skill, because promises have to survive vacations, sick days and busy month-ends.

Give every open promise one owner

The collector who takes the promise owns it until it is kept, broken or escalated. If that person is out, the AR manager reassigns their promises that fall due during the absence, before the absence starts.

Review open promises every week

Spend fifteen minutes in the weekly team meeting on promises due in the next seven days and promises broken in the last seven. That one review catches most of what slips through. It also keeps the team honest about vague promises that were logged as real ones.

Broken promises move up the worklist

A broken promise is one of the clearest signals in collections: the customer has acknowledged the debt, named a date and missed it. Put those accounts near the top of the next day's list, ahead of routine reminders on invoices that are only a few days late.

Keep the rest of the account moving

A promise on one invoice should never pause the whole account. Confirm in writing which invoices the promise covers and keep the others on their normal past-due email sequence. This is one of the simplest ways to lower DSO without hiring, because it stops promises from quietly freezing balances they were never meant to cover.

How Does Abivo Help AR Teams Track Promises to Pay?

Abivo keeps the follow-up around every promise running so your team does not have to remember it. Kate, Abivo's AI collections agent, calls, texts and emails customers about overdue invoices from your accounting system or ERP, logs what each customer commits to, and follows up when a promised payment does not arrive.

That fits the workflow above:

• Promises are logged with the customer's own words, including the amount, the date and the invoices covered, so nothing lives in one person's inbox.

• Covered invoices pause while the rest of the account keeps moving, so a partial promise does not freeze the whole balance.

• Missed dates get a follow-up, so a broken promise is acted on the next business day instead of at the next aging review.

• Disputes and repeat broken promises are handed to a person on your team, so judgment calls and key accounts stay with the people who own them.

To see how this works for a team in the field, read the OFS Group case study. If you are comparing tools for a team your size, see our roundup of collections software for AR teams with 3 or more collectors. And for what to say when the promise comes wrapped in an excuse, see the top excuses for late payments and how to handle each one.

Practical Takeaways for AR Managers

• Accept a promise only when it has an amount, a date, a payment method and a named payer.

• Confirm every promise in writing the same day, listing the invoices it covers and the ones it does not.

• Log promises in one shared place, not in collectors' inboxes.

• Check for the payment on the next business day and follow up within 24 hours if it is missing.

• Escalate after the second broken promise on the same invoices.

• Track promise kept rate and promised versus collected dollars every week.

Related guides for AR teams: how to structure a collections team of 3 to 5 people, how to prioritize collections accounts each week and how to resolve invoice disputes.

FAQ

What is a promise to pay in collections?

A promise to pay is a customer's commitment to pay a specific amount on a specific date, usually made in reply to a reminder or during a collections call. A usable promise names the amount, the date, the payment method and the person releasing the payment.

What should you do when a customer breaks a promise to pay?

Follow up within 24 hours with the facts: the amount and date that were promised and that the payment has not arrived. Ask for the reason and a new date. If the same invoices see a second broken promise, escalate to a senior team member or the account owner.

Should you stop sending reminders after a promise to pay?

Pause routine reminders only on the invoices the promise covers, and only until the promised date. Keep every other open invoice on the account on its normal schedule, and confirm in writing which invoices are covered.

How do you measure promise-to-pay performance?

Track the promise kept rate (promises paid in full by the promised date), the gap between promised and collected dollars each week, and the number of broken promises per customer over the last 90 days.

Can an AI collections agent track promises to pay?

Yes. An AI collections agent like Abivo's Kate logs each promise with the amount, date and invoices covered, follows up when a promised payment does not arrive, and hands disputes and repeat broken promises to the right person on your team.

Want every promise your customers make to be checked the day it is due? Get Started with Abivo.