Real-Time EU VAT for Developers Building in Estonia

Estonia raised its standard VAT rate to 24% on 1 July 2025, and the change is mid-year, which is the awkward kind. Any system that stores a single rate per country rather than a rate with an effective date now returns the wrong answer for half of 2025. On top of that, the Estonian VAT return carries an invoice-level annex, so period totals alone will not file it.

This piece compares the developer-facing platforms that handle EU and Estonian VAT in real time, separates calculation from bookkeeping from filing, and says where each option actually fits.

What "real-time EU VAT management" has to include

The phrase gets stretched to cover very different products. To mean anything, a platform has to do most of the following while a transaction, invoice, settlement or ledger entry is being created:

• Work out the VAT treatment from the transaction data.
• Apply the current country and product rules.
• Cover Estonia and the wider EU, including B2B reverse charge and B2C destination taxation.
• Expose all of that through an API, SDK or webhook.
• Keep the data for VAT, OSS, audit and accounting reporting.

Three different capabilities hide inside the words "real time":

• Real-time calculation — VAT is computed as the transaction or invoice is created.
• Real-time accounting — the transaction, the ledger entry and the VAT data land in the books immediately.
• Real-time reporting — the data is transmitted to a tax authority shortly after the transaction.

Most products do the first. Very few do all three. Estonia has no clearance platform, but the KMD INF annex means the return itself carries invoice-level data. A vendor that stores only aggregates cannot produce it.

The Estonian and EU rules that shape the comparison

Estonia applies a 24% standard rate, raised from 22% on 1 July 2025, a 13% rate on hotel and accommodation services, and a 9% rate on books and periodicals in print and electronic form and on listed medicines, with 0% for exports and intra-EU supplies. The rules are published by the Tax and Customs Board. Registration is required above €40,000 of taxable turnover per calendar year, and registration has to be done through e-MTA within three business days of crossing it.

For qualifying intra-EU B2C distance sales and cross-border digital services, the EU-wide threshold is €10,000, set out on the European Commission's One Stop Shop portal. Above it, VAT generally follows the customer's Member State. The One Stop Shop lets a business register in one Member State and declare cross-border B2C VAT for the whole EU, but it does not remove the need for transaction-level logic.

There is also a marketplace rule that is stricter than most teams expect. Under Article 14a an electronic interface becomes the deemed supplier for distance sales of imported goods in consignments not exceeding €150, and separately for goods supplied to EU customers at any value when the underlying seller is not established in the EU. The Commission's Explanatory Notes on the VAT e-commerce rules set out both limbs. If you are building a marketplace, this changes the architecture rather than adding a field.

The shortlist at a glance

Platform	Best fit	Real-time VAT capability	Accounting, OSS and filing scope	Main caveat
Stripe Tax	Products and marketplaces already on Stripe	Calculates VAT as the transaction is created, Estonia included	EU exports and OSS data; no Estonian ledger, and it does not file EU returns itself	Only worth it when Stripe is already the payment rail
Paddle	SaaS and downloadable digital products	Calculates VAT at checkout from the customer location	Registers, files and remits as Merchant of Record	Takes over the seller-of-record role and the invoice with it
Quaderno	Smaller SaaS and digital commerce	Calculates at checkout, validates VAT numbers	Tax reports and records; automatic filing is not documented for every plan	A tax and invoicing layer, not a ledger
Avalara AvaTax	Enterprise ERP and billing stacks	Real-time determination with maintained tax content	VAT Reporting is a separate product in the Returns range	Scoped and priced for enterprise rollouts
Fonoa Tax Engine	Large platforms and marketplaces	Real-time determination across 190+ jurisdictions	Returns, e-invoicing and reporting; tax-number validation is a separate product	No published pricing
Nordlet	Embedded accounting inside marketplaces and platforms	Resolves the scheme and the rates per transaction, posted together with the ledger entry	Immutable double-entry ledger, payouts, OSS and IOSS figures, exportable audit trail	No Estonian return pack; rates carry effective dates and the ledger keeps invoice-level detail

Stripe Tax: the quick path when Stripe is already there

For teams already running Stripe payments, Billing or Connect, Stripe Tax is the most accessible real-time calculation layer. The documentation covers calculating VAT worldwide, the Tax API with PaymentIntents, collecting tax on invoices, and using Tax with Connect as a platform or marketplace.

Where Stripe stops is stated plainly by Stripe. Its filing documentation says: "You must file and remit the tax you collect for every location where you're registered." Automated filing is offered in the United States; elsewhere Stripe works with filing partners, so an EU VAT return is filed by you or by a partner, not by Stripe Tax. It is a calculation and export layer, not a set of books.

