Value-added tax tends to appear somewhere near the bottom of the list, treated as a compliance checkbox to be handed to outside counsel once your company hits a certain revenue threshold in a new country. A decade ago, this framing made sense. In today’s economy, however, it doesn’t.
The regulatory environment around indirect tax compliance has accelerated sharply in recent years. Factors including real-time data-matching between VAT filings and payment processor records now operational in major markets, e-invoicing mandates expanding globally, and new rules that shift tax collection responsibility in unforeseen ways all play a role.
The result of these changes is that the traditional approach of waiting to deal with the issue until the company has hit scale is riskier. Anrok has put together four key blind spots where U.S. enterprise finance teams most often underestimate their tax exposure and where 2026 regulatory changes have raised the stakes.
The trap
Most U.S. finance leaders approaching their first international market think about VAT registration as an isolated element. For instance, choosing to launch in Germany and only thinking about getting German VAT numbers. In this scenario, what gets missed is that EU VAT rules don’t stop at the border. Once you’re selling across multiple member states, you can trigger registration and filing obligations well beyond the one country you started with..
VAT, at its core, is a supply-chain tax. Every transaction has its own VAT treatment, determined by where the buyer is, not just where the seller happens to be registered. That means VAT isn’t something a company registers for once and checks off a list. Each country decides independently whether a sale is taxable there, based on its own rules for buyer location, transaction type, and registration thresholds. A U.S. company might set up its first VAT registration wherever its first international deal closes and treat that as “VAT is handled” — but as customers show up elsewhere, each new country can bring its own obligations, entirely independent of that first registration. One VAT number covers one country. It says nothing about the others.
Real-world example
Consider a Chicago-based enterprise SaaS company launching in the EU as an example. They chose to register after bringing on their first customers across the EUMunich. As a result, the finance team registers for VAT via the EU OSS scheme and automatically thinks the VAT box is checked. Six months later, during a routine review, their outside counsel flags that a growing share of new customers are individuals in Switzerland and Norway.. The company has been making taxable supplies in two additional jurisdictions with entirely separate VAT registration requirements. The retroactive filings and penalties became the first line item in the international expansion budget that everyone overlooked.
What 2026 changed
What is notable about 2026 is that the EU’s VAT in the Digital Age reform is moving into its next implementation.. Among its provisions is an expansion of the digital reporting requirements that feed into cross-border transaction monitoring. EU member states are working towards being able to share transaction-level data with one another more rapidly and systematically, meaning the gap between when a company makes a taxable supply in a country and when that country’s tax authority can identify it has shrunk.
Finance team checklist item
Before launching into a new international market, map not just the target country’s VAT rules, but the key supply-chain implications. This includes where your customers are located, where services are being delivered, and whether there are any cross-border registrations that cover those supplies.
The trap
E-invoicing, which is the requirement to issue invoices in a structured digital format through a government-connected network, is one of the fastest-moving areas of indirect tax compliance globally. It’s also one of the most consistently underestimated areas by U.S. companies entering their first international markets.
The misunderstanding among finance teams is understandable, but sneaky. Your finance team is aware they need to issue invoices to customers and have a billing system which does that. What they miss, however, is that, in a growing number of countries, an emailed PDF to a customer is not a compliant invoice. The invoice must be generated in a specific format, often XML or JSON,and transmitted through a designated government platform or certified network. In some cases, it must also be validated and cleared before it reaches the customer while being retained in a format that satisfies local audit requirements.
A failure to comply won’t just create the risk of penalty, as in some jurisdictions a noncompliant invoice means the underlying transaction is unrecorded for VAT purposes, which creates a bigger liability.
Real-world example
Consider a Boston-based analytics platform signing its first Indian enterprise customer. To serve them directly, the company sets up a local entity and registers for GST in India. The company begins invoicing through the standard billing system they’ve always used. The invoices are accurate, detailed, and issued perfectly on time. What the finance team failed to realize, however, is that once their Indian revenue crossed India’s e-invoicing turnover threshold, GST law required those invoices to be generated through the government’s Invoice Registration Portal and returned with an Invoice Reference Number and QR code before issuance to the customer. After two quarters of noncompliance invoicing, the company’s Indian customer flags the issue during their own GST audit, requiring retroactive IRP registration and coordination with the Indian Central Board of Indirect Taxes and Customs, after which both companies are now under scrutiny.
What 2026 changed
Indian’s Central Board of Indirect Taxes and Customs has extended its GST compliance data-matching to include payment platform records in 2026. This means the gap between what companies report and what payment processors transmit to the government has become an active audit sign, rather than a passive discrepancy. Companies that have been invoicing in a noncompliant manner in the past while payments clear through Indian banking channels are now facing a higher likelihood of audits.
Additionally, in the EU, the new digital reporting requirements are also moving member states towards more standardized e-invoicing frameworks. France’s mandate went live on Sept. 1, 2026 for large and mid-sized companies, and it’s not an isolated case. Belgium’s B2B mandate took effect at the start of 2026, Poland is phasing in its KSeF system through the first half of the year, and Germany already requires businesses to be able to receive structured e-invoices. Globally, more than 30 countries globally have some form of e-invoicing mandates in effect with dozens more scheduled in the near future.
Finance team checklist item
For every new market you enter, determine whether e-invoicing is mandated, along with what format and transmission method is required. You should also flag whether your billing infrastructure can produce compliant invoices before ever issuing a single one, rather than waiting for a customer to flag an issue.
The trap
Deemed-supplier, or marketplace-facilitator, rules are provisions that move VAT collection responsibility from the seller to an intermediary platform. They were originally meant to be for large e-commerce marketplaces, but U.S. enterprise companies are increasingly getting caught up in them in ways they don’t anticipate.
The most common situation involves a U.S. company that sells through a third-party platform in an international market. Under traditional VAT logic, the U.S. company might expect to have the collection and remittance obligation. Under deemed-supplier rules, though, the platform may be treated as the supplier for VAT purposes. This means that it collects and remits VAT, shifting the U.S. company’s obligation.
While seemingly simple, and perhaps even a benefit, it creates a unique problem. The U.S. company may accidentally be reporting transactions with its own VAT filings that the platform is already reporting, potentially leading to duplications or mismatches that trigger an audit on both sides.
Real-world example
Consider a Seattle-based enterprise software company that starts selling its product through a regional online marketplace in the EU. The U.S. company registers for VAT in the marketplace’s home country or where their customers are located, thinking it’s their obligation, and begins filing returns that include revenue flowing through the reseller. What they missed is that the marketplace qualified as a deemed supplier under EU standards, meaning the platform has already been collecting and remitting VAT on those transactions. The U.S. company has inadvertently been double-counting taxable supplies in its own filings, which causes an unwinding of 18 months of filings and results in issuing corrected returns in multiple jurisdictions when an audit occurs.
What 2026 changed
At the start of the year, Manitoba extended its Retail Sales Tax to remote sellers of cloud computing. It’s one of the most recent North American examples of a jurisdiction expanding its indirect tax net to grab foreign digital suppliers who previously fell outside the rules. The province joins a growing list of Canadian jurisdictions that now require nonresident digital service providers to register and collect. It’s also representative of a growing trend globally.
Finance team checklist item
For any market entered via a third-party platform, distributor, or reseller, determine right away whether that party qualifies as a deemed supplier under local VAT rules. Coordinate filing positions accordingly to avoid double-counting.
The trap
The standard audit exposure that most U.S. finance teams carry when thinking about VAT risk is mitigated by time. If something is wrong with past filings, a tax authority might audit you later in the future. It’s an uncomfortable reality, but one that is manageable due to the lengthy timing. Exposure is also limited to what’s on your filings, for the most part. However, this is an outdated approach.
Tax authorities in major markets are are increasingly cross-referencing VAT filings against other data they already hold — e-invoice records, marketplace and payment platform data, and electronic receipts — to flag inconsistencies automatically. For example, Italy’s tax authority, for example, ran a nationwide campaign in 2026 that cross-checked VAT returns directly against e-invoice and receipt data already on file. This doesn’t mean every mismatch becomes an audit overnight, but it does mean discrepancies get surfaced automatically rather than waiting for a manual review to stumble onto them.
Real-world example
Think for a moment about a New York-based data infrastructure company that expands into India and registers for Goods and Services Tax. Its GST returns are all filed correctly and on time. What’s missed, though, is that some customer payments are being processed through an Indian payment gateway that reports the transaction-level data to the Central Board of Indirect Taxes and Customs. This data shows that gross payments are slightly higher than what’s appearing in the GST filings. This is flagged for two quarters. What would have been a small correction under the old audit model now becomes a formal inquiry due to the length of time, with documentation that may take weeks or months to satisfy.
What 2026 changed
MBB Corporate Services, the global strategic consultancy and professional services firm, outlined how India’s CBIC extended its GST scrutiny framework this year. This action resulted in payment platform data, invoicing systems, e-way bills, income tax filings, and corporate filings, with GST filing data as a standard matching input, rather than an exceptional audit flag. Companies operating in India should now assume that any discrepancy between reported turnover and other government data sources will be found on a systematic level, rather than being caught only if stumbled across by a human auditor.
Further, the EU’s VAT in the Digital Age implementation strategy includes a phased rollout of digital reporting that creates real-time transaction visibility for member state tax authorities. The Organisation for Economic Co-operation and Development’s ongoing Tax Administration 3.0 initiative is pushing towards greater international interoperability between these national data systems as well. This means that data-matching audit exposure isn’t just confined to individual enforcement markets, but rather becoming a global baseline.
Finance team checklist item
Audit your data consistency before you file, rather than after. Ensure you reconcile all payment processor data, billing system output, and VAT return inputs as a standard pre-filing step and maintain documentation explaining any differences.
The 2026 regulatory landscape, including ViDA’s digital reporting infrastructure, India’s payment-data matching, the UAE’s amended enforcement posture, and the ongoing expansion of indirect tax obligations into markets like Canada, has changed. All these changes reflect a global shift towards real-time compliance. Tax authorities no longer need to wait for an audit cycle to identify a mismatch, since systems capture them instantly and aggregate them for when the audit comes.
For finance leaders, the posture shift isn’t about adding resources but about moving indirect tax compliance upstream in the market-entry process. Treat VAT registration, e-invoicing infrastructure, and filing requirements as pre-launch diligence tasks rather than corrections after the fact. By making this shift, you can ensure you aren’t paying high penalty costs for remediation in the future.
This story was produced by Anrok and reviewed and distributed by Stacker.