Product Information
SAP Document Compliance Solution for KSA E-Invoicing Phase One
SAP Localized Solution for Saudi Arabia (KSA) e-invoicing Phase One is now available for SAP ERP and SAP S/4HANA.
KSA localized E-Invoicing Solution helps SAP customers comply with Zakat, Tax and Customs Authority (ZATCA) Electronic Invoicing (FATOORAH).
Solution Overview
- eDocument framework SAP Document Compliance has been developed by SAP Globalization Services to comply with local regulations mandating the use of electronic documents to be sent to business partners and/or legal authorities.
- SAP Note: 3095262 – SAP Document Compliance Saudi Arabia: eInvoicing
- Supported types of documents:
- Customer invoices created from billing or accounting documents
- Supplier invoices (Self-Billing Invoices)
- Credit notes
- Debit notes
- Special Scenarios:
- Nominal supply
- Exports invoices
- Summary Invoice
- The Solution helps you to generate Electronic Invoices and their associated Notes in XML file format as per the Provisions of the E-Invoicing Regulation.
- The Solution generates a QR code and is embedded in the XML file. The QR code can be extracted using printing programs to be printed in any Human Readable Format (such as PDF Forms).
- The Solution allows you to share/send the generated XML file with the buyer via email or any other electronic channel.
- The Solution helps you to save time and effort for the implementation of Phase Two (integration) of KSA E-invoicing (FATOORAH) starting from January 1, 2023.
Product and Solution Videos
Implement SAP eDocument Framework:
- If you are already using Document Compliance, then you need to ensure that all
the SAP Notes are implemented. - If you are not using Document Compliance, then you need to go through the SAP Document Compliance product page and choose Implement and follow the instructions.
Implement SAP Solution for KSA E-Invoicing Phase One
Implement KSA E-Invoicing Phase One via the following SAP Notes:
-
- 3095262 – SAP Document Compliance Saudi Arabia: e-Invoicing
- 3095273 – SAP Document Compliance Saudi Arabia: Consumer Proxy Generation
- 3095264 – SAP Document Compliance Saudi Arabia: DDIC Objects – Prerequisite for 3095265
- 3095265 – SAP Document Compliance Saudi Arabia: Mapping Enablement and Code Correction
Mapping Fields to the XML for Saudi Arabia E-Invoicing Localized Solution
The system uses the Application Interface Framework to map the fields of the source documents to the electronic document, normally an XML file. You can determine how the system fills some of the fields by defining value mappings or fix values.
- Configuring Allowance Condition Type (ALLOWANCE_COND_TYPE)
Use this value mapping to maintain the condition types used for allowances. (Discount). - Configuring Reasons for issuance of credit / debit note for SD (CR_DB_REASON_SD)
Use this value mapping to maintain the reasons for the issuance of credit/debit notes. - Assigning eDocument Type to Billing Document Type (EDOCUMENT_TYPE_SD)
Use this value mapping to map the eDocument type to the Billing Type. This mapping is used to determine the eDocument Type while creating the eDocument. - Configuring Exchange Rate Type for the Company Code (EXCHANGE_RATE_TYPE)
Use this value mapping for maintaining the Exchange Rate Type (One Entry) which your company is using to exchange to SAR. - Configuring Invoice Type Code and 3rd Party Inv. Ind. for FI (INVOICE_TYPE_CODE_FI)
Use this value mapping to map the invoice, credit note, and debit note type codes defined in your system with the external values accepted by the Tax authority. - Configuring Invoice Type Code and 3rd Party Inv. Ind. for SD (INVOICE_TYPE_CODE_SD)
Use this value mapping to map the invoice, credit note, and debit note type codes defined in your system with the external values accepted by the Tax authority. - Configuring Payment Means Code (PAYM_MEANS_CODE)
Use this value mapping to map the payment method defined in your system with the external values accepted by Tax Authority. - Configuring Partner Function for Customer (SALES_ORG_PART_FUNC)
This value mapping is relevant for billing documents only. Use this value mapping if you want to display in the XML different information per sales organization for customer or for contact than the default used by the system. - Configuring Tax Category and Nominal Invoice Indicator (TAX_CATEGORY)
Use this value mapping to map the specific tax codes in your system to the tax categories required by Tax Authority. - Configuring Tax Exempt Reason Code (TAX_EXEMPT_CODE)
Use this value mapping to map the specific tax exemption codes in your system to the ones required by the Tax authority. - Configuring Tax Period (TAX_PERIOD)
Use this value mapping for maintaining the Tax Period (Quarterly/Monthly) which your company is following. - Configuring Unit of Measure in ISO (UNIT_OF_MEASURE_CODE)
Use this value mapping to map the internal unit of measure code (BUn) configured in your system to the one required by the Tax Authority. By using this value mapping, it isn’t necessary to change the configuration you’ve done in the CUNI transaction.
For more info, please refer to the SAP Note 3095262 – SAP Document Compliance Saudi Arabia: eInvoicing
Products Links:
Give us your feedback
To ensure that we’re covering what you need, please leave your feedback at the bottom of this blog post!
Regards,
Mohamed Latif
#SAPGoGlobal #SAPLocalization
Hi Sir..
Thanks for the blog..much informative and helpful one..
I followed all the above steps you mentioned but while generating XML or display button using SAP transaction code "EDOC_COCKPIT", an error message is showing "The data object could not be created: The type does not exist." with Message ID EDOCUMENT000.
I rechecked all the configuration and also the SAP troubleshooting guide 2530509.
Where possibly the fix need to be done so that I could able to generate XML.
Thank you..:)Waiting for your response.
Hello Sitesh,
Hope you are doing well, I am facing the same issue EDOCUMENT000, If you found the root cause of it please share with me.
Please check:
https://answers.sap.com/questions/13717502/xml-generation-fails-in-edocument-cockpit.html
Hi Sitesh Behera,
Thanks for your comments
You can raise an incident to the component “CA-GTF-CSC-EDO-SA” to get the required support.
Best Regards,
Hi Sir,
where the QR code is stored in SAP for E-document.
Waiting for you response...
Hi Behera,
It’s stored on the SAP eDocument database table EDOSAINV.QR_CODE
Regards,
Hi Sir,
Thanks for the information.. In generated XML form EDOC_COCKPIT there is node called QR and it's value is stored in 'EmbeddedDocumentBinaryObject'.
Is there any way to decode QR string into image QR via ABAP or any other means? and What is the use of that QR node in XML?
I would be appreciate if you could please share the solution.
Waiting for your response.
Regards,
Sitesh
As per SAP FAQ, first phase QR code is not compulsory on Invoice output.
If you are using Adobe form then the following document will help you to accomplish you what are looking for.
https://blogs.sap.com/2020/09/25/printing-qr-code-and-digital-signature-in-adobe-forms/
Saudi Arabia FAQ https://jam4.sapjam.com/groups/aDJPUFaeB2noMhwk999hKH/documents/Y9uY3wGULREflpUTMLVslH/slide_viewer
Phase 1 and 2
Hi Shrinivas,
Thanks for your response.
Can we decode the following QR code.. From the above solution we would generate the same below string in the QR code. But I was looking for decode this string and extract the information into a template(Smartform or Adobe Form) which is encoded in this below string...
Waiting for your response...Please correct me if my approach is wrong...
Country specific / Saudi Arabia is Not found in SPRO
we implement all note in installation steps
https://help.sap.com/viewer/79f3a0e33a974335951a4344e42ea4c4/6.18.17/en-US/70d4d5b4ff374e529d5d59c0f22929b1.html
Version : S4CORE : 102 SP 0
is it an issue or it is normal for our SYSTEM version ?
Hi Ramy,
We do not have country-specific settings to be updated for the Saudi Arabia solution, that is why we don't see Saudi Arabia in SPRO
Regards,
Hi Latif,
Thank you for sharing this information.
Could you please confirm or not that the Invoices from RE-FX are included in this solution scope.
(in the SNotes shared by you, I can't find any information about RE-FX)
If Yes, could you share the SAP Notes or documentation ?
Regards,
Taoufik.
Hi Taoufik,
RE-FX is not included in the solution scope
Regards,
Latif
Hi Mohamed,
Good Morning!!
My self Srinivas Taduka, We are trying to install SAP AIF frame work in our local SAP system for Saudi Arabia.
Actually we got an issue while implementing the note 3095265. ( issue - some objects are not available in class ).
After reading through the main SAP note 3095262, it says we need to implement 3084687 for Saudi Arabia.
We tried to implement the note 3084687, but it has lot of pre-requisites.
We are not understanding what we are missing for Saudi or AIF frame work installation.
Kindly help on this issue.
Appreciate your help!!
Thank You,
Srinivas
Hi Srinivas,
To get the required support, you can raise an incident to the component “CA-GTF-CSC-EDO-SA”
More Info and documents relevant to KSA e-invoicing are available on MENA Localization Jam
Thanks,
Latif
Hi Mohamed,
We have successfully implemented AIF,TCI & Saudi specific notes ( total 36 notes ) in our system. Thank you for the information and help.
Thank You,
Srini
Hi MOHAMED ABDUL LATIF ,
Nice blog, i was wondering if there is any future roadmap by SAP to integrate SAP RE-FX module with E-Invoicing solution provided by SAP. For the phase-1 we have developed customized solution to generate and save invoices but Phase-2 which is an integration phase, we need to find a way to do so.
Thanks
Atif
Hi Atif,
No roadmap yet
Best regards,
Latif
Hi Mohammed ,
Is there any way to convert XML to UBL in SAP as ZATCA requirements
Regards,
Mohammed
Hi Mohammed,
UBL is a different format of XML which consist the data according to regulation, and currently used by most of the EU countries.
Some countries like Saudi Arabia have their own format of XML based on the tax authority requirement and specification. Here there is no conversion from country specific format to UBL format. Always one is applicable according to the tax authorities requirement
Thanks,
Mohamed Latif
Dear Mohamed,
any guidelines/configuration documents/SAP KBAs for phase 2 for document compliance solution.
Regards
Dear Mohamed,
Any guide line for Phase 2.
FAQs Doc: https://jam4.sapjam.com/groups/aDJPUFaeB2noMhwk999hKH/documents/InCb65cd58fDn485cc1oR9/slide_viewer
Hi Mohamed,
Nice blog !
I am getting error "Field ID is empty in TaxCategory of TaxSubtotal" while generating e-invoice i.e in XML format for billing document in EDOC_COCKPIT.
It's working fine for Direct FI invoice through FB70 but not for SD Billing Document VF01.
I have maintain the Tax Category Mapping for A1 tax code as below.
Tax Category
Possible to see the video in https://sapvideoa35699dc5.hana.ondemand.com/?entry_id=1_jj0hcccv?
Hi Mohamed ,
Seeking your kind help ,
We are doing green field from ECC to S/4 HANA 2021 cloud. We did all the notes applied in S/4 system and manual config, still we have 2 issues
Your kind advise is greatly appreciated .
Thanks
Vijay M
Hi Vijay,
Raise an incident to the component “CA-GTF-CSC-EDO-SA”, the right team will check and clear your issue
Best regards,
Mohamed Latif
Mohamed Latif,
Greatly appreciate your quick guidance...Just wanted to share some of my research observations... please correct me if I am wrong..
I found the difference between our Existing ECC set up where eInvoicing is running successfully and S/4 is being implemented. The difference is ECC T Code EDOC_COCKPIT is showing Saudi Arabia Tax Invoice (SATAXINV) , where as S/4 is showing Saudi Arabia eInv.(Generation)- (SAINVSTR). Perhaps this is the root cause. Can you help to throw some light where can I change this pointers so that T Code EDOC_COCKPIT will be linked to Saudi Arabia Tax Invoice (SATAXINV) in S/4
Many thanks
Vijay Muppala