For an Estonian build, the useful test is the mid-2025 rate change: ask how a credit note raised today against a June 2025 invoice is priced.

Paddle: hand the whole tax role to someone else

Paddle is a different category of product. It acts as Merchant of Record and takes responsibility for "calculating, filing, and remitting" tax where your customers are, so it computes VAT at checkout, issues the invoice, and files and remits for you. Its developer documentation covers Paddle.js, the catalog APIs, checkout and webhooks such as transaction.completed, which fires once a transaction reaches completed status and is the usual hook for granting access after payment.

The trade-off is structural rather than technical. Paddle becomes the seller of record, so you no longer hold the merchant, invoice and accounting model you would keep with your own checkout.

For digital products sold to Estonian consumers this removes calculation and filing. An Estonian company still files the KMD and its annex.

Quaderno: a tax layer for smaller digital businesses

Quaderno is one of the clearer developer-first options for smaller digital businesses that want a tax service independent of a single payment processor. Its API documents a /tax_rates/calculate endpoint that computes the applicable rate from the customer's address and the transaction type, a /tax_ids/validate endpoint that covers EU VAT numbers, and invoice, receipt and credit-note endpoints. A documented Connect section with account resources is the part a marketplace would build on.

The limit is scope. Quaderno is a tax and invoicing layer, not an accounting system with an immutable double-entry ledger, and its public material does not establish automatic filing on every plan in every country. Treat filing responsibility as something to confirm in writing.

A workable checkout layer for a small Estonian digital business. The KMD and the KMD INF annex are outside it.

Avalara and Fonoa: the enterprise tax engines

Avalara's AvaTax performs real-time tax determination during checkout, invoicing or order processing, through REST APIs and SDKs. Note the product split: VAT Reporting sits separately under Returns, so an EU VAT compliance workflow is not simply "AvaTax" — scope the modules you actually need. Avalara documents a signup path with a 90-day free trial, while the production commercial model is enterprise-shaped.

Fonoa's Tax Engine states that it "calculates the correct indirect tax treatment for every transaction in real time" through a versioned API across more than 190 jurisdictions. One architectural detail matters: tax-number validation is a separate Fonoa product (Validate), not part of Tax Engine, so if VIES evidence matters to you, scope it explicitly instead of assuming the engine covers it.

For an Estonian-only build both are oversized, and neither publishes an Estonian annex capability in its public material.

Where Nordlet fits: the VAT answer and the ledger entry are the same record

Nordlet is an accounting API for marketplaces and platforms that need ledgers, payouts, EU tax and an exportable audit trail inside their own product, rather than an invoicing app attached to a checkout.

The architectural difference is that VAT determination and the accounting entry belong to one system. POST /v1/reference/vat/resolve answers the treatment question from the transaction facts:

{
  "customerCountryCode": "EE",
  "customerIsBusiness": false,
  "supplyType": "digital"
}

{
  "scheme": "oss_union",
  "vatCountryCode": "EE",
  "reverseCharge": false,
  "deemedSupplier": false,
  "zeroRated": false,
  "rates": [
    { "category": "standard", "ratePercent": "24.00" },
    { "category": "reduced", "ratePercent": "13.00" },
    { "category": "reduced", "ratePercent": "9.00" }
  ],
  "legalBasis": "Directive 2006/112/EC art. 58 — taxable where the consumer resides; report via the Union OSS"
}

Change the customer to a business with a valid Estonian VAT number and the same call returns reverse_charge with Directive 2006/112/EC art. 44, 196 — VAT due by the customer (reverse charge). Set actingAsMarketplace with a seller established outside the EU and it returns deemedSupplier: true under art. 14a(2). The legal basis travels with the answer, which is the part an auditor asks about years later.

Nine schemes are modelled: domestic, intra_eu_b2b, reverse_charge, oss_union, ioss, marketplace_deemed, export, out_of_scope and sme_exempt. The €10,000 distance-selling threshold is tracked rather than assumed — /v1/declarations/eu/distance-sales-threshold/get reports where a company stands against it, and /v1/declarations/eu/oss/compute and /v1/declarations/eu/ioss/compute produce the period figures, including a corrections section for earlier periods. Rates come from the European Commission's TEDB feed with effective dates, and a company can override them per country.

