Common Billing Errors on Merchant Statements: How to Find, Verify, and Correct Them

Merchant processing statements can contain dozens of rates, transaction categories, network charges, monthly fees, adjustments, credits, and abbreviations. Even experienced business owners and accounting teams can have trouble determining why a particular charge appeared or why processing costs changed from one month to the next.

Some of the common billing errors on merchant statements include duplicate fees, incorrect processor rates, inaccurate transaction counts, missing credits, misapplied pricing, equipment charges that should have stopped, and unexplained differences between the merchant agreement and the statement. Yet an unfamiliar or higher-than-expected charge is not automatically an error.

Interchange fees can change because customers used different cards. Network fees can change. Refunds and chargebacks can alter settlement totals. A legitimate processor pricing change may increase costs, and some fees may appear a billing cycle after the activity that caused them.

That distinction matters. Before disputing merchant processing billing errors, businesses should compare the statement with their processing agreement, transaction records, settlement reports, prior statements, and any notices or account amendments.

A systematic merchant statement audit makes that process much easier. Instead of asking only, “Why is my bill higher?” businesses can identify exactly which rate, fee, transaction count, adjustment, or settlement amount changed and determine whether the change is justified.

What Is a Merchant Processing Statement?

A merchant processing statement is a periodic record of payment activity and processing charges associated with a merchant account. Depending on the provider and pricing model, it may be called a payment processing statement, merchant account statement, merchant services statement, credit card processing statement, or simply a processing statement.

Statements vary substantially among processors. One provider may separate interchange fees, card network fees, and processor markup into dozens of line items, while another may combine much of the same activity into one or two blended charges. 

That is why comparisons should focus on what each line item represents rather than expecting every statement to use identical terminology.

A typical merchant processing statement can include:

• Gross processing volume
• Number of transactions
• Card sales
• Refund activity
• Chargebacks and reversals
• Interchange categories
• Assessment fees and other card network fees
• Processor percentage markup
• Per-transaction charges
• Authorization fees
• Batch fees
• Gateway fees
• Monthly merchant fees
• PCI-related fees
• Equipment or software charges
• Other adjustments
• Deposits or settlement information
• Merchant and account information

Interchange, network costs, and processor pricing are especially important to distinguish. Card-processing charges are not one single fee. 

As Visa’s educational material explains, interchange reimbursement is part of the transfer between financial institutions, while the merchant’s overall processing cost can include additional acquiring and processing services. 

Merchants reviewing current network costs should therefore use current official information rather than assuming a historic rate still applies.

For a more detailed breakdown of typical statement sections, see this guide to reading a merchant processing statement.

How Processing Charges Appear on Statements

The presentation of processing charges depends heavily on the pricing model. Under interchange-plus pricing, a statement may separately show interchange, assessments, processor percentage markup, and processor per-item charges. Under flat-rate or blended pricing, several of those costs may be combined into a single transaction rate.

Tiered pricing may instead categorize transactions as qualified, mid-qualified, non-qualified, or similar provider-defined groups. Subscription and membership arrangements can add fixed monthly pricing to transaction-level costs.

Some processors deduct fees from daily deposits. Others deposit gross settlement amounts and collect processing fees later, often through a monthly debit. This difference can make two businesses with identical sales activity appear to have very different bank reconciliation patterns.

The important question is not whether a statement looks simple or complex. It is whether the merchant can connect each meaningful charge to transaction activity, a published network cost, or an agreed pricing term.

For additional background on interchange, assessments, processor markup, transaction charges, gateway costs, and other merchant fees, review credit card processing fees explained.

Why Merchant Statement Billing Errors and Discrepancies Happen

Merchant statement discrepancies have many possible causes, and only some are genuine payment processor billing errors. 

Processing systems combine transaction data, authorization records, gateway activity, settlement files, network classifications, pricing tables, account settings, and manual account changes. An error or timing difference anywhere in that chain can affect what ultimately appears on a statement.

A simple data-entry problem can assign an incorrect processor markup. An account migration can retain an obsolete fee. A gateway can continue billing after a merchant changes ecommerce platforms. A terminal can remain listed as rented after it has been returned. A pricing configuration can fail to match the signed agreement.

Other discrepancies have legitimate explanations. For example, authorization attempts may outnumber settled sales because declined authorizations, voids, or repeated attempts are counted. Deposits can differ from POS sales because refunds, chargebacks, reserves, adjustments, fee deductions, or settlement timing affect funding.

Common causes include:

