Understanding Monthly Merchant Statements

Monthly merchant statements are one of the most useful financial documents a business receives, yet they are also one of the most commonly ignored. Many owners glance at deposits, check that card sales were funded, and move on. That habit can leave billing errors, fee increases, chargebacks, reserve deductions, and avoidable costs unnoticed for months.

A merchant statement is more than a receipt from your payment processor. It is a detailed record of card payment activity for a billing cycle. 

It can show gross sales, refunds, chargebacks, deposits, adjustments, processing volume, transaction counts, card types, pricing categories, merchant account fees, and the total cost of accepting card payments.

Understanding monthly merchant statements helps businesses make better decisions about cash flow, reconciliation, pricing, accounting, and payment operations. 

Whether a business accepts ecommerce payments, POS payments, mobile payments, keyed transactions, recurring billing, or invoices, the statement is the place where many costs and funding details become visible.

This guide explains how to read a merchant processing statement, what common fees mean, how deposits and deductions appear, how to calculate effective rate, and how to identify billing issues or cost-saving opportunities. 

The goal is to help business owners, finance teams, ecommerce sellers, service providers, and anyone accepting card payments review statements with more confidence.

What Are Monthly Merchant Statements?

Monthly merchant statements are billing and activity reports issued by a payment processor, merchant services provider, acquiring bank, or related payment partner. They summarize card processing activity for a specific billing period. 

A statement usually includes sales volume, refunds, chargebacks, transaction counts, deposits, processing fees, monthly charges, adjustments, and other account activity.

A merchant statement may also be called a merchant account statement, merchant processing statement, merchant services statement, credit card processing statement, payment processing statement, merchant billing statement, or merchant account billing report. 

The format varies by provider, but the purpose is similar: to show what happened in the merchant account and what it cost to process payments.

This statement is different from a bank statement. A bank statement shows money moving in and out of a deposit account. A merchant statement explains the payment activity behind many of those deposits. 

For example, a bank statement may show a deposit of a certain amount, while the merchant services statement may explain that the deposit came from several card batches after refunds, chargebacks, processing fees, reserve deductions, or adjustments were applied.

It is also different from a POS report or ecommerce sales report. A sales report usually focuses on customer purchases, products, taxes, tips, discounts, and order totals. 

A merchant account statement focuses on payment processing activity. It may show how card networks, issuing banks, acquiring banks, and the payment processor handled those card transactions.

For businesses that accept cards every day, monthly merchant statements are important accounting and operational documents. They help connect sales activity to actual deposits. They also show how credit card processing fees, card brand fees, interchange fees, assessment fees, and processor markup affect net revenue.

Why Merchant Statements Matter for Businesses

Merchant statements matter because they help businesses understand the real cost of accepting card payments. A business may know its sales total, but that does not always show how much money was actually funded after merchant services fees, chargebacks, refunds, reserves, and deductions. Reviewing monthly merchant statements closes that gap.

A payment processing statement can also help a business verify deposits. Card sales do not always deposit as one simple number. 

The final bank deposit may be affected by batch settlement timing, next-day or delayed funding, weekends, holidays, refunds, chargebacks, fees taken daily, fees taken monthly, and reserve activity. Without reviewing the funding summary, a business may mistake a normal timing difference for a missing deposit.

Statements are also useful for detecting billing errors. A new statement fee, unexpected PCI compliance fee, higher gateway fee, duplicate monthly charge, unusual authorization fee, or unexplained adjustment can appear quietly. If no one checks the statement, the business may keep paying that charge.

A merchant statement analysis can reveal whether payment costs are changing. For example, a business may notice that its effective rate increased even though sales volume stayed stable. That could be due to more card-not-present transactions, more rewards cards, a change in pricing model, higher assessment fees, more chargebacks, or additional processor markup.

Reviewing statements also supports better accounting. Finance teams can compare processing volume, deposits, refunds, and chargebacks against POS records, ecommerce reports, invoices, and bank deposits. This makes reconciliation more accurate and reduces confusion at month-end.

Merchant statements are especially important when a business grows, changes sales channels, adds ecommerce payments, begins recurring billing, opens another location, changes equipment, or starts using a new gateway. Each change can affect transaction fees, discount rate, average ticket size, risk profile, and deposit timing.

Key Sections of a Merchant Statement

Most merchant statements include several core sections, though the labels and layout vary. A typical merchant account statement may begin with an account summary, followed by sales activity, deposits, funding summary, card type breakdown, transaction count, fee summary, chargebacks, refunds, adjustments, and monthly service charges.

The account summary gives a quick overview of processing volume, total transactions, net sales, total fees, and deposits. This section is useful for a high-level review, but it rarely tells the whole story. A business should treat it as a starting point, not the full statement analysis.

