Skip to content
English
Log in to support portal
  • There are no suggestions because the search field is empty.

Solving common integration issues

This article gives quick answers to the most common integration questions, so you can often solve a problem without contacting support. It covers sign-in and access errors, company account setup, the testing environment, sending and receiving invoices, Peppol, consumer invoicing in Finland and service availability. Each answer explains the likely cause and what to do next, and links to the documentation for more detail.

Many integration questions have a quick answer. Check this list before you contact support. Each answer links to the documentation for more detail.

Signing in and access

“USER NOT FOUND”
Testing and production use different API keys, and keys from one don't work in the other. Check that your keys match the environment you're calling. Read more.

“401 Unauthorized” when sending or receiving invoices
When your software signs in to Maventa, it asks for the permissions it needs. If it doesn't ask for permission to send or receive invoices, those requests are refused. Also check whether the sign-in has expired: request a new one and try again once. If you get the error again, check your credentials. Read more.

A user can't change company settings
What an integration can do depends on the role of the user it signs in as. Users without the admin role can't change company details or settings. Read more about user roles.

“vendor_api_key_missing”
Every request needs your vendor API key. Check that your software includes it when it signs in. Read more.

Company accounts

A new company account can't be used yet
A company account can't be fully used until a person with the right to represent the company has confirmed it. How this works depends on the company's country. Read more.

The confirmation was signed in the testing environment, but the status didn't change
In the testing environment, the status updates differently from production. Read more.

An old invoice can't be found
Maventa keeps invoices for the current and previous year, roughly two years. Maventa isn't a long-term archive, so store invoices in your own system if you need them for longer. Read more.

Testing environment

A test invoice says “Sent” but never arrived
Email, print, consumer and external operator routes in Finland and Sweden are only simulated in the testing environment. Peppol test sends, and sends between Maventa accounts, work as in production. To test real email delivery, contact Maventa support. Read more.

Test data has disappeared
The testing environment can be cleared without notice. Don't rely on it to store anything.

Sending invoices

An invoice has been “Pending” for a long time
Invoices are usually sent within about 10 minutes. At the turn of the month and at other busy times, it can take a few hours. An invoice can also stay pending on purpose, for example while Maventa retries a Peppol delivery. Pending invoices aren't lost: Maventa monitors them, and they go out once the issue is resolved. Don't send the invoice again. Read more.

An invoice failed
An invoice fails only after every possible delivery route has been tried. What to do depends on the cause:

  • Wrong address: correct the address and send the same invoice to the right address.
  • No delivery route available: send the invoice by another route, such as email or print.
  • Invoice content isn't valid: fix the invoice and send it as a new invoice.

You can also turn on email notifications for failed invoices. Read more.

An invoice was sent by mistake
A sent invoice can't be cancelled through Maventa, because it has already been handed over for delivery. Send a credit note instead, or agree on the cancellation directly with the recipient. Read more.

“DUPLICATE INVOICE NUMBER”
The company has duplicate prevention turned on, and an invoice with the same number was sent in the past 7 days. Read more.

An attachment was rejected
Each attachment can be up to 10 MB, and the whole invoice up to 100 MB. File names can contain only letters A to Z, numbers, full stops and underscores, and can be up to 50 characters long. Read more.

The invoice went by email or print instead of as an e-invoice
When an invoice can't be delivered as an e-invoice, Maventa tries other routes in a fixed order. You can block routes you don't want to use. Read more.

Peppol

Registering a company as a Peppol receiver fails
A company can be registered in Peppol through only one service provider (Access Point) at a time. If it's already registered through another provider, it must ask that provider to remove the registration first. Read more.

A Peppol invoice is taking long to deliver
If the recipient's service provider has a temporary problem, Maventa retries automatically for about two days before reporting the invoice as failed. Don't send the invoice again while it's still in progress. Read more.

Receiving invoices

Invoices are missing from your software
If you use webhooks and your system was unavailable, Maventa retries the notification once an hour for up to 24 hours. Check for new invoices once a day as a backup to catch anything that was missed. Read more.

The same invoice arrives twice
Duplicates can come from repeated notifications or overlapping checks. Keep a list of the invoices you've already processed. Read more.

A received invoice can't be downloaded in the format you want
Download it in its original format or as Peppol BIS 3.0 instead. Read more.

Another integration's invoices appear in your list
If a company uses several integrations, they share one company account. Settings, invoice lists and webhooks are shared. If two different partners' products both download the same received invoice, each partner is billed for it. Read more.

Consumer invoicing in Finland

Consumer e-invoicing hasn't started yet
Opening the bank network connection usually takes a few days. After that, SI-messages (a company's registration message to the banks) can take 1 to 4 banking days to reach the banks, and error notices can arrive several days after sending. Read more.

A consumer e-invoice failed
The consumer may have ended their e-invoicing agreement. Download the latest RI-messages (the bank's notice that a consumer has joined or left e-invoicing) and check for a cancellation. Read more.

Service availability

“503 Service unavailable” or no response
Check status.visma.com under Common Services (Maventa / Visma .net AutoInvoice). Wait and try again, leaving longer gaps between each try. Read more.

“429 Too many requests”
Your software is sending requests too often. Wait before trying again, and avoid checking for new invoices more than once or twice a day if you don't use webhooks. Read more.

Connections are blocked by a firewall
Maventa's IP addresses can change without notice, so firewall rules based on IP addresses aren't recommended. Read more.

Something stopped working after an update
Check the developer changelog and announcements for recent changes.