{"id":26216,"date":"2021-01-05T12:36:57","date_gmt":"2021-01-05T12:36:57","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=26216"},"modified":"2021-01-07T06:23:02","modified_gmt":"2021-01-07T06:23:02","slug":"invoice-approval-process-using-microsoft-teams-and-ai-model-part-2","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2021\/01\/invoice-approval-process-using-microsoft-teams-and-ai-model-part-2\/","title":{"rendered":"Invoice Approval Process using Microsoft Teams and AI Model \u2013 Part 2"},"content":{"rendered":"

This blog is a continuation to part 1<\/a> of the 2-part blog series which will help you understand how to operate the AI model in automated flow and use the data parsed through AI builder.<\/p>\n

Part 1<\/a> – Route an email to external services and create an invoice approval request in Microsoft Teams<\/p>\n

Part 2 – Operate the AI model in automated flow along with enabling the actions (approve and reject) for invoice request and create the invoice in CRM once the request is approved in Microsoft Teams<\/p>\n

First and foremost, we need to create an AI Model and extract the field values from the Invoices using Form Processing. Detailed steps on how to use Form Processing can be seen here<\/a>.<\/p>\n

In our case, from the Invoices using Form Processing we are extracting the below fields.<\/p>\n

\"select<\/a><\/p>\n

After swaddling some of the data of invoice into AI model, now it is time to use it in our automation for extracting those values from invoice. Let\u2019s continue further from where we left off in the flow that we designed earlier in the blog<\/a>.<\/p>\n

Let\u2019s start by adding another action and call the AI builder.<\/p>\n

\"add<\/a><\/p>\n

Add a \u201cPredict\u201d action<\/p>\n

\"predict\"<\/a><\/p>\n

Select the model that we created earlier<\/p>\n

\"QB<\/a>
\nNote:<\/em><\/strong> We have created an AI model named QB Invoices<\/em><\/p>\n

Specify the type of data that we will be sending to \u201cPredict\u201d. AI builder supports both pdf and image. In this illustration, we are going to send invoice as a pdf so let\u2019s fill the field as shown below<\/p>\n

\"document<\/a><\/p>\n

For \u201cDocument\u201d, we will select Dynamic content as shown below.<\/p>\n

\"document\"<\/a><\/p>\n

As soon as we add this field, the flow designer recognizes on its own that there can possibly be multiple attachments available in the email. So it automatically packs up in the loop that will iterate over each attachment in the email.<\/p>\n

\"attachment\"<\/a><\/p>\n

Let\u2019s quickly move the \u201cTeams\u201d action to be within this loop.<\/p>\n

\"move<\/a><\/p>\n

\"post<\/a><\/p>\n

Next, we want to route this for approval using the fields that AI builder extracts from each invoice, so we will add an action that will route the message to an approver in Teams. For this, let us add an action.<\/p>\n

\"add<\/a><\/p>\n

We will again choose a \u201cTeams\u201d connector and \u201cPost a choice of an option\u201d to the user. We will also provide them with two custom fields; \u201cApprove\u201d and \u201cReject\u201d<\/p>\n

\"action\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

This will allow the approver to make the right decision on each invoice.<\/p>\n

We will specify a relevant headline and an approver as a recipient.<\/p>\n

\"add<\/a><\/p>\n

We will update the message field as shown below since we want to be able to see who the invoice is from and also the total invoice amount (we are extracting this amount value from AI builder and building a relevant approval request sentence for an approver with the information they need using dynamic content)<\/p>\n

\"message\"<\/a><\/p>\n

Note \u2013 we can specify the fields into this \u201cMessage\u201d field depending on which of the information you want a flow to bring from the AI builder, so pop the dynamic contents into the message field accordingly.<\/em><\/p>\n

Since we have two possible outcomes \u201cApprove\u201d and \u201cReject\u201d, we will configure a \u201cSwitch\u201d to handle these two options.<\/p>\n

\"predict\"<\/a><\/p>\n

\"control\"<\/a><\/p>\n

\"switch\"<\/a><\/p>\n

We will select a dynamic content for \u201cOn\u201d field as shown below<\/p>\n

\"select<\/a><\/p>\n

\"switch\"<\/a><\/p>\n

Using the concepts that we covered earlier above, let’s create two different cases for \u201cApprove\u201d and \u201cReject\u201d<\/p>\n

Case 1 \u2013 Approve<\/strong><\/p>\n

This will automatically reply back to the sender with an invoice approval and create the invoice into CRM with some of the field values extracted from the invoice through the AI builder.<\/p>\n

Case 2 \u2013 Reject<\/strong><\/p>\n

This will automatically reply back to the sender with an invoice rejection.<\/p>\n

Case 1 \u2013 Flow configuration (If the invoice is approved)<\/strong><\/p>\n

Let\u2019s add an action<\/p>\n

\"add<\/a><\/p>\n

\"reply-to-email\"<\/a><\/p>\n

\"message<\/a><\/p>\n

Enter a relevant line that you would want to send as an invoice approval reply to the sender<\/p>\n

\"body\"<\/a><\/p>\n

Since we want to create a new invoice in CRM, we will add CDS action \u201cCreate a new record\u201d as shown below.<\/p>\n

The currency and price list we set here will be applied to the new invoice being created in CRM. The newly created invoice will have a currency and the price list set.<\/p>\n

Note<\/em><\/strong>: These values have been hardcoded here in this circumstance. However, you can still populate it dynamically, if required.<\/em><\/strong><\/p>\n

\"description\"<\/a><\/p>\n

Since we want the name of an invoice to be the value of the field \u201cDescription\u201d extracted from invoice using AI builder, we will choose the selection shown below. User can perform any dynamic content selection based on the requirement<\/p>\n

\"description<\/a><\/p>\n

We also want to fetch the address from the extracted field from invoice through AI builder, so let\u2019s choose the selection shown below. Here \u201cBILL TO\u201d is the field that is pulled out using the AI model earlier. We will have the same address applied to the invoice that is new going to be created in CRM(based on the requirement, the user is always allowed to do the relevant mappings here between the entity fields and the values that are extracted through AI)<\/p>\n

\"bill<\/a><\/p>\n

Note: We have created a custom \u201cBILL TO\u201d field on the Invoice. Later on, using custom logic, the necessary parts of addresses can be extracted.<\/em><\/strong><\/p>\n

Case 2 \u2013 Flow configuration (If the invoice is rejected)<\/strong><\/p>\n

Let\u2019s add another case for the option \u201cReject\u201d and configure it as shown below<\/p>\n

\"\"<\/a><\/p>\n

\"reject<\/a><\/p>\n

If we summarize, the flow looks like the screenshot below:<\/p>\n

\"flow\"<\/a><\/p>\n

Now let\u2019s see both these cases in action!<\/p>\n

Before we proceed, let\u2019s test the entire flow just to check if everything works fine.<\/p>\n

\"test\"<\/a><\/p>\n

\"test<\/a><\/p>\n

Once you see the below screen post choosing to test the flow, let\u2019s send the email to the approver.<\/p>\n

\"invoice<\/a><\/p>\n

\u00a0<\/strong>Case 1 (Invoice approved)<\/strong><\/p>\n

The sender sends an email with an invoice attachment to the approver\/stakeholder<\/p>\n

Sender<\/p>\n

\"invoice<\/a><\/p>\n

As soon as the above email is received in the inbox, approver sees it in Teams.<\/p>\n

Email received in Outlook of the approver\/stakeholder<\/p>\n

\"email<\/a><\/p>\n

This will be shown to approver in Teams with the values that we extracted through AI<\/p>\n

\"flow\"<\/a><\/p>\n

\"approve\"<\/a><\/p>\n

Click on \u201cApprove\u201d and put the relevant comment as required.<\/p>\n

\"submit\"<\/a><\/p>\n

\"aproval<\/a><\/p>\n

Once the invoice is approved, the reply will be sent back to the sender<\/p>\n

\"reply<\/a><\/p>\n

 <\/p>\n

We can see the new invoice is created in CRM with currency and price lists that were set in the automated invoice processing flow. Also, the name is fetched as an extracted value of the field \u201cDescription\u201d through the AI model.<\/p>\n

Quick verification <\/strong><\/p>\n

Verify if the Description value is the actual invoice that was sent for approval.<\/p>\n

\"quick<\/a><\/p>\n

Extracted as a name of the invoice in CRM<\/p>\n

\"name\"<\/a><\/p>\n

If we check further down, the address is set correctly. This address is also brought from the same invoice which the approver\/stakeholder approved in teams.<\/p>\n

Quick verification <\/strong><\/p>\n

Verify address on the actual invoice which was sent for an approval<\/p>\n

\"quick<\/a><\/p>\n

This is the address on the newly created invoice in the CRM. This shows that the field value extraction was successful through AI builder<\/p>\n

\"invoice<\/a><\/p>\n

Case 2 (Invoice rejected)<\/strong><\/p>\n

Sender sends an email with an invoice attached to the approver\/stakeholder<\/p>\n

\"\"<\/a><\/p>\n

Email received in the approver\u2019s\/stakeholder\u2019s Outlook<\/p>\n

\"email<\/a><\/p>\n

Approver sees it in Teams.<\/p>\n

\"approver<\/a><\/p>\n

Approver rejects the invoice<\/p>\n

\"invoice<\/a><\/p>\n

As soon as the invoice is rejected, the rejection notification is sent back to the sender via email.<\/p>\n

\"invoice<\/a><\/p>\n

Conclusion<\/strong><\/h2>\n

The whole invoice approval process could run in just about a minute. So with the help of these automated operations, we greatly reduce approval time and the possibility of human errors. This can be done even more efficiently and as quick as possible with these external integration services and AI capabilities. Legacy apps can successfully be integrated alongside, infusing the AI intelligence in just a fraction of the time using Power Automate.<\/p>\n

\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

This blog is a continuation to part 1 of the 2-part blog series which will help you understand how to operate the AI model in automated flow and use the data parsed through AI builder. Part 1 – Route an email to external services and create an invoice approval request in Microsoft Teams Part 2\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1902,2029],"tags":[2109,2111,1945,2110],"class_list":["post-26216","post","type-post","status-publish","format-standard","hentry","category-artificial-intelligence","category-microsoft-teams","tag-ai-model","tag-create-invoices-in-crm","tag-microsoft-teams","tag-operate-ai-model"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/26216","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=26216"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/26216\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=26216"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=26216"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=26216"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}