Run a Merchant Interchange Review Without Guessing at Savings

A merchant interchange review starts with a narrow question. A finance lead sees a fee total, dislikes what appears on a statement, and asks whether a different arrangement would lower costs. An account executive who answers with a percentage has skipped the work. The useful first move is to locate the line, name what the line represents, and learn which transactions sit behind the total.

Set up a meeting with a purpose more modest than a savings presentation. Say, “Let us map the statement first. At the end, we will know which items need follow up and who owns each answer.” This language gives finance a reason to participate without asking anyone to accept an early conclusion. Invite a person who knows payment operations and a person who reads the statement. Those roles sometimes sit with one employee. They sometimes do not.

Ask for a recent statement before the session. Request a copy through the merchant’s normal secure process, rather than asking someone to paste account details into an email. Ask the finance contact to mark two or three lines which draw concern. Ask the operations contact to bring a simple view of recent payment activity, if one already exists. Useful context includes transaction type, payment channel, recurring versus individual purchase activity, and periods where volume looked unusual. Do not ask for data the team does not already have ready. The goal is a shared starting point, not an audit.

At the meeting, put one statement line on screen. Read the label aloud. Then ask, “What do you understand this charge to cover?” Wait. A controller might say, “We know this total rises in busy months, but we do not know why.” An operations manager might answer, “Most repeat buyers pay through subscriptions, and our one time orders rise around launches.” Both comments are useful, yet neither proves a cause. Capture each comment as an observation, not as a finding.

Separate the conversation into categories instead of treating every charge as interchange. A statement shows network related costs, processor charges, dispute related fees, or charges linked to a specific service. The merchant’s internal work also has a cost, though internal effort does not belong on a processor statement. When all of those items appear in one discussion, people often use “fees” as shorthand for every frustration. Slow down enough to label each bucket. A payment specialist should answer detailed questions about statement terms or pricing. The AE’s role is to make sure a specific question reaches a specific owner.

Use a plain worksheet with five columns: statement line, merchant explanation, transaction context, open question, and owner. Keep language factual. Write “subscription volume higher in June” rather than “subscriptions caused higher fees.” Write “controller requests explanation of line 14” rather than “line 14 is incorrect.” This discipline matters when a later review finds a different explanation. Nobody needs to unwind a claim made during an early conversation.

Consider a fictional practice situation. Harbor Thread, an online apparel retailer, reports concern after a statement review on Tuesday. The controller circles two fee lines. One total appears beside subscription activity. Another appears beside individual website purchases. The AE asks whether both lines cover similar activity or whether each follows a separate transaction group. The operations manager says subscriptions renew throughout a month, while individual orders spike during seasonal product releases. The controller adds, “Refunds rose during a sizing change.” No person in this fictional meeting knows whether any single fact explains the totals.

The AE records three questions. Which statement labels apply to each transaction group? Did the refund activity affect a separate charge line? Which internal person holds the report needed for a detailed comparison? The third question prevents a common stall. A meeting ends with everyone agreeing data would help, but nobody owns collection. Give a name and a date to each next step. For example, Morgan from finance sends the marked statement by Thursday afternoon. Priya from operations identifies an existing volume report by Friday. A payments specialist reviews both items during the following week.

Merchants sometimes press for a headline before those steps. A buyer might say, “Other providers say they will cut our rate. What percentage will you offer?” Do not argue with a claim you have not seen. Do not repeat a number from another conversation. Reply with the decision behind your restraint: “I hear why a clear comparison matters. First, which transactions drive your concern, and which statement lines do you want compared? Our pricing team needs those inputs before any approved review.” The response is direct, respectful, and grounded in work already discussed.

Stay alert for a reporting question disguised as a price question. A finance lead who says, “We cannot reconcile this charge,” needs a clearer explanation before any commercial discussion. Ask which report finance uses today, who prepares the report, and where labels stop matching. A useful next meeting might include a reporting owner rather than an executive sponsor. Naming this distinction helps everyone spend time on the real task. A pricing conversation without shared definitions often creates more confusion.

Likewise, do not assume every increase calls for a price review. Ask what changed around the period in question. Keep prompts open. “Did transaction volume shift?” “Did payment channels change?” “Did refund or dispute activity look different?” Avoid asking questions which imply an answer. A merchant might find no meaningful change, or the requested report might reveal an issue outside pricing. Both outcomes move the review forward because both replace guessing with an identifiable next question.

Prepare an agenda which fits thirty minutes. Open with the merchant’s concern and desired comparison. Spend ten minutes on statement lines and labels. Spend ten minutes on transaction context. Use the final minutes to assign open items, owners, and a follow up date. Send notes soon after. The notes should distinguish information supplied during discussion from items awaiting validation. A line such as “payments specialist to explain statement label after document review” is stronger than “team reviewing fees.”

Do not let a business case get ahead of evidence. A business case needs an agreed baseline, a defined comparison period, and pricing details approved through the right internal path. Until those pieces exist, speak about the review process rather than an outcome. This protects the merchant from planning around an untested estimate. This also helps internal partners work from a clean record instead of repairing an informal promise.

For practice, use the Harbor Thread situation with a colleague. One person plays the controller and asks for a ten percent reduction. The other plays the AE. Point to the subscription line, ask what activity sits behind the line, and write one open question with an owner. End by scheduling a fictional follow up for the next Tuesday after Morgan shares the marked statement and Priya identifies her existing report.