Cross-Border VAT Routing for Digital Platforms Under OSS and IOSS

How VAT routing works under OSS and IOSS#

If you run an EU-facing platform, cross-border VAT is now an operating decision, not a glossary exercise. Since 1 July 2021, your practical job has been to route each flow to the right treatment: Union OSS, non-Union OSS, the import scheme, or a domestic VAT process outside those special schemes.

The expanded One Stop Shop framework covers three special schemes: non-Union, Union, and import. A taxable person using one of them registers in one Member State of identification and files OSS VAT returns electronically for in-scope supplies and VAT due. But OSS does not replace everything. Those returns sit alongside domestic VAT returns where local obligations still apply.

Choose a route by the supply and the liable entity. Each section below covers eligibility, exclusions and the records your filing team needs.

1. the platform model and who it suits
2. the likely VAT route
3. the operational upside
4. the main limitation or failure mode
5. the escalation trigger

A platform can need several filing tracks at once. Classify B2B versus B2C, services versus goods, supplier establishment and goods location before choosing OSS. The EUR 10,000 threshold is a narrow place-of-supply rule, not a general VAT-free allowance.

Your first control checkpoint is data traceability. You should be able to show why a transaction was routed to a specific treatment, including when a marketplace or platform could be treated as a deemed supplier in certain goods scenarios.

Record-keeping requirements apply to platforms facilitating supplies of goods and services. If your team cannot reproduce why a sale was routed to a specific scheme without rebuilding it in spreadsheets, the control is not mature.

This guide covers VAT routing and filing controls, with separate treatment for the customs changes effective in July 2026. Escalate unresolved supply or role questions to the tax owner without assuming that a pending ruling extends a filing deadline.

If you want a deeper dive, read A guide to the 'One-Stop-Shop' (OSS) for VAT in the EU.

How to choose the right route for your platform#

Determine the customer’s tax status and place of supply first. Then establish who makes the supply for VAT purposes and whether an electronic interface is deemed supplier. Choose the scheme only after those facts are known; an EU VAT registration alone does not prove an EU fixed establishment.

1. Start with the supply type

Separate B2C services, TBE services, and distance sales of goods before selecting a scheme. The expanded OSS framework includes three special schemes (non-Union, Union, and import), so it is not a single route for every cross-border flow.

1. Check establishment before selecting Union or non-Union OSS

No EU business or fixed establishment: assess non-Union OSS for services and Union OSS for eligible intra-EU distance sales of goods. EU establishment: assess Union OSS for eligible services in Member States where the supplier is not established. Imports require a separate IOSS test. The identification-state rules differ by scheme; retain the chosen state and the basis for it.

1. Handle imports as a separate routing decision

If an import leg exists, evaluate the import scheme separately instead of assuming the Union or non-Union route covers it. Build filing cadence into your controls: Union and non-Union returns are quarterly, while import-scheme returns are monthly.

1. Confirm liability role before filing or automation

Confirm whether the platform is acting as the taxable person or could be treated as a deemed supplier in certain goods scenarios. Use this as a routing control across compliance, legal, and finance. If role or treatment remains unclear in a complex cross-border case, escalate before filing, including through VAT Cross-Border Rulings.

Keep B2B and B2C supplies in different routing populations. OSS does not turn every cross-border business invoice into a consumer supply; determine the actual VAT treatment separately.

Best when you sell cross-border B2C from an EU base#

Union OSS can cover eligible B2C services taking place in Member States where the supplier has no establishment, intra-EU distance sales of goods, and domestic goods supplies by a qualifying deemed supplier. Eligible goods supplies can be covered even when the supplier is not EU-established.

• Best for: EU-based platforms or marketplaces with recurring cross-border B2C activity across several EU markets.
• Main benefit: one identification state and one electronic OSS VAT return for supplies covered by the scheme.
• Main constraint: the OSS VAT return is additional and does not replace your domestic VAT return.

