Real-Time EU VAT for Developers Building in Denmark

Denmark is the EU country where the regulator came for the accounting software rather than the invoice. The Bookkeeping Act requires records to be kept in a digital system that meets stated requirements, with a SAF-T export available, phasing in for companies from 2024 to 2026. Meanwhile the VAT itself is the simplest in the EU: one rate, 25%, with no reduced rates at all. So a Danish integration is almost entirely a bookkeeping question.

This piece compares the developer-facing platforms that handle EU and Danish 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 Denmark 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. Denmark inverts the usual question. There is no clearance platform, but the bookkeeping system itself is regulated, so the second capability — do the numbers land in real, exportable books — is the one with a law behind it.

The Danish and EU rules that shape the comparison

Denmark applies a single 25% VAT rate, with no reduced rates; exports and some supplies are zero-rated. The statutory basis is the VAT Act (Momsloven). Registration is required above DKK 50,000 of turnover in 12 months. Denmark keeps the krone, so a euro-only platform needs currency handling that stands up in the books rather than only at checkout.

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, Denmark included	EU exports and OSS data; no Danish 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 Danish return pack and no SAF-T DK export; the ledger itself is immutable and exportable

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.

With one rate and no reduced rates, calculation is close to trivial in Denmark. That makes a calculation-only product a thin purchase here.

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 Danish consumers this covers VAT end to end. It does not address the Bookkeeping Act obligations that fall on your own Danish entity.

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.

In a single-rate country, the tax-calculation part of Quaderno adds little. Its invoicing and record features are the parts worth evaluating.

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.

Neither is a natural fit for a Danish-only build. Denmark is the country where the accounting system, not the tax engine, is the regulated component.

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

{
  "scheme": "oss_union",
  "vatCountryCode": "DK",
  "reverseCharge": false,
  "deemedSupplier": false,
  "zeroRated": false,
  "rates": [
    { "category": "standard", "ratePercent": "25.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 Danish 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 Danish boundary is unusual, so it is worth being exact. Nordlet ships no Danish return pack: /v1/declarations/eu/vat-return/compute with countryCode: "DK" returns a 422 naming Lithuania, Germany and Poland, so the momsangivelse is not generated, and there is no SAF-T DK export and no registration as a Danish digital bookkeeping provider. What Nordlet does provide is the property the Danish law is aimed at: an immutable double-entry ledger with period locking, VAT metadata attached to each entry, a full revision history, and an exportable audit trail — plus VAT determination with its legal basis, OSS and IOSS computation, VIES validation frozen against the invoice, and Peppol BIS 3.0 sending, which is the transport Danish public-sector invoicing already 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 Denmark makes you file

Denmark has a light return and a heavy bookkeeping regime.

• Momsangivelse — the VAT return, filed monthly, quarterly or half-yearly by turnover. Monthly filers, above DKK 50m, pay by the 25th; quarterly and half-yearly filers pay by the first day of the third month after the period.
• Digital bookkeeping — the Bookkeeping Act requires records to be kept in a digital accounting system meeting stated requirements, with a SAF-T export available. It phases in for companies from 2024 to 2026.
• E-invoicing — mandatory for public-sector invoices through NemHandel and Peppol, with OIOUBL giving way to Peppol BIS. B2B remains voluntary.

If you are choosing a system for a Danish entity, the Bookkeeping Act is the requirement that constrains the choice, and it is a requirement about the system, not about a filing.

The full picture for the country — corporate tax, payroll, filing calendar and the authorities behind each form — is on the Denmark 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?
• Danish coverage — 25% with no reduced rates, zero-rating, reverse charge, and krone amounts in the ledger?
• EU destination logic — can it tell Danish 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?
• Bookkeeping Act fit — does the system keep digital records to the standard the Bookkeeping Act sets, with a structured export available?
• Filing responsibility — exactly which step does the vendor accept?

FAQ

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

None should be described as covering all three real-time capabilities for every business model. Denmark makes the question simpler: with a single rate, the differentiator is the books and the export, not the calculation.

Is Stripe Tax enough for a Danish marketplace?

For calculation, Denmark barely needs a tax engine. For a double-entry ledger tracking payouts across many sellers, and for the Bookkeeping Act obligations, Stripe Tax is not the answer.

Does Nordlet file Danish VAT returns automatically?

No, and it does not compute the momsangivelse or produce a SAF-T DK file. Return packs ship for Lithuania, Germany and Poland. For Denmark it provides the determination, the immutable ledger, the OSS and IOSS figures and the audit trail.

What does the Danish Bookkeeping Act require from software?

Records must be kept in a digital accounting system that meets stated requirements, including a structured export, phasing in for companies from 2024 to 2026. It regulates the bookkeeping system itself rather than the invoice or the return.

What to do first

Decide which of the three real-time capabilities you need, and in Denmark start from the bookkeeping requirement rather than the tax engine. 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 and confirm what is and is not covered for Denmark 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:

• Skattestyrelsen: VAT, deadlines and registration — the 25% rate, the DKK 50,000 threshold and the filing deadlines
• VAT Act (Momsloven) — the statutory basis for Danish 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.