Visma.net Integration Checklist (Free, PDF/Excel)

0%

0 of 32 items complete

20 critical items still open - these are the highest-risk gaps.

Download checklist:

1. Scope and design

Business purpose of the integration written in two sentencesCRITICALSystem of record decided for each data object (customer, item, order, invoice)CRITICALDirection, trigger and frequency defined for every flowCRITICALVolume estimate per day and peak hour documentedDecision made between a prebuilt connector, an iPaaS tool and custom codeOwner named on both the business and IT sideCRITICAL

2. Access and authentication

Application registered in the Visma developer and connect environmentCRITICALOAuth flow chosen to fit the use case, with scopes limited to what is neededCRITICALClient secrets stored in a vault, never in code or ticketsCRITICALToken refresh and expiry handled in the integration codeCRITICALSeparate test and production credentials and tenantsCRITICALIntegration user has the least privileges required in the ERP

3. Data mapping

Field by field mapping document approved by the business ownerCRITICALCode lists mapped (units, currencies, tax codes, payment terms, warehouses)CRITICALCustomer, supplier and item identifiers aligned across systemsCRITICALRounding and decimal precision rules agreed for prices and quantitiesCharacter set and special character handling testedDate and time zone handling documented

4. Error handling and reliability

Retry logic with backoff for temporary failures and rate limitingCRITICALIdempotency so a repeated message does not create duplicatesCRITICALDead letter or failed message queue with an owner who reviews itCRITICALAlerts for failed runs sent to a monitored channelPagination handled for large result setsBehaviour tested when the ERP is down or in maintenance

5. Testing, security and go live

Test cases cover create, update, cancel and credit scenariosCRITICALEnd to end test from the source system to the posted invoiceCRITICALReconciliation report comparing counts and values between systemsCRITICALPersonal data in logs minimized to meet GDPR dutiesCRITICALData processing agreement and subprocessors reviewedCutover plan with initial data load and freeze windowCRITICALRunbook for support covering restart, replay and escalationPost go live monitoring for at least one month-end

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

Integration design review

Send us your flow diagram and mapping table and we will comment on risks. Optional and free to discuss.

Optional. The tool and every export work without this. No spam.

How to use this checklist

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

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

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.

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

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.

Frequently Asked Questions

Is this checklist from Visma?

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?

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?

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?

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

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.

Talk to an Expert Explore More Free Tools

Related Tools

ERP Migration & Selection

More Other ERPs tools

See all

Visma.net Integration Checklist for ERP and Shop Floor Systems