EQLEM Connect is an integration hub that runs on your own network. It connects to several Mikro databases, sends and receives e-documents, and posts incoming invoices to Mikro as purchase invoices. You do not have to shut Mikro down.
It can run stand-alone; no EQLEM subscription is required. Connect it to EQLEM whenever you like, and documents and master data flow both ways.
Who is it for?
The customer IT and integration owner manages setup, connections and the error queue. The accounting and e-document operator tracks outgoing documents and posts incoming invoices to Mikro. Managers see the day's status on the operations dashboard. An external developer uses the REST API and webhooks with a standard data model.
How it works
Connect installs on your server as a Windows service. You define the Mikro connections, and each connection has its own queue. Jobs run in order on one connection and in parallel across different ones. Mikro v16 and v17 can be mixed in one installation.
On Mikro v17, writes go through Mikro's official API, and a Mikro API license is a prerequisite. On v16, SQL access is used.
The management screen is on the web. Use it locally on your office network without opening a port, or sign in at connect.eqlem.com and be routed to your own Connect.
What it offers
- Mikro integration: Multiple databases, 22 master data types, and commercial and finance documents. An interrupted first full transfer resumes where it stopped; afterwards only changes arrive.
- e-Document hub: Outgoing documents are validated as UBL-TR and sent to the integrator; an invalid document is never sent. Incoming documents are listed.
- Incoming invoice to Mikro purchase invoice: The account is found by tax ID (VKN). Lines match first by a learned mapping, then by barcode and stock code. A match you make by hand is reused on later invoices. The same invoice cannot be posted twice.
- Critical-event email: Email notification for critical events such as a failed job; administrators set the preferences.
- Bulk retry and operations dashboard: Retry failed jobs in one action. The dashboard shows daily sent, failed and incoming documents, the queue, and recent days.
- Resilience: After repeated errors from the Mikro API, a circuit breaker pauses calls temporarily; under load (429) Connect waits and retries.
- Clock warning: The dashboard warns when the server clock drifts by more than 5 minutes.
- Public REST API and webhooks: Scope- and connection-based access, signed (HMAC) event notifications, and a request key that prevents duplicates.
- Free TLS certificate: An
etiket.eqlem-connect.netname and an auto-renewing certificate; the private key stays with you.
Using it with EQLEM
Once connected, documents created in EQLEM are written to the right Mikro database by your rules, and Mikro documents and master data arrive in EQLEM. Connect starts the link; you manage the rules in the EQLEM web app. The Integration module covers application sync, while Connect is the stand-alone hub.
Benefits
You stop re-keying incoming invoices. You build an e-document flow that does not depend on your integrator. The error queue and dashboard show problems before a customer calls. Mikro connection details stay in the customer's environment.
Related
Product: EQLEM Connect, Solution: EQLEM Connect, e-Document Management, Integration, System sync.
Short FAQ
I do not use EQLEM. Can I still get Connect? Yes. Connect runs on its own, and you can connect it to EQLEM later.
Are Logo or Netsis supported? This release covers Mikro only (v16, v17).
Is Connect a legal archiving service? No. Legal retention of documents remains the taxpayer's responsibility.
Next step
Request a technical discovery call and tell us your Mikro versions, database count and e-document flow. Contact us for commercial terms.