# Visma.net Integration Checklist for ERP and Shop Floor Systems

> Source: https://netray.co/tools/visma-net-integration-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A 30 item checklist for scoping, building and testing an integration between Visma.net ERP and your MES, web shop, CRM or other systems.

## Category

other-erp

## Erp

Visma.net

## Industry

Discrete Manufacturing

## Region

Nordics, Netherlands, Europe

## Audience

- Integration developer
- IT manager
- Finance systems owner

## Tool

**Kind:** checklist

**Groups:**

#### 1. Scope and design

**Items:**

**Text:** Business purpose of the integration written in two sentences

**Critical:** true

**Text:** System of record decided for each data object (customer, item, order, invoice)

**Critical:** true

**Text:** Direction, trigger and frequency defined for every flow

**Critical:** true

**Text:** Volume estimate per day and peak hour documented

**Critical:** false

**Text:** Decision made between a prebuilt connector, an iPaaS tool and custom code

**Critical:** false

**Text:** Owner named on both the business and IT side

**Critical:** true

#### 2. Access and authentication

**Items:**

**Text:** Application registered in the Visma developer and connect environment

**Critical:** true

**Text:** OAuth flow chosen to fit the use case, with scopes limited to what is needed

**Critical:** true

**Text:** Client secrets stored in a vault, never in code or tickets

**Critical:** true

**Text:** Token refresh and expiry handled in the integration code

**Critical:** true

**Text:** Separate test and production credentials and tenants

**Critical:** true

**Text:** Integration user has the least privileges required in the ERP

**Critical:** false

#### 3. Data mapping

**Items:**

**Text:** Field by field mapping document approved by the business owner

**Critical:** true

**Text:** Code lists mapped (units, currencies, tax codes, payment terms, warehouses)

**Critical:** true

**Text:** Customer, supplier and item identifiers aligned across systems

**Critical:** true

**Text:** Rounding and decimal precision rules agreed for prices and quantities

**Critical:** false

**Text:** Character set and special character handling tested

**Critical:** false

**Text:** Date and time zone handling documented

**Critical:** false

#### 4. Error handling and reliability

**Items:**

**Text:** Retry logic with backoff for temporary failures and rate limiting

**Critical:** true

**Text:** Idempotency so a repeated message does not create duplicates

**Critical:** true

**Text:** Dead letter or failed message queue with an owner who reviews it

**Critical:** true

**Text:** Alerts for failed runs sent to a monitored channel

**Critical:** false

**Text:** Pagination handled for large result sets

**Critical:** false

**Text:** Behaviour tested when the ERP is down or in maintenance

**Critical:** false

#### 5. Testing, security and go live

**Items:**

**Text:** Test cases cover create, update, cancel and credit scenarios

**Critical:** true

**Text:** End to end test from the source system to the posted invoice

**Critical:** true

**Text:** Reconciliation report comparing counts and values between systems

**Critical:** true

**Text:** Personal data in logs minimized to meet GDPR duties

**Critical:** true

**Text:** Data processing agreement and subprocessors reviewed

**Critical:** false

**Text:** Cutover plan with initial data load and freeze window

**Critical:** true

**Text:** Runbook for support covering restart, replay and escalation

**Critical:** false

**Text:** Post go live monitoring for at least one month-end

**Critical:** false

**Scoring Note:** An integration is ready for production when every critical item is ticked and the reconciliation report has run clean on test data.

## Content

**Intro:** Visma.net ERP is common among small and mid-sized companies in the Nordics, the Netherlands and the UK, and manufacturers often need to connect it to a shop floor system, web shop or CRM. This checklist covers what to settle before, during and after building that connection.

**Sections:**

#### How to use this checklist

**Body:** Use it at three points: during design, before the first test cycle and before go live. Export it to Excel, add an owner and date to each line, and review it weekly with your integration partner. Critical items are those that, if skipped, usually cause duplicate records, silent data loss or security findings.

#### Authentication and access

**Body:** Visma services use OAuth based authentication through Visma Connect, and the details such as grant types and scopes depend on the API and product you use, so confirm them in the current developer documentation for your product. Keep separate credentials for test and production, store secrets in a vault and give the integration user only the rights it needs. Plan for token expiry from the first prototype.

#### Mapping and reliability

**Body:** Most integration defects come from mapping, not from the transport. Units of measure, tax codes, payment terms and warehouse codes rarely match across systems. Write the mapping table early and have the business sign it. For reliability, design every message so it can be replayed safely, and give failed messages an owner. Silent failures are worse than loud ones.

**Bullets:**

- Decide the system of record per data object
- Make writes idempotent
- Respect API rate limits with backoff
- Log without storing personal data unnecessarily

#### Common mistakes

**Body:** Teams often test only the happy path and discover credit notes and cancellations in production. Another is building directly against production data, which makes mistakes hard to undo. Finally, many forget the reconciliation step. A daily report comparing counts and totals across systems catches drift within a day instead of at month end.

**Cta:** If you want a review of your integration design or help writing the reconciliation checks, Netray can assist. This checklist is free and does not require any contact.

**Faq:**

#### Is this checklist from Visma?

**Answer:** No. It is an independent checklist based on general integration practice. API names, scopes and limits change, so always check the current Visma developer documentation for your specific product.

#### Should I build a custom integration or use a connector?

**Answer:** Use a maintained connector or integration platform when one exists for both systems and covers your flows. Build custom only for unusual logic, and plan the long term support cost.

#### How do I avoid duplicate records?

**Answer:** Use a stable external key for each record, check for it before creating, and make updates idempotent. Keep a mapping table of source ids to ERP ids so replays do not create copies.

#### What should I monitor after go live?

**Answer:** Watch failed message counts, run durations, authentication errors and a daily reconciliation of totals. Review them daily in the first weeks and weekly afterwards.

## Search terms

visma.net integration, visma.net api, visma net erp integration checklist, visma connect oauth, visma.net financials api, visma erp integration manufacturing, visma net data mapping, visma integration testing

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json