Search
Maventa services and reach Finland e-invoicing in Finland Mass Printing Service Sweden e-invoicing in Sweden Norway e-invoicing in Norway Denmark e-invoicing in Denmark Netherlands e-invoicing in the Netherlands Belgium e-invoicing in Belgium Germany e-invoicing in Germany Estonia e-invoicing in Estonia Latvia e-invoicing in Latvia Poland e-invoicing in Poland Italy e-invoicing in Italy France e-invoicing in France Spain e-invoicing in Spain
Finland

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.

Read the Regional spotlight

e-invoicing in Finland

Finland is one of the most mature e-invoicing markets in Europe, with widespread adoption across both the public and private sectors. E-invoicing is mandatory for suppliers to the Finnish public sector (EU Directive 2014/55/EU), and B2B e-invoicing is broadly adopted through the Finnish operator and bank networks. The upcoming EU ViDA (VAT in the Digital Age) regulation is expected to further shape the regulatory landscape.

Maventa supports the full range of Finnish e-invoicing needs — from B2B and B2G invoice delivery through operator and bank networks, to consumer invoicing via netbanks and digital mailboxes, to receivables management and fraud detection. Maventa is a member of the Verkkolaskufoorumi, a collaborative forum of e-invoice operators, banks, and software vendors that develops Finnish e-invoicing infrastructure and standards. The forum is coordinated by TIEKE and has been advancing digital financial management in Finland since 2002.

Finnish company account

When registering a new Finnish company via the API, the company’s VAT number or organisation number (y-tunnus) must be used as the identifier. Visma Sign supports Finnish customer authentication using HETU, Finnish banks, or mobile identifier.

Identifier Description Format Validation
Y-tunnus Finnish Business ID (organisation number) 1234567-8 Structural validation with check digit
VAT number Finnish VAT identifier FI12345678 Structural validation via VIES

Sending in Finland

Delivery channels and routing order

For B2B and B2G invoices, Maventa attempts delivery in the following priority order:

  1. Maventa’s internal network — direct delivery between Maventa customers
  2. Finnish operator network — delivery via operators in the Verkkolaskufoorumi network
  3. Finnish bank network — delivery via Finvoice through banks (the bank network connection is activated automatically when the company account is created and authorized)
  4. Peppol network — delivery to Peppol-registered recipients (requires the full Peppol endpoint ID, see below)
  5. Email — PDF invoice with a virtual barcode in the email body
  6. Print — physical delivery via Maventa’s Finnish print service, with automatic OmaPosti redirect when available

Bank network attachment limitation (B2B)

When invoices are delivered through the Finnish bank network, the invoice image and attachments cannot be transmitted directly as separate files. Instead, Maventa automatically adds a link to the invoice display service in the XML file, where recipients can view the image and download attachments.

For B2B invoices, this is a non-secure (public) link. How the link is displayed to the recipient depends on the bank — there may be differences in how each bank presents the link in its online banking interface. For B2C consumer invoices, the link is secure. See the consumer invoicing (Finland) guide for more details.

Recipient identifiers and address resolution

Finnish invoices can be routed using different identifiers depending on the delivery channel. Maventa does not automatically add a Peppol scheme prefix to a plain Finnish Business ID — if only the BID is provided, the invoice is delivered through the operator or bank network.

Identifier type Format Example Delivery channel
OVT code + operator code 0037 + BID (no hyphen) 003712345678 + 003721291126 Operator and bank networks
Peppol endpoint ID 0216: + OVT code 0216:003712345678 Peppol network
Plain Business ID Y-tunnus 1234567-8 Operator and bank networks (Peppol is not attempted)

To route an invoice via Peppol, the full endpoint ID with scheme 0216 must be included in the invoice XML. For operator and bank network delivery, the OVT code and operator code are sufficient.

For details on how OVT codes are constructed and which operator codes to use, see the OVT codes section under Receiving.

To find a Finnish company’s e-invoice address before sending, use the Verkkolaskuosoitteisto — the national e-invoice address directory maintained by Finnish e-invoice operators and banks. The directory is free to search and lets you verify whether a company can receive e-invoices, and through which operator or bank.

Consumer invoicing (B2C)

For consumer invoices, Maventa supports e-invoicing to Finnish netbanks, Kivra digital mailbox, and OmaPosti digital postal service. Email and print are available as fallback options.

