Statement Analysis for Prospecting: How Agents Turn a Merchant’s Processing Statement Into a Closed Deal

Effective merchant statement analysis for agents starts with a complete statement, a clearly defined effective-rate calculation, identification of the pricing model, separation of structural card/network costs from provider-controlled pricing, and a comparison that shows only savings the merchant can verify. The goal is not the biggest savings claim. It is the most defensible one.

A processing statement is useful because it turns a vague sales conversation into a financial discussion grounded in the merchant’s own account.

But a statement is not a treasure map where every unfamiliar fee represents processor profit.

The real skill is reconstructing what the merchant paid, understanding why the charges occurred, separating costs that would probably follow the merchant to another provider from costs that may change, and then comparing the current account with the proposed account on equivalent assumptions.

That distinction matters because the fastest way to damage credibility is to classify interchange, network costs, annual charges, gateway services, PCI program charges, equipment expenses, and processor markup as though they were all the same thing.

A good analyst does something different:

“Here is what you paid. Here is what appears structural. Here is what appears provider-specific. Here are the items that need clarification. And here is exactly how I calculated the potential difference.”

That is a far stronger prospecting position than circling a dozen statement lines in red.

Merchant Statement Analysis for Agents: The Prospecting Workflow

A disciplined statement review follows the same basic sequence whether the prospect is a restaurant processing $40,000 a month or a multi-location merchant processing several million.

Step	Agent’s Job	Desired Result
1	Earn permission to review the statement	Merchant understands why you need it
2	Obtain a sufficiently complete statement	All material fee and volume pages are available
3	Confirm statement period and volume	Correct analysis period established
4	Locate total processing costs	Numerator for effective-cost analysis identified
5	Calculate the current effective rate	Account-level cost benchmark created
6	Identify the pricing model	Interchange-plus, tiered, flat, subscription, hybrid, etc.
7	Separate probable cost categories	Structural costs distinguished from provider pricing
8	Review recurring/account charges	Monthly, annual, PCI, gateway and service fees identified
9	Inspect qualification patterns	Tiered/non-qualified or other expensive categories flagged
10	Understand transaction mix	Card-present, CNP, debit, commercial and other mix considered
11	Reconstruct proposed pricing	All material proposed costs included
12	Document assumptions	Merchant can see what was held constant
13	Present the comparison	Focus on two or three meaningful findings
14	Leave an auditable summary	Merchant can reproduce the logic
15	Follow up on unresolved questions	Conversation progresses without pressure

The sequence matters.

If you start by hunting for individual fees before establishing volume, total costs and pricing structure, you can spend fifteen minutes debating a $12 monthly charge while missing a much larger pricing issue—or discover later that the charge you criticized was an annual service cost that simply happened to appear during the month reviewed.

A statement teardown should also fit inside a broader consultative sales process. Agents who understand the responsibilities involved in being a merchant-services agent and long-term merchant advisor are less likely to treat the statement merely as a rate-shopping weapon.

How to Ask a Prospect for a Processing Statement

Many agents lose the statement before they ever get a chance to analyze it.

The problem is usually not the request itself. It is the way the request is framed.

“Can I see your processing statement?” sounds like the beginning of a rate pitch. A merchant who has heard the same request from five agents has little reason to hand over a document containing business information unless there is a clearer purpose.

Explain what you are going to do with it.

A useful explanation is:

• determine what pricing structure the account uses;
• calculate the current overall processing cost;
• identify which charges appear to be provider-specific;
• identify items that need clarification;
• compare equivalent services under a proposed account;
• tell the merchant if the analysis does not reveal a meaningful financial improvement.

That last point matters.

The merchant is more likely to share information when the review is positioned as an analysis rather than a predetermined conclusion.

Why Merchants Hesitate

Common objections are reasonable.

A statement may disclose:

• business name;
• merchant identification information;
• processor or acquirer information;
• processing volume;
• transaction counts;
• pricing;
• account or funding references;
• refunds or adjustments;
• chargeback activity;
• service subscriptions.

A business owner may also worry that an agent will cherry-pick an expensive line, quote an unrealistically low replacement rate, or spend the next month making aggressive follow-up calls.

Your approach should reduce those concerns, not dismiss them.

Illustrative Cold-Prospect Wording

“If you’re open to it, send me one recent complete processing statement—all pages. I can break down your current pricing, calculate the overall cost and identify which charges appear to be provider-specific versus costs that would likely exist with another provider. I won’t assume there are savings. If the account is already priced competitively, I’ll tell you that.”

This works because it explains both the request and its limits.

It also avoids the trap of promising:

“I’ll save you 30%.”

No responsible analyst can know that before seeing the account.

Illustrative Warm-Prospect Wording

