Credit card processor statements sit in a blind spot during many acquisition reviews. The seller provides revenue figures—sometimes audited, often just tax return numbers—and a buyer may cross-check those against bank deposits or customer invoices. But the processor statement is where the actual credit card volume lives, and it rarely appears in a diligence file. That gap costs time, and worse, it leaves real revenue discrepancies unspotted until after close.
Does this sound familiar? You’re weeks away from a full Quality of Earnings report and need a faster first read. See how the platform organizes EBITDA and SDE for your own review — free trial, no credit card needed.
For any deal where card payments represent material revenue—especially retail, e-commerce, hospitality, SaaS with card-billing, or service businesses—processor statements are a third-party validation layer that should rank alongside bank feeds and tax returns in your proof-of-cash workpaper. They’re not a substitute for those sources, but they answer a specific question: how much money actually flowed through the payment network that the seller can’t easily hide or misreport?
Why Processor Statements Matter in Diligence
A processor statement is issued monthly by the merchant services provider (Stripe, Square, PayPal, a traditional acquirer like Chase Paymentech, etc.). It shows settled card transactions, fees, chargebacks, and refunds—the complete accounting of card volume that hit the merchant’s account. Unlike a P&L or income statement, which the seller controls and can massage, the processor has already moved money into the merchant’s bank account. It’s a third-party record.
In a normalized EBITDA or SDE calculation, revenue is often the largest line item and the easiest to misstate. A seller might claim $2.5M in annual revenue but only have $2.3M in actual card deposits. The difference might be rounding, cash sales not deposited, or refunds deferred. A processor statement cuts through the ambiguity. It shows exactly what the payment network recorded, and you can reconcile it to bank deposits in minutes.
This matters for two reasons. First, it catches material misstatement early—before you’re negotiating earn-outs or post-close disputes. Second, it helps you normalize non-recurring items. If the seller had a chargeback spike in Q4, or a one-time refund for a large return, the processor statement shows the month and amount, so you can evaluate whether it’s structural or noise.
The Reconciliation Method: Processor to Bank Deposits
The standard diligence approach is straightforward: pull 12 months of processor statements and reconcile the settled deposits to bank transactions. Here’s the working method.
Step 1: Export the monthly settled volume. Most processors allow you to download a summary or detailed report showing total settled card transactions per month. This is the gross card volume that the processor sent to the merchant’s bank account. Note that this is pre-fee—the merchant may have paid 2.9% + $0.30 per transaction or higher, depending on their rate.
Step 2: Identify and subtract processor fees and chargebacks. The processor statement typically breaks out monthly fees (batch fees, monthly minimums, PCI compliance fees, etc.), interchange and assessment fees (these are often baked into the net deposit but should be visible in a detailed report), and chargebacks or customer disputes. Subtract these from the gross settled volume to arrive at the net deposit that should have hit the bank account.
Step 3: Cross-check to actual bank deposits. Pull the bank statement for the same period and find the deposits from the processor or merchant services provider. Match the date and amount. If the processor statement says $47,300 was deposited on the 15th, the bank should show a deposit from the processor of approximately $47,300 on the same day (allowing for funding lag—some processors fund same-day, others fund next-business-day).
Step 4: Reconcile differences. Any material variance—more than 2-3% of monthly volume, or any unexplained missing months—needs an explanation. Common reasons include:
- Multiple processors: The seller may have been using Stripe, Square, and an in-house PIN pad payment system in parallel. You need statements from all of them.
- Delayed settlements or holds: Some processors hold a reserve (1-5% of volume) for risk. That reserve sits in the processor’s account, not the merchant’s, until the hold is released.
- Refunds applied in different periods: A card transaction might settle in Month 1, but the refund posts in Month 3. The processor statement shows the refund when it posts, not when the sale occurred.
- Non-card revenue mixed into bank deposits: The merchant may have received check payments, ACH payments, or cash that appear in the same bank account. The processor statement only shows cards, so you’ll see more in the bank account than the processor statement.
A Concrete Example: The Three-Month Variance
Imagine you’re reviewing a small e-commerce business. The seller’s tax return claims $1.8M in revenue for the year. You pull 12 months of Stripe statements and bank deposits. Months 1–9 reconcile cleanly: Stripe shows ~$147K–$152K per month in settled card volume, the bank account receives deposits matching that range. But Months 10–12 show a discrepancy. Stripe statements show $156K (Oct), $163K (Nov), $204K (Dec), totaling $523K for Q4. But the bank deposits from Stripe in those same months total only $489K—a variance of $34K, or 6.5%.
You ask the seller. They explain that they were testing a new payment system in late September and October, so they split volume between Stripe and a second processor (say, Square). They switched fully to Square in November and December. You request Square statements for October–December. Square shows $12K (Oct), $48K (Nov), $61K (Dec). Now the full card picture is Stripe $156K + Square $12K = $168K for October, which still doesn’t reconcile to bank deposits for that month.
Further digging reveals a $25K hold that Stripe placed on the merchant’s account in early October due to a sudden spike in volume and chargeback risk. Stripe released the hold on the 5th of November, and that $25K posted to the bank account in November. Once you adjust for the hold timing, all months reconcile within 2%—well within normal variance.
This scenario took 30 minutes to resolve with clear statements, but without processor documentation, you’d have written off the variance as “unclear revenue” or lost it entirely. A normalized EBITDA calculation would have been understated by $34K, affecting the offer price by 4–6x that amount depending on the multiple.
Red Flags and Edge Cases
Missing or incomplete statements. If the seller can’t produce processor statements for the full diligence period, that’s a major warning. Payment processing is automatic and heavily regulated—statements are archived for years. Absence suggests either intentional hiding, processor turnover with poor recordkeeping, or the volume was lower than claimed and the seller didn’t want to disclose it.
Frequency or volume spikes with no business explanation. A processor statement might show $80K in volume for 11 months, then $320K in Month 12. That’s a 4x spike. If the seller can’t tie it to a Black Friday promotion, a seasonal event, or a one-time bulk order, it may indicate fraudulent or test transactions the seller later reversed or wrote off.
High chargeback or refund rates. If the processor statement shows chargebacks or refunds consistently above 2–3% of volume, that’s abnormal for most industries and signals either product quality issues, customer disputes, or payment disputes (which may recur post-acquisition and eat into EBITDA).
Multiple processor relationships without clear reason. A small business using Stripe, Square, and PayPal simultaneously, with material volume in each, suggests either failed migration (data quality risk) or intentional distribution to obscure total volume from tax authorities or a lender.
Processor statements that don’t match seller’s claimed card-to-cash ratio. Some sellers claim “80% of revenue is card” but the processor statements show only 55%. That variance means either non-card revenue (checks, ACH, cash) was understated, or card revenue was overstated in the seller’s narrative. Both need clarification.
What to Include in Your Checklist
When you receive processor statements or request them, use this checklist to ensure completeness:
- Statements cover the full 12-month diligence period (or at least the most recent complete 12 months available).
- Statements identify the processor name, merchant account number, and account holder (should match the legal entity being acquired).
- Monthly totals include: gross settled volume, interchange/assessment fees, processor fees, chargebacks, and net deposit to bank.
- Bank statements for the same period show deposits from the processor (or processors, if multiple) matching the net deposit line from the processor statement.
- Any hold, reserve, or delayed settlement is documented and adjusted for in your reconciliation.
- If the seller migrated processors during the diligence period, you have statements from both (or all) processors covering the periods they were active.
- The seller or their accountant can explain any variance greater than 2% between processor statements and bank deposits.
Integration with Normalized EBITDA
Once you’ve reconciled processor statements to bank deposits and confirmed the revenue base, that reconciled total becomes your starting point for normalized EBITDA. If the seller’s claimed revenue was $1.8M but processor statements + other third-party sources total $1.65M, you’re working with $1.65M as your normalized revenue floor. Any normalization adds or deducts from that verified base, not from the seller’s claimed number.
This disciplined approach—validate revenue against third-party processor data, then normalize from there—compresses the range of post-close surprise. It also gives you a defensible position if you renegotiate the purchase price or earn-out after discovering discrepancies.
Processor statements are one layer of a robust revenue verification stack. Bank feeds, customer lists, subscription billing records, and tax returns remain essential. But when cards are material to the business, processor statements are the most direct line from transaction reality to cash in the bank. Skipping them invites the exact kind of revenue misstatement that kills deals or begets post-close disputes.
This article is educational and does not constitute M&A, investment, or accounting advice — confirm findings with a licensed CPA or M&A advisor before making an offer.
Frequently Asked Questions
What if the seller doesn’t have processor statements?
Request them immediately from the processor directly using the merchant account number or the seller’s legal entity name. Most processors retain statements for 5–7 years and will send them to an authorized representative at no cost. If the seller claims they can’t access them or the processor has no record, that’s a material red flag suggesting either data loss, account mismanagement, or fraud. Do not proceed with a revenue figure based solely on tax returns or seller-provided summaries if processor statements are unavailable.
How do I reconcile processor statements if the business uses multiple payment systems (e.g., Stripe, Square, and PayPal)?
Pull statements from each processor separately and sum them by month. Then reconcile the combined total to the bank deposits for that month, accounting for separate settlement schedules (Stripe might fund daily, Square weekly). You may see multiple deposits in a single day from different processors, so organize by deposit date and match line-by-line. Create a summary table showing total card volume by month across all processors, then compare to total bank deposits from all sources (including non-card payments).
What is a normal variance between processor statements and bank deposits?
Variance of 0–2% is typical and usually explained by timing (a deposit posted on the last day of the month in the bank statement but was recorded in the processor statement as the prior month). Variance of 2–5% warrants investigation—it could be explained by holds, reserves, or delayed refunds. Variance above 5% in any single month is abnormal and must be explained in writing by the seller or their accountant before you finalize normalized revenue.
Should processor statements affect the purchase price or EBITDA multiple?
Processor statements affect the normalized revenue base, which is the numerator in your valuation. If processor-verified revenue is materially lower than the seller’s claim, your normalized EBITDA is lower, and so is the purchase price (assuming a consistent multiple). The multiple itself is set by market conditions, comparable transactions, and deal risk—processor statements don’t change the multiple, but they do change the cash flow base the multiple is applied to.
What if processor statements show recurring chargebacks or refunds that seem abnormal?
High chargebacks or refunds (consistently above 2–3% per month) suggest either product or service quality issues, customer disputes, or return/satisfaction problems that may recur post-acquisition. These are structural revenue risks, not anomalies. Build them into your normalized EBITDA as a permanent reduction to gross card volume, or require the seller to warrant and indemnify chargeback levels post-close. Request a detailed breakdown of the top 5–10 chargebacks or refunds to understand whether they were customer disputes, fraud, or operational errors.
This article is educational and does not constitute M&A, investment, or accounting advice — confirm findings with a licensed CPA or M&A advisor before making an offer.
See how IncomeReady organizes normalized EBITDA and SDE before you make an offer.