• Account setup or data-entry mistakes
• Incorrect pricing configuration
• Duplicate billing records
• Incorrect merchant profile information
• Gateway or software integration issues
• Merchant account migrations
• Timing differences between authorization and settlement
• Delayed billing from an earlier period
• Manual account adjustments
• Merchant category configuration
• Contract misunderstandings
• Pricing amendments
• Card-network changes
• Refund and chargeback activity
• Changes in card mix or transaction method

The safest approach is therefore evidence-first: identify the disputed charge, determine what created it, compare it with applicable transaction records and contractual terms, and only then decide whether correction is warranted.

Errors, Pricing Changes, and Timing Differences Are Not the Same

A genuine billing error occurs when the amount charged does not match the amount that should have been charged under the applicable agreement, network rules, transaction activity, or account configuration. Examples include charging a $15 monthly fee twice when only one fee applies or continuing an equipment rental after an acknowledged return date.

A processor pricing change is different. A provider may change its markup or introduce a fee when permitted by the merchant agreement and applicable requirements. Whether the merchant likes the increase does not determine whether it is a billing mistake. The review should focus on the agreement, notices, effective date, and actual calculation.

Network changes are another category. Visa, Mastercard, debit networks, and other payment organizations maintain fee and qualification structures that can change. Official Visa and Mastercard resources publish interchange information merchants and acquiring partners can use when examining transaction classifications.

Timing creates still another category. A fee appearing this month may relate to prior-period activity, while a refund or chargeback may be reflected after the original transaction. Statement periods, settlement dates, and bank posting dates do not always align.

Common Billing Errors on Merchant Statements

The most useful way to investigate merchant statement errors is to separate them by type. Percentage-rate problems require a different verification method from transaction-count discrepancies, gateway charges, PCI-related fees, or equipment billing.

The following issues are among the most important areas to investigate during a merchant fee audit. They are potential errors, not automatic proof that a processor billed incorrectly.

Duplicate Fees and Duplicate Transaction Charges

Duplicate processing fees occur when the same account-level or transaction-related fee is charged more than once without a legitimate reason. A merchant might see two identical gateway monthly fees, two statement charges, duplicate PCI-related fees, or two equipment rentals for the same device.

Start by comparing the fee description, amount, billing date, service period, and account or device identifier. Similar-looking fees are not necessarily duplicates. One may belong to the processor while another belongs to a third-party gateway, POS provider, or software platform.

Duplicate customer transactions are a different problem. If a customer’s $80 purchase was processed twice, the merchant may have two actual sales transactions rather than one processor fee billed twice. Verify the transaction IDs, authorization codes, timestamps, batch records, and customer receipt before classifying the issue.

If two identical merchant fees truly relate to the same service and period, document both statement lines and request clarification or a credit.

Incorrect Processing Rates and Processor Markup

Incorrect processing fees can occur when the processor-controlled rate on a statement differs from the pricing stated in the merchant agreement. For example, an interchange-plus agreement might specify a processor markup of 0.30% plus $0.10 per transaction, while statement calculations consistently apply a different markup.

Do not compare the agreement’s processor markup directly with the statement’s total effective rate. Interchange, assessments, transaction mix, monthly charges, gateway costs, and other fees can make total processing expense much higher than the markup alone.

Locate the pricing schedule and determine whether the relevant contractual rate is:

• A percentage markup
• A per-transaction amount
• A flat transaction rate
• A tiered rate
• A subscription fee
• A combination of several components

Then isolate that specific component on the merchant processing statement.

Under interchange-plus pricing, processor markup is usually easier to separate from underlying card costs. Under flat or tiered pricing, it may be incorporated into broader rates, so verification may require transaction-level reports or clarification from the provider.

Incorrect Per-Transaction Fees and Transaction Counts

Per-transaction errors can become expensive for merchants with large transaction volumes. If the agreement says each transaction costs $0.10 and the statement applies $0.15, the difference may be small on one sale but significant across thousands of transactions.

First confirm exactly what activity is billable. “Transaction” does not always mean completed sale.

Depending on the agreement and processing setup, separate charges may apply to:

• Authorization attempts
• Approved sales
• Declined authorization attempts
• Captures
• Refunds
• Verification requests
• Recurring transactions
• Gateway transactions

This explains why statement transaction counts may exceed POS sales counts.

Suppose a store completed 1,000 sales but had 40 declined card attempts and several retried authorizations. An authorization-fee section might legitimately show more than 1,000 items even though sales reports contain only 1,000 completed purchases.

Reconcile counts by activity type before treating them as incorrect transaction fees.

Incorrect Monthly, Gateway, Batch, and Authorization Fees

