Isak Blomkvist
Yes, monday.com can be connected to Visma Net, the Nordic cloud ERP. The integration turns what is sold, planned and delivered in monday.com into customers, orders and invoices in Visma Net, and sends payment status and actuals back to whoever owns the customer or project. The integration is built in Make or directly against Visma Net's API, depending on volume and how much should flow in both directions. This article covers what the integration does, how it is built and what to decide before you get started.
- The deal is won in monday CRM
- Router · Does the customer exist in Visma Net?YesThe existing customer is usedNoThe customer is created with details from monday.com
- The sales order is created in Visma Net
The integration searches on the company registration number. The sales rep never has to open Visma Net.
- The project is started in monday.com
- The milestone is marked done
- The amount is retrieved from the project board
- The invoice is created in Visma Net
Projects billed in installments get one invoice per milestone, and the project manager sees in monday.com what has been invoiced and what remains.
- Time and expenses are approved in monday.com
- The basis is locked at the end of the month
- One invoice per customer is created in Visma Net
- The invoice number is written back to monday.com
Ongoing engagements are billed on actual time, and finance gets a finished invoice basis.
- The invoice is paid in Visma Net
- Router · Paid on time?YesStatus paid in monday.comNoTask for the account manager
Sales reps and project managers see payment status where they work, and overdue invoices become a task instead of a surprise.
The flows above are examples of how it can work. Every integration is built around your process: which steps it should include, what should happen in each situation and who is responsible for what.
Short answer
There is no built-in Visma Net integration in monday.com's Integrations Center. The integration is built either in Make, where there is a Visma Net app maintained by the community, or as custom code directly against Visma Net's API. Make is often enough for one-way flows, for example an order on a won deal. When the flow should run in both directions, handle large volumes or follow Visma Net's rules for projects, dimensions and approval, it is usually better to build directly against the API. We do both, and we are also a Visma Net partner ourselves.
What the integration can do
Here are four common examples. Your integration can do more, less or something different, depending on how you work.
When a deal is won in monday.com, the customer is created in Visma Net if missing, and a sales order or invoice is set up with items, amounts and payment terms from the deal.
Completed milestones, delivered orders or approved time in monday.com become an invoice basis in Visma Net. The same project can produce several invoices, including recurring ones for contracts.
Invoice number, invoice date and payment status are written back to monday.com, so whoever owns the customer sees the status without logging in to Visma Net.
Posted costs and revenue per project can be retrieved from Visma Net and shown in monday.com, so the project manager can track the margin while the project is running.
Why connect monday.com and Visma Net?
- One place for the work, one for the finances. Sales, projects and delivery happen in monday.com, accounting and invoicing in Visma Net. Nobody has to work in both.
- Less duplicate work. Customer details, items and amounts are entered once, not in two systems.
- Faster invoicing. The invoice basis is ready the same day the milestone or delivery is, not at the next monthly review.
- The project manager sees the finances. Invoiced, paid and posted costs show up in monday.com, where the project is tracked.
How the integration is built
There are three options, and the right one depends on how advanced the flow is.
| Option | Best when | Keep in mind |
|---|---|---|
| Make | One- or two-way flows with moderate volume, for example customer and order on a won deal | The Visma Net app in Make is maintained by the community, not by Make. Whatever the app does not cover has to be built with Make's HTTP module against Visma Net's API |
| Custom code against Visma Net's API | Large volumes, two-way flows and requirements for projects, dimensions and approval rules in Visma Net | Requires a registered application in Visma's developer portal and someone to own and maintain the code |
| Zapier | Simple one-way notifications | Zapier has no Visma Net app, so anything written to Visma Net has to go through webhooks or API calls |
For Visma Net, the choice is more often between Make and custom code than between Make and Zapier. What determines whether the integration holds up is how it is built: how the details in monday.com map to customers, items, VAT codes, projects and dimensions in Visma Net, how the flow handles credit notes and changed amounts, and what happens when Visma Net rejects a record. An integration that works in a test but silently misses invoices in production costs more than it saves. That is why we build with logging and alerts from the start. The integration requires your Visma Net license to include API access and an integration user with the right permissions.
What to decide before you build
An integration is never better than the process it automates. These questions determine whether it works in practice:
- Where is the customer created? Should new customers be set up from monday.com, or should finance approve them in Visma Net first? Also decide which system owns the customer details afterward.
- What should trigger the order or invoice? A won deal, a completed milestone, a delivery or a month-end close. Pick one status in monday.com, and decide who is allowed to set it.
- How should projects and dimensions be matched? Visma Net often wants a project, cost center or department on every line. Those details must exist in monday.com before the flow runs.
- What should flow back? Invoice number, payment status, posted costs or all three. The more that flows back, the more important it is to build directly against the API.
- What happens when something goes wrong? A good flow logs every run and flags when an invoice could not be created, instead of silently skipping it.
How monday.com and Visma Net share responsibility
The most common question when both systems are in place is where to draw the line. Our recommendation is simple: anything to do with the work, planning, follow-up and communication, lives in monday.com. Anything that needs to be posted or audited lives in Visma Net. The integration moves what needs to exist in both places. We describe the split in detail in Projects in monday.com, finance in Visma Net, along with how monday work management and monday CRM fit in. If you use Fortnox, a Swedish accounting system, today and are considering switching, the comparison is in Visma Net vs Fortnox. You can find more integrations under all integrations.
Straviont builds the integration
We are an official monday.com partner and certified CRM specialists with monday.com, and we are also a Visma Net partner. That means we know both sides of the integration: how the boards in monday.com should be structured, and how customers, orders, projects and dimensions fit together in Visma Net. We start with the process, then build the flow in Make or directly against Visma Net's API, with logging and error handling, and manage it as your business changes.
Frequently asked questions
Can monday.com be connected to Visma Net?
Yes. There is no built-in integration in monday.com, but the integration is built in Make or as custom code against Visma Net's API. It can create customers, orders and invoices in Visma Net and send invoice numbers, payment status and actuals back to monday.com.
Can monday.com create invoices in Visma Net automatically?
Yes. When something in monday.com is ready to bill, for example a won deal, a completed milestone or approved time at month-end close, the integration can create the invoice in Visma Net with customer, items and amounts. If the customer does not exist, it is created first.
Can project financials from Visma Net be shown in monday.com?
Yes. Posted costs and revenue per project can be retrieved from Visma Net and shown on the project board in monday.com, so the project manager tracks actuals against budget where the project is run.
Should we build in Make or directly against Visma Net's API?
Make is often enough for one-way flows with moderate volume. When the flow should run in both directions, handle many records or follow Visma Net's rules for projects, dimensions and approval, it is usually better to build directly against the API.
What do we need in Visma Net to connect the systems?
Your Visma Net license needs API access, a registered application in Visma's developer portal and an integration user with permissions for the customer register, orders and invoicing.
We use Fortnox today. Is the integration the same?
The principle is the same, but Visma Net has more concepts to take into account, like projects, dimensions and approval. We describe the Fortnox integration in monday.com and Fortnox.
Next steps
Start by describing the flow from deal to posted invoice: where the customer is created, what triggers the order, which details Visma Net needs and what should flow back. From there, building it goes quickly. If you want help, you can book a free mapping session and we will go through it together.