Since 1 July 2021, EU B2C e-commerce VAT rules have allowed online sellers, including platforms and marketplaces, to register in one EU Member State. They can declare and pay VAT there on relevant cross-border supplies. Under the Union scheme, the identification state is normally where the taxable person is established.

If your facts allow a choice among eligible states, treat that as a long-term control decision. It can bind for the current calendar year plus the next two calendar years.

The gain is consolidation. You file once through that state, and the data and payment are transmitted to the relevant Member States of Consumption. That supports a centralized compliance model across several EU consumer markets.

The main failure mode is weak routing discipline. OSS is optional to join, but once you use a scheme, all supplies that fall under it must be declared through its OSS return. At quarter end, keep two controls in place. Reconcile OSS-covered turnover against the domestic VAT population, and verify that no in-scope cross-border B2C supplies were left in the wrong filing track. Also keep import flows on a separate calendar, because Union and non-Union returns are quarterly while import-scheme returns are monthly.

Use this route when establishment, supply classification, and destination VAT treatment are clear. If those facts are genuinely uncertain in a complex cross-border case, pause automation and escalate early, including through VAT Cross-Border Rulings.

Best when you are non-EU and provide B2C services into the EU#

If you are non-EU, have no EU business or fixed establishment, and your EU-facing model is B2C services, non-Union OSS can be the right starting route. It concentrates filing in one Member State of identification instead of separate registrations across multiple Member States for supplies within the scheme.

The benefit here is administrative concentration, not broader relief. OSS schemes are optional, but once you use one, you must declare all supplies that fall under that scheme through that scheme's OSS return.

Why this route fits#

For non-Union OSS, eligibility turns on facts, not product wording. You need no EU establishment and supplies that fall within the non-Union scheme. If eligible, you can choose any identification state, and that state issues a dedicated VAT ID in EUxxxyyyyyz format. That ID is limited to supplies declared under the non-Union scheme. Treat that limitation as a control point in billing and tax logic.

Where teams get caught#

The common mistake is trying to stretch non-Union OSS beyond its scope. It is not a catch-all for every EU-facing flow run by a non-EU platform. If goods or import legs appear, assess the Union or import scheme separately.

For services-only fact patterns, non-Union OSS is often the first route to test.

If classification is genuinely unclear, escalate early. For complex cross-border VAT treatment, consider requesting a VAT Cross-Border Ruling for advance guidance.

What to verify before go-live#

Before launch, confirm and document the following:

• no EU business or fixed establishment
• service classification for each in-scope flow
• chosen identification state
• Member State of Consumption mapping used in returns
• issued EUxxxyyyyyz identifier and its restricted use

Also align your filing calendar: non-Union and Union OSS returns are quarterly, while import-scheme returns are monthly. Keep the core constraint visible as well: OSS returns are additional and do not replace domestic VAT returns where those still apply.

For a step-by-step walkthrough, see Global VAT Compliance Map for Digital Services Platform Operators.

Best when you import low-value goods for EU consumers#

IOSS is optional for eligible B2C distance sales of goods imported from outside the EU in consignments with intrinsic value no more than EUR 150; goods subject to excise duty are excluded. Goods already in EU stock are not imported distance sales merely because their seller is non-EU.

Why this route fits#

The import scheme is built to simplify VAT declaration and payment for eligible imported distance sales. It sits within the enlarged OSS framework that has applied since 1 July 2021.

Check who registers and whether an EU-established IOSS intermediary is required. Non-EU suppliers generally need one; the mutual-assistance exception depends on the supplier’s country and goods dispatched from that country. Do not confuse this appointed tax intermediary with a marketplace that merely facilitates a sale.

Where teams mis-scope it#

IOSS covers the import slice only. It is not a universal lane for all EU-facing VAT obligations, and OSS VAT returns are additional rather than replacements for regular VAT returns.

Test intrinsic value per consignment, not a website’s basket total alone. Separately stated transport and insurance are excluded from intrinsic value; included charges that are not separately stated may affect it. A EUR 160 consignment is outside IOSS even if its constituent goods cost less than EUR 150 individually. EUR 150 is still the IOSS VAT scope limit; it does not mean customs-duty-free. The EU removed that customs relief on 1 July 2026 and introduced a temporary EUR 3 duty for covered low-value imports. Keep customs charges and their VAT treatment in a separate, current rule set.

