vatnode vs VATapp.net – When a Web Form Isn't an API

VATapp.net is a web tool, not an API. According to its public site checked on 11 September 2026, it offers a browser form where a human types a VAT number and reads the result on screen. As a free, no-account utility for a one-off manual lookup it works well – bookmark it, use it, move on. The category it does not belong to is "developer integration": there is no documented REST endpoint, no JSON payload, no authentication model, no webhook for changes over time. If your system has to validate VAT numbers from code, the real comparison is a human workflow against a programmable one, not two products on the same axis.

Last updated: September 2026

Competitor facts on this page checked against the vendor's own public site, documentation and pricing pages on 11 September 2026. Rows marked absent mean we could not find the capability documented publicly, not that the product lacks it.

Web Tool vs Programmable Endpoint

A web tool is a workflow for one person, one screen, one number at a time. It is great for a salesperson verifying a new lead, a finance assistant checking a single invoice or a founder doing diligence on a supplier. It is the wrong shape the moment you need to validate dozens of VAT numbers per day, store the result against an invoice record or run a recurring re-check.

vatnode is the programmable shape of the same primitive. Same upstream sources (VIES plus national registries), but exposed as a REST endpoint that returns a JSON payload with the VIES consultation number, source authority and verifiedAt timestamp already attached.

What One Validation Call Returns

{
  "valid": true,
  "vatId": "FI26364843",
  "countryCode": "FI",
  "countryName": "Finland",
  "companyName": "SUPERCELL OY",
  "companyAddress": "JÄTKÄSAARENLAITURI 2, 00180 HELSINKI",
  "companyRegistrationDate": "2010-05-06",
  "companyForm": "Oy",
  "industryDescription": "Publishing of computer games",
  "registryCode": "2336509",
  "registryCodeName": "Y-tunnus",
  "source": "VIES",
  "checkId": "019d2a8c-5f3a-7d12-a901-bc23de456f78",
  "verifiedAt": "2026-04-16T10:00:00.000Z",
  "consultationNumber": "WAPIAAAAZ27qPadm",
  "countryVat": {
    "vatName": "Arvonlisävero",     // print on Finnish invoices
    "vatAbbr": "ALV",
    "currency": "EUR",
    "standardRate": 25.5,
    "reducedRates": [10, 14],
    "superReducedRate": null,
    "parkingRate": null,
    "vatNumberFormat": "FI + 8 digits",
    "vatNumberPattern": "^FI\d{8}$",
    "countryVatUpdatedAt": "2026-04-16"
  }
}

VATapp.net shows this on screen. vatnode returns it to your application as structured data you can store and branch on.

Feature Comparison

National Registry Integrations

When the VIES node for a country is down, vatnode falls back to that country's national VAT register wherever one is publicly queryable, so the check still answers instead of returning an error. Fallback runs only against registers that expose VAT registration itself: a company register can list an active business that is not VAT-registered, and deriving a verdict from that would be a false positive.

Separately, when VIES answers but carries no company data, vatnode enriches the response from national company registries – registration date, legal form, industry description and the national registry code. Coverage is per country and moves as registers open up; the coverage page lists which fields each country returns.

VATapp.net has no API and no documented equivalent for either. When VIES is down for a number you looked up manually, there is no fallback. vatnode's source field tells you which authority answered – VIES, ARES, ANAF, and so on.

Granular Webhook Events

Register a VAT number and vatnode re-checks it on a schedule, sending a webhook when something changes – so your customer records and invoice settings stay current without a re-check job of your own.

Where the Manual Workflow Breaks at Scale

Manual lookup is fine until volume grows or rules change underneath you – Finland raised its standard rate from 24% to 25.5% in September 2024, and there is no programmatic way for a web form to push that change into your billing system. vatnode pulls the current rate from the European Commission TEDB daily and returns it inside the same response that validates the VAT number, so the data your application reads is the data your application bills against.

Machine-Readable Audit Trail per Call

Every vatnode response includes a checkId (UUID) and a verifiedAt timestamp. Store both next to the invoice record so every invoice links back to the exact validation call – a reference for support and internal lookups, not evidence on its own.

VATapp.net has no API. A human looks at a result on screen – there is no structured output, no persistent record, and no way to attach evidence of a check to a transaction. For a single spot-check that is fine. For a billing system processing hundreds of invoices, it is not a compliance solution.

Set your own EU VAT as requester in dashboard Account details, and qualified checks return the VIES consultationNumber – a reference that comes from VIES itself, something no manual lookup tool can produce. vatnode logs the checkId, verifiedAt moment, and source authority alongside it as supporting internal record, queryable at any time. Retention requirements vary by country, so confirm yours with a tax advisor.