Procurement System and ERP Integration: SAP, Visma, Xledger and Unit4
"We use SAP — can you integrate with it?" That's the first question we get in 9 out of 10 demos. ERP integration is the biggest concern when choosing a new procurement system, and for good reason: a failed integration can cost millions and delay the project by months. The good news is that modern integration is no longer an IT project that takes half a year.
In this article we explain how Vieri integrates with the most common ERP systems in the Nordics — SAP, Visma, Xledger and Unit4 — what data flows between systems, and why modern API-based integration is easier than most people think.
Key takeaways
- • Vieri has prebuilt integrations to all the major Nordic ERP systems
- • Typical integration time: 2–4 weeks, not the 6 months many fear
- • Standard data fields include suppliers, items, cost centres, projects and invoices
- • PEPPOL support also gives automatic access to 400+ suppliers without custom integration
Why ERP integration is critical
A procurement system that doesn't talk to the ERP quickly becomes an isolated island. Every order must be re-entered manually, every supplier maintained in two places, every invoice matched manually. The result is double work, errors and frustrated employees — exactly what the procurement system was supposed to eliminate.
Good ERP integration provides:
- Single source of truth for master data: Suppliers, items and cost centres are maintained in ERP, used in Vieri
- Automatic invoice flow: Approved invoices are transferred directly to accounting without manual entry
- Real-time budget control: Orders are checked against updated budget in ERP before approval
- Complete audit trail: Every order is traceable from need to payment, across systems
Vieri integration with the four largest ERP systems in the Nordics
SAP (S/4HANA and ECC)
SAP is the choice for large Nordic enterprise customers. The Vieri integration uses SAP's standard APIs (OData/REST) and supports both S/4HANA Cloud and on-premise ECC. We fetch master data (suppliers, material numbers, cost centres) from SAP and deliver back orders, goods receipts and invoice data ready for matching.
Typical SAP setup
- From SAP to Vieri: Suppliers, materials, chart of accounts, cost centres, projects
- From Vieri to SAP: Purchase requisitions, orders, goods receipts, invoices (FB60)
- Integration time: 3–6 weeks
Visma (Business NXT, Net Visma and Global)
Visma dominates the SMB and mid-market in the Nordics. Vieri has deep integration with Visma Business NXT, Net Visma and Visma Global through Visma's open REST API. For many Visma customers the integration can be up and running in under two weeks.
Particularly valuable: Vieri supports Visma's EHF flow — invoices generated in Vieri are automatically PEPPOL/EHF-formatted and can be sent directly through Visma's access point.
Xledger
Xledger is popular among Nordic mid-sized companies and groups. Vieri integrates with Xledger's GraphQL API and supports advanced group functionality — multiple companies, currencies, intercompany invoicing. Master data is synchronised automatically, and invoices are transferred with complete coding ready for finalisation.
Unit4 (UBW / Agresso)
Unit4 (formerly Agresso/UBW) is a standard system in Nordic public sector and higher education. Vieri has prebuilt integration to Unit4 REST API and supports complex account structures typical for municipalities and universities — projects, cost centres, VAT codes, funds and analysis dimensions.
What about an ERP not mentioned here?
Vieri also integrates with Dynamics 365 Finance, Oracle NetSuite, Tripletex, PowerOffice Go and Maconomy. If your ERP isn't on the list, we build a custom integration via standard REST API or file-based exchange (CSV/XML). For PEPPOL-compatible ERP systems, large parts of invoice and order flow can be handled without a custom integration.
💡 Did you know?
Vieri is a DFØ-approved PEPPOL access point. This means organisations can receive invoices from over 400 Nordic suppliers without building a single supplier integration. Just connect to the PEPPOL network and receive structured EHF invoices directly.
5 questions you should ask the vendor
- Do you have a prebuilt integration to our ERP? Don't settle for "yes, we can integrate" — ask to see reference customers with the same ERP.
- What is the typical integration time? More than 8 weeks is a red flag. Modern APIs should run in 2–6 weeks.
- What data flows both ways? You should see a data catalogue specifically mentioning master data (suppliers, items, cost centres) and transaction data (orders, invoices).
- How are errors and discrepancies handled? A good integration layer should log, alert and offer resend — not fail silently.
- Is the integration certified or just custom-built? Certified integrations get updates when the ERP is upgraded. Custom-built often requires a separate development project for each upgrade.
How a typical Vieri integration works
To give you a concrete picture, here's what a typical Visma integration looks like for a Nordic mid-sized business:
| Data type | Direction | Frequency | Use case |
|---|---|---|---|
| Suppliers | Visma → Vieri | Real-time (webhook) | Supplier search and control |
| Cost centres | Visma → Vieri | Daily | Coding at order time |
| Projects | Visma → Vieri | Daily | Project coding |
| Orders | Vieri → Visma | Real-time | Commitment in accounting |
| Goods receipts | Vieri → Visma | Real-time | Accruals |
| Invoice (matched) | Vieri → Visma | Real-time | Ready for payment |
What determines integration time?
We often get asked why integration time varies from 2 to 6 weeks. Three factors are decisive:
- Data quality in the ERP: If the supplier register has duplicates, missing contact info or outdated prices, this must be cleaned up before integration. Estimate 1–2 weeks extra for such cleanup.
- Complexity of account structure: A standard setup with cost centre and project is fast. Advanced dimensions (departments, funds, analysis fields) require more mapping.
- On-premise vs. cloud: Cloud ERPs (SAP S/4HANA Cloud, Visma NXT, Xledger) integrate faster because API access is standardised. On-premise often requires more work with access and networking.
Security and uptime
Integration between core systems requires solid security. Vieri uses OAuth 2.0 for authentication, TLS 1.3 for transport, and stores no ERP data longer than necessary. Every transaction is logged with timestamp, direction and status — fully auditor-friendly.
Integration uptime is 99.9% in SLA. If the ERP is down, messages are queued and delivered when the connection is back — orders are not lost.
Get started
Considering Vieri but unsure how the integration to your ERP works? The easiest is to see it yourself. Book a demo, and we'll show:
- Live integration to your ERP system
- What data is synchronised both ways
- Realistic timeline based on your ERP and data quality
- Reference customers with the same ERP
See the integration to your ERP system
Book a demo and see the Vieri integration to SAP, Visma, Xledger, Unit4 or your own ERP. We'll also show reference customers with the same setup.
Book demo →
