Post

Build AI-powered invoice document automation in Power Automate

Diesen Beitrag auf Deutsch lesen

Extract invoice data from Outlook PDF attachments with AI Builder, route it for approval, store it in SharePoint and generate a Word document.

Original article from March 13, 2026: AI-POWERED DOCUMENT AUTOMATION WITH POWER AUTOMATE, by penbot_rpa, on PenBot_RPA. Read the original

Source may be outdated. The original article is more than 60 days old. Dates and availability refer to the state of the source.

This is our own summary, not a republication or full translation.

Schematic view of the steps described by PenBot_RPA, not a screenshot.

TL;DR

A two-flow Power Automate pattern saves Outlook PDF attachments to OneDrive, uses an AI Builder prompt to extract invoice fields and line items, requests approval, stores header and item data in SharePoint, then populates a Word template and emails confirmation.

Why it matters

  • Makers: Build separate extraction and document-generation flows to turn approved Outlook invoice attachments into Word files.
  • Makers: Configure Word content controls and a repeating myTable section so SharePoint item rows populate the document output.
  • Admins/IT: Review OneDrive sharing settings because the flow creates view links for source files and organization edit links for generated documents.

Frequently asked questions

How does the AI Builder prompt extract invoice fields from an Outlook PDF attachment?

The Run a prompt action receives the attachment file content and requests document number, date, discount, total, and item details as JSON.

Which SharePoint lists are needed for this Power Automate invoice workflow?

The workflow uses separate header-level and item-level lists. Both lists include a status choice that moves from New to Done.

How does Populate a Microsoft Word template add invoice line items?

The second flow gets SharePoint item records by document number and passes Select output into the Word template's repeating myTable field.

Summary by KMUpower, licensed under CC BY 4.0 . Rights to the original article remain with its author.