QuickBooks Online: Match Stripe Net Payouts from POS Sales Receipts
Your POS posts the full sale, Stripe keeps its fee, and the bank sees the net. This QuickBooks Online workflow matches the payout without double-counting.
When a point-of-sale app writes Sales Receipts into QuickBooks Online and Stripe pays out the net, the books and the bank tell two different stories. The receipt records the full sale, the processor keeps a fee, and the deposit that downloads is smaller than the amount you billed. Left alone, this setup either double-counts revenue or strands a balance in a clearing account. The fix is to let each system do one job, and to record the payout yourself.
The flow in three moves
First, the POS integration creates a Sales Receipt for everything the customer paid, including any card surcharge the customer covers. It deposits the full amount to a clearing account set up as Other Current Asset. Revenue is now recorded once, at gross, with all the product and service detail your POS maps.
Second, Stripe collects the charge, keeps its processing fee, and sends the remainder to your bank.
Third, that smaller deposit lands in Bank Transactions and needs to match something. The clearing account is the bridge that makes the third step work.
A worked example
Say a customer buys $332.50 of goods and pays a $9.94 card surcharge. The POS writes one Sales Receipt for $342.44, with the Deposit to field pointed at Stripe Clearing. Stripe’s fee on that charge is $20.81, so the bank deposit is $321.63.
Two different fees are in play, and they belong in different places. The $9.94 surcharge is income, part of the sale on the receipt. The $20.81 processing fee is your expense, and it belongs in a merchant fees account when the payout is recorded.
Should the Stripe connector create the sale too?
Not when the POS already writes the receipt. When both apps record the same charge, the sale lands twice and revenue doubles. One system must own the sale, and the POS is usually the right owner because it carries the revenue account detail.
If the connector offers a setting that limits it to payouts, use it. If it can only post full sales, the simplest path is to exclude or discard the sales it offers, or disconnect it and record payouts by hand as described below.
Why won’t the bank line match by itself?
Bank matching pairs a downloaded line with a recorded payment, deposit, transfer, or journal entry of the same amount within a date window. Your clearing account holds $342.44, but the bank received $321.63, so nothing is equal. A receipt deposited straight to a clearing account never creates a bank-side transaction to match against. Until you record the payout, the review list will keep offering a fresh deposit, which is exactly the duplicate you want to avoid.
Two clean ways to record the payout
Record the fee first. Post an expense or check paid from the Stripe Clearing account for $20.81, categorized to merchant fees. Then record a transfer of $321.63 from Stripe Clearing to the bank account, dated the day the money arrived. The downloaded bank line should now match that transfer; confirm it.
Prefer one entry? Post a journal entry dated the payout day: debit the bank account $321.63, debit merchant fees $20.81, and credit Stripe Clearing $342.44. Open the bank line, choose Find Match, widen the date range if needed, and match it to the entry.
Both routes leave revenue untouched. The sale was recorded once by the POS; these entries only move money and expense the fee.
Keep the clearing account at zero
After each payout cycle, open the Stripe Clearing register. It should return to zero, or hold only funds in transit between a sale and its payout. A growing positive balance usually means a payout was never recorded. A negative balance usually means a fee or payout was posted twice. Run the register after your first full month on this workflow: any leftover amount points straight to the entry that is missing.