One time Customer transactions in KSA eInvoicing
What’s in this Blog?
For the non-returning customers in your business, you may have created one-time customer master with which you may at time create orders and subsequently invoice documents in your business.
How are such transactions handled in the SAP’s solution for KSA eInvoicing ? what data’s and where do they need to be maintained? what are the constraints?
you may have multiple questions as above. Don’t worry, this Blog explains it all.
One time – customer
What generally we first think about one time customer is that it is relevant only for B2C business scenarios where just just one customer master is used to transact with multiple persons and still record their individual identity. This is not always the case. One-time customers can also be used for B2B business scenarios as well.
Having said this, you may just create one single one time customer master in the Business partner transaction and still use it for both B2B or standard invoices and associated credit / debit notes as well as B2C transactions depending on your requirements. Or you may also choose to create one unique OT customer master for B2B and another one for B2C.
The key that differentiates between B2B and B2C transactions in OT customer transactions is the Natural person indicator (BSEC-STKZN). This is shown in the picture below
When this field is set in the OT data entry screen, the transaction is identified as B2C transaction. If not, then it is considered as B2B transaction.
We may enable the natural person indicator at the BP level but that is not considered to identify the type of transaction. So, in case you want the transaction to be created as B2C transaction, you will have to ensure that this field is enabled at the transaction level before saving the document.
VAT number for one-time B2B customer
As all other data are read from the transaction level for one time customer, the VAT number also s read from the transaction level. By standard, the VAT number entered in the screen for OT customers at transaction level is copied to its relevant billing document and the einvoicing solution reads the VAT number from the billing document itself.
The fields used for capturing the one-time customer data is the same as the master data read happening for normal customers in the KSA eInvoicing solution, just that the tables where data is stored is different.
Depending on your system setting you may need to prepare the OT data entry screen to facilitate the entry of the customer information in your system. you may refer to the blog
Other blogs on KSA eInvoicing
Master data mapping in KSA eInvoicing solution | SAP Blogs
Handling Intercompany transactions in KSA eInvoicing | SAP Blogs
Some useful links
- SAP Document Compliance topic page
- Document Compliance Help Page
- Announcement Legal Notification
- KSA eInvoicing Webinar (Login required)
- Saudi Arabia E-Invoice Webinar 28Sep2022.pdf (sapjam.com) (Login required)
- [Release announcement] Phase 2 Solution for Saudi Arabia Electronic Invoicing (sapjam.com) (Login required)
- Entry of master data for one-time accounts | SAP Blogs
Note: For accessing the last three links listed above you need to login to MENA Localization SIG – Overview (sapjam.com)
Thank you for reading this blog. I hope the information is useful to you. Please share your feedback in the comments section below.
I encourage you to follow my profile for similar content.
Thanks, Zaheer! Great post on a topic that does not always get the attention it deserves : )
Thank you for your post,
but how natural person flag influence on edocument type for the invoice as Tax invoice or Simplified invoice?
and if it doesn't have influence, how system will recognize the edocument type, or it will rely only on billing type assignment to edocument type.