{"id":29232,"date":"2026-08-26T07:00:01","date_gmt":"2026-08-26T07:00:01","guid":{"rendered":"https:\/\/bilnex.io\/en\/e-invoicing-finland-2026\/"},"modified":"2026-08-26T07:00:01","modified_gmt":"2026-08-26T07:00:01","slug":"sahkoinen-laskutus-suomessa-2027","status":"publish","type":"page","link":"https:\/\/bilnex.io\/fi\/sahkoinen-laskutus-suomessa-2027\/","title":{"rendered":"Verkkolaskutus Suomessa 2026: S\u00e4\u00e4nn\u00f6t, rajoitukset ja PDF-ansa"},"content":{"rendered":"
\n
\n
\n

Short answer: is e-invoicing mandatory in Finland?<\/h2>\n

For the public sector, the answer is clear-cut: Finnish government agencies and central purchasing bodies have had to accept and process e-invoices meeting the European standard since 1 April 2019<\/a>, with other public buyers following from 1 April 2020<\/a>. B2B sales work differently. From that same 1 April 2020<\/a> date, any buyer, and any supplier with turnover above \u20ac10,000, gained the right to demand an e-invoice instead of a paper or PDF one. That’s a right to request, not a blanket obligation on every Finnish small business. It doesn’t extend to invoices sent to private individuals, as Vero confirms<\/a>. As of 25 August 2026, Finland still has no confirmed general domestic B2B e-invoicing mandate. What exists is a demand right, not automatic enforcement.<\/p>\n

Don’t confuse them: the \u20ac10,000 e-invoice threshold and the \u20ac20,000 VAT threshold<\/h2>\n

These two numbers live in two different laws, and mixing them up is an easy mistake to make. The \u20ac10,000 threshold<\/a> in the e-invoicing act is measured against your company’s turnover for the financial year. The \u20ac20,000 threshold<\/a> for mandatory VAT registration, by contrast, is measured by calendar year, and you have to watch both the current and the preceding calendar year. That means it’s entirely possible for your business to be VAT-exempt while already being legally entitled to both request and send e-invoices.<\/p>\n

Why a PDF attached to an email isn’t a Finnish e-invoice<\/h2>\n

Valtiokonttori, Finland’s state treasury office, says it plainly<\/a>: a PDF or image file sent as an email attachment is not an e-invoice. A genuine e-invoice is machine-readable structured data (figures and fields a computer can read directly rather than a scanned picture of them) that flows straight into accounting or banking software and follows the European standard EN 16931, the shared data format e-invoicing systems across Europe have to support. Finland’s VAT act uses a broader term, “electronic invoice,” and a PDF does technically satisfy that. But that doesn’t make it an e-invoice under the e-invoicing act.<\/p>\n

How do you send your first e-invoice to a Finnish customer?<\/h2>\n

Before you send anything, look up the customer’s business ID, EDI e-invoice address and operator identifier<\/a> (EDI here just means the electronic address format e-invoicing networks use to route a file to the right inbox) in the verkkolaskuosoite.fi registry. Larger organizations often have more than one address listed, so make sure you’ve got the right one for the department you’re billing. Then build the invoice in software that supports the EN 16931 standard, and let your operator (the network that carries e-invoices between sender and receiver, much like how mobile carriers connect calls across different networks) deliver it in the correct format.<\/p>\n

Free portal, accounting software, or an operator?<\/h2>\n

For a one-off invoice, a free portal<\/a> offered by the customer is usually enough: you type the details in once and send. For regular B2B billing, it’s worth connecting your accounting or invoicing software directly to an e-invoice operator instead. If your software doesn’t already have that connection built in, you’ll need to sign a separate agreement with an operator yourself.<\/p>\n

VAT details and the mistakes that get invoices rejected<\/h2>\n

Say you’re billing a Finnish company \u20ac1,200 for services. That invoice must legally include the invoice number, issue date, seller’s VAT number, the taxable amount broken down by VAT rate, and the VAT amount<\/a>, and, where reverse charge applies (meaning the buyer rather than the seller accounts for the VAT), a note saying so. Getting these details wrong isn’t just a formatting headache: careless non-compliance can bring a fine of up to \u20ac5,000<\/a>.<\/p>\n

What should you prepare for cross-border e-invoicing in 2030?<\/h2>\n

The ViDA directive<\/a> (VAT in the Digital Age, the EU’s overhaul of digital VAT reporting) sets a firm date: from 1 July 2030, intra-EU goods deliveries under Article 138 and reverse-charge transactions under Articles 194\u2013197 must be invoiced within 10 days of the taxable event, and invoices for transactions subject to reporting obligations must be issued as e-invoices. If you sell into other EU member states, it’s worth choosing EN 16931-compatible software now rather than waiting for Finland’s more detailed national implementation decision.<\/p>\n

FAQ<\/h2>\n

Kas e-arve on Soomes kohustuslik?<\/h3>\n

Avaliku sektori jaoks on e-arve kohustuslik alates 2019\/2020. B2B-m\u00fc\u00fcgis ei ole \u00fcldkohustust, kuid hankijal ja \u00fcle 10 000 euro k\u00e4ibega ettev\u00f5tjal on n\u00f5ude\u00f5igus alates 1. aprillist 2020. Eraisikule see \u00f5igus ei laiene.<\/p>\n

Mis vahe on 10 000\u20ac e-arve piiril ja 20 000\u20ac k\u00e4ibemaksupiiril?<\/h3>\n

E-arve seaduse 10 000\u20ac piir arvestatakse majandusaasta k\u00e4ibest, k\u00e4ibemaksukohustuslase 20 000\u20ac piir aga kalendriaasta kaupa. Ettev\u00f5te v\u00f5ib olla k\u00e4ibemaksuvaba, kuid samas omada e-arve n\u00f5ude\u00f5igust.<\/p>\n

Miks PDF ei ole e-arve?<\/h3>\n

E-kirja manusena saadetud PDF v\u00f5i pildifail ei ole e-arve, sest e-arve on masinloetav struktureeritud andmestik, mis j\u00e4rgib Euroopa standardit EN 16931 ja liigub otse raamatupidamistarkvarasse.<\/p>\n