Real-Time EU VAT for Developers Building in Italy

Italy is the country where a vendor's "real-time VAT" claim is easiest to test, because Italy already has real-time reporting and has had it for years. Every established taxable person issues structured XML invoices through the Sistema di Interscambio, the tax authority sees them as they are issued, and an invoice that fails validation is simply not an invoice. A platform that computes 22% at checkout and stops there has solved the smallest part of an Italian integration.

This piece compares the developer-facing platforms that handle EU and Italian 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 Italy 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. Italy is the clearest case in the EU where the third capability is the law rather than a feature: invoices are cleared by the Sistema di Interscambio before they reach the customer.

The Italian and EU rules that shape the comparison

Italy applies a 22% standard rate, with reduced rates of 10%, 5% and 4% and 0% for exports and intra-EU supplies, under the VAT Decree (DPR 633/1972). There is no registration threshold: a partita IVA is required from the start of activity. The flat-rate regime (forfettario), available up to €85,000, is VAT-exempt, which is another state your invoicing logic has to carry rather than infer.

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, Italy included	EU exports and OSS data; no Italian 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 FatturaPA payloads and sends through a configured bridge; LIPE and the annual return are not shipped

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 Italian stack, Stripe Tax answers the rate question and leaves the SdI question untouched. The invoice that legally counts in Italy is the XML the SdI accepts, not the one your checkout renders.

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 this removes both the calculation and the filing problem. It does not help an Italian company that has to clear its own B2B invoices through the SdI.

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 is a reasonable tax layer for a small Italian digital business, but the FatturaPA path and the periodic settlement 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.

Fonoa in particular is aimed at exactly this shape of problem — many jurisdictions, several of them with clearance platforms. For a single-country Italian build it is usually more machinery than the problem needs.

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

{
  "scheme": "oss_union",
  "vatCountryCode": "IT",
  "reverseCharge": false,
  "deemedSupplier": false,
  "zeroRated": false,
  "rates": [
    { "category": "standard", "ratePercent": "22.00" },
    { "category": "reduced", "ratePercent": "10.00" },
    { "category": "reduced", "ratePercent": "5.00" },
    { "category": "super_reduced", "ratePercent": "4.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 Italian 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 Italian boundary is specific, so here it is. Nordlet builds the FatturaPA payload — FPR12, schema version 1.2.3 — from the canonical invoice, available at /v1/sales/invoices/einvoice-xml, and sends it at /v1/sales/invoices/einvoice-send through a per-company HTTP bridge configured as it_sdi in compliance settings. The bridge, an accredited intermediary or a connector you run, owns the certified SdI channel and its accreditation; direct certified transport is deliberately not implemented until there are credentials to test against. Natura codes are assumed from the resolved VAT scheme and flagged for review rather than silently chosen. On the return side there is no Italian pack: /v1/declarations/eu/vat-return/compute with countryCode: "IT" returns a 422 naming Lithuania, Germany and Poland, so the LIPE and the annual return are not 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 Italy makes you file

Italy layers a clearance platform on top of ordinary periodic returns.

• E-invoicing through the SdI — all established taxable persons issue FatturaPA XML through the Sistema di Interscambio, which validates and delivers each invoice. Cross-border invoice data is transmitted through the same system.
• Periodic settlements and LIPE — VAT is paid by the 16th of the following month, or quarterly with 1% interest. The periodic settlement communication (LIPE) is filed quarterly, by the end of the second month after the quarter.
• Annual VAT return — the dichiarazione IVA, due 30 April.

The practical consequence for a platform is that invoice issuance and tax reporting are the same act in Italy. If your product issues invoices for Italian sellers, it is already inside the reporting system whether it was designed for that or not.

The full picture for the country — corporate tax, payroll, filing calendar and the authorities behind each form — is on the Italy 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?
• Italian coverage — 22%, 10%, 5%, 4%, 0%, reverse charge, and the forfettario exemption?
• EU destination logic — can it tell Italian 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?
• SdI clearance — can it produce valid FatturaPA XML, choose or flag the Natura code, and reach an accredited SdI channel?
• Filing responsibility — exactly which step does the vendor accept?

FAQ

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

None should be described as covering all three real-time capabilities for every business model. Italy makes the third one unavoidable, so the useful question is which vendor produces valid FatturaPA XML and which one merely calculates a rate.

Does Stripe Tax handle FatturaPA and the SdI?

No. Stripe Tax calculates VAT and exports data. Clearing an invoice through the Sistema di Interscambio is a separate integration, and in Italy it is the one that determines whether the invoice legally exists.

Does Nordlet file Italian VAT returns automatically?

No. There is no Italian return pack, so the LIPE and the annual VAT return are not generated. Nordlet builds the FatturaPA payload and sends it through a bridge you configure, and it produces the VAT determination, the ledger and the OSS and IOSS figures behind the numbers.

What is a bridge, and why does Nordlet use one for the SdI?

A bridge is an HTTP endpoint you configure — an accredited intermediary or a connector you host — that owns the certified channel to the SdI and its accreditation. Nordlet builds and delivers the payload to it. Direct certified transport is not implemented because it cannot be tested without those credentials.

What to do first

Decide which of the three real-time capabilities you need, and treat the SdI as a first-class requirement rather than an export format. 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 you are building a marketplace where the ledger, the payouts and the FatturaPA payload have to come from one place, get started with the sandbox and confirm the Italian scope — payload yes, returns 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:

• Agenzia delle Entrate: IVA rates, rules and e-invoicing — the 22%, 10%, 5% and 4% rates and the SdI obligation
• DPR 633/1972 (VAT Decree) — the statutory basis for Italian 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.