The Integration module syncs EQLEM with the system you already run. Mikro v15, v16 and v17 are supported, along with Logo and Piconn. Nobody asks you to switch the old one off. An agent installed on your own network works together with orchestration in the cloud, and the habit of entering the same record twice fades away.
IT sets up the connection, manages the field mapping and watches the error queue. Operations can work in EQLEM while accounting stays in your existing system. The other way round works too.
Who is it for?
IT and integration teams set up the application sync, file integration and the service. Operations managers watch the transfer data and the error queue. Accounting keeps the ledger in the existing system. Module owners decide which record flows in which direction. System administrators keep the integration sign-in separate through the Dashboard.
The management screens are on web. For local access, an agent is installed on your own network.
How it works
You set up the application sync for Mikro, Logo and Piconn. The agent on your network reaches your local system. Orchestration in the cloud manages the queue.
File integration covers bulk data exchange.
You watch transfer data on web. What went across, what is waiting and where something failed all appear in the list.
In field mapping you connect account, stock and voucher fields on both sides. You lock the direction of the flow in the project design. Whether it runs from EQLEM to the existing system or the other way round is decided up front.
In the error queue you retry record by record. If the same record keeps failing, review its field mapping.
The integration sign-in is a separate identity gate. It does not get mixed up with the daily user sign-in.
When you add a new company, open the master data first and the voucher flow afterwards.
You filter lists with the list experience. Notifications pass on sync errors. Permissions decide who may configure the integration. Commercial documents stay consistent with the document entry model.
Benefits
Your existing system stays in place.
The supported versions are stated plainly: Mikro v15, v16 and v17, plus Logo and Piconn.
The agent on your own network reaches your local system, so you do not have to expose your data.
Both file and service options are available.
Double entry drops and traceability goes up.
Related modules
- Company & System — company scope
- Inventory Management — card and movement sync
- E-Document Management — the document line
- Dashboard & Sign-in — integration sign-in
Related features
System sync, list experience, notifications, permissions, modular licensing, document entry.
Short FAQ
Which systems are supported? Mikro v15, v16 and v17, plus Logo and Piconn. If you run something else, we will look at it with you.
Does EQLEM replace my existing system? No. As a Solution Platform it sits beside it. The sync means you do not enter the same record twice.
Next step
Open a narrow pilot with one company and your critical master data. Start with account and stock cards. Open the voucher flow in a second stage. Write the agent version and the supported system version plainly into your setup checklist. Begin with Try Free, or choose from the Modules catalog.