Monthly merchant fees can include account charges, statement fees, platform costs, minimums, reporting services, support charges, gateway access, software subscriptions, and other recurring services.

An unexpected fee deserves investigation when it is new, larger than usual, duplicated, or inconsistent with the merchant agreement. However, a charge that was disclosed in the original fee schedule but overlooked is not the same as an erroneous charge.

Gateway billing deserves separate attention because online merchants may have multiple vendors. A gateway fee could come through the processor, the gateway company, an ecommerce platform, or an integrated software provider.

Batch fees should be checked against the number of settlement batches. A location configured to close one batch each day should not automatically be assumed to have exactly 30 billable batches in every month. Multiple terminals, manual closures, failed batches, or additional settlement events may affect the count.

Authorization fees similarly require comparison with authorization attempts rather than completed sales alone. Some agreements charge for declined authorization requests as well as approvals.

Missing Refund Credits and Refund-Related Discrepancies

A refund does not always reverse every processing cost associated with the original sale. Providers differ in how they handle the original processor fee, interchange adjustments, network charges, and separate refund fees.

That means a merchant should not assume that refunding a $100 transaction will automatically produce a credit equal to every fee originally paid on that transaction.

When a refund appears incorrect, compare:

• Original transaction amount
• Refund amount
• Refund date
• Refund transaction identifier
• Statement period
• Settlement report
• Processor refund policy
• Contract pricing
• Any fee retained or separately charged

Also account for timing. A refund issued near the end of a billing cycle may appear on a subsequent processing statement or bank settlement.

A real missing-credit problem exists when the provider’s records or applicable terms indicate that a credit should have been applied but it was not.

Unexpected Interchange Categories and Interchange Downgrades

Seeing a higher interchange category does not automatically indicate credit card processing billing errors. Interchange can vary based on card product, transaction method, merchant category, data submitted, settlement timing, and other qualification criteria.

A transaction may cost more when it is keyed instead of properly captured through an applicable card-present method, when required transaction data is incomplete, or when settlement conditions are not met. Commercial transactions can also depend on whether enhanced data was provided.

Visa and Mastercard publish extensive interchange information, and their categories can change. Businesses verifying exact current network rates should use Visa’s official interchange and fee resources or Mastercard’s current published schedules rather than relying on an old statement or third-party rate sheet.

A downgrade may therefore indicate a transaction-processing or qualification problem rather than a billing error. The appropriate response may be to improve transaction data or settlement practices rather than demand a statement credit.

Incorrect Card Network Fees and Assessments

Card network fees, sometimes labeled assessments, dues, brand fees, access charges, or similar terms, are different from processor markup. The processor may pass these costs through, bundle them, or incorporate them into its pricing model.

When a network fee appears suspicious, determine whether the amount is truly presented as a network cost or whether the processor has used a similar label for a provider-controlled fee.

Verification can be difficult because network pricing includes multiple categories and may be updated periodically. Exact comparisons should use current official documentation and the transaction’s network, card product, route, and qualification status.

Debit transactions require particular care. Regulation II contains federal standards affecting interchange for certain debit transactions and includes exemptions for categories such as qualifying small issuers. The Federal Reserve provides current explanatory resources on these debit-card interchange and routing rules.

The practical lesson is that “network fee” should not be treated as either automatically correct or automatically negotiable. Verify its source first.

PCI-Related Billing Errors

Merchant services statements may contain PCI compliance program fees, security-program charges, PCI non-compliance fees, or related account charges. Provider terminology varies.

Potential PCI-related billing errors include a duplicated fee, a non-compliance charge continuing after the merchant completed the required validation and the provider recognized it, or a program charge that does not match the merchant agreement.

Paying a PCI-related fee does not by itself make a business PCI compliant. PCI DSS compliance involves security responsibilities and validation requirements appropriate to the merchant’s payment environment. 

The PCI Security Standards Council merchant resources explain that merchant environments and validation responsibilities vary depending on how payment card data is handled.

If a non-compliance fee appears unexpectedly, verify the merchant’s current validation status, the provider’s records, any outstanding requirements, and the contract provisions governing that charge.

Chargeback Fees and Other Dispute Charges

A chargeback can create more than one statement entry, which frequently causes confusion during payment processing reconciliation. The merchant may see the disputed transaction amount removed and a separate chargeback or dispute-processing fee.

Those are not the same charge.

Later, a representment or reversal can create another adjustment if the dispute outcome changes. The timing may extend across multiple statement periods.

