You launched a SaaS product, your first EU customer is ready to pay, and now you're stuck on a deceptively simple question: how to get a VAT no.
Most founders start in the wrong place. They assume selling into Europe means they need to rush into VAT registration, fill out forms in a language they don't speak, and wait weeks for a number they may not even need. That's how small teams end up wasting time on tax admin instead of fixing onboarding, shipping features, or tightening billing.
The practical path is simpler. First decide whether registration is required. Then, if it is, treat VAT registration like an engineering task: define the trigger, prepare the inputs, submit clean data, and build the ongoing workflow around invoicing and validation.
Table of Contents
- Do You Really Need a VAT Number?
- Understanding VAT Registration Thresholds
- The VAT Application Process Explained
- Gathering Documents and Avoiding Costly Mistakes
- You Got a VAT Number What Happens Next
- Automating VAT Checks for Resilient Billing
Do You Really Need a VAT Number?
A lot of founders searching for how to get a VAT no don't need one yet.
If you run a B2B SaaS and sell digital services to EU companies, the first question isn't how to register. It's whether the reverse charge applies. For B2B digital services, the customer is responsible for the VAT. That's the rule that many generic VAT guides blur together with B2C selling and physical goods.
The biggest mistake SaaS founders make
Here's the common failure mode. A US SaaS company sells subscriptions to a French business. The founder hears “EU VAT,” assumes they must register somewhere in Europe, and starts looking at forms in France, Ireland, or Germany.
That can be the wrong move.
For B2B digital services, the reverse charge mechanism generally shifts VAT liability to the customer. Avalara notes that 31% of small SaaS startups incorrectly register for VAT in multiple EU countries due to confusion over this rule in its discussion of EU VAT number registration and reverse charge treatment.
Practical rule: If your customer is an EU business buying your SaaS for business use, your core task is often validating their VAT status correctly, not racing to get your own local VAT number.
That's why understanding the distinction between B2B and B2C matters more than any registration form. It changes your entire compliance strategy.
A simple mental model
Use this split:
| Sale type | Typical VAT treatment | What you need to focus on |
|---|---|---|
| B2B digital SaaS | Often reverse charge applies | Validate the customer's VAT status and invoice correctly |
| B2C digital SaaS or consumer sales | Seller usually handles VAT obligations | Determine whether registration is triggered |
If you sell subscriptions to VAT-registered businesses in Europe, you usually need a reliable way to confirm the buyer is really a business. If you sell to consumers, you're in a different lane. That's where registration thresholds and collection rules start to matter much more.
A useful checkpoint is understanding the concept of a VAT registration threshold. Founders often skip that and jump straight into registration work that doesn't apply to their model.
Selling to Europe doesn't automatically mean you need an EU VAT number. Selling to EU consumers is what usually forces the issue first.
For SaaS founders, that single distinction can save weeks of admin and a lot of avoidable cost.
Understanding VAT Registration Thresholds
A founder launches a €29 per month SaaS, gets a few dozen signups from Germany, France, and Spain, and assumes VAT can wait until finance grows up a bit. That is how teams end up rebuilding checkout logic under time pressure.
For B2C sales into the EU, thresholds decide when VAT stops being a background issue and starts affecting pricing, billing, and reporting.
The key point is straightforward. Once your consumer sales into the EU pass the small cross-border threshold used under the EU e-commerce VAT rules, you cannot keep treating those sales as a simple domestic problem. You need to charge VAT based on the customer's country, and you need a registration path that matches how you sell. The European Commission's overview of VAT on digital services and distance sales is the cleanest reference for that rule set.
What the threshold changes in practice
For SaaS founders, the threshold is less about tax theory and more about system design.
Below it, some businesses still choose to prepare early, especially if EU consumer growth is lumpy and hard to predict. Above it, preparation is over. Your billing flow needs to identify the customer location correctly, apply the right VAT rate, and produce invoices and reports that can survive a tax review.
That matters because EU VAT for consumer sales is destination-based. A French customer and a Finnish customer can create different VAT outcomes from the same product and the same pricing page.
There is also a trap generic guides skip. The threshold discussion often sounds simple, but the registration path can still get expensive depending on your structure. If you need a local registration outside the simpler schemes, some countries may require a fiscal representative for non-EU businesses. That adds ongoing cost, paperwork, and another dependency between your app and getting paid. A country-specific example helps show how quickly local rules matter once you move past the high-level summary. See this guide to VAT registration and compliance in Portugal.
What to track before the threshold becomes a problem
Founders do not need a giant tax team early. They do need clean billing data.
Track these from day one:
- Customer type: Separate businesses from consumers before payment is captured.
- Customer country: Store it consistently across checkout, CRM, and invoicing.
- Taxable B2C revenue: Measure the sales that count toward EU consumer VAT obligations.
- Registration lead time: Leave time for setup before you are forced to charge VAT.
Tax debt can arise from product decisions. If checkout does not collect the right evidence, if invoices are missing required fields, or if the customer record cannot tell B2B from B2C, the fix is rarely an accountant clicking a button later. It becomes an engineering cleanup project.
A practical founder view
Pure B2B SaaS usually stays in the customer-validation lane longer.
B2C SaaS hits threshold and registration questions much faster. That is why the first question is not “how do I get a VAT number?” It is “do I already have consumer sales that make one necessary, and what will that choice cost me operationally?”
The VAT Application Process Explained
A typical founder scenario looks like this. Stripe is live, the first EU invoices are out, and then someone asks for your VAT number. At that point, speed matters, but filing in the wrong country or with the wrong setup creates more work than waiting a few extra days to do it properly.
The process itself is usually straightforward. The hard part is choosing the correct registration path for your business model. For SaaS, that often means answering a question generic guides skip. Are you registering because you have a real local obligation, or because a customer, marketplace, bank, or internal finance process asked for a VAT number before anyone checked whether you need one?
Pick the country based on obligation, not convenience
The right country is the one that has the legal reason to register you.
For founders selling digital services, that reason usually comes from local taxable activity, consumer sales that trigger registration, stock held in a country, or a specific scheme such as OSS. For pure B2B SaaS, the answer is often less obvious than people expect. A business customer asking for a VAT ID does not automatically mean you need domestic registration there.
This is also where hidden costs show up. Some countries require non-EU businesses to appoint a fiscal representative, and that can turn a simple registration into an ongoing vendor relationship with recurring fees. If you want a concrete example of how local process details change the decision, review this walkthrough on VAT registration and compliance in Portugal.
No marketplace, invoicing tool, or service provider can issue the number for you. The tax authority in the relevant country does that.
What the application usually asks for
The forms differ by country, but the pattern is familiar. Expect to provide your legal entity details, registration number, registered address, business activity, start date for taxable sales, and an explanation of why you need the VAT number.
For SaaS, the business description matters more than founders think. “Software company” is weak. “Subscription-based cloud software sold to business customers in the EU” gives a reviewer enough context to place you in the right box.
Supporting documents usually include:
- Company proof: A recent certificate of incorporation or company extract
- Responsible person ID: Passport or national ID that matches the applicant details
- Address proof: Documentation supporting the registered office or business address
- Business activity summary: A plain-language description of what you sell and who buys it
- Tax registration context: Evidence or explanation showing why registration is required
The common failure mode is not tax law. It is inconsistency. If the company name is abbreviated on one document, the address differs across files, or the activity description reads like startup pitch copy, the application often gets pushed into manual review.
After approval, the tax authority issues the VAT identification number. It will usually include the country prefix.
Here's a short explainer before the next step:
What the timeline looks like
Processing time varies a lot by country and by how clean the submission is. Some registrations move quickly. Others stall because a document is outdated, a translation is missing, or the application was sent through the wrong portal.
Tax offices optimise for certainty.
That is why the fastest path is usually boring. Submit the right form, in the right country, with documents that match each other exactly, and with a business description that makes sense to someone outside SaaS. Chasing support inboxes rarely fixes a weak application. A clean first submission usually does.
Gathering Documents and Avoiding Costly Mistakes
Most VAT registration pain isn't caused by tax complexity. It's caused by preventable document mistakes.
The teams that get through this cleanly treat the application like a compliance package, not a web form. If one document is outdated, missing, badly translated, or inconsistent with the rest, the whole process slows down.
The documents that usually matter
At minimum, expect to collect the basics before you start:
- Current company extract: Use a recent registration record, not an old PDF pulled from your drive.
- Founder or director ID: Make sure the identity document matches the named applicant exactly.
- Proof of address: Use a document that clearly ties the company or responsible person to the stated address.
- Business description: Write this in plain language. “Cloud software subscription for business customers” is more useful than startup jargon.
- Turnover expectation: Keep your figures internally consistent across forms and attachments.
That sounds simple, but small mismatches create big delays. A different company name format across documents, an old address, or unclear activity descriptions can all trigger manual review.
The mistakes that stall applications
France is a good example of how minor details become real blockers. Eurofiscalis notes that when non-French documents are submitted without official French translations where required, around 30% of foreign applications stall, and first-time approval exceeds 70% only when documentation is fully compliant in its guide to VAT registration in France.
That's not a France-only lesson. It's the general pattern across jurisdictions. Tax offices aren't trying to decode startup shorthand.
A few recurring mistakes show up often:
- Missing translations: If a country requires local-language documents, machine translation won't save you.
- Stale records: Some authorities expect recently dated company extracts.
- Incomplete representative details: If a local representative or other contact is required, partial data can stop the file cold.
- Inconsistent business story: If your website says one thing and the application describes another, someone may ask questions.
Clean paperwork beats clever paperwork. Tax offices want consistency they can verify.
The fiscal representative trap
This is the hidden cost that generic guides often bury in a footnote.
For non-EU companies, some countries such as Italy and Spain may require a fiscal representative. That cost can range from €500 to €2,000 per month, and a LinkedIn compliance guide reports that 22% of non-EU e-commerce startups failed due to unanticipated fiscal representative fees in its discussion of international VAT registration and compliance success.
If you're a lean founder, that changes the economics fast. A registration path that looks manageable on paper can become expensive before you've processed much revenue.
That's why “how to get a VAT no” shouldn't be treated like a paperwork-only question. It's a business model question too.
A sensible founder asks:
| Question | Why it matters |
|---|---|
| Do I actually need local registration? | You may not if your sales are reverse-charge B2B SaaS |
| Is a fiscal representative mandatory? | It can materially change cost |
| Are translations required? | Missing them can stall the process |
| Can I support ongoing filing and invoicing? | Registration creates recurring operational work |
Teams that ask those questions early avoid the expensive version of “just register everywhere and sort it out later.”
You Got a VAT Number What Happens Next
Getting approved isn't the finish line. It's the start of recurring obligations.
Once you have a VAT number, you need to keep your invoicing, returns, and customer records aligned with that registration. That's where many founders discover VAT isn't a one-time admin task. It becomes part of the billing system.
Registration creates an ongoing workflow
At a minimum, expect three ongoing responsibilities.
- File VAT returns: Registration usually means periodic reporting to the relevant authority.
- Issue compliant invoices: Where an invoice is required, the supplier's VAT identification number must be shown, except where simplified invoice rules apply.
- Keep customer treatment accurate: If a customer is a business, your records need to support that treatment.
This matters even for technical teams that want finance to “handle tax later.” Billing logic creates the source data. If checkout, CRM, Stripe metadata, and invoice generation disagree, the compliance problem starts upstream.
Why customer VAT validation matters
For B2B sales, customer VAT validation isn't a nice-to-have. It's the evidence layer behind correct tax treatment.
The official EU tool is VIES, but it's important to understand what it is. VAT numbers are issued by national tax administrations, and VIES is a search engine querying national databases, not a single central database. Public access is also limited in many cases because governments restrict what data is exposed.
This screenshot shows the kind of validation workflow developers usually want to support in production systems:
That limitation has practical consequences. You might confirm that a VAT number is allocated, but still get limited company details depending on the country and data protection rules.
Manual validation works for occasional invoices. It doesn't scale well when VAT checks sit inside checkout flows, subscription upgrades, or marketplace onboarding.
If your product lets users self-serve, enter a VAT number in Stripe-powered checkout, or generate invoices automatically, validation becomes an operational dependency rather than a back-office task.
Automating VAT Checks for Resilient Billing
If you only validate a VAT number once in a while, the manual route can be good enough.
If VAT checks sit inside billing logic, signup, invoice generation, supplier onboarding, or marketplace seller verification, manual checks break down quickly. Developers usually discover this when they try to wire VIES into an app and realize they're dealing with old protocols, inconsistent responses, and fragile availability.
Why building your own wrapper usually isn't worth it
On paper, building a small internal wrapper sounds easy. In practice, it turns into maintenance work that never becomes a core advantage.
You need to handle format validation, remote service failures, retries, timeouts, odd edge cases by country, and the mismatch between what your app expects and what the upstream service returns. Then you need to expose errors in a way your billing code can use.
The hidden cost isn't only engineering time. It's reliability risk. When a checkout depends on VAT validation, bad error handling can block legitimate customers or apply the wrong tax treatment.
A better pattern is to keep the integration boring:
- Validate early: Check format before the customer reaches the final billing step.
- Store the result: Keep validation status with the customer record and invoice context.
- Use machine-readable outcomes: Your app needs structured statuses, not brittle text parsing.
- Design for upstream instability: Assume external validation services won't behave like your internal API.
For developers working through this problem, this guide to VAT number lookup workflows is a good reference point for the shape of a production-ready validation flow.
What a resilient setup looks like
A strong implementation usually has a few traits in common.
First, VAT validation is part of the billing architecture, not a support task someone runs manually later. Second, the system distinguishes format errors from unavailable services. Third, the result is reusable across invoicing and tax determination instead of being trapped in one request path.
That matters for small teams. You probably don't want a founder or backend engineer debugging tax validation edge cases during a renewal failure or end-of-month invoice run.
The cleanest path is to treat VAT validation the way you treat payment confirmation or fraud checks. Put it behind a stable interface, persist the result you need, and make sure failure states are understandable to both code and humans.
If your app sells to EU businesses, that's often the main reason behind the search query “how to get a VAT no.” Sometimes you need registration. Often you need a dependable system for knowing when you don't, and for proving why.
If you need a developer-friendly way to validate EU VAT numbers without building and maintaining your own VIES wrapper, TaxID gives you a single REST API for VAT and company ID checks across 31 countries. It returns validation status, company name, and address in clean JSON, with country-specific format checks, caching, and predictable error handling that fits real billing systems.