# D365 Finance and Supply Chain Fit Gap Analysis Worksheet

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

## Short answer

Editable fit gap worksheet that records requirements, responses, effort and cost with running totals.

## Category

microsoft-dynamics

## Erp

Microsoft Dynamics 365 Finance and Supply Chain

## Audience

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

## Tool

**Kind:** worksheet

**Mode:** editable

**Currency:** $

**Columns:**

#### Req ID

**Key:** id

**Type:** text

#### Process area

**Key:** area

**Type:** select

**Options:**

- General ledger
- Accounts payable
- Accounts receivable
- Procurement
- Inventory
- Production control
- Warehouse management
- Master planning
- Product information
- Fixed assets
- Project accounting
- Reporting
- Integration

#### Requirement

**Key:** req

**Type:** text

#### Fit result

**Key:** fit

**Type:** select

**Options:**

- Fit
- Partial fit
- Gap

#### Response

**Key:** resp

**Type:** select

**Options:**

- Standard
- Configuration
- Extension
- ISV
- Integration
- Report
- Process change
- Out of scope

#### Priority

**Key:** priority

**Type:** select

**Options:**

- Must
- Should
- Could

#### Effort

**Key:** days

**Type:** number

**Unit:** days

#### Day rate

**Key:** rate

**Type:** number

**Format:** currency

#### Estimated cost

**Key:** cost

**Type:** number

**Expr:** days * rate

**Format:** currency

**Rows:**

**Id:** R-001

**Area:** Procurement

**Req:** Three-way match with price tolerance by vendor group

**Fit:** Fit

**Resp:** Configuration

**Priority:** Must

**Days:** 3

**Rate:** 1200

**Id:** R-002

**Area:** Production control

**Req:** Print operation travelers with custom barcode layout

**Fit:** Gap

**Resp:** Report

**Priority:** Should

**Days:** 8

**Rate:** 1200

**Id:** R-003

**Area:** Inventory

**Req:** Lot tracking with supplier lot and expiry

**Fit:** Fit

**Resp:** Standard

**Priority:** Must

**Days:** 2

**Rate:** 1200

**Id:** R-004

**Area:** Warehouse management

**Req:** Pick path by customer-specific packaging rule

**Fit:** Partial fit

**Resp:** Extension

**Priority:** Could

**Days:** 15

**Rate:** 1400

**Id:** R-005

**Area:** Integration

**Req:** Nightly interface of shipments to carrier portal

**Fit:** Gap

**Resp:** Integration

**Priority:** Must

**Days:** 12

**Rate:** 1300

**Id:** R-006

**Area:** General ledger

**Req:** Intercompany eliminations for three legal entities

**Fit:** Fit

**Resp:** Configuration

**Priority:** Must

**Days:** 5

**Rate:** 1200

**Totals:**

#### Total effort

**Key:** days

**Agg:** sum

**Format:** days

#### Total estimated cost

**Key:** cost

**Agg:** sum

**Format:** currency

#### Requirements

**Key:** id

**Agg:** count

**Format:** integer

**Summary:**

#### Average cost per requirement

**Key:** avg_cost

**Expr:** sum_cost / count

**Format:** currency

#### Average effort per requirement

**Key:** avg_days

**Expr:** sum_days / count

**Format:** days

**Notes:** Effort figures are examples. Add risk and test effort separately, and review every Gap line for a process change or standard feature alternative before approving customization.

## Content

**Intro:** A fit gap worksheet is where a D365 project decides what the standard product covers and what the business must change or build. This version records the response type for each requirement, adds effort and day rate, and totals the cost so you can discuss scope with numbers.

**Sections:**

#### How to use the worksheet

**Body:** List each business requirement on its own row with an ID and process area. Mark the fit result, then choose the response: standard, configuration, extension, ISV, integration, report, process change or out of scope. Add effort in days and your blended rate and the cost column is computed for you. Review with process owners in workshops and update priority so Must items are not trimmed during budget negotiation.

**Bullets:**

- One requirement per row, written as an outcome.
- Split partial fits into the fit part and the gap part.
- Export to Excel for sign-off and baseline versioning.

#### Method behind a good fit gap

**Body:** Fit gap analysis is only as strong as the requirement quality. Requirements should be testable and linked to a process step. Evaluate each against the standard business process library and the actual configuration in a demo environment, not only against slides. For each gap, ask whether the business can adopt the standard process, whether personalization or a report solves it, and only then whether an extension or ISV is justified.

#### Reading the totals

**Body:** The total effort and cost give an order of magnitude for the customization backlog. Look at the share of cost in the Must category and at the average per requirement. A high concentration in a single process area suggests either an unusual business model or a design that should be challenged. Use the response column to compare how much of the scope relies on extensions versus configuration.

#### Common mistakes

**Body:** Teams often estimate only development effort and ignore design, test, data, training and upgrade impact. Another trap is recording gaps without owners.

**Bullets:**

- No link between a requirement and a test case.
- Customizing to match a legacy screen layout rather than the outcome.
- Ignoring the One Version update cost of each extension.
- Treating ISV licenses as free of ongoing cost.

**Cta:** If you want an independent view on which gaps could be solved with standard features, reports or AI assisted reporting, Netray can review your worksheet.

**Faq:**

#### What is a fit gap analysis in a D365 project?

**Answer:** It compares business requirements to what the standard D365 Finance and Supply Chain product can do and records whether each requirement is a fit, a partial fit or a gap, plus the planned response and its effort.

#### How do I estimate effort for a gap?

**Answer:** Estimate design, build, unit test, integration test, documentation and deployment separately, then add a contingency. Developers often estimate only build time, which understates the real cost by a wide margin.

#### Should every gap be built?

**Answer:** No. Challenge each gap with a process change, standard configuration, personalization, report or Power Platform alternative first. Every extension adds testing and upgrade effort on each One Version update, so build only what the business case supports.

#### Can I use this for other ERPs?

**Answer:** The structure works for any ERP. The process areas and response types in the dropdowns are set for D365 Finance and Supply Chain, but you can retype them to suit another product.

## Search terms

d365 fit gap analysis template, dynamics 365 fit gap excel, fit gap worksheet erp, d365 f&o requirements template, fit gap analysis template excel, d365 implementation requirements gap, erp fit gap cost estimate, d365 solution blueprint fit gap

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