# Business Central Implementation Statement of Work Template

> Source: https://netray.co/tools/business-central-implementation-statement-of-work-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A fill-in SOW for Business Central projects covering scope, phases, deliverables, assumptions, change control and acceptance.

## Category

microsoft-dynamics

## Erp

Microsoft Dynamics 365 Business Central

## Audience

- BC partner
- Project manager
- Customer sponsor

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Customer

**Key:** customer

**Type:** text

**Default:** Northfield Precision Ltd

#### Implementation partner

**Key:** partner

**Type:** text

**Default:** Example BC Partner Inc.

#### SOW date

**Key:** sow_date

**Type:** date

**Default:** 2026-11-02

#### BC edition

**Key:** edition

**Type:** select

**Options:**

- Essentials
- Premium

**Default:** Premium

#### Deployment

**Key:** deployment

**Type:** select

**Options:**

- Cloud SaaS
- On-premises

**Default:** Cloud SaaS

#### Named users

**Key:** users

**Type:** number

**Default:** 35

#### In-scope areas

**Key:** scope

**Type:** textarea

**Default:** Finance, sales, purchasing, inventory, warehouse, and manufacturing with production orders.

#### Out of scope

**Key:** out_scope

**Type:** textarea

**Default:** Custom EDI, shop floor data collection, and historical transaction migration beyond open items.

#### Target go-live

**Key:** golive

**Type:** date

**Default:** 2027-04-01

#### Fee basis

**Key:** fee

**Type:** select

**Options:**

- Time and materials
- Fixed price per phase
- Fixed price with change control

**Default:** Fixed price per phase

#### Key assumptions

**Key:** assumptions

**Type:** textarea

**Default:** Customer provides subject matter experts for 4 hours per week; data is supplied in agreed templates; three trial migrations are included.

**Blocks:**

#### Statement of Work: Business Central Implementation

**Body:** Customer: {{customer}}
Partner: {{partner}}
Date: {{sow_date}}
Product: Microsoft Dynamics 365 Business Central {{edition}}, {{deployment}}
Named users: {{users}}

#### 1. Purpose and objectives

**Body:** This SOW describes the services {{partner}} will deliver to implement Business Central for {{customer}}. Objectives: replace legacy systems for the areas below, standardise processes, and go live by {{golive}}.

#### 2. Scope

**Body:** In scope: {{scope}}

Out of scope: {{out_scope}}

#### 3. Phases and deliverables

**Table:**

**Columns:**

- Phase
- Key activities
- Deliverable
- Customer role

**Rows:**

**0:** Initiate

**1:** Kickoff, governance, project plan

**2:** Project charter

**3:** Sponsor, project lead

**0:** Analyse

**1:** Process workshops, fit-gap

**2:** Fit-gap and design documents

**3:** Process owners

**0:** Configure

**1:** Setup, extensions, data design

**2:** Configured sandbox

**3:** Key users

**0:** Migrate

**1:** Trial loads, reconciliation

**2:** Signed-off migration

**3:** Data owners, finance

**0:** Test and train

**1:** UAT, training, cutover plan

**2:** UAT sign-off, trained users

**3:** Key users

**0:** Go-live and support

**1:** Cutover, hypercare

**2:** Live system, handover

**3:** All users

#### 4. Assumptions and dependencies

**Body:** {{assumptions}}

The schedule depends on timely customer decisions, availability of subject matter experts and access to the BC tenant and legacy data.

#### 5. Fees and payment

**Body:** Fee basis: {{fee}}. Licence costs are billed separately by the licensing reseller unless stated. Travel and expenses are invoiced at cost with prior approval.

#### 6. Change control

**Body:** Any change to scope, schedule or fees must be raised in writing, estimated by {{partner}} and approved by both parties before work starts.

#### 7. Acceptance

**Body:** Each deliverable is reviewed by {{customer}} within 5 business days. Acceptance is deemed when written approval is given or the deliverable is used in production. Defects against agreed requirements are corrected without additional fee.

#### Approvals

**Signatures:**

- For the customer
- For the partner

**Notes:** This is a starting point, not legal advice. Have your own counsel review fees, liability, data protection and intellectual property terms, and attach your master services agreement.

## Content

**Intro:** A clear statement of work prevents the two classic Business Central project disputes: unclear scope and unclear acceptance. Fill in the fields, review the generated document and export it to PDF or Word as the base of your proposal.

**Sections:**

#### How to use the template

**Body:** Enter customer and partner names, edition, deployment model and user count, then write scope and exclusions in plain language. Choose the fee basis that matches your commercial agreement. The document structure follows common ERP delivery phases: initiate, analyse, configure, migrate, test and train, and go-live with hypercare. Export, then edit the tables to your methodology and add module-specific deliverables.

#### What makes a BC SOW strong

**Body:** Be specific about modules, such as Finance, Sales, Purchasing, Warehouse, Manufacturing and Service, and about integrations, reports and extensions. Say how many trial migrations are included and what data volume is expected, because migration is where fixed price projects overrun. State the number of training sessions and who delivers them. Name the environments: sandbox for configuration and testing and production for live use.

**Bullets:**

- List integrations one by one with direction and frequency
- Specify reports as new, standard or modified
- Define hypercare duration and response expectations

#### Fixed price versus time and materials

**Body:** Fixed price per phase works when requirements are well understood after analysis. Time and materials fits exploratory work or heavy customisation. Many partners fix the analysis phase and then fix later phases against the signed fit-gap, which aligns risk with knowledge. Whatever you choose, change control must be in the same document.

#### Common mistakes

**Body:** Vague acceptance language is the biggest risk: define who reviews, how long they have and what counts as a defect versus a change request. Do not leave data migration as an assumption without volumes. Do not forget customer obligations; a project lacking subject matter expert time slips regardless of the partner's skill.

**Cta:** Netray works with BC and ERP partners on data migration, reporting and AI assistants. If you want a second pair of eyes on a scope document, ask for a review.

**Faq:**

#### Is this SOW legally binding as exported?

**Answer:** It is a template and a starting point. It becomes binding only when signed under an agreement your legal advisers have reviewed. Add your master services agreement terms, liability caps, data protection clauses and governing law before use.

#### Should the SOW include licence costs?

**Answer:** Business Central licences are normally sold through a Microsoft partner under a separate agreement. State clearly whether licensing is part of this contract. Most SOWs cover services only and reference licence quantities as an assumption.

#### How detailed should the scope be?

**Answer:** Detailed enough that a stranger could tell whether a requirement is in or out. Name modules, integrations, reports, extensions and migration objects. Use an exclusions list; it protects both sides more than a long list of inclusions.

#### Can I use this for an upgrade or a NAV migration?

**Answer:** Yes, but adjust phases. Upgrade projects need a technical assessment, code and extension conversion, and data upgrade trials. Replace the Analyse and Configure rows with those activities and keep the change control and acceptance sections.

## Search terms

business central statement of work template, dynamics 365 business central implementation sow, erp implementation statement of work template, business central project scope document, business central partner proposal template, business central implementation plan template

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json