3. 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)
5. Available Solution from SAP
eDocument processing using
Full Solution
eDocument processing using
Basic Enablement
The eDocument Basic Enablement allows you to extract the data of
source documents previously created in other SAP 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.
The eDocument Full solution allows you to create eDocuments
based on source documents previously created in other SAP
applications, such as Financial Accounting (FI) or Sales and
Distribution (SD). The system uses the Application Interface
Framework (AIF) to map the transactional data to the required
XML format.
6. Basic Solution
eDocument processing using
Basic Enablement
• 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
The eDocument Basic Enablement allows you to extract the
data of source documents previously created in other SAP
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.
7. Basic Solution
1
2
3
4
1) Create document in
SD / FI
2) Submit the
document
3) Trigger BADI
4) Customer solution
Solution is available for other countries Chile, Croatia, Czech Republic, Hungary, Italy, Peru, Slovenia, Spain and Turkey
Process and data flow within E-Document Architecture
8. Full Solution
eDocument processing using
Full Solution
The eDocument Full solution allows you to create eDocuments
based on source documents previously created in other SAP
applications, such as Financial Accounting (FI) or Sales and
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
9. E-Document – E-Document ( Full Solution)
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
Process and data flow within E-Document Architecture
13. Full Solution - E-Document -> E-Invoice
E-Invoice data flow based on trigger actions
14. Full Solution - E-Document -> E-Invoice
E-Document
Cockpit
Submission
Cancellation
Status
Update
Sending to
Customer
Review XML
Review PDF
Billing Document (including
Dr. memo / Cr. Memo )
FI Document ( Including Dr.
Memo / Cr. Memo)
E-document cockpit is the central place for all functions of e-invoice.
15. Full Solution - E-Document -> E-Invoice -> E-Document Cockpit
Submission to SAT
Status Check
Export xml
Display xml / pdf
Send to customer
Logs
Cancel / Delete
16. Full Solution - E-Document -> E-Invoice – (Status update)
CREATED/CREATE SEND_REQ/REQ_SEND SENT/SENDEDOC ACCEPTED/PAC_RESP
CANCEL_REQ /CANCEL_REQCANCELLED / CANC_RESP
SENT To
Customer
REJECTED
CANCELLED
18. Full Solution - E-Document -> E-Payment (Data Flow)
E-Invoice data flow based on trigger actions
19. Full Solution - E-Document -> E-Payment ( E-Document Cockpit)
E-Document
Cockpit
Submission
Cancellation
Status
Update
Sending to
Customer
Review XML
Review PDF
FI Payment
CPI
PAC
SAT
SAT
PAC
CPI
20. Full Solution - E-Document -> E-Payment-> E-Document Cockpit
Submission to SAT
Status Check
Export xml
Display xml / pdf
Send to customer
Logs
Cancel / Delete
21. Full Solution - E-Document -> E-Payment ( Status Update)
CREATED/CREATE SEND_REQ/REQ_SEND SENT/SENDEDOC ACCEPTED/PAC_RESP
CANCEL_REQ /CANCEL_REQCANCELLED / CANC_RESP
SENT To
Customer
REJECTED
CANCELLED
22. 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
23. Full Solution - E-Document -> E-Payment
E-payment of approved and digital
certificate is assigned.
25. 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