Daily operations live in documents: orders, waybills, invoices, stock vouchers, collections. On EQLEM Platform Web these documents share a common entry experience; header (meta), lines, and record detail. When the module changes, users do not relearn “where do I fill what?” every time. When you open a new module, the team does not have to learn the screen from scratch.
Document entry is not just a form; permissions, company/branch/warehouse scope, stock impact, and the next document in the chain are considered together. A wrong line means quantity written to the wrong warehouse.
Who is it for?
Sales, purchase, warehouse, finance, and accounting operators are primary users. Office teams work heavily on Platform Web; field teams complete related vouchers on Mobile. Approvers check headers; operators fill line detail. Team leads who train staff accelerate onboarding thanks to a standard screen family.
How it works
Typical document: choose document type, enter meta fields such as account/company/branch/warehouse, date, and document number. Lines hold product/service, quantity, unit, price, tax, and warehouse. Record detail and extras open by document type. After save, the document lands in a list and can convert to the next document (order → waybill → invoice).
Stock vouchers (transfer, opening, warehouse issue, and similar) share the same line family; the difference is stock impact. Sales and purchase chains speak the same entry language for waybills and invoices. Finance collection/payment vouchers also use a consistent header–line model. In e-document processes, the operational document connects to the GİB-bound document; matching is managed on dedicated screens.
Permissions decide which steps of a document are visible. Scope can lock default company and warehouse. Validations (required fields, negative stock policy, price rules) fire at save; early warnings instead of silent bad records.
Benefits
Training cost drops: learning one document family transfers quickly to another. Error rates fall because required meta and line discipline are shared. Document chains stay visible; broken Excel steps from order to invoice decrease. Lists and reports feed from the same record, so document quality shows up directly in visibility.
Concept unity between mobile and web is preserved: a field movement appears in the same document family in the office. For existing system / ERP sync, “which voucher types sync?” becomes a clear question.
Relation to modules and products
Sales, purchase, inventory, finance, service/expense, and manufacturing vouchers use this experience. Platform Web is where documents are entered; Mobile completes the field. List experience scans saved documents. Authorization limits delete/approve actions. The e-document module connects operational documents to legal documents. CRM quotes can bridge into the sales chain.
FAQ
Is every module’s document screen identical? Same family and pattern; fields change by document type. Familiar skeleton, flexible content.
Can I save drafts? Save/update behavior depends on document type and flow; you track incomplete documents from lists for operational discipline.
Are all documents on mobile? Per inventory, mobile opens partial fields and document types; heavy office documents may stay on web.
Which documents does sync move? It depends on setup mapping. In Mikro, Logo, and Piconn scenarios, voucher types are selected in project scope.
Next step
Pick one end-to-end chain (for example sales order → waybill → invoice) and run it completely. Try Free to see the document family, then build daily scanning rhythm with list experience.