Possible chargeback billing errors include an identical fee duplicated for one dispute, a fee applied to an account contrary to the agreed schedule, or an adjustment that does not match the processor’s dispute records. But the presence of both a chargeback amount and a chargeback fee normally does not establish duplicate billing.

Match every suspicious entry to a case or dispute identifier where available. Review the original transaction, disputed amount, separate processing fee, representment activity, reversal, and later account adjustments before calculating the final financial impact.

Equipment, Software, and Early Termination Fee Errors

Equipment billing can be overlooked because terminal rentals, POS subscriptions, leases, replacement plans, and software licenses may appear outside the primary transaction-fee section.

Common problems include paying twice for one terminal, being charged after a documented return, continuing to pay for inactive software, or being billed an equipment amount that differs from the signed terms.

Equipment leases deserve particular attention because the equipment provider and payment processor may be different entities. Returning a terminal to one company does not necessarily terminate a separate lease agreement.

Early termination fees also require careful contractual review. Determine the cancellation date, contract term, renewal provisions, required notice, and specific termination language.

If an early termination charge conflicts with the applicable agreement or documented cancellation arrangement, preserve copies of the cancellation request, return tracking, acknowledgment emails, statement page, and contract provision before disputing it.

Monthly Minimum and Pricing-Model Errors

A monthly minimum usually does not mean a merchant must process a minimum dollar amount of sales. In many arrangements it means the merchant must generate a specified minimum amount of eligible processing charges, with the provider billing the shortfall if the threshold is not reached.

The exact calculation depends on the agreement.

For example, if the contract requires $25 in qualifying processing charges and only $18 of eligible charges accrued, a $7 minimum shortfall might be valid. The mistake would be comparing the $25 requirement directly with monthly sales volume without examining how the contract defines the minimum.

Another serious configuration issue occurs when the wrong pricing model is applied. A merchant expecting interchange-plus pricing might discover tiered or blended charges on the statement.

Check the signed pricing schedule, not merely a sales quote or verbal description. Confirm how interchange, processor markup, and per-transaction pricing are supposed to appear. A consistent mismatch between the executed agreement and actual billing warrants documented review.

Incorrect Merchant Category or Debit/Credit Classification

A merchant category code, or MCC, identifies the type of business accepting a payment. Merchant classification can influence network rules, eligibility for certain interchange programs, risk treatment, and other payment-processing considerations.

If a business believes its MCC is wrong, it should request confirmation rather than infer the code solely from processing costs. The appropriate category depends on the merchant’s actual business activity and applicable network definitions.

Debit and credit classification also deserves careful review. PIN debit, signature or network-routed debit, regulated debit, exempt debit, and credit products can have different cost structures.

The Federal Reserve’s Regulation II materials illustrate why a single assumption about “the debit rate” can be misleading: different transactions and issuer categories can be subject to different treatment.

An unusual cost can therefore result from legitimate routing or card-product differences. Investigate the transaction details before calling it a merchant account billing error.

Merchant Statement Billing Error Table

A billing-error table helps turn a confusing statement into an investigation checklist. Rather than treating every unfamiliar item as an overcharge, classify the issue, identify the records needed to verify it, and determine the appropriate next action.

Possible Issue	What It May Look Like	How to Verify It	Next Step
Duplicate fee	Same monthly or service charge appears twice	Compare names, amounts, dates, account IDs, and services	Ask which service each fee covers; request credit if truly duplicated
Incorrect rate	Processor-controlled rate differs from agreement	Compare pricing schedule with statement calculation	Document expected and actual rates
Unexpected monthly fee	New statement, platform, support, or account fee	Review agreement and amendments	Request explanation and effective date
Incorrect transaction count	Statement count exceeds POS sales	Compare sales, authorizations, declines, refunds, and voids	Reconcile by transaction type
Missing refund credit	Expected refund adjustment does not appear	Check refund policy, settlement report, and timing	Trace refund ID and request research
Incorrect processor markup	Percentage or per-item markup differs	Separate markup from interchange and assessments	Provide contract pricing to billing support
PCI fee issue	Duplicate or continuing non-compliance charge	Verify validation status and agreement	Correct compliance records or dispute inaccurate billing
Gateway fee issue	Multiple gateway fees or charge for unused service	Check gateway accounts and third-party invoices	Cancel inactive service or dispute duplication
Equipment billing issue	Rental continues after return	Review lease/rental terms and return proof	Submit return documentation
Chargeback discrepancy	Multiple debits related to one dispute	Match case ID, dispute amount, fee, reversal, and dates	Request case-level explanation
Batch fee issue	More batch charges than expected	Compare terminal settlement reports	Identify additional batch closures
Monthly minimum issue	Unexpected minimum shortfall	Recalculate using contract definition	Dispute only if calculation conflicts with terms