The deposits or funding summary shows when batches were settled and when funds were sent to the business bank account. This section helps explain why deposits may not match gross sales. For example, the processor may deduct refunds, chargebacks, daily fees, reserves, or adjustments before funding.

The sales summary may break activity into card-present transactions, card-not-present transactions, ecommerce payments, POS payments, mobile payments, keyed transactions, debit cards, credit cards, prepaid cards, corporate cards, and rewards cards. This matters because different transaction types often carry different credit card processing fees.

The fee section may include interchange fees, assessment fees, transaction fees, authorization fees, batch fees, monthly minimum fees, PCI compliance fees, gateway fees, statement fees, chargeback fees, retrieval fees, card brand fees, AVS fees, and other merchant account fees.

Some statements provide detailed interchange categories, especially under interchange-plus pricing. Others use broader pricing buckets, such as qualified, mid-qualified, and non-qualified categories. Flat-rate pricing may show fewer details, while tiered pricing may require extra review to understand how transactions were categorized.

Account Summary and Processing Overview

The account summary and processing overview provide a high-level snapshot of activity during the billing period. This section may show total sales, processing volume, refunds, chargebacks, net volume, transaction count, average ticket size, total discount fees, and total merchant statement fees.

For example, a business might see gross card sales of one amount, refunds of another amount, chargebacks deducted separately, and net sales after those deductions. The statement may also show total fees, which allows the business to begin estimating the effective rate.

This section is useful because it helps owners and finance teams quickly understand whether card sales were higher or lower than expected. It can also show whether refunds or chargebacks were unusual. 

If transaction count increased but total sales stayed flat, average ticket size may have dropped. If sales stayed stable but fees increased, the business may need to look deeper into card mix, pricing categories, or new monthly charges.

However, the account summary should not be the only section reviewed. It may combine several costs into one line. It may not explain whether fees came from interchange, assessments, processor markup, monthly charges, or chargebacks. It may also hide important details about deposits and batch settlement.

Deposit and Funding Summary

The deposit and funding summary explains how card sales turned into bank deposits. This section may show batch settlement dates, funding dates, batch totals, deductions, reserve activity, adjustments, and net deposits. It is one of the most important parts of a merchant processing statement for reconciliation.

A batch is a group of approved transactions submitted for settlement. Many POS systems and gateways close batches automatically at the end of the business day. Some businesses close batches manually. Once a batch is settled, the payment processor and acquiring bank begin the funding process.

The amount deposited into the bank account may not match gross sales exactly. There are several reasons for this. Refunds may be deducted from a later deposit. Chargebacks may reduce funding. 

Fees may be deducted daily instead of monthly. Reserves may hold back a percentage of sales. Adjustments may correct previous funding activity. Timing differences may also occur when batches settle after a cutoff time.

For ecommerce sellers and service providers, the funding summary is especially useful because online orders, refunds, subscriptions, and chargebacks may occur across different days. The business may receive one deposit for multiple order dates, or one order date may be split across several funding dates.

To reconcile deposits properly, compare the funding summary with POS reports, gateway reports, ecommerce reports, and bank records. Focus on batch totals, net deposits, refund activity, chargebacks, and any deductions listed near the funding detail.

How to Read a Monthly Merchant Statement Step by Step

Reading monthly merchant statements becomes easier when you follow a consistent process. Start with the account summary, then move through deposits, sales activity, fees, chargebacks, adjustments, and effective rate. 

The goal is not just to confirm that sales happened. The goal is to understand how sales became deposits and what costs were deducted along the way.

First, review gross processing volume. This is the total amount of card transactions before deductions. Compare it with POS reports, ecommerce reports, invoice records, or accounting software. Small timing differences may be normal, but large unexplained differences should be investigated.

Next, review refunds. Refunds reduce net sales and may also affect fees. Some providers refund certain processing charges while others do not. If refunds are high, look for operational causes such as product returns, duplicate orders, customer cancellations, service disputes, or billing errors.

Then review chargebacks. Chargebacks can reduce deposits and add chargeback fees. A chargeback may also create extra administrative work and increase risk monitoring. Look at both the number of chargebacks and the dollar amount.

Next, review batch settlement and deposits. Match batches to bank deposits. Check whether fees are deducted daily or monthly. If fees are deducted daily, each deposit may be net of some processing costs. If fees are deducted monthly, deposits may look closer to gross sales until the monthly billing deduction occurs.

After deposits, review the fee summary. Separate transaction-based costs from monthly account fees. Look for discount rate, transaction fees, authorization fees, interchange fees, assessment fees, processor markup, gateway fees, PCI compliance fees, batch fees, statement fees, monthly minimum fees, and card brand fees.

