# How to reconcile European e-commerce sales across OSS, IOSS and marketplaces Begin with orders and their legal supply chains, not marketplace payouts. A payout can combine sales, tax, fees, refunds, reserves and currency conversions. It is a settlement result, not a dependable sales-tax reporting population. **Diagram:** Reconcile gross orders and refunds before platform settlement. Synthetic seller-liable VAT example: 1,200 - 120 - 60 = 1,020. Marketplace deemed-supplier and import routes require different decisions. For each channel, determine who is the supplier for the relevant tax purpose, where goods start and finish, the customer's status and the applicable reporting route. Use the [order-route and settlement worksheet](#template) to preserve those decisions. This guide proposes operating controls; the tax owner approves actual scheme eligibility and treatment. ## Build a route for each order population List the contractual seller, platform, stock owner, dispatch and destination countries, customer type and any import. Record whether the marketplace is acting as a deemed supplier under the applicable rules. Do not assume a platform collects every tax just because the customer bought through its website. The EU One Stop Shop guidance distinguishes Union [OSS](https://erplocalization.com/glossary/core/#core-oss-and-ioss), non-Union OSS and IOSS, with conditions on the transactions and businesses each can cover. A scheme registration does not make all of a seller's supplies eligible for that scheme. [Your Europe, VAT One Stop Shop](https://europa.eu/youreurope/business/finance-and-tax/vat/one-stop-shop/index_en.htm). Assign a responsible reporter and a reporting route to each eligible transaction. Preserve domestic-return populations separately where required. Foreign stock can create responsibilities that an OSS registration does not settle. Review those arrangements using [the foreign-stock guide](https://erplocalization.com/guides/cross-border-stock-warehouses-vat/). For a route involving services, distinguish the applicable service rules from goods-import rules. A non-Union OSS service sale and an IOSS import are different processes even if the same platform settles both. ## Verify IOSS and customs facts independently The Commission describes the import scheme for eligible distance sales of imported goods in consignments with intrinsic value not exceeding EUR150, excluding goods subject to excise duties. Check the remaining conditions, intermediary requirements and customs-data handoff against the actual supply chain. [Commission, import-scheme context](https://vat-one-stop-shop.ec.europa.eu/one-stop-shop_en). Keep the IOSS identifier available only to the people and service interfaces that need it. Record which party supplies the correct identifier to the customs process and how errors are reported. Do not print an identifier into every customer-facing export merely to make integration troubleshooting easier. The former low-value customs-duty relief and IOSS VAT eligibility are different concepts. The Commission's June 2026 guidance explains the temporary EUR3 customs duty introduced from 1 July for the covered low-value imports. Do not describe EUR150 as a universal current customs-duty-free threshold. [Commission, temporary low-value-import duty guidance](https://taxation-customs.ec.europa.eu/news/guidance-and-legal-text-temporary-flat-fee-low-value-imports-which-will-apply-until-1-july-2028-2026-06-08_en). The Commission's examples clarify that "item" concerns tariff classification rather than the physical quantity: five T-shirts can produce one EUR3 charge, while T-shirts and a watch produce EUR6. Check the detailed grouping, scope and exceptions before configuring a charge. [Commission, classification-based duty examples](https://commission.europa.eu/news-and-media/news/ensuring-fairness-and-safety-eur3-customs-duty-low-value-parcels-2026-06-29_en). Retain the applicable duty, import-VAT and sale-VAT records separately. Do not infer a flat duty for every express consignment or calculate VAT treatment from this simplified description. ## Preserve gross events before reconciling settlement Import order lines, original and adjustment identifiers, invoice/credit references, tax category, taxable amount, tax, total, currency, transaction date and reporting route. Retain dispatch, cancellation, return, refund and payment events with their own dates. Keep platform fees, reserves and currency differences outside the gross sale amount unless the approved accounting and tax analysis specifically requires another treatment. A platform's net remittance should reconcile to the transaction history rather than replace it. For marketplace deemed-supplier cases, retain the platform evidence and the seller's own supply/accounting treatment. The seller may need a different tax representation from the platform's consumer sale. Reconcile the two roles instead of suppressing all seller records. ## Work a synthetic settlement example Assume a fictional seller is confirmed responsible for VAT on one eligible order population. The tax owner has approved the route and an illustrative 20% tax rate. No marketplace deemed-supplier treatment, import, reserve, shipping charge or foreign currency applies to this particular calculation. The seller has ten orders, each EUR100 net plus EUR20 tax. Gross customer charges total EUR1,200. One complete order is returned and refunded, reducing gross sales by EUR120. A separately approved platform fee of EUR60 is deducted from settlement. Net sales after the return are EUR900, tax is EUR180 and the post-refund customer amount is EUR1,080. The platform pays EUR1,020 after deducting its EUR60 fee. The reconciliation is EUR1,200 minus EUR120 minus EUR60, which equals EUR1,020. Do not report EUR1,020 as taxable sales. It includes tax and reflects a fee deduction. Retain the EUR60 expense according to its own invoice and tax treatment, outside the synthetic sales-tax calculation. The example intentionally does not invent the fee's input-tax entitlement. Now consider a different route where the marketplace is independently confirmed to be the deemed supplier. Do not copy the first route's reporting ownership. Reassess the seller-to-platform and platform-to-consumer relationships, the records each party provides and the seller's appropriate return population. ## Reconcile reporting periods and corrections Match each reportable order or approved aggregate to its correct reporting route and period. Keep the original transaction period, refund date and correction period separately. A current platform payout can include a refund relating to an earlier reporting period. Use the applicable scheme's correction rules rather than moving the original sale into the refund month to force agreement. The Commission's OSS guidance provides scheme-specific filing and recordkeeping context. [Commission, One Stop Shop](https://vat-one-stop-shop.ec.europa.eu/one-stop-shop_en). If import evidence shows the wrong identifier or route, assign the case to the customs and tax owners. A customer charged tax twice needs investigation of the actual checkout, customs and declaration records. A customer-service refund alone does not correct the underlying customs data or tax return. Keep adopted future changes separate from current operations. The Commission's [ViDA](https://erplocalization.com/glossary/core/#core-vida) timeline includes later Single VAT Registration measures. Maintain a dated transition plan without applying a future simplification to an October 2026 transaction. [Commission, ViDA timeline](https://taxation-customs.ec.europa.eu/taxation/vat/vat-digital-age-vida_en). ## Complete channel acceptance - ☐ Each order population has approved supplier, marketplace and reporter roles. - ☐ Goods location, customer status and import route support the selected scheme. - ☐ Gross orders, adjustments, fees and settlements remain distinguishable. - ☐ Customs identifiers and charge records are available through controlled interfaces. - ☐ Current duty rules are separate from IOSS VAT eligibility. - ☐ Returns and late corrections preserve original references and periods. - ☐ Finance can reproduce gross-to-net settlement and report-route reconciliations. - ☐ A change of warehouse, platform terms or tax responsibility triggers reassessment. Assign the controller to the settlement bridge, tax to route and correction decisions, platform operations to source extracts and integration to reliable joins. Retain source records and the approved worksheet with each reporting close. Sources checked 17 October 2026 using official EU guidance. The worked figures are synthetic and deliberately avoid imports and deemed-supplier accounting. Real marketplace contracts, registrations and transaction facts determine the applicable reporting treatment. ## Worksheet: E-commerce order route and settlement reconciliation Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment. Show the worksheet Copy this worksheet for the named entity, route and period. Blank fields are intentional inputs. Retain approved decisions and source evidence rather than inferring legal treatment from these headings. - Seller, platform role and approved deemed-supplier decision: - Stock owner, dispatch/destination, customer type and import route: - Approved OSS/IOSS/domestic reporting responsibility and evidence: - Original order/line, dates, net, tax, gross, currency and scheme route: - Returns/refunds with original reference and approved correction period: - Fees, reserves, currency effects and platform remittance: - Gross orders minus refunds minus fees/reserves plus other adjustments equals settlement: - Customs identifier handoff and duty/VAT evidence where relevant: - Changed platform terms/warehouse/routes requiring reassessment: - Controller, tax, operations and interface acceptance: ### Close the record - Prepared by and date: - Reviewed by and date: - Open items, owners and due dates: - Evidence location and version: - Change/review trigger: Keep prior versions and document corrections. A balanced reconciliation does not replace an approved scope decision or missing source evidence. ## Related on this site - [Country pages](https://erplocalization.com/countries/): key facts with sources - [E-invoicing matrix](https://erplocalization.com/e-invoicing/): country × ERP support - [All guides](https://erplocalization.com/guides/) Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17. Related: [Glossary](https://erplocalization.com/glossary/) – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more). --- Canonical: https://erplocalization.com/guides/ecommerce-oss-ioss-marketplace-erp/ · Last updated: 2026-10-17 · Informational only; not tax, legal or implementation advice. Featured placements are paid or promotional and do not affect the compliance data. Data: CC BY-NC 4.0 (commercial use needs a licence: https://erplocalization.com/data-licence/), attribution "ERP Localization (erplocalization.com)".