The central principle is consistency. If the statement can be traced to transaction records, contract terms, network pricing, or a documented adjustment, the charge may be legitimate even if it is higher than expected.

If the calculation cannot be reconciled or clearly conflicts with the written agreement, the merchant has a much stronger basis for requesting correction.

Billing Error vs. Legitimate Processing Fee

The most important skill in a merchant statement audit is distinguishing billing mistakes from legitimate processing costs.

Interchange fees are underlying transaction costs associated with the payment system and issuing side. The exact amount can vary with card product, transaction method, merchant category, qualification, and other factors.

Assessment and card network fees are network-related charges. They are separate from processor markup, although some statement formats bundle the components.

Processor markup is provider-level pricing above applicable underlying costs. Depending on the pricing arrangement, this may include percentage markup, per-transaction fees, monthly account fees, gateway charges, service fees, or other provider costs.

Contract fees may include monthly minimums, equipment charges, PCI program costs, chargeback fees, statement fees, software subscriptions, and early termination provisions.

A billing error occurs when the amount actually billed does not match what should apply based on the agreement, account configuration, transaction records, or relevant fee structure.

That means an unexpected merchant fee can be valid. A disclosed but forgotten annual fee, for instance, may be unpleasant without being incorrect. Likewise, legitimate interchange changes should not automatically be characterized as “hidden processing fees.”

Rate Increase vs. Billing Error

When the effective cost rises unexpectedly, determine who changed the cost.

Start with the processor-controlled markup. Compare the current statement with prior statements and the current agreement. If the percentage or per-transaction markup changed, determine the effective date and whether the provider issued a pricing notice or account amendment.

Next examine card mix and transaction methods. More rewards, commercial, card-not-present, or otherwise differently classified transactions can change underlying costs without the processor changing its markup.

Then review monthly fees, chargebacks, refunds, gateway costs, PCI-related charges, equipment fees, and transaction volume.

Network changes should be verified using current source material. Visa provides official information explaining interchange and processing-fee concepts, while Mastercard publishes region-specific interchange resources.

The key distinction is measurable: if the processor applied a charge different from the applicable agreed pricing, investigate a potential billing error. If the underlying transaction mix or valid pricing terms changed, the higher total may be legitimate.

Hidden Fees vs. Merchant Statement Errors

“Hidden fee” is often used loosely to describe any charge a merchant did not expect. For statement auditing, it helps to be more precise.

A fee disclosed in the signed contract or subsequent valid account amendment but overlooked by the merchant is different from a fee charged contrary to those terms. The first is primarily a contract-review issue; the second may be a billing discrepancy.

A genuinely unclear line item still deserves investigation. Ask the processor what service the fee represents, whether it is processor-controlled or network-related, when it became effective, and where the applicable charge is documented.

Also check whether the same service is being billed elsewhere. Gateway products, POS software, hardware leases, fraud tools, and ecommerce services can involve third-party billing outside the merchant services statement.

Avoid relying only on fee names. Terms such as “service fee,” “network access,” “compliance,” or “platform fee” may mean different things among providers.

Documentation determines whether the charge is legitimate, not whether its label sounds unfamiliar.

How to Read, Compare, and Audit a Merchant Statement

A merchant statement audit should follow the same sequence every month. Consistency makes abnormalities easier to identify and reduces the risk of overlooking small recurring charges.

A good review combines the payment processing statement, merchant agreement, POS or ecommerce reports, settlement reports, refund records, chargeback information, and business bank deposits.

For a reusable monthly review framework, this merchant statement audit checklist provides additional guidance on tracking statement activity over time.

How to Read a Merchant Statement Step by Step

1. Identify the statement period. Confirm the beginning and ending dates before comparing the statement with sales records.
2. Confirm account information. Review merchant number, business location, processing platform, and other identifying details.
3. Review sales volume. Compare reported card sales with POS, ecommerce, or accounting reports for the same processing period.
4. Verify transaction counts. Separate sales from authorizations, declines, refunds, voids, and other activity.
5. Review refunds and chargebacks. Confirm amounts, dates, and transaction or dispute references.
6. Identify interchange. If itemized, review interchange categories and transaction volume assigned to each category.
7. Identify network fees. Separate assessment or network-related charges from processor markup where possible.
8. Locate processor markup. Find the processor’s percentage and per-transaction pricing.
9. Review recurring fees. Check gateway, PCI-related, account, software, equipment, statement, and other monthly charges.
10. Review adjustments. Investigate credits, reversals, miscellaneous debits, and delayed charges.
11. Compare settlement with deposits. Trace batches and funding into the business bank account.
12. Compare everything with the agreement. Verify percentage rates, transaction fees, fixed charges, and special terms against current contractual documents.

