Promise-to-pay tracking
Promise-to-pay tracking that holds B2B customers to the date they gave you
Record what each customer committed to paying and by when, let CollectFlows watch the date, and get told when a promise breaks. Every commitment on your accounts receivable ledger becomes trackable data instead of a note in somebody's notebook.
14-day free trial · No credit card required
- Promises captured as data: customer, amount, date, and who took the call
- Broken promises flagged automatically when the date passes unpaid
- A kept-rate per customer, built from their own resolved promises
- Promise history visible on the customer timeline alongside every follow-up
- 30-day cash forecast weighted by each customer's track record (Enterprise)
The most valuable data in collections is the one nobody records
Everything else in the receivables process looks backwards. An aging report tells you how late an invoice already is. A statement of account tells you what was owed as of a date that has passed. Even a payment history only describes what a customer has already done.
A promise to pay is the one piece of forward-looking information in the whole process. When a customer says “we will pay AED 40,000 on the 25th”, that is a dated, specific, attributable claim about the future — and in most finance teams it is written on a notepad, mentioned in a stand-up, and gone by Thursday.
The cost is not just the forgotten follow-up. It is that the same customer can break four promises in a row and still be treated, on the fifth call, as though their word is good — because nobody has the record in front of them. Promise tracking is what turns a customer's reliability from an opinion into a number.
How promise tracking works here
From the call where the commitment is made to the forecast it feeds.
Record the commitment, not a note
A promise is captured as structured data — which customer, how much, by what date, logged by whom. Not a sentence in a comments column that no report can read.
The date is monitored for you
Open promises with their due dates surface on the dashboard, so the commitments landing this week are visible without anyone maintaining a diary of them.
Broken promises are flagged
When the promised date passes without the payment arriving, the promise is flagged as broken and surfaced to the collector and their manager — rather than quietly ageing into the next report.
A kept-rate per customer
Every resolved promise builds a record of whether that customer keeps their word. Over time you stop treating "we'll pay Thursday" from a reliable payer and a habitual one as the same information.
Cash forecast weighted by track record
On Enterprise, the 30-day forecast counts each open promise at that customer's own kept-rate instead of at face value — so the number reflects who made the promise, not just its size.
Evidence for the credit conversation
When a customer asks for better terms or a higher limit, their promise history is already on file: how many commitments they made, and how many they met.
What a promise is worth: the weighting rule
Once promises are recorded, an obvious temptation follows: add up everything customers have committed to this month and call it the forecast. That produces a number that is reliably too high, because it treats every promise as equally good.
CollectFlows weights each open promise by the kept-rate of the customer who made it, with a deliberately conservative fallback chain:
- Three or more resolved promises on file— the customer's own kept-rate is used. Two out of three kept means a promise counts at roughly two-thirds of its value.
- Fewer than three — their personal rate is a small sample and would swing wildly on one late payment, so the portfolio-wide kept-rate is used instead.
- No resolved promises anywhere yet — the amount is counted in full. Applying an invented discount with no evidence behind it would dress a guess up as a calculation.
The result is presented as a range rather than a single figure, and labelled as a model. The conservative end counts only money somebody has explicitly committed to, discounted by their record; the expected end adds a run-rate baseline for accounts that pay without ever making a promise. This sits in the Intelligence Board on Enterprise, alongside invoice aging and DSO reporting.
The operational side of this — what to capture on the call, how a promise resolves, and what a kept rate is worth once you have one — is covered in our guide to payment promise tracking, and the metrics it feeds in collection KPIs for finance managers.
Where promise tracking fits in the collections process
A promise is not a stage of its own — it is the outcome of a conversation and the trigger for the next one. In practice the loop runs like this: the aging report says who to chase, the collector chases and records what the customer committed to, the promise date is monitored, and the promise either resolves as kept or comes back as a broken commitment that needs escalating.
That loop is what collections management software exists to run, and promise tracking is the part that makes it measurable. Without it you can count activity — calls made, emails sent — but not whether the activity produced a commitment or whether the commitment produced cash.
The same record is also the honest input to a credit decision. A customer whose promises hold is a different credit risk from one whose promises do not, whatever their limit says, which is why the promise history shows up in credit control reviews as well as in collections.
Promise-to-pay tracking FAQ
- What is promise-to-pay tracking?
- A promise to pay, often shortened to PTP, is a customer's commitment to pay a specific amount by a specific date. Promise-to-pay tracking is the practice of recording that commitment as data — customer, amount, date, who took the call — and then monitoring whether it is met, rather than relying on the collector to remember. It matters because a promise is the only forward-looking information in the whole collections process: an invoice due date tells you when a customer was supposed to pay, and a promise tells you when they say they actually will.
- How does CollectFlows know a promise was broken?
- Each promise carries the date and amount the customer committed to. CollectFlows compares that against the invoice balances imported from your accounting system: if the promised date passes and the payment has not landed, the promise is resolved as broken and surfaced to the collector who took it and to their manager. A promise that is met resolves as kept. Both outcomes feed the customer's kept-rate, so the record builds itself as a by-product of the team doing its normal work.
- Why weight a cash forecast by the customer's own kept-rate?
- Because a promise from a customer who keeps four out of five and a promise from one who keeps one in five are not worth the same, and adding them together at face value produces a forecast that is confidently wrong. CollectFlows counts each open promise at the promising customer's own historical kept-rate, but only once there are at least three resolved promises to judge them on — below that, one customer's small sample is noise, so the portfolio-wide rate is used instead. With no evidence at all, the amount is counted in full rather than discounted by an invented percentage. The forecast is presented as a range and labelled as a model, because that is what it is.
- Is this the same as an automated payment reminder?
- No, and the difference is worth being clear about. A payment reminder is something you send; a promise to pay is something the customer gives you. Reminders go out on a schedule regardless of what anyone said, whereas a promise is specific, dated and attributable, and its value is in whether it was honoured. CollectFlows tracks the promises; automated email sequences and approval-based sending are a separate Enterprise capability, and on other plans the sending stays manual while the promise tracking and broken-promise alerting work on every plan.
- Can we see promise history per collector as well as per customer?
- Yes. Because every promise is logged against both the customer and the person who recorded it, the same data answers two different questions: whether a customer keeps their commitments, and whether a collector is getting commitments that hold. A collector logging a high volume of promises that mostly break is a coaching conversation, and it is visible without anyone auditing call notes by hand.
Related
Collections management software
The wider workflow: assignment, follow-up logging and escalation.
Credit control software
Credit limits, over-limit warnings and credit review evidence.
Accounts receivable software
The AR ledger itself — invoices, balances, aging and audit trail.
Pricing
Plans from AED 145/month, with a 14-day free trial.
Stop losing the promise between the call and the follow-up
Record commitments, catch the broken ones, and build a kept-rate you can act on — free for 14 days, no credit card.
14 days free · No credit card required · Cancel anytime