“Since we’ve already talked about your processing setup, the next useful step is your latest complete statement. Please include every page because the fee detail is often separate from the summary page. I’ll use it to reconstruct your current costs and compare them with the proposal on the same volume and transaction assumptions. Was this a fairly typical month for you, or did anything unusual happen?”

Then ask whether the month included:

• unusual seasonal volume;
• a large promotion;
• an unusually high refund period;
• material chargebacks;
• annual account charges;
• equipment purchases;
• a recent price change.

Those questions can prevent a bad annual projection later.

Handle Statement Security Like Business Information, Not Sales Collateral

Do not ask a prospect to post a statement publicly or send sensitive business documents through an unapproved channel simply because it is convenient.

Use the secure intake method approved by your ISO, acquirer or organization.

A processing statement is not automatically equivalent to a database containing cardholder account data merely because it relates to payment processing. But it may contain confidential merchant, account and financial information that deserves appropriate handling.

At minimum:

• collect only what is needed;
• use approved secure transmission and storage processes;
• restrict access to people who need the document;
• follow your organization’s retention and deletion procedures;
• do not circulate statements as sales examples without proper authorization and redaction.

Professional document handling is part of the prospect experience.

Is the Statement Complete Enough to Analyze?

A screenshot of the first page may be enough to begin a conversation. It is rarely enough for a defensible savings proposal.

For a useful review, try to obtain:

• all pages;
• statement period;
• gross or processed sales volume;
• refunds or credits if separately reported;
• transaction count;
• total fees;
• discount or interchange detail where available;
• assessments/network-related detail where available;
• account-level fees;
• gateway or software charges shown on the statement;
• adjustments;
• PCI-related charges;
• chargeback fees where relevant.

If the statement shows “$3,182.44 total fees” but the pages explaining those fees are missing, you can calculate an account-level effective cost, but you cannot responsibly tell the merchant how much of that total is processor markup.

Mark the analysis preliminary until the missing detail is obtained.

The Five-Minute Statement Teardown

A fast statement analysis should not mean a careless one.

The objective of a five-minute review is to determine whether the account deserves deeper analysis and identify the questions worth asking next.

Minute 1 — Confirm Volume and Total Fees

Locate:

• statement dates;
• gross card sales or processed volume;
• refunds;
• net sales if shown;
• transaction count;
• total processing charges.

Do not immediately copy the largest “sales” figure without understanding what it represents.

Statements may show gross sales, net sales, settled sales, card-brand subtotals, refunds and other volume measures differently.

Choose the denominator that corresponds to the processing activity you are measuring and document the choice.

If the incumbent statement calculates pricing using gross settled purchase volume while your proposal model uses net sales after refunds, silently switching denominators can create an artificial difference.

Minute 2 — Calculate Effective Rate

The basic calculation is:

Effective processing rate = relevant processing costs ÷ applicable processed sales volume × 100

Illustrative example:

A merchant processes $100,000 during the statement period and the costs included in the analysis total $2,700.

$2,700 ÷ $100,000 = 0.027

Effective processing rate = 2.70%.

That number tells you the merchant’s cost relative to the selected volume.

It does not tell you how much the processor earned.

It also does not prove that 2.70% is good, bad, high, low or reducible.

You still need to understand the account.

Minute 3 — Identify the Pricing Model

Look for clues indicating:

• interchange-plus;
• tiered or bundled;
• flat rate;
• subscription/membership pricing;
• hybrid/custom pricing.

Statement terminology varies among processors, so treat labels as evidence, not absolute definitions.

Minute 4 — Separate the Major Cost Buckets

Create provisional categories:

1. card-product/interchange economics;
2. card-brand or network costs;
3. processor/acquirer markup;
4. recurring account fees;
5. ancillary services;
6. conditional or event-driven fees.

Some statements make this relatively straightforward. Others bundle several categories together.

If you cannot isolate a cost reliably, label it “requires verification” rather than forcing it into a convenient bucket.

Minute 5 — Mark Questions, Not Just “Bad Fees”

Flag items such as:

• PCI non-compliance charges;
• monthly minimums;
• repeated non-qualified tiers;
• large recurring service fees;
• unusually high authorization expense;
• gateway fees;
• batch fees;
• annual or quarterly charges;
• unexplained product/service fees;
• equipment expenses;
• unusual chargeback-related costs.

A question mark is often more useful than a red circle.

The objective is to create informed discovery:

“What is this charge?”

“Is this service still being used?”

“Does this amount appear every month?”

“Can we reconcile this to the agreement?”

That is a more credible statement teardown sales technique than manufacturing outrage.

Effective Rate: Useful, but Easy to Misuse

Effective rate is one of the fastest ways to summarize an account and one of the easiest numbers to manipulate.

The arithmetic is simple.

The definition of the numerator is not.

