Reads every expense report the moment it is submitted, checks each line against your policy, and posts finance one short Slack verdict with the out of policy amounts quoted.
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Berlin Sales Trip, 4 to 7 May
Eleven line items totalling 1,842.60 EUR. Flights Warsaw to Berlin at 312.40 EUR, hotel for four nights at 688.00 EUR, seven meals between 14.20 and 61.90 EUR, and airport taxis at 74.00 EUR. Every item has a receipt attached and each dinner sits under the 75.00 EUR limit.
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Expensify
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Expense policy
The spending rules a report has to satisfy - per item and per category limits, what always needs a receipt attached, categories you never reimburse, how far back a submission can be dated, and what makes a report worth a proper read rather than a rubber stamp.
Choose which agent runs it
NoClick's built-in models work out of the box — or bring Claude Code, Codex, and other coding agents on your own subscription.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Expense review is the work that quietly gets skipped: an approver with forty reports in the queue clicks through them on a Friday afternoon and hopes. This agent reads each report as it lands, checks the line items against the policy you wrote, and posts finance one short Slack note saying clean or here are the three lines to look at, with the amounts quoted next to the limits they cross. It has no approve button and no reject button on purpose, so nobody's reimbursement is ever held up by a machine's opinion.
What do I need connected before it runs?
An Expensify credential that can read reports and policies, and the Slack channel your finance team watches. Then you write the policy in plain English, which is worth doing even if Expensify already holds rules, because your written version can cover the judgment calls a rule engine cannot. The staged test runs show you exactly what a verdict looks like before a real report arrives.
Can it approve or reject anything?
No. Its Expensify tools read reports and policies and nothing else, so approving, rejecting, editing a line, or changing a reimbursement state are all outside what it holds. The only thing it writes is a Slack message. Nobody is paid or refused because of it.
What does it cost to run?
One agent run per submitted report, so the cost follows your submission volume and spikes at month end like everything else in finance. Each run is a report export, a policy read and one Slack message, which keeps it short. A team filing forty reports a month is paying for forty short runs.
Free to start. Guided setup, a test run against staged conversations, and it's live.