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 as of 2026-05, 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 SLA, no webhook for changes over time. If the system you are building has to validate VAT numbers from code, the comparison is really between a human workflow and a programmable one. This page makes that distinction explicit instead of pretending the two products compete on the same axis.

Last updated: May 2026

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 you this information on screen. vatnode gives it to your application as structured data — ready to store, validate against, and act on programmatically.

Feature Comparison

National registry integrations

When VIES is unavailable or returns no company data, vatnode automatically queries the national business registry. These countries are currently covered:

VATapp.net has no API. 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, BZST, PRH, SIREN, and so on.

Granular webhook events

Subscribe to any VAT number and get notified the moment something changes — so your customer records and invoice settings stay accurate without manual re-checking.

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. These fields are designed to be stored alongside your invoice records — giving you a documented audit trail that links every invoice to the exact validation event that authorised it.

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.

Tax authorities across the EU increasingly expect documented validation at the point of transaction — not retroactive checking. vatnode gives your application a machine-readable record for every check: a unique checkId, the exact verifiedAt moment, and the source authority that answered — stored automatically, queryable at any time.