Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

2019 SAP E-Document Mexico (E-Invoice + E-Payment)

Download as pdf or txt
Download as pdf or txt
You are on page 1of 25

SAP

E-DOCUMENT
MEXICO
By Surya Padhi
E-DOCUMENT
REQUIREMENT
Requirement

▪ In accordance with legal requirements in Mexico,


▪ In Mexico, the law requires companies to issue electronic invoices and to use XML-based files as a medium
for invoice exchange. This exchange, referred to as Comprobantes Fiscales Digitales por Internet (CFDI),
involves a customer, a vendor, and a local authorized certification provider (Proveedor Autorizado de
Certificación, PAC). (e-invoice)
▪ When you receive any payment from your customer for an invoice issued earlier, you must generate an
electronic payment receipt complement. You must send this document, together with the CFDI invoice, to
an authorized provider of digital tax receipts (Proveedor Autorizado de Certificación, or PAC) who can
validate the document and send the validated document to the Mexican tax authorities (SAT) for approval.
(e - payment)
E-DOCUMENT
SOLUTION
Available Solution from SAP

The eDocument Full solution allows you to create eDocuments


based on source documents previously created in other SAP
eDocument processing using applications, such as Financial Accounting (FI) or Sales and
Full Solution Distribution (SD). The system uses the Application Interface
Framework (AIF) to map the transactional data to the required
XML format.

The eDocument Basic Enablement allows you to extract the data of


source documents previously created in other SAP applications,
eDocument processing using such as Financial Accounting (FI) or Sales and Distribution (SD), and
Basic Enablement make it available in the database as an eDocument instance for
further processing. You need to implement your own solutions to
do the following:
•Map the data to the legally required XML format.
•Submit the XML to the tax authorities.
Basic Solution

The eDocument Basic Enablement allows you to extract the


eDocument processing using data of source documents previously created in other SAP
Basic Enablement applications, such as Financial Accounting (FI) or Sales and
Distribution (SD), and make it available in the database as an
eDocument instance for further processing. You need to
implement your own solutions to do the following:
•Map the data to the legally required XML format.
•Submit the XML to the tax authorities.

• Development is needed for mapping , formation and transformation of XML.


• Development is needed for mapping , formation and transformation of PDF.
• Development is needed for status update of file transformation
Basic Solution
Process and data flow within E-Document Architecture
1) Create document in
SD / FI

2) Submit the
document

2
1
3) Trigger BADI

3
4) Customer solution

Solution is available for other countries Chile, Croatia, Czech Republic, Hungary, Italy, Peru, Slovenia, Spain and Turkey
Full Solution

The eDocument Full solution allows you to create eDocuments


based on source documents previously created in other SAP
eDocument processing using applications, such as Financial Accounting (FI) or Sales and
Full Solution Distribution (SD). The system uses the Application Interface
Framework (AIF) to map the transactional data to the required
XML format.

• Customer specific developments / enhancement are needed.


• Additional license for use of SAP cloud platform
E-Document – E-Document ( Full Solution)
Process and data flow within E-Document Architecture

Create the source


document

submit the eDocument

retrieves the eDocument

AIF triggers the mapping

system calls SAP Cloud


Platform Integration
SAP Cloud Platform
Integration processes the
XML
SAP Cloud Platform
Integration receives
information

The system updates the


eDocument
E-Document – E-Document ( Full Solution)

E- Document cockpit can handle multiple countries


E-Document – E-Document ( Full Solution)
Technical component and integration of full Solution
E-DOCUMENT
FULL SOLUTION – E-INVOICING
Full Solution - E-Document -> E-Invoice

E-Invoice data flow based on trigger actions


Full Solution - E-Document -> E-Invoice
E-document cockpit is the central place for all functions of e-invoice.

Billing Document (including Submission


Dr. memo / Cr. Memo )

Review PDF Cancellation

E-Document
Cockpit

FI Document ( Including Dr. Review XML


Status
Update
Memo / Cr. Memo)

Sending to
Customer
Full Solution - E-Document -> E-Invoice -> E-Document Cockpit

Submission to SAT Export xml Send to customer Cancel / Delete

Status Check Display xml / pdf Logs


Full Solution - E-Document -> E-Payment – (Status update)

CREATED/CREATE SEND_REQ/REQ_SEND SENT/SENDEDOC ACCEPTED/PAC_RESP

CANCELLED

REJECTED

CANCELLED / CANC_RESP CANCEL_REQ /CANCEL_REQ

SENT To
Customer
E-DOCUMENT
FULL SOLUTION – E-PAYMENT
Full Solution - E-Document -> E-Payment (Data Flow)
E-Invoice data flow based on trigger actions
Full Solution - E-Document -> E-Payment ( E-Document Cockpit)
CPI
PAC
Submission
SAT

Review PDF Cancellation

FI Payment E-Document
Cockpit

Status
Review XML
Update

SAT
Sending to
Customer
PAC

CPI
Full Solution - E-Document -> E-Payment-> E-Document Cockpit
Status Check Display xml / pdf

Submission to SAT Export xml Send to customer Cancel / Delete

Logs
Full Solution - E-Document -> E-Payment ( Status Update)

CREATED/CREATE SEND_REQ/REQ_SEND SENT/SENDEDOC ACCEPTED/PAC_RESP

CANCELLED

REJECTED

CANCELLED / CANC_RESP CANCEL_REQ /CANCEL_REQ

SENT To
Customer
Full Solution - E-Document -> E-Payment

Important information xml


- UUID of payment document
- UUID of billing document
- Billing document # as reference
- Balance payment if any
Full Solution - E-Document -> E-Payment

E-payment of approved and digital


certificate is assigned.
E-DOCUMENT
ENHANCEMENTS
Full Solution - E-Document -> Conclusion

In short,
• For Mexico e-document legal reporting requirement, you can implement SAP's e-
document solution.
• SAP's E document solution comes with two flavors (1) Basic solution and (2) Full solution.
• E-document solution is available for both traditional ERP and S/4 HANA.
• Customer's requirement can be mitigated with enhancement
• With custom enhancement, transition from current solution to e-document solution is possible.
• To enable e-document solution, you need to implement OSS notes, configure
application, develop enhancements.

Thanks, Surya Padhi | suryapadhi@gmail.com

You might also like