{"id":29355,"date":"2026-09-11T07:00:01","date_gmt":"2026-09-11T07:00:01","guid":{"rendered":"https:\/\/bilnex.io\/en\/finland-e-invoice-law-2019\/"},"modified":"2026-09-11T07:00:01","modified_gmt":"2026-09-11T07:00:01","slug":"finland-e-invoice-law-2019","status":"publish","type":"page","link":"https:\/\/bilnex.io\/en\/finland-e-invoice-law-2019\/","title":{"rendered":"Finland 241\/2019: When Buyers Can Demand E-Invoices"},"content":{"rendered":"
\n
\n
\n

Finland’s Act 241\/2019<\/a> doesn’t automatically turn every invoice sent to a Finnish company into an e-invoice. But since 1 April 2020, a contracting authority (hankintayksikk\u00f6, meaning a public-sector buyer under Finnish procurement law) or a business owner (elinkeinonharjoittaja) whose annual turnover exceeds \u20ac10,000 has the right to require that another party in that same category send an invoice as a proper European-standard e-invoice<\/a>. In practice, that means this: if your Finnish client, whether a company, a municipality, or a state body, chooses to use this right, emailing a PDF invoice no longer meets the request. You need to be able to issue a technically correct e-invoice instead. If the client doesn’t ask, your existing routine keeps working exactly as before.<\/p>\n

Who has the right to demand an e-invoice, and when does it apply?<\/h2>\n

The rule is simpler than it first sounds. Since 1 April 2020<\/a>, a contracting authority or a business owner can ask another contracting authority or business owner to send an invoice specifically as an e-invoice. This is a right to request, not an automatic obligation. An invoice doesn’t become an e-invoice on its own. It only becomes one when the other party specifically asks for it.<\/p>\n

The law isn’t unlimited, though. If using an e-invoice would expose confidential information or threaten Finland’s essential security interests, the right to demand one doesn’t apply. That exception mainly concerns security and defence procurement, not ordinary B2B sales.<\/p>\n

Who can demand it, and from whom?<\/h2>\n

Two categories the law defines<\/h3>\n

The act deals with two types of parties: contracting authorities (hankintayksikk\u00f6) and business owners (elinkeinonharjoittaja). A contracting authority, in the sense Finnish procurement law uses the term, is a public-sector entity: a ministry, a municipality, a state agency, or another body subject to procurement rules. A business owner, meanwhile, is anyone carrying out business or professional activity whose turnover for the financial year exceeds \u20ac10,000<\/a>. Turnover sitting exactly at that line doesn’t count yet. The threshold has to be exceeded, not just reached.<\/p>\n

Where the law stops: consumers<\/h3>\n

It’s worth being clear about what the law does not<\/em> cover: ordinary consumers. If you sell goods or services to a private individual, that customer has no basis under this act to demand an e-invoice. Valtiokonttori (the Finnish State Treasury) explains<\/a> that consumers generally receive invoices through their own online banking rather than as a structured e-invoice. Act 241\/2019 governs invoicing between organisations and with the public sector only, not consumer billing.<\/p>\n

Why is the public sector a tougher case?<\/h2>\n

What this means if you sell to the public sector<\/h3>\n

In practice, if you sell to a Finnish city, a local authority, or a ministry, that buyer has already been required to accept and process e-invoices for some time, regardless of whether they specifically ask you for one. Valtiokonttori confirms<\/a> that this obligation sits inside a broader push to automate invoicing between the public and private sectors.<\/p>\n

Is a PDF invoice sent by email an e-invoice?<\/h2>\n

This is the most common misunderstanding. A verkkolasku (the Finnish term for e-invoice) is a structured, machine-readable document that flows directly into accounting software or online banking, not an image a person reads on a screen. Valtiokonttori states this plainly<\/a>: a PDF or image-format invoice attached to an email is not a verkkolasku, no matter how correct it looks.<\/p>\n

The technical backbone of a legally valid e-invoice is the European e-invoicing standard EN 16931-1:2017<\/a>, published by the European Commission together with a list of permitted message formats (referred to as “syntaxes”). In practice, there are two main formats: UN\/CEFACT Cross Industry Invoice and UBL. In Finland, the formats most commonly used are Finvoice 3.0 and TEAPPSXML 3.0, but these only meet the European standard if the required data fields are filled in correctly. The format alone doesn’t guarantee compliance.<\/p>\n

What should you do if a client asks for an e-invoice?<\/h2>\n

Once a Finnish client tells you they want invoices only as e-invoices, manual work is on its way out. The only question is how fast you can get there.<\/p>\n