What to verify before go-live#

Before go-live, confirm these points in writing:

• Imported B2C distance sale, with intrinsic value per consignment no greater than EUR 150
• No goods subject to excise duty
• Correct registrant, identification state and appointed intermediary where required
• IOSS identifier transmitted securely to the customs declarant; avoid public exposure or reuse on unrelated shipments
• Separate customs-duty calculation and VAT treatment
• Monthly returns and payments, including nil returns where required

The real tradeoff#

The import scheme is optional, but once you use it, you must report all supplies that fall under that scheme through its OSS return. So the real question is not just eligibility. It is whether you can keep the scope boundary clean period after period.

If your model mixes import and non-import flows and classification remains unclear, escalate early and consider advance guidance through a VAT Cross-Border Ruling in a participating Member State.

Best when deemed-supplier risk is your biggest unknown#

Treat deemed-supplier exposure as a legal classification question first, then build automation. If your product, checkout, or fulfillment design puts platform control at the center, move that flow to legal review before you lock tax logic.

Start from what is conditional#

For goods, an electronic interface can be deemed supplier when it facilitates B2C imported distance sales in consignments no greater than EUR 150, or B2C supplies of goods already in the EU by an underlying supplier established outside the EU. The latter includes qualifying domestic supplies as well as intra-EU distance sales. Confirm that the interface actually facilitates the supply under the applicable rule; merely advertising goods or processing payment does not automatically settle the question.

That decision drives downstream reporting design: who is treated as the taxable person, who is responsible for invoicing, and which return population the transaction enters. Decide role first, then scheme and reporting.

Map roles before returns#

Build a role map for each material flow before changing OSS logic, invoice templates, or reports. Track unresolved points by flow and country where relevant instead of forcing one global conclusion.

One risk is applying one global rule across different scenarios. Prevent that by classifying each flow first, then applying scheme logic to that classification.

Keep records even when you are not deemed supplier#

Record-keeping obligations still apply to platforms, including cases where the platform is not deemed supplier. Keep evidence by flow and by filing period so treatment decisions can be reproduced during audit. Minimum evidence pack:

• role map, including seller, platform, and customer-facing invoice party
• classification note showing why the flow was included in or excluded from a scheme
• version history for tax-logic changes affecting treatment
• unresolved interpretation log by flow and country, with approvals for overrides

Watch reporting consequences#

If a taxable person uses an OSS scheme, all supplies in that scheme must be declared through that scheme's OSS return. OSS returns are additional and do not replace domestic VAT returns.

That can make misclassification costly in practice. It can distort who reports the supply and where reconciliation breaks between OSS and domestic filings. Before submission, reconcile deemed-supplier and non-deemed-supplier populations against the same transaction universe.

Escalate unresolved cross-border treatment#

A VAT Cross-Border Ruling may help with an envisaged complex transaction involving at least two participating Member States. Check current participation and national request conditions with the authority where the applicant is VAT-registered. It is not an automatic cure for a filing deadline or a guarantee that every authority will accept the requested interpretation.

If your team is still looking for one universal deemed-supplier rule, treat that as a warning sign. Use a narrower control loop instead: classify each flow, log open points by country, and escalate only the unresolved cases before they affect returns and invoices.

We covered this in detail in How Platform Operators Make EU VAT OSS Filing Defensible.

Best when you run mixed flows and need one decision table#

For mixed flows, build one decision table before you automate anything. It should separate scheme selection, filing cadence, exclusions, and escalation points, so each transaction type has a clear route.

Scheme decision table#

Use this table as an operating map. It is not a substitute for legal analysis.

If your answer depends on whether the platform is only facilitating or is treated as a deemed supplier, mark that flow as counsel-required before filing logic is finalized.