Define What “Total Fees” Means

Two agents can analyze the same statement and report different effective rates because they included different costs.

Potential numerator items include:

• discount/interchange-related costs;
• network assessments and card-brand costs;
• processor markup;
• authorization charges;
• per-item charges;
• batch charges;
• monthly service fees;
• statement fees;
• gateway fees;
• PCI program charges;
• software fees;
• equipment rental.

Other items may need separate treatment depending on what the analysis is intended to measure:

• chargeback principal;
• refund principal;
• one-time terminal purchase;
• equipment installation;
• early termination fee;
• cash advances;
• unrelated software subscriptions;
• annual charges appearing in only one month.

There is no value in saying:

“Your effective rate is 3.08%.”

without being able to answer:

“What did you include in that number?”

A professional proposal might instead state:

Effective cost for this analysis includes processing, card/network-related charges, authorization fees and recurring account charges shown on the statement. It excludes chargeback principal and the one-time terminal purchase identified below.

Now the merchant can reproduce the calculation.

Gross Volume vs. Net Volume

The denominator deserves the same discipline.

Suppose a merchant has:

• purchases;
• refunds;
• reversals;
• multiple card-brand totals;
• PIN debit;
• separate ecommerce activity.

One processor may summarize the statement around gross purchases while another report emphasizes net settled volume.

If you calculate the incumbent’s costs against one denominator and your proposed costs against another, the resulting comparison is unreliable.

Use like-for-like definitions wherever possible.

If perfect matching is impossible, disclose the difference instead of burying it.

Do Not Let One Abnormal Month Become a Twelve-Month Promise

One recent statement may be enough for an initial analysis.

It may not be enough for a confident annual projection.

Request two or three months when the account has meaningful variation caused by:

• seasonality;
• holiday volume;
• restaurant ticket changes;
• ecommerce promotions;
• annual charges;
• changing commercial-card mix;
• recent rate changes;
• unusually high refunds;
• exceptional chargeback activity.

Suppose the current month contains an annual account fee. Multiplying that entire month’s cost difference by twelve could overstate annual savings.

The better approach is to normalize the annual charge across the comparison or review a longer period.

Identifying the Pricing Model

The pricing model changes what you need to analyze.

Pricing Model	Typical Statement Clues	What the Agent Must Be Careful About
Interchange-plus	Interchange/card costs separated from processor markup	Do not portray pass-through interchange as processor profit
Tiered	Qualified, mid-qualified and non-qualified buckets	Tier definitions and qualification rules vary
Flat rate	Simple percentage and/or transaction price	Simplicity is not automatically evidence of bad pricing
Subscription/membership	Recurring membership charge plus transaction pricing	Membership cost belongs in the total comparison
Hybrid/custom	Combination of several structures	Reconstruct the entire model before claiming savings

Interchange-Plus

Interchange-plus, often abbreviated IC+, generally separates underlying interchange from an added processor/acquirer markup.

That can make comparison easier—but only when the statement provides enough detail.

You still need to identify:

• the basis-point markup;
• per-item markup;
• authorization costs;
• monthly account charges;
• gateway expenses;
• other services.

A low basis-point number can look excellent while recurring and transaction-level charges push total cost higher.

Tiered or Bundled Pricing

Tiered statements often group transactions into categories such as:

• qualified;
• mid-qualified;
• non-qualified.

Those are pricing constructs used by processors; they are not universal interchange categories.

A merchant with substantial non-qualified volume deserves investigation, but the label alone does not establish why the transaction landed there.

Flat-Rate Pricing

Flat pricing can be relatively easy for the merchant to understand.

Do not criticize it merely because you can reconstruct a potentially cheaper IC+ account.

The relevant question is whether the proposed alternative provides a meaningful total-cost or operational improvement after all services and fees are included.

Subscription Pricing

Subscription models may combine:

• monthly membership fee;
• lower percentage markup;
• transaction fee;
• gateway or software charges.

The membership cost belongs in the comparison.

Leaving it out because it is not expressed as a rate is not an apples-to-apples analysis.

Interchange vs. Markup on Statements: What the Agent Can Honestly Claim to Save

This is where weak statement analyses often fall apart.

Merchant acceptance cost is not one number controlled entirely by the salesperson’s processor.

At a high level, the merchant’s cost may contain:

card-product/interchange economics + network/card-brand costs + acquirer/processor pricing + ancillary services + conditional charges.

Visa’s current explanation is particularly useful because it clarifies a frequently misstated point: interchange reimbursement fees are transfer fees between acquiring and issuing banks, while the merchant negotiates and pays its merchant discount through its financial-institution relationship. 

Visa’s current U.S. interchange reimbursement information links to its applicable U.S. schedules; the current U.S. schedule located during review is effective April 18, 2026.

