Merchant statement audits help business owners understand what they actually pay to accept card payments. A merchant statement can look like a mix of sales totals, deposits, adjustments, card types, processing fees, chargebacks, and technical fee descriptions.
Without regular review, it is easy to miss billing changes, reconciliation issues, rising fees, or deposit differences that affect cash flow.
A merchant statement audit is the process of reviewing a merchant processing statement line by line to confirm sales activity, deposits, refunds, chargebacks, reserves, monthly charges, and total payment processing fees.
It helps merchants move beyond simply checking whether money reached the bank account. The goal is to understand how gross sales became net deposits and whether the fees charged match expectations.
This guide explains merchant statement audits in a practical way for retail stores, restaurants, ecommerce sellers, service businesses, finance teams, bookkeepers, and new merchants.
You will learn how to read a merchant statement, calculate effective rate, review interchange fees, identify processor markup, match deposits to bank records, and spot red flags that may need follow-up.
For related background, readers may also find it helpful to review guides on credit card processing fees, how to read a merchant processing statement, and interchange-plus pricing alongside this audit process.
What Are Merchant Statement Audits?
Merchant statement audits are structured reviews of merchant processing statements. They help a business confirm what happened during a billing period, including card sales, refunds, chargebacks, adjustments, reserves, batch settlements, deposits, and merchant services fees.
A merchant statement audit is not only about finding mistakes. It is also about understanding payment performance. A business may discover that card-not-present transactions are increasing, gateway fees are higher than expected, chargebacks are affecting deposits, or effective processing rate has moved upward over time.
A merchant processing statement audit usually starts with the monthly statement. The reviewer checks the account summary, processing volume, transaction count, funding summary, fee section, interchange detail, assessment fees, processor markup, and any monthly account fees.
Then the statement is compared with bank deposits, POS reports, ecommerce reports, gateway reports, refund records, and accounting entries.
For example, a restaurant might process $80,000 in gross card sales during a month but receive lower net deposits because refunds, chargebacks, batch fees, monthly fees, and processing fees were deducted. A merchant statement audit explains the difference.
Why Merchant Statement Audits Matter
Merchant statement audits matter because card processing costs can affect margins, cash flow, pricing, and accounting accuracy. Many businesses review revenue daily but only glance at their merchant services statement once a month, if at all. That creates room for missed fee changes, unexplained deductions, and reconciliation problems.
A payment processing statement audit gives merchants better visibility into payment processing fees. It helps show how much was paid in interchange fees, assessment fees, processor markup, transaction fees, authorization fees, batch fees, monthly fees, gateway fees, PCI compliance fees, chargeback fees, statement fees, retrieval fees, and other account charges.
Audits also support better bookkeeping. If bank deposits do not match POS sales, the difference may be caused by refunds, chargebacks, settlement timing, daily batching, net funding, reserve deductions, or month-end cutoffs. Without reviewing the merchant account statement, bookkeepers may post incorrect sales, fees, or receivables.
Merchant statement audits also help businesses compare contract terms with actual billing. If the agreement listed one markup but the statement shows additional monthly fees or a changed discount rate, the merchant can ask questions with specific details.
Regular audits can also highlight cost-saving opportunities. A business may find that keyed transactions are more expensive than card-present transactions, that outdated equipment is causing downgrades, or that a high number of small transactions makes per-transaction fees more important than the percentage rate.
What a Merchant Processing Statement Usually Includes
A merchant processing statement usually includes several sections, though every provider formats statements differently.
Most statements include an account summary, processing summary, sales volume, transaction count, funding summary, batch summary, deposit activity, fee summary, interchange detail, assessment fees, refunds, chargebacks, adjustments, reserves, and monthly service fees.
The account summary provides the starting point. It may show gross sales, credits, chargebacks, net sales, number of transactions, average ticket size, and total fees. This section helps you see the big picture, but it should not be the only section reviewed.
The processing summary may break activity into card-present transactions, card-not-present transactions, ecommerce payments, POS payments, keyed payments, debit transactions, credit transactions, rewards cards, business cards, and other card categories. These details matter because transaction type and card mix can affect processing cost.
The funding summary shows deposits and deductions. It may list batch settlement dates, deposit dates, batch totals, net deposits, refunds, chargebacks, reserves, and adjustments. Some processors deduct fees daily, while others deduct fees monthly. This affects how deposits appear in the bank.
The fee section may include discount rate charges, transaction fees, authorization fees, batch fees, gateway fees, monthly fees, PCI compliance fees, statement fees, chargeback fees, retrieval fees, and processor markup. In some pricing models, interchange and assessment fees appear clearly. In others, they are bundled.
Account Summary and Processing Overview
The account summary and processing overview are useful starting points for a merchant statement review. This section often shows total processing volume, refund volume, chargeback volume, transaction count, average ticket size, total fees, and sometimes the effective rate.
However, the summary is only a snapshot. A merchant statement analysis should go deeper because the summary may hide important details. For example, total fees may include both card network costs and provider-controlled charges. Refunds may appear as separate deductions. Chargebacks may appear in the funding section rather than the fee section.
Average ticket size is also important. A business with a low average ticket may pay more in transaction fees relative to sales volume because per-transaction charges add up quickly. A business with a higher average ticket may be more affected by percentage-based fees.
Use the account summary to identify the main numbers, then verify them against the detailed sections. The summary tells you where to begin. The full statement tells you what changed and why.
Funding Summary and Deposits
The funding summary shows how processed card sales turned into deposits. It may include batch settlement totals, deposit dates, funding dates, net deposits, deductions, reserves, refunds, chargebacks, and adjustments.
Deposit amounts may not match gross card sales exactly. A merchant may process $5,000 in card sales on Monday but receive a lower deposit because fees were deducted, refunds were processed, a chargeback was withdrawn, or a reserve was held. Timing also matters. A batch closed late at night may fund on a different date than the sale date.
Some processors use gross funding, where deposits are closer to gross batch totals and fees are deducted later. Others use net funding, where fees are deducted before deposit. This difference is one of the first things to understand during a merchant account statement audit.
Documents Needed for a Merchant Statement Audit
A useful merchant statement audit requires more than the monthly merchant statement. The statement is the main document, but it should be compared with other records that show sales, deposits, refunds, chargebacks, and fees.
Start with the merchant processing statement for the period being reviewed. Then gather the bank account activity for the same period, including deposits from the payment processor. If possible, export the deposit activity into a spreadsheet so you can sort by date and amount.
Next, collect POS reports, ecommerce platform reports, payment gateway reports, and virtual terminal reports. These reports help verify processing volume, transaction count, card-present transactions, card-not-present transactions, ecommerce payments, refunds, voids, and batch activity.
You should also gather refund records, chargeback notices, retrieval notices, reserve notices, adjustment details, and settlement reports. These documents explain why deposits may differ from gross sales.
Finally, review the processing contract, pricing schedule, fee schedule, prior-month merchant services statements, and any notices of fee changes. Comparing the current statement against earlier statements helps identify new line items or rate changes.
A bookkeeper or finance team may also need accounting software entries, sales tax reports, daily closeout reports, and monthly revenue summaries. The more complete the record set, the easier it is to separate normal settlement activity from possible billing issues.
Step-by-Step Merchant Statement Audit Process
A merchant statement audit works best when done in a consistent order. Start by confirming the statement period. Make sure the beginning and ending dates match the month or billing cycle you are reviewing. Some statements use calendar months, while others use processor billing cycles.
Next, review the total processing volume. Compare the merchant statement with POS, ecommerce, gateway, and accounting reports. Then check transaction count and average ticket size. Sudden changes may show a real business shift, a reporting issue, or a change in transaction mix.
After that, compare deposits with bank records. Match batch settlement totals to bank deposits while accounting for fees, refunds, chargebacks, reserves, adjustments, and funding delays. This step is especially important for reconciliation.
Then identify total fees. Review payment processing fees by category, including discount rate, transaction fees, authorization fees, batch fees, monthly fees, gateway fees, PCI compliance fees, statement fees, chargeback fees, retrieval fees, interchange fees, assessment fees, and processor markup.
Calculate effective processing rate by dividing total processing fees by total processing volume, then multiplying by 100. Compare the result with prior months.
Finally, check new or changed fees, review PCI-related charges, verify gateway and equipment fees, compare the current statement with earlier statements, and document questions for the provider, accountant, or advisor.
Merchant Statement Audit Checklist Table
| Audit Step | What to Review | Why It Matters | Red Flag to Watch For |
| Confirm statement period | Beginning and ending dates | Prevents comparing the wrong records | Statement dates do not match accounting period |
| Review processing volume | Gross sales, net sales, card volume | Confirms sales activity | Statement volume differs from POS reports |
| Review transaction count | Number of payments and credits | Helps explain transaction fees | Count changes sharply without business reason |
| Check average ticket size | Volume divided by transaction count | Shows sales mix changes | Average ticket drops suddenly |
| Match deposits | Funding summary and bank records | Supports reconciliation | Deposits missing or delayed |
| Review refunds | Refund totals and dates | Explains lower deposits | Refunds not reflected in sales records |
| Review chargebacks | Disputes, retrievals, reversals | Shows risk and cash flow impact | Chargebacks rising month over month |
| Identify total fees | All processing and monthly charges | Shows real acceptance cost | New fees appear without explanation |
| Calculate effective rate | Fees ÷ volume × 100 | Tracks total cost trend | Effective rate increases suddenly |
| Review PCI fees | Compliance and non-compliance charges | Avoids unnecessary recurring costs | Unexpected non-compliance fee |
| Compare prior months | Volume, fees, deposits, card mix | Finds trends and changes | Rate or fee increase without notice |
This table can be used as a repeatable monthly framework. It is especially helpful for bookkeepers, finance teams, and owners who want a consistent review process instead of reacting only when a deposit looks wrong.
How to Verify Processing Volume
Processing volume is one of the most important numbers in a merchant statement audit. It represents the dollar amount of card transactions processed during the statement period.
Depending on the statement format, volume may be shown as gross sales, net sales, credit volume, debit volume, card-present volume, card-not-present volume, ecommerce volume, or total processing volume.
To verify processing volume, compare the merchant statement with POS reports, ecommerce reports, gateway reports, and accounting records.
Do not rely on one system only. A POS report may show sales by order date, while the processor statement may show transactions by settlement date. Ecommerce platforms may include orders that were authorized but not yet captured.
Gross sales usually represent card sales before refunds and chargebacks. Net sales may subtract refunds, credits, and disputes. Adjustments and reserves may also affect the final funded amount.
Separating card-present transactions from card-not-present transactions can reveal cost patterns. In-person EMV and contactless payments often price differently than keyed, invoice, recurring billing, or ecommerce payments. If card-not-present volume increases, total fees may rise even if total sales stay flat.
How to Review Transaction Count and Average Ticket Size
Transaction count shows how many card transactions were processed during the billing period. Average ticket size is usually calculated by dividing total processing volume by transaction count. These numbers help explain why fees may change even when sales volume looks stable.
Per-transaction fees matter more for small-ticket businesses. A coffee shop, quick-service restaurant, convenience store, or small retail shop may have many low-dollar transactions. Even a modest authorization fee or transaction fee can increase the effective rate when the average ticket is low.
Higher-ticket businesses may be less affected by per-transaction fees but more affected by percentage-based fees. A service provider processing fewer large invoices may focus more on discount rate, interchange qualification, card type, and processor markup.
Sudden changes in transaction count deserve attention. If transaction count rises while sales volume stays flat, average ticket size has likely dropped. If the average ticket increases sharply, the business may have processed larger orders, fewer small purchases, or a different sales mix.
During a merchant statement review, compare transaction count and average ticket size with prior months. Also compare POS payments, ecommerce payments, card-present transactions, and card-not-present transactions separately when the statement allows it.
How to Match Deposits to Bank Records
Matching deposits to bank records is one of the most practical parts of a payment processing statement audit. The goal is to confirm that processed sales were funded correctly and that deductions are understood.
Start with the funding summary on the merchant statement. Review batch settlement dates, batch totals, deposit amounts, and deductions. Then compare those amounts with bank account deposits from the processor.
Do not expect every deposit to match daily gross sales. Deposits may be reduced by refunds, chargebacks, reserves, adjustments, monthly fees, batch fees, or daily fee deductions. Settlement timing can also create differences. A weekend batch may fund on the next business day. A late batch may appear in the next funding cycle.
If deposits are net funded, fees may be deducted before money reaches the bank. If deposits are gross funded, fees may be withdrawn separately later in the month. Both methods are common, but they require different reconciliation steps.
If a deposit does not match, look for offsetting activity. A refund, chargeback, reserve hold, or adjustment may explain the difference. If no explanation appears on the statement, document the batch date, expected amount, actual deposit, and variance before contacting the provider.
Gross Sales vs Net Deposits
Gross sales and net deposits are not the same. Gross sales generally represent the total card sales processed before deductions. Net deposits represent the amount that actually reaches the bank after certain items are subtracted or adjusted.
Several items can reduce the amount deposited. Refunds return money to customers. Chargebacks remove funds during a dispute. Processing fees may be deducted daily or monthly. Reserves may hold back part of sales volume for risk management. Adjustments may correct prior funding errors or account for special activity.
For example, assume a merchant processes $20,000 in gross card sales. During the same period, the merchant issues $1,000 in refunds, has a $500 chargeback, and pays $600 in processing fees. If fees and disputes are deducted before funding, the net deposit total may be closer to $17,900 before considering timing differences.
This is why reconciliation should not use bank deposits as the only sales source. Bank deposits show cash received, not necessarily total processed sales. Accounting records should separate sales, refunds, chargebacks, processing fees, and deposits.
How to Audit Payment Processing Fees
Auditing payment processing fees means reviewing both the total fee amount and the individual fee categories. A credit card processing statement audit should identify percentage-based fees, per-transaction fees, recurring account fees, and one-time charges.
Percentage-based fees may appear as a discount rate, qualified rate, non-qualified rate, interchange charge, assessment fee, or processor markup. Per-transaction fees may appear as authorization fees, transaction fees, item fees, or network access fees.
Monthly fees may include account fees, statement fees, gateway fees, PCI compliance fees, security fees, minimum fees, reporting fees, software fees, terminal fees, or service fees. Some of these may be expected under the agreement, while others may require clarification.
Chargeback fees, retrieval fees, batch fees, and adjustment fees may appear only when specific activity occurs. For example, chargeback fees may be charged when a customer disputes a transaction. Retrieval fees may appear when documentation is requested.
A merchant services statement audit should separate unavoidable pass-through costs from provider-controlled markup when possible. This is easier on interchange-plus statements because interchange, assessments, and markup may be itemized. It can be harder on tiered or flat-rate statements because costs may be bundled.
Common Merchant Statement Fees Table
| Fee Type | What It Means | Why It May Appear | Audit Question to Ask |
| Interchange fees | Card-issuing bank-related transaction costs | Card type, method, risk, and data affect category | Are interchange categories changing? |
| Assessment fees | Card network-related fees | Network participation and transaction activity | Are assessments itemized or bundled? |
| Processor markup | Provider-added pricing | Percentage markup, transaction markup, or monthly fee | Which fees are provider-controlled? |
| Discount rate | Percentage charged on volume | May include bundled costs or markup | What is included in this rate? |
| Transaction fees | Per-item charge | Charged for each transaction or authorization | How much do small tickets cost? |
| Authorization fees | Cost per approval attempt | Applies when transactions are authorized | Are failed or declined attempts billed? |
| Batch fees | Fee for batch settlement | May apply when daily batches close | Is this charged daily or per batch? |
| Gateway fees | Online payment technology fee | Ecommerce, virtual terminal, or recurring billing | Is the gateway still being used? |
| PCI compliance fees | Security-related account fee | Compliance program or validation support | Is compliance status current? |
| PCI non-compliance fees | Fee for missing validation | May appear if annual steps are incomplete | What must be completed to remove it? |
| Chargeback fees | Dispute-related fee | Customer dispute or reversal activity | Are disputes increasing? |
| Statement fees | Monthly statement or reporting fee | Paper or account reporting charge | Can electronic delivery reduce it? |
| Retrieval fees | Documentation request fee | Cardholder or issuer asks for transaction proof | Are receipts and invoices stored? |
This table gives merchants a practical way to interpret line items without assuming every fee is wrong. The audit question is often the most important part because it turns a confusing line item into a specific follow-up.
How to Calculate Effective Rate During a Statement Audit
Effective rate shows the total cost of card acceptance as a percentage of processing volume. It is one of the most useful numbers in merchant statement audits because it combines many fee types into one easy-to-track figure.
The formula is:
Effective rate = Total processing fees ÷ Total processing volume × 100
For example, if a business processed $50,000 in card payments and paid $1,650 in total processing fees, the calculation would be:
$1,650 ÷ $50,000 × 100 = 3.30%
This means the effective processing rate for that period was 3.30%. The number includes more than the advertised rate. It reflects transaction fees, discount fees, monthly fees, gateway fees, PCI fees, batch fees, chargeback fees, assessment fees, interchange fees, and processor markup if they are included in the total fee amount.
Effective rate is best used as a trend. A single month may be higher because of chargebacks, annual fees, seasonal transaction mix, lower volume, or more card-not-present activity. If the effective rate rises for several months, it is worth reviewing fee changes, card mix, pricing model, refunds, chargebacks, and account charges.
How to Audit Interchange Fees
Interchange fees are a major part of many credit card processing statements. They are connected to card type, transaction method, merchant category, authorization quality, settlement data, and risk characteristics. Published interchange resources from card networks can help merchants understand why different transaction categories may carry different costs.
During a merchant statement audit, review the interchange detail if it is available. Look for categories tied to card-present transactions, card-not-present transactions, rewards cards, business cards, debit cards, ecommerce payments, keyed transactions, recurring billing, and manually entered payments.
A change in interchange fees may not always mean the provider changed pricing. It may mean customers used different card types, more transactions were keyed, more ecommerce orders were processed, more rewards cards were used, or transaction data was incomplete.
Data quality can matter. Missing address verification, delayed settlement, manual entry, incorrect transaction data, or failing to use available security tools may affect qualification in some environments. Ecommerce merchants should pay attention to AVS, CVV, tokenization, fraud filters, and proper authorization and capture practices.
How to Audit Assessment Fees
Assessment fees are different from interchange fees. Interchange fees are associated with the issuing side of the card transaction, while assessment fees are connected to card network rules and network-level charges. On some statements, assessment fees appear separately. On others, they are bundled into a broader discount rate or fee category.
Assessment fees may appear under names such as dues, assessments, network fees, access fees, brand fees, or card association fees. The exact wording depends on the processor and statement format.
During a merchant services statement audit, identify whether assessment fees are itemized or bundled. If they are itemized, compare them with processing volume and prior statements. If they are bundled, ask whether the provider can clarify which portion of the total rate relates to assessments.
Assessment fees are usually less flexible than processor markup, but they still matter during an audit because they help explain total cost. If assessments rise, the reason may be a change in card mix, network fees, cross-border transactions, card-not-present volume, or reporting format.
Do not confuse assessment fees with monthly account fees. Assessment fees are generally tied to transaction activity. Monthly account fees are recurring charges from the provider or platform.
How to Audit Processor Markup
Processor markup is the portion of payment processing cost added by the provider or payment platform. It may appear as a percentage markup, per-transaction markup, monthly fee, gateway fee, statement fee, PCI-related fee, minimum fee, software fee, equipment charge, or bundled rate.
Identifying processor markup is important because it is often the most controllable part of the statement. Interchange and assessment fees may be tied to card network and issuing bank structures, but provider markup may depend on the pricing agreement.
On interchange-plus statements, markup may be easier to find. You may see interchange, assessments, and a separate provider markup such as a basis-point charge plus a per-transaction fee. On tiered, flat-rate, or blended statements, markup may be hidden inside the rate.
During a merchant account statement audit, compare markup-related charges with the processing agreement and fee schedule. Look for new monthly fees, increased transaction fees, changed discount rates, additional gateway costs, or PCI non-compliance fees.
Processor markup is not automatically improper. Providers charge for processing access, support, risk management, reporting, deposits, gateway connections, and service. The audit question is whether the markup is clear, expected, and consistent with the agreement.
Pricing Models and Merchant Statement Audits
Pricing models affect how easy or difficult merchant statement audits are. The most common models include interchange-plus pricing, tiered pricing, flat-rate pricing, subscription pricing, blended pricing, and pass-through pricing.
Interchange-plus pricing usually separates interchange fees, assessment fees, and processor markup. This can provide better visibility but may create longer statements with many line items. It is often useful for merchants who want to understand cost components.
Tiered pricing groups transactions into categories such as qualified, mid-qualified, and non-qualified. The statement may look simpler, but it can be harder to understand why transactions landed in a specific tier or how much markup is included.
Flat-rate pricing charges a simple rate, often with a percentage and per-transaction fee. It can be easier to predict but may not show underlying interchange and assessments. That makes a detailed merchant statement analysis harder.
Subscription pricing may charge a monthly membership fee plus pass-through costs or lower markup. Blended pricing combines multiple cost elements into one rate. Pass-through pricing may show network and interchange costs more directly.
Auditing Interchange-Plus Statements
Auditing interchange-plus statements usually involves separating three cost layers: interchange, assessments, and markup. The benefit is visibility. Merchants can see which costs are tied to card categories and which costs are provider-controlled.
Start by reviewing total volume and transaction count. Then review interchange detail by card type and transaction method. Look for categories tied to rewards cards, business cards, keyed transactions, ecommerce payments, debit transactions, and card-present payments.
Next, review assessments and network fees. Then identify processor markup, which may appear as a percentage over interchange plus a per-transaction fee. Also review monthly fees, gateway fees, PCI fees, batch fees, and statement fees.
Interchange-plus statements may look complex, but they often give merchants the details needed to calculate effective rate and compare month-to-month changes more accurately.
Auditing Tiered and Flat-Rate Statements
Tiered and flat-rate statements may look simpler, but they can be harder to audit deeply. In tiered pricing, transactions may be grouped into qualified, mid-qualified, and non-qualified categories. Non-qualified transactions are often more expensive, so merchants should review why they appear.
A high number of non-qualified transactions may be related to keyed payments, rewards cards, business cards, card-not-present activity, late settlement, missing data, or transaction type. The statement may not always explain the reason clearly.
Flat-rate statements usually show fewer line items. This can help with predictability, but it may hide the difference between interchange, assessments, and markup. Merchants using flat-rate pricing should still calculate effective rate and compare total fees against volume.
How to Review Refunds, Voids, and Chargebacks
Refunds, voids, chargebacks, retrieval requests, reversals, disputes, and adjustments can all affect deposits and fees. During a merchant statement audit, these items should be reviewed separately from normal sales.
A void usually cancels a transaction before settlement. A refund returns money after the original transaction has been processed. A chargeback occurs when a cardholder disputes a transaction and funds may be withdrawn while the dispute is reviewed.
Chargebacks can affect cash flow because the disputed amount may be deducted from deposits. A chargeback fee may also apply. Retrieval requests may appear when documentation is requested before or during a dispute.
Refunds may also affect processing costs. Some fees may not be returned when a refund is issued. Review the statement and agreement to understand how refunds are handled.
Compare refund and chargeback activity with POS, ecommerce, customer service, and accounting records. If chargebacks are increasing, review product descriptions, refund policies, delivery confirmation, customer communication, fraud controls, and transaction documentation.
How to Audit PCI Compliance Fees
PCI-related fees can appear as PCI compliance fees, PCI program fees, security fees, PCI non-compliance fees, data security fees, or annual compliance charges.
The PCI Security Standards Council provides merchant resources that explain payment data security responsibilities, and merchants should understand which systems and processes may be in scope.
During a merchant services statement audit, identify all PCI-related line items. Then determine whether they are expected monthly or annual fees, or whether they are non-compliance fees. A PCI non-compliance fee may appear if required validation steps were not completed.
Merchants should confirm whether their compliance status is current. This may involve completing a self-assessment questionnaire, scanning requirements, working with a qualified provider, or updating account information. The exact steps depend on the business environment and how cardholder data is handled.
Do not ignore PCI fees because they can recur. A small monthly non-compliance fee can become expensive over a full year. If a fee appears unexpectedly, ask what triggered it, what must be completed, and whether removal will be reflected on the next statement.
This article does not provide compliance advice. Merchants should work with qualified professionals when security or compliance requirements are unclear.
How to Audit Gateway, Equipment, and Software Fees
Gateway, equipment, and software fees are easy to overlook because they may not be tied directly to each transaction. They can appear as recurring monthly charges, technology fees, virtual terminal fees, recurring billing fees, mobile reader fees, terminal rental fees, equipment lease charges, POS software fees, plugin fees, or integration charges.
During a merchant account statement audit, list every technology-related fee. Then ask whether the tool is still active, whether it is required, and whether it matches the agreement. A business may still be paying for an old terminal, unused gateway, duplicate plugin, or inactive virtual terminal.
Ecommerce merchants should review gateway fees, tokenization fees, recurring billing fees, fraud filter fees, and API-related charges. Retail merchants should review terminal fees, POS software fees, contactless payment support, and equipment leases. Service businesses should review invoice payment fees, virtual terminal costs, and recurring billing add-ons.
Technology fees may be reasonable when they support operations, security, reporting, or integrations. The audit goal is to confirm they are expected and useful.
How to Compare Merchant Statements Month to Month
A single merchant statement shows one billing period. A month-to-month comparison shows trends. This is one of the most valuable habits in merchant statement audits.
Compare total processing volume, transaction count, average ticket size, refund volume, chargeback volume, total fees, effective rate, card mix, gateway fees, PCI fees, monthly fees, and deposit timing. If possible, track these numbers in a spreadsheet.
Look for changes that do not match business activity. If sales volume is stable but fees increase, review card mix, pricing changes, new fees, chargebacks, and card-not-present activity. If transaction count rises but volume does not, small-ticket transactions may be increasing.
Seasonality can explain some changes. A retailer may see higher volume during busy shopping periods. A restaurant may see more small-ticket transactions during lunch service. An ecommerce seller may see more card-not-present activity during promotional campaigns.
The goal is not to panic over every change. The goal is to understand the reason. When the reason is unclear, document it and ask for clarification.
Red Flags to Look for During Merchant Statement Audits
Merchant statement audits can reveal red flags that deserve follow-up. These include unexplained new fees, sudden effective rate increases, duplicate charges, unexpected PCI non-compliance fees, rising chargebacks, high non-qualified fees, reserve deductions, changed gateway fees, settlement mismatches, or deposits that do not match bank records.
A sudden effective rate increase is one of the clearest warning signs. It may be caused by a pricing change, a new monthly fee, chargebacks, more expensive card mix, lower volume, or more card-not-present transactions.
High non-qualified fees may suggest transaction downgrades, keyed entries, missing data, or a pricing model that is difficult to evaluate. Unexpected PCI non-compliance fees may indicate that required validation steps are incomplete.
Deposit mismatches should be investigated carefully. They may be caused by timing, net funding, refunds, chargebacks, reserves, or adjustments. But if no explanation appears, the merchant should ask for a batch-level breakdown.
Rising chargebacks are also important because they affect cash flow, fees, and account risk. Review disputes quickly and look for operational causes such as unclear billing descriptors, shipping issues, refund delays, fraud, or customer communication gaps.
Merchant Statement Audit Red Flags Table
| Audit Area | Normal Review Item | Possible Red Flag | Action Step |
| Effective rate | Monthly fee-to-volume percentage | Sudden increase without sales change | Compare fee lines and card mix |
| Deposits | Batch totals and bank deposits | Missing or unexplained variance | Review funding summary and ask for batch detail |
| PCI fees | Compliance-related charges | New non-compliance fee | Confirm required validation steps |
| Gateway fees | Online payment charges | Duplicate or unused gateway fee | Verify active tools and integrations |
| Chargebacks | Dispute volume and fees | Rising disputes | Review dispute reasons and documentation |
| Refunds | Refund totals | Refunds not matching records | Compare POS and gateway reports |
| Monthly fees | Recurring account charges | New or renamed fee | Compare with prior statements |
| Transaction fees | Per-item fees | Higher cost due to low average ticket | Review pricing and ticket-size trend |
| Reserves | Held funds | Unexpected reserve deduction | Request reserve terms and release schedule |
| Card mix | Debit, credit, rewards, business cards | More expensive card categories rising | Review transaction methods and data quality |
This table can be used as a quick monthly red flag scan before doing a deeper review.
How to Reconcile Merchant Statements With Accounting Records
Reconciliation connects the merchant statement, bank records, POS reports, ecommerce orders, refund records, chargebacks, batches, settlement dates, and accounting software entries. It helps ensure that revenue, fees, and deposits are recorded correctly.
Start with gross card sales from the POS, ecommerce platform, or gateway. Then subtract refunds, voids, and chargebacks where appropriate. Next, compare settlement batches with the funding summary. Finally, match deposits to the bank account.
Record payment processing fees separately. If fees are deducted from deposits, the bank deposit will be lower than gross sales. If fees are billed monthly, there may be a separate withdrawal or statement deduction.
Use clearing accounts when needed. A clearing account can hold card sales temporarily until deposits and fees are matched. This is helpful when settlement timing crosses month-end.
Bookkeepers should also review month-end cutoffs. Sales on the last day of a month may fund in the next month. Without proper timing adjustments, revenue and deposits may look mismatched.
Reconciliation is not just an accounting task. It helps identify missing deposits, duplicate refunds, unrecorded chargebacks, fee changes, and reporting gaps.
Card-Present vs Card-Not-Present Audit Considerations
Card-present and card-not-present transactions often have different costs and risk profiles. Card-present payments include in-person EMV chip, contactless, tap, and swipe transactions. Card-not-present payments include ecommerce payments, keyed payments, invoice payments, virtual terminal transactions, recurring billing, and many mobile or remote payments.
During a merchant statement audit, review how much volume comes from each channel. A shift from POS payments to ecommerce payments may increase costs because card-not-present transactions can carry higher risk and different interchange categories.
Security tools also matter. Card-present payments may use EMV and contactless technology. Ecommerce payments may use address verification, CVV, tokenization, fraud filters, and secure checkout tools. Virtual terminal payments may require careful data entry and documentation.
Chargeback risk may also differ by channel. Card-not-present transactions can be more vulnerable to fraud or customer disputes if shipping, refund policies, billing descriptors, or transaction records are unclear.
A merchant statement review should not only ask, “What did we pay?” It should also ask, “Which transaction types are driving cost and risk?”
Common Mistakes Merchants Make During Statement Audits
Merchants often make statement audit mistakes because statements are dense and time-consuming. One common mistake is reviewing only bank deposits. Deposits matter, but they do not show total sales, fee categories, refunds, chargebacks, or card mix.
Another mistake is ignoring small recurring fees. A monthly statement fee, gateway fee, PCI fee, reporting fee, or software add-on may seem small but can add up over time. Small fees also matter when margins are tight.
Some merchants do not calculate effective rate. Without effective rate, it is difficult to compare total cost month to month. Others confuse gross sales with net deposits, which can create bookkeeping errors.
Merchants may also skip chargeback review. Chargebacks can reduce deposits, create fees, and signal operational or fraud problems. PCI-related fees are another area that many businesses ignore until non-compliance charges repeat.
Finally, some merchants misunderstand pricing models. A low advertised rate may not reflect total cost if other fees are added.
Fee Review Mistakes
Fee review mistakes usually happen when merchants focus only on the largest line item. A discount rate may look reasonable, but transaction fees, gateway fees, PCI fees, batch fees, statement fees, and monthly fees can still raise the effective processing rate.
Another common mistake is misunderstanding transaction-level costs. A business with many small payments may be heavily affected by per-transaction fees even if the percentage rate looks low.
Some merchants overlook new line items because the fee name looks technical. Others assume all fees are fixed and cannot be questioned. While not every fee is negotiable or removable, each fee should be understood.
A good merchant statement audit asks what the fee is, why it appeared, whether it matches the agreement, and whether it changed from prior months.
Reconciliation Mistakes
Reconciliation mistakes often come from timing differences. Sales date, batch date, settlement date, and bank posting date may not be the same. If the reviewer does not account for these differences, normal funding activity may look like an error.
Another mistake is treating refunds and chargebacks as ordinary sales reductions without tracking them separately. Refunds, disputes, and adjustments should be visible in accounting records.
Reserves can also create confusion. If a processor holds funds, deposits may be lower than expected even though the sales were processed. The reserve terms and release schedule should be documented.
Using bank deposits as the only sales source is risky. Deposits show what was received after deductions and timing differences, not necessarily what customers paid.
Questions to Ask During a Merchant Services Statement Audit
A strong merchant services statement audit turns confusion into specific questions. Useful questions include:
- What is my total processing volume for this statement period?
- What is my total fee amount?
- What is my effective processing rate?
- Which fees are interchange fees?
- Which fees are assessment fees?
- Which fees are processor markup?
- Are there new fees this month?
- Did chargebacks increase?
- Are refunds matching internal records?
- Are deposits matching bank records?
- Are PCI compliance fees or PCI non-compliance fees appearing?
- Are gateway or equipment fees expected?
- Did my pricing model change?
- Are card-present and card-not-present transactions separated?
- Did average ticket size change?
- Are reserves or adjustments affecting funding?
Document these questions before contacting the provider, accountant, or advisor. Include statement dates, line-item names, fee amounts, batch numbers, and deposit differences. Specific questions usually get better answers than general complaints.
Merchant Statement Audit Checklist
Use this checklist for a monthly merchant statement audit:
- Statement period confirmed.
- Total processing volume reviewed.
- Gross sales and net sales compared.
- Transaction count reviewed.
- Average ticket checked.
- Card-present transactions reviewed.
- Card-not-present transactions reviewed.
- Ecommerce payments reviewed.
- POS payments reviewed.
- Refunds reviewed.
- Voids reviewed.
- Chargebacks reviewed.
- Retrieval fees reviewed.
- Deposits matched to bank records.
- Batch settlement dates checked.
- Funding summary reviewed.
- Reserve deductions checked.
- Adjustments reviewed.
- Total fees identified.
- Effective rate calculated.
- Interchange fees reviewed.
- Assessment fees reviewed.
- Processor markup reviewed.
- Discount rate reviewed.
- Transaction fees reviewed.
- Authorization fees reviewed.
- Batch fees reviewed.
- Monthly fees reviewed.
- Gateway fees checked.
- PCI compliance fees checked.
- Equipment fees checked.
- Statement fees checked.
- New fees reviewed.
- Prior month comparison completed.
- Questions documented.
- Statement saved for records.
This checklist can be adapted for different business types. A restaurant may focus heavily on POS payments, batch settlement, tips, and chargebacks. An ecommerce business may focus more on gateway fees, fraud tools, card-not-present costs, refunds, and dispute documentation.
When to Get Help With Merchant Statement Audits
Some merchants can complete a basic merchant statement audit internally. Others may benefit from help from an accountant, bookkeeper, financial advisor, payment consultant, or knowledgeable payment professional.
Help may be useful when statements are complex, fee descriptions are unclear, processing volume is high, chargebacks are frequent, pricing has changed, deposits do not reconcile, or the merchant services agreement is difficult to understand.
A business may also need help if it operates multiple locations, uses several gateways, processes ecommerce and in-person payments, manages recurring billing, or has reserves and adjustments. Multi-channel payment activity can make reconciliation more complicated.
Professional help may also be useful before renegotiating pricing, changing providers, or reviewing a merchant services contract. A detailed audit can help the merchant understand current costs before making decisions.
This guide is educational and should not replace legal, tax, accounting, security, or financial advice. When the issue involves contract terms, taxes, compliance, or accounting treatment, consult a qualified professional.
Best Practices for Ongoing Merchant Statement Audits
The best merchant statement audits are consistent. Review statements every month, not only when something looks wrong. Monthly review helps identify fee changes early and prevents small issues from becoming long-term problems.
Save historical statements, processing contracts, fee schedules, gateway reports, chargeback notices, refund records, and settlement reports. Keeping documents organized makes trend analysis easier.
Calculate effective rate regularly. Compare it with prior months and investigate unexplained changes. Track processing volume, transaction count, average ticket size, total fees, refunds, chargebacks, and deposits in a spreadsheet.
Monitor PCI status and confirm whether compliance-related fees are expected. Review gateway, equipment, and software charges regularly to avoid paying for unused tools.
Reconcile deposits with bank records and accounting software. Ask for written explanations when fees are unclear. Keep a record of provider responses, billing corrections, and pricing updates.
Frequently Asked Questions
What are merchant statement audits?
Merchant statement audits are reviews of merchant processing statements to verify sales activity, deposits, refunds, chargebacks, adjustments, reserves, and payment processing fees. The goal is to understand how card sales turned into bank deposits and whether fees match expectations.
A merchant statement audit can also reveal cost trends, billing changes, reconciliation issues, and possible savings opportunities. It is useful for business owners, bookkeepers, ecommerce sellers, restaurants, retailers, and service providers.
What is a merchant processing statement audit?
A merchant processing statement audit is a detailed review of a merchant processing statement for a specific billing period. It usually includes checking processing volume, transaction count, average ticket size, funding summary, deposit activity, refunds, chargebacks, fees, and pricing details.
The audit may also compare the statement with POS reports, ecommerce reports, gateway reports, bank deposits, refund records, chargeback notices, and the merchant agreement.
How do merchants audit processing statements?
Merchants audit processing statements by following a repeatable process. First, confirm the statement period. Then review total processing volume, transaction count, average ticket size, refunds, chargebacks, funding activity, and total fees.
Next, match deposits to bank records, calculate effective rate, compare fees with prior statements, review PCI and gateway charges, and document questions for the provider or accountant.
What should I check on a merchant services statement?
Check sales volume, transaction count, average ticket size, refunds, chargebacks, batch settlements, net deposits, total fees, interchange fees, assessment fees, processor markup, gateway fees, PCI fees, monthly fees, equipment charges, and new line items.
You should also compare the statement with bank deposits and internal sales reports. This helps confirm whether deposits and deductions make sense.
How do I calculate effective rate during a statement audit?
Calculate effective rate by dividing total processing fees by total processing volume, then multiplying by 100.
For example, if total processing fees are $900 and total card volume is $30,000, the effective rate is 3.00%. This number helps compare total payment acceptance cost from month to month.
Why does my bank deposit not match my sales total?
Your bank deposit may not match your sales total because deposits can be reduced by refunds, chargebacks, processing fees, reserves, adjustments, or prior-period corrections. Timing can also create differences because sales dates, batch dates, settlement dates, and bank posting dates may not match.
Review the funding summary and batch settlement details before assuming there is an error.
What fees should I look for on a merchant statement?
Look for discount rate charges, transaction fees, authorization fees, batch fees, monthly fees, gateway fees, PCI compliance fees, PCI non-compliance fees, statement fees, chargeback fees, retrieval fees, interchange fees, assessment fees, equipment fees, and processor markup.
Also look for new, renamed, or duplicate fees compared with prior statements.
What are interchange fees on a merchant statement?
Interchange fees are transaction-related costs connected to the issuing side of card payments. They can vary based on card type, transaction method, card-present or card-not-present status, rewards card usage, debit or credit type, merchant category, and transaction data quality.
On some statements, interchange fees are itemized. On others, they may be bundled into a broader rate.
What are assessment fees?
Assessment fees are card network-related fees. They are different from interchange fees and may appear as dues, assessments, network fees, access fees, or card brand fees.
Depending on the statement format, assessment fees may be listed separately or bundled into the overall processing rate.
What is processor markup?
Processor markup is the provider-controlled portion of processing cost. It may appear as a percentage markup, per-transaction fee, monthly fee, gateway fee, statement fee, PCI-related fee, software fee, or bundled charge.
Identifying processor markup helps merchants understand which costs may be negotiable or provider-specific.
How often should merchants audit statements?
Merchants should review statements monthly. A monthly merchant statement review helps identify fee changes, deposit issues, chargeback increases, PCI fees, and cost trends before they become long-term problems.
Businesses with high volume, multiple locations, ecommerce sales, or frequent disputes may need a more detailed review.
What should I do if I find an error on my statement?
Document the issue first. Save the statement, line-item name, fee amount, batch date, deposit amount, and any comparison records from the bank, POS, gateway, or accounting system.
Then contact the provider, accountant, or advisor with a specific question. Ask for a written explanation or correction when appropriate. Keep the response with your audit records for future reference.
Conclusion
Merchant statement audits are one of the most useful habits a merchant can build. They help verify sales, deposits, refunds, chargebacks, reserves, adjustments, payment processing fees, effective rate, and statement changes.
A good audit explains how gross sales become net deposits. It also helps separate interchange fees, assessment fees, processor markup, monthly fees, gateway fees, PCI fees, and chargeback fees. This gives merchants a clearer view of total payment acceptance cost.
Review statements consistently, compare trends, reconcile deposits, save records, and ask questions about unusual fees. Over time, merchant statement audits can improve cash flow visibility, accounting accuracy, fee awareness, and payment decision-making.
Leave a Reply