As previously indicated, we strongly advise your company to investigate packaged solutions to address SAP compliance for Mexico CFDI. The following is the structure you will need to design, nevertheless, if you want to comprehend the complexity and process flow for an outbound invoice in Mexico. Keep in mind that sending and receiving from the government is only one step in the process. The SAP configuration work is the most underappreciated task in any Mexico e-Invoicing implementation. Here is an example of the CFDI creation inbound operations in Mexico:
- The customer creates a SAP invoice using the regular SAP procedure to start the process (like the SAP VF01 transaction). According to standard SAP processing, this causes the generation of a billing document, during which your end solution should generate an IDOC and send it to your middleware solution for XML transformation. Traditionally, SAP tRFC is used for this. The most neglected part of every project is the SAP setup used to generate this IDOC and internally manage the process. Don’t underestimate the amount of labour involved or the ongoing configuration modifications that will be required as laws change over time.
- The outbound IDOC should be received by your CFDI compliance solution, which should then extract and package the data into SAT-compliant XML before sending it for fiscal validation, signing, and approval.
- Your Compliance Server will record the incoming message, check it for compliance with the required properties, and sign it using the digital seal certificate that was issued to you by the government. The SAT servers receive the message in real time, validate it, and approve it as two asynchronous messages.
- The best approach is to poll in real-time for the approved SAT messages (along with the SAT assigned timbre string), log them in a long-term archive repository, and then reroute them back into your technological landscape for printing and updating to SAP.
- At all times, SAP should receive status messages for monitoring. This is necessary for your end users to keep track of the flow and to have audit-ready data in case the government makes a request. Along with progress notifications, you should incorporate functions like contingency mode, invoice cancellation, receiving, reject/retry, and the ability to see and print the invoice into the SAP system. The back-end system needs to be configured for these.
- The IDOC and the SAT-assigned protocol number are transformed into a human-readable invoice format and printed as supplementary shipment documentation to be delivered with the package after receiving approval from the government. It’s common to ignore the intricacy of printing and “extended properties.”
- Additionally, it is anticipated that the Invoice output format would remain constant across all SAP billing kinds and output conditions.
- The SAT normally mandates that the electronic invoice be sent to the recipient concurrently with the delivery of the products when the client so requests. You must include this in your process flow because in Latin America, this is often done by email. The recipient will then have an electronic copy of the invoice to compare the printed output to whenever the products actually arrive on the truck when it arrives.
- The printed invoice may travel with the truck for possible inspection by law enforcement or customs agents at any time throughout its route. To verify the legitimacy of the products movement, the official can scan the bar-code printed on the PDF and check it with the SAT servers in real-time. Finally, the receiver can authenticate the printed invoice using this same channel after the products have reached their final destination.