Power Automate RPA for Invoices: Licenses, Sizing and When to Use It

Robotic process automation drives an application through its user interface, the way a person would, because that application has no API. It is the fallback, not the design. The order of preference for the posting step of an invoice process:

A typical invoice pipeline has eight steps: intake from a shared mailbox or SharePoint folder; validation of sender, file type and duplicates; field extraction with AI Builder's prebuilt invoice processing model; a confidence check that routes low-confidence documents to a review queue; a record in Dataverse or SharePoint with status and audit history; approval in Teams by amount, vendor or cost center; posting to the finance system by one of the four options above; and an exception log that someone owns. Only step seven is ever RPA.

Decision rule: if the finance system offers any of the first three options, the project has no desktop flow and no Process license. Confirm that before pricing anything.

Prices are Microsoft list price from the October 2026 price list, per month on an annual commitment, with the month-to-month price in brackets. Microsoft bills them to you. Entitlements are from Microsoft's license types documentation, updated 22 September 2026.

Three rules from the same documentation decide who needs which. A capacity license does not replace a user license: creating automations and running desktop flows, attended or unattended, require a licensed person, the machine that receives a Process license must have been registered by a Premium user, and the monitoring pages for machines and desktop flows are shown only to Premium users. An automated or scheduled flow runs in its owner's context, so one Premium maker covers a flow that nobody else triggers. An instant flow (a button, a Teams action) runs in the context of whoever presses it, so if it touches a premium connector, every user who runs it needs Premium, or the flow carries a Process license instead.

The legacy per-user plan and per-flow plan, and the unattended RPA add-on, were removed from Microsoft's price list on 1 February 2024; existing per-flow licenses keep working but cannot be stacked or added to. The Process license is their replacement, and it is simpler: one license per machine covers every desktop flow on that machine and the cloud flows in the same business process.

Every work account in a Microsoft 365 tenant can build cloud flows with standard connectors (SharePoint, Outlook, Teams, Approvals, Forms, OneDrive) and can build and run desktop flows locally in attended mode in the default environment. That covers a surprising amount of invoice work: a shared-mailbox trigger, an attachment saved to a SharePoint library, an Approvals card in Teams, and a status column updated.

It stops at four places. Premium connectors, including Dataverse outside Teams, SQL Server, HTTP and every finance system connector. Unattended desktop flows. Sharing a desktop flow or running it outside the default environment. And AI Builder: a Microsoft 365 license carries no AI Builder credits, so the moment the pipeline reads an invoice with AI Builder, somebody holds Premium or the flow holds Process.

The request ceiling is lower too: 6,000 Power Platform requests per user per 24 hours on a Microsoft 365 license, against 40,000 for Premium. Decision rule: a Microsoft 365-only build is fine for a workflow that moves files and asks for approvals; the day it reads documents or posts to a finance system, license it properly rather than working around the limit.

Assume 500 invoices a month, one finance person who builds and owns the flows, ten approvers, and an on-premises accounting package with a Windows client and no connector. Prices are Microsoft list, October 2026 price list, annual commitment.

Why scenario D licenses the flow rather than the approvers: ten approvers on Premium would be $150.00 a month, the same as one Process license, and the Process license also survives staff turnover, holds the higher action limit, and does not care who presses the button. Above ten approvers the Process license is cheaper outright.

AI Builder credits are consumed as documents are processed, and each Premium or Process license adds 5,000 credits a month to the tenant. Microsoft publishes the credit cost per page for invoice processing on its AI Builder calculator; run your monthly page count through it before deciding whether 5,000 credits from one license is enough or whether the AI Builder capacity add-on is needed. That add-on is not on the October 2026 price list we publish from, so it is quoted on request.

Dataverse is the other line item at scale: the Dataverse Database Capacity add-on is $40.00 per GB per month, File Capacity $2.00 per GB, and Log Capacity $10.00 per GB, annual commitment, which is why many 500-invoice pipelines keep the PDF in SharePoint and only the metadata in Dataverse. The capacity rules are in Dataverse capacity and pricing explained.

Every action in a cloud flow counts as a Power Platform request: connector calls, HTTP actions, compose steps, variable initializations, retries and pagination, successful or not. A loop counts its own action plus every action inside it per iteration, so a loop with two actions over 10 invoices is 21 requests. Actions inside a desktop flow do not count; only the call from the cloud flow does.

Microsoft's limits (documentation updated 8 September 2026): 40,000 requests per 24 hours per Premium user, 6,000 per Microsoft 365 user, 250,000 per Process license, and 100,000 in any five-minute window regardless of license. Microsoft is in a transition period in which Premium and Microsoft 365 limits are applied per cloud flow rather than per user, at 200,000 and 10,000 respectively, and Process at 500,000; a flow that stays above its transition limit for 14 consecutive days is suspended until a Process license is assigned. Enforcement of the official limits begins at least six months after Power Automate usage reporting is generally available.

