Create Your Own Receipt Format Sample for Technical Support Effortlessly

Receipt format sample for Technical Support

i guess yes you can start in english and the iman will uh will start recording right now yeah i already started the recording uh this session hello everybody this is ayman saad and uh receipt project from eda and this session is for technical support on how to integrate with the e-receipt solution and this session will be represented and discussed in english and will be represented from microsoft team and after they finish the presentation about how to integrate with sdk we will start receiving your uh questions through raising hand feature we will take the uh the questions one by one so uh engineering from microsoft should you start please thank you everyone yes please mr ahmed i just wanted to add a one note that after after this session ended we have another session uh at 1 30. i will share the link for this session in this chat it will be our pleasure to to join with us uh this session for explaining uh the next steps after the explaining the me uh the components of the sdk file so after this session we will have another session and one third i will share the link into this chat okay thank you thank you mr engineer ahmed you can start thank you everyone for joining us today in our session allow me to introduce myself my name is ahmed shaheen i'm a microsoft solution architect who will be helping you to work today on on the session i would like also to to introduce my colleagues uh emmy please introduce yourself yeah hello everyone good morning this is emmy camel from the microsoft team uh working on the e-receipt solution project thank you emmy i also would like to introduce wissam please go ahead hello my name is usham al-sharif i'm a application development consultant working on irishit project as a template as per our session what we will do we will start with the sdk so please feel free to raise your hand whenever needed if there is any question i will guess our team we will be able to handle it and answer the questions as we move forward allow me to start first by asking amy and wissam if you would like to proceed and share your screen and start presenting our sdk yes so i will be sharing my screen so ahmad please let me know it can confirm when you can see the screen i'm able to see it guys are you able to see the screen shared by okay okay uh so thank you everyone i will be starting by um presenting to you the sdk and having a walkthrough on the portal to show you the changes the new features the new apis that we have in the e-receipt solution and that you can use to integrate with our system for the e-receipt so first to start to access the sdk portal so if you are already um using the e-invoicing uh solution so most probably you will be familiar with this portal uh so for the e-receipt solution we we are still using the same portal for for the sdk uh which uh we have this link we will be sending you this link so you can um try it yourselves and um have a walkthrough on the portal so basically it's the same portal nothing has changed we just added some uh new functionalities that we will be showing you uh today so to to to start with the portal we just click to on getting started uh where we go to the portal and the navigation um so mainly we have um on the top you see the tabs we have the release notes the apis itself this is the technical part um and in this part we see three um three areas we have common apis which are the apis that are used um commonly between the invoicing and the edc solution and we have the apis specifically for the e-invoicing and apis for the e-receipt which is the new part and the one the area that we will be covering for the session today we also have the types we have the codes frequently asked questions and contacts and we will be going through uh all of these um during this session and of course if you have any questions uh i prefer that we have the the questions at the end of the session um so please take notes of the questions uh or you can raise your hands and we can have like a discussion at after i'm i'm finished or done with the walk through uh on the portal uh so to get started you will see here this is um just a description about um our solution we are talking here about the e invoicing and the a receipt solution uh if we go to the release notes i just want to show you uh what has been added to um to the portal to the solution uh what are the new features so for the release notes uh about the new features um so this is uh what's the new and the changes that we have here uh for the first part um this is explaining that we have now three subsections the common apis the invoicing apis the adc apis uh we have uh receipt issuance page um mainly explaining any details or any questions about how you can issue the receipt we have also added this is an updated page about some postman collection that we added to include the new apis for the e-receipt solution so basically this is what has changed in the portal for the sdk we're also talking about new types so by types we mean the new document type that we have here which is the receipt type so in the old solution we had the invoice but now we introduced a new type which is the receipt document type and the new return receipt document type which is actually basically a return receipt when you want to return something so we have new types the receipt and the new return receipt and we will be going uh in details in into each one uh to show you the details of the receipts the structure and what are the fields that we have in each one of them uh also a new thing we have uh the codes um so in in the e-invoicing solution we had uh codes that the taxpayers were using but we added also new codes um that that can be used which are the order delivery modes and the payment methods modes and we will be going into these so regarding the apis so the new apis that we have are um login as taxpayer system uh point of sale so here this api is talking about how you can login or integrate your point of sale to the e-receipt solution submit the receipt documents get the receipt details get the receipt submission and and this is similar to the get receipt details but it's a bit different and we will go into these to explain what each one of these apis can do so this is briefly what we have what we will be covering today and what we have um so you are able to integrate with the e-receipt solution and the apis that you can use to integrate so i would like to start first with uh going to the receipt itself to understand the receipt the structure the fields um how it looks like so for the receipt so we have um for now usually we have different versions but for now we have version 1.0 which is the receipt document type version and that is supported on the edc solution up till this moment and for the return to see it we still have the same version version 1.0 uh to be used so um i'll be going into each one so let's check the receipt um and the details that we have in it so you will see here on the right you will have an overview a data structure and additional considerations any extra information that you need to know about the receipt so in the overview it just explains what is the receipt in the data structure this is the part um where we have all the information about the structure and the fields of the receipt um so i'll be going um on all the fields that we have in the receipt and of course if you have any questions um and we can discuss it um at the end of the session or you can raise your hand if you want to now um okay so um you will find the structure of the data will be displayed in a table explaining what's the element and what's the type and the description about the element or the field and an example will be provided as well um for the field itself uh so we'll see here so to start with we have uh the first thing in the receipt we have the header okay so the header is a mandatory field and it contains other elements so if we click here you will find here this is the link so if you click here you will go uh down in the page you'll see you'll see here as well that it has been expanded the item has been expanded and it's showing all the um the elements that we have in in this in the receipt structure for easier navigation for you if you want to navigate from the right so going back and the header is the first um thing that is included in the receipt it includes these fields uh to start with we have the date time issued so this is the the time uh of when the receipt receipt was issued and this is a mandatory field in utc and this is an example of how the date time on the receipt should look like the second thing is the receipt number okay and this is a mandatory um a fiend and then we have the uuid uh so this is the universal identifier of the receipt um which i use it's a mandatory field and it's in sha 256 format uh and we have um a section um explaining that i will be showing you later in the session on how to generate the uuid for the receipt this the third one is the previous uuid so the previous uid uh it's still a mandatory in sha-256 format and this references the previous receipt that was issued from the same point of sale so i need to point out the previous uuid for the receipt i am issuing from the same point of sale uh the other field we have the reference old uuid and this is an optional field and um and this should be included if you have uh if this receipt had an old uid that was assigned to it but it got changed so we need to add this old uuid as a reference for the receipt other than that we have the currency so this is the mandatory field you can choose from the currency codes the currency code tables that we have and you should include what is the currency of the receipt that you are issuing uh we have the exchange rate and of course this is a mandatory field if you are choosing a currency that is other than the egp um the order name code the order delivery mode uh and the gross weight and the not net weight for the receipt and all of these fields are optional so this is uh the header of the receipt if we go back to the core we are finished with the header part the second part is the document type so if we navigate to the document type i have to specify um what is the receipt type uh for example if i'm issuing a sales receipt i have to select that this is an s a sales receipt and the type version of the receipt which for now is 1.0 because we don't have other versions so moving to the core part um and of course they were mandatory fields as well the third part is um information about the center so if we go to that so for the seller we have the rin which which is the registration number it's a mandatory field we have the combin company trade name we have the branch code branch address and for the branch address we have a structure related to that which is should include the following um we have should have the country the government the region city uh the street the building number and the postal code the floor the room and any landmark or additional information uh that can um make the address more clear of course that this is all provided with examples um so it can explain better how the branch address should look like so if we move back to the seller so we said that we have the rin the company trade name the branch code and the branch address which are all mandatory fields the device serial number and here we are talking about the point of sale um serial number that you are using uh the syndicate license number if you have any as this is an optional uh fiend and the activity codes that you are using so this is about the seller part that you need to include in the receipt the next part is the buyer this is information about the buyer so for the buyer we have first thing is the type of the buyer um so the buyer we have three types uh either it's a b it's for business p for person or f for foreigner so um you have to specify which type of buyer you are issuing or giving the receipt to and the second field in the buyer part we have the id of the buyer and by id we mean different things so it either can be the national id when we choose that the type we are using is person or the company registration number if we are saying that the type we are using is b which is business or the passport number when we are saying that we are using um a foreigner type type and this field is optional but it will be mandatory if the receipt uh amount is more than 50 000 egyptian pounds so if the receipt exceeds that amount then this field has to be given it has to be mandatory other than that it will be optional you don't have to provide it um next to the id we have the name of the buyer the mobile number and the payment number which are all optional fields so we talked about the header the document type the seller and the buyer data in the receipt the next part is the item data and this is about the items themselves that are included in the receipt so for the each item we have the internal code of the item which is a string a mandatory field we have a description of the item we have the item type and the item code for example it's egs or gs1 and the code and you we have the unit type which could be like the measurement of the unit itself for example it's um kilograms for example if we are buying something that can be measured in kilograms and these we have code tables for the measures for the unit types which is an old code table included what that was included in the invoicing solution as well we have the quantity for the item the unit price for the item uh the net sale the total sale and the total a commercial discount is an optional field if we have any an item discount is option and the value difference and taxable items for the taxable items it's an array of taxable items so if we navigate to that uh we just need need to say to specify what is the text type that we have and the amount and the subtype of the tax type and the weight so this is the the information that needs to be included for each items that we are adding to the receipt so moving back to the core we have finished the item data so after that we need to have the total sales the total that's on the receipt level not on the item level the total sales it's a mandatory field uh total commercial discount if we have is optional total items discount uh extra receipt discount if it exists it's an optional field as well and the net amount uh fees amount and the total amount and the tax totals the payment method for example i'm saying i'm paying in cash and visa adjustment if we have any adjustment on the receipt uh contractor if it exists it's an optional field and in the contractor we need to include the name of the contractor the amount and the rate and the last uh field or element that we have in the receipt is the beneficiary which includes the amount and the rate and of course this is optional as well so by this we have covered all um the fields that need to be included in the receipt including which one um mandatory and the type of the element as well and um [Music] the last part is additional in consideration usually usually we add notes in this part uh that if you need to consider and here we will need to to check the receipt issuance faq page which i will be navigating to uh at the end so this is what the sales receipt looks like so if we go back to check the other type of the receipt which is the return receipt we want to check how this looks as well uh so i i navigated to the types from the tab at the top uh so you see here these are also as well the old um for the invoicing solution the debit and the credit and the invoice and at the bell at the bottom is the receipt and the return receipt so if i want to navigate to the return receipt uh to check what we have here so basically the return receipt for the structure is it it is exactly the same as the receipt there is no difference the only difference is we have an extra field in the header information so the extra field is the reference uuid so the reference uid it's a mandatory field if you are issuing a sale a return receipt which is referenced to the uuid of the sales receipt the original sales receipt for which you are issuing or having the return receipt other than that we have exactly the same structure exactly and the same fields that's just the only difference here so by that we have covered the um what the receipt and what the return receipt will look like which is the core that we have here for the um the edc solution um so next i wanted to show you that the new code tables that we have so we have two codes which are the order delivery mode and the payment methods these are not very big tables and they are included in the same page so if you navigate from the top or you go on the codes uh i find the old uh codes such as the activity type the branches the country codes currency codes um so the new ones are the order delivery mode so if you navigate to this one uh you will see a table that includes um the the codes the new codes that we have fc is a code for meaning uh from the company place to transport by others dc transported by the company so that's for the order delivery mode for the payment methods we have these codes um which is a bigger table but includes different codes for payment method for example c is cash b visa and so on for different other different payment methods so these are the new codes that we have that has been added to the sdk to the solution um so next i want to go to the core part of this session which are the apis for the e-receipt solution the new apis uh that you have to understand and be able to use to integrate with the e-receipt solution so i'll move to the uh to the e-receipt api page which you can go to from this tab api and you go to the e-receipt part will get you into this page so for the e-receipt api um you will see in the page we have the different apis i will start with authenticate point of sale system which is the first step that you need to do to integrate with the with the solution so about to the page you will you will find this structure of each page for the apis you will have an overview which is an explanation of what the api does signature inputs for the api outputs and additional notes or additional considerations on each api so the first api that i mentioned is authenticate point of sale so this is the first step that you need to do to integrate with the e-invoice the e-receipt solution so the first thing is to be able to use the e-receipt solution you have to register your point of sale so the registration of the point of sale can be done through the registration portal through certain steps um for example you have to provide the vendor the model the syrian number and so on um to register to say that i want to register this point of sale to um to my profile to be able to integrate it with the e-receipt solution um and after that after you have registered the point of sale uh you can start using this api which is you have to authenticate the point of sale so to authenticate the point of sale this api how you can use it um so first thing the signature for the api is post connect this is how you can call the api and what are the inputs that you have to provide the to the api so you can authenticate the the point of sale and be able to integrate it uh so you have to provide so you see here this is the second section of the input so you have to provide the point of save serial number the point of sale os version the point of sale model framework and the pre-shared key so these are the inputs that the api will need to authenticate the point of sale okay and also we have some body parameters in the body um [Music] as an input as well such as the grant type that should be client credentials and you also need to provide the client id and the client secret which are more are like the username and the password uh so you can authenticate the point of sale so after you have given all the input and called the api so what are the outputs that you get so when um the call is successful we have a successful response so of course it returns a status code 200 and what is returned to you is the access it's a gwd okay and this um [Music] this the that you will be using uh to auth that that make sure that your point of sale is authenticated that you can uh call the rest of the apis um later on and um another one thing one note that uh to be able to use the e-receipt solution to be able to authenticate your point of sale uh you need to have to your profile a tag called b2c so the tag b2c is a tag on your profile that enables you to use the features for the b2c for the adc solution which includes the authentication of the point of sale and submitting the receipts and getting a receipt details and all of the apis that we have in the a receipt for the invoicing it's just the b2b um tag so this is not enough if you have the b2b tag it's not enough that you can use um this api or the rest of the apis for the receipt you need to have the b2c uh tag as well so um so this has returned to you the access and the time it's there and um um how long until uh the expires okay it's it's configured now for one hour it's fire and scope um it's an optional it tells you what is the scope of the for example the invoicing uh apis so if the authentication is not correct you will get a 400 bad request and it will tell you what is the error that you are getting what's the reason for example you provided a wrong client id and you're unauthorized the point of sale serial number is invalid and so on it you can get like a list of errors that explains to you why this request is not successful um so as i said this is the first thing that you need to do uh to be able to to use the rest of apis uh to be able to submit your receipts to our solution um you need to provide the authenticate the pos you get the and then use the um for the rest of the apis it means that you are authorized and authenticated to you the rest of apis of course you have must have the b2c tag and you have to register your point of sale first to be able to authenticate it later so this is about the first api that we have here so going back to the full risk list of the apis um [Music] okay so we authenticated the pos so the next thing that logically you will be doing is to submit your receipts to the receipt solution so for that you can use the submit receipt api um and this [Music] this explains an overview about the api information it tells you that the receipt has to follow the receipt structure that i showed you earlier and it tells you as well that this api supports that you submit the receipts in json format [Music] and that you need to authenticate and integrate your point of sale system to be able to use this api so for the signature on how you can call the api uh it's post api v1dc submission and so this is how you can call the api and what are the inputs for the api so um so first i for the for the header parameter content type i have to say that the type of the receipts that um or the documents i am submitting they can they are in in json format so this has to be uh specified i'm saying that i'm submitting in adjacent format and this is the example application slash json and um for the input about the receipts it's itself i need to provide that um [Music] in the body of the request okay i can submit one receipt or multiple uh receipts in the same submission um so if so in the body i have to include the receipts in the structure that we had um that i showed you earlier i need to include all the receipts in json format that can be submitted to the system and the second part is the signature um so this part is is not um is not um included with us for now so you don't have to add the signature uh so basically this is um a digital signature that you need to include um with your submission but as i said this is not necessary to do for now so you all you can do is to just add the list of receipts that you want to submit and of course the receipt can be um either a sales receipt or a returned receipt [Music] within the same submission it doesn't have to be of a specific type just to show you some notes okay okay so this yeah it's not i'll show you to you later um so for it's information about the submission so as i said some limitations um that i will be showing you later on the receipt um the structure and we have some validations that you need to consider um before submitting the receipt in order that the receipt won't be rejected as i said you can have at least one receipt in the submission and other conditions that i will be showing you later to consider before doing the submission to um to the system so um upon sending the request and sending your receipts you will be getting either a successful response or an error uh so when you get a successful rep response and you have submitted the document uh you will be getting um a submission eu id uh this is an id for the submission the whole submission not just the receipt uh that will be generated by the back-end system and be given to you and um you will be getting um a list of accepted receipts um you you will see what are the receipts that are accepted and if there are any rejected receipts you will see uh the list of the rejected receipts and the error for each receipt why this has been um has been rejected so when you get the document uh accepted uh you will get it in um in this structure you will get the uuid of the receipt the long id and the receipt number so for the documents rejected you will get the receipt number the uuid of the receipt and the error the error of why this receipt has been rejected and in the error itself you will find um a message um so this is a message um uh explaining to you uh why this error happened uh the target of the error what caused the error a property path the path and details more details which is um it could be a list of multiple errors that were detected and maybe just not one error so um it's it's going to be the same structure if you go to it but just just specifying that within um a rejected receipt or document you can have multiple errors not just one error and if if the submission is not accepted at all you will get an error a bad response with different codes and each code explaining why what is the error that happened for example it could be a bad structure so for example you have provided the receipt in a structure other than the one that we showed you earlier something it's changed maybe a field is missing um so this could be about structure uh incorrect submitter um maybe i'm not um i'm not authorized to submit this document um maximum size exceeded of the receipts or the submission or we have a duplicate submission this had this submission has been done before so these are the possible errors that we are getting why the the submission was not accepted uh from at the beginning and for the signature as i said this part is on hold now so we can just ignore it um and this is um the api that you can use to submit your receipts to the um your receipt to the solution so after you have done your submission so we have different apis to get information about your receipts or your submissions that has been um now are included now in our system you want to get information you want to query about information about the receipts and the submission so the first api i would be checking is get the receipt submission and this is um an api to check on on the submission itself not each receipt on its own um so for if when you are doing the submission on the system uh it's not um if even if it's accepted we do in the back end other validations on the receipt to make sure everything is correct so during this process it doesn't mean that it's accepted maybe after we are doing the validations we find an error so we have to reject the submission again so in the meanwhile if you want maybe you want to um know about the status of the submission you want to know if it's still in progress if it's accepted if it's rejected so in order to do that you can use this this api which is the get receipt submission um so for this this is how signature this is how you can call uh the api um so to call the api you need to have the submission uuid which was returned to you when you did the submission uh in the first place it it returned to you the uid so you can use that uuid to query about the status of the submission so for the inputs of the api of course you have to provide the submission uid and a page number the page size so the page size is that like it's like the number of the receipts you want to have displayed per page so this is more of how to display um the results um so um the output that you will be getting when you um call this uh api um so you will mostly find about some information about the submission and some information about uh the receipts uh in in the submission so you will find what will be returned to you um the submission you id and the seller id the the the win of um of the seller uh the submission channel so the submission channel is a field um that specifies uh what is the channel that you uh submitted the receipt through so it could be an erp which was included in the invoicing solution could and still with us on on on the adc of course it could be the point of sale which is specifically to the e-receipt it could be that the submission through the portal or the through the mobile application so we have four different channels that uh will be returned to you saying which channel you have submitted the receipt or the submission on the date time received when the submission was received the date time issued when the submission was issued and the status so um so this is uh overall status of the submission of the batch of the receipts as i said we have three statuses it's in progress it means that they were still doing the validations on uh on the submission valid it means that it has been accepted the whole submission is valid invalid it means there is an error with one or multiple receipts in the submission and it's not accepted the submission errors it's a list of errors that we have in the submission and this is the structure of the errors that you will be getting and the receipts you will get you will be getting um a summary of a list of the receipts of in the in the submissions uh in the document summary so this is a summary about each receipt so this is specific not on the whole submission is specifically to the receipts um so you'll find some information such as the uid the receipt number uh datetime issued and received that document type for example it's sales or return receipt the version the seller id the seller name buyer id and uh so some information about um about the receipt itself and the errors um list of errors that were detected within this receipt so this is specifically to the receipts and some midi metadata so for the metadata it's uh includes the total pages total count current page number so this is um [Music] when you call the api and this is what what's the output and what it returns to you uh when you want to inquire about the status of the submission that you did um so of course you get a response if an error if you for example you provided a submission you id that is incorrect that is not in the system you will not be getting anything so this is about the get submission details and as i said you could be using this api to understand to get information about the submission you have made to the system so so after you have submitted the receipts you have inquired um you got the status of about the submission you want information so after that um if the receipts are accepted they will be uh entered in in the system and after that you can get information about there is each receipt individually through um these apis so we have get receipt details and get receipts so basically they're um the same but um get receipt details has more of um information within each proceed so to call the get receipt details so as i said the receipts have been accepted and they are now um in the system and you want to get information about your receipts so to use the api you use the signature get get receipts and you provide the eu id of the receipt you want to get the details about or to inquire about so um as i said as an input you need to provide the uuid of the receipt so the information that is returned to you of course it's information about the receipt okay so the receipt details so this is all the information in the table uh that we um provided to you about the receipt uh you will have the submission new id of which um this receipt was included in which submission the time received the time issued submission channel and the receipt um itself in in this um in this structure so if we go back to document summary so this is the information about the receipt that would be returned the uid long id previous view id reference all the uid if any the date time the receipt number currency and and so on um this is all the information that is returned to you about the receipt details uh when you call this api all this information uh specifically about the receipt you can check it to understand all the fields that will be returned to you and of course you'll get an error if uh you provided a wrong id uuid for example and it's not in in the system so this is the get receipt details api for the get receipt it's very similar to um the the other api they get receipt details uh the only difference here that it includes uh the original json uh receipt um that you have submitted it's in json format so it's the row document and that will be returned to you so as an input it of course it needs the uid as well you need to provide that okay and as an output you will see here the extra field that we have here other than the get document details and that it returns the document in the row format in the json format and as well all the details of the receipt same as the other a difference that it returns to you the receipt in row format so these are all the apis that um that that are included in the system for this phase that you can use to integrate with your with the solution that you can try um at your site the last api that we have is get the receive details anonymously and as i said you need to have your point of sale authenticated to use the all of the apis that we went through the only api that you can use anonymously without a pos authentication so this one it's the get receipt details anonymously it does not have as a requirement that you are authenticated so to use this signat to use this api you call the signature um you have as an input to provide two things um the uuid of the receipt and the date time issued of the receipt so to inquire about a receipt anonymously you will need to provide these two parameters and as an output it will provide you um information about the receipt the document summary and all the details of the receipt um same as the other apis uh one thing that is uh that's different um here other than the apis that in case you are calling this api without authentication anonymously uh the buyer id and the buyer mobile number will not be shown to you if the type is a foreigner or person so um this information is not displayed the buyer id and the mobile number so that's the difference in other than the other apis other than that it will be provided to you the details of the receipt so by that we have covered all the new apis that we have here starting by authentication submitting receipts getting receipt submission and getting receipt details so these are the list of apis that we have here um so the second part or third or fourth part that we can cover in the session is about um going back specifically to the receipt uh detailed as i said we have covered that the receipt needs to have a certain structure but as well um we have some extra information some extra validations that need to be considered you are um submitting or issuing the receipt so you can find this extra information in the receipt issuance feq page uh which you can navigate to from the feq page you will find the receipt issuance feq page that you can check so you will find here on the right the different sections that we have in this page so all related to the receipt so the me we have the first text section is the main um calculations um so these are some of um as i said we do some validations and do some calculations uh on on the receipt uh for example i need to make sure that the the total amount uh is the sum of uh all the items uh in in the receipt so this is a calculations the validation uh that is checked um on our site and if it's not correct it will be rejected so it's better that you have uh cons to consider these calculations um when you are submitting the receipt in order to avoid that you received get rejected so it's better that you do it at your side from your side um to make make your receipts less prone to rejection from the side of the system so to check the main calculations that you need to consider when you are doing the receipt you just click here you will find some um the rules in the main calculations uh you will find all the rules that you need to follow um within your receipt for example the issuer id lengths must be nine digits if receiver type b this um server id lengths must be nine digits and so on so this you need to check this list and make sure that your receipt is is following all these rules so mainly they are basic checks and calculations that need to be considered the second thing is the local validations so um so like i said uh we do some validations on the receipts to make sure that the receipt is correct so the first thing is the structure of the receipt this is the one i showed you at the beginning of the session that the receipt you are issuing you are submitting needs to follow the structure that we showed you and it should be um in json format and if you open this page it will get you to the same page that we checked earlier about the receipt structure um so this is the first validation that you need to do to follow the structure uh the code validation sony you need to make sure that you are uh using uh valid codes from um the code tables that are provided on the sdk you you're not using any invalid code so this the second check um the core field funny validators um is another set of rules um that does that do some validations and checks as well and you see this set of rules okay that you need to be to be considering it's very similar to the main calculation but it's some other checks that extra checks that you need uh to um to to include for example it will tell you that issuer id is required name is required type is required and so on okay so this these two parts are the main calculations and the local validations that you need to be checking and including when you are submitting the receipts to avoid that you are received get rejected and then after they get rejected you have to do the modification and then submit again and after that they get rejected as well so in order to avoid this hassle this waste of time you should consider these validations and calculations before doing any submissions uh the second third part of second part on on the receipt itself so the uuid itself so the receipt uuid this part is generated from your slide not from the system so in order to generate the uid we have this section specifically that explains to you how you can generate the uuid so you'll find the steps here [Music] for example the first step you need to make sure to include all the key fields in the in the receipt object uh with the uid of the previous receipt if receipt type is returned then make sure to include the reference uid um and then at this the on the fourth step it will tell you uh serialize and normalize the receipt which is an operation uh on that will be done on all the receipts field uh to make them um um all flattened in one line uh and if you open the link you will find um this is um another page and that explains in details this is very technical uh how you can um serialize the receipt what is the algorithm that is used you just need to follow the algorithm to breach the serialization step of of the receipt so after doing the serialization of the receipt you start you do you create a hash value of uh the text that is the output of the fourth step using she-256 algorithm and then you convert the hash value from 32 bytes to 64 characters and after that this is the receipt you id that you can include and use so this step is very very important to understand um how you can generate the uid of the receipt it's very detailed and has all the steps that you need to be doing to generate the uid and this link as well that is this schema just uh okay not this one it's it um it should show you the uh the receipt in um json format it's here somewhere so i'll make sure we get to that um in this session um the other part is how to sign the batch uh as i said this is on hold for now so we will be ignoring this part and the other part is the for the qr code that the taxpayer or you should be generating a qr code and including it in the receipt and to generate the qr code it tells you um how to do that um how what what are the um [Music] what is the what are the fields that you need to include uh for the uh for the qr code um so for example we need to have a url for the url of of of the receipt of the qr code it has to be of this format you will you need to follow this format and receipt the type value and registration number branch code some information that you need to include in the qr code and at the end it shows you um what is um the qr code content should look like so you fee you will see this one line that includes all the information that was mentioned above about the receipt and this is an example of um a qr code content that you should be um when you are creating the qr code generating the qr code this is what it should look like yeah receipt batch schema and structure so yeah this is the file i was talking about uh so this is um you see here this is um the submission for the receipts in adjacent format for your reference as an example um how it it should look like so basically these are all the fields that we have discussed earlier but in json format if you don't know how to do that uh the last sections so these are some limitations on the receipt submission so these limitations you need to consider as well in order for your submission not to be rejected so the first thing is the maximum submission size meaning that the maximum number of the receipts in a single submission is 500 receipts or 1.5 megabytes so uh eat whatever of whatever one of these conditions is reached more than that you will not be able to submit your have your submission uh and the minimum submission site is one receipt and maximum is 500. uh average number of lines per receipt is 10. this this is not a condition this is more of an advisory um but of course you can definitely have more than 10 items within a receipt um uh the receipt is allowed to sub to be submitted within an allowed duration which is for now 24 hours um submission date time can be in the future the supported type is json you have to submit with allowed branch and you have to submit with valid document type and document type version and these as well are some limitations on the point of sale devices on itself for example that the syrian number can can be up to 100 characters um the pos device has to be registered first and linked to the rin and you need to have the b2c tag that we discussed earlier earlier and the taxpayer should not be blocked for you to be able to use this point of sale so um these are the limitations on the receipt and the point of sale and by that we have covered uh all of the new features the new apis that you can use so you can integrate and start integrating with the solution you can go to the portal to the sdk portal you can navigate and check the apis yourself as well i wanted to show you some of [Music] how you can use the environment and some of the postman collections that are included here okay so this page is an instruction um on how you can start if you want to start testing the apis um so this section you will see here um it's telling you that if you're using postman so we have um some postman collections that are ready for you uh which includes um all the apis that we've talked about that are ready for you to use right away and uh the different environments that we have that you can test the um the apis on so we have different environments and um the environment file that you need to include um in postman as well to use these environments and this is what is with instruction as well on postman how you can import the environment and the postman collection files uh to start to make it easier for you uh to start testing uh the apis and start playing around with it a bit and at the top as well you will find um information about the different portals that we have uh registration invoicing portal apis identity service um and um the certificate files that you need to um at your device so you're able to use the different environments so this is all um with the screenshot to make it easier for you to start testing the apis so i think by that we have covered everything the walkthrough for the sdk um for the apis uh so to give you like um a head to start um um trying and testing the newest apis um so i think that's it from my side on the sdk portal and i think if you have any questions um you can just just address it to me and the team if you have any questions anything that was not clear during the session thank you emmy so we will take a few minutes to answer your questions please raise your hand so that we are able to to to listen to your question and of course we will go through the order so whoever raised the hand first will be able to ask the question first rajni please go ahead hi um thanks for the session uh just a quick question see how does this work in a web pass scenario where we do not have a point of sale device as such so it's a hosted uh application so if i understood your question correctly rajni now we support for example scenarios that you don't have a physical device or a physical point of sale you can use for example something like a virtual you can use for example your mobile and register your mobile to be your point of sale so this is one of the scenarios that we support uh did i understood your question correctly yeah i understood and another uh quick question uh invoicing is it only for b to b because we have an invoice and receipt b2c scenario it's a combined iar that we issue to customers so then in that case do we just need to integrate with the e-reset api is that sufficient so rajni for all existing taxpayers they are already a b2b so they all have that invoicing capability the invoicing capability will not change now for any uh existing taxpayers who wants to update or add or use the new features that coming from receipt they will need to have for example to be tagged as a b2c so they will have both functionality for b2b or b2c now from a b2c perspective the receipts and the submission of the receipts will not affect the day-to-day business that you have so it will not change anything that you already do it's more like an additional capabilities or an additional features that you will have to submit receipts in addition to submitting invoices so i will need to submit invoice uh i mean i will need to integrate with both apis invoicing as well as receipt if your current business you are already submitting invoices then yes you will need to submit both it depends on your business okay so that that's what i was trying to explain that we have a it's it's called an invoice and reset but basically the uh payment uh collection happens at the same time there is no there are no separate steps so in that case if i can integrate just with the recept uh api is that right no no rajnik each one of them will have a separate flow so for example submitting invoices will use invoices apis and it has a specific flow submitting receipts it's a difference flow so you will need for example to follow the specific flow for submitting either receipt or invoice you cannot for example submit receipts as if it's an invoice and vice versa it has to follow its own flow and its own apis understood okay thank you thanks for the responses team any other questions hey hi this is uh vipin from uh talabad bye pepin please go ahead yeah yes hi i have a quick question for you so actually we are trying uh to integrate from our end microsoft dynamics with the portal and one of the issues and we are also in touch with the microsoft support team who is trying to assist us with the issue so one of the issue which is really we are facing challenge with is the digital signing mechanism so now we have a physical device a device for authentication which has been provided to us but the thing is we are not able to digitally sign and you know there is it does not it say the support says that the digital signature does not work with that usb device and this is some restriction with uh relation to the cloud solution so uh we are confused like what to do and what are the alternatives for it your question weapon has two parts we will need to separate it into two parts part that is related to submitting invoicing which is the current business that you have and this thing we will need to go through the support it will have to go through the b2b support right so it's not going to be handled within today's call because today's call is focused more into receipts which is the b2c now the second part is the b2c at this point in time bitten and the first release that we are providing for receipt will not include signature so the signature will be optional and is currently on hold and it will be discussed in future releases so now if you want to proceed with the b2c and submit all your receipts there is no signature required at this point in time in this release so do you mean that we can upload it without the digital signature at this point in time yes there is the signature for receipts specifically and i'm just saying receipts invoices will continue business as usual you will need to provide signature but for receipts today with release one it is optional you can proceed without the signature and that's only for received weapon okay so uh if we talk like uh i'll give you an example so for our entity the team demar entity we also have the delivery fees associated so which we charge to the end customer so that is a b2c as so how does it work how will the signatures work there so currently you can the signature let me just take a step back and describe the process weapon now for submitting receipts they are submitted as a batch they are not submitted as a single receipt at the time so you submit them as a batch now the whole batch of receipts has a signature component so you can provide the signature as as a batch on the whole batch not to prepare a single receipt okay now the situation is at this point in time since release one will not include a signature you can leave that signature component empty or that field as empty and submit it as is it will go through okay so we will we will try that but in case uh face any challenges can we uh reach out to this the email id that was mentioned as he received at etago.eg absolutely correct yes this is the communication that you will need to reach for okay and you said that b2b will be at a different uh later phase so can we understand when when will that be no b to b will continue business as usual depends so that's what i'm trying to tell you the new component is b to c which is the receipts but b2b will continue business as usual so what you will need is to send your inquiry into our email the one that iman has pasted on the chat window and ask for both cases as i told you you have two cases one which is a to b which is business as usual the second one which is the the e receipts the a receipt you don't require a signature at this point in time in this release okay understood okay thanks thanks thanks for the clarification no worries happy to help uh let's check i guess we have uh sanotz hi this is santosh from alsa yes the question is related to this item code and item type related to this receipts so you have mentioned that egs and gs want to be used for item type and item code internal code intel code and item code right see the thing is in all share we are operating more than millions of items in trading do we need to register all of because we don't follow gs1 we have our own internal ids so if you want to go with egs do we need to register all these items to use it now the general practice is usually to add these these codes you have to register them and they will be specific to you so these items will be specific to you so the business as you as usual process is that you need to register them but i will also open chance to my team to answer amy and wissam do you have any other suggestions yeah so like you said ahmad so the degenerate practice is that you uh have to register request to register these codes that you can use it later on here yeah the volume of items are in a very huge quantity i mean the you know where we operate h m h m's are coming in a very huge con you know it's millions every season they've introduced to item master so you're saying that can we have a bulk update option for this there is a welcome update on the on the portal where you can request the forum for code usage can i answer for this point for this question so please andrea yeah okay yes satosh santosh yeah yes this is the first time to join us in [Music] this workshop or you joined on b2b we already using b2b but the volume of lines are less than b2b scenario but when it comes to the store perspective we have so many brands and these brands internally have millions of items we don't know which one will be trading in egypt you have you have your followers to have to follow you have to follow the same scenario for b2b uh just all items could if you depends on js1 code that will be easy and you don't need to register already we we pull it from the database of one but if you have an internal code official internal code you have to register on the portal of invoicing or received if you you haven't if you haven't registered before see we have uh we we we are franchising business majority are working from u.s uk companies the concern right now is it's not us actually getting item masters they are creating it and when we check with them they don't have any gs1 codes for them that means we have to go with egs only option if you go with egs option we have you have two options if you already registered if you already registered to gs1 it's an easy you don't need to register all with this item but it's already will be we don't have it we check it at the time of it we will check with the b to base time we can see that we are not registered with any gs1 course so it's a it's a it's an option within alisha to understand how we're going to register these items because we don't have gs1 from the host brands they push us the internal ids we need to convert into egs or any other options but you are talking about the branches in uh in egypt yes yeah we operate across middle east at least in north africa you don't you don't need you don't need to resist for each branch which is just only the list of items that will be used through all branches exactly so it's a volume wise it's very huge especially if you talk about h m so many brands are there we operate uh across meena so these all brands has millions of lines every seasons they will push it to us and these lines to identify exactly what i should you know register into egs we we need to know how to proceed with that because if we cannot say which line will be trading in egypt and which one will be trading in other countries okay we will uh provide other decisions about how to generate on our code our internal clue for the egs for the next workshops and for supporting also we will explain how to decrease this uh a lot of amount of items and you can uh build them a specific uh prescriptions for special items that will help you to use it don't need to resist all the huge items this will be explained okay fine okay uh can i have one more question so in an operational model if a till has been replaced for any damages or any you know any working issues immediately we have to register to start trading of can we still make a trading and we can register this parallelly can you elaborate a little bit on the scenario okay in one of the tills when our stores crashed due to some electrical issues or maybe the machine is damaged we will immediately replace with another mission in the store to continue the customer facing in that scenario can we do the registration of the till now what you need to do is to introduce it and register it like if you bring in a new machine this has to be registered again and once it's registered it is ready it will be ready to be starting working right so this this new machine has to be introduced and has to be registered specifically of course following if it's a different model or from a different vendor then you will need to follow up the the whole cycle about registering it adding the provider of this machine adding the model for this machine generating the keys and then you can proceed the business as usual there is no issues and registering a till-less instant in instantly not a not a delayed process right i mean it's basically you need to provide the three areas it's gonna be the vendor the model and to register it to wherever you're gonna use it like for example which branch all these kind of details once you get these details and register it properly you will be able to proceed so i'm asking is there any delay in the registration completion or is it like instant instantaneously you will give the approval i'm under the impression that you're asking if there is a specific approval let me check with wissam do we have a specific approval or once he has the keys he's able to proceed yeah exactly what's he have the client idea the secret he can post and submit the receipts immediately so what you need to get is the keys that's it once you have these keys the registration keys you can proceed okay so so that is what i'm trying to understand if there is a damage happens we have to make an sla for that to replace a neutral registration part and if there is a time delay is there it completing all this process we have to put it as part of our sop standard operating procedure yes okay thank you we have mr ali please go ahead hi how are you all good please go ahead yes i have questions regarding to that maybe i can name it as a software issue you know that there's a device and add-ons in the microsoft msd to do this connection between the tax authority and msd but once we extract the certificate from the and we try to upload it to the to azure it gives that error that the names it's incorrect or the formats the format file is incorrect so this one it should be like a software issue or we have what we will do in this situation because this is like yeah it's it's more like a technical problem what you're facing ali it's either for example are you using a jwt or are you using specific way how to serialize it or extract it i'm under the impression that you can reach out to the same email that iman provided and i guess you will need the support from our operator they can support you it's a business as usual it's not a complex issue okay okay i'll rest for the same email thank you ahmed no problem no problem so do we have any other questions uh can i have one focused in just for uh clarification when you're when you're posting the e invoicing from a store prospective b2c scenario are you looking or validating the machine is exactly same as the trading happen because i'm just considering the last question in case the till crashed and we replaced with a new till can we repost with the old transactions which are not posted with the new till are you talking about invoicing oe or e-receipts because you mentioned this okay so for example if that machine crashed and you have for example certain receipts these receipts that exist on the older machine has to be reissued santosh so you have to reissue them again and resubmit them again but the customer is already left i mean how we can do that i mean it's it's uh it's a receipt switch you can't re reproduce again yes no no you don't need to reproduce the whole receipts now remember that your machine should cache some of these receipts if you are submitting as batch right so it should cache some of them now this data that need to be cached or has to be cached has to be managed to be moved to the new machine or at least to be extracted to the new machine and then it has to be resubmitted so it's not a it's not an issuance of new receipts it's you need to get that data from the older machine okay see my question is like can we have a centralized push of these e-receipts rather than the point of sale because point of sale is more uh critical for us for another store customer facing uh operational activity if i put something centralized which is pushing the receipts to you guys as a b2b scenario is that fine for you guys so what we have is another scenario where you can push it from for example from erp but that will be more of a future scenario we will provide an integration toolkit it's going to be more like an sdk so it's going to be an integration toolkit that will help you to push it for example from erp that will be where you can use that centralized scenario you're talking about okay using the integration toolkit but it's not part of this release it's going to be in the future release okay okay thank you hi ali here it's uh marek uh from arshad again um just to have a question regarding the sdk website that you have um is there any other information that is out there that helps us in terms of the workflows how the things work thanks sam thanks matt for your question now all the information in addition to the sdk you remember while you're using the app which is for example the invoicing portal and so on there is the user guide the user guide will appear on the menu on the left so for example if you want to look at the user guide you will see an updated sections there for example on how to register for example a point of sale or any of the information or the new scenarios that we produced right so everything will be actually updated as being actually posted as we speak correct yes yes so the information that you're looking for for example you can see it in the sdk and another location will be the user guide that is on top of the app itself so you will find it on the navigation menu on the left perfect perfect thank you yeah i i can share that as uh quickly as well um about to the user guide uh which is that you can share the shared link that'll be great yeah i'll share the link and and show you um so this is the extra part which is the user guide so it would look like this um you will have the scenarios so basically it will include everything that you invoicing in the receipt about all the the scenarios um any of the operations the workflow the logic of uh the application so this is more into details and find um different subjects and when you click on each one uh you will see um the details about how you can perform this operation with the screenshots and the clear description so for example if you want to register your point of safe for example so this is for the b2c you will find all the scenarios on different topics ab