LookupTax vs. Vertex (Taxamo): The Database Check Reality
LookupTax covers 100+ countries. Vertex covers ~50. But the real difference isn't just quantity—it's whether 'supported' means database-validated or just format-checked.
LookupTax supports 100+ countries. Vertex (formerly Taxamo) supports around 50 countries. That's already a major difference—but the real gap is hidden beneath the word "supported."
But in fraud prevention, the word "Supported" is often a marketing trap.
You need to know: Is the tool checking the live government registry, or is it just checking if the number has the right amount of digits?
Using the official developer documentation from both providers, we found a significant "Validation Gap" in high-growth markets.
1. The "Syntax" vs. "Database" Trap
❌ Syntax Validation (Weak)
The tool checks if the ID looks right (e.g., "Starts with 'SA' and has 15 digits"). It passes valid-looking fake numbers.
✅ Database Validation (Strong)
The tool connects directly to the government's live registry to confirm the business is active.
Vertex (Taxamo) defaults to "Syntax" checks for many difficult regions to save on engineering overhead. LookupTax builds direct government connections.
2. The Verification Gap: 4 Key Markets
According to the latest documentation, here are four major economies where LookupTax verifies the real entity, while Vertex only checks the format.
Saudi Arabia (KSA)
Vertex: ⚠️ Syntax Only
(Source: Vertex Docs, Note 3)
LookupTax: ✅ Database Check
Connects to CRN database to verify the CRN is active.
Singapore
Vertex: ⚠️ Syntax Only
LookupTax: ✅ Database Check
Verifies GST/UEN status directly with IRAS.
Taiwan
Vertex: ⚠️ Syntax Only
LookupTax: ✅ Database Check
Validates the Unified Business Number (UBN).
Colombia
Vertex: ⚠️ Syntax Only
LookupTax: ✅ Database Check
Verifies the NIT (Número de Identificación Tributaria).
Why this matters: If you sell digital goods (SaaS) to a B2B customer in Saudi Arabia or Singapore, a "Syntax" check will let a fraudster use a made-up ID to evade 15-20% tax. Only a Database check stops them.
3. Transparency: The "Checkmark" Test
One subtle but important difference is how the companies treat this data.
LookupTax is explicitly transparent. Their coverage page has a column for "DB Validation" and a separate column for "Syntax Validation." You know exactly what you are paying for before you make the API call.
Vertex buries these limitations in the "Notes" section of their developer appendix. Their sales material often lists these countries simply as "Supported," leaving you to discover the limitation only after you sign the contract.
Comparison Cheat Sheet: The "Database" Advantage
| Country | LookupTax | Vertex (Taxamo) |
|---|---|---|
| Saudi Arabia | ✅ Live Database | ⚠️ Syntax Only |
| Singapore | ✅ Live Database | ⚠️ Syntax Only |
| Taiwan | ✅ Live Database | ⚠️ Syntax Only |
| Colombia | ✅ Live Database | ⚠️ Syntax Only |
| Hong Kong | ✅ Live Database | ❓ Unlisted/Syntax |
| Australia | ✅ Live Database | ⚠️ ABN Only (by default) |
| EU (VIES) | ✅ Live Database | ✅ Live Database |
The Verdict
Stick with Vertex (Taxamo) if:
You primarily sell to the US, Canada, and EU. Their coverage in these "Core West" regions is excellent, and they offer liability insurance that LookupTax does not.
Switch to LookupTax if:
You are expanding into Asia, LATAM, or MENA. If you have customers in Singapore, Riyadh, or Taipei, you cannot rely on a 1990s-style format check. You need a modern tool that pings the government to confirm your customer actually exists.
Get Started Free →Ready for Real Database Validation?
Stop accepting syntax-only checks. Validate against live government registries in 100+ countries.