# E-Invoicing in Finland

Key formats, routing options, and a practical checklist for sending compliant e-invoices in Finland.

## What matters in practice

This Finland guide explains Finvoice, TEAPPSXML, PEPPOL BIS, and the operator and reference checks that most often decide whether the invoice is accepted on the first try.

## Common e-invoice formats

- Finvoice
- TEAPPSXML
- PEPPOL BIS 3.0 (UBL)

## Routing & delivery

- [PEPPOL](https://peppol.eu/): Network

## Common identifiers

- Business ID (Y-tunnus)
- VAT ID

## Mandate & scope

Finland uses several structured invoice syntaxes, including Finvoice, TEAPPSXML, and PEPPOL BIS, depending on the recipient and service operator.

## Country-specific operating notes for Finland

- The Finnish state only receives e-invoices, and since April 1, 2021 it receives only invoices that comply with the European standard.
- Finvoice 3.0 and TEAPPSXML 3.0 are common Finnish formats for EN 16931-compatible invoices; Peppol is also available for government delivery.
- Email attachments are not accepted as e-invoices, so verify the operator address, OVT/EDI identifiers, and required order or contract reference before sending.

## Quick checklist

- The recipient or operator usually determines which syntax is acceptable for delivery.
- Business ID (Y-tunnus), VAT ID, and bank/payment references should match the parties’ master data.
- Format selection matters: correct invoice data in the wrong syntax can still be rejected.

## How to send (practical steps)

1. Confirm with the recipient or operator whether Finvoice, TEAPPSXML, or PEPPOL BIS is required.
2. Prepare the invoice data with the correct business identifiers, payment details, and references.
3. Validate the file against the selected syntax and code lists before sending.
4. Submit through the agreed channel and keep the transmission receipt or operator acknowledgement.

## Validation & compliance

- Make sure the chosen syntax matches the recipient’s operator setup.
- Check totals, VAT codes, bank details, and payment references for consistency.
- Validate identifiers and invoice references exactly as provided by the recipient.

## Common pitfalls

- Sending correct business data in the wrong syntax for the recipient.
- Mismatch between Business ID, VAT ID, and supplier master data.
- Missing routing or operator-specific reference details.

## Frequently asked questions

### Which invoice format is most common in Finland?
Finvoice, TEAPPSXML, and PEPPOL BIS are all used, with the recipient or service operator deciding which syntax is accepted.

### What should I verify before sending a Finnish invoice?
Check the Business ID, VAT ID, payment references, and the recipient’s operator setup before sending.

## Official links

- [OpenPeppol](https://peppol.eu/)

## Related resources

- [PEPPOL Network Guide](/resources/compliance/peppol-network-guide)
- [UBL (Universal Business Language)](/resources/compliance/ubl-universal-business-language)
- [DIN EN 16931-1 Standard](/resources/compliance/din-en-16931-1-standard)