Payments AEs: Mapping an Invoice Collection Workflow Before a Demo

Invoice collection sounds like a small operational detail until you sit through the demo that gets nowhere. A buyer says their invoicing process works fine, and technically they are not lying. They are describing a system they stopped noticing months ago. Your job as a payments AE is to make that system visible again, one invoice at a time, before you open a deck or mention a feature. Get the workflow wrong and you spend the demo pitching capabilities nobody asked for. Get it right and the buyer starts filling in gaps you did not know existed.

Why This Conversation Goes Wrong

Most payments AEs open with a version of "are your invoices easy to pay." That question invites a shrug and a generic answer. The buyer says yes, mostly, and you have learned nothing about who actually handles a stuck payment or a confused client.

The deeper problem is that invoice collection touches several people who rarely talk to each other. A billing coordinator sends the invoice. An account manager owns the client relationship. Finance reconciles what actually arrived. Customer success hears about it only when a client complains loudly enough. Each person sees a slice of the process and assumes the other slices work the way theirs does. When you ask a broad question, you get whichever slice the person in front of you happens to see.

You need one concrete event to pull on. A single invoice that caused a problem forces the buyer to describe what actually happened, not what is supposed to happen. That distinction matters more in payments than almost anywhere else, because the gap between the documented process and the real one is usually where the deal gets made or lost.

How To Prepare Before The Call

Before you ask anyone about their invoice process, decide what kind of event you want them to walk you through. A stalled payment link is a good choice. So is a client who disputes an amount, or a contact who left the company and never updated the billing record. Pick something specific enough that the buyer has to name a real person and a real system, not a policy.

Write down the roles you expect to hear about. For a professional services firm, that is usually a billing coordinator, an account manager, and someone in finance. You are not trying to guess the org chart correctly. You are giving yourself a way to notice when the buyer skips a role, because that skip is often the most useful thing you learn all call.

Also decide what you are not going to ask for. You do not need account numbers, dollar amounts, or client names. Asking for that detail early makes the buyer defensive and slows the conversation down. You want the shape of the process, not the specifics of any one account. Say that out loud if you sense hesitation. It costs you nothing and it buys real openness.

If you want more grounding before the call, read Payments AEs Handle Merchant Descriptor Questions With Evidence. It covers a related discovery pattern, tracing a customer question back to the system that can actually answer it, which is the same muscle you are using here.

What To Say On The Call

Open by naming the boundary. You might say, "I am not asking about specific accounts, I want to understand what happens after a client tells you an invoice link did not work." That sentence does two things. It tells the buyer you are not fishing for sensitive detail, and it gives them a concrete scenario instead of an abstract topic.

The buyer might answer, "Our billing coordinator would check the invoice system first, see if the link is active, then loop in the account manager to confirm we have the right contact." That is a good start, but it names two people and stops. Ask the next question directly. "And if the link looks fine on your end, who figures out whether the client actually tried to pay, or whether the payment attempt just did not register?"

Here the buyer often reveals the real gap. They might say, "Finance would check that, but honestly it depends on who notices first. Sometimes the account manager just calls the client back before anyone checks the system." That answer tells you the process is informal past a certain point, and that informality is exactly what a demo should address later, not something to gloss over now.

Push once more on where the client actually gets their answer. "When finance confirms what happened, how does the client find out? Same channel, same person who sent the invoice?" If the buyer pauses here, you have found the real seam. Do not fill the pause. Let them work it out loud, and write down whatever they say next word for word. That is the sentence you will reference when you plan the demo.

Mistakes That Undercut The Discovery

A few habits quietly ruin this conversation even when the AE means well.

1. Accepting the first named role as the whole answer. If the buyer says "the billing coordinator handles it," ask what happens when the coordinator is out, or when the issue needs someone with more authority. Single points of contact rarely hold up under a real question.

2. Asking about outcomes before you understand the handoff. Questions like "how often do invoices go unpaid" invite a defensive, rounded off answer. Questions about who does what and in what order invite a precise one.

3. Treating the call as a chance to plant product mentions. If you slip in a feature reference before you understand the workflow, the buyer stops describing their process and starts reacting to your pitch. Save the product for the demo, where it belongs.

4. Letting the buyer's summary stand in for the real sequence. Buyers describe their process the way they wish it worked, not always the way it actually runs. When something sounds too clean, ask for the exception. "What happens when that does not go according to plan" almost always produces the most useful answer of the call.

How To Practice And Score The Conversation

This conversation is hard to practice against a real prospect, because you only get one shot per deal and a bad first attempt costs you credibility. A manager can run it as a role play instead, playing a buyer who resists the premise, gives a clean answer on the first pass, and only reveals the messy exception when pushed a second or third time.

Score the AE on three things. Did they name a specific event instead of asking a broad question. Did they follow the handoff through at least two roles instead of stopping at the first name given. Did they end the call with a plain summary of what they heard, separated clearly from anything they still need to verify.

DealSpeak is built for exactly this kind of rehearsal. You can run the same invoice scenario against an AI counterpart that plays a resistant or vague buyer, get a transcript, and see where the questioning went generic instead of specific. Practicing the sequence a few times before a real call builds the habit of asking for the next role instead of accepting the first one you hear.

For a related workflow worth mapping the same way, see Payments AEs Clarifying Ownership of Payment Link Workflowswhich walks through a similar handoff problem on the payment link side rather than the invoice side.

If invoice collection is one of several workflows you need to map before a demo, browse the full set of Financial Services practice conversations and pick the scenario closest to your next call.

Mapping an invoice workflow before a demo takes fifteen extra minutes on the discovery call and saves you from pitching features nobody needs. The buyer who watched you trace their own process back to a real handoff will trust the rest of what you show them.