How to Compare the Statement With Your Contract

The merchant agreement is the reference point for processor-controlled charges. Start with the pricing schedule and any amendments made after the original account opening.

Look for:

• Percentage markup
• Per-transaction fees
• Flat or tiered rates
• Monthly account fees
• Monthly minimum provisions
• Gateway fees
• PCI-related charges
• Batch and authorization fees
• Equipment purchase, rental, or lease terms
• Chargeback fees
• Refund pricing
• Software charges
• Termination provisions

Do not assume the original proposal contains every binding term. Review the executed agreement and applicable schedules, amendments, or documented account modifications.

Create a simple comparison with four fields: statement fee, actual amount, contractual amount, and difference. If a fee is formula-based, show the calculation.

For network pass-through expenses, processor contracts may not state one fixed dollar amount because network costs can change. In that case, determine whether the processor is passing through the applicable network amount as agreed or adding a provider-controlled markup that needs separate verification.

This method turns vague processing fee discrepancies into testable billing questions.

How to Calculate Your Effective Processing Rate

The effective processing rate measures total processing fees as a percentage of card sales.

Effective Processing Rate = Total Processing Fees ÷ Total Card Sales × 100

Suppose a merchant processes $60,000 in card sales and incurs $1,920 in total applicable processing fees.

$1,920 ÷ $60,000 × 100 = 3.20%

The effective rate can be useful for identifying changes in total processing cost, but it does not tell you why the change occurred.

A rising effective rate may reflect:

• More card-not-present transactions
• Different card mix
• Lower sales volume relative to fixed fees
• More small-ticket transactions
• New monthly fees
• Higher chargeback activity
• Refund-related costs
• Pricing changes
• Interchange downgrades
• A genuine billing problem

If the effective rate moves significantly, investigate the components before assuming overcharged processing fees.

For a deeper explanation of the calculation and its limitations, see how to calculate your effective processing rate.

Comparing Statements Month Over Month

Month-over-month comparison is one of the fastest ways to detect merchant statement discrepancies because it shows exactly what changed.

Create a recurring worksheet containing:

• Processing volume
• Transaction count
• Average ticket
• Refund volume
• Chargeback activity
• Interchange expense
• Network fees
• Processor percentage charges
• Per-item charges
• Monthly fixed fees
• Gateway and software fees
• Equipment charges
• Effective processing rate

Do not compare two months solely by total fees. If sales increased from $30,000 to $50,000, total fees should usually rise even when pricing remains unchanged.

Likewise, a slower month can produce a higher effective rate because monthly account fees represent a larger percentage of lower sales volume.

Look for line items that appear for the first time, disappear unexpectedly, change amount without obvious activity, or duplicate another line. If the processor markup rises while underlying interchange and network categories remain comparable, investigate the pricing change.

A consistent comparison process makes small merchant statement mistakes visible before they recur for many billing cycles.

Merchant Statement Reconciliation, Refunds, and Deposits

Statement review is only one part of payment processing reconciliation. A statement can be internally accurate while bank deposits still appear different from daily sales because settlement follows its own timing and adjustment rules.

A strong reconciliation follows the transaction from the business system all the way to the bank:

POS or online sales → batch totals → settlement reports → processor statement → bank deposits

Each stage answers a different question. Sales reports show what the merchant recorded. Batch reports show what was submitted for settlement. Processor reports show how transactions were processed and adjusted. Bank records show what was actually funded.

Why Merchant Deposits May Not Match Sales

A merchant deposit does not always equal the gross sales total for a particular calendar day.

Common reasons include:

• Processing fees deducted before funding
• Refunds
• Chargebacks
• Split batches
• Multiple locations or merchant IDs
• Settlement cutoffs
• Weekend or holiday timing
• Reserves or holds
• Prior-period adjustments
• Reversals
• Funding delays

Suppose a restaurant records $8,000 in Saturday card sales but its processor’s settlement cutoff places late-night transactions in Sunday’s batch. The resulting bank deposit may not match Saturday’s POS total even though no money is missing.

Similarly, a processor using net settlement may deduct refunds or fees before depositing funds. Another processor may fund gross sales and debit fees separately.

Reconciliation should therefore match specific batch and settlement identifiers whenever possible rather than trying to force every bank deposit to equal one calendar day’s sales.

