AI Agents for Microsoft
Dynamics AX
AX is out of mainstream support and still posting journals. The close does not get to wait for the migration.
- AX 2012 R3 is still the live general ledger at companies that priced the Dynamics 365 migration and decided against it for now.
- The integration surface is AIF, the batch server and the database. Anything reading AX has to be built for what AX offers rather than for a modern REST API.
- Financial dimensions are almost never standard on a long lived AX estate, and the posted combinations rarely match what the setup allows.
- A read first agent is viable under an ERP change freeze because reading is not treated as risk in the way a write is.
- Exception rules and reconciliation logic describe your business, not the release, so the work carries across if you do migrate.
AI agents for Microsoft Dynamics AX read the ledger you are running now. ChatFin works against AX 2009 and AX 2012 through the interfaces those releases actually expose, does the analysis outside the ERP, and proposes entries for your team to post rather than writing them itself.
That read first shape is not a limitation, it is what makes automation possible on an ERP under a change freeze. ChatFin needs no new customisation in the AOT, no change to the batch schedule and no migration to Dynamics 365 Finance and Operations before it is useful.
AX is still running the close at a lot of companies
Microsoft Dynamics AX is spoken about as a product that has been replaced. In finance departments it is a product that is still posting journals. ChatFin sees AX 2012 R3 running live general ledgers at companies that evaluated Dynamics 365 Finance and Operations, priced the migration, and decided the number was not worth it this year or next.
| Release | Where it sits now | What that means for finance |
|---|---|---|
| AX 2009 | Long out of mainstream support | No vendor side automation is coming |
| AX 2012 and R2 | Out of mainstream support | Customisations are frozen in practice |
| AX 2012 R3 | The most common live release | Batch server and AIF are the integration points |
| D365 Finance and Operations | The successor | A migration, not an upgrade |
That gap is the whole point of this cluster. A finance team on AX has the same close, the same payables backlog and the same receivables ageing as a team on a current cloud ERP, and fewer tools pointed at it. ChatFin works against the AX you are running now rather than against the one you might migrate to.
ChatFin reads the AX you are running today. It does not require a migration to Dynamics 365 Finance and Operations first.
What is actually different about automating AX
Four things, and none of them are the ones vendors usually list.
ChatFin is built read first for exactly this reason. It reads AX, does the analysis outside it, and proposes the entry for a person to post. On an ERP under a change freeze that is the difference between a project that starts and one that does not.
ChatFin reads AX and proposes. The posting stays with your team, which is what makes it viable on an ERP nobody wants to write to.
Financial dimensions are where AX analysis goes wrong
AX financial dimensions are flexible by design, and that flexibility is why two people in the same company will produce different numbers for the same question. ChatFin finds the same pattern in nearly every AX estate.
| What happens | Why it happens | What it costs |
|---|---|---|
| The same cost centre exists twice | Created in two legal entities separately | Totals split |
| A dimension is mandatory in theory | Enforced by a customisation that was relaxed | Blanks |
| Dimension values are reused | An old code repurposed for a new department | History breaks |
| The default dimension differs from the posted one | Set on the vendor, overridden on entry | Two answers |
| Dimension sets differ per report | Each report built by a different person | No tie out |
None of that is visible from a report. It is visible from the transactions. ChatFin profiles the posted dimension combinations rather than the dimension setup, which is how the difference between what was configured and what people actually do shows up.
The batch window decides what is true and when
On a cloud ERP the ledger is more or less current. On AX the ledger is current as at the last batch job that touched it, and finance teams learn the schedule the way they learn a train timetable. ChatFin treats that schedule as data rather than as an inconvenience.
| Batch job | What is wrong before it runs | What breaks if you ignore it |
|---|---|---|
| Vendor invoice posting | Pending invoices are not in AP yet | AP looks understated |
| Inventory recalculation | Cost is estimated, not actual | Margin analysis is provisional |
| Consolidation | Subsidiary balances are stale | Group reporting ties to nothing |
| Currency revaluation | FX positions are at old rates | Unrealised gain is wrong |
| Ledger settlement | Open items look open that are not | Ageing overstates the balance |
An analysis run at the wrong hour is not slightly wrong, it is confidently wrong, and it is the kind of error nobody catches because the output looks normal. ChatFin records the as at time and the batch state behind every figure it produces, so a number that was taken before the recalculation is labelled as such rather than presented as final.
ChatFin stamps the batch state and the as at time on every AX figure, so a number read before a recalculation is never presented as a final one.
Where ChatFin starts on an AX estate
Five places, and they map to the five pages under this one. Each is scoped so it can be run without a write into AX.
Payables
Invoice intake, matching against the purchase order and the receipt, and the exceptions queue. ChatFin reads the open AP transactions and the pending vendor invoice register and works the difference. See AI agents for Dynamics AX payables.
Receivables
Open AR ageing, cash application against bank receipts, and the collections list ordered by what is actually collectable rather than by age. See AI agents for Dynamics AX receivables.
The close
Close task status across legal entities, subledger to general ledger tie outs, and the exceptions that appear after the batch jobs finish rather than before. See AI agents for the Dynamics AX close.
FP&A
Budget against actual by posted dimension, flux with a written reason, and questions asked in plain language instead of built as a new report. See AI agents for Dynamics AX FP&A.
Choosing
What to compare when the alternatives are a close platform, a payables platform and staying manual. See Dynamics AX AI alternatives.
Every one of the five runs read only against AX first. ChatFin proves the analysis on your own data before anything is written back.
This does not replace the upgrade decision
It changes when you have to make it. A finance team automating the work on AX is not choosing to stay on AX forever, it is removing the argument that the close cannot improve until the migration lands. ChatFin is honest about the boundary.
The Dynamics AX cluster
Five hubs under this pillar, each with its own use cases.
Live now
Payables · Receivables · Month end close · FP&A · AI alternatives
Across the function trees
AI for accounts payable · AI for accounts receivable · AI for the month end close · AI for FP&A
Other Microsoft ERPs
Dynamics 365 Finance · Business Central
Questions AX finance teams ask
Does this require moving to Dynamics 365 Finance and Operations?
No. ChatFin reads AX through the interfaces the release already exposes, which on most estates means AIF services and the database rather than a modern API. The analysis happens outside AX and the posting stays with your team, so nothing about the ERP has to change before the work starts.
Our AX is heavily customised in X++. Does that break it?
Customisation changes what the data looks like, not whether it can be read. The part that needs attention on nearly every AX estate is financial dimensions, because the posted combinations drift away from what the setup allows. ChatFin profiles the posted transactions rather than the configuration, so it sees what people actually do.
Is the work wasted if we migrate later?
The rules are not. Exception patterns, the dimension mapping and the reconciliation logic describe how your business operates rather than which release it runs on, so they move across. What does not carry across is anything built as an AX specific customisation, which is one reason ChatFin does not build any.
Where should an AX team start?
The payables exception queue and the open AR ageing. Both are readable without any write into AX, both produce a measurable result inside one close, and both are areas where the gap between what the ERP reports and what is actually true tends to be widest.
Automate the AX you have, not the one you might migrate to.
ChatFin reads AX 2009 and AX 2012 through the interfaces those releases expose, profiles your posted financial dimensions rather than your setup, and works the exceptions outside the ERP.
Every proposed entry goes to a person for approval, which is what makes this viable under the change freeze that comes with an ageing ERP.
Bring one month of AX payables exceptions and one AR ageing.
Book a demoSection photograph: a developer workstation with two monitors showing code, sourced from Pexels and used under the Pexels licence.
Section photograph: a dark desk with a laptop, phone, glasses and a calendar, 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.
Bring one month of AX exceptions.
We will run them through ChatFin against your own AX data and show you what the ERP reports against what the transactions say.