Skip to main content

​
Introduction

Finland has no government clearance system: e-invoices travel through accredited operators, and every sender and receiver works through an operator account. The Finland app’s registration provisions each of your Finnish parties its own account with Invopop’s operator partner, activates its services, and allocates its e-invoice address. A party must be registered before it can send or receive anything; there is no shared account to work through. A workspace can hold several Finnish parties, each registered and polled on its own. Once a supplier is registered, continue with the companion guide: Finvoice issuing invoices.

​
Prerequisites

  • The party’s details: legal name, Business ID (y-tunnus, e.g. 2617416-4), and a Finnish address. The Business ID is uploaded without its hyphen as the GOBL tax_id.code.
  • Reception workflows configured: registration checks that the Finland app has a sync and an import workflow configured, and fails with “reception not configured” otherwise. Follow the receiving guide’s setup first.

​
E-invoice addresses

A Finnish e-invoice address is an OVT code: 0037 followed by the Business ID without its hyphen, sometimes with a five-character suffix for routing inside large organisations. For example, the Business ID 2617416-4 gives the OVT code 003726174164. On Peppol, the same code is wrapped in scheme 0216. Registration allocates the party’s address on the operator’s side, so you don’t need to provide one. Counterparties will ask for it, though, and you’ll need your customers’ addresses to send. Look any Finnish organisation up in the national registry at verkkolaskuosoite.fi: since 2024 it mirrors the Peppol address list too, so one lookup covers both networks. You may also meet other address forms that circulate on the Finnish network: IBAN-style addresses from the older bank channel, and operator-prefixed ones such as TE0037…. On party records, always use the OVT code under scheme 0216.

​
Setup

All of the following steps must be carried out from the Invopop Console.
1

Connect the Finland app

  1. Navigate to Configuration → Apps
  2. Find Finland in the app discovery list
  3. Click Connect to activate
2

Set up reception

Registration requires the reception workflows to be configured first, because a registered party’s inbox starts being polled right away. Create the sync and import workflows and configure them on the app as described in the receiving guide, then come back here.
3

Create the registration workflow

​
Register a supplier

1

Upload the party

Create a silo entry with the party’s details. The example below shows the fields a Finnish party carries; for registration, the name and the y-tunnus are what matter:
Finland supplier example
2

Run the registration workflow

Run the registration workflow on the party’s silo entry, from the Console or via the API.
3

Wait for the registration to complete

Registration finds or creates the party’s company under Invopop’s partner account at the operator, activates its services, and waits until the operator reports every service in force and the party’s e-invoice address allocated. Until then the job stays queued rather than reporting success on an account that can’t yet receive.
Once registration completes, the party can send and receive e-invoices, and its inbox at the operator starts being polled automatically.
The party’s e-invoice address works from the moment registration completes, but the national registry counterparties look addresses up in is refreshed once a night. Expect the party to become findable there the following day.
There is no self-serve deregistration yet. To offboard a party, contact support@invopop.com.
At this point, you’re ready to start sending invoices on behalf of the supplier. Head over to the Finvoice issuing invoices guide to continue.

​
FAQ

Upload the supplier as a GOBL party with tax_id.country = FI and the Business ID (y-tunnus), then run the Finland app’s registration workflow. Registration provisions the party its own operator account and allocates its e-invoice address — a party must be registered before it can send or receive anything. See the supplier registration guide.
Scheme 0216, wrapping the party’s OVT code — 0037 followed by the Business ID without its hyphen. Under Finland’s Peppol Authority Specific Requirements, the OVT code is the mandatory participant identifier for Finnish organisations on Peppol. The 0037 at the start of the code itself is a country prefix, not the scheme.
An OVT code: 0037 followed by the party’s Business ID (y-tunnus) without its hyphen, sometimes with a five-character suffix for routing inside large organisations (for example 003726174164). On Peppol, the same code is wrapped in scheme 0216 (0216:003726174164). You can look any counterparty up in the national registry at verkkolaskuosoite.fi: since 2024 it mirrors the Peppol address list too, so one lookup covers both networks.
The OVT code, as an inbox with scheme 0216. Other forms circulate on the Finnish network (IBAN-style addresses from the older bank channel, operator-prefixed ones such as TE0037…), but the OVT code is the canonical form, and it’s what the routing pre-check and the generated e-invoice use.
Registration provisions the party its own account with the operator, and it only completes once every service is in force and the party’s e-invoice address has been allocated on the operator’s side. Until then the registration job stays queued rather than reporting success on an account that can’t yet receive.
Yes. Each party gets its own operator account, its own e-invoice address, and its own reception polling schedule. Register each one separately by running the registration workflow on its party record.
More available in our Finland FAQ section

Participate in our community

Ask and answer questions about invoicing in Finland →