Master Data Approval in D365: From Change Request to System Update

What does it take to change a single main account name in your ERP?

If your company requires internal approval for master data changes, this process may sound familiar.

An employee submits a change request and obtains approval from the designated approvers. Once approved, they open Microsoft Dynamics 365 Finance & Operations (D365 F&O) and manually enter the approved value again.

The approval record and the ERP update are managed separately. As a result, someone must verify that the value entered matches what was approved—and ensure that changes are properly controlled before approval.

Internal control reviews make the process even more time-consuming. To determine who requested a change, what was approved, and when the change was applied, teams must compare approval documents with ERP change records.

To reduce this repetitive work, JGS Consulting developed a reusable master data approval framework as part of the JGS Agile Package.

The framework connects change requests, approvals, and master data updates in a single process within D365 F&O. It also provides a consolidated view of approval requests across different types of master data.

This article examines what standard D365 F&O already supports, where additional development is needed, and how the shared approval framework is designed to improve day-to-day operations.

As Master Data Grows, So Does the Approval Workload

Main accounts underpin financial accounting. Product master data supports purchasing, manufacturing, and inventory operations. Customer and vendor records provide the foundation for business transactions.

Because these records are essential to business operations, changes often require formal controls and approval.

However, when approval and ERP updates are handled separately, employees must still enter approved changes into the system manually.

Even when a database change log is available, determining exactly what was approved may require reviewing additional documents.

Tracking approval status can also be cumbersome. If different types of master data use separate approval processes and management screens, users must navigate multiple pages to understand where each request stands.

The challenge rarely ends with a single type of master data.

A company that introduces approval controls for main accounts may later need similar controls for products, customers, and vendors.

Developing separate change request forms, approval handling, update logic, audit records, and status screens for each master data type means rebuilding much of the same functionality.

This is why JGS designed a reusable framework that can support approval processes across multiple types of master data.

What Does Standard D365 F&O Already Support?

Before developing additional functionality, JGS first evaluated whether standard D365 F&O features, configuration, or process changes could meet the requirements.

D365 F&O already provides various approval and change management capabilities.

The standard workflow engine supports approval routing, approvals and rejections, delegation, notifications, and workflow history.

For customers and vendors, standard change approval functionality can capture proposed changes to selected fields and apply them after approval.

Engineering Change Management also supports change requests and approval processes for certain product-related scenarios.

D365 F&O is therefore not missing master data approval capabilities altogether.

The challenge JGS set out to address was different: providing a consistent approval process across multiple types of master data while accommodating each company's specific control requirements.

For example, introducing a separate change approval process for main account maintenance may require dedicated request records and rules for applying approved changes.

For products and business partners, the standard functionality must also be evaluated against the required level of control.

Managing approval requests across several master data types in a single view requires an additional shared management structure.

JGS also evaluated the standard Database log functionality.

Database log tracks changes made to configured tables and fields. However, it does not, by itself, provide a complete approval process for managing proposed values or preventing unapproved changes from being applied.

JGS therefore chose to reuse standard approval and change management capabilities wherever possible, while developing extensions for the shared processes not covered by the standard functionality.

Of the 13 requirement elements evaluated, three were fully supported by standard functionality and two were partially supported. The remaining elements were identified for additional development or further assessment.

One Connected Process, from Request to Update

How does the shared approval framework change the way master data is maintained?

Consider a request to rename a main account.

First, it starts with a change request.

The employee reviews the current account value, enters the proposed change, and submits the request for approval.

Instead of completing approval outside the ERP and then entering the same information again, the proposed change is managed directly within D365 F&O.

Next, the request moves through approval.

The framework supports different approval methods depending on the type of master data.

By default, it uses the standard D365 F&O workflow engine.

Where appropriate, a simplified approval method is also available. A member of a designated user group can approve the request in a single step from the request details page.

Regardless of the approval method, the framework follows a common control principle: requesters cannot approve their own requests.

