Can AI agents automate Visma Net ERP?
Visma Software Nordic · saas · accountingerplogistics
Visma Net ERP has mature API automation and a newly launched official MCP path. The REST APIs expose extensive read and write coverage across finance, customers, suppliers, sales, purchasing, inventory, projects, time, employees, attachments, budgets, and related records. Visma Connect supports both interactive user authorization and client-credentials applications; customer approval, tenant selection, scopes, and commercial API access remain operational gates. Current Financial, Sales Order, and Journal Transaction APIs support signed webhooks. AI Connect, launched in June 2026, connects MCP-compatible clients such as Claude and Microsoft Copilot to live ERP data. It can read, create, and update supported records while enforcing existing user permissions and product business rules, and it permanently blocks deletion. AI Connect covers the general ledger, receivables, payables, sales orders, inventory, projects, time, and personnel data, but excludes fixed assets and CRM and operates in one company per session. Partner activation and first-version lifecycle are material constraints. UI and computer-use paths remain unassessed.
Best path today: mcp · Overall automatability: 8/10
Modalities
| Modality | Status | Detail |
|---|---|---|
| API | yes | restoauth2-authorization-codeoauth2-client-credentials coverage: partial · docs |
| SDK | unknown | official: unknown |
| MCP | yes | verdict: official |
| Integrations | unknown | |
| CLI | unknown | |
| Extensibility | yes | webhooks: True |
| Data access | export: api-json · import: api-json | |
| RPA / UI automation | unknown | web-dom No repeatable UI probe was run. The official AI Connect MCP and REST APIs are the preferred automation paths; browser automation remains unassessed. |
| Computer use | unknown | measured verdicts only — "unknown" means not yet probed by us |
Scores
| api | mcp | integrations | cli | rpa | computer use | overall |
|---|---|---|---|---|---|---|
| 8 | 8 | — | — | — | — | 8 |
Evidence
| Fact | Tier | Source | Date |
|---|---|---|---|
homepage | declared | source | 2026-08-16 |
platforms | declared | source | 2026-08-16 |
license | declared | source | 2026-08-16 |
modalities.api.exists | declared | source | 2026-08-16 |
modalities.api.kinds[0] | declared | source | 2026-08-16 |
modalities.api.auth[0] | declared | source | 2026-08-16 |
modalities.api.auth[1] | declared | source | 2026-08-16 |
modalities.api.coverage | declared | source | 2026-08-16 |
modalities.mcp.first_party | declared | source | 2026-08-16 |
modalities.extensibility.webhooks | declared | source | 2026-08-16 |
modalities.data_access.export[0] | declared | source | 2026-08-16 |
modalities.data_access.import[0] | declared | source | 2026-08-16 |
verdict.scores.api | declared | source | 2026-08-16 |
verdict.scores.api | declared | source | 2026-08-16 |
verdict.scores.mcp | declared | source | 2026-08-16 |
freshness.watch[0].url | declared | source | 2026-08-16 |
freshness.watch[1].url | declared | source | 2026-08-16 |
freshness.watch[2].url | declared | source | 2026-08-16 |
Last verified 2026-08-16 · volatility high · JSON record