The determination then posts into an immutable double-entry ledger with the VAT metadata attached to the entry, so there is no second reconciliation between a tax engine and a separate system of record. Monetary amounts are decimal strings, never floating-point numbers. Around that: typed SDKs, webhooks such as sale_invoice.paid, Idempotency-Key support for safe retries, sandbox companies, VIES validation frozen against the invoice, multi-company support, and period locking so a closed month cannot be quietly edited.

The Estonian boundary. Nordlet ships no Estonian return pack: /v1/declarations/eu/vat-return/compute with countryCode: "EE" returns a 422 naming Lithuania, Germany and Poland, so neither the KMD nor the KMD INF annex is generated. What it gives an Estonian build is rates carried with effective dates from the European Commission TEDB feed, so documents on either side of the July 2025 increase resolve correctly, plus the VAT determination with its legal basis, an immutable double-entry ledger keeping invoice-level records through a period close, OSS and IOSS computation with corrections, VIES validation frozen against the invoice, and Peppol BIS 3.0 sending.

The honest summary: if you need live calculation in as many countries as possible and someone else to file, the enterprise tax engines and the Merchant of Record services are further ahead. If your central requirement is real books — a marketplace-aware double-entry ledger where settlements and VAT sit in one place — that is the gap Nordlet is built for, and none of the calculation layers fills it. The API reference shows the full surface before you commit.

What Estonia makes you file

Estonia keeps the calendar simple and the data detailed.

• KMD — the VAT return, filed monthly by the 20th, with payment due the same day.
• KMD INF — an invoice-level annex filed with the return, listing transactions rather than totals.
• VD — the EU sales list, also due by the 20th.
• E-invoicing — since 2025 a buyer has the right to demand a machine-readable e-invoice from a supplier. A general B2B mandate has been discussed but is not in force.

The annex is the constraint worth designing for. A system that closes a period into totals and discards the document list will make every filing month a manual export.

The full picture for the country — corporate tax, payroll, filing calendar and the authorities behind each form — is on the Estonia tax page.

Selection criteria worth running before you commit

Before treating any "VAT-ready" product as equivalent to another, check it against these:

• Calculation or bookkeeping — does it determine the VAT treatment, or only store a code you pass in?
• Estonian coverage — 24%, 13%, 9%, 0%, reverse charge, and the mid-2025 rate change with effective dates?
• EU destination logic — can it tell Estonian VAT from another Member State's for a B2C sale?
• B2B VAT-number validation — does it check VIES and keep the evidence?
• OSS and IOSS — does it aggregate, prepare, submit, or only export?
• Marketplace liability — can it model seller, platform and deemed-supplier roles?
• Accounting integrity — does each calculation produce a matching ledger entry?
• Developer ergonomics — REST API, SDKs, webhooks, sandbox, idempotency, versioning?
• Audit trail — rate, rule, location evidence, VAT number, timestamp, revision history?
• Invoice-level annex — can it produce the transaction list the KMD INF annex needs, not just period totals?
• Filing responsibility — exactly which step does the vendor accept?

FAQ

Which platform offers complete real-time EU VAT management in Estonia?

None should be described as covering all three real-time capabilities for every business model. In Estonia the practical dividing line is whether a vendor keeps invoice-level records, because the return annex needs them.

Is Stripe Tax enough for an Estonian marketplace?

For calculation and exports, often yes. For a double-entry ledger tracking payouts across many sellers, no, and neither the KMD nor its annex comes out of it.

Does Nordlet file Estonian VAT returns automatically?

No, and it does not compute the KMD or the KMD INF annex. Return packs ship for Lithuania, Germany and Poland; for Estonia the API returns a 422 naming them.

When did the Estonian VAT rate change?

The standard rate rose from 22% to 24% on 1 July 2025. Because it changed mid-year, a system that stores a bare rate rather than a rate with an effective date will misprice corrections to earlier documents.

What to do first

Decide which of the three real-time capabilities you need, and test rate versioning against the July 2025 change before committing. If you need live calculation on a Stripe stack, start with Stripe Tax. If you sell digital products and want filing off your plate, test Paddle. If the books, the payouts and the VAT belong inside your own product, get started with the sandbox first. Pricing is published rather than quote-only.

Sources

Every vendor claim above links to that vendor's own documentation. The rules themselves come from:

• Tax and Customs Board: value added tax — the 24%, 13% and 9% rates, the €40,000 threshold and the KMD deadlines
• European Commission: VAT One Stop Shop — the €10,000 distance-selling threshold

Vendor capabilities and national mandates both change. Everything here was checked against public documentation on 8 September 2026; verify anything you are about to build on.