# D365 Finance and Supply Chain Fit-Gap Analysis Worksheet (Excel Export)

> Source: https://netray.co/tools/d365-fo-fit-gap-analysis-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

An editable fit-gap register that totals gap hours and cost by fit type, so you can see the true size of customization before you commit.

## Category

microsoft-dynamics

## Erp

Microsoft Dynamics 365 Finance and Supply Chain

## Audience

- D365 F&O functional consultant
- Solution architect
- Project manager

## Tool

**Kind:** worksheet

**Mode:** editable

**Currency:** $

**Columns:**

#### Req ID

**Key:** req

**Type:** text

#### Area

**Key:** area

**Type:** select

**Options:**

- Finance
- Procurement
- Inventory
- Production
- Sales
- Warehouse
- Master planning
- Reporting

#### Requirement

**Key:** desc

**Type:** text

#### Fit type

**Key:** fit

**Type:** select

**Options:**

- Standard
- Configuration
- Personalization
- Extension
- ISV
- Not supported

#### Priority

**Key:** priority

**Type:** select

**Options:**

- Must
- Should
- Could

#### Build hours

**Key:** hours

**Type:** number

#### Rate per hour

**Key:** rate

**Type:** number

**Format:** currency

#### Gap cost

**Key:** cost

**Type:** number

**Expr:** hours * rate

**Format:** currency

**Rows:**

**Req:** R-001

**Area:** Finance

**Desc:** Intercompany invoicing across 3 legal entities

**Fit:** Standard

**Priority:** Must

**Hours:** 0

**Rate:** 150

**Req:** R-014

**Area:** Production

**Desc:** Variance reporting by work cell

**Fit:** Extension

**Priority:** Should

**Hours:** 40

**Rate:** 150

**Req:** R-022

**Area:** Inventory

**Desc:** Serial number capture at goods receipt

**Fit:** Configuration

**Priority:** Must

**Hours:** 6

**Rate:** 150

**Req:** R-031

**Area:** Sales

**Desc:** Customer specific packing slip layout

**Fit:** Extension

**Priority:** Could

**Hours:** 24

**Rate:** 150

**Req:** R-040

**Area:** Reporting

**Desc:** Weekly open PO aging in Power BI

**Fit:** Configuration

**Priority:** Should

**Hours:** 16

**Rate:** 150

**Totals:**

#### Total build hours

**Key:** hours

**Agg:** sum

**Format:** number

#### Total gap cost

**Key:** cost

**Agg:** sum

**Format:** currency

#### Requirements

**Key:** req

**Agg:** count

**Format:** integer

**Summary:**

#### Average cost per requirement

**Key:** avg_gap

**Expr:** sum_cost / count

**Format:** currency

#### Average hours per requirement

**Key:** avg_hours

**Expr:** sum_hours / count

**Format:** decimal

**Notes:** Set Build hours to 0 for Standard fits. Filter the exported file by Fit type to produce the customization shortlist for the steering committee.

## Content

**Intro:** A fit-gap register is the document that decides how much of a D365 Finance and Supply Chain project is configuration and how much is development. This worksheet keeps the register, sizes each gap, and totals cost as you edit.

**Sections:**

#### How to use the worksheet

**Body:** List each requirement on its own row with a short ID. Classify the fit type honestly: Standard if the process works out of the box, Configuration if parameters, workflows or setup solve it, Personalization for user-level interface changes, Extension for developer-built changes, ISV where a third-party solution covers it, and Not supported where the business must change the process. Enter build hours and a blended rate, and the cost column calculates automatically.

**Bullets:**

- One row per testable requirement
- Mark priority with Must, Should, Could
- Use the same Req ID in your FDDs and test cases
- Export to Excel for the steering committee pack

#### Reading the totals

**Body:** Watch the share of total hours that sits in Extension rows. A high share suggests the business process is not yet aligned to standard D365, which raises upgrade, regression and support burden under One Version continuous updates. Compare hours for Should and Could rows to the budget, because these are the first candidates to defer. Average hours per requirement is a sanity check, not a target.

#### Method and honesty in classification

**Body:** Good fit-gap sessions are run against a configured baseline, not slides. Demonstrate the process in a prototype or a Microsoft-provided demo environment and ask users to confirm. Consultants tend to under-estimate extension hours by omitting design, code review, unit tests, deployment and documentation, so apply a loading factor when you convert coding hours to build hours.

#### Common mistakes

**Body:** Teams often treat a wish as a requirement, record a fit that has not been demonstrated, or hide gaps under the Configuration label. Also avoid mixing reporting needs with transactional gaps: many reporting requirements are solved by Excel add-in, workspaces or Power BI without code. Review the register again after every major design workshop.

**Cta:** If your fit-gap list lives in several spreadsheets, Netray can help build a private assistant that matches new requirements against your past gaps and standard D365 capability, with consultant review on every answer.

**Faq:**

#### What is the difference between a fit-gap and a gap analysis?

**Answer:** A fit-gap compares business requirements with what the ERP does in standard form, then sizes the difference. A broader gap analysis can compare any current and target state, including process, skills or data. On D365 projects the terms are often used interchangeably.

#### How many requirements are typical?

**Answer:** It varies widely by scope. A single-entity manufacturer may log a few hundred, while a multi-country rollout can reach several thousand. Quality matters more than count: every row should be testable and have an owner.

#### Should integrations be on this register?

**Answer:** Yes, but many teams track them in a separate interface register for detail. Keep a summary row here so effort appears in the total, and cross-reference the interface ID.

#### Can I import this into Azure DevOps?

**Answer:** Export to Excel or CSV and use the Azure DevOps Excel integration or import tools to create work items. Map Req ID to a custom field so you retain traceability between requirement, design and test.

## Search terms

d365 fit gap analysis template, dynamics 365 fit gap excel, d365 fo fit gap worksheet, fit gap analysis template erp, d365 finance fit gap, d365 requirements traceability matrix

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