If you've ever tried to verify a VAT number by hand, you know the drill. You visit the EU's VIES portal, paste in the number, wait for a response, and hope the system isn't down. For UK numbers, you go to HMRC's separate checker. Then you copy the result somewhere, maybe into a spreadsheet, maybe into your CRM. And then you do it again for the next customer.

For a business processing a few invoices a month, that's annoying. For a SaaS platform onboarding hundreds of B2B customers, it's a genuine operational bottleneck — and a compliance risk if anything slips through.

The good news is that VAT number validation is one of the most straightforward compliance tasks to automate. With the right API, you can validate numbers in real time, directly within your own app or workflow, with no manual steps at all.

What Does VAT Number Validation Actually Check?

A VAT number isn't just a string of digits. Each EU member state issues them in its own format, and the VIES (VAT Information Exchange System) database is the authoritative source for checking whether a given number is both valid and active.

When you validate a VAT number properly, you're checking three things:

• Format — does the number match the expected pattern for that country?
• Active status — is the number currently registered and active with the tax authority?
• Business name — in many cases, you can also retrieve the registered name and address.

That last point matters more than people realise. If a customer gives you a VAT number that's technically valid but belongs to a different company, format checking alone won't catch that. A proper validation call against VIES will.

For UK VAT numbers, VIES is no longer the right system — since Brexit, UK numbers are validated through HMRC's own Making Tax Digital infrastructure. Any tool that only checks VIES will give you incorrect results for UK registrations.

Why VIES Alone Is Not Enough

VIES is a useful system, but it has real limitations if you're relying on it directly.

First, availability. VIES has a well-documented history of downtime and slow responses, particularly when querying national tax authority systems that aren't always online 24/7. If your validation call fails because a country's system is temporarily unavailable, you have to decide whether to reject the customer or let them through unvalidated.

Second, rate limits and reliability. Querying VIES directly at scale is unreliable. It wasn't designed to be used as a backend service by commercial applications.

Third, it only covers the EU. UK VAT numbers require a completely separate API call to HMRC. If your business serves both EU and UK customers — which most do — you need to handle two different systems.

Automating VAT validation isn't a nice-to-have. If you're invoicing B2B customers across Europe, it's the difference between clean books and a compliance headache.

How Automated VAT Validation Works

A VAT validation API sits between your application and the underlying tax authority databases. You send a VAT number, it routes the query to the correct system (VIES for EU numbers, HMRC for UK numbers), handles retries and fallbacks, and returns a structured response.

A typical response tells you whether the number is valid, whether it's currently active, and — where available — the registered business name and address. You can use that information to auto-populate billing details at checkout, gate B2B pricing, or log a validation timestamp for audit purposes.

The VAT API from thevatapi.com handles validation for all 27 EU member states and UK VAT numbers in a single endpoint. You send the VAT number, it returns a structured JSON response with validity status, business name, and address where available. There's no need to maintain separate integrations for EU and UK.

Integrating VAT Validation Into Your App

At Checkout or Signup

The most common integration point is during checkout or account creation. When a B2B customer enters their VAT number, you validate it in real time before they complete registration. If the number is invalid or inactive, you flag it immediately rather than discovering the problem when you try to issue a VAT-exempt invoice.

In Your Billing Flow

If you're using Stripe or another payment processor, you likely collect VAT numbers as part of your billing setup. A validation API call at this point lets you confirm the number before it goes into your invoicing system — which matters because issuing a zero-rated invoice to an invalid VAT number is a compliance error that can come back to bite you in an audit.

In Bulk or Batch Processes

If you've got existing customer data that was never validated, you can run batch validation to clean up your records. This is worth doing periodically even for ongoing customers — VAT registrations can lapse, companies can deregister, and numbers that were valid at signup may no longer be active.

What to Do With the Validation Result

Validation isn't a binary pass/fail in all cases. VIES sometimes returns inconclusive results when a national system is temporarily unavailable — different from a definitive 'invalid' response. Your integration should handle these cases explicitly.

A sensible approach is to store the full validation response alongside the VAT number in your database, along with a timestamp. That way you have an audit trail showing that you made a good-faith effort to validate the number at the time it was provided.

For inconclusive responses, you might choose to let the customer proceed while flagging the account for manual review, or retry the validation later. Either way, having the infrastructure in place to make the call automatically is the first step.

Format Validation vs Live Validation

There's a distinction worth drawing between format validation (checking that the number matches the expected pattern) and live validation (checking against the actual tax authority database).

Format validation is fast and can be done client-side without any API call. It catches obvious errors like missing digits or wrong prefixes. But it won't tell you whether the number is actually registered — a correctly formatted number can still be inactive or fraudulent.

For any business where VAT compliance matters — which is most B2B businesses trading in Europe — you want live validation, not just format checking. The extra API call is worth it.