Consumer e-invoicing in Finland uses a bank messaging protocol with SI-messages (Sender Info), RI-messages (Receiver Info), and RP-messages (Receiver Proposal) to manage e-invoice agreements between the sender and the consumer’s bank. Eight major Finnish banks support this protocol.

For full details on the bank messaging protocol, supported banks, Kivra and OmaPosti integration, and B2C-specific requirements, see the consumer invoicing (Finland) guide.

Receiving in Finland

Companies can receive invoices through several channels once e-invoice receiving is activated. Incoming invoices arrive via Maventa’s internal network, the Finnish operator network, and the Finnish bank network. If the company is also registered with Peppol, Peppol receiving is available as well. Companies can also receive scanned invoices via Scan Network, with AutoScan expected to become available in spring 2026.

Receiving addresses for Finnish companies

Address type Description Example Activation
OVT code Finnish e-invoicing address for operator and bank networks 003712345678 Created automatically when e-invoice receiving is activated
Peppol address Identifier for the Peppol network, using scheme 0216 (OVT) 0216:003712345678 Created when the company registers to receive from Peppol

OVT codes

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.

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.

The second part of the e-invoicing address is the operator code, which defines through which service provider (operator) the invoice is transmitted.

Network Operator code When to use
Finnish operator network 003721291126 Default Maventa operator code
Finnish bank network (Danske Bank) DABAFIHH Recommended when sender uses the bank network, since Maventa’s main bank connection is with Danske Bank
Finnish bank network (OP or Nordea) 003721291126 Maventa’s own operator code can also be used when the sender connects through OP or Nordea

You can search for companies’ OVT identifiers and operator codes in the Verkkolaskuosoitteisto, the national e-invoice address directory. The directory is maintained collectively by Finnish e-invoice operators and banks, and is free to search. Companies can also register and update their own e-invoice address information in the directory at no charge.

Peppol registration

The Peppol identifier for Finnish companies uses scheme 0216, which corresponds to the OVT identifier. The Peppol address is formed as 0216: followed by the OVT code (for example 0216:003712345678). When a company registers as a Peppol receiver through Maventa, the company becomes visible in the Peppol Directory.

For more details on Peppol registration and capabilities, see the Peppol network documentation.

Scanning

Scan Network is available as a scanning solution in Finland. AutoScan is expected to become available in H1 2026.

For Scan Network, invoices can be sent to the company’s scan email address in the format invoice-BID@kollektor.fi, where BID is the company’s Business ID without the hyphen (for example invoice-12345678@kollektor.fi). Paper invoices can also be sent by post to: Company name, Scan ID, PL 100, 80020 Kollektor.

Fraud detection

Maventa’s Detect service is available in Finland. When activated, Detect automatically checks all incoming invoices for potential fraud, including VAT register verification, Business ID validation against YTJ, warning list cross-referencing, and bank account change detection.

For step-by-step instructions on enabling receiving, registering for Peppol, and setting up scanning or fraud detection, see the invoice receiving integration guide.

Accounts receivable services

Maventa offers several accounts receivable and debt collection services in Finland, all delivered as part of the Maventa service with no separate usage fee. For full details on each service, including activation, API integration, assignments, and events, see the Accounts receivable section in the Integration Guide.

Available services for Finnish companies:

Additional services

Mass printing service

The Mass Printing Service (Payslip) allows sending PDF files as physical letters through the Finnish printing service. While originally designed for distributing payslips, it can be used for any type of letter. This service is separate from invoice print delivery and is available only for Finnish companies.

Email invoicing

When invoices are delivered via email for Finnish recipients, a virtual barcode is included in the email body. The email language defaults to Finnish when using Finvoice format, and both Finnish (FI) and Swedish (SV) are supported.

Local e-invoicing formats

Finland supports several invoice formats. For integrations that require consumer invoicing (B2C), use Finvoice 3.0 or TEAPPSXML 3.0 as they support the bank messaging protocol required for Finnish consumer e-invoicing. For more details, see the invoicing formats guide.

Format Standard B2C support Notes
Peppol BIS Billing 3.0 EN16931 No Recommended for cross-border and Peppol delivery
Finvoice 3.0 EN16931 Yes Finnish national format, required for bank network B2C
TEAPPSXML 3.0 EN16931 Yes Alternative Finnish format with B2C support