The Member State of identification is a control decision, not an admin detail. It is the single EU country where you register for the scheme, and in specified Union-scheme choices the selection can bind for the current calendar year plus two following years.

Operational ownership table#

Once the route is set, assign owners before returns start moving, and keep the control checks explicit.

Direct routing rules#

• If the flow is services only and there is no business or fixed establishment in the EU, evaluate Non-Union OSS first, then confirm scope before filing.
• For imports, test the intrinsic-value EUR 150 consignment limit, excise exclusion and intermediary requirement; assess import VAT separately if IOSS is not used.
• If a flow is in an OSS scheme, do not split that scheme population across local filings and the OSS VAT return.
• If role classification is unresolved, especially on deemed-supplier treatment, pause automation and escalate before the next submission cycle.

Keep filing calendars separate. Union and Non-Union run quarterly, while import runs monthly, so do not run mixed flows on one assumed filing calendar. For a broader comparison, see GST Digital Marketplace Platform Comparison for Australia, Canada, and India. Before you lock the decision table into operations, map each rule to implementation controls and audit trails in Gruv Docs.

Best when finance ops need a filing calendar and evidence pack#

If finance ops owns filing, build the calendar around the scheme and keep an evidence pack that can be reproduced from system records. That is a practical way to reduce late-cycle rework and weak audit trails when OSS and import flows run together.

1. Calendar by scheme, not by team habit

Union and non-Union returns are quarterly; IOSS returns are monthly. Return and payment are due by the end of the following month, including nil returns where required. Q3 activity therefore has a 31 October deadline, while September IOSS activity also closes by 31 October on its separate monthly return. Weekend and public-holiday dates do not extend the OSS deadline. Set an earlier internal approval and payment checkpoint.

1. Keep a minimum evidence pack for each period

For each supply retain the consumption state, supply type/date, taxable amount, VAT rate and amount, payments and corrections, and evidence for customer location. Link these to the rule version, liable entity, scheme identifier, filed return and payment reference. Keep OSS records electronically accessible for ten years from the end of the transaction year, including after leaving the scheme.

The Member State of identification is the single EU country where you register for the OSS scheme. In specified Union-scheme cases, that choice can bind for the calendar year plus the next two years. Member State of Consumption needs to stay intact because returns and VAT due are routed from the registration state to the relevant consumption states.

1. Run the close sequence in control order

A practical sequence is: classify flows first, lock ownership second, generate return datasets third, and reconcile to the VAT return last. This helps avoid reconciling before the scheme population is final.

If you choose an OSS scheme, all supplies under that scheme must be declared through that scheme's OSS return. The OSS return is additional and does not replace the VAT return, so reconciliation should test for both omissions and double counting across the two tracks.

1. Use an audit-reproduction checkpoint before pressure hits

Pass criteria: records needed for Record Keeping and Audits in OSS can be regenerated from logs and source exports, without rebuilding the filing story manually in spreadsheets. This checkpoint matters even when a platform is not treated as deemed supplier, because record-keeping duties can still apply.

If reproduction fails, fix the control before expanding automation. If the blocker is a genuinely complex cross-border VAT fact pattern, escalate for legal review or consider an advance VAT Cross-Border Ruling in participating EU countries.

Best when audit readiness is weak but filing is already live#

If filing is already live but your team cannot defend scheme decisions, treat audit evidence as part of filing control now, not as a cleanup task later. Build a controlled evidence register for each OSS VAT return period, along with a log for manual overrides and unresolved judgments. Since OSS VAT returns are additional and do not replace domestic VAT returns, keep evidence aligned to both obligations where relevant.

1. Decision trail for Deemed Supplier judgments

Keep a dated record for each case where the platform might be treated as a Deemed Supplier: transaction facts, conclusion, and approver. Online marketplaces and platforms can be treated, in certain circumstances, as having received and supplied goods themselves. Also keep records when the platform is not treated as deemed supplier, because record-keeping duties can still apply.

1. Transaction-to-scheme mapping by filing period