Building This Into Your Stack

VAT number validation is one of those infrastructure pieces that takes half a day to build properly and then runs silently in the background forever. The effort is front-loaded.

What you need: an API key, an HTTP client, and a few lines of code to call the endpoint and handle the response. Most implementations are under 30 lines. You can check the documentation at thevatapi.com to see request and response formats, error codes, and example integrations.

The result is that your team never needs to manually verify a VAT number again — and your finance team has the confidence that every invoice you issue is backed by a verified, active registration.

VAT compliance sounds like a finance problem, but for developers it's an infrastructure decision. The API you choose becomes a dependency in your billing system, your checkout flow, and your invoicing logic. Pick the wrong one and you're dealing with unreliable uptime, stale rate data, or an SDK that hasn't been updated since 2021.

There are more options in this space than you might expect, ranging from general tax APIs that bolt on VAT as one feature among many, to purpose-built VAT APIs designed for EU and UK compliance specifically. This comparison focuses on the latter — because if VAT compliance is what you need, a specialist tool will serve you better than a generalist one.

What to Look For in a VAT API

Before comparing specific products, it's worth being clear about what you actually need. Most VAT use cases fall into three categories: validating VAT numbers, looking up VAT rates by country and product type, and calculating VAT amounts. Not all APIs cover all three equally well.

Other factors worth evaluating: how fresh is the rate data, how reliable is the uptime, how well-documented is the API, and what happens when you need to validate a UK number (which requires a separate HMRC integration, not just VIES)?

The VAT API (thevatapi.com)

The VAT API is built specifically for EU and UK VAT compliance. It covers VAT number validation for all 27 EU member states plus the UK, current VAT rates for every EU country (including reduced and super-reduced rates by category), and VAT amount calculations.

What sets it apart for developers is the simplicity. It's a clean REST API with JSON responses, comprehensive documentation, and a consistent structure across all endpoints. The validation endpoint handles both EU numbers (via VIES) and UK numbers (via HMRC) transparently — you send the number, it figures out the routing.

Rate data is kept current, which matters because EU member states adjust their rates more often than most people realise. There's a dedicated rates endpoint that returns the full rate structure for any country, including reduced rates for categories like food, books, and medical supplies. You can explore the full API at thevatapi.com.

Pricing is usage-based and there's a free tier that works well for development and lower-volume production use. For a straightforward VAT use case, it's one of the most cost-effective options available.

Vatstack

Vatstack focuses primarily on VAT number validation and has been around for a few years. It supports EU and UK validation, returns business name and address data where available from VIES, and has a reasonably clean API design.

It's a solid choice for pure validation use cases, though it doesn't offer rate lookup as a core feature. If your use case is specifically B2B VAT number verification at signup or checkout, it's worth evaluating. For broader VAT compliance needs — rates, calculations — you'd need to supplement it.

TaxJar

TaxJar is primarily a US sales tax automation platform that has expanded to cover international VAT. It's a heavyweight option with a lot of features, but it's built around US tax workflows and VAT support feels like an add-on rather than a core product.

If your business is primarily US-based and you need light-touch EU VAT coverage alongside US sales tax, TaxJar might make sense. If you're building something EU-first or need deep VAT compliance, you'll probably find it more complex and expensive than you need. Their documentation is available at taxjar.com.

Avalara

Avalara is the enterprise end of the market. It's a comprehensive global tax compliance platform used by large businesses with complex multi-jurisdiction requirements. It handles VAT, but it also handles US sales tax, GST, customs duties, and a lot more.

The tradeoff is complexity and cost. Avalara isn't a REST API you drop into a weekend project — it's an enterprise integration with a corresponding sales process and pricing model. For most SaaS products and SMBs, it's significantly more than you need.

Vatlayer

Vatlayer offers EU VAT rate data via a simple API and has been one of the longer-standing options in the space. It's reasonably well-documented and easy to integrate for basic rate lookups.

The main limitation is that it focuses on rate data rather than validation, and its UK coverage post-Brexit has been inconsistent. If you're building something that needs current, reliable VAT number validation alongside rate data, you'll likely need to combine it with another service.

How to Choose

For most developers building SaaS products, marketplaces, or e-commerce platforms that serve EU and UK customers, the decision comes down to a few questions. Do you need validation, rates, or both? Do you need UK VAT support? How much complexity can your integration absorb?

A purpose-built VAT API will almost always outperform a general tax platform on documentation quality, response reliability, and cost — especially at lower volumes.

If you need a single API that handles EU and UK VAT number validation plus current rate data in a clean, developer-friendly package, the VAT API at thevatapi.com is the most direct option. It covers the core use cases without the overhead of an enterprise platform, and the documentation makes integration genuinely quick.

