Peppol in Northern Europe: How the State, Providers and Businesses Divide the Work

A comparison of documented service models, not a test of current availability. The cited pages were accessed for this series on 22 September 2026; access to a page is not a successful registration or delivery test. Denmark’s profile is explicitly dated 19 October 2021. The Finnish, Swedish and Norwegian descriptions below are attributed to their publishers, not certified as live service guarantees.

Northern Europe is often invoked as an answer rather than examined as a set of choices. One side says its experience proves that commercial intermediaries are indispensable. Another says the Nordic states provide everything themselves. Neither description is a useful basis for deciding how a Slovak business should fulfil a statutory obligation.

The relevant question is narrower: who sets the rules, who operates the infrastructure, who contracts for the service, and what practical route remains available to a small supplier? Public governance, private operation and free access at the point of use can coexist. They are not mutually exclusive models.

I support Peppol. What I want from a comparison is not a prestigious foreign label, but a clear account of how responsibility and costs are distributed.

Start by separating three different activities

Business-to-government invoicing, usually shortened to B2G, concerns a supplier billing a public buyer. Business-to-business invoicing, or B2B, concerns transactions between businesses. Tax reporting sends information to the tax administration. A service can support more than one activity, but evidence about one does not establish the rules for the others.

A government agency offering its suppliers an invoice portal is therefore meaningful evidence of an accessible procurement channel. It is not evidence that every domestic business can use that portal to invoice every other business. Nor does it tell us whether invoice data are reported for tax purposes.

Peppol itself should also be separated from the institutions around it. Finland’s State Treasury describes a network in which companies connect through service providers to exchange standardised business documents, including orders and invoices.3 That explains the delivery model. It does not by itself decide whether the supplier, the buyer or the state should procure and finance a particular access service.

Finland: an operator network with a public-facing alternative

The Finnish State Treasury’s instructions for invoicing the state describe several routes. Suppliers can send through an operator with an agreement with Posti Messaging, and they can also send through Peppol.1 The same instructions offer a government-provided online invoicing service free of charge for invoicing a Finnish government agency when the supplier does not have suitable invoicing software.1

That is an important combination. There is a provider ecosystem, but the public buyer also addresses the problem of a supplier lacking an integrated system. Public accessibility does not require pretending that the operational supply chain contains no commercial companies.

The scope matters just as much as the availability. These are instructions for invoicing the state, not a promise of a free universal B2B service. A company may still prefer an integrated commercial product because manual entry into a portal is unsuitable for its volume or workflow. The Finnish example supports the feasibility of a publicly supported baseline in a defined setting; it does not establish the economics of extending it to an entire national economy.

The State Treasury also identifies itself as Finland’s Peppol Authority and directs businesses to system suppliers and Peppol providers for connection.3 Governance and operational service provision are visibly distinct roles. That distinction is precisely what a Slovak discussion should preserve.

Sweden: look at an actual buyer, not a national slogan

The Swedish Tax Agency gives suppliers a Peppol address and asks them to send electronic invoices through the network.2 It also explains that suppliers without an e-invoicing system can use its supplier portal, provided by OpusCapita, free of charge.2

This is a particularly useful example because the tax agency appears here as a buyer. Sending an invoice to it for goods or services is not the same event as reporting a private transaction to it as a regulator. Confusing those roles would turn a practical procurement example into an unsupported claim about nationwide fiscal reporting.

The portal also illustrates why “public or private?” is an incomplete question. A public institution can make a service available while buying its technology from a private supplier. The business user sees a usable compliance route; the public buyer manages the procurement relationship behind that route.

I am not claiming that this arrangement removes every registration requirement, condition of use or operational dependency. Nor does this single agency’s page establish identical provision by every Swedish public buyer. It demonstrates a concrete arrangement that can be investigated, costed and compared rather than dismissed as conceptually impossible.

Norway: providers are part of the picture

Norway’s public procurement authority, DFØ, publishes a list of access points supporting EHF and BIS formats. Its page explains that these access points can send and receive invoices and other documents, and that DFØ is responsible for the formats.4 The list also cautions that it is not exhaustive and depends on information from suppliers.4

