AR software tracks payment promises after an e-invoice is sent by automatically logging any commitment a customer makes to pay by a specific date, then monitoring that date and triggering follow-up actions if payment does not arrive. This removes the need for a finance team member to manually track every verbal or written commitment across scattered spreadsheets or email threads.
For growing businesses sending dozens or hundreds of invoices each month, that kind of automated oversight is the difference between cash arriving on time and invoices quietly slipping past their due dates. The sections below walk through exactly how this works, from what counts as a promise to how reporting helps you spot patterns over time.
What counts as a payment promise in accounts receivable?
A payment promise in accounts receivable is any commitment from a customer to pay an outstanding invoice by a specific date. It differs from a standard payment due date because it reflects a direct agreement made after the invoice was issued, often following a reminder or a conversation about an overdue balance.
Payment promises typically arise in a few common situations. A customer might reply to an email reminder saying they will transfer funds by the end of the week. They might call your finance team and agree to pay in instalments. Or they might respond to a WhatsApp message with a specific date. All of these are promises, and all of them need to be tracked.
What makes promise tracking different from basic invoice tracking is the layer of accountability it adds. A standard due date is set when the invoice is raised. A payment promise is a secondary commitment, one that often carries more weight because the customer has actively confirmed it. When that promise is broken, it signals something worth acting on quickly.
Ready to maximize your cashflow?
Automate your accounts receivable, reduce payment delays and get paid faster.
How does AR software capture and log payment promises automatically?
AR software captures payment promises by integrating with the communication channels your team uses to follow up, including email, WhatsApp, and SMS, and logging any agreed payment date directly against the relevant invoice record. Some platforms allow team members to manually record a promise after a phone call, while others can detect promise-related language in written replies.
The key benefit is centralisation. Instead of one person keeping notes in a spreadsheet and another tracking replies in their inbox, every promise lives in one place alongside the invoice, the customer’s contact history, and their payment behaviour. Anyone on the finance team can see the current status at a glance without chasing internal updates.
When a promise is logged, the software typically pauses or adjusts the standard dunning sequence for that invoice. There is no point sending an automated overdue reminder to a customer who has already confirmed they will pay on Friday. The system holds the workflow and waits, only resuming if the promised date passes without payment.
What happens when a customer misses a promised payment date?
When a customer misses a promised payment date, AR software automatically detects the broken promise and triggers a targeted follow-up. Rather than treating the invoice as simply overdue, the system flags it as a missed commitment, which typically warrants a more direct response than a standard first reminder.
This distinction matters in practice. A customer who has never been chased before responds differently to a gentle nudge. A customer who agreed to pay three days ago and did not follow through needs a firmer message that references the specific promise they made. Good AR software makes it easy to send exactly that kind of personalised, context-aware communication automatically.
Depending on how your workflows are configured, a missed promise might escalate the invoice to a senior team member, trigger a different message template, or move the account into a higher-priority queue for manual review. The goal is to respond faster and more appropriately than a generic reminder sequence would allow.
How does payment promise tracking connect to dunning workflows?
Payment promise tracking connects to dunning workflows by acting as a conditional gate. When a promise is recorded, the dunning sequence pauses. When the promise is kept, the invoice is marked paid and the workflow closes. When the promise is broken, the workflow resumes or escalates, often skipping earlier steps because the customer has already had direct contact.
This integration makes dunning smarter and more human. A rigid dunning sequence sends the same messages on the same schedule regardless of context. A promise-aware workflow adapts based on what has actually happened in the relationship with that customer.
For finance teams managing hundreds of invoices, this matters enormously. Without promise tracking, a customer who agreed to pay last Tuesday might receive a generic first reminder on Wednesday, which feels tone-deaf and can damage the relationship. With it, the system knows the context and responds accordingly, keeping communication relevant and professional at every stage.
Which integrations make promise tracking more accurate?
Promise tracking becomes significantly more accurate when AR software integrates with your accounting or ERP system, your communication channels, and creditworthiness monitoring tools. These connections ensure that payment data, customer conversations, and risk signals all flow into a single, up-to-date picture for each invoice.
The most important integration is with your accounting package. When a payment arrives, the AR software needs to know immediately so it can close the promise and stop any follow-up. Without a live connection to systems like Exact, Twinfield, AFAS, SAP, or NetSuite, there is always a lag, and that lag can result in chasing a customer who has already paid.
Communication channel integrations, covering email, WhatsApp, and SMS, ensure that replies and confirmations are captured in context rather than sitting in someone’s personal inbox. And integrations with credit monitoring tools, such as Dun and Bradstreet, add another layer by flagging customers whose creditworthiness has changed, which can inform how urgently a broken promise needs to be escalated.
What reporting does AR software provide on payment promise behaviour?
AR software provides reporting on payment promise behaviour by tracking metrics such as promise kept rate, average days between promise and payment, frequency of broken promises per customer, and the overall impact of promises on your days sales outstanding. This data helps finance teams identify which customers are reliable and which consistently overpromise.
Over time, these reports reveal patterns that are impossible to spot when you are managing invoices manually. A customer who has broken three promises in a row has a different risk profile from one who always pays within a day of committing. Reporting surfaces that difference clearly so your team can adjust credit terms, communication tone, or escalation speed accordingly.
You can also use promise behaviour data to improve your dunning workflows. If a particular message template consistently results in promises that are then broken, that is a signal to adjust the approach. If customers who receive a WhatsApp reminder are more likely to keep their promise than those who receive an email, that insight can shape how you prioritise channels going forward.
How MaxCredible helps with payment promise tracking
We built MaxCredible to take exactly this kind of complexity off your plate. Whether you are a lean finance team at a fast-growing company or a credit controller managing thousands of invoices, our platform handles payment promise tracking end to end. Here is what that looks like in practice:
- Automatic promise logging across email, WhatsApp, and SMS, so nothing gets missed regardless of which channel your customer uses
- Smart dunning workflows that pause when a promise is recorded and escalate automatically if it is broken, without anyone having to intervene manually
- Live integrations with over 800 accounting, ERP, and CRM systems including Exact, AFAS, Twinfield, SAP, and Salesforce, ensuring payment data is always current
- Creditworthiness monitoring via Dun and Bradstreet, so you can factor in risk signals when deciding how to respond to a broken promise
- Clear reporting on promise behaviour by customer, giving you the data to make smarter decisions about credit terms and follow-up strategy
Clients using our platform typically see payments arrive up to 50% faster, collection costs drop significantly, and finance teams save up to 80% of the time they used to spend on manual follow-up. If you want to see how it works for your business, get in touch with our team and we will walk you through it.
Frequently Asked Questions
How do I get started with payment promise tracking if my team currently manages everything in spreadsheets?
The first step is to connect your accounting or ERP system to an AR platform that supports promise tracking, so invoice data flows in automatically without manual entry. From there, you configure your communication channels (email, WhatsApp, SMS) and set up dunning workflows that pause when a promise is recorded. Most teams find that migrating from spreadsheets is faster than expected because the AR software imports existing invoice data and customer records, meaning you can be up and running within days rather than weeks.
Can payment promise tracking work if my customers prefer to make commitments over the phone rather than in writing?
Yes — most AR platforms include a manual promise logging feature specifically for this scenario, allowing a team member to record the agreed date and any notes directly against the invoice immediately after a call. This is just as effective as automatic detection from written replies because the promise is still centralised, visible to the whole team, and monitored by the system. The key discipline is logging the commitment straight after the conversation rather than relying on memory or a personal note.
What is a realistic promise kept rate, and how do I know if mine needs improving?
Promise kept rates vary by industry and customer base, but a well-managed AR process typically sees 70–85% of promises fulfilled on or close to the agreed date. If your rate is consistently below 60%, it usually signals one of two things: either your dunning messages are generating commitments that customers do not take seriously, or you have a segment of high-risk customers who need tighter credit terms or more proactive escalation. Your AR reporting dashboard should break this metric down by customer so you can pinpoint where the problem is concentrated rather than treating it as a blanket issue.
How should I handle a customer who repeatedly makes and breaks payment promises?
A pattern of broken promises is a credit risk signal and should trigger a review of that customer’s terms rather than simply another follow-up message. Practically, this means escalating the account to a senior team member or credit manager, considering a reduction in credit limit or a move to prepayment terms, and adjusting your communication tone to be more direct about the consequences of continued non-payment. AR software that integrates with credit monitoring tools like Dun and Bradstreet can also flag whether the customer’s broader financial position has deteriorated, which adds important context to that conversation.
Will pausing dunning workflows when a promise is recorded mean some invoices fall through the cracks if the promise is missed?
No — pausing the workflow does not mean the invoice is forgotten. The system holds the dunning sequence and actively monitors the promised payment date, automatically resuming or escalating the workflow the moment that date passes without a confirmed payment. The key is ensuring your AR software has a live integration with your accounting system so it detects incoming payments in real time rather than relying on manual updates, which is where delays and gaps typically occur.
Can promise tracking data influence the credit terms I offer new or existing customers?
Absolutely, and this is one of the most underused benefits of promise behaviour reporting. A customer with a history of keeping promises on time is a low-risk account that may warrant extended payment terms or a higher credit limit, while one with repeated broken promises is a signal to tighten terms proactively. Over time, combining promise kept rate, average days to payment, and broken promise frequency gives you a practical, evidence-based profile for each customer that goes beyond a standard credit score and reflects how they actually behave in your specific relationship.
What is the difference between a dunning workflow and a payment promise workflow, and do I need both?
A dunning workflow is the scheduled sequence of reminders sent after an invoice becomes overdue, while a payment promise workflow is the conditional logic that activates when a customer makes a specific commitment. You need both working together: the dunning workflow drives outreach and generates promises, and the promise workflow then takes over to monitor and respond to those commitments. Running dunning alone without promise tracking means your system cannot distinguish between a customer who has said nothing and one who agreed to pay yesterday, which leads to tone-deaf communication and missed escalation opportunities.
Related Articles
- How can credit management software improve cash flow?
- How does AI protect sensitive financial data in AR?
- What is intelligent debtor management?
- What is the last step before sending to collections?
- How long should you wait before sending a first reminder?
This content was generated with the help of AI and it may contain mistakes