Streamline Vendor Invoice Automation Dynamics 365 for Security

Vendor invoice automation dynamics 365 for Security

good day everyone welcome to Dynamic 365 bytes our topic for the current series of videos is invoice automation SP my name is vesh wamani I'm a FastTrack program manager in Dynamics 65 finance and operations and I have with the Amar Kumar who a senior program manager in P say 6 to5 Financial operations so invoice capture is extensible to fit to customers business needs and in this series we would try to explain how easy it is to extend invoice capture and what are the areas that you could actually plug in your extension in and F it to the customers business this is meant to purely educate customers and partners on the extensibility story on invoice CCH to make it more interesting we want to see the extensibility story in the lens of uh business use case so on screen you have our hypothetical business use case that we clim for to elaborate this Soo cons Consulting procures a lot of items from its vendors vendors have a g payment terms but based on the size of the vendor if msme number is sent on invoice document they need to be paid immediately otherwise they may face a legal action not can be liable for payment so these invoices in crafts needs to be settled immediate so how do we achieve this through the extensibility story that we have the first step is to train an AI model to be able to capsure the additional MSM number from the invoice document and the subsequent step are to receive that captured field on data ver as well as on fendo and then use the same to be transferred to a vendor invoice on AO utilize it and save it onto a vendor transaction once the invoices was Ser then finally utilize this when you are actually running the payment proposals on a daily bases if you see any invoice with an msme number take it up for payment immediate to avoid penal but that is what we would want to showcase in the next set of slides these are the chronological steps that we will follow to land the extensions in the right way to ensure that we capture msme number and then use it in pay so first we would actually create a new additional field on the data was model for invoice header and then we then create a custom aild model train it with one additional field and once it is published you plug it back onto invoice capture while doing that we would actually ensure that the new field that is added is targeting the new field that is created on the data verse invoice models header that we have create created in the previous now once that is done they would actually transfer the invoice onto fendo so here we would need to have extension fields to capture the additional information that invoice capture is giving so we would need to extend invoice header Ono and then you would need to also have the same field to be able to capture the vendor transaction itself so finally we'll utilize this in the payment let's look at the first step of creating an extension field on the invoice modeling data to be able to create new fields in the invoice chapter model first you would need to log into the makers portal in the power apps and then switch on to the any envirement where you have the invoice capture installed and go to Solutions and in Solutions you create a new solution give it a name and say okay I already done that so this is my new solution so in invoice capture solution which we have uh invoice cat extensions we can now add an existing table I have already done that but I'm just showing you navigation so we would have to filter for staying invoice header and then in this you would want to add a column so which have already done it's a saying MSM once you have created the field click on the field details to capture The Logical name of the field we would need it to give a value for user defined field settings for this to capture The Logical me now come back the table section and in there select all then go to User it's fine here in the settings and inside this would want to Beed here and here you would say new using the form right and this you would specific by The Logical name of your field and save it the scope being header or like so whenever the phone uses you want to select header since I created feel and select it then it see okay I've done this already so I work for back from there yeah this can't leades the first part of story of extensibility obviously you would need to publish all your customizations on the data now let's move on to the second step