Brex for finance teams: the controls and approvals guide

Most companies adopt Brex for one reason. The old corporate card program was a mess, the personal-card-plus-reimbursement loop was worse, and Brex offered a clean replacement with an actual mobile app. So they swap the cards, turn on the NetSuite or QuickBooks sync, and call it done.

What gets left on the table is the rest of the platform. Brex is not really a card company anymore. It is a spend infrastructure layer with cards, expense, bill pay, travel, and a business account all running on the same data model. Used that way, finance ops stops being a series of monthly fire drills and starts looking like a system.

This piece is for controllers and CFOs at $5M to $200M companies who already have Brex deployed and want to know what the second 80% looks like. The plays below are the ones we actually build for clients, with the integration shape and the failure modes called out.

The Spend Sprawl Most Brex Customers Have

Almost every team we audit has the same set of symptoms. Brex is doing its job. The systems around it are not.

• Month-end close still takes 7 to 10 business days because GL mapping is mostly manual and exceptions are handled in a Google Sheet.
• Policy lives in a Notion doc that no one reads, while the actual card controls in Brex are looser than the written policy.
• Vendor onboarding takes a week because W9 collection, NetSuite vendor setup, and Brex card provisioning are three separate manual steps.
• Bill pay is in Brex but approvals happen in email threads, so the audit trail is split across systems.
• SaaS subscription spend has crept up 30% year-over-year and no one can tell you which tools are actually being used.

None of those problems are Brex's fault. They are integration gaps. Each one closes with a workflow that already has the data it needs sitting in Brex, the HRIS, the accounting platform, and Slack.

Automation Plays We Build with Brex

1. Policy-as-Card-Control Translation

Trigger: the written expense policy gets updated, or a new role is hired. Workflow: we map every policy line to a Brex control (merchant category, dollar limit, time window, approval required) and reconcile the two automatically. When a category is missing from Brex, finance gets a Slack alert. When a Brex card has limits looser than policy, the system tightens it. Outcome: the policy doc and the actual enforced controls stop drifting apart, and finance stops auditing for things that should have been blocked at swipe.

2. Vendor Onboarding to Virtual Card in 10 Minutes

Trigger: ops signs a new vendor or a contractor invoice lands. Workflow: a form collects entity type, W9 or VAT, payment terms, and contract value. The automation creates the vendor record in NetSuite or QuickBooks, provisions a Brex virtual card with a spend cap matching the contract, sets the GL code, and notifies the budget owner in Slack. Outcome: the standard one-week onboarding compresses to under 15 minutes, and the vendor record, the card, and the GL mapping all start aligned.

3. Slack-First Approval Routing

Trigger: a Brex transaction or bill exceeds the threshold for auto-approval. Workflow: the system posts a Slack message to the approver with vendor, amount, GL category, prior 90-day spend with that vendor, and a one-click approve / deny / route-up button. Decisions write back to Brex via API, and the audit trail lives in both Slack and Brex. Outcome: approval cycle time drops from days to minutes, and approvers get the context they need without opening another tool.

4. Month-End Close Orchestration

Trigger: the last business day of the month, or whatever cutoff you run. Workflow: the system pulls the full Brex transaction file, validates that every line has a GL code, an approved memo, and a matched receipt. Exceptions get routed to the relevant cardholder via Slack with a 48-hour SLA. Clean transactions push to NetSuite in batch. A close-readiness dashboard tracks resolution. Outcome: close drops from a 7 to 10 day grind to a 2 to 4 day review pass, and finance stops chasing the same five offenders every month.

5. SaaS Spend Visibility and Renewal Defence

Trigger: a new SaaS charge hits a Brex card, or a known vendor is approaching renewal. Workflow: the system clusters every recurring charge by vendor, attributes it to the responsible team, pulls usage data where available (Slack, Google Workspace, Okta), and surfaces the cost per active user. Renewals 60 days out get flagged with a Slack thread that includes price history, usage trend, and the contract owner. Outcome: SaaS sprawl gets cut at the renewal moment instead of discovered six months too late, and finance walks into every renewal conversation with data instead of guesses.