Mastercard similarly states that interchange rates are generally paid by acquirers to issuers and that interchange is one component of the Merchant Discount Rate established by the acquirer. 

Its current merchant interchange explanation and U.S. rate resources also explain that qualification can depend on factors including merchant category, authorization-to-clearing timing, transaction data and product characteristics.

That is why an agent should avoid saying:

“Visa is charging you this fee and I can remove it.”

or:

“All of this interchange is processor profit.”

Neither is an accurate description.

What Is More Likely to Be Provider-Controlled?

Depending on the agreement and pricing architecture, differences may exist in:

• basis-point markup;
• transaction markup;
• authorization pricing;
• batch charges;
• monthly account charges;
• gateway pricing;
• software pricing;
• equipment costs;
• ancillary service pricing.

“Potentially provider-controlled” still does not mean “automatically removable.”

Use your actual proposal.

If your proposed account includes a monthly PCI program charge, gateway fee or batch fee, those belong in the comparison even if the incumbent uses different names.

Network/Card-Brand Costs Are Another Bucket

Do not collapse assessments or network-set charges into processor markup simply because they appear on the processor’s statement.

A statement may pass network-level costs through explicitly, bundle them, mark them up, or use terminology that is difficult to interpret.

The proper analytical question is not:

“Is there a fee with Visa or Mastercard in the name?”

It is:

“What does this line represent, how is it calculated, and how would the same category be treated under the proposed account?”

Sometimes the answer requires processor documentation or the merchant agreement.

That is acceptable.

A good analyst is allowed to say, “I cannot confirm this from the statement alone.”

Interchange Optimization Is Not the Same as Markup Reduction

Some opportunities are operational rather than contractual.

A merchant may potentially improve transaction qualification through better data, configuration or processing practices.

Examples can include:

• supplying transaction information required for an applicable interchange program;
• transmitting appropriate enhanced data for eligible commercial-card transactions;
• configuring card-present transactions correctly;
• correcting avoidable authorization or settlement practices.

But optimization claims require evidence.

Before projecting savings, understand:

• merchant category;
• acceptance channel;
• card-present versus card-not-present mix;
• commercial-card usage;
• transaction data currently supplied;
• authorization and clearing practices;
• current interchange qualification;
• gateway capabilities.

Do not promise:

“We’ll qualify every transaction at the lowest interchange rate.”

There is no single universal lowest rate for every transaction. Current Visa and Mastercard materials both show that interchange structures vary by product, transaction conditions and other criteria.

Don’t Call Every Line Item a Junk Fee

“Junk fee” may be useful shorthand in conversation, but it is a poor analytical category.

Statement charges usually fit more useful descriptions:

Category	Better Analytical Question
Legitimate pass-through cost	Would this cost substantially follow the merchant to another provider?
Processor-specific fee	How is it defined in the agreement?
Optional service fee	Does the merchant still need or use the product?
Conditional charge	What condition triggered it?
Penalty-like charge	Can the merchant correct the triggering condition?
Unexplained line	What documentation explains the charge?
Potential duplicate	Are two charges paying for materially different services?

Use phrases such as:

• fee worth investigating;
• processor-specific recurring charge;
• conditional account charge;
• line that should be reconciled to the agreement;
• potentially avoidable charge;
• service whose continuing value should be confirmed.

Do not call something fraudulent merely because you do not recognize the abbreviation.

PCI Non-Compliance Fees: Separate the Standard From the Processor Charge

PCI terminology is frequently mishandled during statement pitches.

PCI DSS establishes security requirements for entities in the payment ecosystem. PCI SSC states that PCI DSS is intended to apply to merchants regardless of size, while the applicable validation and reporting requirements are managed through payment brands, acquirers and other compliance-accepting entities. 

PCI SSC also states that the Council itself does not manage compliance programs or impose non-compliance consequences.

That distinction is why an agent should never tell a merchant:

“PCI requires this $29 monthly fee.”

merely because the statement says “PCI.”

A processor or acquirer may operate a compliance program and may contractually charge:

• PCI program fees;
• validation-related fees;
• security-program fees;
• non-compliance charges.

But the statement charge and the PCI DSS security standard are not the same thing.

The current PCI SSC guidance on merchant PCI DSS validation responsibilities makes clear that merchants should work with their acquirer/payment brand on their validation requirements.

When a PCI-related charge appears, ask:

1. What is the exact statement description?
2. What does the incumbent say the charge covers?
3. Is the merchant’s required validation complete?
4. Is the charge conditional on incomplete validation?
5. Would completing the required validation affect it?
6. Does your proposed provider have a comparable PCI program charge?
7. What must the merchant do under the new provider’s validation program?

That converts a provocative fee into an operational question.

Tiered Pricing and Downgrades: Look for the Pattern, Not Just the Label