Finally, calculate the effective rate. Divide total processing fees by total processing volume. This gives a broad view of overall processing cost. If the rate is higher than expected, look at transaction mix, average ticket size, card-not-present activity, non-qualified fees, chargebacks, and monthly charges.

A simple review process may look like this:

• Confirm gross processing volume.
• Compare refunds and chargebacks to sales records.
• Match batches and funding dates to bank deposits.
• Review all recurring monthly fees.
• Separate interchange, assessments, and processor markup where possible.
• Calculate effective rate.
• Compare the statement with prior months.
• Note any new, unclear, or increased charges.

Common Fees Found on Merchant Statements

Merchant statement fees can appear under many names. Some are transaction-based, some are percentage-based, and others are fixed monthly charges. Understanding these fees helps businesses identify what is normal, what needs clarification, and what may be avoidable.

Transaction fees are usually charged per transaction. They may appear as per-item fees, authorization fees, capture fees, or transaction charges. Authorization fees apply when a card is submitted for approval. Even if a transaction is later voided, an authorization cost may still appear depending on the billing setup.

The discount rate is a percentage charged on processing volume. In some pricing models, the discount rate may include several cost components. In other models, it may represent only processor markup above interchange and assessment fees.

Interchange fees are charges associated with card-issuing banks and card network rules. They vary based on card type, transaction type, merchant category, entry method, risk level, and data quality. Assessment fees are card brand fees charged by card networks. These may appear as separate line items or be bundled into broader pricing.

Processor markup is the portion charged by the payment processor or provider above underlying network and issuing-bank costs. It may appear as a percentage, a per-transaction fee, a monthly fee, or a combination.

Batch fees are charged when a business submits a batch for settlement. Statement fees may cover producing or delivering the merchant billing statement. Monthly minimum fees may apply when processing activity does not generate a minimum amount of fees. 

PCI compliance fees may relate to payment security program administration, while PCI non-compliance fees may appear when required validation steps are incomplete.

Gateway fees apply to ecommerce payments, virtual terminal payments, recurring billing, and other online payment tools. These may include monthly gateway charges, per-transaction gateway fees, tokenization fees, or account updater fees.

Chargeback fees are charged when a customer disputes a transaction. Retrieval fees may apply when additional transaction documentation is requested. AVS fees may apply when address verification is used, especially for card-not-present transactions.

Common merchant account fees may include:

• Interchange fees
• Assessment fees
• Processor markup
• Discount rate charges
• Transaction fees
• Authorization fees
• Batch fees
• Gateway fees
• Statement fees
• Monthly minimum fees
• PCI compliance fees
• PCI non-compliance fees
• Chargeback fees
• Retrieval fees
• AVS fees
• Card brand fees
• Equipment or software fees
• Reserve deductions
• Adjustments

Understanding Interchange, Assessments, and Processor Markup

A useful way to understand credit card processing fees is to separate them into three broad layers: interchange, assessments, and processor markup. These categories are not always displayed clearly, but they explain much of what appears on a merchant services statement.

Interchange fees are tied to the card-issuing bank and the card network’s interchange structure. These costs vary by card type and transaction conditions. 

For example, a card-present debit transaction may cost less than a keyed rewards credit card transaction. A business card with incomplete data may cost more than a properly entered transaction with stronger verification.

Assessment fees are charged by card networks. They are usually smaller than interchange fees but still affect the total cost of processing. Assessment fees may include brand usage charges, network access fees, cross-border fees, or other card brand fees. The exact names vary by network and processor.

Processor markup is the amount charged by the payment processor or merchant services provider for processing, support, technology, risk management, reporting, funding, and account administration. 

Markup may appear as a percentage above interchange, a per-transaction fee, a monthly fee, gateway fees, statement fees, or other service charges.

Knowing the difference matters because not all fees are controlled by the same party. A business usually cannot directly negotiate interchange fees or assessment fees. However, processor markup, monthly account fees, gateway fees, equipment fees, and some service fees may be worth reviewing.

This distinction also helps during merchant statement analysis. If the statement shows rising costs, the reason may be a change in card mix rather than a provider-controlled rate increase. 

For example, more corporate cards, rewards cards, keyed payments, or ecommerce payments may increase interchange costs. On the other hand, a new monthly service fee or higher processor markup may require a different conversation.

For more background on interchange-related costs, a business can review educational resources on how interchange fees work and official card-network fee information such as interchange resources.

Pricing Models and How They Appear on Statements

Merchant statements look different depending on the pricing model. The most common models include interchange-plus pricing, tiered pricing, flat-rate pricing, subscription pricing, and blended pricing. Each model affects how fees are displayed and how easy the statement is to review.

