Why this always takes longer than expected
Every seller who has done this once knows the feeling: it should take twenty minutes, and it takes an afternoon. The arithmetic is trivial — gross sales minus fees minus refunds should equal the payout. What eats the time is tracing each deduction back to the specific order or category it belongs to, when the settlement report gives you a wall of lines and no obvious place to start.
This guide is that tracing process, made repeatable. Not a trick to make it instant, but a method that turns a guessing exercise into a short list of genuine judgment calls, done the same way every time.
Two decisions before you start
Two choices, made once, save re-litigating them every single payout cycle.
What counts as a confident match
Decide, once, how much agreement between order reference, category and amount you need before treating a match as settled versus needing a second look.
Who resolves ambiguous cases
Decide who has the context to tell an ambiguous deduction apart from a genuine discrepancy, so a flagged line doesn't sit unresolved because no one owns the decision.
Neither decision needs to be perfect on the first try. Most sellers set an initial confidence bar, run a cycle or two, and adjust — too strict and everything gets flagged for review, defeating the purpose; too loose and genuine discrepancies slip through unnoticed. What matters is making the decision explicitly rather than letting it drift cycle to cycle based on whoever happens to be reviewing that day.
The seven steps
Gather the settlement report and gross sales export
Pull the marketplace's own settlement report covering the payout period you're reconciling, and a gross sales export covering the same window.
Take a moment here to confirm the two documents actually cover the same period — a settlement report's boundaries rarely line up neatly with a calendar month, and a misaligned window is the single most common cause of a reconciliation that looks wrong but isn't.
If you sell through more than one channel — a marketplace and your own storefront, say — gather a settlement report or export for each channel now rather than partway through. Starting the reconciliation with only part of the picture just means repeating the early steps once the missing channel turns up.
Read every line on the settlement report
Extract the order ID, category, amount and date for every deduction, not just the largest ones — a small deduction that looks routine sometimes turns out to be the one worth checking most closely.
Read each category exactly as the marketplace labels it, without paraphrasing or grouping it mentally. A category that's genuinely ambiguous should stay ambiguous at this stage — resolving it belongs in the matching step, not in how it gets transcribed here.
Match each line against gross sales
Compare order reference, category and timing together against the gross sales export, rather than order reference alone. A weak reference combined with an exact category and amount match is often enough for a confident match; a weak reference alone usually isn't.
Where a deduction could plausibly belong to more than one order, note both rather than picking one — that's exactly the case the next step exists to resolve, and forcing a choice here just moves the ambiguity somewhere less visible.
Review flagged and unmatched lines
Work through anything that didn't match confidently. Most resolve quickly once you look at the actual deduction — a refund from a prior period, a promotional credit, a reserve release that hadn't been logged yet.
Resist the urge to force a match just to clear the list. An unresolved item left visible is far better than a wrong match buried inside a total that now looks clean but isn't accurate.
Keep a brief note on how each flagged case was resolved, even a single sentence. It costs almost nothing at the time and saves real effort the next time a similar-looking deduction appears and someone has to remember why it was fine last time.
Account for reserve holds separately
If the marketplace held back part of the payout as a reserve, track that amount as its own pending line rather than treating it as a shortfall in the current period's total — more on this in the section below.
Note the expected release date if the settlement report provides one, so a later release shows up as an expected event rather than an unexplained deposit weeks or months from now.
Produce the reconciled summary
Build a clear breakdown: gross sales, each deduction category with its total, and the net payout that resulted. This is the actual deliverable — the artifact an owner or a bookkeeper actually wants to see.
Include the confidence level alongside each matched category rather than flattening everything to a simple total. An owner reading the summary benefits from knowing which categories are rock-solid and which were confirmed manually after a flag.
Log the period and set the next date
Save the reconciled record — it's the reference point for next cycle and the answer to any question about a specific payout months later. Then put the next reconciliation date on the calendar before this one fades from memory; the section on cadence below covers how often makes sense.
If anything about the process felt slower or more confusing than it should have this cycle, write that down too. A small note now — “the settlement report changed its fee category names” — is exactly the kind of detail that gets forgotten by the time it matters again next cycle.
A payout period, worked from start to finish
A two-week Amazon settlement period, 340 orders, no other marketplaces involved.
| Step | Time |
|---|---|
| Gather settlement report and sales export | 5 minutes |
| Read the settlement report | 2 minutes, done in one batch |
| Automatic matching | Under a minute |
| Review 9 flagged, 5 unmatched | 25 minutes |
| Produce the reconciled summary | Immediate, from the matched output |
| Log and schedule next cycle | 5 minutes |
Under forty minutes total, with the bulk of it spent on the fourteen genuinely ambiguous cases rather than the hundreds of straightforward ones. That ratio — a handful of real judgment calls, everything else handled consistently — is the point of the whole method.
Common mistakes
Reconciling against a calendar month instead of the settlement report's own period boundaries.
Treating the net payout figure as the thing to verify, rather than tracing it back through every deduction to gross sales.
Folding a reserve hold into the current period's total instead of tracking it as a separate pending line.
Waiting a full month to reconcile, letting several settlement reports pile up into one large catch-up session.
Forcing a low-confidence match to clear the list instead of leaving it visibly unresolved.
Losing the matched history when the bookkeeping role changes hands, forcing the next person to start from zero.
The specific causes behind a payout that never quite matches — with concrete examples — are covered in why your marketplace payout never matches your sales report.
Most of these six share a root cause worth naming directly: treating a weak signal — a rounded total, an old assumption, a silence — as stronger evidence than it actually is. The seven steps above exist specifically to avoid that by checking multiple signals together rather than any single one alone.
When a marketplace holds part of the payout back
A reserve held against future refunds or disputes doesn't disappear — it's released later, often weeks or months after the original settlement period, as a deposit that on its own looks unexplained.
Reconciling that correctly means reading the reserve line from the original settlement report, tracking it as pending, and matching the eventual release back to that original entry when it appears — the mechanics of that specific case are covered in marketplace payout reconciliation.
Doing this across several marketplaces
If you sell through more than one marketplace, each with its own settlement format and payout schedule, the same seven steps apply at each marketplace individually — and the outputs roll up into one consolidated picture rather than each marketplace being reconciled in isolation with no combined view for the owner.
One practical adjustment worth making at that scale: steps one and two — gathering and reading — happen once per marketplace, but steps six and seven — producing the reconciled summary and logging it — happen once at the consolidated level, after every marketplace's results are combined.
The very first reconciliation
If payouts have never been formally reconciled before, expect the first pass to surface more unmatched and ambiguous cases than any cycle after it — that's the backlog of small inconsistencies that accumulate when nothing has ever been checked against the settlement report in detail.
Treat the first pass as cleanup, not failure. Every fee-category quirk and every unusual deduction it finds makes every subsequent cycle faster, which is exactly why the investment is worth making once rather than never.
Choosing a cadence that actually sticks
Matching your reconciliation cadence to the marketplace's own payout schedule is the right default — every two weeks for a biweekly marketplace, weekly or daily for a faster-settling payment processor. A cadence any looser than the payout cycle itself guarantees the reconciliation is always behind the reality it's meant to reflect.
Some larger sellers with a dedicated bookkeeper reconcile every single payout the day it lands, catching a discrepancy within days rather than waiting for a monthly review. That's more frequency than most sellers strictly need, but it's worth considering for a marketplace with a history of fee errors, where early detection matters most.
Whatever the interval, the deciding factor isn't precision — it's whether the interval is short enough that a seller can still remember the context behind an unusual deduction when they see it, rather than trying to reconstruct a months-old memory from a settlement report line alone.
What to do with a genuine discrepancy
The reconciliation itself stops at producing an accurate breakdown of what happened — what to do about a genuine discrepancy is a separate decision. Some sellers raise every unexplained fee with the marketplace, however small; others set a dollar threshold below which it's not worth the time to dispute.
Whatever the policy, having a genuinely accurate reconciliation — not one padded with fees that were actually correct but got flagged by mistake — is what makes that policy worth following. A dispute raised over a deduction that was actually correct, because it was never properly matched, wastes the marketplace's support time and yours.
It's worth keeping a running log of disputes raised and their outcomes — over time, that log tells you which fee categories a given marketplace tends to get wrong, which is useful context for deciding where to focus review effort in future cycles.
What you actually need
A settlement report for the period, downloaded from the marketplace.
A gross sales export covering the same window, in a spreadsheet.
A note of any known reserve holds and their expected release dates.
Somewhere to log the reconciled result each cycle, even a simple spreadsheet.
Nothing exotic — the method works with what most sellers already have access to. What changes is how the matching step gets done: by hand, line by line, or read and matched automatically. The full picture of that automated step is in marketplace payout reconciliation.
If a gross sales export doesn't exist yet in a usable form, the very first cycle will take longer simply assembling one. That one-time setup cost is worth treating as separate from the recurring cycle time, since it won't repeat once the basics are in place.
Handing this off to a new bookkeeper
Ecommerce bookkeeping roles turn over more often than most finance functions — a year or two is common, sometimes less. What tends to get lost in that handoff isn't the settlement reports themselves, which usually survive, but the informal knowledge: which fee categories a given marketplace tends to get wrong, which reference formats are normal, which unmatched cases from last cycle were resolved and how.
Hand over the matched history, not just a blank settlement report — context about resolved ambiguous cases is worth more than it looks.
Write down the cadence and the date of the last reconciliation, so the new bookkeeper knows exactly where continuity picks up.
Note any marketplaces with known nonstandard patterns — reserve schedules, category quirks — before the knowledge leaves with the outgoing bookkeeper.
A method that lives in a document rather than in one person's head survives the handoff intact — which is, in the end, the whole point of writing it down as seven repeatable steps rather than an intuition one bookkeeper develops and takes with them.
That's the whole guide, really: seven repeatable steps, written down once, so the next person doesn't have to reinvent them under pressure.
Three ways to do this, compared
There isn't one correct way to reconcile a marketplace payout — the right method depends on order volume, on how much time is realistically available, and on how much the seller already has in place. Worth laying the three common approaches side by side.
| Method | Best for | Main cost |
|---|---|---|
| Fully manual | Very low order volume, under fifty orders per payout period | Time, and no record of how ambiguous cases were resolved |
| Spreadsheet-assisted | Moderate volume with a maintained gross sales spreadsheet | Someone still has to transcribe every settlement line by hand |
| Automated matching | Any volume, especially with reserves or multiple marketplaces | Requires exporting a settlement report and sales data in a readable format |
Most sellers don't pick one method forever — they start fully manual because that's what's available on day one, move to a spreadsheet once the manual version becomes unmanageable, and reach for automated matching once order volume, reserves, or multiple marketplaces make the spreadsheet version too slow to keep up with.
None of the three is wrong for a seller small and simple enough that it works. The seven-step method above applies to all three — what changes between them is how much of steps two and three happens by hand versus automatically.
The matched log, column by column
Whatever method produces it, the record worth keeping each cycle has a specific, minimal shape. A log with these columns answers almost any question that comes up later without anyone having to reopen the original settlement report.
Payout period and marketplace, exactly as the settlement report identifies them.
Gross sales and each deduction category total, taken from the report.
The net payout amount and deposit date.
Confidence or review status — confirmed, flagged and resolved, or unmatched.
Who resolved any ambiguous case, and a one-line note on how.
Five columns, not fifteen. The temptation with any record-keeping exercise is to capture everything that might conceivably be useful someday, and the result is a log so tedious to maintain that it stops being kept up to date within a cycle or two. These five cover the questions that actually get asked — which period, how much per category, when did it land, how confident was the match, and who signed off on anything unusual.
A spreadsheet with these five columns, one row per reconciled payout, is genuinely all it takes — no database, no specialized software, just a file anyone on the team can open.
How to tell the process is actually working
It's easy to run a reconciliation cycle and feel like it went fine without any real way to check that impression. A few concrete signals are worth tracking across cycles, because the direction they move in says more than any single cycle's outcome.
The unmatched count is shrinking, not growing
A rising trend usually means fee categories or references are drifting out of your expected pattern faster than they're being corrected.
Flagged cases resolve in minutes, not hours
If confirming an ambiguous match still takes real investigation every time, the underlying sales data — SKUs, order references — likely needs cleanup.
The same fee category doesn't get flagged every single cycle
A recurring flag on one category usually points to a specific, fixable issue: a rate change, a misclassification, a promotional program not accounted for.
The log from last cycle actually gets referenced
If no one ever looks back at the matched history, either nothing has come up that needed it yet, or it isn't being kept in a place anyone remembers to check.
None of these four require any special tooling to check — they're just questions worth asking honestly every few cycles, the same way any recurring process benefits from an occasional step back to check it's still serving its purpose rather than just being repeated out of habit.
If two or three of the four are trending the wrong direction at once, that's usually a sign the underlying sales data itself needs a dedicated cleanup pass, separate from the regular cycle — trying to fix data-quality problems inside the normal reconciliation rhythm tends to just make every cycle slower without actually closing the gap.
What a realistic payout cycle looks like
It helps to see the seven steps laid out against an actual calendar rather than as an abstract list, because the gaps between steps matter as much as the steps themselves.
| Day | What happens |
|---|---|
| Payout day | Settlement report and sales export gathered, lines read (steps 1-2) |
| Payout day + 1 | Matching run, flagged and unmatched lines reviewed (steps 3-4) |
| Payout day + 2 | Any reserve holds noted and tracked (step 5) |
| Payout day + 2 | Reconciled summary produced and shared with the owner (step 6) |
| Payout day + 3 | Record logged, next date scheduled, notes written down (step 7) |
A few days right after each payout lands, spread out rather than crammed into one sitting, with natural breakpoints between reading, matching and reporting. For most sellers that's a comfortable pace even alongside other responsibilities — the total active time across that window is a fraction of what an all-at-once, single evening attempt tends to require, because working in shorter blocks avoids the fatigue that leads to rushed, sloppy matching later in a long session.
Every seller runs this same short sequence once per payout, all year. The total annual time investment stays modest precisely because it never accumulates into a backlog the way a once-a-quarter attempt does.