Search
Getting Started Invoice sending Invoice sending Consumer Invoicing Printing Email invoicing Invoice receiving Invoice receiving Scanning Detect Fraud reporting Integration tools Webhooks Reference implementations Maventa Connector Embeddable User Interface Peppol Peppol Network Document Exchange Invoice Response Self-billing support Invoicing formats Invoicing formats Validation Peppol BIS 3.0 Finvoice 3.0 Document types and type codes Preview Maventa JSON (table) Preview Maventa JSON (json schema) Account management Companies and Settings Department Company Users Billing Accounts receivable Accounts receivable Ropo Reminder & Collection Amili Kassavirta Amili Perintä

Detect

Detect is an automated service that verifies incoming invoices and their supplier details. It helps companies automate invoice processing, identify potential fraud attempts, and prevent errors in payments and accounting. Detect is integrated into the invoice receiving flow, so notifications appear in the right context alongside the invoice.

Available checks

VAT check

VAT — For invoices that include value-added tax (VAT), Detect verifies that the sender is registered in the relevant VAT register. If the total VAT amount on the invoice is below 1 EUR/NOK/SEK (depending on currency), the check is skipped.

The data sources depend on the sender’s country:

Supplier activation check

SUPPLIER_ACTIVATION — For scanned invoices, Detect checks whether the supplier could have sent the invoice electronically instead.

BID check

SENDER_BID_STATUS — Verifies the sender’s business identifier against central business and bankruptcy registers. This check is available for invoices from Norwegian and Finnish senders. For Finland, it also includes a check against the Prepayment Register.

The check validates that the sender’s business ID is registered and active in the national company register. It also returns information about whether the company is undergoing insolvency or bankruptcy proceedings.

The registers used depend on the sender’s country:

Warning list check

SENDER_WARNING_LIST — Verifies the invoice sender against registers that list suspected fraudsters and businesses involved in scams. See the warning list guide section below for details.

Bank account change check

BANK_ACCOUNT_CHANGED — Checks whether the sender has changed their bank account number since the previous invoice. Available for invoices received via Peppol and scanning.

Check descriptions

Check descriptions

Close

How Detect works

Detect is integrated into the incoming invoice workflow via the REST API. The flow works as follows:

  1. The receiving company activates the desired checks. Once activated, Maventa automatically runs them on all incoming invoices for that company.
  2. When an invoice becomes available for download, the corresponding check results are also available to retrieve and display.
  3. Maventa provides predefined descriptions, notification statuses, and messages. Translations are available in English, Norwegian, Finnish, Swedish, Danish, and Dutch.
  4. The integrated system (the company’s financial software or ERP) is responsible for activating the checks and displaying the results to the end user.

Integration requirements

Process

  1. Activate Detect checks — PATCH /v1/services/detect/checks
  2. Fetch results for each invoice — GET /v1/invoices/{id}/detect_results
  3. Display the results to the user

Contractual requirements

Authentication

Authenticate as a company and use the analysis scope.

Example flow: activation and usage

Step 1. Activate the service

To start using Detect, activate the checks you want to use for the company.

The end user must be shown and must accept the General Service Disclaimer before any checks are activated.

Use GET /v1/definitions/detect/checks to retrieve all available checks and their details, including which registers each check uses. Display this information to the user.

Use PATCH /v1/services/detect/checks to activate checks:

Use GET /v1/services/detect/checks to confirm which checks are currently active.

Example of check activation in the Maventa user interface:

Checks activation

Checks activation

Close

Step 2. Run checks on incoming invoices

Once activated, Maventa automatically checks all incoming invoices for the company. When the checks are complete, the invoice is released to the customer’s inbox and the results become available via the REST API.

Invoices and attachments are downloaded as usual. Detect results are retrieved with a separate call:

Use GET /v1/invoices/{id}/detect_results to fetch results for a specific invoice.

Fetch results

Fetch results

Close

Step 3. Display notifications to the user

After fetching the check results, display relevant notifications to the user. If an issue is detected, show a notification message within the integrated system — for example, in invoice listings, booking views, or approval screens.

All possible check results and their descriptions are available via GET /v1/definitions/detect/checks.

Example of result display in a user interface:

Detect check results

Detect check results

Close

Step 4. Deactivate checks

Use the same endpoint to deactivate checks:

General disclaimer

Visma does not warrant that the customer’s use of the check services will be uninterrupted or error-free, or that the service and/or the information obtained by the customer through the services will meet the customer’s requirements. The customer acknowledges and agrees that the check services will evolve over time and that functionality may be added and removed from time to time.

The customer assumes sole responsibility for results obtained from the use of the check services and for conclusions drawn from them. Visma shall have no liability for any damage caused by errors or omissions in any information, instructions, warnings, or flags provided to the customer in connection with the check services, or the customer’s actions or non-actions in response to such information.

Warning list guide

This section explains the warning list check in detail. It can be shared directly with end users or used as a basis for customer support documentation.

What is a warning list?

A warning list is a register containing alerts about suspected fraudsters and companies involved in scams or business swindles.

How does the warning list check work?

When an invoice is received, the sender’s company information is compared against a set of warning lists. If a match is found, a notification is issued to the invoice receiver.