Interchange-plus pricing usually separates interchange fees, assessment fees, and processor markup. This can make the merchant processing statement longer, but it often provides more visibility into the underlying cost structure. Businesses that want detailed merchant statement analysis may prefer this format because it shows more of the fee breakdown.

Tiered pricing groups transactions into pricing categories such as qualified, mid-qualified, and non-qualified. The statement may show fewer line items, but it can be harder to understand why certain transactions landed in a higher-cost category. A rewards card, keyed entry, missing data, or card-not-present transaction may be downgraded into a more expensive tier.

Flat-rate pricing charges one simple rate, or a small set of rates, for broad transaction categories. For example, swiped or tapped transactions may have one rate, while keyed or ecommerce payments may have another. This can make billing easier to understand, but it may hide underlying interchange and assessment costs.

Subscription pricing may charge a monthly membership-style fee plus pass-through interchange and a smaller per-transaction markup. Blended pricing combines multiple cost components into one rate. It may be convenient, but it can make it difficult to see which fees are network costs and which are processor markup.

No pricing model is automatically best for every business. The right fit depends on processing volume, average ticket size, transaction count, sales channel, card mix, refund activity, chargeback risk, and the business’s need for transparency.

Interchange-Plus Pricing on Statements

Interchange-plus pricing usually provides the most detailed view of merchant statement fees. Under this model, the statement may show actual interchange categories, card brand assessments, and processor markup separately. The markup is often shown as a percentage plus a per-transaction fee.

For example, a statement may list several interchange categories based on card type, entry method, transaction data, and risk level. It may then list assessment fees and separate processor charges. This structure can make the statement longer, but it gives the business more information to review.

The advantage is transparency. A business can see how much of the cost came from interchange fees, how much came from assessment fees, and how much came from processor markup. This helps when comparing providers or asking questions about fee increases.

The challenge is complexity. Interchange categories can be difficult to interpret without experience. A long list of card types, rates, and transaction counts may feel overwhelming. Still, for businesses with higher processing volume or more complex payment activity, the detail can be valuable.

Tiered and Flat-Rate Pricing on Statements

Tiered pricing and flat-rate pricing can make monthly billing look simpler, but they may also make the underlying cost structure harder to see. In tiered pricing, transactions are grouped into categories. Qualified transactions usually receive the lowest listed rate, while mid-qualified and non-qualified transactions cost more.

A transaction may move into a higher tier for several reasons. It may be keyed instead of dipped or tapped. It may involve a rewards card, business card, international card, missing address verification, late batch settlement, or incomplete transaction data. The statement may show the category but not always explain the reason.

Flat-rate pricing is often easier to read because it may show one rate for card-present transactions and another rate for card-not-present transactions. This can help small or low-volume businesses predict costs. However, it may not reveal how much of the fee is interchange, assessment, or processor markup.

The tradeoff is simplicity versus visibility. A simpler statement may be easier to understand, but a detailed statement may provide better insight into savings opportunities. Businesses should review whether the pricing model matches their transaction patterns.

For a deeper look at simplified pricing structures, this guide to flat-rate credit card processing can help explain how broad pricing models affect payment costs.

How to Calculate Your Effective Rate

Effective rate is a simple way to estimate the overall cost of accepting card payments. It shows total processing fees as a percentage of total processing volume. Businesses use effective rate to compare monthly costs, spot changes, and evaluate whether their payment setup is becoming more expensive.

The formula is:

Effective rate = total processing fees ÷ total processing volume

For example, if a business processes $50,000 in card payments and pays $1,500 in total processing fees, the effective rate is 3%. The calculation is $1,500 divided by $50,000.

This number is useful because it combines multiple costs into one percentage. Instead of trying to review every fee line first, a business can start with the effective rate and then investigate why it changed. 

If the effective rate was 2.7% one month and 3.4% the next, something likely changed in transaction mix, fee structure, chargebacks, refunds, monthly charges, or pricing.

Effective rate should not be the only metric reviewed. It can be affected by average ticket size, transaction count, sales channel, card type, card-present transactions, card-not-present transactions, ecommerce payments, chargebacks, gateway fees, and monthly account fees.

A business with many small transactions may have a higher effective rate because per-transaction fees represent a larger share of each sale. 

A business with larger average tickets may show a lower effective rate, even if the percentage markup is similar. A business with more keyed or online payments may pay more than a business with mostly chip or contactless POS payments.

Monthly Merchant Statement Comparison Table

The table below summarizes common sections of a merchant statement, what they show, why they matter, and what businesses should review. The labels may differ depending on the payment processor, but the concepts are widely used across merchant billing statements.

