Configuration Governance Platform
Make configuration
governable.
ConfigCompare enables organisations to understand, validate, monitor and govern ERP configuration throughout the application lifecycle using Deterministic Comparison, historical Snapshots and governance capabilities.
Built for Microsoft Dynamics 365 Finance & Supply Chain Management, with Snapshot capability for legacy Dynamics AX and AX 2012 estates.
Available on Microsoft Marketplace
- D365 Finance & Supply Chain ManagementAvailable now
- Dynamics AX / AX 2012Legacy Snapshot capability
- Business Central · DataverseOn the roadmap
Deterministic evidence
From Snapshot to governed result
- 01Snapshot AKnown configuration state
- 02Snapshot BComparison state
- 03Deterministic ComparisonFactual evidence
Ruleset applied · 3 Escalations assigned to their responsible owners
100%
deterministic. AI explains results; it never performs the Comparison.
1,930
curated configuration tables in the starter catalogue, extensible for ISV and bespoke tables.
46,148
multi-option settings per legal entity in the reference environment - configurable decisions, not records.
2010
AXImprove established, specialising in Microsoft Dynamics since Axapta.
The platform
Comparison is the mechanism. Configuration Governance is the purpose.
Deterministic Comparison establishes the factual configuration state. Rulesets and AI Insights turn that evidence into governance decisions a business owner and an auditor can both read.
- Every Difference is attributable to a table and field, with both values retained.
- Matches are retained. An expected Match can matter as much as a Difference.
- Rulesets classify results by severity and assign Responsibility.
- AI Insights explain the results. The Deterministic Comparison remains the source of truth.
Questions that matter
Real questions. Deterministic answers.
Start with the operational question, then use governed configuration evidence to answer it.
- Change over time01
Is PROD the same as it was yesterday?
Compare Snapshots across time to detect Configuration Drift and establish exactly what changed.
Explore the evidence - Testing confidence02
Does UAT contain the right configuration for testing?
Validate UAT against an approved baseline while retaining visibility of both expected and unexpected Differences.
Explore the evidence - Upgrade assurance03
Did an update change configuration or application structure?
Use pre- and post-upgrade configuration and metadata analysis to identify change and assess its impact.
Explore the evidence - Rollout consistency04
Are companies aligned with the approved template?
Compare multiple companies against an approved template to support consistent regional and global rollouts.
Explore the evidence
Four governance pillars
Configuration evidence where delivery risk appears.
Apply governed evidence throughout delivery, operations, support and application change.
- 01
Application Lifecycle Management
Validate DEV to TEST to UAT to PROD and keep companies aligned to the approved template.
- 02
Governance & Audit
Detect Configuration Drift and retain audit evidence for SOX and internal controls.
- 03
Testing & Support
Answer "it worked yesterday" with evidence and accelerate root cause analysis.
- 04
Upgrades
Baseline before One Version updates and validate configuration and metadata after.
See it in practice
Bring configuration into the governance conversation.
Arrange a ConfigCompare demonstration with AXImprove, or do your due diligence first: the complete technical reference is public.
Book a demo