If an error occurs when transferring invoices, invoice with errors is moved to a error status created when enabling the integration.

To be able to send that invoice to your customer, you need to

  • check the error from the transfer log,
  • fix the data causing the error
  • and change the status back to waiting for transfer.

To access the Transfer log, open Settings menu from top navigation and select Integrations > Integrations. If there are several integrations used in your organization, you can use filter Integration name to narrow down the list of log messages. You can also use Date and Log level to filter the results shown.

Typical errors

Finvoice 3.0

Error message Solution
The 'BuyerStreetName' element is invalid - The value '' is invalid according to its datatype 'genericStringType235' - The actual length is less than the MinLength value. The invoice doesn't have address line. Open invoice and add address. Remember to add address also for the customer card.
The 'BuyerTownName' element is invalid - The value '' is invalid according to its datatype 'genericStringType235' - The actual length is less than the MinLength value. The invoice doesn't have city in address. Open invoice and add receiver's city. Remember to add full address also for the customer card.
The 'BuyerPostCodeIdentifier' element is invalid - The value '' is invalid according to its datatype 'genericStringType235' - The actual length is less than the MinLength value. The invoice doesn't have postcode in address. Open invoice and add receiver's postcode. Remember to add full address also for the customer card.
The element 'Finvoice' has invalid child element 'SpecificationDetails'. List of possible elements expected: 'InvoiceRow'. The invoice doesn't have any invoice rows. Open invoice and add invoice row.
Seller must have at least one bank account. Add bank account details into Settings > Organization > Bank accounts. Remember to use IBAN format. Then open invoice, change status to draft, then back to "Transfer to", to update the bank details on the invoice.
Seller must have a BIC in bank account details. Bank account number must be given in IBAN format and it needs to have correct BIC/SWIFT code. Go to Settings > Organization > Bank accounts to fix the account number.
Company not found. The Company UUID given in Data transfer settings, is not recognized by Maventa. Go to Settings > Integrations > Maventa, and compare the Company UUID to the one in Maventa settings. Verify that the are no extra spaces in the beginning or end of the entered value.
User not found. The API key given in Data transfer settings, is not recognized by Maventa. Go to Settings > Integrations > Maventa, and compare the API key to the one in Maventa settings. Verify that the are no extra spaces in the beginning or end of the entered value.
Error in Maventa for Finnish customers: "Laskun lähetys epäonnistui. Vastaanottajan operaattori on pankki." The bank network connection is not enabled. The connection is disabled as default when Maventa account is created. It takes about a week to get the connection working.
Invoices not found. Check that business unit for invoice/project is active. Go to Settings > Organization > Business units, and click Show disabled business units and activate business unit.
Could not save invoice nr due to duplicate invoice number. The invoice has already been sent to Maventa and cannot be transferred there again. Check that the invoice is in Maventa.
If the invoice has transferred correctly, in Severa you can edit the invoice's invoice status to sent. This way the automation won't try to send the invoice to Maventa again.

Peppol 3.0

Error message Solution
Sending to PEPPOL failed [xxxxxxxxxxx] [xxxxxxxxxxx] A VAT number MUST be valid Norwegian organization number (nine numbers) followed by the letters MVA. Add MVA at the end of organization number on customer card and company details under settings.


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.