Statement Section	What It Shows	Why It Matters	What to Review
Account Summary	Gross sales, refunds, chargebacks, net volume, total fees, transaction count	Gives a quick overview of monthly activity	Compare sales, fees, and transaction count with prior months
Sales Summary	Processing volume by card type, payment method, or sales channel	Helps explain cost differences	Look for shifts in card-present and card-not-present activity
Deposit or Funding Summary	Batch deposits, funding dates, net deposits, deductions	Helps reconcile bank deposits	Match funding totals to bank records and batch reports
Batch Settlement Detail	Daily batch totals and settlement timing	Shows when transactions were submitted for funding	Check late batches, missing batches, or unusual batch fees
Fee Summary	Processing fees, monthly fees, service charges, network fees	Shows total payment processing cost	Identify new, increased, duplicate, or unclear fees
Interchange Detail	Interchange categories, rates, transaction counts, card types	Explains many variable card costs	Look for expensive card categories or downgraded transactions
Assessment and Card Brand Fees	Network-related percentage and per-item charges	Adds to total processing cost	Review changes in card brand fees or unusual network charges
Processor Markup	Provider-controlled percentage, per-item, or monthly charges	Often the most reviewable cost layer	Separate markup from interchange and assessments
Refunds	Returned transaction amounts	Reduces net sales and may affect fees	Compare refund activity with sales and customer service records
Chargebacks and Retrievals	Disputes, documentation requests, related fees	Can reduce deposits and increase costs	Monitor dispute trends and response deadlines
Adjustments and Reserves	Corrections, holds, releases, reserve deductions	Can affect cash flow and reconciliation	Investigate unclear deductions or funding holds

Use this table as a monthly checklist. A statement may look complicated at first, but most sections answer one of four questions: What did the business process? What was deposited? What was deducted? What changed from the previous month?

Red Flags to Look for on Merchant Processing Statements

A merchant processing statement can reveal early warning signs of billing problems, operational issues, or unnecessary costs. Red flags do not always mean something is wrong, but they do mean the business should ask questions.

One common red flag is an unexplained fee increase. If total fees increased faster than processing volume, review the fee summary, card type breakdown, pricing categories, and chargebacks. The cause may be a change in transaction mix, but it could also be a new fee or pricing adjustment.

Another warning sign is a new monthly charge. Statement fees, PCI compliance fees, gateway fees, software fees, monthly minimum fees, and service fees can appear without much attention. If a fee is unfamiliar, ask what it is, why it applies, and whether it is optional or avoidable.

Excessive non-qualified fees can also be a concern. Under tiered pricing, many transactions falling into higher-cost categories may suggest keyed entry issues, missing data, late batch settlement, card-not-present risk, or a pricing structure that is not ideal for the business.

High chargeback fees are another important red flag. Chargebacks reduce revenue and create extra costs. Frequent disputes may also signal fulfillment problems, unclear billing descriptors, customer service gaps, fraud risk, or subscription cancellation issues.

Funding mismatches should also be reviewed. If bank deposits do not match the funding summary, there may be timing differences, refunds, chargebacks, reserves, split deposits, or adjustments. If the mismatch cannot be explained, it should be investigated.

Watch for:

• New or unfamiliar monthly fees
• Sudden increases in discount rate or transaction fees
• High non-qualified or downgrade costs
• Unexpected PCI non-compliance fees
• Duplicate gateway or software charges
• Unusual batch fees
• Chargeback spikes
• Reserve deductions or funding holds
• Deposit amounts that do not reconcile
• Vague adjustment descriptions

Deposits, Batches, and Reconciliation

Deposits and reconciliation are among the most practical reasons to review monthly merchant statements. Card payments do not always flow into a bank account in the same amounts shown on sales reports. Batch settlement timing, refunds, fees, chargebacks, reserves, and adjustments can all affect the final deposit.

Batch settlement is the process of submitting approved transactions for funding. A batch may include one day’s card activity, but the timing depends on the POS system, gateway, business hours, and settlement cutoff. If a batch closes after the cutoff, funding may shift to a later date.

For reconciliation, start with gross card sales from the POS system or ecommerce platform. Then compare that number with the processing volume on the merchant statement. Next, subtract refunds, chargebacks, and known adjustments. Then compare the remaining activity with the funding summary and bank deposits.

Some processors deduct fees daily. In that case, deposits may already be reduced by processing costs. Other processors deduct fees monthly. In that case, deposits may be closer to gross sales, and fees may appear as one larger monthly debit. Understanding the billing method is essential for accurate cash flow tracking.

Ecommerce payments can add complexity because orders, captures, refunds, and settlements may happen on different dates. A customer may place an order on one day, the transaction may capture later, and the deposit may occur after that. Subscription billing may create additional timing differences.

