Sales invoice error notifications
If a sent sales invoice encounters an error, review the root cause and update the invoice details accordingly. Below are examples of error messages returned by Maventa or the recipient’s service provider.
In this article you can find examples of the errors that might occour:
Not enough information about the recipient
This error occurs when the recipient’s information is incomplete. It is essential to ensure that at least one of the following details is correct:
- OVT code
- VAT/BID
- Email address or postal address
Print service disabled, invoice sending to print fails (IPOST)
If invoice delivery to the print service fails and you receive the error message “The invoice could not be sent to the print service. Print service is not enabled,” the likely cause is that the print service has not been activated in your settings or the invoice file is missing address information.
You can activate the print service in your Maventa settings. If the invoice should be deliverable and the print service is enabled, verify that all address details are correct. The recipient’s address must include a country code (FI for domestic addresses).
To send invoices via the print service, the following information is required:
- Street address
- Postal code
- City
- Country code
Invoice send via email but Recipient email address is invalid
The recipient's email address is invalid. E-invoices can be sent as PDF attachments, via link, or with accept/reject options. For detailed instructions on delivery methods, please refer to our support site.
No routing found for recipient or incorrect electronic invoice address
This error most commonly occurs when the provided e-invoice address is incomplete or incorrect. If only the OVT code has been entered, it is advisable to also provide the Business ID (Y-tunnus) to assist in locating the appropriate routing, especially if the operator ID is missing.
However, this alone does not guarantee that a valid e-invoice address will be found. In most cases, the error can be resolved by including the operator ID in addition to other required details. When the operator ID is provided, the invoice is sent directly to the specified e-invoice address without additional verification from address directories.
If you have entered the complete e-invoice address, double-check that both the OVT and operator IDs are correct. You can confirm the address details with the recipient or consult the e-invoice address directory.
Update the recipient’s information in your invoicing software and resend the invoice. Alternatively, you can correct the information and re-route the invoice directly from your Maventa account.
Multiple routes found with recipients electronic invoice address
Multiple recipients have been identified for this invoice. The provided Business ID (Y-tunnus) is associated with several e-invoice accounts, preventing Maventa from determining the correct recipient.
To avoid this issue, it is recommended to always include the recipient’s OVT code whenever possible. This error typically occurs when only the Business ID or the Business ID and OVT code are provided without the operator ID.
Maventa attempts to supplement missing information by comparing the Business ID with data in our system. In cases where multiple potential delivery routes exist for the same Business ID, Maventa cannot specify the correct delivery address.
Finnish bank network service has not been enabled / Recipient´s operator is a bank
The recipient's operator is a bank.
To send invoices to recipients using bank-operated e-invoice services, the bank network connection must be activated. Detailed instructions for activating bank connectivity are available here. The activation process typically takes 2–4 banking days, after which you will receive a confirmation by email.
If invoices sent to bank operators have encountered errors, they can be resent once activation has been confirmed. Please note that when sending invoices via the bank network, the due date must be at least four banking days from the date of transmission.
Invoice due date is too soon
The due date for the invoice is too close. When the recipient’s operator is a bank, banks require that the due date is at least four banking days from the date of transmission. Please extend the payment term accordingly before resending the invoice.
Maventa is unable to forward invoices to banks without an updated due date, as the receiving bank operator will reject the invoice until the due date is modified in the invoice data. This correction must be made in your invoicing software.
Other error: IBAN and BIC do not match
Other error: IBAN and BIC do not correspond
When submitting an invoice through the bank network, it is essential to provide the correct IBAN account number (EpiAccountID) and the corresponding bank’s BIC code (EpiBfiIdentifier). Please ensure both the IBAN and BIC details are accurately entered on the invoice.
Delivery failed: Failed checks: Invalid IBAN
The error message indicates that the payment details in the invoice file contain an invalid IBAN. This is often due to the IBAN beginning with lowercase “fi” instead of uppercase “FI.”
Update the bank account details in your invoicing software and resend the invoice with the corrected information.
Invoice fails validation
The error message indicates that the invoice file does not meet the format requirements or is otherwise incompatible. A validation error may occur if, for example, the text in a field exceeds the maximum allowed length, or if special characters are used that are not permitted in certain invoice elements.
You can test your invoice data in your Maventa account under Tools > Test XML Invoice Data. The validator will display the rows and descriptions of any errors found. Update the invoice data in your invoicing software according to the validation message and resend the corrected invoice.
Mismatch in address details between SOAP envelope and MessageTransmissionDetails element
Address information in the SOAP envelope does not match the MessageTransmissionDetails element
The invoice was rejected by the recipient's operator due to a mismatch between address details provided in the SOAP envelope and those in the MessageTransmissionDetails element. This issue typically arises if the SOAP envelope and MessageTransmissionDetails contain different identifiers—for example, the company’s business ID (Y-tunnus) is entered in one field and the OVT code in another.
To resolve this, ensure that the same OVT code is used as the identifier in both the SOAP envelope and the MessageTransmissionDetails element by updating the settings in your invoicing software. This will ensure consistency and compliance with the Finvoice format requirements.
<eb:From><eb:PartyId>003711111111</eb:PartyId><eb:Role>Sender</eb:Role></eb:From><eb:From><eb:PartyId>DABAFIHH</eb:PartyId><eb:Role>Intermediator</eb:Role></eb:From><eb:To><eb:PartyId>FI2222222222222222</eb:PartyId><eb:Role>Receiver</eb:Role></eb:To><eb:To><eb:PartyId>NDEAFIHH</eb:PartyId><eb:Role>Intermediator</eb:Role></eb:To>XML
An example of MessageTransmissionDetails from the original invoice data is shown below:
<MessageTransmissionDetails><MessageSenderDetails><FromIdentifier>1111111-1</FromIdentifier><FromIntermediator>DABAFIHH</FromIntermediator></MessageSenderDetails><MessageReceiverDetails><ToIdentifier>FI2222222222222222</ToIdentifier><ToIntermediator>NDEAFIHH</ToIntermediator></MessageReceiverDetails></MessageTransmissionDetails>
In this case, the value eb:PartyId003711111111 and 1111111-1 do not match, as the OVT code must always be used for the sender in the SOAP envelope. To correct this, update the sender identifier in your invoicing software to the company's OVT code.
If "Maventa" is listed in the intermediary field while "DABAFIHH" appears in the SOAP envelope, ensure that both fields reflect the same intermediary code (DABAFIHH). Consistency across these elements is required for successful invoice processing.
If you are confident that your invoice is correct and all necessary services are active, but the error is not listed, please contact our customer support team.
If the error originates from your financial management software, we recommend reaching out directly to your software provider's support services.
Did you find it helpful? Yes No
Send feedback