For each quarterly Union or non-Union period and each monthly import period, retain the mapping from transaction type to scheme choice, not just filed totals. Tie each population to the relevant return, the Member State of identification, and the Member State details used in the filing. The standard is reproducibility from source exports, not spreadsheet reconstruction under audit pressure.

1. Deregistration and exclusion watchlist

Track potential Deregistration and exclusion changes in a visible log. A taxable person or intermediary can leave a scheme voluntarily, or be excluded by a Member State, so this cannot live only in inboxes or adviser memory. When facts change, recheck your filing basis before the next period.

Verification checkpoint: for any period, can you produce records, invoices, and bad-debt-related support without a manual rebuild? If not, fix the register before the next cycle. If the facts raise genuinely complex cross-border VAT questions, escalate early and consider a VAT Cross-Border Ruling request under the national conditions of a participating EU country.

Best when legal uncertainty should stop automation#

Use automation only for rules that stay consistent across flows and countries. If the legal answer is uncertain, route the case to approval before filing.

1. Mixed-flow role conflict

If your model combines services, imported goods, and platform-facilitated goods, one tax rule may not be enough. OSS has three schemes: non-Union, Union, and import. Return cadence also differs: quarterly for Union and non-Union, monthly for import. When Taxable Person or Intermediary responsibility, or deemed-supplier treatment for platform-facilitated goods, is unclear, role and scheme judgments should be reviewed before filing. Verification checkpoint: test one sample order per flow and confirm why one scheme was used and why the other two were excluded.

1. Member State of Consumption splits the answer

If the same facts can produce different filing logic by Member State of Consumption, stop full auto-routing for those markets. OSS is optional, but once you use a scheme, all supplies in that scheme must be declared through that OSS return. Keep these cases behind reviewer gates and store the supporting analysis in the period file.

1. Deregistration needs a replacement filing plan first

Treat Deregistration as a control event, not an admin toggle. A taxable person or intermediary can leave voluntarily or be excluded, and OSS returns are additional rather than a replacement for domestic VAT returns. Before any move, document which supplies leave the scheme, who owns the replacement path, and how Member State of identification records are handled.

1. Bad debt assumptions belong in review, not code

Do not hard-code one bad-debt treatment across markets. OSS materials include rules on records, invoices, and bad debt relief, but they do not provide one EU-wide bad-debt rule for every case. When treatment is uncertain, get jurisdiction-specific confirmation. For complex cross-border VAT questions, consider a VAT Cross-Border Ruling request filed under national conditions in a participating EU country.

Conclusion#

The defensible approach is a sequence, not an acronym. Before the next filing cycle, map each in-scope flow to the relevant OSS special scheme: Union OSS, Non-Union OSS, or the Import Scheme.

1. Classify each flow first. Start at transaction level, then map to the relevant OSS special scheme. For each in-scope transaction, keep a clear link to the Member State of identification used for that scheme. If you choose that state under the Union scheme from multiple fixed establishments, that decision can bind you for the current calendar year plus the next two.

2. Choose the scheme by flow, then apply it consistently. The schemes are optional, but once you use one, all supplies that fall under that scheme must be declared through that scheme's OSS VAT return. Do not force mixed goods, services, and import legs into one shortcut rule. Test each leg on its own facts, especially where deemed-supplier treatment is uncertain.

3. Treat filing cadence as a control design issue. Union and non-Union returns are quarterly, and import-scheme returns are monthly. OSS returns are electronic and additional, not a replacement for the regular VAT return, so your close process should show what was included in OSS and what remained in regular VAT reporting.

4. Keep reproducible records and escalate gray zones early. Platforms have record-keeping obligations for facilitated goods and services, including scenarios where deemed-supplier status may not apply. Your period file should let a reviewer reproduce classification, scheme choice, identification state, and filed return data. For genuinely complex cross-border cases, consider requesting a VAT Cross-Border Ruling in a participating EU country where you are VAT-registered.

If your team needs help deciding where to automate versus where to keep approval gates for VAT-sensitive flows, talk to Gruv.