Master the Electronic Invoice Format for Support with airSlate SignNow

Electronic invoice format for Support

foreign I'd like to welcome you to today's Dynamics 365 Tech talk today's topic is electronic invoicing for Dynamics 365. my name is Agent I'll be your moderator today we are broadcasting this session through teams Live Events and the audio can be heard through your device speakers this session is being recorded on behalf of the Microsoft Corporation when you join this event your name email address and or phone number may be viewable by other system participants in the attendee list by joining your agreeing to this experience the recording will be available on the tech talks Community Dynamics page within five business days if you have questions for the presenters who need support please use the Q a panel located on the right side of your screen our presenters will be responding to your questions throughout the presentation thank you for your patience during these announcements presenting for us today from Microsoft we have gibralto Ona dorat senior program manager Merrick ruleski Prince of PM manager and Dimitri colusny principal engineering manager Gilberto over to you okay thank you AJ morning good afternoon everybody so you're welcome to this presentation so I will start showing you the agenda for today so we want to make a quick overview about what is electronic invoicing service I want we want to make to present you what's new and present you make a short demo of the new features I want to show you the upcoming features and we will finish with a quick question and answer session so making a quick uh introduction here just remember uh we have we have already recorded we had already uh First Tech talk session about electronic invoicing it was made in February so please feel free to join the community and watch the recording of that first session so first let's give you a context for in the motivation for the electronic invoicing service so electronic invoicing is nowadays is a regulatory Trend which was mostly made to prevent tax evasion globally estimations and says that um 20 or or from 20 to 30 percent of collection taxes have problems with tax evasion so and electronic invoicing is already a reality in many countries around the world so such kind such as Brazil Italy Mexico and more and the European Union has a goal to make the electronic invoicing uh predominantly predominantly voicing method for all companies the edit ranking voicing so it start started as B to G business to government uh scenario but now this is being expanded and also is fulfilling the business to business scenario in in a growth market so today there are more than 500 billions of invoices issued globally around Celsius as 65 billion they are electronically fertilizing a 12 percent of Market penetration so when it comes to electronic invoicing most of the companies they have to deal uh even during implementation and operation they have to deal with two conflicting demands right from one side they need to deal with a variety of formats architectures Technologies level of maturities are across the countries and especially if the electronic invoice is has is driven by the government so this is a mandatory compliance so not compliance sometimes it's not a is not an option and of course they need to face the agility to comply right so from time to time governments go update the legislation and modify certain aspects of the different device and then company needs to the needs to have the necessary agility to comply with those changes in the other hand uh Global especially global companies they want to operate globally and scale right so they also want to optimize Investments across multiple countries and regions to fulfill the electronic invoicing requirements so I mean not investing redundantly across the countries to attend this and of course they want to simplify the management of system integration so the electronic invoicing aims to bring to to uh to propose a balance to meet those two different kind of uh demands so then what electronic invoicing services does first is a cloud service for issuing and receiving electronic invoices for issuing it supports a variety of electronic invasive formats to comply with logo to comply with local regulations from several countries it integrates with tax authorities web services for granting electronically authorization or approval this is a common requirement when we talk electronic devices driven by the government and for receiving it also supports a variety of electronic invoicing formats and it also integrates with office and sharepoints to automatically receive electronic invoices so and what are the main capabilities so uh in the training voice is a worldwide worldwide cloud service available in multiple data center geographies so nowadays is deployed to the United States Europe UK and Asia but if necessary we can deploy to more regions okay it also it's uh out of box integration with Microsoft Dynamics 365 finances supply chain employees operations it is available only for cloud installations and electronic invoicing also has a core a set of features which are common independent on the counter or region right so you can for example issue and receive electronic invoices for different countries you can integrate with office email accounts and sharepoints for for integration with folders you can store your diet your data on your Azure storage account and your secrets and digital certificates on your Azure key vote you can manage access and permissions you can manage the electronic invoice format itself and you can manage the life cycle of the configuration formats and for is the specific parts of that needs to be fulfilled it's fulfilled the electronic invoice allows you you can use the out of box configurable invoicing formats now available for 13 countries plus staple format you can of course configure and customize the electronic invoice forms for the countries that we are supporting this is the list plus people you can generate invoice formats as XML and Json formats you can assign the electronic invoice with digital certificates and you can electronically communicate with taxal towards web services for granting approval and you can customize and create new electronic invoice formats that depends ing to your needs and requirements okay so for a more detailed video about electronic voicing so I'm going to transition to my colleague Dimitri Dimitri hello everybody so to start with the details of electronic and voicing first of all we need to review what are the main components that participate in the iterations related to electronic documents generation or electronic conversation generation and submission first of all uh probably some of you already know there is a functionality so all regulatory configuration search uh this regulatory configuration service is there tools therefore is the platform for Designing the electronic reporting formats and designing the process how this generated electronic invoices will be a process and submitted to external web services and external channels as well as it is possible to design the process how electronic and voicing service will listen to external channels like emails and sharepoints and process incoming documents to Accurate with this configurable setup of electronic invoice structures and electronic documents processing these structures are stored as actually as configuration as XML files in global repository managed by Microsoft as Microsoft we ship out of the box some templates your countries and this templates of the configurations are available already in globalization repository as well as you as partners of customers as soon as you created these configurations uh you go stores them in the global repository and if you want you can share them here with other partners customers the next point or the next main component is Gilberto mentioned already these are Azure resources fully managed by you like DeWalt and storage account keyword is needed for storing secrets and certificates that are used in some of the scenarios like digital sign or during establishing of traffic connection to external web services as well as storage account there is the main storage managed by you for all documents that are generated electronic documents that are generated by electronic motion stories or that counter electronic invoice in service either from your Billing System from here from if I'm doing our case or from external systems like from external web services or SharePoint or mailbox uh them electronic invoicing uh operates this uh FM down and there is a certain steps to set up on both F and those side and electronic invoicing site to make this connection apparent shs already mentioned that the electronic and voicing can integrate these uh SharePoint mailbox and external web services but it is not limited because we are working on extending this some capabilities of you know integration with other channels and much more external web service in the next slide uh we will start looking into some details the first thing that I want to reiterate probably and describe in a more details the component that is related to regular configuration service and particular to electronic reporting formats uh Electronic Reporting functionality is available in F1 door for quite a while and here we reuse this functionality for the purposes of creation and defining the structure of electronic formats and now we support the Json XML txt and these few parts of these electronic files and one of the very important thing here is a possibility to define the validation rules for for the structure that allows you to do certain calculations on their document level that we will result in either success validation or year validation uh before you submit the document electronic document or electronic and was further uh to work with the final country specific formats or the formats that you need in your business to business scenarios we support conversion or to the formats from a unified structure that is called uh actually that is based on ubl structure and comes to electronic and voicing service from fandom and this conversion can be done actually both way when you export the document or when you import external document the system will be able to convert the files from one structure to another also we are working on supporting udl structure you build invoice that is possible to use as an Import and Export structure in the electronic Imaging service besides of that the current conversing service has other capabilities like supporting code for multiple languages in the for example invalidation rules and has some technical stuff for tracing on the performance and debugging it and it is possible to package multiple files generated with an electronic reporting to zip archive uh this is the part that is related to particular electronic files but on the next slide you can see that uh the second uh main component here in the electronic documents in interchange processes is the steps that are performed with the generated file as an example here you can see that uh there are there can be several steps uh these steps we call actions and all the actions are combined in the so-called processing pipeline so besides the generation of the file uh in most of the cases and scenarios you will need to do certain steps with this file and with regulatory configuration service it is possible not only to use actions and processing pipelines provided by Microsoft test in place but create your own pipelines reusing these actions in them and building the process that will satisfy your business requirements uh we provide some predefined step of the set of these actions and you can like play around setting up each action's behavior and draw such process uh quickly reviewing this one as an example we can see that business data or in unified structure will come from the front door during submission of the document to an electronic unboxing service for calling electronic conversion service with ask to perform generation and submission of your invoice The Next Step here in this example we generate electronic file action that actually understands to what format incoming data should be converted and picks necessary latest format Electronic Reporting format to do this transformation of the document a resulted file is stored then to Azure storage and the same file then goes to the next action that is responsible for digital signature that sets a stance secret or certificate start in the keyboard in your keyboard The Next Step can be a submission to external web service and then the the results can be processed by uh the actions that is responsible for processing of the response from external web services and for processing we also use electronic reporting configurations not to provide flexibility in no code setup and development of this process where on the configuration you can Define what to do with the particular response from web service and those sort of actions shows in this uh diagram one of the next actions here is just sending the file through email to be defined mail address uh so uh just to summarize that protecting pipeline this is the way uh uh you describe how electronic and washing service should work and what it should do with the incoming financial data uh besides of that all the submission results added on back to F and dockline and depending on the setup on FM dos side the corresponding tables and trackers for example journals can be updated with certain information that will be sent back to your fm Dom as well as in the front door you can see there or you can download the files generated here during processing pipeline execution the next thing is how submission login works on F1 door and on the next Slide the wrap view screenshots but your videos see that in a Pandora as well during our demo there is quite a reach set of informations that you can get from your submission process on the right side there is a example that is also configurable in terms of number of the columns and informations that can be brought here without necessity to develop anything uh you don't hear all the um submissions that you have done and details of these submissions or statuses of the submissions to the series uh on the left side this is example if you go to the details of one of the submissions you can see details per each action and it is very important that the pitch action you can get the year or messages if they occur there to understand what web processed successfully and what messages were completed or what actions were completed with any years and you can see output and input results of each action to do analysis uh if it is needed for you to understand what is going on with the processing pipeline besides on that uh if we go to the next slide uh we can see that the process of defining on all these rules and all these companies can be considered can be seen quite a complex one uh from the very beginning but to simplify the whole process we have introduced the life cycle management for the whole uh processing and for the whole submission of electronic invoices but to describe this in more details we need to get familiar with some conceptual things first of all we have introduced the new Concepts that is called globalization feature this globalization feature in fact is the uh some kind of containers that test all the artifacts that allows you to build the proper pipelines the proper processing and using Pro performance so usually a teacher consists of electronic reporting configurations that take part in the process as well as processing pipeline that describes how the service operates uh we as Microsoft provide a set of such features uh your specific countries with some predefined parameters and redefine TR configurations uh we releases Microsoft provider you can import this electronic and voicing features to your instance of regulatory configuration service and build your feature that will be done already under your configuration provider uh these necessary changes if you need that for example you can specify some additional parameters or you can adjust your configurations if it is necessary or in the pipelines as soon as you have done the changes you can either publish the global requisitory and share it with other partners and customers if you want or you will be publishing that to electronic invoicing Service as we all deploy to electronic unboxing service in this case at this step electronic and washing service will know voltages and how it should operate in the particular scenario and besides of the overall like life cycle here we support versioning of these features and data vacuums uh that can be multiple features uh in electronic and watching service with multiple versions and there is a concept of the so-called context and applicability rules that I will show you in more details during demo but the idea is that on the vendors side you define a set of parameters like pairs of key value as it describes some details of particular uh or provide some metadata for particular electronic invoice for example it can be some legal entity country so-called type of document or even customer group and if this set of parameters meshes correctly these parameters on the feature level then particular feature globalization feature will execute but uh that steps we will review weekly during our demo and now I return back the stage to gilberta thank you Dimitri so moving forward and what is new um so in April we released uh electronic invoicing service and the configuration for Egypt in this release we release more 12 countries the configuration for more 12 countries Austria Belgium Brazil denarc Estonia Finland France Germany Italy Netherlands Norway and Spain plus the formats for people right which in many countries even outside Europe adopts the the standard of people and we also are releasing the receiving vendor invoice capability to receive vendor invoice either from email accounts as well from SharePoint folders so now let's play a short demo and then in next dimit will make another demo as well in this scenario I will demonstrate the electronic invoicing for Brazil right so just giving some little bit of context so my in my scenario contoso plans to start a new operation in Brazil for selling Goods uh in this case contosion is to prepare a new legal entity and this new new legal entity and needs to comply with the local legislation meaning that it needs to be prepared to issue the Brazilian electronic invoice which is called an artificial Electronica or simply nfe which is a mandatory requirement for trade operations in case of Brazil the electronic invoice is a mandatory requirement uh it is a kind of electronic invoice that needs to be sent to the government web services to approval or reselection right and the operation can just can only proceed with the government operation from these web services and failure to comply with this requirement or meaning not issue in Fe is illegal and exposes contoso to several tax fine to a severe tax fine in case of tax auditing so this those are the stories so the first story is a army story he's the account receivable administrator so he wants to prepare its legal entity to comply with the Brazilian electronic invoice and Fe he doesn't need to know very much detail about what nfv does but he knows the overall requirement which is basically uh it's necessary to generate an XML file this the file this XML for the electronic invoice format for Brazil is pretty much standard across the counter but there are possibilities to make some small uh customizations in case of need this XML file must be digitally signed this is another requirement and once the XML is digitally signed it must be sent to the government web services which is going to process and grantee either approval or rejection in case of some uh um inconsistence in the file so nrna of course knows that he must comply with this because this is a mandatory requirement in the country and the second story is the accountable is the accounts receivable clerk it's simply going to show you how the clerk operates the issuing of electronic wise uh will uh we'll do this for the clerk the only thing that he expects is simply uh issue the electronic invoice and view the status if it was approved or rejected or rejected okay so then now let's go to RCs so now I am Arnie I am on RCS okay and I want to prepare uh my legal ways to issue the Brazilian electronic invoice so as early I simply go to globalization feature I go to electronic voice if this my first time that I go here so I can simply import my Brazilian electronic invoice format from the global repository as as Dimitri show so in this case I have already imported here to My RCS instance and once I have imported then I create a local version of this feature right based on the the feature that I have just imported here and then I have here my feature that created so in this page uh Arne can manage all aspects of the electronic invoicing feature for Brazil right in the first step he manages the life cycle right he control the the status of the electronic invoicing feature in this case my feature is interrupt if Arnie wants to view or customize something in the layout of the Brazilian electronic device he simply can go here on on the form itself so this is one of the things that come ready and ready to consume from from the global Repository and then Arnie can use here the former designer and if necessary Arne can customize or modify anything that he wants or need in case of need but uh but the format came comes pretty much ready for the usage uh in this in the electronic invoicing and the second thing that RNA wants me to do is to review the parameterization of the feature if for those who knows a little bit about the Brazilian voice nfe here we have several nfe events so the first one is the most important event which is the one who effectively generate the the the Brazilian voice signs sends to the government so RNA simply needs to review this configuration here and needs to make just the last my configuration before starting use so one of the things that he needs to do is first he needs to tell to this pipeline actions which is going to be the digital certificate that is going to be used to sign the file in this case this digital certificate needs to be uploaded in the key votes uh for for a contoso company right and and it simply needs to uh review the URL of uh uh the web services who the government web services who is going to uh to to process this electronic device okay so a part of apart from that so this is the sequence of actions that is going to generate the electronic invoice and also Arnie needs to review the applicability rules in case and something needs to be adjusted right something's like something like for example the legal entity ID of the company but in the state where the electronic invoice is going to be issued but everything is pretty much done here so then once I need review all the steps so Arnie simply change the status to complete this case and then publish which is going to save this version of the electronic invoice in the global Repository and in The Last Action become and in The Last Action Arnie will publish you and sorry it will deploy this electronic invoicing to the electronic service to the electronic YC environment so if you just tell which service environment he wants and then click by doing this Ani is ready to go the configuration is done and his fno is ready to start issuing electronic invoice so let's see for example how is going to be the accounts receivable clerk experience for example so now I have some screenshots here so now I am on ethanol right I am on the Brazilian legal entity so RNA and arnino the the accounts receivable clerk already uh posted uh uh a Brazilian invoice so this is a view of the Brazilian voice notice it's the status is created so then Arnie it will go to a specific form which is common for uh for all countries for submitting this invoice to the electronic inviting service notice that it can be run either explicitly or if necessary can run in background so uh the clerk or Arnie can schedule a batch to keep running this from time to time but let's see that let's say that the clerk wants to run explicit for this in Brazilian voice and then when he hits okay the process starts meaning that fno is sending this the data of the Brazilian voice to the electronic invoicing service the service is processing generating the file signing communicating with the web services with the Brazilian tax Authority web services and get response in this case for example when the response comes the services uh updates the status of the Brazilian voice in the in the table now for example the clerk can see okay my invoice was approved and if the clerk wants to see more details about this processing so there is a specific uh form in fno where the clerk can navigate he he can goes there selecting voice clicking submission details and then he the clerk will see the detail submission so in this case he can view the execution log of for all steps from the pipeline action the last one in this case is the one who uh says what is the final processing status in this case message error 100 return it from the Brazil from the tax authority to web services means the nfe was approved and in case the clerk wants to see okay I want to view the file which was generated in the same form in the same submission for details is simply mark the action who generate and sign the file actually the first one generate the second action and assign the file and by simply clicking on view the clerk can view the file so this is the the final uh file generated by the policy for the Brazilian voice okay okay moving forward now I'm going to transition to Dimitri who is going to make a demonstration for fatula PA and the next presentation will be devoted to the scenario when you need to import uh electronic and Voice via email to a fando and in this case we will review as an example for today Italian document and the process will look like that some email with this XML attached comes to your mailbox and electronic invoicing service can read mails from this box and then pass this file for further processing and mapping to the front door data structure directly in the front door and also based on that create gender uh voice uh I will show all the steps uh in details starting from actually set up of regulatory configuration service and uh show you how the setup looks like on the front door let's start with the document what I want I want to send through email this example or from electronic document I heard from mailbox empty mailbox that contains some already predefined folders and I will send actually to myself uh attachment now you pause it this attachments that I have shown you and some message hello let's send it you can see that we have in the mailbox inbox uh incoming mail is attached invoice there are no folders like a test a year or whatever yes but we will see that these folders will be created when we first run the process because we will set up in this way I have a some time ago created purchase order that I want to invoice and uh information in the invoice actually matches uh the details of this page set let's go to regulatory configuration service here we have globalization features workspace where you need to set up all the details to operate with some electronic and more submission process I will not describe some details that are not directly related to this process right now but let's go first directly to electronic invoicing features mobilization features similar to what new Angel Gerta demonstrated right now for Brazil but what he did he imported template from uh from Global report published by Microsoft but in this scenario we will create the globalization feature and corresponding pipelines from the scratch so let's call this feature it says for this feature we had the first number of the version we don't need in this scenario any configurations here configurations on the service side because the only model mapping will be executed on the from those side but what we need we need to set up the integration collaboration with the email box and describe how the attachment cell will be retrieved and sent to a fender so I'm adding a new setup that actually proposes you a few options [Music] and here are three types the first one is the procession pipeline a processing pipeline is the set of actions what I described to you but in this context the processing pipeline Stores Only exporting scenarios when you submit any document from F and do and it must be processed but when we release an external channels uh we need to Define either data Channel or data Channel and processing pipeline the first one just takes the attached attachment from the mail and pass it to F1 though the next one can do additional steps or actions with the incoming document I choose the first one because in this scenario I need just to pass it over and I have two predefined channels that we support right now and we are working on explaining the set of internet channels right now I will work through incoming the mail and click create here going to the details I see that there is some information on data channel that is pre-populated and some information I should add first of all let's start with uh description of the channel and we will provide channel name this data channel name is important for using in a front door and I will show you the usage of this channel name then we can Define username and Secret I keep my names and secrets in the keyboard and here I can refer to the keyboard secrets that will automatically taken from the keyboard during connecting to my mailbox so in this scenario I have for the name I have email account key move secret and I keep password and keyboard secret password there are some additional parameters one of them is main for folder to look into for reading mail it is corresponds to the real mailbox in archive folder iOS specify processing this is the folder that you'll store successfully processed nails so they will be moved from inbox to processing and then error box will be moved all the invoices that are processed with some kind of errors what is needed also here processing mode we have two options by attachment or by mail it means that if there are several attachments uh in the mail and you translate here by attachment each attachment will be considered as a separate electronic invoice that must be processed if you select by email it means that one electronic and Voice or electronic document will correspond only to one email that comes but if there are several attachments they all will be linked and passed to F and do for some kind of foreign for example if you need uh to store and you receive from uh PDF file with a document also I need in our case I selected by attention because I want just to retrieve the attachment and here I need to specify what attachments I am interested in I need to provide the name to each attachment and provide the filter this name will be used also in the front door to understand what to do with this particular file and for example if you have PDF as a second file you should Define it here and then can be processed and somehow separately in a front door uh so I save that and then I should go to applicability rules applicability rules is a set of conditions that allows iPhone door to understand which uh and to allows a Founder to pass information describing what you want to do right now with the service for example if you submit some electronic document you can Define that it is uh generated in the particular legal entity for this particular customer and then you can set up here in applicability rules the same fields or some other fields and electronic conversing service will receive the code from ofando it will match as many lines of this rules with the incoming date as possible and the most applicable uh feature with the applicable version will be considered matched and it will be executed this approach you you'll be able to orchestrate uh different features for different legal entities or if you define uh your B2B communication using some EDI or whatever you can Define several features here and set up the applicability rules the ways that for example for particular custom a particular customer group or some other conditions like types of the document different processing pipelines will be executed and different conversion of the document will be down to like different formats in our case I want to provide information Channel equals to uh file mail and as soon as in the front door there is a call to the service saying that I have such information Channel fat mail in this case service will choose this particular Pipeline and start you'll start listening to mailbox I click save click validate and here I see that action parameter mandatory will not set continued returning back to the setup I see that I didn't Define server address uh this validation helps you to provide online data refuse I Define this server address that is needed for proper operation safe and validation should show that it is successful okay we have done the setup and after that I want to make sure that this version is completed and now I will deploy it to the service to be sure that the service can already operate with the incoming requests related to to the particular to the particular uh teacher I publish that and right now all this configuration is published now then I go to purchase orders and there is a receive electronic document process I know that right now my mail is inbox and I want to run the request to the service there are usually two requests sent to the service uh to get the file and here I need to check what what is happening is the file we see that the file is moved from inbox to rotating folders that just created it means that trans series the series is successfully got this email and now it is processing code already within the service the next thing that I need to do is to uh pass the file from the service to a front door I click that receive electronic documents once again and we can actually see that this file will be processed by the source and the details will be sent to fnd and corresponding tables in the front door will be updated with uh vendor inverse information while we need two steps because the first one is a pushing service to communicate with some Outlook the second is to retrieve the documents and this is that there is a response document successfully imported one we can go to pending calendar invoices form and we see that there is a invoice that is created for me today this is exactly what I was expecting for uh but also we can go to electronic documentary seat log and see that right now it is my time uh there is a record in the receipt log I can go to details see the details of this processing I don't have processing actions because we didn't set up battery showed you how to say or some examples of from the details per each action but we have here overall status completion that is good and we have processing data for example the files that comes to uh as an attachment from email to the system or for example we can look at body on somewhere and get the details there uh because we keep this information here is an invoice that I was saying uh how it looks like on in parameters in the front door uh you probably uh seen these two main components that I refer to name of the channel so here this says that iPhone do should call this service to check that mail Channel and to do that there is a VR configuration that constructs this request so if you need to do anything to change you can just update or change this electronic reporting context and here we have in a definition of the file of the attachments that we are interested in and if there are more attachments all of them can be defined here and you can do different actions with this files here on the vendors side for example file we just applied Electronic Reporting model mapping that transforms this file from its own file and not actually transforms but saves information matches information to database and save this to database and the approaches of saving to database is described in the rendering with import configuration uh so I I demonstrated you set up and execution as well as some parameters of FN Dot and now I'm letting gilberta to continue with his presentation okay just let me share my screen back okay hope you can see my screen so just moving forward for the final part of the session so this is our roadmap what we have ahead so for 20 2021 Wave 2 this year we have a planet for electronic invoicing service in the Italian SDI integration uh which is going to be public preview Indonesia uh Saudi Saudi Arabia and Mexico and for 2022 wave one which is going to be beginning of next year we plan for we planned The Last Mile known out of box b2g invoicing via an isv connector and dataverse integration so our last so here there are some resources uh uh we have a plenty of documentation already available in Microsoft the docs here it's the link and if you want to contact us uh so you can send the email for you can send your message to this email and if you want you please join the Yemen community that we have dedicated for electronic invoice which is the twinkie voicing service okay Okay so you have two minutes left or some question and answers uh I would read a couple of questions from the chalk uh here and uh let's start we have one minute and actually uh uh okay I have I see some question is it possible send an automatic email to a customer they think you had just issued him here and invoice so there is a possibility to Define automatically as the customer address based on on your customer in your own in the file that is generated this is uh done by mean of retrieving customer information from now that actually comes from a Honda electronic and washing service we can send electronic emails yeah but we can send these emails right now to the predefined addresses exactly uh this period we are working on extending this functionality and we have in our pipeline or for next next additional capabilities of the service the possibility to send emails and or redirect them for example generated documents directly to the customers or to to vendors to your partners so right now out of the box these days you download see this information but who is interested with uh this capability this functionality please let us know directly through the mail that is available uh you don't have uh you don't have time to answer more questions until you'll be doing right now uh after you complete this call uh and uh thank you very much Gilberto do you have anything else to present so thank you very much for your time your participation and your interest so and thank you I'm going to actually post a short survey Link in the Q a panel if you could please uh find some time to participate just let us know what we did the well today and what you'd like to see in future events as a reminder the recording for today's session will be available on the tick tocks Community Dynamics page within five business days I'd like to send a big thank you to our presenters and of course you the audience for joining us today this concludes today's event