ZATCA/FTA compliance for organizations still running Dynamics AX 2012, without forcing an upgrade to hit a compliance deadline.
Dynamics AX 2012 R2 and R3. Earlier versions assessed case by case depending on database schema.
| Method | When we use it |
|---|---|
| SQL / staging table extraction | Standard path — reads directly from AX's SQL Server database via a staging layer. |
| AIF (Application Integration Framework) | Used where AX's own integration framework is already configured and maintained. |
| Middleware connector (dsFatoora) | Validates, signs and submits; writes clearance status back to AX. |
AX 2012's core financial posting logic is stable and well understood after years of production use — the gap isn't reliability, it's the absence of any e-invoicing framework at all.
AX 2012 has no native e-invoicing or ZATCA/FTA compliance capability. Every part of the pipeline — validation, XML generation, signing, submission — has to be added externally.
We read invoice data directly from AX's database via a staging extraction layer, run it through the full dsFatoora compliance pipeline, and post clearance status and QR data back against the original AX transaction — giving you a compliant path on your current version while you plan any future migration on your own schedule, not the regulator's.
No. We integrate directly with AX 2012 via database extraction — no upgrade required to meet a compliance deadline.
We extract from a staging/replica layer, not the live transactional database, to avoid any performance impact on AX itself.
Yes — the data mapping work done for compliance is directly reusable groundwork if you later migrate to D365 F&O.