Implementation responsibilities and controls

Configuration is only one part of implementation

A technology change can affect data, access, reporting, approvals and day-to-day work. A sound implementation therefore needs more than a configured environment. It needs agreed requirements, owners for decisions, representative test cases, a clear acceptance route and a plan for operating the result after change.

Responsibilities to make explicit

• Requirements: the organisation identifies the process, users and intended outcome.
• Data and access: accountable owners confirm source data, roles, permissions and exceptions.
• Testing: representative and exceptional scenarios are tested against agreed expected results.
• Acceptance: an authorised business owner reviews evidence and accepts the agreed scope.
• Ongoing ownership: the organisation assigns responsibility for future changes, releases and operational review.

Use evidence at each stage

Keep a concise record of the scope, decisions, assumptions, test results and accepted changes. This helps the organisation understand what was configured, why it was configured and what should be reviewed when systems, processes or guidance change.

SCSB’s implementation work is defined by the agreed engagement scope. The organisation and its advisers remain responsible for business decisions and for any accounting, tax, legal, privacy, security or regulatory conclusions.

For an agreed Microsoft 365 or Dynamics 365 Business Central implementation requirement, contact SCSB to discuss the relevant scope.