EU VAT, actually operable.
Calculate, store, and report on EU VAT from a single API surface — official rates, merchant-friendly tax classes, historical lookups, source profiles, and an audit-grade evidence trail. No spreadsheets, no plugin sprawl.
Live rate atlas
EU-27
States
27
Classes
37
Rates
999
— How it works
From official source to filed return.
01
Pull official rates
TEDB SOAP imports run on a schedule. Standard, reduced, super-reduced, parking, and zero rates land in one normalised table with validity windows.
02
Map to merchant classes
The 88 official categories collapse into 37 merchant-friendly tax classes — books, pharma, accommodation, energy, repairs, transport, and more.
03
Calculate at supply date
POST /v1/vat/calculate resolves the right rate for a country, class, and supply date. Minor units in, exact gross/net/VAT out — every time.
04
Persist evidence for OSS/IOSS
The result becomes a transaction record. Source profiles, thresholds, quarter previews and accountant exports all read from the same audit-friendly model.
— Why VAT Engine
Built for EU VAT depth,
not generic tax lookup.
Most tax APIs stop at country rates. VAT Engine is designed around the evidence, dates, sources, and reporting states a merchant actually needs after the sale.
TEDB without the chaos.
Official source of truth, exposed as merchant-friendly tax classes — books, food, pharma, accommodation, energy, repairs, transport.
Raw input
88
TEDB categories
Merchant output
37
usable classes
Time-aware by transaction date
Validity windows mean refunds, audits, and backfills resolve to the rate that applied on the supply date.
SME thresholds for all 27
TEDB SME service data with EUR + national-currency context, including non-eurozone members.
One audit-friendly compliance flow
Transactions, source profiles, OSS thresholds, Union OSS previews, and accountant exports — designed as a single model.
Connector foundation first
PlannedEncrypted tokens, webhook inboxes, idempotent jobs, source aliases, and review queues — before Shopify, WooCommerce, Magento, or Sylius.
Security baked in, not bolted on.
Scoped API keys · 2FA & backup codes · CSRF protection · activity logs · rate limiting · hardened backend controls.
27 states
Standard and reduced rates across every EU member state.
37 classes
Merchant-facing classes mapped from official TEDB categories.
999 rates
Country by tax-class rows with validity windows.
Time aware
Past, present, and future lookup support for audit trails.
— Core workflows
One API, checkout to filing.
Developers get straightforward endpoints. Finance gets records that stay usable for audits, accountant exports, and compliance monitoring.
Calculate VAT
Return gross, net, VAT amount, rate, and tax class context from one REST call.
Resolve rates
Query current or historical rates by country, date, and curated tax class.
Track transactions
Keep immutable VAT calculation records ready for exports and compliance views.
Manage sources
Normalize stores, marketplaces, channels, and raw tags into source profiles.
Account & API key ops are part of the product.
Generation, rotation, revocation, scoped permissions, usage tracking, 2FA, backup codes, CSRF protection, activity logs, and hardened request handling — all in the dashboard.
Scoped API keys
2FA & recovery
Usage visibility
Connector-ready commerce data.
Shared integration infrastructure first, so external orders import, review, and report consistently — before platform-specific sync.
— Build with it
Ship VAT in a day, not a quarter.
Authenticate, calculate, persist. Add rate lookups, source profiles, and reporting as your workflow matures.
— Evaluation notes
Questions buyers and developers always ask.
Why not just store one VAT rate per country?
EU VAT depends on product type, country, date, exemptions, and reporting context. VAT Engine models tax classes, validity windows, source profiles, and transaction history so the calculation result can feed reporting later.
What is different from generic tax API products?
The product is focused on EU VAT depth: official TEDB imports, curated merchant-facing classes, SME thresholds, OSS/IOSS reporting primitives, and historical rate resolution for compliance workflows.
Can this support e-commerce integrations later?
Yes. Source profiles and filing-grade supply events are already part of the foundation. The roadmap adds shared connector infrastructure before platform-specific sync for Shopify, WooCommerce, Magento, Sylius, and headless stores.