Real-Time EU VAT for Developers Building in Romania

Romania has stacked three obligations on top of each other in three years: e-Factura clearance for B2B since 2024 and B2C since 2025, SAF-T D406 for all taxpayers since 2025, and a VAT rate rise from 19% to 21% in August 2025 that also merged the two reduced rates into one. Failing to issue an e-invoice can cost 15% of the invoice value. Romania is not a country where a rate table is enough.

This piece compares the developer-facing platforms that handle EU and Romanian 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 Romania 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. Romania is firmly in the third category, twice over: invoices are cleared through the national e-Factura platform, and SAF-T D406 delivers transaction detail on a regular schedule.

The Romanian and EU rules that shape the comparison

Romania applies a 21% standard rate, raised from 19% on 1 August 2025, and a single 11% reduced rate that merged the former 5% and 9% rates on the same day, covering food, medicines, water, books, hotels and similar; a transitional 9% rate on qualifying new homes runs to 31 July 2026. Exports and intra-EU supplies are zero-rated. The rules are published by ANAF. Registration is required above RON 395,000, raised from RON 300,000 on 1 September 2025. Romania uses the leu, so currency handling has to survive both the reporting and the books.

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, Romania included	EU exports and OSS data; no Romanian 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	Builds the e-Factura CIUS-RO payload and sends through a bridge; D300 and SAF-T D406 are not generated

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 a Romanian stack, Stripe Tax gives you a rate. The e-Factura clearance and the D406 file, which are where the penalties live, are untouched by it.

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 Romanian consumers this covers VAT end to end. A Romanian company still owes e-Factura clearance and SAF-T on its own activity.

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 checkout calculation. e-Factura and D406 are outside its scope, and in Romania those are the obligations with deadlines and fines.

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.

Romania is one of the strongest cases for an enterprise engine, because clearance and SAF-T together are a substantial build. It is still a large purchase for a single-country product.

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

{
  "scheme": "oss_union",
  "vatCountryCode": "RO",
  "reverseCharge": false,
  "deemedSupplier": false,
  "zeroRated": false,
  "rates": [
    { "category": "standard", "ratePercent": "21.00" },
    { "category": "reduced", "ratePercent": "11.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 Romanian 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 Romanian scope is partial, and the split is worth knowing exactly. On the invoice side, Nordlet builds the RO e-Factura payload as EN 16931 UBL with CustomizationID CIUS-RO 1.0.1, available at /v1/sales/invoices/einvoice-xml and sent at /v1/sales/invoices/einvoice-send through a per-company HTTP bridge configured as ro_efactura, which owns the ANAF SPV OAuth credentials and the certified channel. One known gap is flagged rather than guessed: the county (CountrySubentity) is missing from the address data model, so it is reported as a warning on the payload. On the return side there is no Romanian pack — /v1/declarations/eu/vat-return/compute with countryCode: "RO" returns a 422 naming Lithuania, Germany and Poland — so neither D300 nor the SAF-T D406 file is generated.

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

Romania asks for three separate things, on three different clocks.

• RO e-Factura — structured e-invoices through the national platform. Mandatory for B2B since 2024 and for B2C since 2025, and from 2026 invoices must be sent to the platform within 5 working days of issue. Failing to issue an e-invoice can cost 15% of the invoice value.
• SAF-T D406 — the standard audit file. D406 General is filed monthly or quarterly, matching the VAT period, by the last day of the following month; an assets file is annual, and a stocks file is produced on ANAF request. It has applied to all taxpayers since 2025.
• D300 — the VAT return, filed monthly or quarterly by the 25th, with payment at the same time.

The three obligations draw on the same underlying records, which is the strongest practical argument for keeping invoicing and bookkeeping in one system rather than two.

The full picture for the country — corporate tax, payroll, filing calendar and the authorities behind each form — is on the Romania 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?
• Romanian coverage — 21%, 11%, the transitional 9% on new homes, 0%, reverse charge, leu amounts and the RON 395,000 threshold?
• EU destination logic — can it tell Romanian 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?
• e-Factura and SAF-T — can it produce CIUS-RO UBL invoices, reach the ANAF platform within 5 working days, and emit the D406 file?
• Filing responsibility — exactly which step does the vendor accept?

FAQ

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

None should be described as covering all three real-time capabilities for every business model. Romania splits into three problems — clearance, SAF-T and the return — and very few vendors solve more than one.

Does Stripe Tax handle RO e-Factura?

No. Stripe Tax calculates VAT and exports data. Clearing an invoice through the national e-Factura platform is a separate integration, and in Romania missing it carries a penalty of 15% of the invoice value.

Does Nordlet file Romanian VAT returns automatically?

No. There is no Romanian return pack, so neither D300 nor SAF-T D406 is generated. Nordlet does build the e-Factura CIUS-RO payload and send it through a bridge you configure, flagging the missing county field rather than inventing one.

What changed in Romanian VAT rates in 2025?

The standard rate rose from 19% to 21% on 1 August 2025, and the former 5% and 9% reduced rates merged into a single 11% rate on the same day. A transitional 9% rate on qualifying new homes runs to 31 July 2026.

What to do first

In Romania, treat e-Factura and SAF-T as the requirements and the rate table as a detail. If you sell digital products and want the whole tax role elsewhere, test Paddle. If the ledger, the payouts and the e-Factura payload have to come from the same data, get started with the sandbox and confirm the Romanian scope — payload yes, returns and SAF-T no — 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:

• ANAF: VAT guidance — the 21% and 11% rates, the D300 return and the registration threshold
• European Commission: eInvoicing in Romania — the RO e-Factura mandate and its phases
• 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.