Monthly Statement Audit Checklist for Merchants

A monthly statement audit checklist helps merchants understand what actually happened with card payments during a billing period. 

It gives business owners, ecommerce sellers, retail stores, restaurants, service providers, bookkeepers, and finance teams a repeatable way to review sales, deposits, refunds, chargebacks, and payment processing fees without feeling lost in a dense merchant statement.

A merchant statement can look complicated at first. It may include a funding summary, sales summary, processing volume, transaction count, interchange fees, assessment fees, processor markup, gateway fees, PCI compliance fees, chargeback fees, retrieval fees, reserves, adjustments, and other line items. When these items are not reviewed carefully, billing errors and cost increases can go unnoticed.

The goal of a monthly merchant statement audit is not just to find mistakes. It is also to understand trends. If your average ticket size changes, chargebacks rise, refunds increase, or your effective processing rate moves higher, your monthly merchant statement can reveal it.

This guide explains how to review a merchant processing statement step by step, calculate your effective rate, match deposits to bank records, analyze merchant statement fees, and create a consistent review process that supports better cash flow and cleaner accounting.

What Is a Monthly Statement Audit Checklist?

A monthly statement audit checklist is a structured review process for checking the details on a merchant statement. It helps merchants confirm that card sales, deposits, refunds, chargebacks, reserves, adjustments, and merchant services fees are recorded correctly for the statement period.

Instead of looking only at the final bank deposits, the checklist walks through each major part of the merchant account statement. This includes the account summary, sales summary, funding summary, fee summary, interchange detail, assessment fees, processor markup, recurring charges, and chargeback activity.

A monthly merchant statement audit is especially useful because card payments usually involve multiple moving parts. A single transaction may include authorization, settlement, interchange, assessment, processor markup, gateway activity, batch settlement, and funding. 

By the time money reaches the business bank account, the deposit may already reflect deductions, refunds, chargebacks, reserves, or timing differences.

The checklist gives merchants a practical way to answer important questions. Did the processing volume match POS payments and ecommerce payments? Did the funding summary match the bank account? Were chargeback fees or retrieval fees expected? Did PCI compliance fees appear? Did gateway fees, statement fees, monthly fees, or batch fees change?

A payment processing statement audit also helps merchants compare one month to another. Even small changes in transaction fees, authorization fees, discount rate, card brand fees, or merchant account fees can add up when transaction count is high.

Why Merchants Should Audit Monthly Statements

Merchants should audit monthly statements because payment acceptance costs can change quietly. A business may see card sales increasing and assume everything is fine, while the effective processing rate is also rising due to higher card-not-present transactions, more rewards cards, new gateway fees, or additional monthly service charges.

Checking only bank deposits is not enough. Deposits show what arrived in the account, but they do not always explain how gross sales became net deposits. Refunds, chargebacks, reserves, batch settlement timing, statement fees, PCI compliance fees, and other adjustments may all affect the final funding amount.

A merchant services statement audit helps with accounting accuracy. Bookkeepers and finance teams need to reconcile gross sales, net sales, processing fees, refunds, chargebacks, and deposits correctly. If the merchant services statement is ignored, sales may be overstated, fees may be misclassified, or deposits may be matched to the wrong batch.

Audits also support contract and pricing review. If a merchant account statement shows new fees, increased monthly fees, unexpected gateway fees, PCI non-compliance charges, or a changed discount rate, the merchant can document the change and ask for an explanation. Regular review also makes it easier to identify cost-saving opportunities. 

For example, a restaurant with many small tickets may be affected heavily by per-transaction fees. An ecommerce seller may see higher costs from card-not-present transactions, chargebacks, and gateway fees. A service provider may discover that recurring billing fees or virtual terminal fees are adding more cost than expected.

What Documents You Need Before Starting the Audit

Before starting a merchant account statement audit, gather all documents connected to card payment activity for the same statement period. The monthly merchant statement is the main document, but it should not be reviewed alone.

Start with the merchant statement or merchant services statement. This document usually includes processing volume, transaction count, total fees, deposits, funding summary, sales summary, refunds, chargebacks, adjustments, reserves, and service charges.

Next, gather bank account records. You will use these to confirm net deposits, funding dates, delayed deposits, reserve deductions, and settlement timing. Bank deposits may not match gross sales because fees, refunds, chargebacks, or adjustments may already be deducted.

You should also collect POS reports, ecommerce platform reports, gateway reports, settlement reports, batch reports, refund records, and chargeback notices. If your business uses more than one sales channel, separate card-present transactions from card-not-present transactions where possible.

Contract and pricing documents are also useful. These may show expected discount rate, transaction fees, authorization fees, monthly fees, gateway fees, PCI compliance fees, batch fees, statement fees, equipment fees, and other merchant account fees.

Finally, keep prior-month statements nearby. Comparing statements month to month is one of the best ways to identify unusual changes. A single month may not tell the full story, but a trend can show whether processing fees, chargebacks, refunds, or average ticket size are moving in the wrong direction.

Useful documents include:

