Which countries Zeppol covers, and which come next
Published 13 September 2026 · every effort judgement checked against the shipping code on 13 September 2026
Most e-invoicing apps answer "which countries do you support?" with a list of flags. That question has two halves and the flags answer neither. The first half is whether the network we deliver on reaches that country's requirement at all. The second is what a merchant established there needs from us that a German one does not. This page answers both, country by country, and says where the order of work comes from.
The short version
The two questions, and why they are separate
Question one: does the country's requirement run on Peppol? This is the one that decides whether Zeppol is the right product at all, and it is covered in full on EU e-invoicing mandates. Italy, France, Poland, Romania, Greece and Spain each built a national route that a Peppol access point cannot deliver into. No amount of work on our side changes that. They are not slow items on a roadmap; they are a different product.
Question two: what does a merchant established there need that we do not already do? This is the roadmap question, and it has a surprisingly concrete answer, because Peppol publishes the country rules as machine-readable files and we already run them.
Why the answer is concrete: the rules ship with the standard
Eight countries have national validation rules inside Peppol BIS Billing 3.0: Germany, Denmark, Greece, Iceland, Italy, the Netherlands, Norway and Sweden. They are not a separate download and there is no national profile to adopt: they sit in the same schematron file as the Peppol rules themselves, and each one fires automatically when the seller's country code matches. A Swedish supplier's invoice runs the Swedish rules. A German supplier's runs the German ones. Nobody opts in and nobody can opt out.
Zeppol already validates every invoice against that file before anything is sent, so we can read off exactly what a new country demands rather than estimate it. In release 3.0.20, the current one and the one Zeppol pins, Germany carries 30 rules, Denmark 14, Greece 19, Sweden 13, Iceland 10, the Netherlands 9, Italy 4 and Norway 2. The remaining EU countries carry none, which is the single largest reason most of them cost us nothing.
Every country, and what it costs us
Status as at 13 September 2026. The middle column is the law; the right-hand column is our build. A country can be easy for us and still be the wrong product for a merchant there, and Italy is the clearest example: an Italian seller's invoice would pass validation happily, and it still would not satisfy Italy, because Italy requires submission to SdI.
| Country | Does Peppol satisfy its requirement? | What a merchant established there needs from us | Where it sits |
|---|---|---|---|
| Germany | Yes: one of several permitted routes; the duty is about format, not channel | Nothing. This is what Zeppol is built and tested on | Live |
| Belgium | Yes: Peppol is the mandated route, live since 1 Jan 2026 | Nothing. Euro, VAT-number addressing, no national rules | Live |
| Ireland | Yes: Peppol, phased from Nov 2028 | Nothing | Live |
| Luxembourg | Yes: Peppol; bill 8815 proposes receiving from Jan 2028 | Nothing | Live |
| Austria | No B2B mandate; Peppol is used for public bodies and cross-border | Nothing | Live |
| Slovakia | Yes: moving to Peppol BIS 3 from 1 Jan 2027, law passed Dec 2025 | Nothing known yet; the real-time reporting leg is a separate question we are watching | Live, watching |
| Slovenia | Yes: one of four permitted routes from 1 Jan 2028 | Nothing | Live |
| Latvia | Yes: national platform and Peppol, from 1 Jan 2028 | Nothing | Live |
| Estonia | No mandate; a buyer may demand an EN 16931 invoice since Jul 2025 | Nothing | Live |
| Lithuania | No B2B mandate; Peppol connected for public bodies | Nothing | Live |
| Malta | No B2B mandate; plain Peppol BIS, no national platform | Nothing | Live |
| Cyprus | No B2B mandate; Peppol through the government gateway | Nothing | Live |
| Croatia | Partly: Peppol carries the invoice from 1 Jan 2026, but the fiscalisation report to the tax administration is a separate leg we do not file | Nothing for the invoice. The reporting leg is out of scope | Invoice only |
| Bulgaria | No B2B mandate in law; SAF-T reporting phases in from Jan 2026 | Nothing. Bulgaria joined the euro on 1 Jan 2026, which removed the only real obstacle | Live |
| Portugal | No B2B e-invoicing mandate; Peppol is the B2G route | Nothing for Peppol. The qualified electronic signature required on PDF invoices from Jan 2027 is a different obligation we do not discharge | Live, partial |
| Netherlands | Yes: Peppol, with a mandate phased 2030 to 2032 | Fields. Nine national rules. A KVK or OIN number on the seller and, for a Dutch buyer, on the buyer too. Neither is captured today | Next |
| Finland | No mandate; a buyer over EUR 10,000 turnover may demand EN 16931 | Addressing. Euro, and no national rules, but Finnish businesses are addressed by organisation number, not VAT number, which our onboarding cannot yet derive | Next |
| Denmark | No mandate, but bookkeeping systems must send and receive Peppol or OIOUBL | Currency and fields. Danish krone, 14 national rules, CVR numbers on both parties, organisation-number addressing, and Danish payment-reference formats | After that |
| Sweden | No B2B mandate; plain Peppol BIS, widely used | Currency and fields. Swedish krona, 13 national rules including a checksum on the organisation number and a restricted VAT rate set, plus Bankgiro and Plusgiro payment encoding | After that |
| Norway (not EU) | Yes: mature Peppol country, and outside the EU | The most of any Peppol country. Norwegian krone, organisation-number addressing, two national rules, and no VIES: Norway is outside the EU VAT system our VAT validation depends on, and outside the country list our eligibility gate uses | After that |
| Italy | No: SdI clearance only | Peppol does not discharge the Italian obligation. Not on the roadmap | Not a route |
| France | No: approved platforms and a state directory, receiving live since 1 Sep 2026 | A different integration, not a Peppol one. Not on the roadmap | Not a route |
| Poland | No: KSeF clearance, national FA(3) schema | Not on the roadmap | Not a route |
| Romania | No: e-Factura clearance through ANAF | Not on the roadmap | Not a route |
| Spain | As a format, not as a route: a Peppol BIS message counts, but the platform carrying it must be certified in Spain | Platform certification, not document work. Not on the roadmap | Not a route |
| Greece | No: myDATA with accredited providers; Peppol is the B2G route only | Greece has 19 national rules and they are structural: the invoice number must be six segments and must carry a MARK number issued by myDATA. That is a myDATA integration wearing Peppol clothes | Not a route |
| Hungary | No: real-time reporting to NAV, not e-invoicing | Not on the roadmap | Not a route |
| Czechia | No B2B mandate; the national route is not Peppol | Not on the roadmap | Not a route |
What "nothing" actually means
Fourteen countries in the table need nothing from us, and that deserves an explanation rather than a claim, because it is the sort of thing vendors say loosely.
A merchant in one of those countries is addressed on Peppol by their VAT number, under the scheme their country uses: 9925 for Belgium, 9935 for Ireland, 9938 for Luxembourg, and so on. Zeppol reads that scheme out of the official Peppol code list rather than hard-coding a German one, so onboarding a Belgian store already works the same way a German one does. Their invoices are priced in euro, which is what we issue in. Their buyers are inside the EU VAT system, so VIES validation applies unchanged. And no national rules fire on their documents, so the invoice our builder produces is the invoice their country expects.
What "nothing" does not mean is untested. We have tested German output exhaustively and every other country by construction. Before we name a country as supported in the app, it gets its own validation fixture and a real send on the test network. That is a day of work per country, not a project, but it is not zero and we would rather say so.
What the three "next" countries actually need
The Netherlands is the clearest piece of work on this list and the most likely to be worth doing. Two of the nine Dutch rules are the whole job: the seller's legal entity identifier must be a KVK or OIN number, and when the buyer is also Dutch, theirs must be too. Our invoice builder already has a slot for the seller's, because we anticipated this; nothing fills it, and the buyer's side has no slot at all. So the work is capturing a KVK number during onboarding, capturing the buyer's at checkout alongside the VAT number we already ask for, and the Dutch rules on addresses and payment means that come with them.
Finland is smaller and stranger. There are no Finnish rules to satisfy and the currency is euro, so the document is fine as it stands. What is missing is the address: Finland, like Denmark, Norway and Sweden, identifies businesses on Peppol by organisation number rather than VAT number, and the part of our onboarding that derives a merchant's own Peppol address only knows the VAT-number schemes. A Finnish merchant cannot currently finish onboarding, which is a better failure than a wrong invoice but is still a failure.
Denmark, Sweden and Norway share one prerequisite, and it is the reason they sit together. Zeppol issues invoices in euro and blocks anything else for review rather than guessing. That is the correct behaviour for a German-first launch and it makes the Nordics unreachable, because a Danish store sells in kroner. Multi-currency is not hard, but it is not cosmetic either: it touches VAT rounding, the tax breakdown and the PDF. Once it is done, Denmark and Sweden are a fortnight of rule work each. Norway adds two further problems that neither of the others has: no VIES, because Norway is outside the EU VAT system, and no place in the country list our eligibility gate uses, so Norwegian orders are currently classified as exports and left alone.
The order, and the argument for it
The roadmap does not follow difficulty. It follows the deadline, because a compliance product is bought by someone who is about to be late and by almost nobody else.
- Germany, through January 2027 and January 2028. The only market with a deadline ahead of us and a store count behind it. Everything else on this page is accumulation.
- Belgium, now, at no cost. Belgium's mandate is live and its wave has largely broken. Most Belgian businesses were registered on Peppol by their bank or their accountant before Shopify entered the picture. We are not going to win Belgium. We are also not going to spend anything to be available there, so it stays open.
- Slovakia 2027, then Latvia, Slovenia, Luxembourg and Ireland 2028. This is the most useful finding on the page. The next four Peppol deadlines after Germany all land in countries that cost us nothing to support. Being ready for them is a testing exercise and a listing change, not a build.
- The Netherlands, ahead of its own mandate. The Dutch mandate is not until 2030, but Dutch buyers ask for structured invoices today, and there are far more Dutch Shopify stores than the country's size suggests. This is the one place where buyer demand, not law, justifies building early.
- Finland, then Denmark, Sweden and Norway. No deadline, ever, on current law. The Nordics are an evergreen market bought for convenience rather than compliance, which makes them the right thing to build when there is no deadline to chase, and the wrong thing to build before one.
What we will not build
Italy, France, Poland, Romania, Greece, Hungary and Spain are not slow items. Each needs an integration with a national platform: SdI, the French approved-platform regime, KSeF, e-Factura, myDATA, NAV, and Spain's certified-platform rules, and each of those is a product in its own right, built and sold by companies that do only that. Adding one badly would be worse than not adding it, because a compliance app that appears to cover a country it cannot file into is the most expensive kind of wrong.
If you are established in one of those countries, we would rather tell you that here than after you install something. The same test is worth applying to any app that answers the coverage question with a row of flags: ask which of those countries it actually files into, and on what evidence.
Frequently asked questions
Can I use Zeppol if my store is not in Germany?
Yes, if you are established in one of the fourteen EU countries listed as live above: Belgium, Ireland, Luxembourg, Austria, Slovakia, Slovenia, Latvia, Estonia, Lithuania, Malta, Cyprus, Croatia, Bulgaria or Portugal. Those countries need no engineering from us: euro pricing, VAT-number addressing on Peppol and no national validation rules. Germany is where the product is built and tested, so it is where the deepest support is, but it is not a restriction.
Can I sell to a country you do not list as supported?
Almost always yes, and this is the distinction that matters most. Peppol's national rules apply to the seller's country, not the buyer's, so a German store invoicing a Dutch, Danish or Finnish business is already producing a correct invoice today. What we cannot yet do is serve a merchant who is themselves established in one of those countries. Selling into a country and being established in it are different problems, and only the second one is on this roadmap.
Why is the Netherlands not supported when Dutch e-invoicing runs on Peppol?
Because the network reaching a country is not the same as the document being accepted there. The Netherlands has nine national validation rules inside Peppol BIS Billing 3.0, and two of them are fatal: a Dutch seller's legal entity must be identified by a KVK or OIN number, and so must a Dutch buyer's. We do not capture either yet. Until we do, a Dutch merchant's invoice would be rejected on validation, so we would rather not claim the country.
When will the Nordics be supported?
After multi-currency, which is their shared prerequisite: Zeppol issues invoices in euro today and blocks anything else for review rather than guessing at the VAT rounding. Finland is the exception and comes first, because it is already in euro and needs only organisation-number addressing. Denmark and Sweden follow, then Norway, which additionally sits outside the EU VAT system that our VAT validation depends on. None of these countries has a mandate deadline, which is why they come after the countries that do.
Will you ever support Italy, France, Poland or Spain?
Not on the current plan. Each of those countries requires submission to a national platform that a Peppol access point cannot deliver into: SdI, the French approved-platform regime, KSeF and Spain's certified-platform rules respectively. That is a separate integration per country, not a variation on what Zeppol does. If you are established in one of them and invoicing domestically, you need software built for that country.
How do you know what each country requires, rather than estimating it?
Peppol publishes the national rules as machine-readable schematron, distributed inside the same file as the Peppol rules themselves, and Zeppol validates every invoice against that file before anything is sent. So the requirements for Germany, Denmark, Greece, Iceland, Italy, the Netherlands, Norway and Sweden can be read directly rather than guessed, and the other EU countries can be shown to have none. The rules fire automatically on the seller's country code; no country-specific profile has to be adopted for them to apply.
Does this page change if a country moves its deadline?
The order does, and deadlines in this area move often. What does not change is the effort column, because it depends on the Peppol rule sets and on currency rather than on politics. A country that postpones its mandate becomes less urgent without becoming harder.
This page describes what Zeppol supports and plans to support; it is not a commitment to a date and it is not legal or tax advice. The mandate column was checked against primary sources on 13 September 2026 and is set out in full, with sources, on EU e-invoicing mandates. The effort column was assessed against Zeppol's own shipping code and against the Peppol BIS Billing 3.0 rule set on the same date. Mandates and deadlines here move often, so confirm your own obligations with a qualified adviser in the country concerned.
E-invoices from your Shopify B2B orders
Zeppol turns every B2B order into an EN 16931 document, checks it against the EU and the German rules, and sends it over Peppol or by email. Join the list and I'll be in touch before the deadline.