Finvoice
Finvoice is a publicly available Finnish electronic invoicing standard published by Finnish banks. The forwarding service is built around the Finvoice message format, and current documentation identifies Finvoice 3.0 as the current schema. A Finvoice XML file still needs the applicable validation, recipient address, intermediary, and delivery arrangement; readable XML alone does not establish successful delivery or compliance.
Why this matters when you invoice
Finvoice is both a structured data format and part of a forwarding ecosystem. A technically readable invoice still needs the correct recipient address, intermediary details, validation and delivery arrangement to reach the intended receiver.
Where it appears
Finvoice appears in Finnish bank and operator e-invoicing services, accounting software exports, invoice-address instructions, and validation guidance.
Format and routing are separate
A supplier has a Finvoice XML file and the customer's Business ID. Before delivery, the supplier still needs the customer's e-invoice address and intermediary and must follow the validation and forwarding process required by its operator. The Business ID alone is not the routing address.
Common mistakes
- Assuming any XML invoice is Finvoice.
- Using the Business ID as though it were the e-invoice address.
- Treating a file that opens successfully as proof of operator acceptance.
View supported Finvoice XML
Use the XML viewer to inspect supported fields in a Finvoice document before the separate validation and delivery steps.
InvoiceCraftly can display supported Finvoice XML in its viewer, but it does not certify Finvoice compliance or send the invoice through a Finnish operator.
Official references
Sources and terminology reviewed 5 September 2026. Next evidence review: 4 December 2026.
Frequently asked questions
What is the current Finvoice schema?
Finance Finland's current documentation identifies Finvoice 3.0 as the current schema.
Can InvoiceCraftly send a Finvoice through a Finnish operator?
No. The XML viewer can display supported Finvoice XML; operator delivery and formal validation remain separate steps.