Nexus SoftSphereDocumentation
Documentation › Nexus Health › Implementing

Implementing Nexus Health

Bring the application into service, in the order the data depends on.

Order of implementation

Each step depends on the one above it. Doing them out of order is the most common cause of an implementation that has to be redone.

  1. Legal entity and company — every transaction is stamped with the entity it belongs to, and that stamp cannot be changed afterwards, so create these first.
  2. Chart of accounts, periods and currency — opening a period late is easy; reposting a year of history into a corrected structure is not.
  3. Master data — customers, suppliers, items or employees, depending on the modules in scope.
  4. Document numbering — a series per entity and document type. Set these before the first document is raised: a series already in use cannot be renumbered.
  5. Roles, then users — create the roles first and attach people to them, so nobody holds a broad role "temporarily". See Securing Nexus Health.
  6. Approvals — see Approvals and workflow.
  7. Opening balances — last, once everything above is fixed.
One connection string is one entity. Pointing a second entity at an existing database to save setup time merges two companies' ledgers, and the merge cannot be unpicked afterwards.