The check uses the following information from the sender:

I received a notification that my invoice is from a company on a warning list. What does this mean?

The invoice sender has been identified in either a third-party register or a Visma user-generated warning list.

Receiving a warning means that the company name or business ID matches information in at least one of the registers.

In the notification message, the “Source” field indicates which register the sender was found in. If the sender appears on multiple registers, all matching register names are included in the notification.

See the list of registers and the criteria for listing companies below.

Sources

The warning list check uses a combination of well-known third-party warning lists and user-reported warnings from Visma customers.

  • This set of registers is not exhaustive. A company not appearing on a list does not guarantee the invoice or sender is legitimate.
  • The information provided by the registers varies. Some may include example invoices, descriptions of past fraud attempts, or other details about reported cases.

EUIPO

The European Union Intellectual Property Office list contains warnings focused on companies involved in trademark and design services scams. Typically, the name, logo, or service appears very similar to a real organisation.

Svenskhandel Varningslistan

Svenskhandel Varningslistan contains warnings about fraudulent invoices, companies with unscrupulous sales practices, and offers or mailings that may be perceived as misleading.

Trygg Handel

The Trygg Handel warning list contains warnings against active fraudsters and business scams.

Visma

Visma users can report an invoice if they suspect the sender is fraudulent. The warning message shows how many different invoice receivers have reported the company.

How to handle warnings

Having a routine in place for handling suspected fraud is important. When a warning appears, consider the following steps:

  1. Confirm with the supplier whether they actually sent the invoice.
  2. Review the invoice details and compare them against any existing agreements.
  3. If the invoice appears to be illegitimate, dispute it through the appropriate channel.
  4. Report suspected fraud — see fraud reporting for details.

Check the relevant regulations and recommended practices for your country and area of business.

Financial supervisory authorities

Central business registers

Visma warning list criteria

The Visma invoice sender warning list is a crowdsourced list of companies suspected by users of Visma’s invoice services, or by a business partner of the sender, to be engaged in suspicious or fraudulent activities.

As part of the warning list check, Detect uses fraud reports from customers. See fraud reporting for details on how to integrate fraud reporting.

Companies are listed based on one or more of the following criteria. The decision to add a company to the list is made through a combination of automated and manual evaluation on a case-by-case basis.

If you suspect a company is listed by mistake, contact Visma through regular support channels or email support.maventa@visma.com.

Back to top

AI Chat Support 24/7

  • Get help via AI chat available 24/7 whenever it suits you
  • Chat extensively uses Maventa support pages, websites, and blogs in its answers
  • If you need assistance that the AI cannot provide, you can also ask a customer service agent to join the conversation
  • Support requests processed Monday to Friday
Cancel Open chat

Got feedback?

Did you not find what you were looking for? Or was something explained unclearly? Or just want to share your thoughts? We are happy to hear your feedback!

Note: This form is not a way to get support, this is only for feedback for the documentation website. If you need support, please contact Maventa support.

Integration Guide Services & Reach API Specification Changelogs Integration guide Getting Started Invoice sending Consumer Invoicing Printing Email invoicing Invoice receiving Scanning Detect Fraud reporting Webhooks Reference implementations Maventa Connector Embeddable User Interface Peppol Network Document Exchange Invoice Response Self-billing support Invoicing formats Validation Peppol BIS 3.0 Finvoice 3.0 Document types and type codes Maventa JSON (table) Maventa JSON (json schema) Companies and Settings Department Company Users Billing Accounts receivable Ropo Reminder & Collection Amili Kassavirta Amili Perintä Services and reach Maventa services and reach e-invoicing in Finland Mass Printing Service e-invoicing in Sweden e-invoicing in Norway e-invoicing in Denmark e-invoicing in the Netherlands e-invoicing in Belgium e-invoicing in Germany e-invoicing in Estonia e-invoicing in Latvia e-invoicing in Poland e-invoicing in Italy e-invoicing in France e-invoicing in Spain Api specification API overview Getting Started Common & authentication API Invoices API Documents API Companies & settings API Lookups API Detect API Validator API Receivables API Billing API Scanning API B2CFI API B2CNO API B2CSE API Partner API Getting Started API Methods Overview Account Configuration API Methods Invoice Sending API Methods Invoice Receiving API Methods B2C Norway API Methods B2C Finland API Methods Other API Methods Changelogs Product changelog Developer Changelog
Clear Send

Enter your credentials to Maventa testing environment, to authenticate and try things out with the Swagger UI. This will fetch a Bearer token using OAuth2 with the endpoint POST https://ax-stage.maventa.com/oauth2/token. The token is stored in your browser's session storage (cleared when you close the tab) and used in Swagger calls done from this documentation website. The token is valid for 1 hour.

Never use your production credentials here. This is only for testing the Maventa test environment in the Swagger UI.
Reset All None
eui global company lookup document:receive document:send invoice:receive invoice:send company:read company:write validate receivables:assignments analysis billing:reports partner:invoice_delivery_actions partner:lookups partner:takeovers partner:lyanthe_scan_service fi_bank_message:send fi_bank_message:receive
Cancel Sign In