After approval, the authorized change is applied to the master record.

The framework uses the approved value to update the relevant master data.

It is also designed to restrict direct edits to the affected record while approval is pending.

However, the scope of these restrictions—including standard application screens, data integrations, and batch processing—still needs to be confirmed through testing.

Finally, the request and approval history remain linked.

Each change request is designed to retain the previous and proposed values, the users involved, processing timestamps, approval status, and any rejection reasons.

This allows users to trace not only the final change but also the request and approval process behind it.

A Unified View of Master Data Approvals

Another important part of the framework is its consolidated approval status view.

As approval controls expand from main accounts to products and other master data, employees should not have to open a different management screen for every approval request.

The framework provides a shared view where requests can be filtered by master data type, approval status, and request source.

It is also designed to include standard customer and vendor change approval requests.

This does not replace the individual approval functions already available in D365 F&O.

Instead, it builds on existing processes by providing a common place to monitor approval activity.

The framework is also designed for reuse.

For example, if a company first implements approval controls for main accounts and later extends them to products, the common request handling, history tracking, and approval status functions do not need to be developed from scratch.

Each new master data type can be registered through configuration parameters, including its approval method.

Type-specific logic, such as applying an approved value to the relevant master record, is developed only where necessary.

This keeps the reusable framework separate from the processing logic unique to each master data type.

Expected Benefits

The shared master data approval framework is designed to deliver three key benefits.

1. Less Duplicate Data Entry

The approved value can be applied directly from the change request, reducing the need to re-enter information from a separate approval document.

2. Stronger Controls Over Master Data Changes

By restricting changes while approval is pending and applying approved values through a defined process, the framework aims to improve consistency in master data governance.

3. A Clear Audit Trail for Every Change

Linking change requests, approval history, and the applied results makes it easier to support internal control reviews and investigate master data changes.

There are also potential benefits for implementation and ongoing maintenance.

The framework is developed using extensions rather than direct modifications to Microsoft standard code.

Where standard workflow functionality is used, its existing capabilities remain part of the approval process.

Company-specific settings, such as the master data types requiring approval and the applicable approval methods, are handled through configuration parameters wherever possible.

Within the supported configuration options, approval policies can be adjusted without additional development.

When a new master data type is introduced, only the functionality specific to that type needs to be added.

This extension-based approach may also reduce maintenance effort during future updates.

However, extensions still require compatibility checks and regression testing when standard functionality changes.

Current Status and Next Steps

As of October 16, 2026, the shared master data approval framework within the JGS Agile Package had completed its planned development work and entered the testing phase.

The capabilities described in this article reflect the framework's design and developed functionality.

They do not indicate that final test acceptance has been completed or that the framework's operational benefits have been verified in a live customer environment.

JGS plans to share implementation screenshots and test results once validation is complete.

Upcoming articles in the JGS Agile Package series will explore main account and product approval features built on this shared framework, along with BOM and route approval capabilities designed to complement standard D365 F&O processes.

Who Could Benefit from This Framework?

The framework may be particularly useful for:

• Companies that manually re-enter approved master data changes into their ERP systems.
• Organizations that need a clear record of change requests and approvals for internal control reviews.
• Businesses planning to extend approval controls from main accounts to products, customers, vendors, and other master data.

Effective master data governance involves more than simply adding an approval button.

What matters is maintaining a clear, traceable record of who requested a change, who approved it, and what was ultimately updated in the ERP system.

The JGS Agile Package's shared master data approval framework is designed to make this process reusable across projects—without rebuilding the same approval structure each time.

If you're considering improvements to master data governance or approval processes in D365 F&O, we'd be happy to discuss your requirements.

Contact JGS Consulting: https://jgs.ai.kr/support/contact

JGS Consulting Corp. — Designing the future of business.

한국어 글은 네이버 블로그에서 보실 수 있습니다: https://blog.naver.com/jgsconsulting