Regional spotlight
Formats? Mandates?
We've got you covered!
-
Overview of B2G, B2B and B2C e-invoicing in Finland. -
Key formats, networks and channels you may need to support. -
High-level regulatory and compliance considerations.
e-invoicing in Finland
When registering a new Finnish company via the API, the VAT number or organisation number (y-tunnus) must be used as the company identifier. Visma Sign supports Finnish customer authentication using either HETU, Finnish banks and mobile identifier.
For B2B and B2G, sending in Finland is currently supported in the following priority order: through Maventa’s internal network, then through Finnish operator network or Finnish bank network and finally through the Peppol network. Email and print delivery are also available as fallback options.
If you want to send to Peppol for a Finnish recipients, you need to give the full Peppol id with scheme id. If you only give recipient’s bid it won’t never ever try Peppol (example: 0126:003712345678)
For consumers (B2C) we support e-invoicing to banks, Kivra and fallbacks as email and print. Also through our print service provider, we support OmaPosti sending.
SOAP MessageTransmissionDetails Buyer API parameters
- OVT code - The OVT code is the unique part of a company’s e-invoicing address that ensures invoices are delivered to the correct recipient when sending through the Finnish operator or bank network.
The second part of the e-invoicing address is the operator code, which defines through which service provider (operator) the invoice is transmitted. Maventa’s operator code is 003721291126 for the operator network. When sending invoices through the Finnish bank network to a Maventa customer, the sender should use DABAFIHH as the operator code, since Maventa’s main bank connection is with Danske Bank. However, if the sender uses OP or Nordea, Maventa’s own operator code (003721291126) can also be used.
An OVT identifier is created by combining the Finnish Tax Administration’s prefix 0037 with the company’s Business ID (Y-tunnus) — written without the hyphen (8 digits) — and, if necessary, an optional suffix of up to 5 characters (called osastolaajennos). In total, the OVT code length is typically 12–17 characters.
You can search for companies’ OVT identifiers in the public Finnish e-invoice address directory hosted by Tieke.
- Peppol id -
The following example PDF is generated when invoice is sent in Finnish market, and the XML is in Finvoice 3.0 format. FIX_EXAMPLE_PENDING Download as PDF
The following example PDF is generated when invoice is sent in other markets, and the XML is in Finvoice 3.0 format. FIX_EXAMPLE_PENDING Download as PDF
Example Finvoice 3.0 XML of above visualisations: FIX_EXAMPLE_PENDING
Finnish market example has <SpecificationDetails> -element given (<SpecificationFreeText> tags). That element has different font and styling. The font is Courier (all the characters are equally wide). The purpose of using this font type in this case is to keep the formatted text as it is given in the XML.
Example usage of <SpecificationDetails> -element and how it would look like in the PDF
<SpecificationDetails>
<SpecificationFreeText>LASKUN VAPAAMUOTOISET ERITTELYTIEDOT:</SpecificationFreeText>
<SpecificationFreeText>Sarake-1 Sarake-2 Sarake-3</SpecificationFreeText>
<SpecificationFreeText>---------------------------------------------------------------------------------------------------</SpecificationFreeText>
<SpecificationFreeText>1.sarakkeen tieto 2.sarakkeen tieto 10,00</SpecificationFreeText>
<SpecificationFreeText>Toinen rivi Toinen rivi 1 000,00</SpecificationFreeText>
<SpecificationFreeText>Kolmas rivi 3/2 1,00</SpecificationFreeText>
<SpecificationFreeText>Muotoituja tietoja voidaan käyttää mm.tarkemman erittelyn esittämiseen:</SpecificationFreeText>
</SpecificationDetails>FIX_IMAGE_PENDING
The following example PDF is generated when invoice is sent in Finnish market, and the XML is in TEAPPSXML 3.0 format. FIX_EXAMPLE_PENDING Download as PDF
The following example PDF is generated when invoice is sent in other markets, and the XML is in TEAPPSXML 3.0 format. FIX_EXAMPLE_PENDING Download as PDF
FIX_EXAMPLE_PENDING