These five plays compose. The vendor onboarding workflow feeds the close orchestration. The policy translation feeds the Slack approvals. Each one alone moves a metric. Run together, they convert Brex from a card program into the spine of the finance ops stack.

How Brex Should Integrate With Your Stack

Brex is most valuable when it stops being the system you log into and starts being the spend layer that other systems read from and write to. The integration map we build typically looks like this.

• NetSuite, QuickBooks Online, Xero, or Sage Intacct: bidirectional sync of vendors, GL codes, and transactions, with custom mapping per entity.
• HRIS (Rippling, Gusto, BambooHR, Workday): new hire triggers card provisioning with role-based limits, off-boarding triggers card freeze and final reimbursement.
• Slack: approvals, anomaly alerts, budget burn warnings, missing-receipt nudges, all in the channels people already live in.
• CRM (Salesforce, HubSpot): client travel spend tied to opportunity records, so cost of acquisition rolls up correctly.
• BI (Looker, Sigma, Metabase): Brex transaction data piped into the warehouse for spend analytics that go deeper than the native dashboard.
• Procurement and vendor intake forms (Tally, Typeform, internal apps): structured intake feeds Brex card provisioning and NetSuite vendor creation in one shot.

What ROI Actually Looks Like

These are ranges from teams we have shipped this work for, with the usual caveat that every company is different. Indicative, not promised.

• Month-end close: typically lands between 40% and 60% faster once GL mapping, exception routing, and sync are automated.
• Policy violations: usually drop 70% or more, because non-compliant spend gets blocked at swipe instead of caught in audit.
• Vendor onboarding cycle time: typically 3 to 5 days down to under an hour.
• Controller and AP analyst time freed: usually 10 to 15 hours per week per person, redeployed from data entry to actual analysis.
• Software spend visibility: SaaS sprawl typically gets 15% to 25% trimmed in the first 90 days, just because someone can finally see the line items.

The economics typically pencil within the first quarter. Between the freed controller and AP hours, the SaaS spend reductions, and the avoidance of a separate Concur or Bill.com license, the build pays for itself well inside one finance year. The compounding gain comes from the close timeline. A finance team that closes in three days instead of nine gets to spend the other six on the questions that actually move the business.

Where Teams Go Wrong

The wrong moves are predictable. We see the same five patterns in almost every audit.

• Treating Brex as a card replacement only. The cards work fine on day one, so nobody touches the rest of the platform. Bill pay, travel, and AP keep running in legacy tools the company is paying separately for.
• Leaving the NetSuite sync at default. The out-of-the-box mapping covers maybe 60% of the GL accounts a mid-market company uses. The other 40% gets coded to a catch-all and reclassified at close. Painful, every month.
• Letting policy and controls drift. The written policy is updated quarterly. The Brex card controls were configured at onboarding and never touched again. By month six the two have nothing to do with each other.
• Approvals in email. Brex routes high-value transactions cleanly, but if you accept the default email approval flow instead of pushing it to Slack with full context, decisions slow down and the audit trail splits.
• Under-resourcing the build. Teams treat the Brex deployment as an IT project, hand it to one analyst part-time, and expect a finance ops transformation to fall out. It does not. The integrations are not technically complex on their own, but they touch policy, GL strategy, approval authority, and team behaviour. That is a build that needs an owner with both finance fluency and automation fluency, and most internal teams have one or the other, rarely both.

Where Moonira Comes In

Brex is the foundation. The automations on top of it are the work. We build the policy-to-control mapping, the vendor onboarding pipeline, the Slack approval routing, and the close orchestration that turn a card replacement into actual finance ops infrastructure.

If your team has Brex running and the close still takes 8 days, that gap is what we build into.