Manage e-documents, incoming invoices and ERP connections from one hub without shutting Mikro down. Connect runs on your network and keeps your data and Mikro connection details in your environment.
It can run stand-alone; no EQLEM subscription is required. It connects to EQLEM whenever you want.
What it is for
Accounting stays in Mikro. Connect is the bridge between Mikro, your e-document integrator and, if you want, EQLEM. It sends outgoing documents, receives incoming invoices and posts them to Mikro as purchase invoices, and collects errors on one screen.
Who it is for
Businesses that run Mikro, manage several databases, or want an e-document flow that does not depend on their integrator. Customer IT does the setup, the accounting and e-document operator runs the daily work, and managers watch the dashboard.
Mikro integration
- Versions: Mikro v16 and v17, mixed in one installation if needed.
- Multiple databases: Each connection has its own queue. Jobs run in order on one connection and in parallel across connections.
- Write path: On v17, only Mikro's official API; a Mikro API license is a prerequisite. On v16, SQL access.
- Resilience: After repeated errors from the Mikro API, a circuit breaker pauses calls briefly and jobs are retried as temporary failures. Under load (429), Connect waits and retries. Concurrent calls to the same Mikro server are capped.
- Timeouts: If a write result is unknown, Connect does not blindly write again; it looks for the existing document by reconciliation.
e-Document hub
- Outgoing: Validated as UBL-TR and sent to the integrator. An invalid document is never sent. Status is written back to Mikro.
- Incoming invoice to Mikro purchase invoice: The account is found by tax ID (VKN). Lines are matched in order by learned mapping, barcode and stock code. You match an unmatched line by hand, Connect learns it and reuses it on later invoices. The same invoice cannot be posted twice.
- Integrator accounts: Accounts and the ERP connection to tax ID mapping are defined in Connect Web and stay local. Integrator adapters: Mysoft, Trendyol e-Faturam, Kolaysoft, NES, Doğan e-Dönüşüm; live verification happens in the pilot.
Critical-event email
You receive email for critical events such as a failed job. An administrator sets the SMTP configuration and which events notify, and can send a test email.
Bulk retry and operations dashboard
- Bulk retry: Retry failed jobs in one action (up to 500 jobs at a time); the action is written to the audit trail.
- Operations dashboard: Documents sent, failed and received today, queued and failed jobs, and a breakdown of recent days.
- Clock warning: The dashboard warns when the server clock drifts by more than 5 minutes; the support package includes clock information.
Installation
- On-prem: Connect installs on your server as a Windows service; the local database can be SQLite, MSSQL or PostgreSQL.
- Access: The local web app works on your office network without opening a port. Optionally sign in at
connect.eqlem.comwith username and password and be routed to your own Connect. - Free TLS: An
etiket.eqlem-connect.netname is created, DNS is managed automatically, and the certificate is issued free and renews automatically. The private key stays with you; by default only port 443 is needed. You can also use your own domain or PFX certificate.
Security
- Mikro connection details, integrator accounts and the TLS key stay in the customer environment; we recommend restricting access to the server and backups with file and database permissions.
- Local users are authorized by role and company scope; two-factor authentication (TOTP) is optional.
- Critical actions are written to the audit trail. The REST API is limited by scope and connection; webhooks are signed.
Stand-alone use and connecting to EQLEM
- On its own: Without an EQLEM subscription you use the e-document hub, Mikro connections, the operations dashboard and the public REST API and webhooks.
- With EQLEM: Once connected, master data and documents flow from Mikro to EQLEM, and documents created in EQLEM are written to the right Mikro database by your rules. Connect starts the link; you manage the rules in the EQLEM web app.
- You can connect later; your existing Connect installation does not change.
Retention responsibility
EQLEM Connect is not a legal archiving service. Legal retention of e-documents remains the taxpayer's responsibility.
Scope
This release covers Mikro v16 and v17. Non-Mikro systems and portless (relay) cloud access are out of scope. Contact us for commercial terms.
Related
Product: EQLEM Connect, Module: EQLEM Connect, e-Document Management, Integration.
FAQ
I do not use EQLEM. Can I still get Connect? Yes. Connect runs stand-alone.
Do I need an extra license for Mikro v17? Yes, writes require a Mikro API license.
What if the system cannot find a line on an incoming invoice? You match the line by hand and Connect learns the mapping.
Next step
Request a technical discovery call and tell us your Mikro versions, database count and e-document flow.