A mismatch becomes a stronger billing concern when transaction-level and settlement records indicate that a particular funded amount should have arrived but did not.

Refunds and Chargebacks Can Create Statement Discrepancies

Refunds affect gross volume, net processing volume, settlement, and merchant deposits. Depending on processor policy, they can also affect transaction fees and the treatment of costs associated with the original sale.

A refund issued during one statement period may settle in the next. That timing difference can make monthly reports appear inconsistent even when both records are correct.

Chargebacks create another layer. A disputed sale amount may be removed from merchant funding, while a separate chargeback fee is assessed. If the merchant later prevails in the dispute, a reversal or adjustment may restore some funds in a later period.

For each chargeback, track:

1. Original transaction.
2. Dispute case number.
3. Chargeback amount.
4. Separate chargeback fee.
5. Representment submission.
6. Reversal or outcome.
7. Final settlement adjustment.

This creates an audit trail that distinguishes actual duplicate billing from multiple legitimate entries associated with the same dispute.

How to Document and Dispute Merchant Statement Billing Errors

Once a merchant has evidence that a statement charge may be incorrect, the next step is a focused billing inquiry. Strong disputes identify a specific fee, the amount actually billed, the amount expected, and the records supporting the difference.

Avoid beginning with a broad accusation that the processor is overcharging. A precise request gives billing staff enough information to trace account configuration, pricing history, settlement records, or individual transactions.

How to Document a Suspected Billing Error

Create a record for each suspected discrepancy containing:

• Statement date and billing period
• Merchant account or location
• Exact fee name
• Amount charged
• Number of affected items
• Transaction, batch, or dispute reference
• Expected fee or rate
• Difference between expected and actual billing
• Applicable contract provision
• Pricing schedule or amendment
• Relevant statement page
• Transaction or settlement report
• Screenshots when useful
• Prior correspondence
• Date the issue was discovered

If the problem spans several months, calculate the difference separately for each billing period. That makes it easier to verify the requested credit.

For a rate discrepancy, include the calculation. For example, show the agreement’s markup, relevant processing volume, expected fee, actual fee, and resulting difference.

For equipment or account cancellation issues, preserve return tracking, cancellation confirmation, device serial numbers, and effective dates.

Good documentation protects both sides from misunderstandings and allows the processor to answer the specific billing question.

How to Dispute a Merchant Statement Billing Error

Use a structured process:

1. Confirm the charge. Make sure the fee is not a legitimate network cost, separate service, delayed adjustment, or other transaction type.
2. Review contract terms. Locate the rate or provision that establishes the expected charge.
3. Gather records. Collect statement pages, transaction details, settlement reports, pricing documents, and correspondence.
4. Contact billing support. Use the support channel specified for the merchant account.
5. Identify the exact fee. Provide the line-item description, amount, date, and account information.
6. Request an explanation in writing. Ask what generated the fee and what pricing provision applies.
7. Request correction or credit when supported. State the amount you believe should be corrected and why.
8. Retain correspondence. Keep ticket numbers, emails, letters, and names or departments involved.
9. Verify later statements. Confirm the adjustment appeared and that the underlying configuration was corrected.

Merchant agreements can impose notice requirements or dispute deadlines. There is no single universal deadline appropriate for every merchant account, so review the applicable agreement and raise suspected errors promptly.

What If the Processor Does Not Correct the Error?

If the initial billing inquiry does not resolve a documented discrepancy, request escalation through the processor’s formal account or billing review process.

A merchant can:

• Request supervisor or account-management review
• Resubmit the issue with a concise calculation
• Provide the specific contract language
• Ask for the reason for denying the requested correction
• Follow any formal dispute procedure stated in the merchant agreement
• Preserve all correspondence and supporting records
• Continue monitoring future statements

If a material contractual dispute remains unresolved, the business may consider seeking appropriate professional advice based on its circumstances. That is particularly important when termination provisions, significant historical billing, separate equipment agreements, or legal rights are involved.

This article provides general educational information and does not replace individualized legal, accounting, tax, or financial advice.

Preventing Future Merchant Statement Errors

The easiest billing problem to correct is the one identified during its first billing cycle. Businesses that review statements consistently are less likely to discover months of duplicate charges, forgotten subscriptions, incorrect processor rates, or lingering equipment fees.

Statement monitoring should be a normal accounting control rather than something done only after processing expenses become noticeably high.

Recommended practices include:

