Finance · Track & Escalate
Every transaction checked. Only the violations surface.
Brex transactions from the past month are pulled, matched line-by-line against your policy rules (meal limits, receipt thresholds, category requirements), and cross-referenced with Sage GL entries. What lands in your inbox is an exception report with 15 violations, not 500 rows.
Works acrossBrexSage
What you get.
Every Brex transaction checked against your expense policy and cross-referenced with Sage GL entries. The controller reviews 15 flagged exceptions instead of scanning 500 transactions.
The controller spends two days reviewing transactions that a policy check could catch in minutes.
Month ends. The controller exports 487 Brex transactions into a spreadsheet and starts reviewing. Duplicate charges, meals over the $75 limit, uncategorized spend, missing receipts. It takes two full days. By the time they finish, two more weeks of transactions have piled up.
The real problem is not the time. It is what gets missed. A $2,400 duplicate SaaS charge slipped through for three months because the vendor name was slightly different on the second charge. A team lead's $1,200 dinner was filed under "Client Entertainment" but had no client name attached. These violations are easy to catch when you check every line. Nobody checks every line.
What changes.
- 01Transactions reviewedBefore · Controller manually scans each oneWith Doe · All 487 checked automatically; only exceptions surfaced
- 02Time to auditBefore · 2 full days per monthWith Doe · Report ready on the 1st; controller reviews in under an hour
- 03Violations caughtBefore · Whatever the reviewer spots before fatigue sets inWith Doe · Every violation, including fuzzy duplicate vendor matches
- 04GL reconciliationBefore · Done separately, often a week laterWith Doe · Included in the same scan with mismatches flagged
How Doe scans for expense policy violations
- 01Pulls all Brex transactions from the past monthBrexPulled 487 transactions from February. $342K total spend across 6 departments. 89 transactions over $500. 12 international charges. 34 recurring vendor payments.
- 02Cross-references transactions against GL entriesSageGL entries for February pulled. 3 Brex transactions have no matching GL entry. 2 GL entries reference vendors not appearing in Brex data (possible manual payments booked incorrectly).
- 03Checks every transaction against the expense policy and builds the exception reportDoe14 exceptions: 2 duplicate vendor charges ($2,400 and $890), 3 meals over the $75 per-person limit, 4 transactions missing receipt attachments, 2 charges with no expense category, and 3 Brex-to-GL mismatches. Each includes employee, date, amount, and specific policy violated.
- 04Recurring1st of every monthRuns on the 1st so the exception report is ready before the controller starts their day. Violations accumulate month-over-month for trend tracking. Exception report in Doe.
Up and running in under ten minutes.
- 01Connect your toolsOne-click OAuth for each integration. No API keys, no engineering.
- 02Describe what you need“On the 1st of each month, pull every Brex transaction and check against our expense policy: $75 per-person meal limit, receipts required over $25, no duplicate vendor charges. Cross-reference with our Sage GL.”
- 03It runs on scheduleRuns on the 1st of each month and produces the exception report in Doe.
Before you delegate.
- 01Can Doe learn our specific expense policy?Yes. You define your rules: per-person meal limits, receipt thresholds, approved expense categories, vendor restrictions. Doe applies them line by line. When your policy changes, update the rules and the next scan uses the new version.
- 02What about edge cases like split transactions or partial reimbursements?Doe flags anything it cannot cleanly resolve. Split transactions where the combined amount exceeds a policy limit get flagged. Partial reimbursements that create an apparent mismatch get flagged with context. The goal is zero missed violations, not zero false positives.
- 03Does it catch duplicate charges with different vendor names?Yes. Doe matches on amount, date proximity, and vendor name similarity. If "Acme Software Inc" and "ACME SW" both charge $2,400 within a few days, both get flagged as a possible duplicate. The controller confirms or dismisses each one.
- 04What happens when Doe finds a violation?Each violation appears in the exception report with the employee name, transaction date, amount, vendor, and the specific policy rule it broke. Doe does not take action — your controller handles violations according to your internal process.
- 05How does the GL cross-reference work?Doe matches each Brex transaction to a corresponding Sage GL entry by amount, date, and vendor. Unmatched transactions on either side get flagged: Brex charges with no GL entry (possibly unbooked), and GL entries with no Brex match (possibly manual payments that need verification).