Find the Real Owner of a Reconciliation Problem

Reconciliation complaints often arrive as a short sentence: “Our team spends too much time in spreadsheets.” An account executive should resist treating those words as a product request. The sentence usually describes a result, not a single cause. Accounting compares a ledger export with a processor report. Operations investigates refunds or booking changes. A payment administrator knows where a status changed. Each person sees a different portion of one workflow.

Start with one recent item rather than a broad question about pain. Ask for a fictionalized version if details are sensitive. “Pick one refund or payment adjustment from last week. Where did your team first notice a difference?” Then ask what happened next. You are mapping a path, not trying to prove a theory. Write down each record named, each handoff, and each person who supplied an answer. Leave unknown steps marked as unknown instead of filling gaps with assumptions.

A fictional travel company offers a useful practice situation. A traveler cancels a reservation on Tuesday. The booking record changes on Tuesday afternoon. The payment record shows a refund status on Wednesday. Finance sees a different amount in a report during Friday close work. Support has an email from the traveler but no link to finance’s worksheet. None of those facts explain a failure on their own. They give the AE a route for careful questions.

The AE might say, “When finance sees an amount worth checking, which record do they open first?” The controller replies, “Usually our booking export.” The AE follows with, “What field sends them from the booking export to the payment record?” A reply such as “reservation number, unless there was a partial refund” exposes a useful condition. Ask how partial refunds receive a reference, where staff find the reference, and whether finance sees the same reference. Those questions turn a complaint into an observable investigation.

Avoid asking every question in a single call. A fast list feels like an interrogation, and a vague answer produces a vague follow up. Choose the next question from the answer you received. If the controller says, “We wait until close,” ask what triggers work before close. If they say, “Support sends us a note,” ask where finance reads the note. If they say, “Operations checks an admin screen,” ask who owns the screen and what they record after review. Each answer decides where the next conversation belongs.

Time matters, though a calendar label alone tells little. Ask when an exception becomes visible, when someone claims ownership, and when the team considers the item resolved. Those points often differ. A refund might appear on Wednesday, sit untouched until Friday, then receive a spreadsheet note on Monday. The gap does not prove a system issue. A close schedule, a missing reference, or a handoff from support might explain the delay. Name the delay before proposing any evaluation work.

Use plain language when you restate the workflow. “I heard finance begins with a booking export. A partial refund needs another reference. Support holds context from the traveler, and operations checks a separate screen. Is my outline accurate?” This recap gives each participant room to correct you. A correction is useful. For example, operations might explain a payment administrator already produces a daily exception file. Now the next meeting should include the administrator, not another general stakeholder.

Ownership is often divided by decision, not department name. The controller often owns a close deadline. An operations lead decides whether an exception needs review. A payment administrator often knows which identifier survives through several records. Support owns the customer conversation. Ask each participant what decision they make after receiving an item. “What do you decide once this reaches you?” produces a stronger answer than “Who owns reconciliation?” A team title rarely describes the actual work.

Keep product language out of the early map. Do not say a tool will eliminate exceptions, remove manual effort, or solve every mismatch. No honest discovery call has enough evidence for such a claim. Instead, state the limited purpose of a deeper review. “We would like to understand one approved workflow and learn whether a shared view of these records would be worth exploring.” This preserves the customer’s control over scope and gives them a reason to invite the people whose knowledge is missing.

An anonymized workflow review should have a narrow agenda. Ask the customer to select one item type, such as a refund, fee adjustment, or booking change. Ask them to bring the record names, available identifiers, and a description of their present review sequence. Do not ask for account numbers, customer names, or screen access during an informal call. A drawing with boxes and arrows is optional. A written sequence works well when someone walks through each step from memory.

Before the session, send a short note with only the facts already shared. “You described finance starting from a booking export, with extra work around partial refunds. We propose reviewing one anonymized partial refund. We hope to identify the records used, the reference fields available, and the people needed for any later discussion.” The note does not promise an outcome. Recipients have time to correct the focus before they spend time in a meeting.

In a role play, let the controller say, “Our team lives in spreadsheets.” A weak response says, “We solve reconciliation.” A stronger response says, “Which column tells your team an item needs manual work?” If the controller answers, “The status differs from our booking record,” ask, “Where does someone look next, and what reference do they carry with them?” The rep learns to move from a broad complaint toward a real sequence without pretending to know the answer.

Coach for patience when a prospect gives an incomplete answer. Suppose the controller says, “Operations handles refunds.” Do not treat this as final ownership. Ask, “What does operations decide before finance receives an update?” Then ask, “Who would know which reference follows a partial refund?” Those prompts might reveal two distinct roles. Or they might show one person performs both tasks during close. Either result improves the meeting plan.

Finish the working example with a clear next action. For the fictional travel company, write a meeting invitation for Thursday at 2:00 p.m. with the controller, the payment administrator, and the operations lead. The invitation names one anonymized partial refund from the prior week. Open the session by asking the controller to state the first record finance uses. Write each later record and reference in order. When the group reaches the missing reference, ask the payment administrator who enters or receives the reference, then record an owner beside the step before scheduling any further work.