Skip to content
  • There are no suggestions because the search field is empty.

Consumer invoicing

This support article explains how to manage consumer e-invoicing and direct payments through Maventa using automated biller (SI) and receiver (RI) messages. It provides step-by-step instructions for setting up the service, transferring invoicing rights seamlessly during a property manager change, and troubleshooting common technical error messages related to bank account mismatches, formatting, and delivery timing.

 

General information about consumer invoicing

Through Maventa, consumer invoices can be delivered as e-invoices or direct payments directly to online banking, by email, or via a printing service.

Activating consumer e-invoicing requires the biller to send a separate notification (SI message) to the banks. The SI message informs consumers of the possibility to receive e-invoices from the biller in question. After this, the consumer can express their willingness to receive e-invoices by using the biller's receiver notification (RI message).

The biller can send three types of SI messages:

  • ADD message: Addition of a biller notification.
  • CHANGE message: Modification of a biller notification.
  • DELETE message: Deletion of a biller notification.

The biller can also send a receiver proposal (RP message) to the consumer when the biller wishes to propose switching to consumer e-invoicing.

 

Consumer E-Invoicing process

This process enables Finnish companies to send consumer e-invoices to personal online banks, as well as direct payments to consumers who do not use online banking services. Using the service requires a Finnish Business ID (y-tunnus) and a domestic bank account.

  1. SI messages are created and sent from the biller's ERP to Maventa. SI messages can also be sent directly from the Maventa user interface. The biller must send one separate SI message to each bank. If the messages are sent from the Maventa user interface using data generated by the Federation of Finnish Financial Services (FKL) tool, Maventa automatically splits the messages for the respective banks without the need to separate the data manually per bank.
  2. Maventa forwards the SI messages to the operator bank (DABAFIHH).
  3. The operator bank forwards the SI messages to each destination bank.
  4. The banks receive the SI messages and store the information that the biller is ready to send consumer e-invoices via Maventa. After this, the biller can be searched for in the biller registry within the online bank. If a bank does not accept the SI message, it returns an error message, which is transferred to Maventa and can be downloaded into the software or directly from the user interface.
  5. An agreement on consumer e-invoicing is established between the biller and the consumer when the consumer notifies the bank that they wish to receive consumer e-invoices from the biller in question and provides the identification reference requested in the SI message (e.g., a reference number).
  6. The bank sends an RI message (notification of the consumer's willingness to receive e-invoices) to the operator bank.
  7. The operator bank forwards the RI message to Maventa.
  8. The biller's ERP downloads the incoming RI messages from Maventa and saves the consumers' information into the customer registry. RI messages can also be found in the user interface.
  9. The biller can now send consumer e-invoices to the consumer in question.


Step-by-Step start of consumer invoicing

Biller notifications (SI messages: ADD/CHANGE/DELETE) are sent via Maventa, and response messages (RI messages) are received from consumers. Once the required notifications have been processed, the invoice can be sent directly to the consumer's online bank.

Prerequisites and implementation steps

  1. The company must be registered with Maventa.
  2. The banking network connection must be active.
  3. Generate the ADD messages.
  4. Send the biller messages from Maventa.

After these steps, the consumer can make a receiver notification in their own online bank. Once the receiver notification is completed, a response message (RI) arrives in Maventa, displaying the consumers who have adopted the service. These response messages are downloaded into the invoicing system to serve as the basis for invoice data. Once the invoice data is generated, it is sent from the invoicing software to the consumer's online bank.

How to send messages via Maventa:

Once the banking network connection is activated for the company's account, select B2C Messages from the top menu. Detailed sending instructions can be found in a separate support article: Instructions for sending a biller notification.

Reviewing sent SI Messages and response messages:

Sent SI messages can be viewed under the Sent messages section, and RI messages under the Received messages section. If there is an error in the SI messages, banks will return an error message within 4 banking days. Under the Error messages section, you can view and download these error files, which indicate the cause of the error.

  • "Sent messages": Displays the identifier, creation time, and download link for sent SI messages. The status SENT indicates that the message went through to the banks, while the status ERROR indicates that it failed with an error.
  • "Received messages": Displays the RI messages created by consumers.
  • "Error messages": Displays SI messages rejected and returned as errors by the banks. Downloading the error message reveals which bank returned the error and provides a more detailed reason for the failure.

 

Instructions for sending biller notifications

Biller notifications (Add, Change, Delete) can be generated using the FKL biller notification tool and sent from the Maventa user interface. The program compiles notifications destined for different banks into a single summary file. Maventa automatically splits this file by bank during transmission.

Every biller notification begins with the SOAP frame <SOAP-ENV:Envelope> and ends with the </FinvoiceSenderInfo> tag.

Technical requirements for message transmission:

  • The sender address must always be an EDI/OVT identifier starting with 0037.
  • The routing bank DABAFIHH is used as the operator code (intermediary).
  • The message must contain a unique MessageId value (notification identifier).
  • Messages are transferred from the intermediary bank to the destination banks within 1–4 business days. Banks do not send a separate confirmation for successful delivery, but in case of a failure, the SI message is set to an error state. Potential error situations regarding agreements may only become visible a week after transmission.

Transmission steps in the user interface

  1. Log in to the Maventa account.
  2. Select B2C Messages > Send (this menu is only visible if the banking network connection is active).
  3. Select the desired message and click Send.

⚠️ If the system returns the error Duplicate messageID, the message is being sent with an already existing MessageId identifier. The identifier must be unique and must be changed in the data before attempting a new transmission. Successful transmissions are displayed under Sent messages.


Message types

The biller notification informs consumers about the availability of e-invoicing. Consumer invoicing is based on the biller notification and the receiver notification. Biller notifications are sent to all banks offering e-invoice services so that the payer can order an e-invoice in their online bank. This order generates a receiver notification, which the biller retrieves as a file. This operation requires an agreement between the company and its own bank regarding the transmission of e-invoices and direct payments.

The biller notification is generated programmatically. If no proprietary software is available, the FKL tool is used.

Message type Description and use case
ADD (Addition of biller notification) Used when a company starts consumer e-invoicing or offers a new invoicing topic.
CHANGE (Modification of biller notification) Used when the details of an active notification (e.g., account number, address, or intermediary) change.
DELETE (Deletion of biller notification) Used when consumer e-invoicing or a specific invoicing topic is discontinued completely.
RP (Receiver Proposal) The biller proposes switching to e-invoices by asking for the consumer's e-invoice address before sending the invoice. Visible in the consumer's online bank for 30 days.


Fields of the invoicer notification (SI message) 

You can create a new biller notification, modify an existing one, or delete a biller notification on the FKL website: https://laskuttajailmoitus.finanssiala.fi/. Below are the field definitions found in the Federation of Finnish Financial Services tool. Note that this tool is not a service provided by Maventa.

Specifications of fields in the Financial Sector's Tool

Download example SI message

 

Select banks: The banks to which the new biller notification will be sent:

  • Aktia (HELSFIHH)
  • Danske Bank (DABAFIHH)
  • Nordea (NDEAFIHH)
  • OP Ryhmä (OKOYFIHH)
  • POP pankit ja Bonum Pankki (POPFFI22)
  • S-Pankki (SBANFIHH)
  • Säästöpankit (ITELFIHH)
  • Ålandsbanken (AABAFI22)
 
Notification identifier
A unique identifier (1–48 characters) for the biller’s internal use (e.g., message ID in the system).
 
 
 

Biller details:

  • E-invoice address (In modification notifications, the previous/current e-invoice address is used)
  • Intermediary ID (In modification notifications, the previous/current intermediary ID is used)
  • Biller Business ID (y-tunnus)
  • Biller name: Length 2–70 characters, must be provided in at least one language (Finnish/Swedish/English).
  • Street address
  • Postal address
  • Country code and name: The country's ISO code (Finland is FI) and name.
  • Organizational unit: The biller's full EDI/OVT identifier (in the format 0037...).
  • Website description: Text used when displaying the biller's website address (for example, Federation of Finnish Financial Services FKL).
  • Website URL: The biller's website address (for example, www.finanssiala.fi).


Services offered by the biller

  • E-invoice
  • E-invoice and direct payment
  • E-invoice and direct payment, no new direct payments (The biller only offers the e-invoice option to new customers, and new direct payment mandates cannot be made. However, the biller can still use direct payment for consumers who have previously made a mandate or whose mandate entered into force before the direct debit migration).


Invoice details section:

  • Invoicing topic code: A unique identification code defined by the biller. Transmitted in the payment instruction part (ePI) of the Finvoice e-invoice under the EpiPaymentInstructionId element. The code must match the information provided in the invoice message to enable automatic payment.
  • Invoicing topic name: Plain text matching the code (e.g., Electricity bill or Phone bill), based on which the consumer selects the correct topic in their online bank. Must be provided in all three languages (Finnish, Swedish, English).
  • Instructions for the receiver: Additional information on switching to e-invoicing in three languages (e.g., No paper invoices will be sent after the e-invoice notification. / Efter att vi har mottagit meddelandet kommer vi inte att skicka pappersfakturor / No paper invoices will be sent after the e-invoice notification.).


Payer identification details 1: Identification info (4–70 characters) used by the biller to match the address notification with the correct customer and invoice (e.g., Reference number, Customer number, Agreement number, Order number, or Phone number). Must be provided in all three languages.

  • Data type: The online bank may support formal validation of the identification data based on the selected type. Validation rules can specify the length (1–35) and whether spaces and hyphens are permitted. Length rules must either both be specified or neither.


Payer identification details 2: Identification info (4–70 characters) that the biller requests the recipient to fill in so the biller can match the incoming address notification with the correct customer and invoice. Examples: Reference number, Customer number, Agreement number, Order number, and Phone number. Identification details must be provided in all three languages so that the consumer using the online bank can view the info in their preferred service language.

  • Payer may propose a due date: Select this if you wish to allow it.
    Payer may propose a billing period: Select this if you wish to allow it.

💡 Requirements and data types correspond to the Payer identification details 1 field.


Biller's bank account details:

  • IBAN account number: The biller's account number in IBAN format. All account numbers appearing on paper invoices must be included in the biller notification. The consumer will only receive an e-invoice subscription prompt if the account number used has been declared in this biller notification. A new account is added using the "Add account" button. When account details change, all account numbers (both modified and unmodified) must always be sent in the modification notification. Space for new account information can be made by selecting "Account has changed", which also enables the "Transfer account" button to shift previously declared modification details to replace the removed ones.
  • Account bank BIC: The bank's BIC code.

 

 

Instructions for creating invoicer notifications when the property Manager/Accounting firm changes

      This operating model applies to situations where the property manager changes, but the residents' e-invoice addresses and direct payment mandates remain unchanged. If the housing company also changes its bank and/or e-invoice operator in connection with this, remember that the modification messages must be sent through the old bank.

      1. Housing company details do not change

      The old property manager provides the original biller notification details to the new property manager:

      • E-invoice address
      • E-invoice operator
      • Invoicing topic code
      • Maintenance fee account(s) used

      The old property manager should be requested to remove the housing company's e-invoice services from their agency's agreement only after the new property manager has made their own agreement with the bank and received the necessary biller notification details as well as the e-invoice addresses of the company's residents. This ensures uninterrupted collection of maintenance fees.

      2. Housing company details change

      2.1 Necessary modifications to the biller notification

      A modification notification (CHANGE message) must be sent to the banks if any of the following information changes:

      • The housing company’s e-invoice address and/or intermediary bank.
      • The housing company’s name.
      • The housing company’s account number.
      • The housing company’s address details.
      • The invoicing topic name (e.g., Maintenance fee, rent, utility charge, or housing payments).
      • The e-invoice or direct payment service is to be discontinued.

      📌 The active invoicing topic code of a housing company cannot be changed.

      2.2 Tasks of the old property manager or accounting agency before handover

      Modifications to the biller notification must be sent from the e-invoice address and through the e-invoice intermediary from which the active biller notification was originally sent. The old property management agency sends a CHANGE message to transfer the active biller notification to the new property manager, stating the new intermediary bank and, if necessary, the new e-invoice address.

      The service must not be terminated before the new property manager has received the information and the rights to manage the notification. The residents' e-invoice addresses, intermediary details, and billing methods must be delivered to the new property manager.

      ⚠️ Sending a biller notification deletion (DELETE message) terminates all active e-invoice and direct payment subscriptions, forcing residents to make receiver notifications and direct payment mandates all over again.

      2.3 Tasks of the new property manager or accounting agency

      Following the transfer, the new property management agency can make other necessary changes (such as updating account numbers) by sending a new modification notification containing the details of the active notification. The housing company’s account number must be provided as both old and new information (even if it does not change) when sending a CHANGE message.


      Error messages for consumer invoices


      Delivery failed: "EpiDateOptionDate ei ole sallitussa aikavälissä" 

      • Reason: The due date of the invoice has already passed or is too close.
      • Solution: Leave at least four banking days between the transmission of the invoice and its due date.


      Delivery failed: "Osoitetiedot SOAP -kehyksellä ja MessageTransmissionDetails -elementissä eivät täsmää"

      • Reason: The system rejects the invoice if the information in the SOAP frame does not match the information in the MessageTransmissionDetails field that immediately follows it. This error is usually caused by having the company's Business ID instead of the EDI/OVT identifier in the MessageTransmissionDetails section while the SOAP frame uses the EDI/OVT identifier.
      • Solution: Change the company identifier in your financial management software to the company's EDI/OVT identifier (format 0037...) and send the invoice again.
       
      Delivery failed: "Vastaanottajalla ei ole voimassaolevaa vastaanottoilmoitusta (e-lasku tai suoramaksu)"
       

      • Reason: The consumer customer is missing a receiver notification (RI message) or they have cancelled the agreement, meaning no valid consumer agreement exists.


      Delivery failed: "No senderinfo match EpiPaymentInstructionId and creditor acc"

      • Reason: The account details of the biller notification (SI message) and the sender of the consumer invoice do not match. The account number in the ePI part of the invoice must be one of the account numbers declared in the biller notification.
      • Solution: Ensure that the exact same account number is found on the consumer invoice. If you want to change the bank account, a new CHANGE-type SI message must be sent with the new account number.


      E      rror messages for invoicer notifications and follow-up actions


      Laskuttajailmoitus on jo olemassa / SAMOILLA TUNNISTETIEDOILLA LÖYTYY JO LASKUTTAJAILMOITUS

      • Reason: A biller notification with the same details already exists in the bank in question. The same biller can only send multiple notifications if they have a unique invoicing topic code.
      • Action: The notification does not need to be resent to that bank. If you want to send another biller notification for a different service, it must be sent with a different invoicing topic code.


      Laskuttajailmoitusta ei voida kohdistaa

      • Reason: The sent CHANGE or DELETE message cannot be targeted by the bank because the notification to be modified cannot be found, or the message residing at the bank contains different details (e.g., a different invoicing topic code).
      • Action: If the notification to be modified cannot be found, send a new ADD message to that bank. If the modification notification contained incorrect information, correct the details and resend the message.


      Muutettavaa laskuttajailmoitusta ei löydy

      • Reason: The sent CHANGE message cannot be targeted by the bank because the biller notification to be modified does not exist.
      • Action: Send an ADD message instead of a CHANGE message to that bank.


      Poistettavaa laskuttajailmoitusta ei löydy

      • Reason: The notification to be deleted cannot be found at the bank, or the message residing at the bank contains different details (e.g., a different invoicing topic code).
      • Action: A DELETE message does not need to be sent to that bank. If there was erroneous information in the message, correct the details and resend it. 


      Creditor not found

      • Action: Resend the biller notification. If the error recurs and resending does not help, please contact our customer support for further investigation.


      ERROR: DUPLICATE MESSAGEID

      • Reason: The notification has already been sent once with the same MessageId identifier (<eb:MessageId>). The identifier must be unique for every transmission attempt (applies to ADD, CHANGE, and DELETE messages).
      • Action: Fix the MessageId element (the notification identifier) in the data and resend the biller notification.


      Mitättömiä merkkejä SellerInstructionFreeText tiedossa

      • Reason: A character set issue where, for example, the letter "ä" has turned into a special character. This is typically caused by copying text from another source that uses a different character encoding.
      • Action: Resend the notification to the banks for which the notification returned an error. Type the details manually into the biller notification to avoid the error. If you wish to correct text in banks where it appears incorrectly, a CHANGE modification notification is sent with manually entered data.


      ERROR: MESSAGE PARTYID DOES NOT MATCH COMPANY OVT

      • Reason: The EDI/OVT identifier in the biller notification does not match the e-invoice address in Maventa. An e-invoice address in IBAN format cannot be used in the notification.
      • Action: Ensure that the biller notification uses the sending company's e-invoice address in the format 0037 + Business ID and that the value DABAFIHH is used as the operator identifier. Example of the correct format:

      <eb:From><eb:PartyId>003712345678</eb:PartyId><eb:Role>Sender</eb:Role></eb:From><eb:From><eb:PartyId>DABAFIHH</eb:PartyId><eb:Role>Intermediator</eb:Role></eb:From>


      Muu virhe: Tarkista ja korjaa SellerInstructionFreeText elementti

      • Reason: This error typically occurs in SI messages sent to Nordea, as Nordea requires the SellerInstructionFreeText element as mandatory. The system returns an error if the element is missing.
      • Action: Add the element to the data in three languages, for example:
        • Anna viimeisimmän laskun viitenumero.
        • Ge den senaste fakturans referensnummer.
        • Enter the reference number.


      Palvelusopimus puuttuu

      • Reason: This error occurs if the invoice is intended as a B2C invoice but has been interpreted as a B2B invoice based on the data and routed to the wrong channel. The error can also be caused by an invoicing topic code that does not match. The invoicing topic element is mandatory on all B2C consumer invoices.
      • Action: Check and correct the invoicing topic element in the data and resend the invoice from the invoicing software. If the problem persists, please contact our customer support if necessary.


      Terminating or transferring consumer invoicing

      Deletions and modifications of biller notifications are primarily done within the invoicing software. These instructions advise on how to terminate a biller notification on a Maventa account or transfer it to another intermediary using DELETE and CHANGE messages.

      Terminating a biller notification:

      1. Generate and send DELETE-type SI messages to the banks using the FKL tool to remove the biller notification.
      2. Ensure that the deletion messages contain exactly the same details as your active notification, especially the PaymentInstructionIdentifier code. The code can be verified under Consumer Invoicing > Sent messages.
      3. Note that after biller notifications are terminated, consumers must re-subscribe to any potential new e-invoices through their own online bank.

      Transferring a biller notification:

      1. Create CHANGE messages using the FKL tool to transfer the notification to the new intermediary.
      2. Define the new intermediary's e-invoice address and operator code in the CHANGE message.
      3. Open the bank connection to the new intermediary before sending the messages.
      4. Save incoming e-invoice subscriptions received on the Maventa account to a local computer. During the transfer, the transmission of e-invoices can continue without interruption through the new routing bank.

      Processing of notifications at banks:

      • Wait 5 business days after sending the messages before terminating the Maventa account.
      • If a bank returns an error, correct the erroneous message and resend it.
       

       

      Useful Links

      General Guidelines and Links to Finvoice Messages

      https://www.finanssiala.fi/aiheet/verkkolaskutus-finvoice/#/

       

      Comprehensive Document on All Message Types

      https://file.finanssiala.fi/finvoice/Ilmoittamispalvelun_soveltamisohje_201.pdf

       

      Biller Notification Creation 2.0 (TOOL)

      https://laskuttajailmoitus.finanssiala.fi/

       

      Biller Notification Creation Program, Instructions

      https://file.finanssiala.fi/finvoice/Laskuttajailmoituksen_teko-ohjelma_ohje.pdf

       

       

      Guidance on Maintaining E-Invoicing When Changing Property Managers

      https://file.finanssiala.fi/finvoice/ohje_e-laskutuksen_sailymisesta.pdf