Key Takeaways
- Marketplace facilitator laws require platforms to collect and remit US Sales Tax on behalf of sellers, but they do not remove all compliance obligations from the seller
- Marketplace sales can still count toward economic nexus thresholds in many states, meaning sellers may trigger registration obligations they are not aware of
- Sellers with both marketplace and direct sales channels face a more complex compliance picture than those selling exclusively through one platform
- Misclassifying products or assuming platform-level compliance covers all scenarios is a common and costly mistake
- Businesses selling into the US through marketplaces should conduct a full nexus review to understand their true compliance exposure
What Marketplace Facilitator Laws Actually Say
Marketplace facilitator laws were introduced by US states in the years following the Wayfair decision to simplify sales tax collection for high-volume online transactions. Rather than requiring each individual seller to register and remit tax in every state where they had economic nexus, these laws shifted that responsibility to the marketplace platform itself.
On paper, this looks like a clean solution. In practice, the protection it offers sellers is more limited than most assume.
The laws generally require the marketplace to collect and remit tax on sales it facilitates. They do not require the marketplace to manage the seller’s broader compliance position. They do not assess whether the seller has nexus arising from other activities. They do not account for direct sales the seller makes outside the platform. And they do not resolve questions about product taxability, exemption certificates, or historical liability.
What marketplace facilitator laws do is handle one specific part of the compliance process for one specific channel. Everything else remains the seller’s responsibility.
The Nexus Problem Most Sellers Do Not See Coming
One of the most significant and least understood consequences of selling through marketplaces is the impact on economic nexus thresholds.
In many US states, marketplace sales count toward the seller’s economic nexus threshold, even where the marketplace is collecting and remitting the tax. This means a seller who believes they have no direct US Sales Tax obligations because they sell exclusively through Amazon may already have crossed the economic nexus threshold in multiple states without knowing it.
Understanding what triggers US Sales Tax compliance obligations is essential for any seller operating in the US market, regardless of which channel they sell through. Thresholds vary by state, and the look-back period used to assess whether a threshold has been crossed differs too.
Once a seller crosses a threshold, they may have registration, filing, and reporting obligations in that state even if all their sales in that state were made through a marketplace facilitator. Some states are explicit about this. Others are less clear, which creates uncertainty that sellers often resolve by doing nothing and hoping for the best. That is rarely a sound strategy.
Where the Protection Breaks Down
The assumption that marketplace protection is comprehensive tends to break down in several predictable situations:
Direct sales outside the marketplace
Many sellers operate across multiple channels simultaneously. They may sell through Amazon in the US while also taking direct orders through their own website or through a separate platform that does not qualify as a marketplace facilitator. In these cases, the seller has direct nexus obligations that the marketplace cannot cover, and the combination of marketplace and direct sales can accelerate threshold crossings across states.
Product taxability
Marketplace facilitators collect tax based on the information available to them, including how products are classified. Where a seller has misclassified a product, or where the platform applies a default taxability rule that does not accurately reflect the product’s status in a particular state, the tax collected may be incorrect. The seller, not the platform, is typically responsible for the accuracy of underlying product classifications.
Exempt sales
Where a seller makes sales to exempt buyers, such as resellers or tax-exempt organisations, the exemption certificate process is the seller’s responsibility. A marketplace may not have visibility into the exempt status of the buyer, and the seller cannot assume that exemption claims will be handled automatically.
Historical liability
Marketplace facilitator laws generally apply from the date of enactment in each state. They do not retroactively protect sellers from liability that arose before the laws came into effect. Sellers who were making significant sales into US states before the laws were introduced may have pre-existing exposure that no amount of marketplace compliance will resolve.
For a detailed breakdown of how marketplace facilitator laws interact with seller obligations, see our guide on marketplace facilitator laws and US Sales Tax.
The 2026 CTC Map: Which Markets Are Live, Rolling Out, or Incoming
The global CTC landscape is uneven. Some countries already operate mature clearance or real-time reporting systems. Others are introducing mandatory structured e-Invoicing first, with reporting obligations to follow.
Live or established CTC and e-Invoicing markets include Italy and Malaysia. Italy has operated mandatory B2B and B2C e-Invoicing through SdI since 2019. Malaysia’s phased e-Invoicing regime is also active, with implementation continuing into 2026 through the Inland Revenue Board’s MyInvois framework. Malaysia’s official e-Invoice guideline confirms phased implementation dates, including 1 July 2026 for certain newer businesses with annual turnover or revenue of at least RM1 million.
Markets rolling out or expanding in 2026 include Poland, France, Belgium, and Croatia. Poland’s KSeF system became mandatory for B2B e-Invoicing in early 2026. France is introducing mandatory B2B e-Invoicing and e-reporting from September 2026, with phased issuing obligations for large and mid-sized companies in 2026 and smaller businesses in 2027. Belgium requires structured domestic B2B e-Invoicing from 1 January 2026, with near-real-time reporting expected later.
Markets with incoming or phased mandates include Germany, Spain, and the wider EU. Germany introduced the ability to receive compliant e-invoices from 1 January 2025, with issuing obligations phased in for larger businesses from 2027 and all businesses by 2028. Spain’s B2B e-Invoicing framework continues to develop, with the Council of Ministers approving a royal decree for mandatory B2B e-Invoicing in March 2026. The mandate is expected to come into force in October 2027.
For businesses, the key message is that CTC compliance is not one project. It is a rolling programme of country-specific mandates, formats, timelines, platforms, and operating models.
How ViDA Will Reshape CTC Requirements Across the EU
VAT in the Digital Age, usually shortened to ViDA, is the EU’s major VAT modernisation package. It aims to reduce fraud, simplify compliance, and align VAT rules with the digital economy.
The most important CTC-related change is the move toward digital reporting requirements for intra-EU B2B transactions. The European Commission says the new system introduces real-time digital reporting for cross-border trade based on e-Invoicing, helping member states fight VAT fraud, including carousel fraud.
In practice, ViDA will push businesses toward structured e-Invoicing and faster transaction-level reporting across the EU. It will also create pressure for member states to align domestic systems with EU standards over time. Cross-border B2B digital reporting requirements are due from 1 July 2030, while member states with domestic real-time reporting obligations must align with EU standards by 1 January 2035.
For multinational businesses, ViDA matters even before the main 2030 reporting date. It is shaping national policy decisions now. Countries introducing domestic e-Invoicing mandates are designing systems with EU interoperability, structured formats, and future digital reporting in mind.
This means finance teams should not treat ViDA as a distant regulatory event. The practical preparation starts with today’s invoice data: customer VAT numbers, product taxability, exemption codes, credit note logic, invoice sequencing, archiving, and ERP integration.
For a broader VAT foundation, see our guide on how digital VAT processing improves reclaim success rates.
The Key System Gaps That Lead to CTC Non-Compliance
The most common CTC failures are not caused by a lack of awareness. They happen because business systems were built for periodic VAT reporting, not real-time validation.
The first gap is poor master data. If customer names, VAT IDs, addresses, entity registrations, product codes, or tax classifications are incomplete, invoices can fail validation before they are issued.
The second gap is format readiness. Many legacy invoicing workflows still rely on PDFs, spreadsheets, manual uploads, or email-based approval. CTC mandates usually require structured invoice data, not just a document image.
The third gap is weak ERP integration. A company may have compliant invoice data, but if its ERP cannot connect to a government platform, Peppol access point, accredited provider, or local API, the invoice flow still breaks.
The fourth gap is unclear exception handling. Rejected invoices need ownership. Someone must monitor failed submissions, correct data, resubmit invoices, communicate with customers, and reconcile status updates with accounting records.
The fifth gap is country-by-country rule fragmentation. A business may assume one e-Invoicing vendor or configuration will work globally, only to discover that each country has different fields, formats, transmission channels, deadlines, archiving rules, and buyer communication requirements.
The sixth gap is VAT reporting reconciliation. CTC data, VAT returns, ledgers, sales reports, and purchase records must align. If real-time submissions show one version of the transaction and the VAT return shows another, the discrepancy can trigger audits or blocked deductions.
For businesses comparing e-Invoicing tools, see our guide to the best e-Invoicing compliance solutions.
Next Steps: Mapping Your CTC Exposure Before the Next Mandate Lands
The first step is to build a CTC exposure map. List every country where your business is VAT registered, has a fixed establishment, issues domestic invoices, receives supplier invoices, sells cross-border, or operates through marketplaces or platforms.
Then classify each market by mandate status: live, rolling out, incoming, or under consultation. For each market, identify the model: clearance, reporting, structured e-Invoicing only, or hybrid.
Next, map your invoice flows. Separate sales invoices, purchase invoices, credit notes, self-billing, intercompany charges, exports, intra-EU supplies, domestic B2B, B2C, and services. CTC rules often apply differently depending on transaction type.
After that, test system readiness. Can your ERP create the right data fields? Can it generate the required format? Can it connect to the required platform? Can it receive status messages? Can it store the cleared invoice and audit trail?
Finally, assign ownership. CTC compliance cannot sit only with tax. It needs a shared operating model across finance, IT, tax, legal, procurement, and customer-facing teams.
Prepare Your VAT Operations for Real-Time Reporting
CTC mandates are arriving market by market, but the direction is clear: VAT compliance is becoming digital, transactional, and real time.
VAT IT helps businesses understand their VAT exposure, strengthen digital compliance processes, and prepare for evolving e-Invoicing and reporting obligations across jurisdictions.
Need to assess where your business is exposed to CTC requirements? Speak to our team about mapping your VAT compliance risks before the next mandate goes live.
Frequently Asked Questions
1. Are services treated the same as goods under CTC mandates?
Not always. Some CTC mandates apply broadly to goods and services, while others treat services differently depending on whether the transaction is domestic, cross-border, B2B, B2C, or exempt. Services can also trigger different VAT place-of-supply rules, invoice fields, and reporting obligations. Businesses should assess services separately instead of assuming goods rules apply automatically.
2. What data format do CTC submissions typically require?
Most CTC systems require structured electronic data rather than a PDF. Common formats include XML, UBL, CII, Peppol BIS Billing, or country-specific schemas. The required format depends on the jurisdiction and platform. The important point is that the invoice data must be machine-readable, validated, and capable of being processed by tax authority systems.
3. Can a business use the same invoicing software across all CTC countries?
A business may use one global invoicing or ERP platform, but it usually needs country-specific configurations, integrations, formats, and workflows. CTC rules differ by market, including clearance steps, reporting deadlines, accepted schemas, archiving rules, and buyer delivery methods. The software must support local compliance rather than only generic e-Invoicing functionality.
4. Does a business need to store CTC-submitted invoices separately from its own records?
Usually, businesses must retain both their accounting records and compliant invoice evidence, including the submitted invoice, clearance status, timestamps, unique identifiers, and any authority response. Whether this requires separate storage depends on local law and system design. The key is being able to prove what was issued, submitted, accepted, corrected, and archived.
