Nordlet

← Blog

Real-Time EU VAT for Developers Building in Poland

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

Nordlet Team · · 12 min read

Poland moved the goalposts in 2026. The National e-Invoicing System became mandatory in February for the largest businesses and in April for almost everyone else, so a Polish invoice is now an FA(3) XML document with a KSeF identifier rather than a PDF. On top of that sits JPK_V7M, which is not a VAT return with a separate ledger export but a single file containing both. A vendor that offers "Polish VAT" and means a 23% rate is describing a small corner of the work.

This piece compares the developer-facing platforms that handle EU and Polish 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 Poland 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. Poland now sits firmly in the third category: KSeF clearance for invoices and JPK_V7M as a combined return and ledger file mean the tax administration sees transaction detail, not just totals.

The Polish and EU rules that shape the comparison

Poland applies a 23% standard rate, with reduced rates of 8% and 5% and 0% for exports and intra-EU supplies, under the VAT Act (ustawa o podatku od towarów i usług). The registration threshold rose to PLN 240,000 on 1 January 2026, from PLN 200,000. Poland uses the złoty, so a platform that assumes euro amounts everywhere will need conversion and rounding rules that survive an audit.

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, Poland included EU exports and OSS data; no Polish 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 Generates the JPK_V7M XML and the KSeF FA(3) payload; upload and KSeF sessions run through a bridge

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 Polish build, Stripe Tax stops well before the two things that actually take time: the JPK_V7M file and the KSeF submission.

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 is a clean answer to Polish consumer VAT. It does nothing for a Polish company's own KSeF obligations on domestic invoices.

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.

Quaderno is a reasonable checkout layer for a small Polish digital business. JPK_V7M and KSeF are outside 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.

Poland is one of the countries where an enterprise engine earns its price, because KSeF and JPK are both non-trivial. It is still a large purchase for a team that only needs one country.

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

{
  "scheme": "oss_union",
  "vatCountryCode": "PL",
  "reverseCharge": false,
  "deemedSupplier": false,
  "zeroRated": false,
  "rates": [
    { "category": "standard", "ratePercent": "23.00" },
    { "category": "reduced", "ratePercent": "8.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 Polish 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 Polish scope is the widest Nordlet ships outside Lithuania, and it still has edges. /v1/declarations/eu/vat-return/compute with countryCode: "PL" returns the JPK_V7M(3) declaration fields as pack boxes, and /v1/declarations/pl/jpk-v7m/generate produces the full XML, validated against the official XSD set vendored in the repository and enforced in tests. Evidence rows carry the mandatory per-row KSeF choice — BFK until a KSeF integration supplies a real NrKSeF — and intra-EU acquisitions are self-assessed through WEW rows. GTU markers, the fixed-asset split and prior-period carryover are flagged for manual entry rather than guessed. Uploading the file to the Ministry of Finance gateway is a human step. On the invoice side, the KSeF FA(3) payload is built and validated against the official XSD, and sending runs through a per-company bridge configured as pl_ksef, which owns the KSeF tokens and certificate sessions; feeding the returned KSeF number back into the JPK rows is not implemented yet.

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

Poland has two obligations that interlock, which is why they are worth reading together.

  • JPK_V7M — a single monthly file, due by the 25th, that contains both the VAT declaration and the sales and purchase records. Small taxpayers may settle quarterly, but the records part is still filed monthly.
  • KSeF — the National e-Invoicing System. Mandatory from 1 February 2026 for businesses whose 2024 turnover exceeded PLN 200m, and from 1 April 2026 for other businesses, with micro-businesses following in 2027. Invoices are issued as FA(3) XML and receive a KSeF identifier. 2026 is a grace period; penalties begin in 2027.

The interlock is the detail to plan for: every JPK evidence row has to say how the invoice was issued, and once KSeF is live for you that means carrying the KSeF identifier from the invoice into the record.

The full picture for the country — corporate tax, payroll, filing calendar and the authorities behind each form — is on the Poland 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?
  • Polish coverage — 23%, 8%, 5%, 0%, reverse charge, złoty amounts and the PLN 240,000 threshold?
  • EU destination logic — can it tell Polish 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?
  • KSeF and JPK — can it produce XSD-valid FA(3) invoices, reach KSeF, and emit a JPK_V7M file whose evidence rows carry the right KSeF marker?
  • Filing responsibility — exactly which step does the vendor accept?

FAQ

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

None should be described as covering all three real-time capabilities for every business model. Poland splits the work clearly: calculation, the JPK_V7M file, and KSeF submission are three different problems, and few vendors solve more than one.

Does Stripe Tax handle KSeF or JPK_V7M?

No. Stripe Tax calculates VAT and exports data. The KSeF invoice and the JPK_V7M file are separate integrations, and in Poland they are the ones with deadlines attached.

Does Nordlet file Polish VAT returns automatically?

No. It produces an XSD-valid JPK_V7M(3) XML file with the declaration and the evidence rows, and flags what it cannot derive — GTU markers, the fixed-asset split and prior-period carryover. Uploading the file to the Ministry of Finance gateway is still a human step.

When did KSeF become mandatory?

On 1 February 2026 for businesses with 2024 turnover above PLN 200m, and on 1 April 2026 for other businesses; micro-businesses follow in 2027. 2026 is a grace period, with penalties from 2027.

What to do first

Decide which of the three real-time capabilities you need, then check the Polish specifics separately, because they are where the effort goes. 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 JPK_V7M file and the KSeF invoice have to come from the same data, get started with the sandbox and confirm the manual steps 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:

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.