Ecommerce bookkeeping means rebuilding sales from payouts. The bank statement shows one net deposit per payout, so take each channel's payout report, record product sales and shipping charged at their gross amounts, book fees, refunds and sales tax separately, and confirm the parts add up to the deposit. Then code shipping, inventory and app costs from the card statements.
Why don't ecommerce payouts equal ecommerce sales?
An ecommerce payout is what a store platform or marketplace sends to the seller's bank after subtracting what it is owed. Between the order total a customer paid and that deposit sit transaction fees, channel commissions, refunds, chargebacks, shipping labels bought through the platform, and sometimes a reserve. The deposit is a remainder, not a sales figure.
That gap is why an online store's bank statement is a poor revenue report on its own. A client selling through their own storefront and two marketplaces might see three or four deposit descriptions a week, each a different mix of orders. None of them says how many orders it covers or what the store paid to get them.
The gap also runs in the other direction. A payout can include money that is not income at all, such as sales tax the store collected and still owes to a state, or a reimbursement from the channel for a lost parcel. Treating every deposit as sales overstates revenue in those cases and buries a liability.
The fix is to book from the channel's own records and use the bank statement as the proof. Every payout in the channel report must appear as one deposit on the statement, and every channel deposit on the statement must appear in a report.
Turning one marketplace payout into ecommerce sales lines
One marketplace payout becomes one journal entry with several lines: product sales and shipping charged as income, sales tax as a liability, refunds and fees as their own debits, and the net payout as the bank deposit. The lines must balance to the amount on the bank statement, to the cent.
A worked payout
The figures below are an example of a single weekly payout from a marketplace, not data from a real store. In this example the store collects and remits its own sales tax for these orders.
| Payout line | Example amount |
|---|---|
| Product sales, 84 orders | 6,400.00 |
| Shipping charged to customers | 380.00 |
| Sales tax collected | 412.00 |
| Refunds issued, 3 orders | (260.00) |
| Transaction and channel fees | (231.75) |
| Net payout to bank | 6,700.25 |
The entry that records it:
| Account | Debit | Credit |
|---|---|---|
| Checking | 6,700.25 | |
| Sales refunds and returns | 260.00 | |
| Channel and payment fees | 231.75 | |
| Product sales | 6,400.00 | |
| Shipping income | 380.00 | |
| Sales tax payable | 412.00 | |
| Totals | 7,192.00 | 7,192.00 |
The match is the last step. Find the deposit of 6,700.25 on the bank statement within the payout's expected arrival window. If the bank shows a different amount, the payout report and the deposit are describing different payouts, or the channel made an adjustment after the report was pulled.
Card processors attached to a storefront follow the same pattern. The guide to payment processor statements in bookkeeping covers that entry for a single processor, including payouts that cross a month end.
Which ecommerce channel report should the books follow?
Each ecommerce channel has its own payout report, and the books should follow the one that lists payouts with their component transactions, not a sales report that counts orders by order date. Only a payout-level report ties to the bank, because it groups orders the same way the deposit does.
For a store on Shopify Payments, the Shopify Help Center page on payouts points to the Shopify Payments activity report as the place to review a breakdown of transactions, fees and payouts. Marketplaces publish their own equivalents under names such as settlement report, disbursement report or payments report.
Setting up channel reports per client
For each store client, write down once:
- Every channel the client sells through, including small ones such as a wholesale portal or a craft fair card reader.
- The name of the payout report in each channel, and who on the client side can export it.
- The deposit description each channel uses on the bank statement, so a payout can be recognized at a glance.
- Whether each channel remits sales tax itself or passes it to the store.
The last item changes the entry. Where a marketplace collects and remits tax for the seller, tax should not appear as a liability in the store's books at all. Read the report to see which one applies rather than assuming.
Collecting those exports every month is the slow part of ecommerce work. A client portal for bookkeepers gives the store owner one place to drop the reports, instead of a thread of emails with attachments.
Ecommerce refunds and chargebacks larger than a payout
An ecommerce refund normally comes out of the next payout, so the deposit is just smaller. When refunds or chargebacks for a period exceed the sales in it, the channel either holds the negative balance against future sales or debits the seller's bank account directly. That debit is the line that confuses a month.
A store debit from a channel looks like an expense on the statement, but it is not one. It is the settlement of a negative balance: refunds, a chargeback, or fees that sales did not cover. Code it against the same accounts the payout would have used, from the channel report for that period.
Chargebacks need their own treatment because they can reverse. A customer disputes a charge, the channel pulls the money and a fee, and weeks later the seller may win the dispute and get the money back. The walkthrough on recording a chargeback and its reversal has the two entries.
Seasonal refund waves
Online stores often see a wave of returns after a holiday sales peak. In the month after the peak, refunds can exceed new sales on a channel, and the payout report may show a negative balance carried forward. Note the carried amount at month end, because it is money the store owes the channel, and it belongs on the balance sheet as a payable rather than disappearing until the next payout.
Ecommerce reserves and balances held at month end
An ecommerce reserve is part of the seller's balance that a channel holds back instead of paying out, often for new sellers, for high refund rates or for products shipped weeks after the order. Reserved money is the store's asset. It has been earned but not deposited, so it needs a balance sheet account.
Create one clearing account per channel, such as "Marketplace A balance held." Each payout entry then runs through it: sales and fees go in, the deposit comes out. At month end, the clearing account balance should equal what the channel's report says it is holding, including any reserve and any sales not yet paid out.
This matters most at year end. A store with a large December can have thousands in a channel balance on December 31. Without a clearing account, those sales slip into January in the books, even though the store earned them in December.
Holding money that belongs to others is a theme across industries, and the handling differs. A store's channel balance is its own money held by someone else. The post on law firm bookkeeping covers the opposite case, client money the firm holds and must keep separate from its own operating funds.
Ecommerce shipping, inventory and app costs on card statements
The cost side of an ecommerce business mostly shows up on the owner's credit card and the business checking account, not in the payout. Shipping labels, inventory purchases, packaging, advertising, and the stack of monthly app subscriptions a storefront collects all need accounts that let the owner see margin per order.
A workable chart of accounts for a small online store keeps these separate:
- Inventory purchases, recorded to an inventory asset if the client tracks stock, or to cost of goods sold if they do not.
- Inbound freight, which is part of product cost.
- Outbound shipping and labels, set against shipping income.
- Packaging and fulfillment supplies.
- Advertising, split by channel if the owner wants to see return on ad spend.
- Software and app subscriptions, which grow quietly and are worth listing for the owner once a quarter.
Shipping labels are the trap. Some channels let sellers buy labels and take the cost from the payout, so it appears in the payout report. Others charge the card on file, so it appears on the card statement. A store that does both will double count if the bookkeeper codes labels from both sources without checking which is which.
These costs are recurring and repeat by vendor, which makes them good candidates for rules. AutoBankConvert applies each client's own rules and past coding to the converted card and bank lines, so the same label vendor, packaging supplier and app charges are coded the same way every month and only new vendors go to review.
Booking ecommerce payouts straight to revenue
Booking each ecommerce payout as a single sales line is the shortcut that causes most problems in online store books. It understates revenue by the fees and refunds, hides what each channel costs, mixes collected sales tax into income, and leaves no trace of reserves. The bank reconciles, yet the profit and loss is wrong.
The damage shows up later in specific ways:
- The store's gross sales in the books do not match the gross figures in the channel's own year-end reports, and someone has to explain the difference.
- Fees disappear into a lower sales number, so the owner never sees that one channel takes far more than another.
- Collected sales tax looks like income, and the tax payment later looks like an expense.
- Any reserve or negative balance is invisible on the balance sheet.
Fixing it after the fact means pulling every payout report for the year and rebuilding each entry. That is slow, so it is far cheaper to set up the gross-up method in the first month with a new store client.
The same discipline applies to organizations that receive money through online giving tools. The guide to nonprofit bookkeeping shows how a donation platform's net payouts are grossed up in the same way.
If you manage several store clients, AutoBankConvert converts their bank and card statements in a batch, checks each against its balances and keeps every store's rules in its own workspace, so the payout entries start from clean, categorized statement lines.