If your needs are primarily EU validation without UK requirements, Vatstack is a reasonable alternative. If you're an enterprise with complex global requirements, Avalara is worth evaluating. For most use cases in between, a purpose-built tool beats a generalist one every time.

A Note on Data Freshness

One thing that rarely gets discussed in API comparisons is how often the underlying data gets updated. EU VAT rates do change — member states periodically adjust standard, reduced, and super-reduced rates, and temporary rate changes need to be tracked and rolled back.

An API that was accurate two years ago might be serving stale data today. When evaluating any VAT rate API, it's worth asking specifically about update frequency and how quickly rate changes are reflected in the API's responses. For production applications, stale VAT rates aren't just inconvenient — they can result in incorrect invoices.

The moment European customers start signing up for your SaaS, VAT enters the picture. And for a lot of founders, that triggers a mild panic. Tax consultants, OSS registrations, reverse charge mechanisms — it sounds like a full-time job.

The reality is more manageable than it looks. The hard part of EU VAT compliance — the rules — is well-documented. The practical part — collecting the right information and charging the right rates — can be handled almost entirely through APIs and some thoughtful checkout design.

This post walks through what you actually need to build: what data to collect, when to charge VAT, how to validate VAT numbers, and how to keep your rates current without manually tracking every EU member state.

The Core Rules You Need to Know

B2B vs B2C Makes All the Difference

The most important distinction in EU VAT is whether you're selling to a business (B2B) or a consumer (B2C). For B2B sales where the customer has a valid VAT number and is based in a different EU country, the reverse charge mechanism applies — you issue a zero-rated invoice and the customer self-accounts for VAT in their own country. You don't charge VAT. You just need to verify their VAT number.

For B2C sales — selling to consumers or businesses without a valid VAT number — you charge VAT at the rate applicable in the customer's country. For digital services, the EU's One Stop Shop (OSS) scheme simplifies this by letting you declare and pay VAT for all EU countries through a single registration in one member state.

UK Is a Separate System

Post-Brexit, the UK has its own VAT system, independent of the EU. UK customers need UK VAT validation, and the rules around when to charge UK VAT differ from EU rules. If you're selling to UK businesses, you'll want to validate their UK VAT numbers through HMRC, not VIES.

What to Build: A VAT Compliance Checklist for SaaS

Here's the minimum viable VAT implementation for a SaaS product with EU and UK customers.

1. Collect the Right Customer Data

At checkout or account creation, collect the customer's country and whether they have a VAT number. Make the VAT number field optional but present — many B2B customers expect to enter it and will be frustrated if they can't.

Store the country and VAT number in your customer record. You'll need it for invoicing, and you'll need it to determine whether to charge VAT.

2. Validate VAT Numbers in Real Time

When a customer enters a VAT number, validate it immediately. Don't wait until you issue the invoice. Use a service like The VAT API to check the number against VIES (for EU numbers) or HMRC (for UK numbers). The API returns whether the number is valid and active, and often the registered business name.

Store the validation response — status, business name, timestamp — alongside the VAT number. This is your audit trail.

3. Determine Whether to Charge VAT

The logic here is straightforward once you have the data:

• Customer has a valid EU VAT number and is in a different EU country from you → reverse charge, zero-rated invoice.
• Customer is an EU consumer (no VAT number) → charge VAT at their country's rate.
• Customer is a UK business with a valid UK VAT number → reverse charge applies.
• Customer is in your own country → standard domestic VAT rules apply.

4. Keep VAT Rates Current

EU VAT rates change. Not constantly, but regularly enough that hardcoding them is a mistake. Using the VAT API rates endpoint returns the current rate structure for any EU country, including standard, reduced, and super-reduced rates by category.

5. Generate Compliant Invoices

EU VAT invoices have specific requirements: your VAT number, the customer's VAT number (for B2B), the applicable rate, the VAT amount, and for reverse charge invoices, the relevant legal reference. If you're using Stripe, many of these fields can be configured through their invoice settings — but you need to make sure the data flowing into the invoice is correct upstream.

OSS Registration: Do You Need It?

If you're selling digital services to EU consumers (B2C) and your cross-border EU sales exceed €10,000 per year, you need to account for VAT in each customer's country. The OSS scheme simplifies this enormously — instead of registering for VAT in every EU country separately, you register for OSS in one member state and file a single quarterly return covering all EU sales.

For most SaaS businesses with EU consumer customers, OSS registration is the right approach. It's not complex, but it does require quarterly filings. A good accountant familiar with EU VAT can handle these efficiently.

The Stack That Makes This Manageable

You don't need enterprise tax software to handle EU VAT compliance for a SaaS product. A reasonable stack looks like this: a billing platform (Stripe Billing or Paddle both have VAT support built in), a VAT validation API for checking customer VAT numbers at signup, a VAT rates API for keeping your rate data current, and an accountant to handle the actual VAT returns.

