POWER AUTOMATE FLOW MOCKUP
InvoiceFlow AP — approximates the cloud flow designer canvas: trigger, AI Builder extraction, conditional branching, approval, exception handling. Static reference only.
InvoiceFlow AP — Automated Invoice Processing ● Turned on
Save
Test
28-day analytics
Run history
When a file is created
SharePoint — Incoming Invoices
Extract invoice fields
AI Builder — Invoice Processing model
Vendor, Invoice #, Amount, PO Ref, Due Date 94% confidence
Condition
Amount ≤ ₹2,500 AND PO matched
YES
Auto-approve
No human step needed
NO
👤
Start approval
Adaptive Card in Teams
📤
Post to ledger (child flow)
PostToERP_v1 · updates Dataverse Invoice status
Scope: Catch (configure run after = has failed)
Log exception + Teams alert to AP Lead
Recent runs
RunTrigger fileDurationStatus
#4821Invoice_NorthlineSupplies_2312.pdf8.2sSucceeded
#4820Invoice_Ashford_0091.pdf11.6sSucceeded
#4819Invoice_Meridian_5502.pdf4.1sFailed — SharePoint throttled, retried
What this shows: the try/catch scope pattern and child-flow reuse (PostToERP_v1) represent production-grade reliability engineering, not a one-shot happy-path demo. The run history panel is what turns "I built a flow" into a measurable, monitored automation asset.