Accounting, ERP, line-of-business systems, and spreadsheets that do not talk to each other cost hours every week. We build the integrations and automate the flow between them — with plain, predictable code, and AI as a building block where it actually adds value.
TL;DR
System integration and automation at WOLLUM means getting existing systems to exchange data without manual re-keying: orders, hours, invoices, and customer data flow between accounting (Fiken, Tripletex, Visma, PowerOffice), ERP, line-of-business systems, and Microsoft 365. We build API integrations first and use language models where the task requires interpreting text and documents. First integration in production in 2–6 weeks. Our own product Jobbkontroll syncs with Fiken using the same approach: a log of what went through and what was rejected, and a vendor-neutral core where a new accounting system is a new adapter.
System integration is connecting software systems that were not made to talk to each other — via API, file exchange, or, for older systems, robotic operation — so data is entered once and flows on automatically. Automation is the next step: rules and software that do the work between the systems, from creating an invoice when a job is closed to raising an alert when something deviates. We work with business systems; control systems such as PLC and SCADA are outside what we deliver.
We follow one piece of data — an order, a time entry, an invoice — through your systems and find where it is keyed twice, where it stops, and what that costs in hours.
Fiken, Tripletex, Visma, PowerOffice, Microsoft 365, EHF/Peppol, and line-of-business systems with APIs. Older systems without APIs are handled with file exchange or RPA, with API as the first choice wherever it exists.
Rules, and AI where it makes sense — interpreting free text, receipts, and email — the rest in plain code. Everything is logged, and deviations go to a manual queue with alerts, never into a void.
Typical delivery
2–6 weeks for the first integration
Data flow mapping in week 1. Build and test in weeks 1–4. Parallel run with manual checks in weeks 4–6 before full operation. Further flows are built in turn and reuse the infrastructure from the first.
How pricing works
Pricing is set after a scoping phase, as a fixed price per phase.
Read more: in-depth article on this topic
The durations are our estimate for a first version of this type. Time and price for your project are set during scoping.
Office hours, workshop hours and hours in the field are logged against the same project and work package, approved by the project manager and sent as invoicing data straight to the accounting or ERP system you use, such as Tripletex, Visma, PowerOffice Go or Xledger. You see estimate vs actual, billable utilisation and contribution margin per project while the project is running, without changing systems.
If you keep your own project system, we connect certificates, checklists and the customer's document requirements to it. Documents from subcontractors and your own people land on the right project and order, the status of each document is visible, and the documentation package is put together from what is already recorded, with no new system to learn.
For agencies and platform companies: contact forms, CRM, newsletters, payments and the publishing tool (CMS) sharing the same data, so an enquiry or a payment never has to be moved by hand. We build on the vendors' own APIs, such as Stripe for payments and Resend for email.
The status of each connection: what we have delivered and where, what is live in our own product, and which systems have a documented API we can build against.
| System | Read | Write | Status at WOLLUM | Proof | Documentation |
|---|---|---|---|---|---|
| StripeMatch-fee payments in the RoboConnect platform | Yes | Yes | delivered in a client project | Case study: RoboConnect | API documentation (Stripe) |
| ResendTransactional email in the RoboConnect platform | No | Yes | delivered in a client project | Case study: RoboConnect | API documentation (Resend) |
| FikenContacts and products kept in step, invoicing data and purchase vouchers with receipts sent to Fiken, with a synchronisation log | Yes | Yes | live in our own product (Jobbkontroll) | Product page: Jobbkontroll | API documentation (Fiken) |
| Tripletex | Yes | Yes | documented API, not built | API documentation (Tripletex) | |
| Visma.net | Yes | Yes | documented API, not built | API documentation (Visma.net) | |
| PowerOffice Go | Yes | Yes | documented API, not built | API documentation (PowerOffice Go) | |
| Xledger | Yes | Yes | documented API, not built | ||
| Unimicro | Yes | Yes | documented API, not built | API documentation (Unimicro) | |
| RamBase | Yes | Yes | documented API, not built | API documentation (RamBase) | |
| Monitor | Yes | Yes | documented API, not built | API documentation (Monitor) | |
| Microsoft Dynamics 365 Business Central | Yes | Yes | documented API, not built | API documentation (Microsoft Dynamics 365 Business Central) | |
| Visma Severa | Yes | Yes | documented API, not built | API documentation (Visma Severa) | |
| Onix | Yes | Yes | documented API, not built |
Book a 30-minute meeting, or send us a few lines about what's grinding. We reply within one business day.