# D365 Finance and Supply Chain Functional Design Document (FDD) Template > Source: https://netray.co/tools/d365-fo-functional-design-document-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A fill-in functional design document for a D365 F&O gap, covering requirement, process, data, security and test approach, with sign-off lines. ## Category microsoft-dynamics ## Erp Microsoft Dynamics 365 Finance and Supply Chain ## Audience - D365 F&O functional consultant - Business analyst - Solution architect ## Tool **Kind:** template **Output:** document **Fields:** #### Project name **Key:** project **Type:** text **Default:** Contoso Manufacturing D365 F&O Rollout #### FDD ID **Key:** fdd_id **Type:** text **Default:** FDD-PRD-014 #### Design title **Key:** title **Type:** text **Default:** Production order cost variance by work cell #### Module **Key:** module **Type:** select **Options:** - General ledger - Accounts payable - Accounts receivable - Inventory management - Production control - Procurement and sourcing - Sales and marketing - Warehouse management - Cost accounting - Product information management **Default:** Production control #### Author **Key:** author **Type:** text **Default:** A. Consultant #### Date **Key:** date **Type:** date **Default:** 2026-10-20 #### Business requirement **Key:** requirement **Type:** textarea **Default:** Cost accountants need production order variances reported by work cell and period, because the standard report only groups by item and production order. #### Standard behavior and why it does not fit **Key:** standard **Type:** textarea **Default:** Standard production order cost reports show variance per order. Work cell is held on route operations, not on the cost transactions, so grouping by cell is not available without a join. #### Proposed solution **Key:** solution **Type:** textarea **Default:** Create a data entity based view joining production route cost transactions to route operation resource group, exposed in a workspace tile and exportable to Excel. #### Data and setup impact **Key:** data **Type:** textarea **Default:** No new tables. One new view and one security privilege. Resource groups must be populated for all active routes. #### Security roles affected **Key:** security **Type:** text **Default:** Cost accountant, Production manager #### Acceptance criteria **Key:** tests **Type:** textarea **Default:** Report matches the standard cost variance total for the period to the cent. Users without the privilege cannot open the view. **Blocks:** #### Document control **Table:** **Columns:** - Field - Value **Rows:** **0:** Project **1:** {{project}} **0:** FDD ID **1:** {{fdd_id}} **0:** Title **1:** {{title}} **0:** Module **1:** {{module}} **0:** Author **1:** {{author}} **0:** Date **1:** {{date}} #### 1. Business requirement **Body:** {{requirement}} #### 2. Standard behavior and gap **Body:** {{standard}} #### 3. Proposed solution **Body:** {{solution}} #### 4. Data, setup and configuration impact **Body:** {{data}} #### 5. Security **Body:** Roles and duties affected: {{security}} #### 6. Integration and reporting impact **Body:** List any data entities, Power BI datasets, Excel add-in reports or external interfaces touched by this design. State None if not applicable. #### 7. Acceptance criteria **Body:** {{tests}} #### 8. Open questions and risks **Table:** **Columns:** - # - Question or risk - Owner - Due **Rows:** **0:** 1 **0:** 2 **0:** 3 #### Approvals **Signatures:** - Business process owner - Functional consultant - Solution architect - Development lead **Notes:** Adapt headings to your methodology (for example Sure Step or your own). Keep each FDD to one gap so the effort estimate and test cases trace cleanly. The document is a starting point, not a contractual specification. ## Content **Intro:** A functional design document turns a fit-gap result into something a developer can build and a tester can verify. This template gives you the sections most D365 Finance and Supply Chain projects expect, with sign-off lines. **Sections:** #### How to use the template **Body:** Complete one FDD per gap, not one per workstream. Fill the fields on the left and the document on the right updates; export it to PDF or Word and attach it to the work item in Azure DevOps. Start from the business requirement in the owner's words, then describe what standard D365 does today. The gap is the difference between the two, and writing it explicitly stops scope from drifting during build. **Bullets:** - One gap per document keeps estimates traceable - Quote the business requirement in the owner's language - State standard behavior before proposing anything custom - Name the security roles and duties that will change #### What a good D365 FDD contains **Body:** The solution section should say whether the answer is configuration, a personalization, a Power Platform item, an extension, or an integration. Extensions in finance and operations apps should follow the extensibility model (event handlers, Chain of Command, extension classes) rather than overlayering, so mention the intended approach even if the technical design comes later. Note data entities and the data management framework if migration or integration is involved, and name reports (SSRS, Power BI, Excel) affected. #### Acceptance criteria and traceability **Body:** Write acceptance criteria as observable results, such as a report total that equals a standard report to the cent, or a user without a privilege being blocked. These become the UAT cases and, where stable, regression cases for the Regression Suite Automation Tool. Add the FDD ID to the matching fit-gap row, the technical design and the test case, so a change request can be traced both ways. #### Common mistakes **Body:** The usual problems are bundling several gaps in one document, describing screens instead of outcomes, leaving security until UAT, and skipping the impact on data migration. Another is proposing a custom build where a configuration parameter or a feature management switch already exists. Check Feature management and the module parameters first, and record what you checked. **Cta:** If your team writes many FDDs from ERP knowledge scattered across wikis and tickets, Netray can build a private assistant that drafts the first version from your own standards and past designs, with a consultant reviewing every output. **Faq:** #### Is this the same as a technical design document? **Answer:** No. The functional design describes what the business needs and how the process should behave. The technical design describes how developers build it, including classes, tables, extensions and performance. Many teams link the two by FDD ID, with the technical design written after the functional design is approved. #### Does it follow a Microsoft format? **Answer:** No. Microsoft does not mandate a single FDD layout. This template uses sections common on D365 projects and you can rename or reorder them to match your delivery methodology or the standard of your implementation partner. #### Can I add fields for my own project? **Answer:** You can add rows or text to the exported document in Word after export. For repeatable projects, copy the structure into your own document library so every consultant uses the same headings and acceptance criteria style. #### Where should the signed FDD be stored? **Answer:** Keep it with the work item in Azure DevOps or your project repository, linked to the fit-gap row and test cases. The key is that anyone reviewing a change later can find the approved version and see who accepted it. ## Search terms d365 functional design document template, dynamics 365 fdd template, d365 fo fdd, functional design document dynamics 365 finance, d365 gap design document, d365 fo functional specification template, d365 supply chain fdd word --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json