Collections Call Scripts for AR Managers Reaching AP Contacts
AR managers need scripts built for bureaucracy, not just a demand to pay.

A generic collections script is built for a simple job: remind someone they owe money, ask them to pay it. That job doesn't exist on most calls an AR manager actually makes to an AP contact. AP contacts work inside a professional bureaucracy, not as lone decision-makers sitting on a check they're withholding. Their job is to process payments through a system with approval chains, shared inboxes, coordinators, and automated portals standing between "we got your invoice" and "the money moved." A script written for a single debtor has no answer for any of that.
B2B collections also run on different rules than consumer collections. FDCPA restrictions don't apply here, so an AR manager can be more direct with an AP contact than a consumer-collections agent could ever be with a cardholder. That freedom sounds like an advantage, and in a narrow sense it is, but it raises the stakes on discipline. The AP contact on the other end of the line is also a point of contact for every future invoice the company will ever send that customer. Pushing too hard or sounding too generic damages the relationship long after the specific invoice gets paid.
The invoice never arrived and is sitting in a Coupa queue waiting on an approver who's been out all week. Someone on the AP side thinks a line item is wrong. The person who used to handle this account left the company three months ago and nobody updated the AR team. A script that only prepares for "please pay this overdue invoice" collapses the second any of those branches appear, and they appear constantly. The AR manager left without a script starts improvising, and improvised calls are where discount promises get made, soft payment dates get accepted without follow-through, and relationships quietly erode one awkward conversation at a time. Emagia's guidance on AR phone calls frames scripts as flexible, customer-centric guides for the call, not rigid lines read word for word. But flexibility isn't the same as winging it. Flexibility requires a structured skeleton built for each scenario, which a generic script doesn't offer.
Preparing for a call before it reaches an AP contact
Preparation is the real work of the call, not paperwork to get through before it starts. An AP contact can tell within the first thirty seconds whether the person calling knows the account or is fumbling through a spreadsheet mid-sentence, and that first impression decides how much credibility the rest of the call gets.
Walking into the call with the invoice number, the invoice date, the exact amount outstanding, a record of every prior email and portal submission, and the current account status isn't optional homework. Quadient's guidance on collection calls treats these as the bare minimum before dialing, and for good reason: showing up with that information on hand signals respect for the AP contact's time, and it keeps the conversation focused on getting the invoice paid instead of re-explaining a situation the caller should already understand. Confirm who the actual AP contact is before picking up the phone, too. Billing contacts change jobs, move teams, and get replaced more often than AR teams update their records, and a huge share of dead-end calls trace back to someone calling a person who hasn't touched that account in months.
Know the account itself, not just the invoice. A strategic customer with a long payment history and significant future business deserves a different tone than a small, chronically late payer who's never once paid on time. Emagia's guidance on AR call strategy backs this up directly: segmenting by risk, size, payment history, and strategic importance should shape how a call gets approached before a single word gets said. Confirm, too, whether the account runs its payables through a supplier portal like Coupa or Ariba. If it does, check the invoice's portal status before the call. The AP contact is going to check that portal status anyway, often while the AR manager is mid-sentence, so walking in already knowing what they'll see keeps the conversation a step ahead.
Timing matters as much as information. An invoice approaching its due date shouldn't sit untouched until it's officially late. Early contact catches a disputed line item or a missing document while there's still time to fix it, rather than letting the problem age into something closer to a write-off. Once an invoice crosses that threshold, the move is to escalate without delay, not to wait and hope the next billing cycle sorts it out on its own.
Script for first contact when no one has responded to emails or portal submissions
First contact after silence (no reply to emails, no movement on the portal) calls for an opener that does three things at once: confirms the right person is on the line, states the purpose of the call immediately, and opens a dialogue instead of issuing a demand. Quadient's example script is a model worth borrowing almost word for word: "Hello, this is [Your Name] from [Your Company], calling about your account with us and an outstanding invoice dated [Date]." It's polite. It's direct. It gets to the point in one sentence, which is what a busy AP contact needs from a call they didn't schedule.
Confirm the contact's identity before saying anything about the invoice amount or account details. If the person on the line isn't actually the right contact, dollar figures shared too early can end up in the wrong hands or just get forgotten, and the call has to start over with someone else anyway.
Once the opener lands, shift into a problem-solving dialogue. Ask whether the invoice was received. Ask if there are any questions or concerns about it. Invite the contact to walk through what's going on from their side. This single move surfaces the real blocker instead of assuming the worst, which is usually that the customer is deliberately withholding payment, when the far more common explanation is an invoice that got buried, misrouted, or caught in a portal nobody's checked in two weeks. From here, three branches tend to open up: the invoice was never received, payment is delayed somewhere inside the customer's internal process, or there's an actual dispute. Each of those gets its own script in the sections that follow.
If the invoice was received, acknowledged, and nothing about it is in dispute, move straight to securing a commitment. Open-ended questions like "when can you pay this" invite vague answers with no real deadline attached. Use a controlled-choice question instead: "Would making a payment through your portal by [specific date] work, or would you prefer to set up a wire? I can send the banking details now." Quadient's script handles this exact moment by confirming the AP contact knows ACH, credit card, and wire are all available through the payment link, then asking directly: "Will you be making a payment today?" That kind of direct, specific ask is far more likely to produce a real answer than anything softer.
Voicemail needs its own version of this script. State the name, company, invoice number, and a callback number, clearly and without rushing through it. Never use the word "collection" in a voicemail. It puts people on the defensive before they've even called back, and it makes a routine invoice follow-up sound like a legal matter. Keep the message friendly, specific, and short enough that returning the call feels easy. Follow it immediately with an email that repeats the invoice details in writing, so the AP contact has something concrete to act on even if the voicemail gets missed.
Script for when an AP contact says the invoice is in a supplier portal and they can't act on it yet
An AP contact saying "it's in the system" or "it's pending approval" isn't a refusal, and it shouldn't be treated like one. The invoice is genuinely stuck somewhere inside a workflow the AR manager has no direct access to, and the AP contact is often just as limited in what they can do about it in that exact moment. The job on this call is to figure out, together, exactly where the invoice is stuck and what has to happen to move it.
That means asking specific, workflow-level questions instead of accepting a general status update. "Can you tell me which step it's at in your approval process?" gets further than "has this been approved yet." "Is there anything on your end, a PO match, a receipt confirmation, or a coding question, that would help move it forward?" invites the AP contact to flag a problem they might not have mentioned otherwise. "Who in your organization owns the next approval step?" gives the AR manager a name to follow up with if the call doesn't resolve things completely.
If the AR manager's company has visibility into the portal itself, whether that's Coupa, Ariba, or another system, check the invoice's exact status before raising it: submitted, received, matched, or rejected. Reference that specific status in the conversation rather than a vague statement about what was sent weeks ago. If the status shows a mismatch or a rejection the AP contact didn't even know about, that's useful information, not an argument. Offer to send a corrected document or a PO reconciliation right away, and confirm exactly who on the AP side should receive it so it doesn't land in another shared inbox and disappear.
Close this kind of call with a specific commitment, not a vague one. Ask for the name of the approver who holds the next step, and, with the AP contact's cooperation, a realistic date by which that approval should clear. That gives the AR manager something concrete to follow up on instead of calling back in two weeks to ask the same open-ended question all over again.
Script for when an AP contact disputes a line item or invoice amount
A dispute is often the most important conversation an AR manager will have on that account, the one moment where the customer is telling them directly what's standing between the invoice and payment. The script here has to move through three stages in order: listen, validate, propose a next step, all without agreeing to anything the AR manager isn't actually authorized to agree to.
Open by listening, not defending the invoice. "I want to make sure I understand the concern correctly. Can you walk me through which line item you're questioning?" gives the AP contact room to lay out the issue without feeling like they need to justify why they haven't paid yet. Emagia's framing of dispute calls captures the balance well: the caller needs to listen carefully, validate the facts, and propose a next step, whether that's a correction, a payment plan, or an escalation, all while staying inside the company's own financial controls and policies.
Two distinct types of disputes appear on these calls, and they call for different responses. A factual dispute involves something like a wrong quantity, a wrong price, or a service the customer says was never delivered. A process dispute involves something more mechanical, like a wrong PO number, missing backup documentation, or an incorrect billing address. For a factual dispute, don't agree to a credit or an adjustment on the call itself. Commit instead to reviewing it within a specific window and name who on the AR side will follow up in writing: "I'll take this back to our team and have an answer to you by [specific date]. I'll also send you a summary of this conversation so you have it for your records." For a process dispute, resolve it on the spot where possible. Offer to resend the invoice with the correct PO number, confirm what backup documentation is needed, and ask the AP contact to confirm when the corrected invoice will re-enter their approval workflow.
In either case, close with a controlled choice that keeps momentum going: "Would it be helpful if I sent the corrected invoice directly to you, or should it go through your portal?" The biggest mistake on a dispute call is accepting "we'll look into it" as if it were an answer. It isn't a next step, and it isn't a plan. A named person responsible for the review, a specific date, and a channel, email or portal, for the response keeps the dispute moving. Document the dispute, the exact objection raised, and the agreed next step right after hanging up, then send a follow-up email confirming all three in writing.
Script for when a document is missing and holding up payment
A missing document is one of the most common, and most fixable, reasons a B2B payment stalls. When an AP contact says "we're waiting on your W-9" or "we need a certificate of insurance before we can release payment," that's a specific, solvable problem, and the call should move straight into fixing it rather than treating it as another excuse to work around.
Confirm which document is missing rather than assuming it's the same one that caused a delay last quarter. Ask whether it should go directly to the AP contact or through the portal, since different companies route these differently and guessing wrong just adds another delay. Ask how long it takes to clear once it's received, so there's a real expectation set for when the invoice moves forward. If the document can go out within hours, say so on the call itself: "I can have that to you by end of day. If I send it to this email address, will that be enough to release the invoice for payment?" That kind of specific commitment, made live on the phone, tends to get action faster than any email ever will.
Sometimes the AP contact isn't even sure which document is needed, especially during a new customer onboarding or after an acquisition scrambled the AP team's processes. In that case, ask them to forward the hold notification from their own system or send over a requirements checklist. That one step saves a second round of calls over a different missing document a week later. Close by confirming the payment timeline directly: once the document lands and gets processed, ask for the specific date the invoice will hit the next pay run. Then follow up immediately with an email that attaches the document and references the invoice number and the agreed payment date, so there's a written record both sides can point back to.
Script for escalating to an AP manager when the contact-level conversation
Some calls reach a point where the AP contact genuinely can't help further, because the issue sits above their authority. Repeated vague answers, a contact who keeps deferring without a timeline, or a dispute that's dragged past the timeframe promised on an earlier call are all signs it's time to escalate. That escalation call should stay just as structured as every call before it: name the invoice, summarize the history of contact attempts briefly and factually, and state what's needed, whether that's a decision, an approval, or a firm date. Reference the prior conversation with the AP contact by name rather than skipping over it, since undermining that relationship on the way up the chain tends to make the next invoice harder, not easier. The goal of an escalation call is the same as every script before it: a specific commitment, from a specific person, by a specific date.