• Monthly merchant statement
• Bank deposit records
• POS payments reports
• Ecommerce payments reports
• Gateway reports
• Batch settlement reports
• Refund and void records
• Chargeback and retrieval notices
• Contract or pricing schedule
• Prior merchant account statements
• Accounting software entries

Key Sections to Review on a Merchant Statement

A credit card processing statement may vary by provider, but most statements include several common sections. The layout may be simple, detailed, bundled, or highly technical depending on the pricing model and statement format.

The account summary usually provides a high-level view of processing volume, transaction count, refunds, chargebacks, total fees, and net activity. This section is helpful, but it should be treated as a starting point rather than the full audit.

The processing summary or sales summary may break out card-present transactions, card-not-present transactions, keyed transactions, ecommerce payments, POS payments, debit activity, credit activity, and other transaction types. This helps you understand how payment mix affects cost.

The funding summary shows deposits, settlement dates, batch settlement activity, deductions, reserves, adjustments, and net deposits. This section is important for reconciliation because it connects the merchant processing statement to the bank account.

The fee summary is where many merchants spend the most time. It may include interchange fees, assessment fees, card brand fees, discount fees, transaction fees, authorization fees, batch fees, gateway fees, monthly fees, statement fees, PCI compliance fees, chargeback fees, retrieval fees, equipment fees, and processor markup.

The chargeback and adjustment sections should also be reviewed closely. These items can affect cash flow, create operational risk, and signal possible fraud, fulfillment, billing, or customer service issues.

Account Summary and Sales Overview

The account summary and sales overview give a quick snapshot of activity for the statement period. This section often includes gross sales, refunds, chargebacks, net sales, total processing volume, transaction count, average ticket size, and total merchant services fees.

This is the first place to check whether the numbers look reasonable. If your business had a busy month but the processing volume looks low, you may need to compare the statement with POS reports, ecommerce reports, or gateway reports. If the transaction count increased but sales volume stayed flat, your average ticket size may have dropped.

Average ticket size matters because many payment processing fees include both percentage-based charges and fixed per-transaction fees. A business with smaller tickets may pay more relative to sales because transaction fees and authorization fees apply to each sale.

The account summary is helpful, but it can hide details. For example, total fees may look normal even if one fee category increased and another decreased. That is why a full merchant statement analysis should continue into the fee summary, funding summary, and detail sections.

Deposit and Funding Summary

The deposit and funding summary explains how card sales became bank deposits. It may show settlement dates, batch totals, net deposits, deducted fees, refunds, chargebacks, reserves, and adjustments.

Deposits often do not match gross sales exactly. A batch may settle after the statement period ends. Fees may be deducted daily or monthly. Refunds may reduce a deposit. Chargebacks may be withdrawn from funding. Reserves may be held back. Adjustments may correct prior activity.

For reconciliation, match each funding deposit on the merchant statement to the bank account. Pay attention to dates because settlement timing can create differences between the date of sale, the batch settlement date, and the bank deposit date.

If a deposit is missing, duplicated, delayed, or reduced unexpectedly, document it. A funding mismatch is one of the most important red flags in a payment processing statement audit because it affects cash flow and accounting records.

Step-by-Step Monthly Statement Audit Checklist

A practical monthly statement audit checklist should be simple enough to repeat every month. The goal is not to become a payment expert overnight. The goal is to build a reliable review process that helps you catch errors, understand costs, and keep better records.

Start by confirming the statement period. Make sure the merchant statement covers the same dates as the POS reports, ecommerce reports, gateway reports, and bank records you are reviewing. A mismatch in date ranges can create false differences.

Next, review total processing volume and transaction count. Compare these numbers to internal sales reports. Then calculate average ticket size by dividing total processing volume by transaction count. A large change in average ticket size may indicate a sales mix change, reporting issue, or unusual activity.

After that, compare deposits with bank records. Match funding summary entries to actual bank deposits and note any differences caused by batch settlement, deducted fees, refunds, chargebacks, reserves, or adjustments.

Then review refunds, voids, chargebacks, and retrieval fees. These items affect cash flow and may indicate operational problems if they rise over time.

Finally, identify total fees and calculate your effective processing rate. Review interchange fees, assessment fees, processor markup, monthly fees, gateway fees, PCI fees, equipment fees, statement fees, and other line items. Compare the results with prior statements and document any questions.

Monthly Statement Audit Checklist Table

Audit Step	What to Review	Why It Matters	Red Flag to Watch For
Confirm statement period	Billing dates and settlement dates	Keeps reports aligned	Statement dates do not match internal reports
Review processing volume	Gross sales, net sales, card volume	Confirms sales activity	Volume differs from POS or ecommerce reports
Check transaction count	Number of sales and authorizations	Shows activity level	Count jumps without a sales explanation
Calculate average ticket	Volume divided by transaction count	Helps explain fee changes	Average ticket drops sharply
Match deposits	Funding summary and bank deposits	Supports reconciliation	Missing or reduced deposit
Review refunds	Refund totals and timing	Affects net sales and cash flow	Refunds higher than expected
Review chargebacks	Disputes, fees, reversals	Shows dispute risk	Chargebacks increase suddenly
Identify total fees	Fee summary and billing detail	Measures total processing cost	New or duplicate charges
Calculate effective rate	Fees divided by volume, multiplied by one hundred	Tracks cost trend	Rate rises without clear cause
Check recurring fees	Gateway, PCI, equipment, monthly fees	Finds overlooked charges	Unexpected new monthly fee
Compare prior month	Volume, fees, deposits, chargebacks	Spots trends	Cost increase repeats
Document questions	Notes for provider or accountant	Creates audit trail	No written explanation for changes