Two levers exist. Stack up to 10 Process licenses on one flow, 250,000 requests each, or put up to 25 solution-aware flows in a flow group that shares one license. The Power Platform Requests add-on ($50.00 per month, annual commitment) raises a limit by 50,000 but cannot currently be assigned to a user or a flow, so it is not the fix for a single throttled flow. For 500 invoices a month at even 200 actions each, 100,000 requests a month is far inside a Premium owner's limit; the limit matters when a flow polls a mailbox every minute or loops over a whole library.

An attended desktop flow runs on the maker's own PC while they watch; it is what Premium includes, and it is right for a finance person who presses a button to post the morning's batch. An unattended desktop flow runs on a machine with nobody signed in, triggered by a cloud flow or, since October 2026, by a scheduled trigger set directly in the Power Automate automation center with daily, weekly, monthly, hourly or custom recurrence. Unattended runs need a Process license allocated to the machine, and one bot executes one unattended desktop flow run at a time; a second concurrent run needs a second Process license on the same machine.

The machine is a Windows PC or virtual machine you provide, registered with Power Automate for desktop by a Premium user, with the accounting client installed and a dedicated service account that owns the sessions. The Hosted Process license removes the machine: Microsoft provides and manages a virtual machine on Azure, and each license supports one hosted bot, individually or in a hosted machine group that scales between committed and maximum bots.

Governance that belongs in the first build, not the second: separate development and production environments; a data loss prevention policy that keeps finance connectors away from consumer connectors; credentials for the accounting client stored as Power Platform credentials rather than in the flow; and a named owner for the exception queue. Microsoft's roadmap lists a flowchart authoring mode for desktop flows for November 2026, which makes a screen-driven posting flow easier to maintain when the vendor changes a dialog.

Three signs that the invoice project should not use RPA at all. The finance system is cloud-hosted with an API: build a custom connector or use the vendor's own. The volume is high and the logic is integration rather than people: Azure Logic Apps bills per action without per-user licenses, and the move is covered in Power Automate vs Azure Logic Apps. The accounting package is due for replacement within a year: do not automate a screen you are about to retire; automate the approval and the filing, and post by hand until the new system's connector exists.

Where RPA is right, keep it small: one desktop flow, one machine, one Process license, and a cloud flow that does everything else. The services that build this are fixed price, quoted in writing before work begins: AI document and invoice processing automation from $6,950 for the full pipeline, purchase request and approval automation in Teams at $1,950 per project for the approval half alone, business process automation with built-in Microsoft 365 tools at $1,500 per project for a Microsoft 365-only build, and custom business apps and process automation at $175 per hour for the desktop flow itself.

What license do I need for Power Automate RPA?

The person who builds and manages desktop flows needs Power Automate Premium, $15.00 per user per month on an annual commitment at Microsoft list price. Unattended runs need a Power Automate Process license on the machine, $150.00 per month, or a Hosted Process license at $215.00 if Microsoft hosts the machine.

Can I run Power Automate RPA with just a Microsoft 365 license?

Only attended desktop flows on your own PC in the default environment, with standard connectors and no AI Builder. Unattended runs, premium connectors, sharing a desktop flow and document processing all need Premium or Process.

How many Process licenses do I need?

One per machine that runs unattended desktop flows, which covers every desktop flow on that machine and the cloud flows in the same process. Add one for each additional concurrent run on the same machine, and one for each cloud flow you want licensed on its own rather than through its owner.

Does AI Builder cost extra for invoice processing?

Each Premium or Process license includes 5,000 AI Builder credits a month, consumed per page processed at the rate Microsoft publishes in its AI Builder calculator. Beyond that, the AI Builder capacity add-on is quoted on request.

What happens if a flow exceeds its action limit?

During Microsoft's current transition period a flow above its per-flow limit for 14 consecutive days is suspended and its owner notified; assigning a Process license raises the limit to 250,000 requests per day and the flow can be turned back on. Up to 10 Process licenses stack on one flow.

Is Power Automate RPA the same as the old UI flows?

Yes. UI flows became desktop flows in Power Automate for desktop, with attended and unattended modes, machine groups, and since 2026 scheduled triggers and a flowchart authoring mode.

• Types of Power Automate licenses — Microsoft Learn, updated 2026-09-22, checked 2026-10-11
• Power Automate licensing FAQ — Microsoft Learn, updated 2026-09-22, checked 2026-10-11
• Requests limits and allocations — Microsoft Learn, updated 2026-09-08, checked 2026-10-11
• Power Automate pricing — Microsoft, checked 2026-10-11
• Microsoft 365 roadmap, item 573278: Schedule desktop flows directly with Scheduled Triggers — Microsoft, launched October 2026, checked 2026-10-11
• Microsoft 365 roadmap, item 573292: Build and visualize desktop flows using Flowchart mode — Microsoft, planned November 2026, checked 2026-10-11