Since August 2025, Mexico's DIOT (the monthly report of VAT paid to suppliers) can only be filed on the SAT's new online platform, and the bulk-upload file grew from 25 to 54 fields per supplier. Many companies running SAP still build that file in Excel every month. It can come straight from SAP, but only if VAT accounting is right at the source.
What changed with the new DIOT
- Online platform only: the desktop application is gone; the return is filed on the SAT portal with e.firma, by manual capture or by uploading a TXT file.
- 54 fields per supplier: VAT is broken down in more detail (by rate, creditable and non-creditable, imports, withholdings and returns).
- Same deadline: the law sets the 17th of the following month, and the annual tax rules have allowed filing until the last day of that month.
What SAP needs to generate it
The DIOT reports VAT actually paid to each supplier. If your SAP posts VAT when the invoice arrives instead of when it is paid, no report will reconcile. Before worrying about the file, check these four points:
- Cash-basis VAT: tax codes that post VAT as pending on the invoice and transfer it to creditable VAT when the payment clears. We explain it in Cash-basis VAT in SAP S/4HANA for Mexico.
- Supplier master data: RFC (Mexican tax ID), third-party type (domestic, foreign or global), operation type and, for foreign suppliers, tax ID and country.
- Cleared payments: payments must clear the invoice (F110 or F-53 with clearing). A payment posted on account without clearing does not transfer VAT.
- Special cases configured: VAT withholdings, credit memos, down payments, partial payments and foreign-currency invoices.
Two ways to build the report
| Option | When it fits | Considerations |
|---|---|---|
| SAP standard (Mexico localization / Document and Reporting Compliance) | Your S/4HANA release already ships the new layout and SAP notes apply cleanly. | Depends on release and installed notes; in systems run by a foreign headquarters, it must be coordinated with them. |
| Custom (Z) development | The standard is not available, your release is old or you need your own grouping rules. | Reads the transferred VAT items and builds the 54-field TXT; must be maintained if the SAT changes the layout. |
Either way, the heavy lifting is in configuration and data, not in the program.
The errors we see most
- VAT posted as creditable at invoice time, so the monthly DIOT never matches payments.
- Suppliers without RFC, with a generic RFC or without operation type, rejected on upload.
- Partial payments that transfer all of the VAT, or none of it.
- Tax codes inherited from a foreign corporate template that do not distinguish Mexican rates.
How to start
Take the last DIOT you filed and compare it with the payments posted in SAP. The differences tell you exactly what to fix. We can review it with you: book an assessment or see our SAP Mexico tax localization service.
Frequently asked questions
Does SAP generate the 54-field DIOT out of the box?
It depends on the release. SAP published notes for the new layout within Mexico localization, and recent S/4HANA releases cover it through Document and Reporting Compliance. On older or heavily customized systems a custom report is often the better choice.
Why doesn't my DIOT match creditable VAT?
Almost always because VAT is posted when the invoice is received rather than when it is paid, or because some payments do not clear the invoice. The DIOT reports VAT actually paid.
Can I generate the DIOT from SAP if headquarters abroad runs the system?
Yes. Configuration is limited to the Mexican company code (tax codes, accounts and supplier data) and is coordinated with the corporate team for transports and testing.