This evidence contradicts any romantic account in which Nordic digitisation happens entirely inside government without a service-provider market. It shows public stewardship of formats alongside operational suppliers. It does not, on its own, establish every company’s commercial terms or the current scope of Norwegian B2B obligations.

For Slovakia, the lesson is to examine the interfaces between these responsibilities. A standards authority should not disappear from accountability merely because a provider carries the message. Equally, government ownership of a specification does not make the government the operator of every access point.

Denmark: an instructive historical comparison

OpenPeppol’s Denmark profile describes public-sector invoicing using either Peppol or the national OIOUBL format, with public recipients supporting both.7 It also describes the Danish Business Authority’s role in provider registration and quality assurance.7

However, the profile explicitly says it was last updated on 19 October 2021.7 I use it as evidence of that documented institutional design, not as a reliable statement of Denmark’s complete legal position in 2026. In particular, its statement about the absence of a B2B mandate should not be recycled as a current fact without checking newer legislation.

This source limitation is itself a lesson. International comparisons age badly when an old country profile is used to settle a new legislative debate. Architecture can remain informative even when the timetable or mandatory scope needs fresh verification.

A hypothetical supplier makes the choice concrete

Imagine a Slovak manufacturer that occasionally supplies a Finnish government agency and also sells regularly to private customers at home. This is a hypothetical business, not a reported case.

For its occasional public invoice, a buyer-supported portal might be adequate if the manufacturer meets that portal’s access conditions; eligibility has not been tested here. For recurring private sales, it might choose integration from its accounting system through a commercial Peppol provider. These are rational choices for different workflows, not contradictory attitudes toward digitalisation.

Now suppose a Slovak statutory obligation required a separate recurring commercial relationship even for the occasional transaction. The policy question would be whether that relationship is necessary for the public objective, not whether Peppol needs access-point infrastructure. Infrastructure can be procured in different ways.

Conversely, suppose the state supplied only a manual form and claimed that businesses no longer faced costs. That would be equally misleading. Re-entering invoice details, managing delegated access and reconciling acknowledgements still consume work. A public baseline should be evaluated for usability and integration, not merely for the absence of a subscription price.

The strongest argument for the provider-led approach

Commercial providers can specialise, integrate with accounting systems, support multiple jurisdictions and offer contractual service levels. Public administrations may reasonably prefer a competitive ecosystem to maintaining every business-facing feature themselves. Finland’s own explanation of Peppol places service providers at the centre of network connection.3

That argument deserves a serious answer: the proposal is not to abolish providers. It is to distinguish a mandatory baseline from optional added value. Government could procure operation of a basic channel, while companies buy automation, specialist support and international functionality where these deliver value.

A public baseline could also fail. It might be underfunded, difficult to use, unfairly favoured or dependent on one contractor. The Nordic examples do not remove those risks. They show that public accessibility and commercial operation can be combined; they do not prove that every combination is efficient.

What Slovakia should actually compare

I would test both a provider-led model and a public baseline, not use foreign examples to declare either efficient. For each, publish the covered transactions and eligible users; the business’s contract partner or public-service terms; who selects and pays the operator; and who answers for failed delivery. Keep B2G, B2B and tax reporting separate. Specify which sending, receiving, correction and export functions belong to the baseline and which integrations or support services are optional additions.

Test a low-volume supplier, an integrated medium-sized business and a cross-border group over the same period. Record registration, delegation and support work alongside fees and budget costs. Rehearse provider switching and public-operator replacement, including pending invoices, usable records and continuity. Neither a competitive market on paper nor a public procurement contract establishes practical replaceability.

The northern lesson is not “copy Scandinavia.” It is that standards, markets and public responsibility can be allocated deliberately. Slovakia should preserve a competitive provider ecosystem while testing whether a direct public baseline can prevent compulsory compliance from becoming a compulsory separate commercial relationship, even where a tariff is free. That is a design question worthy of evidence, not a question Peppol answers automatically.

The cited sources establish particular access arrangements: Finnish government invoicing, a Swedish agency’s supplier portal, a Norwegian provider list and a historical Danish profile. They do not establish comparative total costs, security, recovery performance or universal Slovak B2B access. Those outcomes remain to be measured for both designs. A business with a foreign customer should obtain that customer’s instructions rather than treat this comparison as a compliance route.