E-Document Management attaches compliant electronic document flows to your sales and purchase close. E-invoice, e-archive, e-despatch and the other document types use the same data as your commercial transactions. You can let your existing system produce the document and leave the matching to EQLEM, or the other way round. You choose the direction of the integration. Portal queues and the question "which invoice matched?" end up in one place.
Accounting tracks incoming and outgoing e-invoices. The warehouse attaches e-despatch to the shipment. Sales runs the e-archive and e-export scenarios. Document templates and more than eleven integrator definitions set up the sending line.
Who is it for?
Accounting and e-document teams run the outgoing, incoming, pending and cancelled queues. Sales and purchasing teams attach the commercial document to its electronic counterpart. The warehouse tracks shipments in e-despatch scenarios. IT picks the integrator and sets up the document template and the compliance line. System administrators watch credit usage and permissions.
All document types are available on web: e-invoice, e-archive, e-despatch, e-export, producer receipts and self-employment invoices. On mobile only part of the e-invoice flow works. Integrator and template management are on web.
How it works
You set up the sending and receiving line through the compliance connection and more than eleven integrator definitions.
You manage the outgoing, incoming, pending and cancelled states of an e-invoice on web. E-archive, e-despatch, e-export, producer receipts and self-employment invoices are also on web.
To attach an incoming document to a purchase or sales record, the header is matched first. If the header does not match, the system drops to line matching. Lines that do not match stay on the list and wait for an operator. That cuts the manual matching people used to do in spreadsheets.
Document templates control how the output looks. Even if you change integrator, the same document model is kept.
Commercial invoices and dispatch notes are created through document entry. The e-document layer completes the electronic close. You filter the queues with the list experience. Notifications pass pending or rejected documents to the team. If you already run another system, system sync aligns the document flow. Permissions decide who sends, who cancels and who matches.
An ordinary day runs like this. The incoming queue is scanned and matched in the morning. Outgoing e-invoices and e-archives go out during the day. Pending and cancelled documents are checked in the evening. E-despatch flows with sales or the warehouse on the day of shipment.
Benefits
The compliance line and the choice of integrator sit on one platform.
Header and line matching cuts the load of incoming documents.
Document templates bring the invoice closer to your own branding.
The close is completed on the same data as sales and purchasing.
You watch credit usage from the modular licensing panel. To avoid quota surprises, you can set up an early warning with a report and a notification.
Your existing system can keep producing document numbers while EQLEM takes on the queue and the matching. Decide the sync direction together with the integration team.
Related modules
- Sales Management — outgoing e-invoice and e-archive
- Purchase Management — matching incoming e-invoices
- Finance Management — collection and payment close
- Integration — aligning with your existing system
Related features
Modular licensing, document entry, list experience, notifications, permissions, system sync, reporting.
Short FAQ
How many integrators are supported? More than eleven integrator definitions are ready. You pick and configure yours on web.
Are e-despatch and e-export on mobile? No, both are on web. Only part of the e-invoice flow works on mobile.
Next step
Settle your integrator, your document template and your first incoming and outgoing e-invoice queue in a narrow pilot. Leave e-export and producer receipts to a second stage. Begin with Try Free, or pick a scope from the Modules catalog.