Tuesday, March 8, 2011

SAP, Mexico e-Invoicing and Servicio de Administración Tributaria

Most of us are aware by now that Mexico mandated some new real time requirements for e-invoicing that went into effect on January 1, 2011.  I have been in conversations with several folks within the SAP ecosystem that are now having difficulty supporting these requirements with on-premise SAP solutions.

These new requirements are changes from 2010's e-invoicing requirements.  The concept of the folio number is now gone, and there is a requirement to support real-time exchanges of data with SAT.

Some of the new requirements, as identified in this press release from Crossgate are:

  • Regulatory compliance checks with government-certified organizations for both senders and receivers of invoices.
  • Outgoing invoices must be prepared in a specific XML format and authorized in advance.
  • Invoices in excess of 2,000 Pesos are required to be approved digitally.
  • Incoming invoices must be externally validated, then archived and stored.
  • Folio numbers have been eliminated and replaced by the Timbre Fiscal, which includes the signed “Sello del SAT,” along with a 32-character UUID code that is assigned by the SAT and remains globally unique throughout all invoices created in Mexico.
The press release that listed these requirements also stated announced that Crossgate, a global e-invoicing services company (co-owned by SAP) that specializes in supporting SAP customers, has recently implemented support for these requirements in 11 global companies.  They support these new requirements in a cloud computing SaaS business model that is integrated with SAP.

************************************************

Kevin R Benedict Independent e-Invoicing/EDI Consultant, Analyst and Blogger
Join the SAP EDI and SAP Information Interchange group on Linkedin:
http://www.linkedin.com/groups?about=&gid=2884582&trk=anet_ug_grppro


*Full Disclosure: I am an independent consultant that has worked with and for many of the companies mentioned.

No comments:

Post a Comment