This table can be used as a recurring monthly merchant statement audit worksheet. Merchants with multiple locations, sales channels, or merchant accounts may want to complete one checklist per account, then prepare a summary across all accounts.

How to Verify Processing Volume

Processing volume is one of the most important numbers on a merchant statement. It represents the amount of card activity processed during the statement period, but it may be reported as gross volume, net volume, settled volume, or billed volume depending on the statement format.

Start with the total processing volume shown on the merchant processing statement. Then compare it with POS reports, ecommerce reports, gateway reports, and accounting records. 

If you accept both in-person and online payments, separate card-present transactions from card-not-present transactions. This can help explain fee differences because these transaction types often carry different costs and risk profiles.

Gross sales usually represent total card sales before refunds, chargebacks, and certain adjustments. Net sales may subtract refunds and returns. Net deposits may subtract fees, chargebacks, reserves, and other deductions. These numbers are related, but they are not the same.

If the merchant statement shows lower volume than your sales reports, check whether some transactions settled after the statement period. Also review voids, refunds, split tenders, gift cards, cash sales, third-party delivery orders, and other activity that may not appear in card processing volume.

How to Review Transaction Count and Average Ticket Size

Transaction count shows how many card transactions were processed. Average ticket size shows the typical value of those transactions. Together, they help explain why credit card processing fees may change even when total sales volume looks stable.

To calculate average ticket size, divide total processing volume by transaction count. For example, if a business processes fifty thousand in card volume across one thousand transactions, the average ticket size is fifty.

This matters because many merchant statement fees include a percentage charge and a fixed transaction fee. A business with many small tickets may feel the impact of transaction fees, authorization fees, and batch fees more heavily than a business with fewer high-ticket transactions.

If transaction count rises while processing volume stays flat, average ticket size decreases. That may increase the effective rate because fixed transaction fees are spread across smaller sales. Restaurants, coffee shops, convenience stores, and quick-service businesses often need to watch this closely.

If average ticket size rises or falls suddenly, compare it with actual sales behavior. Did the business run a promotion? Did ecommerce orders increase? Did more customers use invoices or recurring billing? Did a POS reporting issue duplicate or omit transactions?

A monthly merchant statement audit should not treat transaction count as a minor detail. It is one of the clearest indicators of how sales behavior affects payment processing fees.

How to Match Deposits to Bank Records

Matching deposits is a core part of merchant statement reconciliation. The funding summary on the payment processing statement should be compared with actual deposits in the business bank account.

Start by listing each deposit shown on the merchant statement. Include the settlement date, funding date, batch amount, deductions, reserve activity, refunds, chargebacks, and net deposit amount. Then compare those entries to the bank account.

Do not expect every bank deposit to match gross sales. A deposit may reflect net deposits after deducted fees, refunds, chargebacks, or reserves. Some processors deduct fees daily, while others deduct them monthly. Some deposits may combine multiple batches, while others may split activity across different funding dates.

Batch settlement timing is another common reason for differences. A sale may occur late in the day, settle in the next batch, and fund on a later banking day. This is especially common around weekends, holidays, or after cutoff times.

If a deposit does not match, trace the difference before assuming an error. Check refund timing, chargeback deductions, adjustment entries, reserve holds, batch cutoff times, and whether the deposit belongs to a different statement period.

Gross Sales vs Net Deposits in a Statement Audit

One of the most common mistakes in a merchant statement audit is confusing gross sales with net deposits. Gross sales, net sales, processing volume, and net deposits each tell a different story.

Gross sales usually refer to the full amount of card sales before refunds, chargebacks, fees, or adjustments. Net sales may subtract refunds and returns. Processing volume may reflect the amount used to calculate some payment processing fees. Net deposits represent the amount funded to the bank account after certain deductions.

For example, a business may process ten thousand in gross card sales. During the same period, it may issue five hundred in refunds, receive one chargeback, pay processing fees, and have a reserve deduction. The bank deposit will not equal ten thousand because the funding amount reflects these deductions and timing differences.

Chargebacks can also reduce deposits. A chargeback may remove the disputed sale amount and add a chargeback fee. Retrieval fees or dispute-related fees may appear separately.

Reserves are another reason deposits may be lower than expected. Some merchant accounts include reserve activity, especially when there is elevated risk, unusual volume, delayed delivery, or higher dispute exposure.

Understanding these differences helps merchants avoid accounting errors. Sales should be recorded based on the appropriate sales source, while fees, refunds, chargebacks, and adjustments should be recorded separately for clean financial reporting.

How to Audit Processing Fees

A processing fee audit starts with identifying total fees for the statement period. Then break those fees into categories so you can understand what is driving cost.

