Real-Time EU VAT for Developers Building in Hungary

Hungary invented the modern version of real-time invoice reporting, and it is still the strictest implementation in the EU. Every invoice issued by a VAT-registered taxpayer is reported to NAV as XML, immediately, with no value threshold. Hungary also has the highest standard VAT rate in the union at 27%. So when a vendor says it supports "real-time Hungarian VAT", the only question that matters is whether it talks to Online Számla.

This piece compares the developer-facing platforms that handle EU and Hungarian 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 Hungary 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. Hungary is the country the phrase was coined for. Invoice data goes to NAV immediately, for every invoice, with no value threshold, so the third capability is not optional and cannot be batched at month end.

The Hungarian and EU rules that shape the comparison

Hungary applies a 27% standard rate, the highest in the EU, with reduced rates of 18% and 5% and 0% for exports and intra-EU supplies. The 18% rate covers certain dairy and bakery products and some events; the 5% rate covers new housing, medicines, books, district heating and some foods. The statutory basis is the VAT Act, Act CXXVII of 2007. The exemption threshold is HUF 20,000,000 for 2026, raised from HUF 18m and rising to HUF 22m in 2027. Hungary uses the forint, so a euro-only platform needs conversion and rounding rules that hold up in the reported XML.

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, Hungary included	EU exports and OSS data; no Hungarian 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 Online Számla integration and no ÁFA return pack; produces the ledger and Peppol invoices

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 a Hungarian build, Stripe Tax stops exactly where the obligation starts. Online Számla reporting is a separate integration, and it is the one with immediate deadlines.

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 Hungarian consumers this is a clean route. It does nothing for a Hungarian company's own Online Számla obligation on invoices it issues.

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 covers checkout calculation. Neither the ÁFA return nor Online Számla reporting is within its scope.

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.

Hungary is one of the countries where an enterprise engine with a documented Online Számla connector is a defensible purchase, because the reporting is unforgiving and continuous.

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

{
  "scheme": "oss_union",
  "vatCountryCode": "HU",
  "reverseCharge": false,
  "deemedSupplier": false,
  "zeroRated": false,
  "rates": [
    { "category": "standard", "ratePercent": "27.00" },
    { "category": "reduced", "ratePercent": "18.00" },
    { "category": "reduced", "ratePercent": "5.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 Hungarian 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 Hungarian boundary is wide, and worth stating before anything else. Nordlet has no Online Számla integration: invoice data is not transmitted to NAV, and there is no Hungarian return pack — /v1/declarations/eu/vat-return/compute with countryCode: "HU" returns a 422 naming Lithuania, Germany and Poland. National e-invoicing payload builders exist for Italy, Poland and Romania, not for Hungary. What Nordlet covers for a Hungarian entity is the accounting side: VAT determination carrying its legal basis, 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. If your Hungarian company issues its own invoices, the Online Számla connection remains a separate requirement.

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

Hungary reports continuously and files periodically.

• Online Számla — real-time invoice reporting to NAV. It is mandatory for all invoices issued by VAT-registered taxpayers, in XML, with no value threshold. Reporting happens as the invoice is issued, not at period end.
• ÁFA return — the VAT return, filed monthly, quarterly or annually by the 20th. NAV assigns the frequency.
• eVAT drafts — NAV prepares draft returns from the reported data, which only works when the reported data is right.

The order of dependency is the thing to design around: the invoice report comes first, and the return follows from it. Getting the reporting wrong makes the return wrong too.

The full picture for the country — corporate tax, payroll, filing calendar and the authorities behind each form — is on the Hungary 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?
• Hungarian coverage — 27%, 18%, 5%, 0%, reverse charge, forint amounts and the HUF 20,000,000 exemption threshold?
• EU destination logic — can it tell Hungarian 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?
• Online Számla — does it report invoice data to NAV in the required XML as invoices are issued, with no value threshold?
• Filing responsibility — exactly which step does the vendor accept?

FAQ

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

None should be described as covering all three real-time capabilities for every business model. Hungary makes the third one the deciding factor: a vendor without an Online Számla connection is not a complete answer regardless of how good its calculation is.

Does Stripe Tax report to Online Számla?

No. Stripe Tax calculates VAT and exports data. Transmitting invoice data to NAV is a separate integration, and in Hungary it is mandatory for every invoice.

Does Nordlet report Hungarian invoices to NAV?

No. There is no Online Számla integration and no Hungarian return pack. Nordlet covers the determination, the ledger, the OSS and IOSS figures and the audit trail; the NAV reporting connection is a separate requirement.

Is there a value threshold for Hungarian invoice reporting?

No. Every invoice issued by a VAT-registered taxpayer is reported, regardless of value, in XML.

What to do first

In Hungary, start from Online Számla and work backwards, because it is the obligation with no tolerance. If you sell digital products and want the whole tax role handled elsewhere, test Paddle. If you need books, payouts and an audit trail inside your own product alongside a separate NAV reporting connection, get started with the sandbox and confirm which parts are covered before you build around it. Pricing is published rather than quote-only.

Sources

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

• NAV: VAT and Online Számla — the 27%, 18% and 5% rates and the real-time invoice reporting obligation
• VAT Act (Act CXXVII of 2007) — the statutory basis for Hungarian VAT
• 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.