Key Takeaways
- Transformance’s AI phone agent agrees payment plans within your rules and sends a written confirmation after the call.
- Every call has one structure: who you are, the invoice, one open question, a three-item close.
- A spoken promise is not payment: in a randomized field experiment, only about half of the debtors who committed to pay actually paid (Inter-American Development Bank, 2019; tax debt).
- An objection is a diagnosis: split the undisputed part from the contested part and agree one next step with an owner and a date.
- Keep strategic accounts, disputes and anything after the formal notice with a person; let an AI phone agent cover the routine calls.
In This Article
- Key Takeaways
- What should an AR collections call say at each dunning stage?
- How should every collections call open and close?
- What do you say when the customer pushes back?
- Who should make the call: a collector, the account owner or an AI phone agent?
- What ground rules keep a B2B collections call fair?
- What should you record after the call?
- What do you leave on voicemail?
- How does Transformance support AR collections calls?
What should an AR collections call say at each dunning stage?
Name the invoice, find what blocks payment, close with amount, date and method; Transformance’s AI phone agent sends the written confirmation after the call. The stage only changes how direct the ask is.
AR collections call script by dunning stage (net 30; days from the due date; a starting policy, wording is ours)
Counted from the due date, not the invoice date. Placeholders are in brackets.
An AR collections call is a phone contact with a customer about an overdue invoice that diagnoses the blocker and ends in a dated, written commitment. Stages and days come from the net-30 row of the B2B dunning cadence; the AR aging report shows each invoice’s stage.
Why the weight sits on the close: Colombia’s national tax agency randomly assigned 34,783 tax debtors to a scripted phone call or to no contact. About 5.4% of the control group paid anything within the year, against about 11% of those assigned to a call (Mogollón, Ortega and Scartascini, Inter-American Development Bank Working Paper 10057, 2019; figures via the OECD Observatory of Public Sector Innovation summary). Of those who attended the follow-up meeting, half committed to pay, and only about half of those paid. Caveat: this is tax debt owed to a state, from a 2014 trial, and calls seemed less effective for businesses than for individuals. No published study identifies a best script for trade invoices, so the wording is ours: test two versions per segment.
Takeaway: the stage changes the ask and the owner; the close does not.
How should every collections call open and close?
Open with who you are, the invoice number, amount, due date and days overdue; close with the amount, date and method the customer commits to, then confirm it in writing.
Prepare before you dial: invoice and PO copy, proof of delivery, earlier promises, the customer’s usual payment run, and what you may offer.
The opening, in three sentences:
- Who you are, your company, and whether two minutes suit them now.
- The invoice number, amount, due date and, if late, the days past due.
- One open question: “Is there anything stopping this payment?”
The three-item close. Every call ends with an amount, a date and a method. “Soon” and “next week” are not dates. Repeat it back: “So that is $18,400 for invoice 30117, paid on 14 March by bank transfer.” If the customer cannot commit, the close is an owner and a date to come back.
Give the payer a way to act on the call. The Colombian study’s authors conclude that personal interaction must be paired with easy-to-follow, immediate actions: resend the invoice while you talk, or name the portal entry that needs approval.
Confirm in writing the same day. A spoken commitment turned into payment only about half the time in that experiment, and a call alone leaves no proof. Two lines are enough:
Thank you for your time today. As agreed, $18,400 for invoice 30117 will be paid on 14 March by bank transfer. If anything changes, please reply to this email.
Diarize the date and check on the day; how AI tracks promise to pay covers the follow-up. State next steps as facts from your payment policy, never as threats: “the next step in our payment policy is a formal notice on 2 April.”
Takeaway: without an amount, a date, a method and a same-day email, a call is a conversation, not a commitment.
What do you say when the customer pushes back?
Treat each objection as a diagnosis: confirm the facts, split the undisputed part from the contested part, and agree one next step with an owner and a date.
Late payment is often not refusal. More than half of the businesses surveyed in Western Europe name liquidity pressure as the main reason business customers pay late, and administrative bottlenecks, banking delays and technical issues add delays even where cash is available (Atradius, B2B payment practices trends in Western Europe 2026, May 2026).
Six objections and what to do with them
A payment plan is dated part payments agreed in writing, for example $6,000 on 15 April, $6,000 on 15 May and $6,400 on 15 June (illustrative).
Disputes leave the dunning cadence. A contested line moves to a dispute owner; the undisputed balance keeps running. Short payments go to cash application first: match the cash, then ask about the difference (short-payment email to a customer).
Takeaway: every objection ends in one owner and one date, and a contested amount leaves the dunning run.
Who should make the call: a collector, the account owner or an AI phone agent?
A collector makes the routine human-contact calls, the account owner takes strategic accounts before anything formal, and an AI phone agent covers the volume a team cannot reach.
An example design you adapt:
- Collector: the day +14 call for most customers, and every call where a dispute or a plan is on the table.
- Account owner: strategic accounts at about day +21 on net 30, before anything formal.
- Senior contact: calls after the formal notice and every decision on a supply hold or agency referral.
- AI phone agent: routine pre-due, due-date and reminder calls across the long tail.
Tone follows the ladder: service before the due date, specific at +7 and +14, formal at +30, final at +45.
Volume explains the last line. A human collector makes 15-20 calls a day; Transformance’s AI phone agent makes 15-20 calls an hour, in 70+ languages, and says at the start of every call that it is an AI (Transformance platform data, 2026). More in the AI calling agent guide.
Takeaway: automate the routine call, keep judgment with a person, and let the stage decide who dials.
What ground rules keep a B2B collections call fair?
Never misstate the amount, the contract or the consequence, speak only to people with a role in the payment, say if the call is recorded, and keep selling out of the call.
Many published scripts are written for consumer debt. A trade-invoice call is one company talking to another; our house rules:
- Facts only. If you are unsure of a figure, say you will check and call back.
- The right person: AP, the approver, the finance contact or the account owner.
- Consequences from the policy, with a date. Supply holds and agency referrals are a person’s decision.
- Say so if you record. Tell the customer at the start of the call, and follow the stricter local practice.
- An AI says it is an AI. Transformance’s AI phone agent does this at the start of every call.
- No upselling. A collections call is not a sales call.
This is general guidance, not legal advice.
Takeaway: a fair call is a factual call.
What should you record after the call?
Record the date, the person, the blocker, the agreed amount, date and method, and the next action, then send a two-line written confirmation the same day.
- Date, time, person and role (AP clerk, approver, controller).
- Invoice numbers discussed.
- Blocker category: paid, not received, approval, dispute, cash flow, wrong contact.
- Agreed amount, date and method, or why none was agreed.
- Next action and owner, with a date.
After a quarter, the blocker category shows whether your overdue balance is a cash problem at customers or an invoice problem at home, which is fixed upstream, not on the phone.
Further written wording is in the dunning email templates. Hold the invoice out of reminders until the promised date.
Takeaway: if it is not in the note and the confirmation email, it was not agreed.
What do you leave on voicemail?
Leave your name, your company, the invoice number and a direct call-back number, send an email within the hour, and never state amounts or consequences to a mailbox.
Hello, this is [name] from [company], calling about invoice [no.]. Please call me on [number], or reply to the email I am sending you today.
You cannot know who listens to the mailbox so the detail goes in the email. After a second unanswered attempt, change the channel or the contact; see when a B2B customer is not responding to overdue invoices.
Takeaway: voicemail gets a name and a number; facts go in the email.
How does Transformance support AR collections calls?
CollectPulse actions 100% of overdue invoices within 24 hours, and its AI phone agent makes the routine calls within your rules while a person approves what matters.
Coverage. CollectPulse actions 100% of overdue invoices within 24 hours (manual teams: 30-40%), captures 3x more promises to pay than manual work and brings DSO down 8-12 days on average (Transformance customer data, 2026).
The call. The AI phone agent agrees payment plans within rules you set and sends a written confirmation of the promise to pay or the plan after the call. Calls are recorded and kept in the audit trail. Reminders pause automatically when a dispute or a promise to pay is logged.
Rules per customer group. Tone, channel and timing of reminders can be set per customer tier or segment; see automated dunning that protects B2B customer relationships.
Control. Vero, Transformance’s AI agent, works from Customer 360 (payment history, promises to pay, disputes, deductions), investigates, proposes the next step with evidence, and a person approves, with thresholds by amount, entity and customer and a full audit trail. More: how AI automates AR collections and CollectPulse.
ERP scope. The ERP connection typically takes 2-3 days, and your IT team may be involved; full rollout takes up to 4-8 weeks (Transformance customer data, 2026). Details: which ERP systems Transformance integrates with.
Takeaway: the agent works the routine calls; your team keeps the decisions.
Who Transformance is for
- ERPs: finance teams that run AR in SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations or Business Central, or Odoo, all running in production with customers; Oracle and Infor are supported.
- Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centers.
- Payment volume: from under 1,000 to over 100,000 payments a month.
- Industries: manufacturing, consumer goods and food and beverage, logistics, e-commerce, agriculture, energy and professional services.
- Scope: cash application alone, or the full order-to-cash: cash application, deductions, AR collections and cash forecasting.
Conclusion: one structure, six stages, one written close
Every stage uses the same short call. Transformance’s AI phone agent covers routine calls within your rules; your team keeps strategic accounts, disputes and every decision after the formal notice. Book a Call to see it on your overdue list.
Key terms
- Dunning: the structured sequence of reminders and notices for overdue invoices; a call is one of its touches.
- Promise to pay: a dated, amount-specific commitment to pay, and the goal of most calls.
- Past due: an invoice not paid by its due date; days past due set the stage.
- Dispute management: handling contested invoices outside the dunning cadence.
- Payment plan: dated part payments agreed in writing.
- Escalation matrix: who takes over at which stage, with what authority.
Related guides
- Which ERP systems does Transformance integrate with?
- What is the right B2B dunning cadence?
- How does automated dunning protect B2B customer relationships?
- What is a B2B invoice dispute workflow?
- AI calling agent for accounts receivable
Frequently Asked Questions
What should you say on a collections call for an overdue B2B invoice?
Say who you are, name the invoice number, amount and due date, ask what is holding payment, and close with the amount, date and method the customer commits to. Confirm it in writing the same day.
When should you make the first collections call?
On net 30, a pre-due check at day -3 to -7 for new and strategic customers, and a human-contact call by day +14 for most others. Published first-call days vary widely, so test two versions.
Can an AI agent make collections calls?
Yes. Transformance’s AI phone agent makes 15-20 calls an hour in 70+ languages, identifies itself as AI at the start of every call and agrees payment plans within rules you set (Transformance platform data, 2026).
Should collections calls be recorded?
A call note and a same-day confirmation email are the minimum; if you record, tell the customer at the start. Transformance’s AI phone agent calls are recorded and kept in the audit trail.
Which ERP systems does Transformance work with?
SAP S/4HANA, SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo run in production with customers; Oracle and Infor are supported. The connection typically takes 2-3 days, and your IT team may be involved.
How large does a company need to be?
Transformance is built for mid-market to large enterprise teams, 250 to 2,000+ employees, handling from under 1,000 to over 100,000 payments a month, including groups with several entities.
How long does it take and what does it cost?
A full rollout takes up to 4-8 weeks (Transformance customer data, 2026). Cost depends on scope, from cash application alone to the full order-to-cash, and on the number of entities: Book a Call and we size it with you.
SAP, SAP S/4HANA, Microsoft, Dynamics 365, Business Central, Oracle, NetSuite, Odoo and Infor are trademarks of their respective owners (SAP SE, Microsoft Corporation, Oracle Corporation, Odoo S.A., Infor). Transformance is not affiliated with or endorsed by them.




