Reconciling Marketplace Payouts With Your Books

Why "just recording the deposit" isn't real bookkeeping

The easiest, and worst, way to book marketplace income is to record each bank deposit as revenue. It's fast, but it collapses gross sales, marketplace fees, advertising spend, refunds, sales tax collected, and any reserve activity into a single net number — which means your books can no longer answer basic questions like "what's my actual gross margin," "how much am I really spending on ads," or "what's my refund rate trending toward." It also makes your books harder to defend if you're ever audited, since the deposit total won't match your sales records at the transaction level.

Proper reconciliation means recording the full detail behind each settlement — gross sales, each fee category, refunds, and any tax collected on your behalf — as separate line items, so the net deposit is the natural result of summing those lines rather than the only number you ever see.

The reconciliation process, step by step

1. Pull the marketplace's detailed settlement report for the period (not just the payout summary) — this typically breaks out gross sales, referral/commission fees, fulfillment fees, advertising charges, refunds, chargebacks, and any reserve adjustments.
2. Set up a clearing/holding account in your accounting system representing "money the marketplace owes me but hasn't paid yet" — sales and fees post here as they occur (or as a batch matching the settlement report), and the actual bank deposit clears this account down, ideally to zero (a nonzero residual is a sign something wasn't recorded correctly).
3. Book each category as its own line: gross sales (revenue), referral/commission fees (expense), fulfillment fees (expense), advertising (expense), refunds (contra-revenue), reserve held (a receivable/asset until released), sales tax collected and remitted by the marketplace (generally not your revenue or expense at all — it passes through).
4. Match the resulting net figure to the actual bank deposit. If they don't match exactly, the gap is usually a timing issue (a settlement period that spans a bank statement cutoff) or a missed line item — don't force a plug entry without understanding why first.
5. Repeat every settlement period — the process gets much faster once you've built a template or, better, connected an integration between the marketplace and your accounting software that automates most of this.

A simplified worked example

Recording only the $9,670 deposit tells you nothing about the $2,760 in commission, the $1,850 in ad spend, or the $620 in refunds — all of which are separately important to know if you're trying to understand your actual unit economics or catch a fee or refund-rate trend early.

Handling reserves correctly

A reserve that's withheld but not yet released shouldn't just disappear from your books — it's still your money, temporarily held. Book it as a receivable/asset ("reserve held by marketplace") rather than as an expense, and move it to cash once it's actually released in a later settlement. Treating a reserve as a loss when it's withheld (and then as a windfall when it's released) distorts your profitability in both periods.

Multi-marketplace reconciliation

If you sell on more than one marketplace, keep the reconciliation separate by channel before rolling up to a combined view — this is the only way to see which channel's fee structure, ad efficiency, or refund rate is actually driving your overall numbers, rather than a single blended figure that obscures which channel needs attention.

Tools that make this easier

• Native or third-party integrations between your accounting software and each marketplace, which can automate pulling settlement data and posting it to the right categories (see Ecommerce Accounting Software Comparison).
• A dedicated reconciliation spreadsheet template, if you're not yet ready to invest in an integration — even a manual template that separates the categories above is a large step up from booking bank deposits alone.

Common mistakes

• Recording only the net bank deposit as revenue, losing all visibility into fees, ads, and refunds.
• Treating a held reserve as a loss instead of an asset, and treating its later release as unexplained income.
• Reconciling infrequently (e.g., annually) so a fee or refund-rate problem goes unnoticed for months.
• Blending multiple marketplaces into one number, hiding which channel is actually underperforming.
• Booking sales tax collected by a marketplace facilitator as your own revenue, inflating apparent sales.

Best practices

• Reconcile every settlement period, not just at tax time or month-end.
• Use a clearing account so the bank deposit is a check on your reconciliation accuracy, not the only figure you record.
• Keep reconciliation broken out by marketplace channel before rolling up to a total.
• Automate with an accounting-software integration once volume makes manual reconciliation too time-consuming.

Checklist

• [ ] Pull the detailed settlement report for the period.
• [ ] Post gross sales, each fee category, refunds, and reserve activity as separate lines.
• [ ] Confirm the net of those lines matches the actual bank deposit.
• [ ] Investigate any unexplained gap rather than plugging it.
• [ ] Repeat by channel if selling on multiple marketplaces.

FAQs

How often should I reconcile? At minimum every settlement period (often biweekly); monthly at the very least. Waiting longer makes it harder to catch a fee or refund-rate issue while it's still small.

What if the numbers don't match exactly? Check for a settlement period that spans your bank statement's cutoff date first — this is the most common cause. If that doesn't explain it, look for a reserve, adjustment, or fee category you haven't mapped yet.

Is this worth doing manually, or should I use an integration? Manual reconciliation is a fine starting point and teaches you the categories, but once you're processing more than a small number of settlement periods a month across one or more marketplaces, an accounting-software integration usually pays for itself in time saved and reduced error risk.