Common fee categories include percentage-based fees, per-transaction fees, discount fees, interchange fees, assessment fees, processor markup, monthly fees, gateway fees, PCI compliance fees, batch fees, authorization fees, statement fees, equipment fees, card brand fees, chargeback fees, retrieval fees, and other merchant account fees.

Some statements show each fee separately. Others bundle multiple fees into a discount rate or qualified, mid-qualified, and non-qualified categories. The more bundled the statement, the harder it may be to see the underlying cost structure.

Start by locating total fees. Then separate variable fees from fixed fees. Variable fees rise with processing volume or transaction count. Fixed fees may appear even when volume is low.

Next, compare each category with prior statements. A small increase in authorization fees may be normal if transaction count increased. A new PCI non-compliance fee, duplicate gateway fee, or unexplained statement fee should be reviewed.

A merchant services statement audit should also look for fee names that sound similar but are charged separately. For example, a gateway monthly fee and gateway transaction fee may both appear. Equipment rental and software subscription charges may also appear as recurring line items.

Common Merchant Statement Fees Table

Fee Type	What It Means	Why It May Appear	Audit Question to Ask
Interchange fees	Fees connected to card-issuing banks	Card type, transaction method, and card data affect cost	Are these passed through or bundled?
Assessment fees	Network-related fees	Applied through card network rules	Are they listed separately or included in another fee?
Processor markup	Provider-controlled margin or service charge	Covers processing service and support	Is this consistent with pricing terms?
Discount rate	Percentage fee on volume	May include markup or bundled pricing	What costs are included in this rate?
Transaction fees	Fixed fee per transaction	Applies to each sale or authorization	Did transaction count increase?
Authorization fees	Fee for approval requests	May apply to sales, declined transactions, or authorizations	Are authorization counts reasonable?
Batch fees	Fee for settling a batch	May apply when batches close	Are batches closing efficiently?
Monthly fees	Recurring account fees	Account maintenance or service billing	Was this expected?
Gateway fees	Online payment or virtual terminal access	Ecommerce, invoicing, or recurring billing	Is the gateway still being used?
PCI compliance fees	Security and compliance-related charges	Compliance program or status-related billing	Is compliance status current?
Statement fees	Charge for monthly statement or reporting	Account billing line item	Can electronic delivery reduce this?
Chargeback fees	Fee for disputes	Applied when a customer disputes a charge	Did disputes increase?
Retrieval fees	Fee for information requests	May relate to dispute documentation	Is documentation being submitted on time?
Equipment fees	Terminal, reader, or POS hardware charges	Lease, rental, or support billing	Is the equipment still active?

This table is a starting point. Fee names vary across statements, so merchants should review definitions in their pricing schedule or request written clarification when a line item is unclear.

How to Calculate Effective Rate During the Audit

The effective rate is one of the simplest ways to understand total payment acceptance cost. It shows total processing fees as a percentage of total processing volume.

Use this formula:

Effective rate = total processing fees ÷ total processing volume × one hundred

For example, if a merchant processed forty thousand in card volume and paid one thousand two hundred in total processing fees, the effective rate is three percent.

This number is useful because it includes more than the advertised discount rate. It can reflect transaction fees, authorization fees, gateway fees, monthly fees, PCI compliance fees, statement fees, chargeback fees, batch fees, assessment fees, interchange fees, and processor markup.

However, effective rate should be used carefully. A higher effective processing rate is not always an error. It may increase when average ticket size drops, card-not-present transactions rise, chargebacks increase, refunds are high, or monthly fees are spread across lower processing volume.

Compare effective rate month to month. A single month may be unusual due to seasonal sales, refunds, disputes, or lower volume. A steady increase over multiple statements deserves closer review.

How to Audit Interchange Fees

Interchange fees are a major part of many credit card processing statements. They are connected to the card-issuing side of a transaction and are influenced by several factors, including card type, transaction method, merchant category, card data quality, and risk level.

A merchant statement may show interchange detail line by line, especially under interchange-plus pricing. You may see different rates for debit cards, credit cards, rewards cards, business cards, keyed transactions, ecommerce payments, and card-present transactions.

Card-present transactions generally have different risk characteristics than card-not-present transactions. Ecommerce payments, keyed payments, invoice payments, and recurring billing may carry higher costs because there is no physical card interaction at the point of sale.

Transaction data quality can also matter. Missing address verification, missing security code checks, late settlement, manual entry, or incomplete data may affect qualification. For business-to-business transactions, missing enhanced data can sometimes affect processing cost.

A merchant statement audit should compare interchange categories with actual sales activity. If the business mostly accepts in-person chip or contactless payments, but the statement shows a large amount of keyed or card-not-present volume, investigate why.

Interchange is often not controlled directly by the processor, but merchants can still influence some drivers through proper terminal setup, timely batch settlement, accurate transaction data, and fraud prevention practices.

How to Audit Assessment Fees

Assessment fees are different from interchange fees. They are generally tied to card network rules and may be charged as small percentage-based or transaction-related amounts. On some statements, assessment fees appear separately. On others, they may be bundled into a broader pricing category.