Tiered pricing commonly uses labels such as:

• qualified;
• mid-qualified;
• non-qualified.

The exact structure is processor-specific.

A large amount of non-qualified or higher-tier volume deserves attention because it may materially affect the merchant’s effective cost.

But avoid jumping directly from:

“I see non-qualified volume.”

to:

“Your processor intentionally downgraded these transactions.”

Possible contributors can include:

• card-product mix;
• rewards products;
• commercial cards;
• card-not-present transactions;
• transaction-data requirements;
• authorization/settlement timing;
• merchant category;
• processor tier design.

Your job is to determine what is observable and what still needs explanation.

A productive conversation sounds like:

“A meaningful portion of your volume is falling into the higher-priced tier. I want to understand which card and transaction types are driving it before I assume we can eliminate that cost.”

That preserves credibility.

Monthly Minimums: Read the Contract Before Explaining the Formula

A monthly minimum generally creates a contractual minimum amount of qualifying processing or discount charges the merchant must generate during the billing period.

Exactly which charges count toward that minimum can vary.

Do not assume the label alone tells you the formula.

Check:

• the amount actually charged;
• the pricing schedule;
• what fees count toward the threshold;
• whether the merchant regularly falls below it;
• whether seasonality triggers the minimum;
• whether the proposed account includes its own minimum or volume commitment.

A minimum can matter greatly to a low-volume or seasonal merchant and be irrelevant to another account that consistently exceeds it.

Other Fees Worth Investigating

A statement review should distinguish “questionable” from “unfamiliar.”

Statement Fee

May cover paper statements or account administration.

Ask whether:

• electronic statements are available;
• the proposed provider has an equivalent charge;
• the merchant actually receives a service associated with it.

Batch Fee

May apply when transactions are settled in a batch.

Evaluate frequency.

A seemingly small batch charge can matter more to a merchant closing multiple batches each day than to a merchant settling once.

Gateway Fee

May cover ecommerce or virtual-terminal gateway access.

Before promising to remove it, verify whether the proposed account:

• includes the gateway;
• bills it separately;
• uses a different gateway;
• requires an additional integration fee.

Authorization Fee

May apply per authorization attempt.

Transaction count matters here.

A percentage-only comparison can badly understate costs when one proposal carries materially higher per-transaction charges.

AVS Fee

Address Verification Service-related charges may occur in card-not-present environments.

Confirm:

• whether it is separately priced;
• whether the proposed gateway or processor handles it differently;
• whether the merchant relies on AVS as part of its fraud controls.

Voice Authorization

An occasional voice-authorization fee may simply reflect a legitimate exceptional transaction.

Repeated usage deserves an operational question.

Monthly Service or Account Fee

Determine what it covers and whether the proposed provider charges something comparable under another name.

Regulatory or Product Fee

The label alone is not proof that the charge is government-mandated, network-mandated or processor-created.

Ask for the provider’s definition.

Annual Fee

Annual charges can distort a one-month statement comparison.

Normalize them appropriately.

Equipment and Software Fee

Confirm whether the merchant:

• rents;
• owns;
• leases;
• subscribes;
• bundles software with processing.

Switching the merchant into “cheaper processing” while adding a costly POS subscription is not a savings win.

Chargeback Administration Fee

Separate the transaction principal from the administrative charge.

Also distinguish ordinary recurring processing economics from an abnormal month containing heavy dispute activity.

Red Flags Worth Leading With

Do not overwhelm a merchant with twenty annotations.

Lead with the issues that are understandable, financially meaningful and verifiable.

Finding	Why It Deserves Attention	What to Verify Before Pitching
PCI non-compliance fee	May be tied to incomplete validation or the provider’s program	Merchant validation status + incumbent terms
Repeated non-qualified tiers	Could materially affect effective cost	Card mix + processor tier rules
Monthly minimum	Can increase cost in slower periods	Contract calculation
High apparent markup	May be provider-controlled	Separate it from pass-through costs
Apparent duplicate service fees	Merchant may be paying for overlapping products	What each service actually provides
Equipment lease	Can change switching economics	Remaining lease obligation
Large annual fee	Makes one month look unusually expensive	Normalize it across the analysis period

None of these is proof of misconduct.

They are reasons to ask better questions.

Build a Savings Proposal the Merchant Can Verify Line by Line

A good savings proposal does not require the merchant to trust your spreadsheet.

The merchant should be able to trace each major line back to:

• the statement;
• the proposed pricing schedule;
• a clearly identified assumption.

Use a layout like this:

Cost Category	Current Statement	Proposed Pricing	Difference	Assumption
Card/interchange-related costs	Based on observed mix	Held constant unless justified	—	Same card mix
Network/card-brand costs	Current treatment	Equivalent proposed treatment	Difference if documented	Same network mix
Processor markup	Current reconstructed markup	Proposed contractual markup	Calculated difference	Same sales volume
Per-item fees	Current	Proposed	Calculated difference	Same transaction count
Monthly account fees	Current	Proposed	Calculated difference	Like services included
Gateway/POS	Current	Proposed	Calculated difference	Equivalent functionality
Other recurring services	Current	Proposed	Calculated difference	Matched where applicable
Total estimated cost	Current total	Proposed estimate	Estimated difference	Based on stated period

The strongest proposals are boring in the best possible way.

Every number has a source.

Every assumption is visible.

Every material exclusion is disclosed.

Hold Constant What You Cannot Predict

If you are comparing processors rather than redesigning the merchant’s transaction environment, the cleanest model often holds constant:

• card mix;
• transaction channel;
• monthly volume;
• transaction count;
• average ticket;
• regulated versus exempt debit mix;
• rewards mix;
• commercial-card mix.

You can then isolate the pricing differences you are actually proposing.

If the proposed solution genuinely changes transaction qualification—for example, through better eligible commercial-card data—show that as a separate optimization scenario rather than quietly lowering assumed interchange in the base comparison.

Apples-to-Apples Means More Than Processing Rates

A basis-point reduction does not automatically create a cheaper account.

Compare the complete operating package.

Material items can include:

• terminal purchase;
• terminal rental;
• equipment lease;
• gateway;
• virtual terminal;
• POS software;
• PCI program charges;
• monthly account fees;
• batch fees;
• authorization fees;
• chargeback pricing;
• faster-funding fees;
• integrations;
• minimums;
• annual fees;
• contract duration.

If the incumbent includes POS software in the current cost and the proposed solution requires a separate subscription, include that subscription.

If the proposed processor advertises lower markup but requires a paid gateway, include it.

A merchant should be able to ask:

“What will my total account cost under the same operating conditions?”

and receive a useful answer.

Annualized Savings: Show the Math and the Limitations

Suppose a like-for-like analysis identifies an estimated $210 monthly difference attributable to provider-controlled or otherwise avoidable costs.

The annualized estimate is:

$210 × 12 = $2,520

The correct presentation is:

Estimated annual difference: $2,520, assuming comparable volume, transaction count, card mix, services and pricing remain consistent.

Avoid:

Guaranteed annual savings: $2,520.

Card mix, sales volume, qualification and other variable costs can change.

If the proposed provider genuinely offers a contractual guarantee covering specified fees, describe that guarantee exactly as written. Do not transform a limited guarantee into a universal promise.

Every Savings Claim Needs an Audit Trail

At minimum, document:

1. source statement period;
2. processed sales volume used;
3. transaction count when relevant;
4. current costs included;
5. current costs excluded;
6. proposed costs included;
7. proposed costs excluded;
8. assumptions held constant;
9. one-time charges normalized;
10. qualification-dependent assumptions;
11. services matched between accounts.

Watch for common presentation tricks—even accidental ones:

• incumbent annual fee included, proposed annual fee ignored;
• current gateway included, proposed gateway omitted;
• high seasonal month projected against lower assumed future volume;
• interchange treated as processor profit;
• gross current cost compared with only proposed markup;
• every transaction assumed to qualify at an idealized rate;
• equipment lease ignored because it is “not processing”;
• monthly subscription left off because it appears on another invoice.

A clean savings proposal from a statement should survive scrutiny from the incumbent processor.

That is a feature, not a weakness.

The Teardown Should Create Questions, Not Manufacture Outrage

A statement presentation is usually strongest when it has two or three findings.

For example:

“Your overall effective processing cost for this period is 2.70% using the costs and volume shown here.”

“This group of charges appears to be provider-specific rather than underlying interchange.”

“This PCI-related line needs verification against your current compliance status and agreement.”

“I held the observed card mix and transaction volume constant when modeling the proposed account.”

That gives the prospect something understandable to evaluate.

Do not turn the presentation into theater.

Statements full of red circles, arrows and words like “RIP-OFF” may create short-term emotion, but they also invite the merchant’s current provider to dismantle your credibility one inaccurate line at a time.

For agents developing a broader local prospecting practice, a relationship-first approach fits naturally with the principles in this guide to building a merchant-processing agent business: needs discovery and continued support matter after the initial pricing discussion as much as the first quote.

Presenting the Findings Without Trash-Talking the Incumbent

Attacking the incumbent usually adds little analytical value.

Instead of:

“Your processor is stealing from you.”

Say:

“This appears to be a provider-specific charge. I would compare it with the pricing schedule in your current agreement.”

Instead of:

“Their rates are terrible.”

Say:

“Based on this statement period, the provider-controlled pricing appears higher than the proposal I am showing.”

