An overhead view of a team with printed charts and a large screen
Dynamics AX · FP&A · Hub

AI Agents for Dynamics
AX FP&A

Whether a cost line is genuinely variable is testable against ten years of actuals. Most driver models are built on an assumption instead.

Key takeaways
  • An old AX database often holds a decade of transaction history in one place, and it is almost never analysed because reporting was built for the current period.
  • Whether a cost line is genuinely variable is testable against years of actuals, and most driver models rest on an assumption instead.
  • In a worked variability test over ten years, three of five assumptions did not hold, and each had been in the model for years.
  • A dimension value in an old installation may have meant three different things across a decade with nothing recording the changes.
  • Holding the mapping with effective dates is the difference between having a decade of history and being able to use it.

AI agents for Dynamics AX FP&A test which cost lines actually track volume across the full history the database holds, hold the mapping between dimension values and their changing meanings with effective dates, and rebuild trends on a single basis. ChatFin reports the fit rather than a verdict and posts nothing.

The opportunity here is unusual. AX installations frequently hold ten years or more of transaction history in one database, and almost none of it is analysed, because reporting was built for the current period and running anything across years is slow and needs a specialist. That history answers questions a newer system simply cannot.

Dynamics AXDynamics 365FP&ADriver modelsVariabilityDimensionsSeasonalityVariance analysisAI agents for finance
01

An old AX database is the best analysis asset most teams do not use

Dynamics AX installations often hold a decade or more of transaction history in one place. ChatFin finds that history is almost never analysed, because reporting was built for the current period and running anything across years is slow and needs a specialist.

What a decade of history supportsWhether it gets used
Seasonality by product and customerRarely
Supplier price trends across contractsAlmost never
Payment behaviour per customerNo, and it is the best credit signal available
Cost structure shifts over yearsOccasionally, by hand
Which cost lines actually track volumeNo, and it decides every driver model

The last row is worth dwelling on. Whether a cost line is genuinely variable is testable against ten years of actuals, and most driver models are built on an assumption rather than that test.

In ChatFin

ChatFin runs the variability test across the full history and reports which cost lines actually track volume, which usually contradicts at least one assumption in the existing model.

02

A worked variability test

Ten years of actuals, testing which cost lines move with volume.

Cost lineAssumedActuallyWhat it means
Direct materialsVariableVariable, stronglyThe model is right
Freight outVariableVariable, with a step at volume thresholdsNeeds a step, not a rate
Indirect labourVariableFixed for two years then stepsModelled wrong every year
MaintenanceFixedTracks volume with a lagShould be variable, lagged
UtilitiesVariableFixed with a seasonal patternModelled wrong

Three of five assumptions do not hold. Each has been in the model for years and each distorts every scenario built on it, and testing them is arithmetic over data the business already owns.

In ChatFin

ChatFin reports the correlation and the fit for each line rather than a verdict, so the person who owns the model decides what to change.

An overhead view of a team with printed charts and a large screen
Three of five assumptions did not hold against ten years of actuals.
03

Dimension structures that have drifted for a decade

An old installation has been through reorganisations, acquisitions and chart changes, and the dimension structure carries all of them.

Values repurposed more than once. A code may have meant three different things across a decade with nothing recording the changes.
Entities merged or split. Comparisons across the event are between different populations.
Retired values still on historic transactions. Any analysis has to handle them rather than filter them out.
Mappings held in a spreadsheet somebody maintains. Which is the actual asset, and it is undocumented.
In ChatFin

ChatFin holds the mapping with effective dates so a ten year trend can be rebuilt on one basis, which is the difference between having a decade of history and being able to use it.

04

Where this underperforms

Three.

The history was migrated with gaps. A partial decade is worse than five clean years, and it needs stating before any trend is drawn.
Nobody knows when dimensions changed meaning. The mapping has to be reconstructed, which is a person's job before it is an agent's.
No governed access route. Nothing here works through screen automation.
Start with the variability test on five cost lines. It uses data you already own, needs read access only, and it usually contradicts an assumption that has been in the model for years.

Deeper in Dynamics AX FP&A

Three use cases sit under this hub, in build and shown rather than linked.

Worked on this page
Natural language querying of finance data · Financial forecasting · Financial modeling

Covered as sections here
Variability testing · Driver models · Dimension mapping · Seasonality · Variance analysis

Questions Dynamics AX FP&A teams ask first

What can a decade of AX history actually tell you?

Seasonality by product and customer, supplier price trends across contract cycles, payment behaviour per customer, and which cost lines genuinely track volume. The last one decides every driver model in the business and is almost never tested. ChatFin runs that test across the full history and reports the correlation and fit per line.

What does a variability test usually find?

That several long standing assumptions do not hold. In a worked test over ten years, freight moved with volume but in steps rather than at a rate, indirect labour was fixed for two years at a time then stepped, and maintenance tracked volume with a lag despite being modelled as fixed. Three of five assumptions were wrong and each had been in the model for years.

Why is dimension mapping harder on an old installation?

Because it has been through reorganisations, acquisitions and chart changes, so a value may have meant three different things across a decade with nothing recording when it changed. Retired values still sit on historic transactions and the real mapping is usually a spreadsheet somebody maintains. ChatFin holds it with effective dates so a long trend can be rebuilt on one basis.

How ChatFin works in Dynamics AX FP&A

Use the decade of history you already own.

ChatFin tests which cost lines actually track volume across the full history, reports correlation and fit rather than a verdict, and leaves the model decision with the person who owns it.

It holds dimension mappings with effective dates so a ten year trend can be rebuilt on one basis, and it posts nothing.

Bring five cost lines and your driver assumptions. The test takes an hour.

Book a demo
AM
Ashok Manthena
CEO and co founder, ChatFin

Ashok Manthena is the CEO and co founder of ChatFin, an AI agent platform for enterprise finance that runs across NetSuite, Acumatica, JD Edwards, SAP and Dynamics 365. He works with CFOs and controllers on governed automation of the close, payables, receivables and reporting. Connect on LinkedIn.

Image credits. Header photograph: an overhead view of a team with printed charts and a large screen, sourced from Pexels and used under the Pexels licence.
All images are served from the Pexels content network. No third party product screenshots, vendor logos or licensed media are used on this page.
Get started

Bring five cost lines and your assumptions.

We will test each against your own history through ChatFin and show you which assumptions hold and which have been wrong for years.

✓Variability tested against your full history
✓Correlation and fit reported, not a verdict
✓Dimension mappings held with effective dates
Request a demo
Confidential & private