Every marketplace seller has had the same conversation with their finance team. Amazon deposits a number into the bank. Someone in accounting looks at that number, looks at what the brand thinks it sold, and the two do not agree. Not by a little. The deposit is smaller, sometimes dramatically smaller, and the gap is made up of dozens of line items with names nobody outside the platform fully understands. Referral fees, FBA fulfillment fees, storage fees, refund reimbursements, advertising costs, reserve holds, chargebacks, and a handful of adjustments that seem to appear from nowhere. The brand sold, say, a hundred thousand dollars of product. The bank saw seventy something. And the job of explaining the difference, in a way that survives an audit and closes the books cleanly, falls to a person who did not design any of it.
I have spent a long time inside this problem, first building commerce capability inside NetSuite and now running an operations consultancy that lives in it every day. Of all the places where marketplace revenue and NetSuite quietly disagree, settlement reconciliation is the one that causes the most pain and gets the least respect during an integration. Brands scope the order flow carefully. They think hard about how a marketplace order becomes a sales order. And then they treat the money coming back as an afterthought, a bank deposit to be booked and moved past. That afterthought is exactly where the trouble compounds.
A marketplace settlement is not a payment, it is a story
The mental model most brands carry over from their own storefront is that a sale produces a payment, and the payment matches the sale. On a marketplace, that model breaks immediately. A settlement is not a payment against one order. It is a batch, a period of activity that the platform has netted down into a single transfer, and inside that batch are hundreds or thousands of individual events that each need a home in your general ledger. The gross sales are in there. So are the fees the marketplace charged for the privilege of selling on it. So are the refunds it processed on your behalf, the reimbursements it owes you for lost inventory, the advertising it billed against the same account, and the money it is holding in reserve and will release later on its own schedule.
Marketplace settlement reconciliation, done properly, is the discipline of taking that netted transfer apart and matching every piece of it back to the activity that created it. It is settlement decomposition, and it is the difference between a finance team that can tell you exactly what Amazon charged you in fees last month and one that can only tell you what hit the bank. Those are very different levels of visibility, and the gap between them is where profitability quietly disappears.
Why marketplace fees (referral, FBA, storage) decide your real margin
It is tempting to treat the fees as noise, a cost of doing business to be lumped into one expense line and forgotten. That instinct is what keeps brands from understanding their own margins. On a marketplace, the fees are not a rounding error. Referral fees, fulfillment fees, and storage fees together can consume a serious share of the sale price, and they vary by product, by size, by season, and by how long inventory sits. A brand that books its marketplace revenue net, meaning it only records what landed in the bank, has thrown away the entire cost structure of its largest sales channel. It cannot see which products are actually profitable after fees, because the fees were never recorded against the products that incurred them.
FBA fee reconciliation is the clearest example of why this granularity earns its keep. When fulfillment fees are decomposed and posted correctly in NetSuite, a brand can finally answer the question that decides its assortment strategy. Which items make money after the marketplace takes its cut, and which ones are moving volume while losing margin. That answer is invisible to a company booking net deposits, and it is the single most valuable output of doing settlement reconciliation the right way. Getting the gross sales, the fees, and the reimbursements each into their own place in the ledger is not accounting for its own sake. It is the only way to see the true profitability of the channel.
The reserve, the timing, and the close that never ties out
The second thing marketplaces do that wrecks a naive setup is hold your money and release it on their own clock. Platforms routinely keep a reserve, a portion of your sales held back against potential refunds and disputes, and they release it in a later settlement period. This means the money you earned in one month arrives across two or three. If your integration books revenue when the cash arrives, your revenue recognition is now driven by the marketplace’s payout cadence rather than by when you actually made the sale. Two brands with identical sales can show wildly different monthly revenue simply because their reserve timing differs. That is not a real difference in performance. It is a reporting artifact created by treating a settlement like a payment.
This timing problem is why marketplace reconciliation belongs in the month end conversation, not off to the side. The sale, the fee, the refund, and the payout can each land in different periods, and the job of a well designed integration is to keep them attached to the right moment regardless of when the money moves. When that is done, the close ties out, the revenue lands in the period the sale happened, and finance stops spending the last days of every month chasing a deposit that does not match anything. When it is not done, reconciliation becomes a monthly forensic exercise, and the phrase I hear most often from operations leaders is that nobody fully trusts the marketplace numbers anymore.
Three marketplaces, three data models, one very confused ledger
There is a pattern I see again and again, and it is worth naming because it is so predictable. A brand starts on one marketplace, gets it working well enough, and then grows. It bolts on a second platform, then a third, each one added quickly to capture the revenue, each one integrated a little differently by whoever was available at the time. The result is three marketplace channels flowing into NetSuite through three different patterns with three different data models, and no single person who understands all of them. Orders fall through the cracks. Inventory that a marketplace has reserved for its own fulfillment does not show as allocated in NetSuite, so the same unit gets promised twice. And settlement reconciliation, already hard for one platform, becomes genuinely unmanageable across three that each decompose their payouts differently.
The fix is not to reconcile harder. It is to normalize. A unified marketplace order to cash process takes every channel, however different its native format, and translates it into a consistent set of transactions in NetSuite. Each order creates the right transaction type for the client’s billing model. Each settlement is decomposed and matched back to the orders that produced it. Orders that the marketplace fulfills itself still generate correct financial records even though the brand never touched the physical shipment. The point is a single operational and financial view across every channel, so that adding the fourth marketplace is a known, repeatable motion rather than another improvised integration nobody will remember how to support.
What good marketplace settlement reconciliation looks like in NetSuite
When marketplace settlement reconciliation is designed on purpose, a few things become true that were not before. Finance can open NetSuite and see gross sales, fees, refunds, reimbursements, and reserves as distinct, matched figures rather than a single mysterious deposit. Profitability by product after marketplace fees is a report, not a research project. Revenue lands in the period the sale occurred, so the close ties out and month end stops being a fight with a payout schedule. And when the brand launches on the next platform, the flow already knows how to normalize it, because the process was built to absorb new channels rather than to handle one at a time.
This is the work Hairball does every day. As a top Celigo implementation partner and a NetSuite continued success provider, we build the marketplace order to cash and settlement reconciliation process so that every payout is decomposed, every fee is matched to the sale that incurred it, and multi-channel revenue arrives in NetSuite as a single reconcilable picture rather than a set of deposits nobody can explain. We normalize Amazon, TikTok Shop, Walmart, and the rest into one consistent flow, so profitability is visible, the close is clean, and adding the next channel does not mean adding the next unsolved problem.
If your team can tell you what a marketplace deposited last month but cannot tell you what it charged you in fees, what it is still holding in reserve, or which products actually make money after the platform takes its share, that gap is not permanent. It’s a settlement process that was never fully designed, and designing it is exactly the kind of problem we were built to solve.
