Technology implementation scope

Start with a defined requirement

A useful technology implementation scope describes the change the organisation needs, the current systems and data involved, the people affected, and the evidence that will show whether the agreed work is ready for use. It should also distinguish standard product configuration from any integration, data, process or change-management dependency.

SCSB service scope

SCSB provides Microsoft 365 implementation and Dynamics 365 Business Central implementation. For Business Central, the approved public scope also includes financial-reporting configuration, SST workflow support and MyInvois/e-Invoice workflow support. The right combination depends on the organisation’s requirements and should not be inferred from a product name or a generic industry example.

Boundaries that remain with the organisation

The organisation retains responsibility for its process owners, business data, access decisions, approvals and decisions about accounting, tax, legal, privacy or regulatory treatment. A configured workflow can make records and review steps more structured; it does not itself establish a legal or regulatory outcome.

What to prepare before discussion

• the processes and outcomes the organisation needs to support;
• the relevant users, roles, source data and systems;
• the integrations, reports or workflow exceptions that matter;
• the person responsible for internal decisions and acceptance; and
• the current documentation or authority guidance that affects the requirement.

For a defined implementation requirement, contact SCSB to discuss whether the scope is appropriate.