Expense Review on Autopilot

What this automates

Expense review is a compliance check pretending to be a judgment call. Someone in finance opens each report, squints at line items, and compares them against a policy document they mostly know by heart. The overwhelming majority of reports are fine — and every one of them costs the same review minutes as the genuinely questionable ones.

This blueprint splits the work the way it should be split: machines check every line against the written policy, humans decide only the lines the machine flagged. It's the intermediate blueprint because it chains two different AI nodes — a prompt node for extraction, an agent node for judgment — and that division of labor is the lesson worth learning here.

The design

Step	Node	What it does
1	Submission trigger	Fires when an expense report is submitted — Dataverse row, SharePoint list item, or your expense system's connector
2	Prompt node — extract line items	Normalizes the messy submission into a clean list: date, vendor, category, amount, attendees, notes
3	Agent node (the brain)	Checks each line against the travel-policy SharePoint; returns per-line {compliant, reason} — see below
4	Condition — every line compliant?	Branches on the structured output
5a	Auto-approve + notify AP	All-compliant path: marks approved, posts the summary to the AP channel/queue
5b	Approvals — route exceptions	Any flagged line: creates an Approval for finance with the agent's per-line reasoning in the request body