The growth of sales on marketplaces almost inevitably comes down to an accounting bottleneck: the numbers are there, but they are in different places. The TotalCRM material describes this as vitally as possible — the same "narrow section" appears in the accounting: reports in the cabinet, transfers in the bank, deductions in separate lines, and the period must be closed quickly and without breaks.
The essence of the problem is the mixing of three different entities, which many people habitually try to combine into one: sales (revenue), deductions (commissions, logistics, storage, fines/adjustments) and transfer (the result of mutual settlements). The most common error scenario in the article is stated bluntly: the document begins to be made "by enumeration", which is why the deductions "disappear" from the primary, and then the closing of the month "breaks".
What is UPD in a practical sense for a seller? This is not a "magic paper", but a reference document that helps the accounting department to correctly fix the fact of the provision of services / operations and link it to the reporting lines of the marketplace. That is why, as noted in the text, sellers so often look for "one document" that "legitimately explains where the amounts in the report came from and why the transfer differs from sales."
In the applied logic of marketplaces, "DOP" is the mode when the UPD is used as the primary transfer document for operations/services (and not necessarily as an invoice). Terminology and function differences/statuses are discussed in detail in the materials on EDI: DOP and CFDOP are different modes, and the attributes of the document and its status in the exchange system depend on this.
On the Ozon side, the important guideline is simple: closing documents and reports are generated according to the regulations and are available to the seller in the documents section, including the UPD to the implementation report (depending on the mode and scheme of operation). It is convenient to use this as the "skeleton" of the closure: the implementation report as a database of events, UPD/acts as confirmation of services/ operations, the bank as transfer control.
How do I print a receipt with Wildberries for the report? It is important not to mix the roles here: a receipt is a confirmation of payment/expense (often for an advance report), and UPD/acts are a documentary base for the sale/services of a marketplace. A receipt is a confirmation of payment/purchase, not a document for the sale of marketplace services.
The main conclusion for businesses is that in 2026, marketplaces are no longer “just sales”, but a full—fledged financial logistics circuit. Whoever keeps the discipline of the documents (period, meaning of the amount, statuses, the bundle "report line → accounting item") closes the month in hours. Those who focus only on "how much money came in" get chronic discrepancies and manual reconciliation for days.
