Nordlet

← Blog

Real-Time EU VAT for Developers Building in Ireland

A grounded comparison of accounting and tax platforms that handle Irish and EU VAT through APIs, SDKs and webhooks, with clear notes on what each one actually covers.

Nordlet Team · · 12 min read

Ireland has two VAT registration thresholds rather than one — €85,000 for goods and €42,500 for services — and a rate structure with more zero-rated categories than most of the EU: most food, oral medicines and children's clothing all sit at 0%. A platform that models Irish VAT as "23% unless told otherwise" will be wrong often, and wrong in a direction customers notice.

This piece compares the developer-facing platforms that handle EU and Irish 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 Ireland 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. Ireland has no clearance platform and no e-invoicing mandate in force, so the third capability is not a legal requirement here. The first one is harder than it looks, because of how much is zero-rated.

The Irish and EU rules that shape the comparison

Ireland applies a 23% standard rate, with reduced rates of 13.5% and 9% and a wide 0% band covering exports, most food, oral medicines and children's clothing. The 13.5% rate covers construction, fuel and many services; the 9% rate covers newspapers and some tourism, and restaurant, catering and hairdressing services move from 13.5% to 9% in July 2026. The rules are published by Revenue, and the statutory basis is the Value-Added Tax Consolidation Act 2010. Registration thresholds are €85,000 for goods and €42,500 for services; a non-established business registers from its first taxable supply.

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, Ireland included EU exports and OSS data; no Irish 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 Irish return pack; determination carries the legal basis and the ledger carries the 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.

On an Irish stack the test worth running is the zero-rated categories, not the standard rate. Ask how food, oral medicines and children's clothing are handled before assuming coverage.

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 Irish consumers this covers calculation, filing and remittance. An Irish company still files VAT3 and the annual return of trading details.

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.

It handles the checkout case for a small Irish digital business. VAT3 and the RTD are not produced by 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 Irish-only build both are more product than the problem needs. Ireland has no clearance platform and no mandate to absorb.

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": "IE",
  "customerIsBusiness": false,
  "supplyType": "digital"
}

{
  "scheme": "oss_union",
  "vatCountryCode": "IE",
  "reverseCharge": false,
  "deemedSupplier": false,
  "zeroRated": false,
  "rates": [
    { "category": "standard", "ratePercent": "23.00" },
    { "category": "reduced", "ratePercent": "13.50" },
    { "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 Irish 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 Irish boundary is short. Nordlet ships no Irish return pack: /v1/declarations/eu/vat-return/compute with countryCode: "IE" returns a 422 naming Lithuania, Germany and Poland, so neither the VAT3 nor the annual return of trading details is generated and nothing is filed through ROS. What is there for an Irish build is the VAT determination with its legal basis attached, an immutable double-entry ledger with the VAT metadata on each entry, OSS and IOSS computation with corrections, VIES validation frozen against the invoice, and EN 16931 invoices over Peppol BIS 3.0. Rate determination is per country and rate category rather than per product classification, which matters more in Ireland than elsewhere: the wide 0% band is a product-level decision that has to be made upstream.

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 Ireland makes you file

Ireland has a light filing calendar by EU standards.

  • VAT3 — the VAT return, filed bi-monthly by the 23rd through ROS, with payment due at the same time. Less frequent periods are available to smaller traders.
  • Return of Trading Details (RTD) — an annual return summarising supplies and purchases by rate.
  • E-invoicing — no mandate is in force. A consultation has been running, and the EU ViDA timetable will eventually reach intra-EU B2B invoices.

With no invoice-level reporting to the tax authority, the Irish burden is small. The complexity is in the rate decisions themselves rather than in the transport.

The full picture for the country — corporate tax, payroll, filing calendar and the authorities behind each form — is on the Ireland 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?
  • Irish coverage — 23%, 13.5%, 9%, the wide 0% band, reverse charge, and two separate registration thresholds?
  • EU destination logic — can it tell Irish 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?
  • Zero-rate handling — can it place food, oral medicines and children's clothing in the 0% band rather than defaulting them to 23%?
  • Filing responsibility — exactly which step does the vendor accept?

FAQ

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

None should be described as covering all three real-time capabilities for every business model. Ireland has no clearance platform, so the comparison narrows to calculation quality and whether the numbers land in real books.

Is Stripe Tax enough for an Irish marketplace?

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

Does Nordlet file Irish VAT returns automatically?

No, and it does not compute VAT3 or the RTD. Return packs ship for Lithuania, Germany and Poland; for Ireland the API returns a 422 naming them.

Why does Ireland have two VAT registration thresholds?

Supplies of goods and supplies of services are treated separately: €85,000 for goods and €42,500 for services. A business supplying both has to track them against different limits, and a non-established business registers from its first taxable supply.

What to do first

Decide which of the three real-time capabilities you need, and test any candidate against the zero-rated categories rather than the standard rate. 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:

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.