Mexico CFDI 3.3 invoice in SAP S/4HANA Cloud

The e-invoice in Mexico is the final document in an regular  OTC process. CFDI 3.3 document is the only valid invoice document for the fiscal Mexican authorities.

In this blog post we will see how to prepare the system to trigger the electronic invoices document for the customers using the standard functionality for Mexico localization in SAP S/4HANA Cloud.

We will start with the first steps of configuration of the localization for e-inoice for Mexico.

Configure Value Mapping.

With the role of Configuation Expert (BR_CONF_EXPERT_BUS_NET_INT) open the app of Configure Value Mapping.

This process steps show you how to create the required value mapping for generate the electronic invoices.

Blart, payment document types

CFDI_PAYMETHOD Assign SAT(Mexican fiscal authorities) Payment Method codes. Those are the relation between SAP payment terms and SAT payment method codes (all the SAT codes catalog you can find it in the web page of the SAT).

CFDI_PAYMNT_MEANS Means of payment. Relation between payment method from SAP S/4HANA Cloud and payment means of the SAT authorities.

CFDI_TAXES_ASSIGN Assign SAT Tax types and factor types. You need to assign all the tax types you will be use in SAP S/4HANA Cloud and the relation with the SAT tax type.

CFDI_USAGE  Use of CFDI for correponding customer. Assign the corresponding CFDI usage at your customers, according at the type of transaction (This information is available in SAT catalog of CFDI in SAT government portal).

Note: In case you need to create your own logic for filling CFDI_USAGE per customer, you can implement the localization BADI for Mexico Usage of CFDI, this BADI is called during the maping of the XML, which is triggered when you submit an eDocument from the Mexico eInvoice processes of the eDocument Cockpit.

DOC_TYPE Document type. Identify for the SAT authorities what kind of transaction (incoming or egress) represent the document types used in SAP S/4HANA Cloud.

FORMA_PAGO Method of payment of the transaction.

PRODUCT_CODE Assign Product/Service codes to material numbers. It is the relation between the SAP products or services codes in your SAP S/4HANA Cloud system between the SAT codes, provided in the SAT catalog that you can download from SAT portal.

SERVICE_PROVIDER Assign service provider for a company code. Assign the name of your PAC (authorized supplier by the SAT to certified the e-invoice) provider for your company code.

TIPO_RELACION Relation type based on related document type. Relation between CFDI (SAT) documents and SAP S/4HANA Cloud documents.

UNIT_OF_MEASURE Value mapping for UOM with SAT description. Assign the relation between the unit of measures in SAP S/4HANA Cloud and SAT unit of measures (available in the SAT catalog mentioned above).

After you end all those previous steps, you can trigger you e-invoice documents, below show you how after invoice document is generated in billing in the create billing documents app, the invoice document is trigger to e-document cockpit.

In e-document cockpit we can see our invoice document, in preview status to be submitted to the PAC.

Once the invoice it´s submitted if everything was configured correct and the connection with the PAC it´s in place, you will see the status change in green color and the message “accepted by the authorities” that means your document have all the fiscal requirements and the XML document obtain the fiscal stamp and it´s a valid document as the image below..

The image below is the xml sample of the invoice triggered above.

Additional you can see the representative printing version of the XML obtained.

In conclusion

We saw from functional perspective all the previous requirement to configure the value mappings to obtain e-invoice document in Mexico will all the requirements needed by fiscal authorities, using the standard functionality of SAP S/4HANA Cloud.  Please follow all the steps and follow our best practices to obtain the reach the goal in SAP S/4HANA Cloud.

Please feel free to contact me by direct message or an e-mail, thanks.