Instead of:

“They hid this fee.”

Say:

“The statement description does not explain this line clearly enough for me to classify it. I would ask the provider what it covers.”

The difference is more than tone.

Neutral language forces your analysis to stand on evidence.

That is exactly what you want when the prospect takes your proposal back to its current representative.

What If the Current Provider Matches Your Price?

Assume this can happen.

A merchant may send your analysis to the incumbent, receive a retention offer and stay.

Do not respond by hiding your calculations or inventing another problem.

Compare the counteroffer.

The decision may then involve:

• markup;
• contract term;
• equipment obligations;
• pricing transparency;
• reporting;
• integration quality;
• support;
• onboarding risk;
• operational features.

If the incumbent’s written counteroffer is legitimately more attractive, say what the numbers show.

You can still compete on differences that are real.

A merchant who sees you accurately analyze a competitor’s better offer is more likely to regard you as a professional rather than a rate salesperson.

When the Prospect Says, “I’ll Check With My Processor”

That objection is not necessarily a rejection.

A useful response is:

“That makes sense. Ask them about these specific lines and whether any pricing change they offer is permanent or promotional. If they revise the account, send me the written offer and I’ll compare it using the same volume, transaction count and service assumptions.”

Then stop selling for a moment.

Give the merchant something concrete to investigate.

Follow-Up 1 — Ask What the Incumbent Explained

Do not reopen with:

“Have you decided?”

Ask:

“Were they able to explain the PCI line and the monthly minimum?”

Now the follow-up continues the analysis.

Follow-Up 2 — Review the Written Counteroffer

If pricing changed, request the written schedule.

Verbal promises are difficult to compare.

Follow-Up 3 — Compare the Same Categories

Check:

• markup;
• per-item costs;
• recurring fees;
• gateway;
• equipment;
• contract length;
• minimums;
• annual charges;
• promotional pricing;
• ancillary services.

Final Follow-Up — Leave the Analysis Useful

A concise closing note might say:

“I summarized the current statement, their revised pricing and my proposal using the same assumptions. If your processing mix changes materially, the estimates should be updated.”

That gives the prospect a document worth keeping.

Repeated pressure calls rarely improve the quality of the analysis.

Do Not Ignore Early-Termination and Equipment Obligations

A processing proposal can show real monthly savings and still be a poor near-term switch.

Investigate:

• early termination provisions;
• liquidated-damages clauses;
• equipment leases;
• POS contracts;
• gateway commitments;
• integration costs;
• outstanding equipment balances;
• installation or migration expenses.

A merchant statement may reveal an equipment line but not the remaining contractual obligation.

Do not guess.

Ask for the relevant agreement when switching economics depend on it.

A simple calculation illustrates the problem:

If the merchant might save $200 a month but faces a substantial non-cancellable equipment obligation, the gross savings figure alone does not answer whether switching now makes sense.

Timing is part of the analysis.

When to Analyze Multiple Statements

One month works well for preliminary prospecting when the account is stable.

Two or three months are more useful when:

• volume is seasonal;
• ticket mix changes;
• holiday activity is significant;
• ecommerce promotions distort the month;
• annual charges appear;
• commercial-card usage changes;
• pricing recently changed;
• refunds vary significantly.

For a restaurant, one month may capture an unusually high share of premium rewards cards.

For a B2B supplier, one month may contain unusually heavy commercial-card volume.

For an ecommerce merchant, a promotion may alter ticket size, authorization count and refund behavior.

A multi-month view reduces the risk that you attribute normal mix variation to the incumbent processor—or to your proposed savings.

Four Statement-Analysis Scenarios

Scenario 1 — The Expensive-Looking Interchange-Plus Account

Hypothetical.

A merchant processes $80,000 during the month and incurs $2,160 in costs included in the analysis.

Effective cost:

$2,160 ÷ $80,000 = 2.70%.

At first glance, an agent may see 2.70% and assume there is a large savings opportunity.

A deeper review shows that most of the cost appears tied to the merchant’s observed card/product and network mix. The identifiable provider-controlled spread is comparatively modest.

The right pitch is not:

“I can bring you down by a full percentage point.”

It is:

“Most of your cost appears structural to the transactions you’re accepting. I see a smaller provider-pricing difference that may be worth discussing, but I would not characterize the entire 2.70% as processor markup.”

The credibility gained may be more valuable than an exaggerated quote.

Scenario 2 — The Tiered Merchant With Heavy Higher-Tier Volume

Hypothetical.

A statement shows qualified, mid-qualified and non-qualified pricing, with a material amount of sales landing in the more expensive buckets.

The useful finding is:

“A significant portion of this account is priced outside the base qualified tier.”

The next questions are:

• Which card types are landing there?
• Are card-not-present transactions involved?
• Does the current tier structure reprice particular products?
• Are transaction-data or timing issues relevant?
• What would the merchant’s actual card mix cost under the proposed model?

A credible proposal reconstructs the known transaction mix under the new model.

It does not pretend the underlying card economics disappear.

Scenario 3 — The PCI Non-Compliance Charge

Hypothetical.

A merchant’s statement contains a monthly “PCI NON-COMP” line.

A poor agent says:

“That’s a fake fee. I’ll eliminate it.”

A better agent asks:

• Have you completed the validation requested by your current provider?
• Did the provider tell you why this charge began?
• Is the charge removed after the required validation is accepted?
• Does the proposed account have its own PCI program charge or validation process?

The agent may ultimately discover an avoidable charge.

But that conclusion comes after verification.

Scenario 4 — The Incumbent Counteroffer

Hypothetical.

An agent identifies a genuine pricing difference and gives the merchant an auditable comparison.

The incumbent responds by lowering its markup and removing one recurring account charge.

The agent now performs the analysis again.

Do not keep comparing your proposal with the old incumbent statement.

Compare:

revised incumbent offer vs. current proposed offer

using:

• identical volume;
• identical transaction count;
• equivalent services;
• the same assumed card mix.

If the financial difference becomes small, talk about the remaining contractual, service, technology and support differences.

Do not manufacture new “hidden fees” because the original savings advantage disappeared.

Common Statement-Analysis Mistakes That Cost Agents Credibility

Using the Wrong Volume Denominator

Dividing by net sales for one provider and gross sales for another can manufacture a rate difference.

Analyzing an Incomplete Statement

A first-page screenshot may show total fees without enough information to classify them.

Treating Interchange as Processor Markup

This can dramatically inflate the supposed “negotiable” portion of the account.

Calling Every Assessment a Processor Fee

Network-level and provider-level charges are different categories.

Ignoring Transaction Count

Per-item pricing can materially change the proposal even when percentage pricing looks lower.

Treating an Annual Charge as Monthly

A month containing an annual fee can make the account look artificially expensive if the charge is multiplied by twelve.

Ignoring an Annual Charge Entirely

The reverse error also occurs: agents remove an incumbent annual fee from the comparison but forget that their own proposed provider charges one.

Using an Abnormal Month

Seasonality, promotions, commercial-card volume or unusual refunds can distort projections.

Ignoring Equipment Obligations

A processing difference is not the same as net switching economics.

Assuming Every Non-Qualified Transaction Can Be Fixed

Higher-priced transactions may reflect card type, channel, data, tier structure or other factors.

Comparing Different Service Packages

Removing a gateway, POS platform or faster funding option from the proposed cost is not savings if the merchant still needs the service.

Omitting the Proposed Gateway

A common way to make a proposal look cheaper is to compare the incumbent’s all-in statement with only the proposed processing pricing.

Promising the Cheapest Theoretical Interchange

The relevant question is what the merchant’s actual transactions are likely to qualify for.

Treating a Processor PCI Fee as a PCI SSC Fee

PCI DSS requirements and provider billing programs are not interchangeable concepts.

Trash-Talking the Current Provider

Aggressive accusations create an easy opening for the incumbent to discredit the rest of the analysis.

Hiding Assumptions

If the savings depend on an assumption, put the assumption in the proposal.

The Goal Is Not to Prove Every Prospect Is Overpaying

Some statement analyses will produce an inconvenient result:

The current account is reasonably priced.

That is not a failed analysis.

You may find:

• only modest markup savings;
• competitive existing pricing;
• equipment obligations that outweigh short-term savings;
• card mix driving most of the merchant’s costs;
• an incumbent counteroffer that closes the gap;
• operational advantages in your platform but no dramatic rate savings.

Say so.

An agent who can tell a prospect:

“I can offer you a different platform, but I cannot support a large savings claim from the statement you’ve given me.”

is demonstrating something competitors cannot easily imitate: restraint.

That matters for long-term accounts.

Residual income is more durable when the original sale was based on expectations the account can actually meet.

FAQ

Accuracy Is the Closing Technique

Strong merchant statement analysis for agents is not about discovering the scariest-looking fee.

It is about reconstructing the merchant’s actual cost, separating structural card and network economics from provider-controlled pricing, finding charges that deserve investigation, and presenting an apples-to-apples comparison the merchant can independently verify.

Accuracy protects more than the immediate pitch.

It protects your credibility when the incumbent reviews your proposal. It builds merchant trust when actual billing begins. It improves close quality because the prospect understands what is changing. And it supports account longevity and residual income because the merchant was sold on numbers the new relationship has a reasonable chance of delivering.

The best statement analysis is not the one with the biggest claimed savings.

It is the one that still makes sense after everyone checks the math.