# Acumatica Implementation Statement of Work Template > Source: https://netray.co/tools/acumatica-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 outline for an Acumatica project with scope, phases, deliverables, assumptions, customer responsibilities and approvals. ## Category erp-migration ## Erp Acumatica ## Audience - Implementation lead - Project manager - Operations director ## Tool **Kind:** template **Output:** document **Fields:** #### Customer **Key:** customer **Type:** text **Default:** Northfield Fabrication Inc. #### Implementation partner **Key:** partner **Type:** text **Default:** Example ERP Partners LLC #### Project name **Key:** project **Type:** text **Default:** Acumatica Manufacturing Implementation #### Planned start **Key:** start **Type:** date **Default:** 2027-01-11 #### Target go-live **Key:** golive **Type:** date **Default:** 2027-07-01 #### Edition **Key:** edition **Type:** select **Options:** - Manufacturing Edition - Distribution Edition - General Business Edition **Default:** Manufacturing Edition #### Legal entities / sites **Key:** entities **Type:** text **Default:** 1 legal entity, 2 plants #### In-scope modules **Key:** modules **Type:** textarea **Default:** General Ledger, AP, AR, Cash Management, Inventory, Purchasing, Sales Orders, Production Management (BOM, routing, production orders, MRP) #### Named users **Key:** users **Type:** text **Default:** 45 #### Fee basis **Key:** fee **Type:** select **Options:** - Time and materials with estimate - Fixed fee by phase - Fixed fee **Default:** Fixed fee by phase #### Out of scope **Key:** outscope **Type:** textarea **Default:** Custom development beyond listed items, historical transaction migration, EDI trading partner onboarding, hardware **Blocks:** #### Statement of Work: {{project}} **Body:** Customer: {{customer}} Partner: {{partner}} Planned start: {{start}} Target go-live: {{golive}} Product: Acumatica Cloud ERP, {{edition}} Scope: {{entities}} Named users: {{users}} #### 1. Purpose and objectives **Body:** This Statement of Work describes the services that {{partner}} will provide to {{customer}} to implement Acumatica. The objectives are to replace the current system, standardize financial and operational processes, and reach go-live by {{golive}}. #### 2. In-scope modules **Body:** {{modules}} #### 3. Out of scope **Body:** {{outscope}} Any item not listed in section 2 is handled through the change control process in section 8. #### 4. Phases and deliverables **Table:** **Columns:** - Phase - Key activities - Deliverable - Customer sign-off **Rows:** **0:** Discovery **1:** Process workshops, fit gap, data review **2:** Solution design document **3:** Project sponsor **0:** Configuration **1:** Company setup, chart of accounts, items, BOMs, workflows **2:** Configured test tenant **3:** Process owners **0:** Data migration **1:** Mapping, cleansing, test loads **2:** Signed off load reports **3:** Data owners **0:** Testing and training **1:** Integration tests, user acceptance, role training **2:** UAT sign-off, training log **3:** Project sponsor **0:** Cutover and support **1:** Final load, go-live, hypercare **2:** Go-live checklist, hypercare report **3:** Project sponsor #### 5. Fees and payment basis **Body:** Fee basis: {{fee}}. Fees by phase, expenses and payment schedule are set out in the commercial annex. Acumatica subscription fees are separate and are contracted through the reseller agreement. #### 6. Customer responsibilities **Body:** {{customer}} will provide a project manager with decision authority, timely access to process owners, cleansed source data, test participants for each module, and approvals within 5 business days of a request. #### 7. Assumptions **Body:** Requirements are as discussed in discovery. The number of integrations, reports and users is as stated in this document. Source data is available in structured files. The target go-live depends on the customer meeting the responsibilities in section 6. #### 8. Change control **Body:** Changes to scope, schedule or fees are raised in writing, estimated by {{partner}}, and become effective only when approved by both parties. #### Approvals **Signatures:** - Customer sponsor - Customer project manager - Partner engagement lead **Notes:** This template is a starting point, not legal advice. Have your counsel review the final document and align it with the master services agreement and any reseller contract. ## Content **Intro:** A vague scope is the most common cause of ERP project disputes. This statement of work outline sets modules, phases, deliverables, assumptions and responsibilities in one document that both sides can sign. **Sections:** #### How to use the template **Body:** Fill in the customer, partner, edition, user count and site structure, then list the modules you intend to implement and the items that are explicitly excluded. Choose the fee basis and set start and go-live dates. The document updates as you type. Export it to PDF or Word, then add your commercial annex and rate card. Review each section with the project sponsor before sending it to legal. **Bullets:** - Be specific about what is out of scope - Tie every deliverable to a named sign-off role - State data migration scope by object - List integrations individually #### What a good ERP SOW contains **Body:** At minimum: objectives, in-scope and out-of-scope modules, phases with deliverables, the fee basis, customer responsibilities, assumptions and a change control clause. For a manufacturing implementation, add the number of BOMs and routings to be loaded, the planning approach such as MRP, and the shop floor data collection method. These details drive the effort far more than user count does. #### Fixed fee versus time and materials **Body:** Fixed fee by phase gives budget certainty but depends on a precise scope and a disciplined change process. Time and materials with a not-to-exceed estimate flexes with discovery. A common compromise is fixed fee for discovery, then a fixed fee per phase once the design is signed. Whichever you choose, tie payments to deliverables, not to calendar dates. #### Common mistakes **Body:** Leaving reports and integrations as a line saying as needed is the biggest risk. Counting customer responsibilities as assumptions rather than commitments is the second. Also avoid treating training as a single event: key users need hands-on practice in the test tenant long before end-user sessions. **Cta:** If your project includes AI reporting or document automation on top of the ERP, we can provide a short scoped add-on section for your SOW. **Faq:** #### Is this suitable for any Acumatica edition? **Answer:** Yes. The edition is a field, and you edit the module list to match. Manufacturing projects typically add production management scope; distribution and general business projects can trim those items. #### Who normally writes the SOW? **Answer:** The implementation partner usually drafts it from discovery, and the customer reviews it. Customers who draft their own scope document before talking to partners tend to get clearer proposals. #### Does this replace a contract? **Answer:** No. A statement of work normally sits under a master services agreement that covers liability, IP, confidentiality and termination. This template covers scope and project mechanics only. #### How detailed should the deliverables be? **Answer:** Detailed enough that a stranger could tell whether each one was delivered. Name documents, test environments and reports, and state who signs off. Avoid generic wording such as best practice configuration. ## Search terms acumatica statement of work template, erp implementation sow template, erp project scope document template, acumatica implementation scope, erp statement of work example, erp project assumptions template --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json