During a payment processing statement audit, look for assessment fee line items in the fee summary or network fee section. They may be labeled as card brand fees, network access fees, assessment charges, or similar terms.

Assessment fees are usually less controllable than processor markup. However, they still matter because they contribute to the effective processing rate. If assessment fees increase, compare the change with processing volume, card mix, cross-border activity, card-not-present transactions, or other network-related activity.

Merchants should avoid assuming every fee is processor markup. Some statement fees are pass-through costs, while others are provider-controlled. Understanding the difference helps when asking questions or comparing pricing.

If the statement does not clearly separate interchange fees, assessment fees, and markup, ask for a written breakdown. A clear breakdown can make future merchant statement analysis much easier.

How to Audit Processor Markup

Processor markup is the portion of payment processing fees that may be controlled by the payment provider or processor. It can appear as a percentage markup, per-transaction fee, monthly fee, gateway fee, statement fee, PCI-related fee, batch fee, equipment charge, software fee, or bundled discount rate.

Identifying markup is important because it helps merchants understand which fees may be negotiable, adjustable, or tied to the provider’s pricing structure. Interchange fees and assessment fees may be pass-through items, but markup is often where pricing differences appear.

On interchange-plus statements, processor markup may be easier to identify because interchange, assessments, and markup are often separated. On tiered or flat-rate statements, markup may be blended into qualified, mid-qualified, non-qualified, or flat-rate categories.

Review markup month to month. If the percentage markup, transaction fees, monthly fees, gateway fees, or statement fees change, document the change and compare it with contract terms.

Also look for duplicate or inactive service charges. A merchant may still be paying for a gateway, terminal rental, mobile reader, plugin, or software add-on that is no longer being used.

How Pricing Models Affect Statement Audits

Pricing models affect how easy or difficult a merchant statement audit can be. The same processing activity may appear very differently depending on whether the account uses interchange-plus pricing, tiered pricing, flat-rate pricing, subscription pricing, or another blended structure.

Interchange-plus pricing usually separates interchange fees, assessment fees, and processor markup. This can make merchant statement analysis more transparent, but it may also produce longer statements with many line items.

Tiered pricing groups transactions into categories such as qualified, mid-qualified, and non-qualified. This can make statements appear simpler, but it may be harder to understand why certain transactions cost more.

Flat-rate pricing applies a predictable rate to many transactions, which can simplify forecasting. However, it may make the underlying mix of interchange, assessment fees, and markup less visible.

Subscription pricing may include a monthly membership fee plus lower markup or transaction costs. This can be useful for some merchants but should still be audited carefully because monthly fees, transaction count, and volume all affect the total cost.

No pricing model removes the need for review. Every merchant account statement should still be checked for volume, deposits, refunds, chargebacks, effective rate, new fees, and recurring charges.

Auditing Interchange-Plus Statements

Interchange-plus statements often provide more detail than bundled statements. They may list interchange categories, assessment fees, and processor markup separately. This can help merchants see what portion of total cost is related to card type, transaction method, network charges, and provider pricing.

When auditing this type of statement, start with total processing volume and total fees. Then review interchange detail. Look for unusual categories, such as higher-cost card-not-present transactions, keyed entries, rewards cards, business cards, or downgraded transactions.

Next, review assessment fees and processor markup. Confirm whether the markup matches expected pricing terms. Then check monthly fees, gateway fees, PCI compliance fees, batch fees, authorization fees, statement fees, and equipment fees.

This pricing model can support a more detailed merchant services statement audit, but it requires careful reading. Do not assume a long statement means something is wrong. More detail can actually make the audit more useful.

Auditing Tiered and Flat-Rate Statements

Tiered and flat-rate statements may look easier to read because they group costs into fewer categories. However, they can make it harder to see exactly how much of the fee is interchange, assessment, or processor markup.

With tiered pricing, transactions may be grouped into qualified, mid-qualified, and non-qualified categories. Non-qualified transactions usually cost more, so a sudden increase in that category should be reviewed. It may be related to keyed payments, card-not-present transactions, late settlement, missing data, or certain card types.

With flat-rate pricing, focus on total fees, transaction count, average ticket size, refunds, chargebacks, and effective rate. Even if the rate seems simple, added monthly fees, gateway fees, PCI fees, equipment charges, and dispute fees can change the true cost.

For these statements, the effective rate is especially useful. It gives merchants one number to compare month to month, even when the underlying fee structure is not fully itemized.

How to Review Refunds, Voids, and Chargebacks

Refunds, voids, chargebacks, retrieval requests, reversals, disputes, and adjustments can all appear on a merchant statement. These items affect deposits, fees, accounting records, and cash flow.

A void usually cancels a transaction before settlement. A refund returns money after the sale has settled. A chargeback occurs when a cardholder disputes a transaction through the card issuer. A retrieval request may ask for transaction documentation before or during a dispute process.

During a monthly merchant statement audit, compare refunds on the statement with POS reports, ecommerce reports, customer service records, and accounting entries. Confirm that refunds were authorized, recorded correctly, and tied to the proper order or invoice.