• Review every merchant services statement monthly
• Keep signed processing agreements accessible
• Save pricing amendments and notices
• Document negotiated pricing
• Reconcile settlement deposits
• Monitor effective processing rate
• Compare fee categories month over month
• Track refunds and chargebacks
• Maintain accurate business and account information
• Review gateway and software subscriptions
• Verify equipment charges
• Record account changes in writing
• Investigate new line items promptly

A payment-processing relationship can evolve over time. Locations open or close, software changes, gateways are added, devices are replaced, transaction channels shift, and pricing may be amended. Keeping internal records current is therefore as important as examining the statement itself.

Common Merchant Statement Review Mistakes

One common mistake is looking only at the total monthly processing fee. A total tells you what was charged, but not why. Volume changes, transaction counts, fixed fees, and card mix all influence the number.

Another mistake is comparing effective rates between very different months without context. A seasonal business may process far less volume during one month while still paying the same fixed monthly charges.

Other common review problems include:

• Ignoring transaction counts
• Confusing interchange with processor markup
• Assuming every new fee is incorrect
• Failing to check contract terms
• Ignoring small recurring charges
• Overlooking refunds
• Treating chargeback fees as duplicate chargeback amounts
• Failing to reconcile bank deposits
• Comparing calendar-day sales directly with settlement deposits
• Waiting several statement cycles before asking questions

A merchant statement audit is most effective when the business identifies both unusual charges and legitimate operational reasons for cost changes.

Statement Issues by Business Type

Retail businesses should pay particular attention to terminal charges, POS software fees, batch activity, card-present classifications, duplicate customer transactions, and equipment billing. Keyed transactions that replace normal chip or contactless acceptance may also warrant review because transaction characteristics can affect cost.

Restaurants should account for tips, post-authorization adjustments, closing procedures, batch settlement, POS subscriptions, and authorization counts. A transaction count that appears high may reflect payment workflow rather than duplicate charges.

Ecommerce businesses commonly need to review gateway fees, card-not-present pricing, fraud-management tools, recurring billing services, refunds, authorization attempts, and chargebacks. Separate third-party gateway billing can make duplicate-service costs harder to spot.

B2B businesses should examine commercial card activity, transaction classification, and enhanced transaction data where applicable. Missing qualifying information can sometimes increase processing costs without creating a statement billing error.

The correct audit method therefore depends partly on how the business accepts payments.

Questions to Ask Your Payment Processor

When a line item cannot be reconciled internally, focused questions produce better answers than simply asking why processing is expensive.

Useful questions include:

• What does this fee represent?
• Is this charge listed in my current agreement?
• Is this interchange, a card network fee, or processor markup?
• What transaction activity generated this fee?
• When did this rate become effective?
• What was the previous rate?
• Was an account or pricing notice issued?
• Why does this fee appear twice?
• Are these charges for different services?
• How is my transaction count calculated?
• Are declined authorizations included?
• Why did my effective processing rate increase?
• How are refunds handled under my account pricing?
• Are original transaction fees returned after a refund?
• What caused this interchange category or downgrade?
• Which merchant category code is assigned to the account?
• Can you provide the current detailed fee schedule?
• Can you provide transaction-level reporting?
• How was this monthly minimum calculated?
• Will a confirmed incorrect fee be credited?
• If corrected, when will the account configuration change?

Request supporting information when the answer involves a rate, transaction category, or contract provision.

Frequently Asked Questions

Conclusion

Common billing errors on merchant statements can include duplicate fees, incorrect processor rates, inaccurate per-transaction charges, wrong transaction counts, missing credits, incorrect monthly minimum calculations, equipment billing problems, and pricing that does not match the merchant agreement.

But unusual charges should not automatically be labeled merchant statement billing errors. Interchange fees, card network assessments, processor markup, refunds, chargebacks, delayed adjustments, transaction qualification, pricing changes, and contractually disclosed fees can all produce legitimate differences.

The most reliable approach is to compare the payment processing statement with the current merchant agreement, transaction-level records, settlement reports, prior statements, and bank deposits. Calculating the effective processing rate can highlight unusual changes, while month-over-month comparisons help isolate which cost component actually moved.

Regular payment processing reconciliation also makes it easier to distinguish missing funds from settlement timing and to separate duplicate processor fees from legitimate transaction activity.

When a genuine discrepancy is found, document it carefully. Record the exact fee, actual amount, expected amount, applicable contract provision, transaction or batch references, and supporting records before contacting billing support.

A consistent monthly merchant statement audit gives businesses something more useful than a general impression that processing costs are high: it provides the evidence needed to understand each charge, identify inaccurate billing promptly, and verify that corrections remain in place.