Mexican Tax Compliance
CFDI 4.0, DIOT and electronic accounting: what an ERP automates and what stays manual
How much Mexican tax compliance an ERP handles out of the box for CFDI 4.0, DIOT and electronic accounting, and what is still manual work.
· 5 min read
A company that already has an Oracle ERP or Oracle NetSuite usually assumes that Mexican tax compliance comes solved out of the box. Oracle's and NetSuite's Mexico localization covers the foundation; what is missing depends on how it is configured and on what each operation requires, and it tends to show up as a surprise in the first audit or the first request from the SAT (Mexico's tax authority).
This article is not tax advice. It explains what the SAT requires for three specific obligations, CFDI 4.0 (Mexican e-invoicing), DIOT (the Mexican VAT report on third-party transactions) and electronic accounting, how much of that a standard ERP handles, and what you should always validate with your tax team or your accountant.
What the SAT requires today for CFDI, DIOT and electronic accounting
According to the SAT, CFDI 4.0 has been in force since January 1, 2022, and is the mandatory version for issuing invoices. Among the changes from earlier versions, the recipient's name or legal name, tax regime and postal code are required data on every invoice, and there is a specific field to indicate whether the transaction is an export.
The DIOT, the Informative Return of Transactions with Third Parties, requires monthly reporting to the SAT of the VAT (IVA) transactions made with suppliers, using the A-29 format. According to the SAT, it is filed in the month immediately following the one the information corresponds to, with no minimum amount per transaction.
Electronic accounting requires periodically submitting to the SAT the company's chart of accounts and its trial balance, in the XML format defined by Annex 24 of the Miscellaneous Tax Resolution. It is an obligation derived from Article 28 of the Federal Tax Code.
What an out-of-the-box ERP covers
A well-configured Oracle or NetSuite ERP handles the structural part of all three obligations. It generates the CFDI with the fields the Mexican standard requires, maintains a chart of accounts and a trial balance that can be extracted, and organizes supplier transactions in one place instead of scattering them across emails and loose invoices.
That foundation is what makes compliance possible. It is not, by itself, compliance. The difference between the two is precisely the part you see least until it fails.
What is completed with custom add-ons
Oracle and NetSuite have a Mexico localization that covers the foundation. The SAT publishes changes frequently and each operation has its own requirements: the exact format of Annex 24, the stamping mechanics with an authorized provider, supplier validation under Article 69-B of the Federal Tax Code (blacklisted suppliers). At CETERiS we configure that foundation, connect it to the PAC (authorized certification provider for e-invoices) and complete it with custom add-ons.
In practice, that means the ERP's chart of accounts needs to be mapped to the account grouping code the SAT requires for electronic accounting, the stamping process needs to be connected to an authorized certification provider, and the DIOT needs to correctly extract the VAT detail by supplier from the transactions that already live in the system.
None of these three steps is exotic. They are configuration work and, in some cases, a targeted development on the ERP, not a limitation of the product itself.
Why you should review the localization layer in a global ERP
A global ERP like Oracle or NetSuite first organizes the accounting and business structure that works in any geography, and on top of that adds a localization layer for each country where it operates.
That Mexican localization layer exists and can be implemented well. The point of this article is that its scope is defined in the project, and that assuming it is automatic is what leaves gaps that nobody decided on purpose.
How to tell whether your current ERP leaves you exposed
There are specific questions that help you see whether the tax side was completed or only half done.
- Is the ERP's chart of accounts mapped to the account grouping code the SAT requires, or does someone translate it by hand every period?
- Does the trial balance come straight out of the system in the correct format, or does it go through a manual adjustment before it is sent?
- Is the DIOT built from an ERP report or from a manual reconstruction of supplier invoices?
- Does the system check against SAT lists before registering a new supplier, or does that review depend on someone remembering to do it?
If several of these answers end in manual work, it is not necessarily an error in your implementation. It is a part of the scope that may have been left out, and it is worth reviewing with your tax team before it shows up as a finding in an SAT review.
It bears repeating plainly: this article does not answer any of these four questions for you, and no decision about how to file or how to correct an SAT finding should be made without your tax team or your accountant reviewing it first. What can be assessed from the ERP is whether the information those teams need comes out of the system cleanly or depends on manual work that can be automated.
This article does not replace a tax opinion on your particular case. Tell us which ERP you have and which part of CFDI, DIOT or electronic accounting is still being handled by hand, and we will review it together with what your tax team has already validated.
Sources
How we can help
Facing something similar?
Tell us which system you run and what it can't do for you today. The first conversation is about understanding your situation.
Request an assessment
Free guide · 24 pages · In Spanish
From Excel to ERP: how to tell if it's time
What we'd tell you in a first assessment meeting, in writing: how to know whether you need an ERP, what it costs in estimated ranges and how to migrate without disrupting operations. Currently available in Spanish; English edition coming soon.
- The 7 signs you've outgrown spreadsheets
- What an ERP costs and what drives the price
- The 5 most expensive mistakes
- A checklist to decide whether it's time