Chargebacks deserve close attention. Review the disputed amount, chargeback fees, reason codes if provided, response deadlines, reversals, and final outcomes. Rising chargebacks may signal fraud issues, unclear billing descriptors, shipping delays, product quality concerns, subscription cancellation problems, or documentation gaps.

Adjustments may correct earlier settlement errors, funding issues, or billing changes. Because adjustment descriptions can be vague, document them and ask for clarification when needed.

How to Audit PCI Compliance Fees

PCI compliance fees, PCI non-compliance fees, security fees, and related charges may appear on a merchant services statement. These fees are tied to payment data security programs, compliance validation, or non-compliance status.

During the audit, check whether a PCI compliance fee was expected under your pricing terms. Then verify whether any PCI non-compliance fee appeared. A non-compliance fee may mean the account has not completed required validation steps, such as a questionnaire or security scan, depending on the business setup.

PCI-related fees should not be ignored because they can recur monthly. If the business believes it is compliant but the statement shows a non-compliance fee, contact the appropriate support channel and request written confirmation of what is missing.

It is also important to separate fee review from security responsibility. Paying a fee does not automatically mean payment data practices are complete. Merchants that store, process, or transmit cardholder data should understand the applicable security requirements and maintain appropriate records.

For more background, the official payment data security standards resource explains how payment data security standards are developed and maintained.

How to Audit Gateway, Equipment, and Software Fees

Gateway fees, virtual terminal fees, recurring billing fees, equipment leases, terminal rentals, POS software costs, mobile reader fees, plugin fees, and integration charges can be easy to overlook because they may appear as small monthly amounts.

Start by listing every recurring fee on the merchant account statement. Then compare each fee with the services the business actually uses. If a gateway fee appears, confirm which website, invoice tool, or virtual terminal it supports. If a terminal rental appears, confirm that the device is active and assigned to the correct location.

Ecommerce merchants should pay close attention to gateway fees, tokenization fees, recurring billing fees, fraud tool fees, and plugin charges. Retail stores and restaurants should review POS software costs, terminal fees, mobile reader fees, and batch fees.

Recurring charges can become outdated. A business may change POS systems, stop using a gateway, replace equipment, or close a location while old charges continue. These small amounts can add up over time.

Internal guides on payment processing cost basics and choosing a POS system can help merchants understand how software, hardware, and processing services may connect.

How to Compare Statements Month to Month

A single statement shows activity for one billing period. Comparing statements month to month shows trends. This is where a merchant statement audit becomes more useful for managing payment processing costs.

Track the same numbers every month: processing volume, transaction count, average ticket size, total fees, effective rate, refunds, chargebacks, gateway fees, PCI fees, monthly fees, batch fees, authorization fees, and net deposits.

Then compare those numbers with business activity. Did sales increase? Did ecommerce payments grow? Did card-present transactions decline? Did a new POS system launch? Did a promotion create more small-ticket transactions? Did chargebacks come from one product, location, or sales channel?

If effective rate increases, look for the cause. It may be lower volume, smaller average ticket size, more card-not-present transactions, increased chargebacks, higher gateway fees, new PCI charges, or changed pricing.

Month-to-month review also helps identify billing changes quickly. A new monthly fee may be small, but if it repeats every statement, it becomes part of the ongoing cost structure.

Red Flags to Look for During a Merchant Statement Audit

A merchant statement audit should include a red flag review. Red flags do not always prove an error, but they show where merchants should investigate.

One common red flag is a sudden increase in effective processing rate without a clear change in volume, transaction count, card mix, or sales channel. Another is a new fee that was not explained, such as a PCI non-compliance fee, gateway fee, statement fee, monthly service charge, or equipment fee.

High non-qualified fees may indicate downgrades, keyed entries, delayed settlement, missing transaction data, or a change in card mix. Duplicate charges may appear when two similar fees are billed for the same service.

Funding issues are also important. Missing deposits, unexpected reserve deductions, unexplained adjustments, or deposits that do not match bank records should be researched promptly.

Chargeback increases are another warning sign. A rising dispute count can affect cash flow, increase fees, and create account risk. It may also reveal customer service, fraud prevention, delivery, or billing descriptor issues.

Other red flags include unexpected retrieval fees, inactive equipment charges, changed gateway fees, rising authorization fees, unexplained batch fees, or statement line items with vague descriptions.

Monthly Merchant Statement Audit Comparison Table

Audit Area	Normal Review Item	Possible Red Flag	Action Step
Processing volume	Compare statement to sales reports	Volume mismatch	Check date ranges, batches, and channels
Transaction count	Compare to POS or gateway count	Count jumps unexpectedly	Review duplicate sales, authorizations, or reporting
Average ticket size	Compare with prior months	Sharp decrease	Check promotion activity or small-ticket growth
Deposits	Match funding summary to bank	Missing or reduced deposit	Trace refunds, chargebacks, reserves, and timing
Refunds	Compare to refund records	Refunds unusually high	Review approval process and return policy
Chargebacks	Review dispute count and fees	Chargebacks increasing	Investigate reason codes and documentation
Fees	Review total and categories	New or duplicate fee	Request written explanation
Effective rate	Compare month to month	Rate rises without reason	Review volume, card mix, and new charges
PCI charges	Check compliance-related fees	Non-compliance fee appears	Confirm compliance status
Gateway charges	Review online payment fees	Fee for unused gateway	Confirm active services
Equipment charges	Review terminal or reader fees	Billing for inactive device	Match charges to equipment inventory
Adjustments	Review corrections and reserves	Vague deduction	Ask for detail and keep records

