Log in

Finance

Every transaction checked. Only the violations surface.

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.

Integrates with:

What changes

Before
With ZeroTwo
Transactions reviewed
Controller manually scans each one
All 487 checked automatically; only exceptions surfaced
Time to audit
2 full days per month
Report ready on the 1st; controller reviews in under an hour
Violations caught
Whatever the reviewer spots before fatigue sets in
Every violation, including fuzzy duplicate vendor matches
GL reconciliation
Done separately, often a week later
Included in the same scan with mismatches flagged

Transactions reviewed

Before

Controller manually scans each one

With ZeroTwo

All 487 checked automatically; only exceptions surfaced

Time to audit

Before

2 full days per month

With ZeroTwo

Report ready on the 1st; controller reviews in under an hour

Violations caught

Before

Whatever the reviewer spots before fatigue sets in

With ZeroTwo

Every violation, including fuzzy duplicate vendor matches

GL reconciliation

Before

Done separately, often a week later

With ZeroTwo

Included in the same scan with mismatches flagged

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.

How ZeroTwo scans for expense policy violations

1

Pulls all Brex transactions from the past month

Brex

Pulled 487 transactions from February. $342K total spend across 6 departments. 89 transactions over $500. 12 international charges. 34 recurring vendor payments.

2

Cross-references transactions against GL entries

Sage

GL 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).

3

Checks every transaction against the expense policy and builds the exception report

Google

14 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.

Runs 1st of every month · Exception report in ZeroTwo

Get started in under 10 minutes

1

Connect your tools

One-click OAuth for each integration. No API keys, no engineering.

2

Describe 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.

3

It runs on schedule

Runs on the 1st of each month and produces the exception report in ZeroTwo.

Frequently asked questions

Yes. You define your rules: per-person meal limits, receipt thresholds, approved expense categories, vendor restrictions. ZeroTwo applies them line by line. When your policy changes, update the rules and the next scan uses the new version.

ZeroTwo 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.

Yes. ZeroTwo 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.

Each violation appears in the exception report with the employee name, transaction date, amount, vendor, and the specific policy rule it broke. ZeroTwo does not take action — your controller handles violations according to your internal process.

ZeroTwo 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).

Stop doing the work your tools should do for you.

Set it up once. ZeroTwo runs it every time.