Good reconciliation practices include:

• Closing batches consistently.
• Keeping POS and gateway reports.
• Matching batch totals to funding dates.
• Recording refunds separately.
• Tracking chargebacks as deductions.
• Reviewing reserve holds and releases.
• Comparing bank deposits with statement funding details.
• Investigating unexplained adjustments.

For businesses using online tools, understanding the difference between payment gateways and manually entered transactions can help explain statement activity. This overview of virtual terminals and payment gateways provides useful context for remote payment acceptance.

Refunds, Chargebacks, and Adjustments on Statements

Refunds, chargebacks, and adjustments can reduce deposits, increase costs, and complicate reconciliation. These items are often listed separately on a merchant statement because they affect payment activity after the original sale.

Refunds occur when a business returns money to a customer. On a statement, refunds may appear as negative sales, return items, refund volume, or deduction activity. A refund may reduce a future deposit rather than the deposit from the original sale date. That timing difference can confuse reconciliation if refunds are not tracked carefully.

Chargebacks occur when a cardholder disputes a transaction through the card issuer. A chargeback may remove the transaction amount from the business’s funding and add a chargeback fee. Even if the business later wins the dispute, the reversal may appear in a different billing period.

Retrieval requests may appear when documentation is requested for a transaction. These can happen before or during a dispute. A retrieval fee may apply even if the transaction does not become a chargeback.

Adjustments are corrections or account-level changes. They may include billing corrections, funding corrections, reserve deductions, reserve releases, returned deposit items, chargeback reversals, or other account activity. Because adjustment labels can be vague, businesses should review them carefully.

Reserves are another important item. A reserve is a portion of funds held back to cover potential risk such as refunds, chargebacks, or delayed fulfillment. Reserve deductions reduce cash flow, while reserve releases may increase deposits later.

When reviewing these sections, compare the statement with customer service records, refund logs, dispute notices, ecommerce order records, and bank deposits. If a chargeback or adjustment is unfamiliar, document the transaction date, amount, reason code if available, and response deadline.

Card-Present vs Card-Not-Present Costs on Statements

Card-present and card-not-present transactions often have different costs because they carry different risk levels and data requirements. A card-present transaction usually happens when the customer taps, inserts, or swipes a card at a POS terminal. 

Card-not-present transactions happen when the card is not physically used at checkout, such as ecommerce payments, phone orders, keyed payments, invoices, virtual terminal transactions, and recurring billing.

Card-present transactions often benefit from stronger verification tools, such as EMV chip technology and contactless payment security. These transactions may qualify for lower interchange categories when processed correctly. However, costs still depend on card type, merchant category, ticket size, and pricing model.

Card-not-present transactions usually carry more fraud and dispute risk. Because the card and cardholder are not physically verified in the same way, these transactions may cost more. Ecommerce payments, keyed transactions, recurring billing, and mobile invoice payments may also involve gateway fees, AVS fees, tokenization fees, fraud tools, or account updater charges.

AVS, or address verification, helps compare billing address details with issuer records. CVV checks help confirm that the customer has access to the card security code. Tokenization replaces sensitive card data with a token for safer storage and recurring payments. These tools can support fraud prevention and payment security, though they do not eliminate risk.

The PCI Security Standards Council provides payment security resources through its official security standards site, which can help businesses understand data protection responsibilities.

Businesses should review statements to see how much volume comes from each channel. If card-not-present volume is rising, higher fees may be expected. However, proper data entry, fraud controls, clear billing descriptors, and timely batch settlement may help reduce avoidable downgrades and disputes.

How Statement Fees Can Affect Cash Flow

Statement fees affect cash flow because they reduce the amount of card revenue a business actually keeps. Gross sales may look strong, but net deposits tell the more practical story. A business needs to understand both numbers to manage cash flow accurately.

Processing fees may be deducted daily or monthly. Daily deduction reduces each deposit, which means the bank account receives net funding. Monthly deduction allows larger deposits during the month, followed by one larger fee debit. Neither method is automatically better, but each affects cash planning differently.

Chargebacks can create sudden deductions. A disputed transaction may be removed from funding before the business has resolved the case. If chargebacks are frequent or high-dollar, they can create cash flow pressure, especially for businesses with narrow margins.

Reserves can also affect cash flow. If a processor holds a percentage of deposits, the business may not receive all card revenue immediately. This can matter for businesses that rely on card sales to purchase inventory, pay staff, cover shipping, or fund operating expenses.

Gateway fees, monthly minimum fees, PCI compliance fees, statement fees, software fees, and equipment fees may seem small individually, but together they can affect monthly profitability. These fixed fees have a stronger impact when sales volume is low.

