M.E.Doc depends on its environment, permissions and required accounting integration. Installation is only the start: define users, entities, document sources and support. Knowing exactly what a backup contains and how to restore it is especially important.
Agree the environment and working roles
Establish usage, user and entity counts, equipment and versions. Check current vendor requirements. Do not migrate by copying an arbitrary folder without planning and validation.
Separate document work, configuration and restoration permissions. Transfer keys and passwords through an agreed secure channel. Technical support should not create an uncontrolled shared copy of a private key.
Test the document path from accounting
Define the source system, formats and supported connector. Documents need the correct entity, details and period. Where several installations exist, verify which one the integration actually uses.
For example, an export may succeed but reach the wrong environment. A transmission-complete message does not replace inspecting the received record. Reconcile contents, status, retries and corrections.
Check backup scope against its purpose
M.E.Doc documentation distinguishes database backups from mechanisms preserving broader application state. Some backup types exclude archived documents. Inventory required data, configuration, roles and archives and verify how each is retained.
Protect copies from unauthorised access and loss with the working computer. Test restoration in an agreed environment without accidentally overwriting production. Verify required entities, documents and permissions.
Updates and handover should preserve operation
Before updates, agree user shutdown and a verified backup. Afterwards, test required actions and exchange. An available update does not mean every integration can skip retesting.
Hand over environment, backup, access and support information. Accounting and legal decisions remain with relevant specialists; the technical team delivers agreed operation. Support stays understandable after computer or contractor changes.
Sources and further reading
