The EU VIES (VAT Information Exchange System) is the backbone of cross-border B2B trade. However, like any distributed public infrastructure, it isn't immune to outages. Under Article 138 of the EU VAT Directive (2006/112/EC), applying a 0% VAT rate on intra-community sales requires proof of the buyer's active VAT registration at the time of supply. When VIES or national member-state nodes (such as the German/Austrian Finanzamt, Dutch Belastingdienst, Polish Urząd Skarbowy, French DGFiP, Spanish AEAT, or Italian Agenzia delle Entrate) go down, merchants face a critical dilemma: block legitimate checkout or risk losing zero-rate exemption in a tax audit.

For a business operating under modern EU tax scrutiny and approaching ViDA, "the EU server was down" is not an acceptable defense unless backed by immutable due diligence (Vertrauensschutz). Here is how to navigate VIES downtime while keeping sales moving and audit trails bulletproof.
1 Why VIES Goes Down (And Why It's Not One System)
VIES is a "gateway" rather than a single database. When you validate a VAT number, the request travels from the EU Commission's portal to the national tax database of the Member State in question.
If Italy or Germany is updating their local tax servers, VIES cannot verify numbers from those countries.
During peak filing seasons, response times can slow down significantly.
If a national server doesn't respond within a few seconds, VIES returns an "Unavailable" or MS_UNAVAILABLE error.
Do not let a temporary VIES fault interrupt a sound VAT workflow. Under Article 138 of the EU VAT Directive (2006/112/EC), applying 0% VAT on cross-border B2B supplies strictly requires proof of active taxable status at the time of supply. If VIES is temporarily unavailable, VIESAC’s proprietary resilience layer (SmartRouter™, SmartCache™, monitored local registry connections, and AI-assisted quality controls) protects your legal due diligence defense for tax audits (Finanzamt, Belastingdienst, Urząd Skarbowy, DGFiP, etc.). The live official VIES response remains decisive: while it is delayed, VIESAC records the downtime context, manages controlled queues, and automatically fetches the official consultation certificate the moment the Member State service recovers.
2 VIES Error Codes & Fault Troubleshooting (SOAP API)
Because VIES is a real-time gateway to 27 national systems, the errors you receive (often referred to as SOAP Fault Codes) follow specific patterns. Understanding these is critical for ViDA compliance, where a technical glitch can block your real-time digital reporting (DRR). Here is how VIESAC provides technical resilience against these faults.
| Error Code (SOAP) & Pattern | Technical Analysis & VIESAC Solution |
|---|---|
INVALID_INPUT (201) Malformed VAT number or request input | Input needs correction: remove invalid characters, spacing or a malformed country prefix, then retry. VIESAC can normalize ordinary formatting noise before the live call; it never changes or assumes the official result. |
INVALID_REQUESTER_INFO (202) Requester VAT details cannot be confirmed | Review the requester details: correct the VAT number supplied for the requester and send a fresh request. This fault concerns the requester data, not the validity of the VAT number being checked. |
SERVICE_UNAVAILABLE (300) Central VIES service is temporarily unavailable | Central service interruption: record the failed attempt and retry with controlled backoff. An unavailable service is a technical state, never evidence that the target VAT number is invalid. |
MS_UNAVAILABLE (301) Member State service is under maintenance or unavailable | Official national source is temporarily unavailable: preserve the timestamp and audit context, then recheck through VIES after the Member State service recovers. Do not convert this into an invalid result. |
TIMEOUT (302) Official endpoint did not respond within the response window | Response window exceeded: keep the check pending and place it in a controlled retry queue. A timeout is distinct from an invalid VAT number and from VIES concurrency-limit faults. |
VAT_BLOCKED (400) Official VAT status is blocked | Official restriction: retain the live fault in the audit trail and resolve it through the appropriate business or tax process. It must not be turned into a fallback approval. |
IP_BLOCKED (401) VIES usage-protection control has been triggered | Request protection applies: reduce request pressure, queue the check and retry responsibly. This protects the public service and is not a decision about the target VAT number. |
GLOBAL_MAX_CONCURRENT_REQ (500) Global maximum number of concurrent VIES requests reached | Global request-count limit: VIES has reached its simultaneous-request ceiling. VIESAC uses controlled pacing and queues the request for a later fresh official response. |
GLOBAL_MAX_CONCURRENT_REQ_TIME (501) Global concurrent-request time limit reached | Global time-based concurrency limit: pause with controlled backoff before retrying. This is a capacity signal, not the same fault as TIMEOUT (302) and not a VAT-status result. |
MS_MAX_CONCURRENT_REQ (600) Member State maximum number of concurrent requests reached | Member State request-count limit: the national VIES route has reached its simultaneous-request ceiling. Preserve the attempt and retry the official route when capacity returns. |
MS_MAX_CONCURRENT_REQ_TIME (601) Member State concurrent-request time limit reached | Member State time-based concurrency limit: apply controlled backoff and recheck through the official route. It is a capacity condition, not TIMEOUT (302) or an invalid VAT number. |
3 The Golden Rule: "Unavailable" ≠ "Invalid" & Vertrauensschutz
One of the costliest mistakes businesses make is treating a technical timeout or HTTP 500 error as an invalid VAT number and unfairly charging domestic VAT to an exempt B2B customer—or conversely, granting a 0% exemption without any logging.
Statutory Due Diligence: European tax jurisprudence (and national provisions such as § 6a UStG / § 17a-c UStDV in Germany) protects honest businesses under the doctrine of Vertrauensschutz (protection of legitimate expectations) if and only if you can prove that you exercised due commercial diligence, documented the outage attempt with exact timestamps, and obtained the official VIES consultation certificate as soon as the service was restored.
4 Practical Handling: A 3-Step Strategy with SmartRouter™ & SmartCache™
Follow these steps to protect both sales conversion and Article 138 audit compliance when VIES is down:
- 1. Document Every Attempt with Cryptographic Timestamps — In the eyes of tax inspectors from the Finanzamt, Belastingdienst, or Urząd Skarbowy, an unrecorded attempt does not exist. VIESAC SmartRouter™ immediately logs the timestamp, the input VAT, and the exact SOAP fault code (e.g.
301 MS_UNAVAILABLEor302 TIMEOUT) into your permanent audit log. - 2. Leverage SmartCache™ & Asynchronous Consultation Recovery — Don't block checkout. If the partner was previously verified, SmartCache™ confirms the baseline validity while scheduling an automatic background recheck. Once the national tax database recovers, VIESAC automatically captures the official VIES consultation number and seals the audit certificate with SHA-256 integrity.
- 3. Communicate with Transparent Customer Notices — Inform your customer transparently: "EU VIES registry is undergoing temporary maintenance. Your VAT has been recorded and will be certified automatically once the national tax node responds." This builds buyer confidence and prevents cart abandonment.
5Frequently Asked Questions: VIES Outages & Fault Codes
Does MS_UNAVAILABLE (301) or SERVICE_UNAVAILABLE (300) mean the VAT number is invalid?
No. MS_UNAVAILABLE (301) means a national Member State tax server is undergoing maintenance or is temporarily unreachable, while SERVICE_UNAVAILABLE (300) affects the central EU VIES gateway. Never treat a technical fault as an invalid VAT status; check live node health on viesac.eu/countries and queue an automatic recheck.
What is the difference between TIMEOUT (302) and GLOBAL_MAX_CONCURRENT_REQ_TIME (501)?
TIMEOUT (302) means the upstream endpoint did not answer within the response window. GLOBAL_MAX_CONCURRENT_REQ_TIME (501) and MS_MAX_CONCURRENT_REQ (600) mean VIES reached its concurrency limit and require paced retries with SmartCache™ rather than tight retry loops that trigger IP_BLOCKED (401).
Can we still apply 0% intra-EU VAT when VIES is down?
Yes, provided you document commercial due diligence (Vertrauensschutz under Article 138 of the EU VAT Directive). Record the outage timestamp and SOAP fault code, rely on VIESAC’s 25+ national fallback paths where supported, and retrieve the official VIES consultation number automatically as soon as the national server recovers.
How does VIESAC handle German (DE) VIES outages or missing company names?
When the German VIES node returns MS_UNAVAILABLE or omits name and address fields, SmartRouter™ uses VIESAC’s direct channel to Germany’s Federal Central Tax Office (BZSt) plus corroborating verification layers with clear provenance while queuing official VIES recovery.
How can we prove to tax auditors that outage logs and recovered certificates were not altered?
Every saved record includes a canonical SHA-256 snapshot, independent RFC 3161 trusted timestamps (DigiCert EU), raw XML evidence, and 10+ year EU archive retention. Anyone can independently confirm integrity on viesac.eu/verify.
How VIESAC Automates the Downtime Headache
Managing manual retries and logs is a developer's nightmare. VIESAC was designed to handle the instability of government servers so you don't have to.
- →Automatic Retries & Queuing: If VIES is down, our system automatically queues the request and retries until it's completed.
- →Clear Status Reporting: We distinguish between an "Invalid" number and a "Service Down" status, so your workflow can continue uninterrupted.
- →The Ultimate Audit Trail: VIESAC stores a permanent digital certificate for every check—including those that required multiple attempts—ensuring you are 100% ready for a ViDA audit.
Pro Tip
Don't let a server glitch in another country stop your business growth. Use an EU VAT validation API with retry logic or our WooCommerce plugin so checkout never blocks and your audit trail stays complete. See also how to validate EU VAT for audit.