Kivra moves to OmaPosti

What is happening

Posti has acquired Kivra’s digital post business in Finland, and Posti’s OmaPosti takes over as the digital mailbox Maventa delivers to. Posti stops routing anything to Kivra after 31st of October 2026, and Kivra’s service closes for consumers on 1st of December 2026, when the app is removed and Finnish Kivra accounts shut down.

Maventa changes its routing ahead of both of those dates. From 15th of October 2026, Maventa delivers digital post to OmaPosti. Kivra still works as a fallback for the rest of that month: a consumer who has a Kivra account but has not activated OmaPosti can keep receiving invoices and letters there until Posti’s deadline. Consumers can read whatever is already in their Kivra inbox until the service closes.

Nothing breaks on the switchover date. Maventa and Posti handle the connection between them, your existing sending calls keep working, the routing order stays the same, and a digital post delivery costs what it did before.

Two things are worth acting on, though. One sending parameter is renamed, and if you currently force consumer invoices straight to print, you have to allow the digital route explicitly before OmaPosti can be used at all. Both are covered below.

This page describes the change in full. The same parameters and fields are also documented in context in Consumer Invoicing (Finland) and the Mass Printing Service.

Check that your invoices can reach OmaPosti

Maventa looks up OmaPosti for a consumer invoice only when that invoice is allowed to take a digital route. If your integration sends consumer invoices straight to print, Maventa’s lookup never runs. The invoice can then reach OmaPosti only through the print service provider’s lookup. That path is not reported back to you, it is billed as a printed letter, and it disappears on 1st of March 2027.

To use OmaPosti properly, do one of the following:

Either way, the invoice is checked against OmaPosti before it goes anywhere near print, so a consumer with an OmaPosti account receives it digitally. That is faster for them, and a consumer who has activated OmaPosti has chosen to receive their invoices and letters there rather than by email or on paper. See two routes to a consumer’s OmaPosti for how the two paths differ.

Keeping the e-invoice route in use is also worth doing for what is coming. On its own it changes little today. Finnish consumer e-invoicing still rests on an agreement per consumer, and Maventa sends an e-invoice only when the invoice carries the consumer’s full e-invoice address, so an invoice that has the address never needs the fallback chain in the first place.

That is starting to shift. Consumer invoicing in Finland is moving towards opt-in-once models, where a consumer agrees to receive e-invoices generally instead of choosing each sender separately. Nordea’s Siirto already works this way: a consumer who has activated it can receive an e-invoice from a company without having chosen that company as a sender beforehand, because the e-invoicing address can be retrieved from Siirto.

Maventa is adding support for Siirto, currently expected late in 2026 or early in 2027. The Siirto lookup will run as part of the e-invoice route, so that route has to be in use for the lookup to happen at all. Keeping it in use means your consumer invoices start using Siirto as soon as Maventa supports it, with no further work on your side. An integration that forces consumer invoices to print will not reach Siirto either.

What changes in your integration

Three names change when your digital post traffic moves to OmaPosti, at the latest on 15th of October 2026. They affect names and values only, not behaviour. Only one of them can force a code change: if your integration compares delivery_method to the string kivra, it needs widening.

You do not need these parameters for an invoice to reach OmaPosti. They are not available everywhere. The SOAP API has no allow_digital_post or prevent_digital_post, and the older IPOSTXML-based mass printing method has no letter_subject or extra recipient lookup fields. Delivery to OmaPosti still happens in both cases, because the routing decision belongs to Maventa. What the parameters add is explicit control: allowing digital post where it would otherwise be skipped, or switching it off for a particular invoice or letter.

Each change in detail

The digital post parameter gets a provider-neutral name

The parameter no longer names a provider, because what it actually says is that the invoice may go to a consumer’s digital mailbox in Finland. Which company runs that mailbox is Maventa’s routing responsibility, and the new name survives the next time the answer changes. In Finland, digital post currently goes to Posti’s OmaPosti.

The old name keeps working. allow_kivra_fi behaves exactly as before and routes the invoice to OmaPosti. There is no deadline and nothing you have to do. Maventa recommends moving to the new name when it suits your release schedule, since that is the name the documentation uses from now on.

The mass printing status response reports a new delivery method

GET /file_status/{uuid}/details returns letters[].delivery_method for every letter in a batch. A digital post delivery used to report kivra and now reports omaposti.

Both values can turn up in the same batch while the switchover is in progress.

The billing action is renamed

