The Mexico eAccounting mandates are set to take effect on March 3rd, 2015 and there is still no end to end solution from SAP. Actually, there are some very glaring gaps to take into consideration. You still have time to address these issues with end to end solution providers. Continuing to wait puts you at risk for missing the deadlines and fundamentally putting an audit bull’s-eye on your back.
More importantly, the infractions defined on the SAT website could be upwards of $3,000 USD per error and a backing out of deductions. At best, this is cash flow delayed on deductions, at worst this is significant fines. When you consider that for every peso the Mexico SAT spends on audits, they collect 61 pesos of additional revenue – what do you think they are going to do?
So here is what you need to know – about the current gaps that have been nicely complied on an SCN Wiki:http://wiki.scn.sap.com/wiki/display/LOCLA/Electronic+Accounting
OUT of SCOPE – in other words if you fall into these categories – an OSS note strategy will not work and you will be forced to do Z-programs or look at a vendor such as Invoiceware who can solve not only the SAP CFDI issuing, SAP CFDI XML validation from suppliers, and eContabilidad as a single package.
The standard SAP Electronic Accounting solution for Mexico (eContabilidad) does not support:
- Companies that can’t create an FSV
- SPL: Special Purpose Ledger data
- FI-CA: Contract Accounting data
- Report data in a second currency
- Auxiliary reports still need correlated data between SAP and the report – don’t forget the correlation.
- Balance report executed by dates ranges, it can only be executed for a specific period. This is a larger issues as even if you run 12 periods, many companies don’t run them exactly to the calendar month as requested by the Mexico SAT. What if the January period ends January 23rd as an example? It is also possible that you run up to 16 periods – again standard OSS notes will not work for you. Here is a direct quote from the community – “I'm also confused why "report executed by date range" is suddenly out of scope. It's a legal requirement, so how can it be just declared "out of scope" and still count as if SAP "supports" this?”
OSS Notes for the Journal Entries are not out todate! And current discussions say will be a consulting project not a standard solution.
The most important issue is the UUID and the Polizas and those notes aren’t even finalized– the first two reports just trigger audits – the third report is what is used to justify deductions, avoid penalties and allow you to take a tax refund.
From SCN: For Electronic Accounting, you need 3 XML, GL, balance and accounting document files are needed, the first two are very simple to keep track of. The last file which is the accounting document with the UUID of customers, suppliers, expense accounts, payroll is the complicated one.
Part of the data needed for this XML file, in case of income or expense Journal Entries, is the CFDI information: "UUID" (e-invoice number), the "RFC" (Tax Number of the issuer of the e-invoice) and the amount.
- The UUID* is a 36 char data.
Even with a MIRO container, there needs to be a way to get those UUID into the SAP system and ensure they are correct. Remember the accuracy of the codes is mission critical as that UUID code is what will be used to automate the audit against the government systems.
So you need to understand the realities of SAP OSS notes and the lessons learned from the easy reports, let alone the difficult one (the Journal Entries) that will have to consider 3rd party solutions. Ensure you spend time looking at your back-up plans and additional vendors who can handle these customizations as part of their solution approach.