Refunds also reduce cash flow. If a business receives revenue in one period and refunds the customer in another, the cash impact may not align neatly with the original sale.

The best approach is to review gross sales, net deposits, total fees, refunds, chargebacks, and reserves together. This gives a more accurate picture of available cash and payment acceptance costs.

Pro Tip: Build processing fees and expected refunds into cash flow forecasts. Treat card revenue as net-of-cost revenue, not just gross sales.

Common Mistakes Businesses Make When Reviewing Merchant Statements

Many businesses make the same mistakes when reviewing monthly merchant statements. The first mistake is checking only total sales. Sales volume matters, but it does not show whether deposits were correct, fees changed, or chargebacks increased.

Another mistake is ignoring small recurring fees. A statement fee, gateway fee, PCI compliance fee, monthly minimum fee, or software fee may look minor, but recurring charges can add up over time. These fees should be reviewed just like percentage-based processing costs.

Some businesses do not calculate effective rate. Without this calculation, it is difficult to know whether total processing cost is rising or falling. Effective rate is not perfect, but it is a helpful starting point for merchant statement analysis.

Another common mistake is overlooking chargebacks. A business may focus on sales and deposits while missing dispute activity. Chargebacks can create direct losses, fees, operational work, and risk concerns.

Businesses also sometimes fail to compare deposits to bank records. They assume the processor funded everything correctly. Most deposits are routine, but reconciliation is still important. Timing differences are common, and unresolved discrepancies should be documented.

Misunderstanding pricing categories is another issue. Under tiered pricing, a business may not know why transactions are being billed as mid-qualified or non-qualified. Under flat-rate pricing, a business may not see the underlying cost differences. Under interchange-plus pricing, the detail may be accurate but difficult to interpret.

Finally, many businesses do not review PCI-related charges. A PCI compliance fee may be expected, but a PCI non-compliance fee may indicate that required validation steps are incomplete. Businesses should understand what each charge means.

How to Review Merchant Statements for Cost-Saving Opportunities

A merchant statement can help identify ways to reduce avoidable payment costs. Not every fee can be changed, but many statement patterns are worth reviewing. The key is to separate unavoidable network costs from operational issues and provider-controlled charges.

Start by reviewing effective rate over several months. If the rate increased, look for causes. Did card-not-present volume rise? Did average ticket size fall? Did chargebacks increase? Did a new monthly fee appear? Did more transactions fall into non-qualified categories?

Next, review downgrade or non-qualified fees if the statement uses tiered pricing. High downgrade costs may be related to keyed entry, missing AVS data, late batch settlement, business card data requirements, or card-not-present activity. Improving transaction data accuracy may help some transactions qualify more favorably.

Review gateway fees and software charges. Businesses sometimes pay for old gateways, inactive terminals, unused accounts, duplicate software tools, or features they no longer need. If a fee is tied to equipment or technology, verify that the service is still active and useful.

Monitor chargebacks and retrieval fees. Reducing disputes can lower direct fees and protect revenue. Clear billing descriptors, strong customer communication, delivery confirmation, transparent refund policies, and fraud screening can help reduce preventable disputes.

Review monthly minimum fees. If a business pays a monthly minimum because processing volume is low, it may need to evaluate whether the account structure still fits its activity.

Also review the pricing model. Interchange-plus pricing may provide more transparency for some businesses. Flat-rate pricing may be easier for others. Tiered pricing may be harder to analyze if many transactions fall into higher-cost categories.

Questions worth asking include:

• Which charges are processor markup?
• Are any fees optional?
• Are there inactive equipment or gateway fees?
• Why are transactions being downgraded?
• Are card-not-present transactions entered with complete data?
• Are batches being settled on time?
• Are chargebacks preventable?
• Does the pricing model still match the business?

For businesses learning how small percentage changes affect processing costs, this overview of basis points in credit card processing can provide helpful context.

Questions to Ask About Your Merchant Statement

A good merchant statement review often comes down to asking the right questions. Business owners and finance teams do not need to memorize every fee code, but they should know how to challenge unclear charges and investigate changes.

Start with the effective rate. Ask: What is my effective rate this month, and how does it compare with previous months? If it changed, ask what caused the change. Look at volume, transaction count, average ticket size, refunds, chargebacks, and fee categories.

Next, ask which fees are processor markup. This helps separate provider-controlled charges from interchange fees and assessment fees. If the statement does not clearly separate these costs, ask for a written explanation.

Review new fees carefully. Ask whether any new monthly charges appeared this month. If so, ask when they started, why they apply, and whether they are required. Do the same for increases in gateway fees, statement fees, monthly minimum fees, PCI compliance fees, or batch fees.

