Fintech SDR Discovery: Asking About Invoice Matching Work

Invoice matching sounds narrow, but it is one of the clearest windows you have into how a finance team actually runs its accounts payable process on a discovery call. The topic has real inputs, real owners, and a real handoff between departments, which makes it one of the few topics that resists vague answers. Ask it well and the prospect describes their own process back to you. Ask it poorly and you sound like you are fishing for a weakness to sell against.

Why This Conversation Goes Wrong

You can approach invoice matching one of two bad ways. The first is leading with the pitch, asking something like "do you struggle with invoice matching errors" before the prospect has said anything about their process. That question assumes a problem exists and invites a defensive answer. Most controllers will tell you their process works fine, even when it does not, because nobody wants to admit their team fumbles paperwork to a stranger on a cold call.

The second mistake is treating invoice matching as one uniform activity. In reality it splits into distinct types of exceptions. A missing packing slip is a documentation problem. A quantity that does not match the purchase order is a business dispute between two people who may not even work in the same department. Lump these together and you miss the part of the story that actually matters, the handoff between accounts payable and whoever accepted the delivery.

Ask about invoice matching the wrong way and you get a one word answer like fine, and the call stalls. Ask about it the right way and the prospect walks you through a real sequence of events, which gives you something specific to build a follow up call around.

How to Prepare Before the Call

Before you ask a controller or an AP manager anything, know the basic mechanics of three way matching. An invoice, a purchase order, and a receiving record all have to agree on quantity, price, and terms before AP releases payment. When one of those three does not match, someone has to resolve it before the invoice pays. That resolution step, not the matching itself, is where the real conversation lives.

Write down two or three open questions before the call instead of a script. Ask what happens when an invoice does not match on the first pass. Ask who gets pulled in when the AP team cannot resolve the mismatch on their own. Ask how the answer gets back to the person waiting to release payment. Keep your questions open enough that the prospect has to describe their actual process rather than agree or disagree with your assumption.

Decide in advance what you are listening for. You want the trigger that starts an exception, the person who owns the fix, and the path the answer takes to get back to AP. Get all three and you have enough to propose a next step. Get only one and you have enough to ask a better question, not enough to book a meeting.

What to Say on the Call

Start from a fact the prospect already gave you, not from an assumption. If a controller mentions that a handful of invoices need research every week, treat that as your opening rather than restating it as a problem.

You ask, "When an invoice needs research, what does your AP person check first?"

The controller answers, "They pull up the receiving record and compare it to the invoice. If the quantity is off, they email the person who received the shipment and wait."

You ask, "Who actually settles that question, the buyer or someone in the warehouse? And once it's settled, how does that answer make it back to AP?"

The controller answers, "Usually the buyer, since they placed the order. They just reply to the email thread, and someone in AP has to remember to go back and finish the invoice."

That exchange gives you three concrete things, the trigger, which is a quantity mismatch, the owner, which is the buyer, and the return path, which is an email thread someone has to remember to check. Notice that at no point do you ask the controller to admit the process is broken. The controller described a normal, functioning workflow that happens to depend on someone remembering to close a loop. That is plenty to talk about later without ever calling it broken.

If the controller says their current method works well and sees no reason to change it, thank them and end the topic there. Do not push for a meeting the prospect has not earned. For a similar approach applied to a different handoff, see Fintech SDR Discovery Finding the Break in a Purchase Order Handoff.

Mistakes to Avoid

Do not call the process a matching problem or a matching error. That phrase puts the prospect on the defensive and makes them feel judged for something that, in most companies, is a normal part of running accounts payable. Use the prospect's own words instead. If they call it a research queue, call it a research queue. If they call it an exception, call it an exception.

Do not confuse a missing document with a disputed decision. An administrator can usually track down a missing packing slip or a copy of a purchase order in a few minutes. A quantity dispute needs the person who accepted the delivery, and that person often sits outside accounts payable entirely, maybe in procurement or in a warehouse. Treat both as the same kind of delay and you will propose the wrong fix and invite the wrong people to any follow up meeting.

Do not skip the return path question. Plenty of reps stop once they learn who resolves the exception and never ask how the resolution gets back to the person holding the invoice. That return path is usually the weakest link, an email thread, a sticky note, a hallway conversation, and it is often the most useful detail to bring into a proposal.

Do not force a meeting when the prospect says the process works. Reflect back that both roles, AP and the buyer, sit at different points in the sequence, and ask whether it would help to have someone from each side in the same conversation. If the answer is no, respect it. Pushing past a genuine no wastes the prospect's time and costs you credibility on the next call.

How to Practice and Score the Conversation

If you manage a team, score three things on this call. Did the rep learn what triggers an exception. Did the rep learn who owns the resolution. Did the rep learn how the answer gets back to AP. A call that answers all three deserves a strong score even if it never turns into a meeting, because the rep proved they can extract a real process instead of a vague complaint.

Score the language too. A rep who says "the question between AP and the buyer" is doing better work than one who says "your matching problem," even if both reps learned the same facts, because the first framing came from the prospect's own words and the second sounds like an accusation.

Before you end the call, read the sequence back in one sentence and confirm it with the prospect before proposing any next step. Something like, "So when the quantity is off, your AP team emails the buyer, and once the buyer responds, someone has to close the loop on the invoice, is that right." A prospect who agrees with that sentence has just validated your understanding out loud, which makes any next step feel earned rather than pushed.

You can rehearse this exact exchange in DealSpeak against an AI controller, try different phrasings, and see where your questions produce a real answer instead of a defensive one. That kind of practice matters more for invoice matching than for most topics, because the difference between a good question and a bad one here is a single word choice, not a whole different approach. Find more Financial Services practice conversations covering related handoffs, including how a revenue recognition dispute moves between teams, in Fintech SDR Discovery Use a Revenue Recognition Handoff as a Hypothesis.

Closing

Invoice matching gives you a rare thing on a cold call, a process with clear steps and clear owners that a prospect will happily describe if you ask without judgment. Learn the trigger, the owner, and the return path, and you have a real reason to talk again. Skip the judgment, use the prospect's own words, and let the prospect decide whether the gap is worth a meeting.