Integration · ERP

A digital coworker for Visma Business

A digital coworker that works directly in your Visma Business installation — preparing the basis for purchasing, placing purchase orders, following up order confirmations and registering goods receipts. The system stays on your own server. The manual steps simply stop happening.

← Integrations

  • AvailableThe integration runs in production today
  • On-premisesConnects to your local installation — no cloud migration required
  • Purchasing firstThe purchasing flow is what we have connected and run live

Visma Business is Visma’s ERP for larger operations, and at many customers it still runs where it has always run: on their own server behind the firewall. That is a perfectly reasonable setup — but it is also why most AI tools never reach the system. They assume a cloud API that is not there.

A digital coworker connects to your installation where it stands instead. No migration to Visma.net or Business NXT, no parallel register and no change for the people working in the system every day.

We started with purchasing, because that is where most time is lost: needs spotted too late, orders placed when someone has a spare moment, and order confirmations nobody checks until the goods fail to arrive.

Why this integration

What you get out of it

Works on your own server

The coworker connects to your local Visma Business installation. You do not have to move to the cloud first in order to automate anything.

Built for the purchasing flow

From a need appearing to a registered goods receipt — the whole chain, not just a lookup in the item register.

Reads and writes

The coworker creates and updates records in Visma Business — it does not just read data out. That is where the time is actually saved.

A full audit trail

Every action is logged: what the coworker tried to do, which data it used and what the system replied.

Capability

What it does in Visma Business

These are the flows running today. If you need something not listed here, we build it around your requirement.

Purchasing needs — monitors stock levels, reorder points and sales orders and flags what needs buying.

Purchase orders — prepares the basis and places orders with the right supplier according to your rules.

Order confirmations — reads the supplier reply and compares price, quantity and dates against the order.

Delivery follow-up — updates delivery dates and chases the supplier when something is late.

Goods receipts — registers received goods and matches them to the purchase order.

Item and supplier data — looks up items, prices, terms and previous purchasing history.

The flow

From a need appearing to a registered goods receipt

This is what a typical purchase looks like when a digital coworker runs it.

Comes in

  • Stock need
  • Sales order
  • Supplier reply by email

Digital coworker

Prepares the basis, picks the supplier according to your rules, sends the order and reconciles the reply — and escalates to a human when price, date or quantity differs.

Lands in Visma Business

  • Purchase order
  • Updated delivery date
  • Goods receipt

Who notices the difference

What it means for different parts of the business

An integration is rarely interesting in itself. This is what it actually changes for the people working in Visma Business every day.

Purchasing

Purchasing that happens on time

Needs are caught as they arise, not when someone gets round to looking. Orders go to the right supplier and confirmations are reconciled without anyone reading every email.

Warehouse and production

Fewer surprises

Late deliveries surface before they stop production, and goods receipts are registered straight away instead of piling up.

Management and IT

No new platform to maintain

The server stays where it stands. IT decides how access is set up and how far it reaches — after that every action is logged and traceable.

Getting started

How you connect it

Setup is a one-off effort. Expect days, not weeks — provided you know which flow you want to start with.

  1. We walk through the purchasing flow

    A conversation where you describe how purchasing is handled manually today: who decides, which rules apply and where it tends to go wrong. We tell you honestly what the coworker will not handle.

  2. You and your IT set up access

    We agree with your IT team or hosting partner on how the coworker reaches the installation, and with which permissions — no more than the flow requires. Credentials are stored encrypted and per account.

  3. We configure the coworker

    We build the flow against your setup and your purchasing rules, and test it on real cases from your own day-to-day work.

  4. You approve before it goes live

    The coworker first runs with you as reviewer — you see every purchase order before it goes out. Once you are comfortable, you let it run on its own.

Security

Access, logging and accountability

Access to Visma Business is set up once together with your IT team and stored per customer. Your credentials are never shared between accounts and are never used outside the actions your digital coworkers are configured to perform.

Because the system sits on your own server, you decide how the connection is made and how far the permissions reach. We do not need broader access than the flow we have agreed on.

Every action goes through our job queue — fully logged, auditable and searchable. You also set the limits for purchasing: which suppliers are allowed, which amounts may go through automatically and what must always be reviewed by a human.

Running Visma Business?

Tell us how purchasing is handled at your company today. We will show you what it looks like with a digital coworker — against your own installation.

Book a call