A Finvoice 3.0 & TEAPPSXML 3.0 mapping document is available for reference when converting between the two formats.

Invoice image and attachments

If no invoice image (PDF) is included with the invoice, Maventa automatically generates one from the XML data. Maventa uses two different templates depending on the sender’s country. The Finnish market template is used when the sender is a Finnish company, while the other markets template is used when the sender is from another country.

The Finnish market template includes a payment reference barcode on the last page. The example PDFs below do not include the barcode, but it will appear once valid payment data (IBAN and reference number) is provided in the invoice XML.

For Finvoice and TEAPPSXML formats, attachments are included in a ZIP package alongside the XML file. The XML and the invoice image PDF must share the same filename (for example 12345.xml and 12345.pdf). Other attachments do not need to match the XML filename. For TEAPPSXML, attachments must also be referenced inside the XML file. For more details on attachment handling, see the invoice sending guide.

Example of auto-generated invoice image (Finland)

Finvoice 3.0

Examples of auto-generated invoice images for Finvoice 3.0:

For details on Finvoice-specific features such as discount and charge handling, credit notes, and recipient resolution, see the Finvoice 3.0 format guide.

Finvoice supports a <SpecificationDetails> element that allows free-form specification text on the invoice. This element is rendered in a monospace font (Courier) to preserve column alignment and formatted text exactly as provided in the XML.

<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>
</SpecificationDetails>

TEAPPSXML 3.0

Examples of auto-generated invoice images for TEAPPSXML 3.0:

Back to top

AI Chat Support 24/7

  • Get help via AI chat available 24/7 whenever it suits you
  • Chat extensively uses Maventa support pages, websites, and blogs in its answers
  • If you need assistance that the AI cannot provide, you can also ask a customer service agent to join the conversation
  • Support requests processed Monday to Friday
Cancel Open chat

Got feedback?

Did you not find what you were looking for? Or was something explained unclearly? Or just want to share your thoughts? We are happy to hear your feedback!

Note: This form is not a way to get support, this is only for feedback for the documentation website. If you need support, please contact Maventa support.

Integration Guide Services & Reach API Specification Changelogs Integration guide Getting Started Invoice sending Consumer Invoicing Printing Email invoicing Invoice receiving Scanning Detect Fraud reporting Webhooks Reference implementations Maventa Connector Embeddable User Interface Peppol Network Document Exchange Invoice Response Self-billing support Invoicing formats Validation Peppol BIS 3.0 Finvoice 3.0 Document types and type codes Maventa JSON (table) Maventa JSON (json schema) Companies and Settings Department Company Users Billing Accounts receivable Ropo Reminder & Collection Amili Kassavirta Amili Perintä Services and reach Maventa services and reach e-invoicing in Finland Mass Printing Service e-invoicing in Sweden e-invoicing in Norway e-invoicing in Denmark e-invoicing in the Netherlands e-invoicing in Belgium e-invoicing in Germany e-invoicing in Estonia e-invoicing in Latvia e-invoicing in Poland e-invoicing in Italy e-invoicing in France e-invoicing in Spain Api specification API overview Getting Started Common & authentication API Invoices API Documents API Companies & settings API Lookups API Detect API Validator API Receivables API Billing API Scanning API B2CFI API B2CNO API B2CSE API Partner API Getting Started API Methods Overview Account Configuration API Methods Invoice Sending API Methods Invoice Receiving API Methods B2C Norway API Methods B2C Finland API Methods Other API Methods Changelogs Product changelog Developer Changelog
Clear Send

Enter your credentials to Maventa testing environment, to authenticate and try things out with the Swagger UI. This will fetch a Bearer token using OAuth2 with the endpoint POST https://ax-stage.maventa.com/oauth2/token. The token is stored in your browser's session storage (cleared when you close the tab) and used in Swagger calls done from this documentation website. The token is valid for 1 hour.

Never use your production credentials here. This is only for testing the Maventa test environment in the Swagger UI.
Reset All None
eui global company lookup document:receive document:send invoice:receive invoice:send company:read company:write validate receivables:assignments analysis billing:reports partner:invoice_delivery_actions partner:lookups partner:takeovers partner:lyanthe_scan_service fi_bank_message:send fi_bank_message:receive
Cancel Sign In