Skip to main content

​
Introduction

In Finland, e-invoices travel through accredited operators without government clearance. Registering a party in the Finland app creates its own account with Invopop’s operator partner and activates its services. A Finnish party also gets its own e-invoice address. Suppliers outside Finland can register too, to send only. See suppliers outside Finland. Registration includes one step no one in the flow can do for the supplier: their representative must sign an authorization agreement and verify their identity before the party is registered. The registration workflow publishes a signing link you share with them, and continues automatically once the signed authorization is approved. A party must be registered before it can send documents. A workspace can hold several parties, each registered on its own.

​
Prerequisites

  • The party’s details: legal name, Business ID (y-tunnus, e.g. 2617416-4), and an address. The Business ID is uploaded without its hyphen as the GOBL tax_id.code. For a supplier outside Finland, use its own country’s tax ID (see suppliers outside Finland).
  • A representative on the party: the first entry in the party’s people list, with a name and a role in the company. The signing wizard prefills this person as the signer.
  • The representative’s availability: someone authorized to sign on the supplier’s behalf has to complete the signing step, with their identity document at hand, before registration can finish.
  • Reception workflows configured: registration checks that the Finland app has a sync and an import workflow configured, and fails with “reception not configured” otherwise. Suppliers outside Finland don’t receive through this app, so the check doesn’t apply to them.
Registering a Finnish party will fail if a sync and import workflow is not configured.
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 a Finnish party’s address on the operator’s side: it is the party’s own OVT code, the same one you set as the 0216 inbox on the supplier party. Counterparties will ask for it, and in Finland an e-invoice address is quoted as a pair, the address plus the operator that serves it. Give them both: your OVT code and Invopop’s operator, Apix Messaging, operator ID 003723327487. You’ll also 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 a Finnish party, always use the OVT code under scheme 0216.

​
Suppliers outside Finland

Companies from any other country can register here to invoice Finnish receivers. Most Finnish businesses receive their e-invoices on the domestic operator network, which the Peppol app can’t reach. Use the company’s own tax ID on the party. The operator registers the company under that tax ID. For most countries this is the full VAT number. For Sweden and Norway it is the Org.nr on its own, because their VAT numbers are built from it. Sending works as it does for a Finnish supplier, with the same workflow, checks and formats. Give the party an inbox with the company’s own electronic address, such as a Swedish Org.nr under scheme 0007. Suppliers outside Finland are registered to send only. A Finnish e-invoice address is built from a Finnish Business ID, so they don’t get one. They aren’t listed in the national registry, and Finnish senders can’t reach them on the domestic network. The app doesn’t poll an inbox for them, and the authorization agreement their representative signs covers sending only. To receive invoices too, register the company in the Peppol app. Finnish senders who invoice abroad can reach it there.

​
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 (Finnish parties only)

Registering a Finnish party requires the reception workflows to be configured first, because its 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. If you only register suppliers outside Finland, skip this step.
3

Create the registration workflow

Finvoice register party workflow

Add to my workspace →

​
Register a supplier

1

Upload the party

Create a silo entry with the party’s details. Registration uses the name, the tax ID and the representative under people. The example below shows a Finnish party, with its y-tunnus as the tax ID:
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. The workflow publishes the signing link and pauses at the Wait for Finland agreement approval step until the signed authorization is approved.
3

Share the signing link

The workflow adds a public signing link to the party’s silo entry. Open the party in the Console to copy it, and send it to the supplier’s representative.
4

Have the representative sign

The link opens a short hosted wizard: the representative confirms their name and role (prefilled from the party’s people entry), uploads a photo of their identity document, reviews the authorization agreement, and signs it — typing their name or drawing a signature that is stamped onto the document.When the identity check passes, the authorization is approved on the spot. Otherwise it goes to Invopop’s team for review, and the representative sees the outcome on the same page.
In sandbox workspaces the identity check is skipped: any image is accepted and the authorization is approved as soon as it is signed.
5

Wait for the registration to complete

As soon as the authorization is approved, the workflow resumes on its own. Registration finds or creates the party’s company under Invopop’s partner account at the operator and activates its services. The job stays queued until the operator reports every service in force.For a Finnish party, registration also waits until the operator has allocated its e-invoice address, so the job never reports success on an account that can’t receive yet. A supplier outside Finland gets no address, so its registration completes as soon as its sending service is active.
Once registration completes, a Finnish party can send and receive e-invoices, and its inbox at the operator starts being polled automatically. A supplier outside Finland can start sending.
A Finnish 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.

​
Sign the agreement via the API

Integrators building their own onboarding UI can drive the signing step without the hosted wizard. The Finland app exposes three endpoints on its service, authenticated per enrollment. All three read the signer from the party entry, so the first person in the party’s people list must carry a name and a role before they are called.

​
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.
For a Finnish party, the OVT code, as an inbox with scheme 0216. A supplier outside Finland uses its own electronic address, such as a Swedish Org.nr under scheme 0007. Other forms circulate on the Finnish network (IBAN-style addresses from the older bank channel, operator-prefixed ones such as TE0037…), but for a Finnish party the OVT code is the canonical form, and the one the routing pre-check and the generated e-invoice use.
Registration provisions the party its own account with the operator, and the job stays queued until every service is in force. For a Finnish party, it also waits until the operator has allocated its e-invoice address, so it never reports success on an account that can’t receive yet. A supplier outside Finland only sends, so its registration completes as soon as its sending service is active.
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 →