This comparison table is useful for finance teams, bookkeepers, and owners who want a consistent review process without rebuilding the audit from scratch every month.

How to Reconcile Merchant Statements With Accounting Records

Reconciliation connects the merchant statement, bank deposits, POS reports, ecommerce orders, gateway reports, refunds, chargebacks, fees, batches, settlement dates, and accounting software entries.

Start with sales records. Use POS reports or ecommerce reports to confirm gross sales and transaction activity. Then compare card sales to the merchant processing statement. Separate cash sales, gift cards, third-party payments, invoices, and other tender types so card volume is not overstated.

Next, match deposits. Use the funding summary to connect batch settlement activity with bank account deposits. Record timing differences clearly, especially when transactions settle near the end of the statement period.

Then record fees. Depending on how the processor deducts fees, they may reduce daily deposits or appear as a monthly debit. Accounting entries should reflect processing fees separately from sales so financial reports show both revenue and expense accurately.

Refunds and chargebacks should also be reconciled separately. A refund reduces revenue or creates a contra-revenue entry depending on accounting setup. A chargeback may need to be recorded as a reduction of sales, bad debt, dispute expense, or another category based on professional guidance.

This process helps prevent common errors, such as recording net deposits as sales, missing processing fees, double-counting refunds, or overlooking chargeback deductions.

Card-Present vs Card-Not-Present Audit Considerations

Card-present and card-not-present transactions often have different costs, fraud exposure, and statement patterns. A strong monthly statement audit checklist should separate these transaction types whenever the statement provides enough detail.

Card-present transactions happen when the customer pays in person through a terminal, POS system, chip card, contactless card, or mobile wallet. These transactions may have different risk and authentication characteristics than keyed or online payments.

Card-not-present transactions include ecommerce payments, invoice payments, virtual terminal payments, keyed transactions, recurring billing, and phone orders. These transactions may involve additional gateway fees, fraud screening fees, address verification, security code checks, tokenization, and higher dispute exposure.

During the audit, compare card-present volume and card-not-present volume with actual business activity. If card-not-present volume increases, the effective processing rate may increase too. This does not automatically mean billing is wrong, but it should be understood.

Also review fraud and dispute patterns by channel. Ecommerce payments may require stronger checkout controls, clearer billing descriptors, delivery confirmation, and better refund communication. POS payments may require proper terminal setup, staff training, and secure handling of fallback or keyed entries.

For more context on payment acceptance tools and sales channels, review this educational overview of merchant services features.

Common Mistakes Merchants Make During Statement Audits

Many merchants make statement audit mistakes because they are busy, the statement is difficult to read, or the bank deposit appears to be the only number that matters. Unfortunately, these shortcuts can hide errors and cost changes.

The most common mistake is reviewing only deposits. Deposits are important, but they do not show the full picture. A deposit may already reflect refunds, chargebacks, deducted fees, reserves, and adjustments.

Another mistake is ignoring small recurring fees. Monthly fees, statement fees, gateway fees, PCI fees, equipment fees, and software charges may look minor, but recurring charges can become meaningful over time.

Some merchants do not calculate effective rate. Without this number, it is harder to compare the true cost of payment processing month to month.

Others confuse gross sales with net deposits. This can create accounting problems because sales, fees, refunds, and chargebacks should not be treated as one blended deposit number.

Merchants may also misunderstand pricing models. A low discount rate does not necessarily mean low total cost if transaction fees, authorization fees, gateway fees, and monthly charges are high.

Fee Review Mistakes

Fee review mistakes often begin with focusing only on the largest line item. While interchange fees and discount fees matter, smaller line items can also affect total cost.

Merchants may overlook authorization fees, batch fees, statement fees, gateway fees, PCI compliance fees, non-compliance fees, equipment charges, retrieval fees, and chargeback fees. These charges can be easy to miss when they appear across different sections of the statement.

Another mistake is assuming every fee is new or unnecessary. Some fees may be pass-through costs tied to interchange or assessments, while others may be provider-controlled markup. The audit should identify and classify fees before drawing conclusions.

Finally, merchants may fail to compare current fees with prior statements. A fee that looks normal by itself may be unusual if it just appeared or increased.

Reconciliation Mistakes

Reconciliation mistakes usually happen when timing differences are ignored. Sales date, batch date, settlement date, funding date, and bank posting date may all differ.

Merchants may also use bank deposits as the only sales source. This can understate gross sales because deposits may already be reduced by refunds, chargebacks, fees, reserves, or adjustments.

Another common issue is failing to reconcile refunds and chargebacks separately. Refunds may appear in POS reports, ecommerce reports, gateway reports, and merchant statements at different times. Chargebacks may remove funds long after the original sale.

