Nordlet

← Blog

Real-Time EU VAT for Developers Building in Sweden

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

Nordlet Team · · 12 min read

Sweden has a temporary VAT change running right now that will break naive implementations: food drops from 12% to 6% for April 2026 through December 2027, then goes back. If your platform stores a rate rather than a rate with a start and an end date, it will produce the wrong figure on every credit note raised after the change ends. That is a better test of a vendor than any feature list.

This piece compares the developer-facing platforms that handle EU and Swedish 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 Sweden 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. Sweden has no clearance platform and no B2B e-invoicing mandate, so the third capability is not a legal requirement here. The temporary food-rate change makes the first one less trivial than it looks.

The Swedish and EU rules that shape the comparison

Sweden applies a 25% standard rate, with reduced rates of 12% and 6% and 0% for exports and intra-EU supplies, under the VAT Act (Mervärdesskattelag 2023:200). The 12% rate covers food, restaurants and hotels; 6% covers books, newspapers, passenger transport and cultural and sporting events. Food is temporarily cut from 12% to 6% between April 2026 and December 2027. Registration is required above SEK 120,000 of turnover, raised from SEK 80,000 in 2025, and non-established businesses register before the first sale.

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, Sweden included EU exports and OSS data; no Swedish 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 Swedish return pack; rates carry effective dates, and the ledger keeps 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 a Swedish stack, test the temporary food rate before anything else. A calculation layer that cannot express a rate with an end date will be wrong in January 2028.

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 Swedish consumers this covers calculation, filing and remittance. A Swedish company still files its own momsdeklaration.

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 reasonable checkout layer for a small Swedish digital business. The momsdeklaration is 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 a Swedish-only build both are oversized. They are worth it when you are live across many countries and several of them clear invoices centrally.

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

{
  "scheme": "oss_union",
  "vatCountryCode": "SE",
  "reverseCharge": false,
  "deemedSupplier": false,
  "zeroRated": false,
  "rates": [
    { "category": "standard", "ratePercent": "25.00" },
    { "category": "reduced", "ratePercent": "12.00" },
    { "category": "reduced", "ratePercent": "6.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 Swedish 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 Swedish boundary. Nordlet ships no Swedish return pack: /v1/declarations/eu/vat-return/compute with countryCode: "SE" returns a 422 naming Lithuania, Germany and Poland, so the momsdeklaration is not generated and nothing is filed with Skatteverket. The part that matters for the temporary food rate is that rates come from the European Commission TEDB feed with effective dates rather than as bare numbers, and a company can override them per country, so a document dated inside the reduced-rate window resolves differently from one dated after it. Alongside that sit the VAT determination with its legal basis, an immutable double-entry ledger with period locking, OSS and IOSS computation with corrections, VIES validation frozen against the invoice, and Peppol BIS 3.0 sending, which is the transport Swedish public-sector invoicing uses.

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

Sweden keeps its obligations conventional, and the frequency scales with size.

  • Momsdeklaration — the VAT return. Businesses above SEK 40m file monthly, by the 26th; smaller businesses file quarterly, and businesses up to SEK 1m may file annually.
  • E-invoicing — mandatory for invoices to the public sector over Peppol. B2B e-invoicing remains voluntary.
  • SIE files — the Swedish accounting interchange format is a widely used convention for moving ledger data between systems, not a filing obligation. It is still worth asking whether a system can produce one.

With no clearance platform in the picture, a Swedish integration is judged on whether the periodic figures can be rebuilt from the ledger at the rate that applied on the day.

The full picture for the country — corporate tax, payroll, filing calendar and the authorities behind each form — is on the Sweden 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?
  • Swedish coverage — 25%, 12%, 6%, 0%, reverse charge, krona amounts, and the temporary food rate with its end date?
  • EU destination logic — can it tell Swedish 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?
  • Rate versioning — does it store rates with effective dates, so a credit note raised in 2028 against a 2026 invoice uses the rate that applied then?
  • Filing responsibility — exactly which step does the vendor accept?

FAQ

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

None should be described as covering all three real-time capabilities for every business model. Sweden has no clearance platform, so the comparison is between calculation layers and systems of record.

Is Stripe Tax enough for a Swedish marketplace?

For calculation and exports, often yes. For a double-entry ledger tracking payouts across many sellers, no, and the momsdeklaration still has to come from somewhere else.

Does Nordlet file Swedish VAT returns automatically?

No, and it does not compute the momsdeklaration. Return packs ship for Lithuania, Germany and Poland; for Sweden the API returns a 422 naming them. It produces the determination, the ledger, the OSS and IOSS figures and the audit trail.

What is happening to the Swedish VAT rate on food?

It is temporarily cut from 12% to 6% from April 2026 to December 2027, then returns. Any system that stores a bare rate rather than a rate with effective dates will misprice corrections made after the window closes.

What to do first

Decide which of the three real-time capabilities you need, then test rate versioning against the temporary food rate before you commit to anything. 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.