Skip to Content
Technical Articles

Reporting Payments in SAP S/4HANA for advanced compliance reporting for Mexico eAccounting Reports

When you report Electronic Accounting in Mexico, you need to inform how your company’s payments were performed. Basically, SAT (Servicio de Administración Tributária) – which is the legal institution that regulates taxes in Mexico – wants to know what payment method was used (check, bank transfer…) by your company and further details (banks involved, check number…) of the financial transactions.

In this post, we explain how the Auxiliary Report for Folios determines the payment method of journal entries and how the Journal Entries Details report finds the payment details and banks in the SAP S/4HANA system.

Determination of Payment Method in Journal Entries

The payment method used by your company in financial transactions is reported to the Mexican government through the Auxiliary Report for Folios, in the element MetPagoAux of the XML output file. When informing the payment method, you need to follow a pre-defined SAT catalog for payment methods. You can find the catalog in SAT website, under Catálogo de métodos de pago.

In the SAP S/4HANA system, the payment method is a one-character long information that is present in the FI invoices and payment documents, on the supplier and customer line items.

As SAT requires that the payment method value of the documents is informed according to its catalog, a mapping configuration is required to map the value that you enter in the SAP system to the value required by SAT in the catalog.

You can set this mapping through the Specify Mapping for External Payment Method customizing activity, that is in the SAP Customizing Implementation Guide, under Financial Accounting > General Ledger Accounting > Periodic Processing > Report > Statutory Reporting: Mexico > Specify Mapping for External Payment Method (V_FIMX_PAYM_MAP).

Once you have specified this mapping, your company’s payment methods will be informed in the Auxiliary Report of Folios output XML file.

Finding Payment Details in SAP S/4HANA

Even though the payment method information is not required in the Journal Entries Details report, you need to report payment details information.

The payment details are reported in the Journal Entries Details report in three different nodes of the XML output file: Check, Bank Transfer and Others. The report determines which node to fill based on your configuration for payment methods. So, the Specify Mapping for External Payment Method (V_FIMX_PAYM_MAP) customizing activity is also relevant for the Journal Entries Details report, and you should go through it before running the report in your system.

Payment methods configured as 02 (Cheque) will have the details included in the Check node, while payment methods configured as 03 (Transferencia) will be included in the Bank Transfer node, and any other will be included in the Other node.

The Journal Entries Details report fetches the payment details from the REGUH (Settlement data from payment program) and PAYR (Payment Medium File) tables, which contain the payment details generated by the Automatic Payment Transactions: Status program (F110 transaction).

Payments made through transactions that don’t update REGUH table, for example, F-28 and F-53 transactions, won’t have its details automatically fetched by the Journal Entries Details report. To report data from these payments, you’ll need to enhance the Journal Entries Details report through the Define Compliance Reports Fiori app. This way, the report reads data for these payments from your custom table.

Bank Key

One piece of information that is also required in the payment details of checks and bank transfers that you report in the Journal Entries Details report are the banks involved in the financial transactions. Similar to the payment methods, SAT requires that you report the bank information according to a pre-defined catalog.

To meet this requirement, when the Journal Entries Details report is reading data from REGUH table, the following logic is applied: for national banks, the report considers the first 3 digits of the bank key, and for foreign banks, the report sets automatically the ‘999’ value.

Having said that, mind to review if your system master data is correctly maintained for Mexican banks as per defined in SAT bank catalog, under Catálogo de bancos.

We hope this post is helpful for you. Now you know how you can stay fully compliant with payments reporting for eAccounting in Mexico.

Do you have questions about Mexico eAccounting Reporting in SAP S/4HANA for advanced compliance reporting? Check our SAP FAQ Note.

You can find the full documentation for Mexico eAccounting Reporting in SAP S/4HANA for advanced compliance reportingin the SAP Help Portal, under help.sap.com/viewer/s4h_op_mexico.

Follow the Advanced Compliance Reporting tag in SAP Community to stay tuned on the latest news about SAP S/4HANA for advanced compliance reporting for Mexico.

#SAPGoGlobal #SAPLocalization

Be the first to leave a comment
You must be Logged on to comment or reply to a post.