Flag expenses that break policy before an approver sees them
Every morning, WebRun opens Expensya, reads the expenses submitted since the last run, checks each one against your policy limits, receipt requirements, and allowed categories, logs every breach in Airtable with the claimant and the rule broken, and posts finance a Microsoft Teams list to settle.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch expense claims that break policy before approval?
Every morning WebRun opens Expensya, reads the expenses submitted since the last run, and checks each one against your policy limits, required receipts, and allowed categories. It logs every breach in Airtable and posts finance a Microsoft Teams list, so problem claims are settled before an approver ever sees them.
- Problem claims are caught the morning after they are submitted
- Approvers stop being the ones enforcing the expense policy
- Repeat breaches by rule and by claimant are counted in one base
Built for finance teams · controllers · office managers · companies with field staff
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
expensya.comin a real browser with your saved login - no setup, no API keys. -
1
Expensya - screen new claims against policy
WebRun opens Expensya to screen new claims against policy. - Open Expensya and list the expenses submitted since the previous run
- Check each claim against your policy: per-category limits, the receipt requirement, and the date window for claiming
- Flag expenses with no receipt attached, an amount over the category limit, or a category that does not fit the stated purpose
- Capture the claimant, the report it sits in, the amount, and which rule it breaks
Done when Every new expense is either clean or recorded with the rule it breaks.
-
2
Airtable - log each breach and its rule
WebRun opens Airtable to log each breach and its rule. - Add a row per flagged expense with the claimant, amount, category, rule broken, and report
- Mark rows resolved once a later run sees the claim corrected or withdrawn
- Keep a running count per claimant and per rule, so a recurring pattern is visible
Done when Airtable holds every flagged expense with its rule and its resolution state.
-
3
Microsoft Teams - post the list for finance
WebRun opens Microsoft Teams to post the list for finance. - Post the day's flagged claims to your finance channel, largest amount first
- Say for each one which rule it breaks and what would fix it, for example a missing receipt
- Leave the outcome to finance. WebRun never approves, rejects, or edits an expense in Expensya
Done when Finance has today's flagged claims with the reason for each one in Teams.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it reject expenses automatically?
No. WebRun flags a claim and explains the rule it breaks. Approving, rejecting, or sending an expense back to the claimant stays with finance and the approving manager.
Does it message the person who claimed?
No. The list goes to your internal finance channel in Microsoft Teams. Any conversation with the claimant is started by a person, in your own words.
Which rules does it check?
The ones you give it: per-category limits, whether a receipt is attached, the claim date window, and category fit. Add or change a rule and the next run applies it.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.