What teams build in Prowork for invoice audit and AP

Invoice work runs in two directions at once, and companies here usually build in both: proving what they owe before a payment goes out, and knowing what they are owed while there is still a reasonable chance of collecting it.

Of the 139 companies whose usage went into this study, 102 run some version of this work in Prowork, spread across 1,576 flows that were active in the last 90 days. Grouping those flows by what each one actually does gives the breakdown below.

Freight Invoice Audit is the largest of those patterns at 606 flows across 57 companies, with Accounts Payable accounting for another 276 across 42 companies. The grouping follows what a flow does rather than which team happens to own it, which is why one company often turns up in several of these rows at once, and the businesses building the most of them work in apparel, health and beauty, and logistics.

Three of those flows in more detail, described by what each one does rather than by who built it. Company names are withheld, so each is identified only by the size and category of the business running it.

A $25M+ logistics provider. Processes vendor repair invoices by extracting parts, labor, tax, and work-order details, then matching them to maintenance records for AP review. Allocates costs across line items and flags missing or ambiguous matches so exceptions can be resolved before posting. Built on API, email attachments, SharePoint.

A $1B+ apparel brand. Reconciles vendor invoice PDFs against the AP payment list to confirm the vendor, invoice number, and amount due match. Flags missing invoice support and payment variances so finance can resolve exceptions before payments are approved or released. Built on email attachments.

A $25M+ apparel brand. Reconciles monthly purchase orders by matching received quantities against product invoices, overhead charges, and freight allocations to produce a validated cost report by PO and SKU. Blocks updates and alerts the team when required costs or quantities are missing, ensuring only clean reconciliations are appended to live reporting. Built on Google Sheets, Slack, API, Shopify, email attachments.

Read enough of these flows and the same shape keeps appearing. A flow pulls the same records from each system that holds a version of them, standardizes whatever identifiers are needed before those records can be joined at all, applies the comparison or the calculation as explicit logic, and then labels every row with an outcome so that the handful needing attention can be routed to whoever is able to act on them.

What differs from one flow to the next is which single step genuinely calls for interpretation. Reading a supplier PDF, resolving a merchant name that never quite matches the ledger, or deciding which category a vague line description belongs in are all handled by AI steps inside the flow, while the matching rules, the tolerances and the thresholds around them stay explicit, since those are the parts a controller or an auditor will eventually want to read for themselves.

Most of these run on a schedule or fire from a trigger rather than waiting for someone to remember to open them, and that is largely what separates a report describing what happened last month from a process that surfaces the problem while there is still time to do something about it.

The sources they read from are worth noting, because they are rarely the tidy ones. Across the documented flows in this category the most common inputs look like this:

Email attachments and spreadsheets sit at the top of that list on most pages, which is a fair description of where operational data actually lives once it leaves a system of record.