The goal is to automate the data collection and validation so your accountant has accurate records to work from — not to replace the accountant entirely.

The API parts of this are genuinely straightforward. Building the validation call and rate lookup into your checkout flow is a day's work. After that, it runs automatically.

Common Mistakes to Avoid

Charging the wrong VAT rate because you hardcoded rates that have since changed. Issuing zero-rated invoices without validating the customer's VAT number. Not storing validation timestamps, which you'll need if you're ever audited. Not handling UK numbers separately from EU numbers after Brexit.

None of these are catastrophic individually, but they accumulate into compliance risk. Automated validation and current rate data through an API eliminates most of them at source.

Building an invoicing system is one of those projects that seems straightforward until you account for international VAT. A domestic invoice is simple enough. Add the goods or services, apply the rate, show the tax amount, done. But once you're invoicing customers across Europe — with different VAT rules for B2B and B2C customers, different rates by country, and different documentation requirements — the complexity grows quickly.

The good news is that most of this complexity can be automated. The rules are consistent and well-documented. What you need is the right data at the right point in the flow, and the logic to apply it correctly.

The Data You Need Before You Can Generate an Invoice

A VAT-compliant invoice starts with good customer data. You need to know where the customer is based (billing address, not delivery address), whether they're a business or consumer, and if they're a business, their VAT registration number.

This data should be collected and validated at the point of customer onboarding or checkout — not at invoice generation time. By the time you're generating an invoice, the VAT treatment should already be determined.

VAT Number Validation: The Foundation of B2B Invoicing

If you're issuing zero-rated (reverse charge) invoices to B2B customers in other EU countries, validating their VAT number is not optional — it's the basis of your legal justification for not charging VAT. The VAT API provides a REST endpoint that validates EU numbers through VIES and UK numbers through HMRC, returning validity status, business name, and address where available.

Your customer onboarding flow should call this endpoint when a VAT number is entered. Store the full response — valid/invalid status, business name, timestamp — in your customer record. This serves as your audit trail.

For ongoing customers, consider periodic re-validation. VAT registrations can lapse. A customer whose VAT number was valid at signup may have deregistered a year later. Quarterly re-validation of active customer VAT numbers is a reasonable practice for businesses with audit exposure.

VAT Rate Lookup

For B2C invoices to EU consumers, you need the correct VAT rate for the customer's country. Rather than maintaining a rate table yourself, integrate with a VAT rates API that returns current rates by country code.

The rates endpoint at thevatapi.com returns the current standard, reduced, and super-reduced rates for any EU country. Cache the rates in your application with a daily or weekly TTL. Rates change infrequently, but they do change — a cached value from six months ago might be wrong.

Determining the VAT Treatment

With customer data and rates available, the logic for determining VAT treatment looks like this: if the customer is in the same country as the seller, apply domestic VAT rules. If in a different EU country with a valid VAT number, apply the reverse charge. If in a different EU country without a valid VAT number, charge VAT at the customer's country's rate. If in the UK, apply UK VAT rules.

This logic should be encapsulated in a single function that takes customer country, VAT status, and product type, and returns the applicable rate and treatment. Test it thoroughly against each scenario before going live.

What Has to Appear on the Invoice

EU VAT invoices have specific mandatory fields: invoice number, invoice date, seller name and address, seller VAT number, buyer name and address, description of goods/services, unit price, quantity, net amount, VAT rate, VAT amount, and gross amount.

For reverse charge invoices: the buyer's VAT number, and a statement such as "Reverse charge — VAT to be accounted for by the recipient in accordance with Article 196 of Directive 2006/112/EC."

Generating the invoice is the easy part. The hard part is making sure the data going into it is correct. Get the upstream validation and rate logic right, and the invoice almost generates itself.

Invoice Numbering

Invoices need sequential numbering. Use an auto-incrementing integer and format it as needed (INV-2026-0001, etc.). The requirement is that the sequence is unbroken and each number appears only once. Don't delete invoice records; instead, issue credit notes to reverse incorrect invoices.

Credit Notes

When you need to reverse an invoice — due to a refund, an error, or a cancellation — you issue a credit note rather than deleting the original invoice. Credit notes reference the original invoice number, show the reversal amount, and follow the same VAT treatment as the original. Your system needs to handle credit notes as a first-class entity.

Record Retention

VAT records must be retained for specific periods — typically 6 years in the UK, and varying by country across the EU. Your system should store invoice data in a way that makes retrieval by date range and customer straightforward. Alongside the invoice itself, store the VAT validation response and timestamp, and the customer's stated country.

Testing Your VAT Logic

Before going live, test every scenario: domestic B2B, domestic B2C, EU B2B with valid VAT number, EU B2B with invalid VAT number, EU B2C, UK customer, and customer with no country data. Create test invoices for each and verify that the VAT treatment, rates, and invoice content are correct.