A clean reconciliation process should track gross sales, refunds, fees, chargebacks, reserves, adjustments, and net deposits as separate items.

Questions to Ask During a Merchant Services Statement Audit

A good merchant services statement audit includes specific questions. These questions help merchants move from passive statement review to active cost and cash flow management.

Ask these questions every month:

• What is my total processing volume?
• What is my total transaction count?
• What is my average ticket size?
• 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?
• Did any new fees appear this month?
• Did any existing fees increase?
• Are gateway fees, monthly fees, and equipment fees expected?
• Are PCI compliance fees or non-compliance fees appearing?
• Did chargebacks increase?
• Did refunds increase?
• Do deposits match bank records?
• Were any reserves or adjustments deducted?
• Did my pricing model change?
• Are card-present and card-not-present transactions reported correctly?
• Are all statement questions documented?

If you cannot answer these questions from the statement, ask for clarification. A merchant account statement should help you understand payment activity, not leave you guessing.

Monthly Statement Audit Checklist for Merchants

Use this monthly statement audit checklist as the final review before filing the statement. It works for retail stores, restaurants, ecommerce sellers, service providers, mobile businesses, and finance teams.

• Statement period confirmed
• Merchant account statement saved
• Total processing volume reviewed
• Gross sales compared with internal reports
• Net sales reviewed
• Transaction count reviewed
• Average ticket size calculated
• Card-present transactions reviewed
• Card-not-present transactions reviewed
• Ecommerce payments reviewed
• POS payments reviewed
• Refunds reviewed
• Voids reviewed
• Chargebacks reviewed
• Retrieval fees checked
• Deposits matched to bank records
• Funding summary reviewed
• Batch settlement activity checked
• Net deposits confirmed
• Adjustments reviewed
• Reserves reviewed
• Total fees identified
• Effective rate calculated
• Effective processing rate compared with prior months
• Interchange fees reviewed
• Assessment fees reviewed
• Card brand fees reviewed
• Processor markup reviewed
• Discount rate reviewed
• Transaction fees reviewed
• Authorization fees reviewed
• Batch fees reviewed
• Monthly fees reviewed
• Gateway fees reviewed
• PCI compliance fees reviewed
• Statement fees reviewed
• Chargeback fees reviewed
• Equipment fees reviewed
• Software fees reviewed
• New fees reviewed
• Duplicate charges checked
• Prior-month comparison completed
• Questions documented
• Statement saved for records

This checklist can be copied into a spreadsheet or accounting workflow. The more consistently it is used, the easier it becomes to spot trends and unusual changes.

When to Get Help With a Merchant Statement Audit

Some merchants can review statements internally. Others may benefit from help from an accountant, bookkeeper, financial advisor, payment consultant, or knowledgeable payment professional.

Consider getting help if the statement is difficult to understand, fees increased without explanation, chargebacks are frequent, reconciliation does not balance, deposits are missing, reserves appear unexpectedly, or pricing terms are unclear.

High-volume merchants may also benefit from a more detailed merchant statement analysis because small rate changes can have a larger financial impact. Businesses with multiple locations, multiple gateways, ecommerce payments, subscription billing, or several merchant accounts may need a more structured reconciliation process.

Professional guidance can also help when contract language, pricing models, or accounting treatment is confusing. For example, a bookkeeper may help classify fees and reconcile deposits, while a payment specialist may help interpret interchange, assessments, and processor markup.

This guide is educational and should not replace legal, tax, accounting, or compliance advice. When a statement issue could affect financial reporting, taxes, contracts, disputes, or compliance obligations, consult the appropriate qualified professional.

Best Practices for Ongoing Monthly Statement Audits

The best audits are consistent, documented, and simple enough to repeat. A monthly statement audit checklist should become part of the closing process for every billing period.

Save every monthly merchant statement in a secure folder. Keep related documents nearby, including POS reports, ecommerce reports, gateway reports, bank records, refund records, chargeback notices, and pricing documents.

Calculate effective rate every month. Then compare it with volume, transaction count, average ticket size, card mix, refunds, chargebacks, and sales channel activity. This helps you understand whether cost changes are caused by pricing, business activity, or unusual fees.

Review PCI status regularly. If PCI non-compliance fees appear, address them quickly and keep documentation. Also review gateway, equipment, and software fees to make sure the business is not paying for unused tools.

Ask for written explanations when something is unclear. Verbal answers can be forgotten, but written notes help support future audits.

Internal resources on merchant account selection mistakes can also help merchants understand why pricing structure, contract terms, and hidden fees deserve careful review.

Conclusion

A monthly statement audit checklist helps merchants review the full story behind card payments. It supports better visibility into gross sales, net deposits, refunds, chargebacks, reserves, adjustments, merchant statement fees, and total payment processing fees.

The most useful audit process is consistent. Review each monthly merchant statement, calculate effective rate, compare trends, reconcile deposits, investigate unusual fees, and keep accurate records. When questions come up, document them and ask for clear written explanations.

By following a structured monthly statement audit checklist, merchants can better understand processing costs, protect cash flow, improve reconciliation, and make more informed payment decisions.