Automated Brex Reimbursement Tracking
Every morning, WebRun opens Brex, finds every employee reimbursement still pending approval, records who submitted it, the amount, the expense category, and the days it has waited, writes the queue into Notion, and posts approvers a Teams list with the oldest claims first.
How do I see which employee reimbursements are waiting on approval?
Every morning WebRun opens Brex, finds the employee reimbursements still waiting on an approver, and records each one's submitter, amount, expense category, and days waited. It logs the queue in Notion and posts Microsoft Teams a list ordered oldest first, so staff are paid back in the cycle they claimed in.
- Staff get paid back in the same pay cycle they claimed in
- Every approver sees their own pending claims each morning
- Claims waiting over 5 days are flagged before anyone chases
Built for finance teams · controllers · office managers · startup ops
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
dashboard.brex.comin a real browser with your saved login - no setup, no API keys. -
1
Brex - find reimbursements pending approval
brex.com
WebRun opens Brex to find reimbursements pending approval. - Open Brex and filter reimbursements to those still awaiting approval
- Capture the submitter, amount, expense category, and submission date for each
- Work out the days waited and which approver each one currently sits with
Done when Every pending reimbursement is listed with its submitter, amount, and age.
-
2
Notion - log the queue with its ageing
notion.so
WebRun opens Notion to log the queue with its ageing. - Update the reimbursement queue database with today's pending claims
- Set submitter, amount, category, days waited, and approver on each row
- Close out rows for claims approved or rejected since the last run
Done when The Notion queue matches the live pending list in Brex.
-
3
Microsoft Teams - put it in front of the approver
microsoft.com
WebRun opens Microsoft Teams to put it in front of the approver. - Post the finance channel a list grouped by approver, oldest claim first
- Flag anything waiting longer than 5 days and anything above your review threshold
- Never approve, reject, or pay a reimbursement. WebRun only queues them for a person to decide
Done when Each approver can see their own pending claims 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 approve reimbursements on my behalf?
No. Approving releases money, so WebRun never clicks approve or reject. It only builds the queue and shows each approver what is waiting on them, and the decision stays with a person in Brex.
Does it message the employees who submitted?
No. The only output is an internal Notion record and an internal Teams post. Employees are never contacted, so nobody gets an automated nudge about their own claim.
How does it know what is urgent?
It sorts by days waited and flags anything over 5 days plus anything above the amount threshold you set, so the oldest and largest claims sit at the top of the Teams post.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.