To reconcile merchant processor deposits to card sales, start from the processor's payout report, not the bank statement. Each deposit is a net figure: gross card sales less processing fees, refunds, chargebacks and reserves. Gross each deposit up to those parts, match the parts to the sales records, and assign every batch to the month it was sold.
Why merchant processor deposits never equal the day's card sales
A merchant processor deposit is the net amount a card processor sends to the client's bank after it settles a batch of card sales. The day's card sales are a gross figure from the register or the online store. They differ because the processor deducts fees, refunds and chargebacks first and may pay several days at once.
Four things usually sit between the gross sales and the deposit:
- Processing fees. Most processors take their fee out of each batch rather than billing it separately, so the deposit is short by the fee.
- Refunds. A refund to a customer comes out of the next payout, not out of the day the original sale was made.
- Chargebacks. When a cardholder disputes a charge, the processor pulls the disputed amount back, often with a separate dispute fee.
- Batching and timing. A payout can cover one day, two days or a whole weekend, and it lands in the bank a day or more after the sales.
A bookkeeper who matches the bank deposit straight to a sales figure will find a small, irregular difference on almost every line. That difference is not an error. It is the fees, refunds and chargebacks, and it has to be recorded, not written off.
The general mechanics of pairing ledger lines with bank lines are covered in the guide to matching ledger entries to bank statement lines. This post deals with the one kind of line that never matches on amount alone.
Reading the processor payout report against bank deposits
A processor payout report is the document that lists, for each deposit, the sales, fees, refunds and other adjustments that make it up. It is the bridge between the sales records and the bank statement. Without it, a firm can only guess how a net deposit splits into sales and fees.
Processors name the report differently, but the content is similar. Stripe's documentation for its payout reconciliation report, for example, says the report helps you match the payouts in your bank account with the batches of payments they relate to. It groups the transactions in each payout by category, such as charges, refunds and fees, and an itemized download lists every payment, refund, dispute and fee included in the payout.
Ask the client for three things for the period being reconciled:
- The payout or settlement report for every payout dated in the period, plus the first few days after it.
- The sales summary from the register or store for the same days, showing card sales separately from cash.
- The bank statement for the account the payouts go to.
Then work payout by payout. Find the payout's net amount on the report and locate the matching deposit on the bank statement. The amounts should agree to the cent. Next, take the payout's gross sales figure and compare it with the card sales in the register summary for the days the payout covers. If both comparisons agree, the payout is proven: its net side ties to the bank and its gross side ties to the sales.
A payout that ties to the bank but not to the sales usually means the batch covers different days than you assumed. A payout that ties to the sales but not to the bank usually means a second adjustment, such as a dispute fee, that you have not yet found on the report. A deposit you cannot find on any payout report may not be a card deposit at all; it could be the client's own money moving between accounts, which the post on transfers between a client's own accounts covers.
A deposit that appears twice in the books is a separate problem. If a payout was recorded once from the bank feed and once from a sales summary, see duplicate and missing entries behind reconciliation differences.
How do you book processor fees, refunds and chargebacks from a net deposit?
Booking a net merchant deposit means recording the gross sales and each deduction separately, so the books show full sales and the cost of taking cards. The entry is a "gross-up": one debit to cash for the deposit, debits for fees, refunds and chargebacks, and one credit to sales for the gross amount.
Recording only the net deposit as sales understates both revenue and expenses by the same amount. Profit looks the same, but the income statement no longer agrees with the processor's reports or with Form 1099-K, and a reviewer cannot see what the client paid in card fees.
Worked example: one week of payouts for Juniper Lane Bakery
Juniper Lane Bakery is a fictional client. Every figure below is an example value. The bakery takes cards through one processor, which pays into checking account XXXX-4821. The week runs Monday, March 9, 2026 to Friday, March 13, 2026.
| Sale date (example values) | Gross card sales | Refund | Chargeback | Dispute fee | Processing fees | Paid in |
|---|---|---|---|---|---|---|
| Mon Mar 9 | $1,240.00 | $36.21 | Payout A | |||
| Tue Mar 10 | $985.50 | $28.78 | Payout A | |||
| Wed Mar 11 | $1,102.25 | $45.00 | $32.19 | Payout B | ||
| Thu Mar 12 | $1,318.75 | $120.00 | $15.00 | $38.51 | Payout B | |
| Fri Mar 13 | $1,653.50 | $48.28 | Payout C | |||
| Week total | $6,300.00 | $45.00 | $120.00 | $15.00 | $183.97 |
The three bank deposits on the March statement for XXXX-4821:
| Payout (example values) | Gross sales | Less refunds, chargebacks and fees | Net deposit | Bank date |
|---|---|---|---|---|
| Payout A | $2,225.50 | $64.99 | $2,160.51 | Wed Mar 11 |
| Payout B | $2,421.00 | $250.70 | $2,170.30 | Fri Mar 13 |
| Payout C | $1,653.50 | $48.28 | $1,605.22 | Mon Mar 16 |
| Total | $6,300.00 | $363.97 | $5,936.03 |
The week reconciles to a zero difference:
| Reconciliation (example values) | Amount |
|---|---|
| Gross card sales per register | $6,300.00 |
| Less refund | ($45.00) |
| Less chargeback | ($120.00) |
| Less dispute fee | ($15.00) |
| Less processing fees | ($183.97) |
| Expected deposits | $5,936.03 |
| Deposits per bank statement | $5,936.03 |
| Difference | $0.00 |
Payout B is the one with every kind of deduction. Its gross-up entry, dated March 13:
| Account (example values) | Debit | Credit |
|---|---|---|
| Checking XXXX-4821 | $2,170.30 | |
| Merchant processing fees ($70.70 fees plus $15.00 dispute fee) | $85.70 | |
| Sales refunds | $45.00 | |
| Chargebacks | $120.00 | |
| Card sales | $2,421.00 | |
| Total | $2,421.00 | $2,421.00 |
Some firms record daily card sales from the register into a clearing account first, then clear it when each payout lands. The credit in that case goes to the clearing account instead of card sales, and the clearing account should return to zero once every batch has paid. Either way, the debits and credits must agree with the payout report line for line. Which accounts the client uses for refunds and chargebacks is a decision for the firm and the client; the entry only has to show them.
Merchant settlement timing: weekend batches and payouts across month end
Merchant settlement timing is the gap between the day a card sale is made and the day its payout reaches the bank. Payouts usually lag sales by one or more business days, and a weekend's sales often arrive as one deposit. Each batch belongs to the month of its sales, even when the money lands in the next month.
Stripe's report documentation notes that it groups a payout by the estimated arrival date, not the date the bank posts the deposit, and that weekends, holidays and bank processing can affect when funds arrive. That is why the bank date and the processor's date for the same payout can differ by a day. Match on amount and the payout reference, not on date alone.
Month end is where timing matters. Suppose Juniper Lane Bakery's March 31 sales are paid on April 1. If the bakery records card sales from the register each day, the March books show those sales, and the money is owed by the processor at March 31. It is not yet in the bank and it is not yet a deposit the bakery has made, so it usually sits in a card clearing or receivable account at month end rather than on the bank reconciliation. If the bakery's books record a deposit dated March 31 that the bank posts on April 1, that line is a deposit in transit like any other. The post on what a deposit in transit is explains how those adjust the bank balance.
A useful month-end test: list every payout whose sales fall in the month, and check that each one either appears on the month's bank statement or is in the clearing balance. Anything left over is a payout you have not found yet.
Old timing items that never clear deserve their own review. A check that has sat outstanding for months is a different problem from a deposit, and the post on stale-dated and voided checks in a bank reconciliation covers it.
What happens when a processor holds a reserve on merchant deposits?
A reserve is money the processor keeps back from payouts to cover future refunds and chargebacks. It reduces each deposit, so the deposits fall short of sales less fees by the reserve amount. The withheld money still belongs to the client and should be tracked as an amount due from the processor until it is released.
Stripe's reserves FAQ describes a reserve as a temporary hold on a portion of a business's funds for a predetermined period. It says there are two types, fixed and rolling, and that reserve funds are released in full at the end of the reserve period unless they are used to cover a refund or dispute.
In the books, a reserve changes the gross-up entry by one line. If Payout B above had a $100.00 reserve held back, the deposit would be $2,070.30 instead of $2,170.30, and a $100.00 debit would go to an asset account such as "Processor reserve receivable." When the processor releases the reserve, the release arrives as part of a later payout, and that payout's entry credits the receivable.
Keep a running schedule of the reserve: amounts held, amounts released, and amounts used for refunds or disputes. The balance on the schedule should agree with the reserve balance the processor's dashboard or statement shows. A reserve receivable that only grows, with no releases, is worth raising with the client, because the processor may have applied it to disputes that were never recorded.
Tying a year of merchant processor deposits to Form 1099-K
Form 1099-K reports the gross card payments a processor handled for the client during the calendar year. Total bank deposits from that processor will be lower, because deposits are net. Proving the difference means listing the refunds, chargebacks, fees, reserves and year-end timing items that separate the two figures.
The IRS Instructions for Form 1099-K say the box 1a gross amount is the total dollar amount of reportable payment transactions, without regard to any adjustments for credits, cash equivalents, discount amounts, fees, refunded amounts, shipping amounts or any other amounts. The same instructions have boxes 5a through 5l report the gross amount for each month of the calendar year, which helps when one month does not tie.
Here is a year-end tie-out for Juniper Lane Bakery. All figures are example values for calendar year 2026. The fees line covers every 2026 sale, so the two year-end batches are shown at their net payout, and no reserve was held at January 1.
| 1099-K tie-out (example values) | Amount |
|---|---|
| Form 1099-K box 1a gross amount | $312,480.00 |
| Less refunds per processor reports | ($2,310.00) |
| Less chargebacks | ($640.00) |
| Less processing and dispute fees | ($9,061.92) |
| Less reserve still held at Dec 31, 2026 | ($1,500.00) |
| Less net payout for Dec 31, 2026 sales, paid Jan 4, 2027 | ($1,212.40) |
| Plus net payout for Dec 31, 2025 sales, paid Jan 2, 2026 | $1,045.75 |
| Expected 2026 processor deposits | $298,801.43 |
| Processor deposits per 2026 bank statements | $298,801.43 |
| Difference | $0.00 |
If a difference remains, compare month by month: total each month's payouts from the bank statements and set them against that month's box 5 amount less the month's refunds and fees. The month that does not tie is where the missing payout, unrecorded refund or second processor account sits. How the gross amount is treated on the return is a separate question for the preparer; the tie-out only shows that the books and the form describe the same money.
A tie-out like this needs all twelve bank statements for the account. Schema CPA reads each checking statement a client sends, ties its opening balance to the prior month's closing balance, and calls out a month that is missing from the run, so the deposit total starts from a full year. The workflow on the homepage shows how statements are collected and checked.