Ask whether PCI non-compliance fees appear. If they do, find out what validation step is missing and how to correct it. Payment security requirements can be technical, so documentation matters.

Ask about chargebacks. Are chargeback fees increasing? Are disputes tied to a certain product, service, location, sales channel, or billing descriptor? Are retrieval fees appearing before disputes?

Ask whether deposits match sales reports. If not, identify whether the difference comes from refunds, chargebacks, reserves, timing, fees, or adjustments.

Useful questions include:

• What is my effective rate?
• Which fees are processor markup?
• Are any new fees appearing this month?
• Why did my fees change?
• Are there PCI non-compliance fees?
• Are chargeback fees increasing?
• Do deposits match my sales reports?
• Are card-not-present transactions costing more?
• Are monthly minimums or statement fees being charged?
• Are there reserve deductions or funding holds?
• Are gateway fees tied to active services?
• Are batch fees higher than expected?
• Are refunds unusually high?
• Are any charges duplicated?

Best Practices for Managing Monthly Merchant Statements

The best way to manage monthly merchant statements is to create a repeatable review process. A consistent process saves time and helps catch problems early.

Review the statement every month, even when sales look normal. Payment costs can change quietly. A new fee, higher markup, PCI non-compliance charge, or chargeback trend may not be obvious from bank deposits alone.

Keep copies of statements in a secure location. Statements may be needed for accounting, loan applications, tax preparation, dispute research, pricing reviews, or processor comparisons. Store them by month and merchant account if the business has multiple locations or sales channels.

Compare statements over time. One statement tells you what happened during one billing period. Several statements show trends. Look for changes in processing volume, average ticket size, card-not-present activity, total fees, effective rate, chargebacks, refunds, and monthly charges.

Reconcile deposits regularly. Match POS reports, ecommerce reports, gateway reports, funding summaries, and bank deposits. Document timing differences and investigate unexplained gaps.

Train staff on proper transaction entry. Incorrect keyed transactions, missing address verification, delayed batch settlement, or inconsistent refund handling can affect costs and disputes. Staff training can reduce avoidable errors.

Review contract terms and pricing notices. Some fees may be described in agreements, monthly messages, online portals, or statement notes. If a charge changes, ask for the explanation in writing.

Monitor chargebacks closely. Keep documentation, respond by deadlines, and look for root causes. Reducing disputes can protect both revenue and processing stability.

When to Get Help Reviewing a Merchant Statement

Some businesses can review statements internally. Others may need help from an accountant, financial advisor, payment consultant, or knowledgeable payment professional. Help may be useful when statements are complex, fees are unclear, or payment costs are significant.

A business should consider getting help if it has high processing volume. Even small rate differences can matter when volume is large. A detailed merchant statement analysis may reveal whether costs are driven by interchange, assessments, processor markup, chargebacks, or transaction practices.

Help may also be useful when fees increase without a clear explanation. If the effective rate rises, new charges appear, or non-qualified fees become excessive, a second review can help identify the cause.

Businesses with frequent chargebacks may also benefit from guidance. Chargebacks involve customer service, fraud prevention, billing descriptors, documentation, fulfillment, and dispute response. A statement may show the cost, but additional review may be needed to reduce the problem.

Ecommerce sellers, subscription businesses, professional services firms, and businesses using virtual terminals may face more card-not-present risk. They may need help reviewing AVS usage, gateway fees, tokenization, recurring billing practices, fraud tools, and refund workflows.

Help is also useful when deposits are difficult to reconcile. If funding does not match reports, and timing differences do not explain the gap, an accountant or payment professional can help trace the activity.

Businesses should ask for explanations in writing and keep records. A good review should clarify what each fee means, whether it is pass-through or markup, whether it can be changed, and what operational steps may reduce avoidable costs.

Final Thoughts

Monthly merchant statements are essential tools for understanding payment costs, reconciling deposits, managing cash flow, and spotting billing issues. They show more than card sales. They reveal how transactions were processed, what fees were charged, when deposits were funded, and how refunds, chargebacks, reserves, and adjustments affected the business.

A merchant statement may look complicated at first, but it becomes easier when reviewed section by section. Start with processing volume, then review deposits, refunds, chargebacks, fee summaries, pricing categories, and effective rate. Compare each statement with prior months to spot changes.

Understanding monthly merchant statements also helps businesses ask better questions. Instead of simply asking why fees are high, a business can ask which fees are interchange, which are assessment fees, which are processor markup, why card-not-present costs increased, whether non-qualified fees are avoidable, and whether deposits match sales reports.

The most important habit is consistency. Review statements every month, save copies, reconcile deposits, monitor chargebacks, and document unclear charges. Over time, this process can help businesses control payment costs, improve accounting accuracy, and make more informed payment processing decisions.