The price is identical. Only the name changes, and a single billing period can contain both actions while the switchover is in progress.

What stays the same

Payment reminders and collection demands

You can keep sending payment reminders and collection demands through the same integration, and OmaPosti receives them as digital post. Sending does not change, and digital collection still requires the sender’s consent.

What does change is how the consumer sees them. Kivra showed reminders and collection demands as document types of their own. OmaPosti initially shows them as invoices: they appear in your sender folder and in the Invoices section, the payment functions work, and the consumer is notified about an incoming invoice rather than an incoming reminder or collection demand.

Posti is building a dedicated document type for collection demands. The schedule is not settled yet, and Maventa will announce it separately once Posti confirms it.

Two routes to a consumer’s OmaPosti

From 15th of October 2026, an invoice or letter can reach a consumer’s OmaPosti in two ways. They are not equivalent, and Maventa is consolidating them into one.

  Maventa’s direct connection The print service provider’s lookup
When the lookup happens Before the invoice or letter reaches the print service provider Just before printing
Treated as An electronic route Part of the print route
Reported to the sender Yes No. You cannot tell whether the item reached OmaPosti or was printed and posted
Billed as A digital delivery (EINVOICE_OMAPOSTI_FI) A printed letter, considerably more expensive
Available Ongoing As a fallback until 1st of March 2027

On 1st of March 2027, the print service provider’s lookup goes away and Maventa’s direct connection becomes the only route to OmaPosti. That is worth moving to before the deadline: the delivery is reported back to you, you pay the digital post price rather than the letter price, and there is one predictable way an item reaches OmaPosti instead of two.

An invoice or letter takes the OmaPosti route when one of the following is true:

Otherwise the sending keeps going through the print service provider’s lookup for as long as that fallback exists.

Both routes are described in full in Printing (Finland) for invoices and in the Mass Printing Service for letters.

Timeline

Date What happens
September to 15th of October 2026 Maventa moves digital post traffic from Kivra to OmaPosti
By 15th of October 2026 allow_digital_post, the omaposti delivery method and the billing action EINVOICE_OMAPOSTI_FI are all in use. allow_kivra_fi still works
15th of October 2026 Maventa delivers digital post to OmaPosti, with Kivra still available as a fallback
31st of October 2026 Posti’s deadline. After this date nothing is routed to Kivra
1st of December 2026 Kivra’s service closes for consumers, the app is removed and Kivra accounts in Finland shut down
1st of March 2027 The print service provider’s OmaPosti lookup is removed, leaving Maventa’s direct connection as the only route

Between 15th and 31st of October 2026, a message still goes to Kivra if the recipient has a Kivra account but cannot be found in OmaPosti. Either way it reaches the consumer digitally, and you do not need to do anything about it.

Consumers have to activate OmaPosti themselves

Kivra users are not migrated to OmaPosti. Posti does not create OmaPosti accounts on their behalf, and documents sitting in a Kivra inbox are not copied across.

For a sender, this has a practical consequence. Kivra covers the gap for the rest of October, but from November 2026 onwards a consumer who has not activated OmaPosti has no digital mailbox at all. When the lookup finds no account, the invoice or letter carries on to the next available route, usually email or print, which is slower and costs more than a digital delivery.

15th of October 2026 is the date that matters for consumers. Anyone who activates OmaPosti by then receives digital post there from the moment Maventa switches over, with no gap.

Posti contacts Kivra users directly, but a reminder that comes from the company whose invoices they receive tends to carry more weight. It is worth making sure that message reaches them, whether it comes from you or from the companies sending invoices through your software.

What consumers need to do

Posti’s customer service answers consumer questions in the OmaPosti app chat or on 0100 5577.

A good moment to review your mass printing integration

If you still send letters with the older IPOSTXML-based method, this is a sensible time to move to the JSON API (POST /input_json). It gives the most reliable digital post delivery, because the recipient details travel with the call, and it prepares the integration for the removal of the print service provider’s lookup in March 2027.

Sub-processor

Posti Jakelu Oy acts as a sub-processor for the consumer digital mailbox in Finland from 15th of October 2026. It processes recipient contact and identification details (name, address, email address, phone number and, where needed, national identification number) along with the content of invoices and letters. Processing takes place in the EU/EEA.

Maventa keeps an up-to-date list of all its sub-processors in Visma’s Trust Centre.

Questions?

Maventa’s support team is happy to help with anything about this change.