← All Posts

Blog

The Payout Isn't the Sale

A lot of owners who take card payments through Stripe or Square record income the same way: a deposit shows up in the bank feed, it plainly came from customers, so it gets categorized as sales. It’s a reasonable instinct. The money is real, it’s sitting in the account, and the bank feed is the one part of the books that never forgets to show up for work. If the deposit matched what customers paid, this would be a perfectly good system.

Test it against a single week, though, and it starts to wobble.

Here’s a composite with invented figures, for a consultant who bills clients through invoices they pay by card. Three clients paid this week: $1,850.00, $640.00, and $412.50, for $2,902.50 in total. The processor kept $85.14 in fees across those three payments and sent the rest to the bank as one deposit: $2,817.36.

Categorize that deposit as sales and the books say the business brought in $2,817.36 this week, when clients paid $2,902.50. The fees, which are a real cost of getting paid, don’t appear anywhere. Eighty-five dollars sounds like a rounding error until it happens every week. Over a year, that gap can grow into a figure you’d very much like to see when you’re comparing processors or deciding whether to pass card fees along, and books kept this way will never show it to you.

Why the deposit never lines up

Processors pay out on their own schedule, and they usually pay out net. Square’s fee guide says its processing fees are deducted before funds are transferred to your linked bank account. Timing blurs things further. Stripe’s payout documentation counts settlement in business days for US accounts, and its own example puts day 0 for a Saturday charge on the following Monday. Square’s transfer options page says payments accepted on a Friday before 5 PM PT post to your bank by Monday morning, depending on your bank’s processing speed. The date on a deposit tells you when the money moved, which isn’t always the day a client paid.

The deposit can even run backward. According to the same Stripe page, if refunds outweigh new payments and your balance goes negative, Stripe can create a payout that debits your bank account. That’s an awkward line to categorize as sales.

Then the software adds its own wrinkle. QuickBooks’ guide to matching bank transactions says it won’t suggest a match when bank fees change the total amount or when multiple payments were deposited together as a single group, which describes most processor payouts. With no match offered, the owner clicks Categorize, and the same guide notes that categorizing creates a brand-new record. If those three invoices were already marked paid, the week’s income gets counted a second time; Intuit’s duplicate transactions guide covers this under “Income is doubled.” Inflated revenue feels wonderful right up until someone compares it to the bank statement.

Gross in, fees out, deposit in the middle

The fix is to record each sale at the amount the customer paid, record what the processor kept as an expense, and let the deposit be the thing that ties them together. Intuit’s guide to making bank deposits has you put payments you need to combine into Undeposited Funds, then create a bank deposit and check each one you want to group. Its walkthrough for third-party merchant fees adds the processor’s fee on that same deposit as a negative amount under “Add other funds to this deposit,” coded to the expense account you use for fees. For the consultant’s week, that’s three payments totaling $2,902.50, a fee line of negative $85.14, and a deposit of $2,817.36 that matches the bank to the penny while income stays where the invoices put it.

You need the breakdown to do any of that, and Stripe, for one, will hand it over. Its payout reconciliation report is built to match the payouts in your bank account with the batches of payments and other transactions they relate to, and its itemized download lists every payment, refund, dispute, and fee included in a payout. One limit is worth knowing: Stripe says the report covers accounts on automatic payouts, and if you trigger instant payouts yourself, reconciling those against your transaction history is your job.

For a business taking card payments most days, we’d usually reach for a clearing account instead. It’s a holding account named for the processor: gross payments go in, fees come out, and each payout moves money on to the bank, so its balance should equal whatever the processor is still holding for you. When those two numbers disagree, something (often a fee or a refund) hasn’t been booked. Either method works. The trouble starts when a business uses both, sometimes on the same payout, because that’s how one week’s sales get recorded once through the clearing account and again from the bank feed. If an app syncs your processor into your books, check its first few payouts by hand before you trust it; a sync that posts net deposits as income just makes the original mistake faster.

Back in the bank feed, that $2,817.36 is still one line with one tidy number. Recorded this way, it closes out a story the books now tell in full: $2,902.50 paid by three clients, $85.14 kept by the processor, and the rest in the bank where it belongs.


Bat City Books helps service-based small businesses record processor payouts so income, fees, and the bank all agree. If your bank feed is full of payout deposits that have been booked as sales, let’s talk.