FAQ - Mexico's Electronic Accounting Anexo 24

All the information related to the support of the legal requirement Anexo 24 (Annex 24) and all the changes published by SAT (Mexico's tax authority) will be informed in the Announcement SAP Note 2042663. Then, before reading this current wiki, keep in mind that you should review the content of that SAP Note 2042663, because its content is updated with every change in the Mexico's Electronic Accounting solution or changes in the SAT's legal requirement.

Check below if you followed all the instructions or implemented the last version of the released SAP Notes of Mexico's Electronic Accounting. Notice that some SAP Notes have manual pre and post implementation steps.

2042663 Announcement for Electronic Accounting in Mexico
2050349 Chart of Accounts and Account Balances
2066631 DDIC Note
2075584 UUID field for Vendor invoice verification
2091656 General correction
2093023 Information on General Issues
2093189 Journal Entries
2096590 General correction N1
2104844 DDIC Note D1
2105358 JE CFDI Details
2105359 JE Travel Expense Details
2117491 General correction N2
2123987 BAdI FIGLMX_ACC_BAL
2125164 Auxiliary Accounting
2127273 JE Corrections
2127291 General correction N3
2132684 DDIC Note D2
2133659 JE CFDI Details N1
2133660 JE Travel Expense Details N1
2135616 JE Correction N2
2136377 General correction N4
2142967 Auxiliary Report Performance Tuning and XSLT Upgrade
2143807 Electronic Accounting and SAP_FIN 720
2144380 Validation Anio parameter missing
2145283 General correction N5
2145556 Validation SaldoIni parameter missing
2148062 Validation Invalid nomenclature
2148209 Validation XML document cannot be read
2148995 Wrong account information in XML files
2152894 Change in length of the Order number and Incorrect tag
2155001 Error FIGLMX011 No data exists for the specified
2161386 General Correction N6

A - Report of Chart of Accounts and Account Balance:

A1 -  Report parameters: This report has the following execution parameters below.

Company Code: The report can be executed to generate a XML for one Company Code or a consolidated XML for many companies, only if all these companies are part of the same Legal Entity (same Tax Number or RFC) and share the same Chart od Accounts.

FSV (Financial Statement Version): It classifies the accounts according to the Grouping Code of the government and the nature.

Account Group: It allows to limit the accounts selection for one or many account groups.

Period: For which the data has to be selected.

A2 - How to use the report: We suggest you to watch the video from the link below, which is a presentation of the use of the solution.

Electronic Accounting presentation: https://sap.na.pgiconnect.com/p3kbsnihe47

A3 - Field TotalCtas: As per the latest information we got from SAT, the TotalCtas is not needed. SAP is waiting for the new XSD (XML Schema Definition) to be release by SAT. Once it is available, the development team will ascertain all the information reported and correct it if necessary. The current XSD will be changed.

A4 - Dump MESSAGE_TYPE_X CL_GUI_CFW FAGL_GET_GLT0 I_CURTP: Implement the SAP Note 2093023. Notice that the SAP Note 1741346 is a prerequisite for the Mexico's solution to work correctly. If your system already had the code of the SAP Note 1741346, you should review the instructions provided in the content of this SAP Note and follow them. If you face some problem with this SAP Note, we suggest you to open a thread in the link below.

SAP Financials Forum: http://scn.sap.com/community/erp/financials

A5 - Use of Financial Statement Version: In the SAP Note 2042663, there is a guide that explains how the FSV has to be defined. There should be only one level of items. In this level, you have to assign the grouping code of the second level according to what was published in SAT’s website on 04/DEC/2014. Check the example of how the FSV should be in the attached file. The new grouping codes can be found in point B of the new version of the legal requirement, also attached. Also, more details are shown in the attachment of SAP Note 2096590. Notice that if the FSV is not correctly configured, the report will show the error 'Data is not available'. In order to know how to customize the FSV, check the first link below. If you face some problem in FSV, we suggest you to open a thread in SAP Financials Forum, the link is in the topic above.

SAP Help FSV: http://goo.gl/s4Op0E

A6 - Error 'Data is not available': Review the two topics above (A4 and A5). Confirm that you follow all these instructions and the content informed in the related SAP Notes.

A7 - Missing transaction FIGLMX_EACCT: Review the content of the SAP Note 2091656. Check if the SAP Note is applied in your system and if you followed the manual instructions.

A8 - Grouping code: In the rule published it now defines that the accounts have to be mapped to the second level of the grouping code. This means that the accounts mapping has to be done again, this time with the new grouping codes of second level. This new mapping can be done in the existing FSV or a new FSV can be defined for this. Notice that SAT does not expect to get accounts in all the grouping codes of the catalog. The accounts have to be mapped to the grouping code that has the most similar meaning than the information posted in the account. No new accounts have to be created.

A9 - XML format: The formats of the XML files were changed by SAT in 04/DEC/2014. The adjustments to the XML files for the Chart of Accounts and for Accounts Balances are now in process and it will take around some weeks to change the code, test the modifications and create the new SAP Notes. As soon as the SAP Notes are released, it will be informed in the Announcement SAP Note 2042663 and in the list of the SAP Notes in the beginning of this current SAP KBA.

A10 – Field Period: When the report is executed for the balances, the period entered in the execution parameters is the month. So, if executed for period 01, it means that the data selected will be for the period of January, for the period 02 is February, etc. Internally, the report will look for the period variant of the Company Code and will find to which period the month corresponds to. For example, in your case, January is period 03. So if you run the report for period 01 (January), the report will determine that the month of January corresponds to the period 03, and it will get the balances for your period 03.

A11 - GL Account mapping: SAT requires that expenses are classified in Administrative, Sales and Manufacturing, for example. The Electronic Accounting solution proposes the use of FSV, and using this tool, it is possible map GL accounts. Actually, SAT needs to know what is posted in the GL accounts that the companies have. In the law, it is defined that the companies have to assign their accounts to the grouping code that is more similar to what is posted in the account. For example, in the grouping codes, there are two grouping codes for Customers, the Domestic Customers and the Foreign Customers. If a company has only an account for Customers (where both domestic and foreign customers' transactions are posted), they should see from which they have more customers (more business volume). If they have more domestic customers than foreign customers, they should assign their account to the 'Domestic Customers' grouping code. If they have more foreign vendors, they should assign their account to the 'Foreign Customers' grouping code. If you have more questions about the determination of the grouping, contact SAT to get support to determine in which grouping code you have to assign the accounts. From a product perspective, we do not have another possibility to report the information, so you will have to assign the account to one grouping code even though the values might be related to other grouping codes. From the legal requirement, we understand that you cannot have the same account in different groups, so these scenarios will be reported under one group only. The government is aware that this requirement might not be perfect, but they will check what they will get from the companies as per their requirement, and they will do future adjustments. About the product perspective, we do not have another possibility to report the information, as cost centers/cost elements are not reported in the grouping, only the GL Account. You will have to assign the account to one grouping code even though the values might be related to other grouping codes.

B - Report of Journal Entries:

B1 - Main SAP Notes: The solution was provided the SAP Notes 2093189, 2105358 and 2105359. Also, review the list of SAP Notes in the beginning of this current SAP KBA Note. Notice that the government postponed the date to submit the XML file of Journal Entries to June/2015.

B2 - Dump 'IV_DMBTR is unknown': In case you face the dump 'The field "IV_DMBTR" is unknown, but there is a field with the similar name "IV_WRBTR", implement the SAP Note 2133659.

C - Report of Auxiliary of Accounts:

The report to generate the XML file for the Auxiliary of Accounts was released via SAP Note 2125164. Please, remember to review the list of SAP Notes in the beginning of this current SAP KBA Note.

D - Other topics of Electronic Accounting reports:

D1 - Language: According to the law, the information has to be in Spanish. The reports will select the long text of the account in Spanish. If the long text does not exists in Spanish, the English long text will be used instead. In case the GL Account text is not being reported in language Mexican Spanish (1X), follow the content of SAP Note 2096590.

D2 - Field UUID for vendor invoice verification: If you are creating a material invoice (MM) in Mexico, and you need to record the Electronic Invoice Number (UUID), and in some cases the Tax Number (RFC) of the issuer of the invoice, follow the SAP Note 2075584.

D3 - Prerequisite SAP Notes: If you face some issue related to SAP Notes that are prerequisites, check which is the component and open a new thread in the specific forum. For example, you have issues implementing the prerequisite SAP Note 1741346, open the thread in the SAP Financials Forum (link below), because the component of this SAP Note is FI-GL. If you have issues with the prerequisite SAP Note 1497003, open the thread in the SAP Netweaver Forum (link below), because the component of this SAP Note is BC-CCM-FIL.

SAP Financials Forum: http://scn.sap.com/community/erp/financials

SAP Netweaver Forum: http://scn.sap.com/community/netweaver-administrator

D4 - New submission dates for XML files: Notice that the government postponed the date to submit the XML file of Journal Entries to June/2015. Also, the government postponed the date to submit the Chart of Account and Account Balances of January. They have to be submitted at the same time than the Account Balances of February, this is 03/APR/2015. These information were published by SAT in 27/FEB/2015.

D5 - New Journal Entries Auxiliary: This field will not be generated by SAP, because it is used when the Mexico's Electronic Invoices (CFDI) data is not available in the system from where the Journal Entries' file is being generated.

D6 - Special Purpose Ledger and Contract Accounting: The solution does not support SPL and FI-CA data, and also there are no plans to support it.

D7 - Second currency: The solution does not support a second currency, and it is according to SAT's legal requirement Anexo 24. It complies with all the necessary requisites of the Mexican government and that is the purpose of the solution. If it is needed some internal report to provide you the data in USD (Dollar) for example, it is possible to create a z report based in the solution code with this functionality.

D8 - Period selection: Now the solution can be executed by two different date ranges, the first option is '1 to 12', that indicate the months January to December, and the second option is '13', which indicates the special posting periods from 13 to 16, for year-end adjustments.

D9 - Field 'File Name': In order to use this field correctly, you need to check the instructions provided in the description of the SAP Note 2093023. Remember to check if the SAP Note 1497003 is already implemented in your system, and in case it is already present in your system, you need to confirm if you follow all the instructions informed in its description. If you face the errors or dumps with 'The type CL_FS_PATH is unknown', or runtime errors like CALL_FUNCTION_NOT_FOUND or CX_SY_DYN_CALL_ILLEGAL_FUNC, it indicates an incomplete implementation. Be sure to follow the manual steps precisely or import the transports provided in the SAP Note 1497003. Also, more details are shown in the attachment of SAP Note 2096590. If you face some problem with this SAP Note, we suggest you to open a thread in the link below.

SAP Netweaver Forum: http://scn.sap.com/community/netweaver-administrator

D10 - XML corrupted: In case you cannot open the generated XML file in your browser or the browser shows a formating error, it happens because the XML is being generated with a blank line in the beginning of the file. In order to fix it, follow the content of SAP Note 2096590. 

D11 - XML validation: SAP Note 2136377 corrects issues related to validation of the structure of the XML files. Notice that the SAP Note corrects the errors due to the structure of the file, however there might be other errors, such as wrong grouping codes or nature defined in the FSV. The tool provides a short description of the errors found. The link to the validation tool is informed below. Check the attached files of SAP KBA Note 2041490 with an explanation about how the tool works.

SAT's XML Validator tool: https://ceportalvalidacionprod.clouda.sat.gob.mx