DOGAN ADIYAMAN Dynamics 365 Security and Controls Manager

My clients keep asking whether there is a payment proposal workflow exist nor not. The answer is no. However, I believe that there should be a workflow.

Possible business solution:

• Create a stand alone payment proposal,
• Submit it to workflow,
• Transfer approved proposal into a payment journal.

Please vote if you agree with the idea.

In D365FO, there’s currently no way to proactively monitor large purchase price variances (PPVs). I’m suggesting a feature where users can set PPV tolerance thresholds, and if a purchase exceeds the limit, the system notifies the team or triggers a review. This helps catch unusual cost differences early—before month-end or audits—so the business can investigate and take action. It would be especially helpful for finance and procurement teams and support better compliance with internal controls like SOX. Many companies handle this manually today with reports or reconciliations, but a built-in alert or workflow would make it much easier and reduce risk of financial misstatements.

Currently, when an employee is terminated in the Human Resources module of Dynamics 365 Finance & Operations, the associated system user account is not automatically disabled. This creates a compliance and security risk, as terminated employees may still retain active access to the system.

Suggested Improvement:

Introduce functionality so that when an employee is terminated in HR, their corresponding D365FO user account is automatically disabled. This would align HR actions with system security, reduce manual administration, and strengthen compliance (e.g., SOX, internal controls).

In many organizations, vendor records must undergo internal reviews (e.g., due diligence, tax ID verification, or approval from Procurement and Compliance) before they can be used in financial transactions. Currently, when a vendor is created in D365FO, it is immediately available for posting purchase orders or invoices unless manually placed on hold. This creates a risk that unverified or unapproved vendors may be used prematurely.

The requirement is to automatically place all newly created vendors on hold until they are reviewed and explicitly released by authorized personnel.

Proposed System Behavior: When a new vendor record is created in D365FO, the vendor hold status should default to “All”.