{"id":29473,"date":"2026-09-19T11:00:01","date_gmt":"2026-09-19T11:00:01","guid":{"rendered":"https:\/\/bilnex.io\/en\/e-lasku-vs-verkkolasku-2\/"},"modified":"2026-09-19T11:00:04","modified_gmt":"2026-09-19T11:00:04","slug":"e-lasku-vs-verkkolasku-2","status":"publish","type":"page","link":"https:\/\/bilnex.io\/fi\/e-lasku-vs-verkkolasku-2\/","title":{"rendered":"E-kuva vai nettikuva? Suomalaisen laskun ero"},"content":{"rendered":"
\n
\n
\n

Short answer: the difference is the recipient, not the file format<\/h2>\n

In Finnish business language, these two words are separated by who receives the invoice, not by technology. E-lasku<\/strong> normally means an invoice that arrives in a private person’s online bank. Verkkolasku<\/strong> means a machine-readable invoice moving between companies and the public sector, landing straight in the recipient’s accounting software. The State Treasury of Finland (Valtiokonttori) defines a verkkolasku<\/a> as an invoice in machine-readable, that is structured, form, sent directly into accounting software or into an online bank. A PDF or image invoice sent as an email attachment is not a verkkolasku. So if a Finnish customer asks for a verkkolasku, ask them for their verkkolaskuosoite (e-invoice address) and their operator identifier. The rest is plumbing.<\/p>\n

\n

Key facts<\/strong><\/p>\n\n\n\n\n\n\n\n\n\n\n
Fact<\/th>\nValue<\/th>\nValid from<\/th>\nSource<\/th>\n<\/tr>\n<\/thead>\n
Definition of a verkkolasku<\/td>\nAn invoice in machine-readable, structured form sent straight into accounting software or an online bank; a PDF or image invoice sent as an email attachment is not a verkkolasku<\/td>\nas of September 2026<\/td>\nvaltiokonttori.fi<\/a><\/td>\n<\/tr>\n
Right to demand an EN-standard e-invoice (Act 241\/2019)<\/td>\nA contracting authority and a qualifying business may require a structured e-invoice; the provision has applied since 1 April 2020 (the act entered into force on 1 April 2019)<\/td>\n1 April 2020<\/td>\nfinlex.fi<\/a><\/td>\n<\/tr>\n
The \u20ac10,000 figure in Act 241\/2019<\/td>\nNot an invoice amount and not a VAT threshold \u2014 it belongs to the definition of a business and is based on financial-year turnover above \u20ac10,000<\/td>\n1 April 2019<\/td>\nfinlex.fi<\/a><\/td>\n<\/tr>\n
Scope of Finvoice 3.0<\/td>\nThe XML-based format is suitable for invoicing between companies of every size and for consumer invoicing; the implementation guide’s last dated change is 16 September 2025<\/td>\n16 September 2025<\/td>\nfile.finanssiala.fi<\/a><\/td>\n<\/tr>\n
Tax Administration’s verkkolasku to a company<\/td>\nSent about three weeks before the due date; can be used to pay real estate tax and prepayments and back taxes<\/td>\npage updated 26 January 2026<\/td>\nvero.fi<\/a><\/td>\n<\/tr>\n
ViDA cross-border digital reporting<\/td>\nMember States adopt the measures by 30 June 2030 at the latest and apply them from 1 July 2030; invoices for the covered cross-border transactions must be issued within 10 days of the chargeable event<\/td>\n1 July 2030<\/td>\neur-lex.europa.eu<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

The Finnish Tax Administration puts it from the other side: it describes a verkkolasku as “e-laskun kaltainen”<\/a>, an invoice similar to an e-lasku, but meant for companies and associations, while private persons get the e-lasku. Technically, both can travel in the same Finvoice format.<\/p>\n\n\n\n\n\n\n\n\n\n\n
<\/th>\ne-lasku<\/th>\nverkkolasku<\/th>\n<\/tr>\n<\/thead>\n
Typical recipient<\/td>\nprivate person<\/td>\ncompany, association, public sector<\/td>\n<\/tr>\n
Where the invoice ends up<\/td>\nonline bank or another payment service<\/td>\npurchase invoice handling and archiving software, also the online bank<\/td>\n<\/tr>\n
Machine-readable<\/td>\nyes (e.g. Finvoice)<\/td>\nyes (e.g. Finvoice 3.0, TEAPPSXML 3.0)<\/td>\n<\/tr>\n
What must exist first<\/td>\nthe recipient’s agreement in their bank to receive invoices<\/td>\na contract with an operator and a verkkolaskuosoite<\/td>\n<\/tr>\n
What Finnish law touches<\/td>\nnot the focus of the verkkolasku act<\/td>\npublic procurement obligation and the right to demand a structured invoice<\/td>\n<\/tr>\n
Practical point<\/td>\nconvenient payment<\/td>\nautomating the whole purchase invoice process<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The same technical invoice can be both<\/h2>\n

This is where most explanations go wrong. An e-lasku is not an “unstructured consumer PDF”, and a verkkolasku is not some other file type. Finvoice 3.0 is an XML-based Finnish e-invoice format, and its implementation guide says plainly that the format suits invoicing between companies of every size as well as consumer invoicing<\/a>. The same guide defines a consumer e-lasku as a Finvoice invoice that the consumer receives in an online bank or another payment web service. The guide is a living document: its last dated change is 16 September 2025, when it was added that a credit note amount may also be zero.<\/p>\n

One misunderstanding is worth pulling out by the root \u2014 an invoice in Finvoice 3.0 format is not automatically compliant with the European e-invoicing standard EN 16931 (the EU norm that defines what data a structured invoice must carry). The State Treasury stresses that both Finvoice 3.0 and TEAPPSXML 3.0 can be used to produce standard-compliant invoices, but it does not happen by itself<\/a>. The responsibility sits with the sender, and some operators check compliance before passing the invoice on.<\/p>\n

What does the recipient actually do with your invoice?<\/h2>\n

Think through two scenarios with the same \u20ac1,200 invoice to a Finnish customer.<\/p>\n

If the customer is a company<\/h3>\n

The invoice travels through an operator into their purchase invoice system. From there it goes on an approval round, into the accounts, and into the archive. The State Treasury names one concrete benefit: the recipient can lift the reference number and the account number straight into the payment<\/a>, so less time goes into sorting out payments. Your \u20ac1,200 doesn’t sit in someone’s inbox waiting for a person to retype the numbers.<\/p>\n

If the customer is a private person<\/h3>\n

Here the logic is different. The invoice arrives in the online bank for payment and that’s where their work ends. Writing about a project on one-off consumer invoicing, the State Treasury notes that with the solutions available on the market an e-lasku could not be sent directly to a consumer, because the consumer must first make an agreement in their bank with the invoice sender to receive invoices<\/a>. For a one-off sale to a private person, the e-lasku is therefore not a channel you can just start using.<\/p>\n

In the Finvoice transmission service both sides need a contract with their own service provider: the seller sends the invoice through their operator, and the buyer either imports it into their system or views it in a browser.<\/p>\n

A PDF sent by email is not a verkkolasku<\/h2>\n

This is the most common misunderstanding between an Estonian seller and a Finnish buyer. A PDF invoice can be a perfectly correct invoice document: all the required details in place, VAT calculated correctly. It is still not a verkkolasku. The State Treasury’s page states it without conditions: s\u00e4hk\u00f6postin liitteen\u00e4 l\u00e4hetett\u00e4v\u00e4t pdf- tai kuvamuotoiset laskut eiv\u00e4t ole verkkolaskuja, meaning invoices sent as a PDF or image email attachment are not verkkolaskus. A picture of an invoice gives the buyer no automation at all. Someone still has to type the data in.<\/p>\n

So when a Finnish customer says “l\u00e4het\u00e4 verkkolasku” and you email a PDF, their request has not been met \u2014 in a larger organisation, the invoice may simply come back.<\/p>\n

When does Finnish law give the right to demand a structured invoice?<\/h2>\n

The Finnish verkkolasku act is Act 241\/2019 on the electronic invoicing of contracting entities and businesses<\/a>. Three things in it are worth keeping apart.<\/p>\n

First, the act defines an electronic invoice as an invoice that has been issued, transmitted and received in a structured electronic format allowing automatic processing, and that complies with the European e-invoicing standard and the listed syntaxes. A scanned image does not fit that definition.<\/p>\n

Second, in public procurement falling within the scope of the procurement acts, Finnish contracting entities must receive and process e-invoices that meet the EN standard. That is an obligation on the buyer’s side.<\/p>\n

Third, a contracting entity and a business meeting the conditions have the right to require that an invoice be presented in structured electronic form. The act entered into force on 1 April 2019, and the provision granting that right has applied since 1 April 2020. The \u20ac10,000 figure appearing in this act is neither an invoice amount nor a VAT threshold. It belongs to the definition of a business and is based on financial-year turnover above \u20ac10,000.<\/p>\n

What the act does not do<\/h3>\n

It does not turn every domestic Finnish business-to-business invoice into a mandatory verkkolasku. None of the sources cited here sets out, as of 15 September 2026, a nationwide B2B obligation or a separate per-invoice fine. In practice, a large share of buyers requires a structured invoice by contract, not by law.<\/p>\n

Do this when a Finnish customer asks for a verkkolasku<\/h2>\n

The State Treasury’s advice is simple: before sending, make sure the buyer receives e-invoices at all, and get their exact invoicing details. After that your operator takes care of the invoice arriving in the technically correct shape. In practice it goes like this:<\/p>\n