To record merchant processing fees correctly, book card sales at the gross amount the customer paid and book the processor's charges as a separate expense, whether the processor takes them from each deposit or debits them once a month. The fee total for the month should then agree with the processor's monthly statement.
Gross or net: two ways to book merchant processing fees
Merchant processing fees can be booked gross, with full sales and a separate fee expense, or net, with only the deposit amount recorded as sales. Gross recording is the method that keeps revenue complete and makes the fee a visible cost. Net recording is faster, but it removes information the owner and the tax preparer both need.
The difference is easiest to see with one day of example card sales of 2,000.00 and a fee of 58.00 taken from the deposit. The bank receives 1,942.00 either way. The two methods record it like this:
| Method (example) | Bank | Card sales | Merchant fee expense |
|---|---|---|---|
| Gross | Debit 1,942.00 | Credit 2,000.00 | Debit 58.00 |
| Net | Debit 1,942.00 | Credit 1,942.00 | none |
Both entries balance, and both agree with the bank. Only the gross entry agrees with the sales report, and only the gross entry shows that taking cards cost 58.00 that day.
Which merchant processing fees go to which expense account?
Most businesses need one expense account for merchant processing fees, and a second only when a fee type is large enough to manage on its own. Split the processor statement into a few groups so a rise in cost points to its cause, rather than creating an account for every line the processor prints.
A workable mapping, offered as an example:
| Fee group | What the statement may call it | Example account |
|---|---|---|
| Transaction costs | Interchange, assessments, per-item or discount fees | Merchant fees: transaction |
| Fixed monthly costs | Statement fee, account fee, minimum fee, gateway fee | Merchant fees: monthly |
| Incident fees | Chargeback fee, retrieval fee, returned item fee | Merchant fees: incidents |
| Equipment | Terminal rental or lease | Equipment rental, not merchant fees |
Incident fees deserve their own line because they track a business problem, not sales volume. A month with many chargeback fees usually has disputed sales behind it, and those disputes need their own work, covered in how to reconcile chargebacks.
Recording merchant processing fees from the monthly processor statement
The monthly processor statement is the source document for merchant processing fees. Total its fees by group, compare that total to what reached the books during the month, and post the difference. If the processor debits fees in one line early the next month, accrue them so the expense lands in the month the sales happened.
The steps for a processor that bills monthly:
- Total the fees on the statement for the month, by group.
- Find the single fee debit on the next month's bank statement and confirm it equals that total.
- At month end, if the debit has not posted, record the accrual: debit merchant fee expense, credit accrued liabilities, for the statement total.
- When the debit clears, debit accrued liabilities and credit the bank.
For a processor that takes fees from each deposit, the steps are shorter. Add up the fees taken from each deposit during the month and check that the sum equals the statement. A difference usually means one deposit was booked at net, or the statement includes a monthly charge that was debited separately.
Some businesses run card deposits into one account while the processor debits fees from another, for example in a structure where subsidiary accounts sweep to a concentration account each night. In that case the fee debit has to be found on the right account before it can be matched. Zero balance account reconciliation explains how to follow money through those sweeps.
Why does net recording of merchant processing fees hide revenue?
Net recording hides revenue because the amount booked as sales is already reduced by the fees, so the books report less than customers paid. The missing amount is still an expense, but it never appears as one. The ledger then fails to agree with the processor's sales reports and with the gross figure the processor reports to the IRS.
The tax reporting point is the one that tends to surface later. The IRS page on what to do with Form 1099-K says the gross amount on the form isn't adjusted for fees, credits, refunds, shipping, cash equivalents or discounts. A business that books card sales at net will see a 1099-K larger than its recorded sales, and someone will have to explain the gap at tax time. With gross recording, the gap shrinks to refunds, timing and the other listed items, each of which the books already show.
There is a management cost as well. An owner reading a net profit and loss statement sees no merchant fee line, so a processor price increase or a shift to costlier card types goes unnoticed.
Charges near merchant processing fees that are not fee expense
Several amounts on a processor statement look like merchant processing fees but are not expenses. A chargeback reverses a sale, a returned bank payment reverses a receipt, and a reserve is money the processor is holding, not money spent. Booking any of them to fee expense overstates the cost of processing and leaves a receivable or a sales reversal unrecorded.
Treat them this way:
- Chargeback amount: reduce sales or record a receivable while the dispute is open. Only the separate chargeback fee is an expense.
- Returned ACH payment: reverse the customer receipt and reopen the invoice. ACH return reconciliation covers the return codes and the follow-up.
- Reserve withheld: record an asset for the amount held, and reduce it as the processor releases funds.
- Fee refund or credit: reduce merchant fee expense in the month the credit appears.
Matching all of this by hand is slow when a client has several processors. PreciseBankFlow reads the bank statement and lists every debit that has no ledger entry behind it, so an unbooked monthly fee debit shows up as an exception before you close. The PreciseBankFlow homepage describes the checks it runs.