{"id":6789,"date":"2021-12-27T07:00:00","date_gmt":"2021-12-27T15:00:00","guid":{"rendered":""},"modified":"2025-06-11T07:51:16","modified_gmt":"2025-06-11T14:51:16","slug":"automating-before-and-after-payment-invoices-with-ai-builder","status":"publish","type":"post","link":"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/power-automate\/automating-before-and-after-payment-invoices-with-ai-builder\/","title":{"rendered":"Automating before and after payment invoices with AI Builder"},"content":{"rendered":"

AI Builder is a Power Automate capability that provides AI models that are designed to optimize your business processes by gleaning insights from your data. One of the most taxing manual processes in an organization is processing forms and invoices, luckily this is a strength of AI Builder. This is the part two of a 3-part weekly series on some common ways to get started.<\/p>\n

Background and challenge<\/h2>\n

One of the most common paper processes to automate today is to manage data inside forms and invoices. Depending on their complexity and contents it\u2019s usually admitted that it takes 5 minutes on average to manually extract the information: someone reads a value on the invoice, types or copy\/pastes the value into the destination (such as ERP), and repeats for all fields. This is not a long-term solution with plenty of double handling struggle, tedious manual tracking in Excel, and disruption of service when someone from the Accounts Payable (AP) team is out-of-office.<\/p>\n

Automation can help, as it can offload the majority of the work with great accuracy and free some time and energy for more stimulating tasks. The core challenge is usually more or less the same: automate the way the data from invoices (vendor, amount, product(s), etc.), gets into their invoice management system.<\/p>\n

What AI Builder can do<\/h2>\n

One of AI Builder’s perks is its document automation prepackaged solution. It\u2019s easy to set up (with point-and-click and wizard-based experiences), leverages deep integration with Microsoft Power Platform as a whole (Power Automate, Power Apps, Power BI, and Power Virtual Agents), and out-of-the-box connect to all things Microsoft (SharePoint, Excel, Dynamics 365, Azure), and hundreds of other apps.<\/p>\n

Implement the solution<\/h2>\n

The fastest way to build something to improve the AP workflow is to use AI Builder\u2019s document automation prepackaged solution. It allows you to very easily extract information from documents and export that in a Dataverse table that can be used to feed an ERP:<\/p>\n

\"\"<\/p>\n

A step-by-step guide<\/a> allows you to get started.<\/p>\n

First the document automation base kit needs to be installed. This usually takes up to 10 minutes for a given environment:<\/p>\n

\"\"<\/p>\n

Once the installation is complete, several objects are now showing under the solution:<\/p>\n

\"\"<\/p>\n

Next the process owner (the person who installed the solution and has rights to modify\/customize all files contained within the solution) needs to properly configure roles in the Power Platform Admin Center; the solution contains a prebuilt Power App that can be used to see and edit what was automatically processed by the solution. The person who should have access to this app should be assigned the role of Manual Reviewer. And the process owner should make sure to have the System Customizer role.<\/p>\n

\"\"<\/p>\n

Objects within the solution then need to be configured so it can properly process the pipeline of documents \u2013 for instance which mailbox will get scanned and for which types of emails. Below it will scan a specific email address (jack@proseware.com) whenever the email contains attachments (\u201cInclude Attachments = Yes\u201d) and only attachments (\u201cOnly with Attachments = Yes\u201d), so emails that contain a proper\/non-empty body of text will not be scanned).<\/p>\n

\"\"<\/p>\n

Once everything is properly configured (see here<\/a> for more details) the flow will automatically parse the emails so the Manual Reviewer can now see invoices flowing into the dedicated Power App:<\/p>\n

\"\"<\/p>\n

Every time a new invoice will be dropped by email it will get automatically processed by AI Builder and once the processing completes, the data will be stored in the \u201cDocument Automation Data\u201d table. The System Customizer can easily tweak this app: display or not display a specific field, display the confidence scores, brand it with a logo, etc.<\/p>\n

Since October 2021 (and to streamline even more the install experience), the solution includes AI Builder\u2019s generic\/prebuilt invoice processing model. This prebuilt model will extract data out-of-the-box (you don\u2019t have to train a custom model with plenty of documents).<\/p>\n

If you see that this generic\/prebuilt model isn\u2019t able to properly extract data from invoices from a specific supplier, you can create a dedicated custom model that you\u2019ll have to train properly so it can extract data from this specific supplier\u2019s documents. Creating (and testing) a new model can take a couple of hours but you\u2019ll then be able to leverage this work automatically, whenever a new invoice from them is dispatched.<\/p>\n

For additional fine-tuning, one can tweak the minimum confidence score below which a manual\/human review will be required. For instance, if you want everything below 60% to be reviewed by a person, you can change that in the dedicated flow (Document Automation Validator):<\/p>\n

\"\"<\/p>\n

Overall \u2013 and depending on the complexity of the invoices\/variety of invoice suppliers one might have, and overall knowledge of the Power Platform \u2013 it usually takes one or two working days to install an E2E working instance of the document automation: from installing the document automation solution, to prototyping, tweaking, and creating the custom form model (if required).<\/p>\n

Next and if you have some suppliers who only send paper invoices, you could tweak the Power App so it can extract information from an picture taken on a phone.<\/p>\n

Expected ROI<\/h2>\n