Every Monday, hundreds of thousands of sellers open the finance section of their dashboard, look at their balance, check their bank statement—and freeze in disbelief. The numbers on screen refuse to match. One figure glows in the dashboard, another is calculated in the weekly report, and a third lands in the bank account.
The knee-jerk reaction is that the platform messed up again or withheld too much. Amid payout delays, any discrepancy feels like a disaster. Yet panicking and messaging support is pointless until you learn to reconcile these numbers down to the kopeck yourself. In 9 out of 10 cases, discrepancies happen not because the marketplace is stealing, but because of complex accrual mechanics: CIS sales, prior-period adjustments, and hidden service deductions. Let's walk through a verification algorithm for Wildberries and Ozon reports that will save both your nerves and your money.
Where Discrepancies Hide on Wildberries
On Wildberries, the biggest source of stress is misunderstanding which metric in the report is actually final. In the "Finance" → "Sales Reports" → "Weekly" section, many sellers look at the "To Be Transferred for Goods" («К перечислению за товар») column and expect that exact amount to hit their bank account.
That is a rookie mistake. "To Be Transferred for Goods" is an intermediate gross figure: the value of sold items minus the base commission. From that figure, the marketplace also deducts outbound and return logistics, paid storage, paid acceptance, the «Джем» subscription, penalties, and loyalty program compensations.
Your only anchor figure in the entire report is the "Total Payable" («Итого к оплате») line. Only that number must match the registry in the "Payment History" tab and your bank statement. When we calculated unit economics and margins on Wildberries, we broke down how hidden service deductions eat away at planned margins if you skip checking the report breakdown.
Even the "Total Payable" line can diverge from expectations due to two quirks:
Geographic split. For a single week, the platform often generates two parallel reports: sales within the Russian Federation and sales in EAEU countries. You must add the "Total Payable" figures from both reports together.Month-end overlap. If a week crosses from one month into the next, the settlement period splits into two independent reports by date. Miss one slice, and your balance won't reconcile.
Ozon Report Traps and Building Data Bottom-Up
Ozon uses different logic, though it has its own hidden interface trap. In "Finance" → "Payouts," the "Sales Payment" («Оплата реализации») line shows revenue only from buyers inside Russia.
Sales to customers in CIS countries are processed by Ozon under a buyout mechanic. The platform buys the goods from the seller and resells them in its own name. Those amounts arrive on a separate line—"Marketplace Buyout Payment" («Оплата выкупов маркетплейсом»)—backed by a УПД-1 document.
The catch is that the popular "Store Economics" section simply doesn't display these buyouts. A seller sees understated revenue, starts slashing ad spend, while the money is just sitting on another line. For an accurate reconciliation on Ozon, you must sum both lines: sales and marketplace buyouts.
The acceptable variance between your accounting spreadsheet and the platform's payout must not exceed 0.1%. If the delta is higher, there is a systemic error in your books: a double-counted commission, a missed return, or an unrecorded logistics invoice.
Never copy summary totals straight from marketplace reports. Accounting must be built strictly "bottom-up"—tracking every single transaction for every SKU. When the sum assembled from thousands of operations matches the platform's report down to the kopeck, your unit economics are crystal clear.


