<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=523033&amp;fmt=gif">

Using Configurable Controls with Microsoft Dynamics

One of the main benefits of using Microsoft Dynamics is that it is easily configured to meet the unique business challenges and processes of varying companies.   Because these configuration decisions have such a large impact on transactions and financial statements, it is imperative that these configurable controls are monitored to ensure that they are properly deployed.    Additionally, auditors have renewed focus on these controls to ensure that the risks configuration controls present are adequately mitigated.

Examples of these configurable controls include: 

  1. Module settings
  2. Workflows
  3. GL posting profiles or groups
  4. Tolerance limits

These areas are a central focus during implementation, but most companies use the ‘set it and forget’ methodology and controls are never subsequently reviewed or monitored.


There are a few simple steps to take to implement a control framework around Microsoft Dynamics configurations:

  1. Set a baseline for the configuration settings and document it.
  2. Include configuration changes in the company’s standard change management process.
  3. If changes are approved, update the relevant documentation accordingly.
  4. Do a risk assessment to determine the key configurations.
  5. Set up a periodic review and sign off on key configurations
  6. Consider deploying a tracking or audit trail solution that monitors changes to key configurations

An example would be a company using workflow approval for purchase orders.   With workflows, most companies review the rejections, approvals and resulting transactions but they fail to monitor the configurations of the workflow itself.  Once the approval hierarchy and dollar thresholds have been determined and configured, document the settings. 

The workflow should be periodically monitored to ensure that it was never accidentally, purposefully or fraudulently disabled.  The approval hierarchy should be reviewed to ensure accuracy after users have moved in and out of the company and positions.  Adding an audit trails to this configuration and setup information will help notify the business process owners of any changes and help prevent unauthorized transactions from leaving the building. Read more about best practices for setting up Audit Trails.

Regardless of which Dynamics product you use (Dynamics 365, AX, GP, NAV or SL), be sure to implement a control framework. Have questions? Email us and we are happy to help!