Finance integration guide
Brex + UbiGrowth workflows
Brex is a corporate card and spend management platform that owns card transactions, expense policy, and approvals. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Brex part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a finance workflow around Brex with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Card, Transaction, Expense, Budget, User, and Receipt. Brex identity is the card and the user it belongs to, not the vendor. Spend analysis by vendor requires normalising merchant strings, which arrive as raw descriptors rather than as clean names.
Brex is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
The platform layer is the usual destination for this connection, because the value shows up as governed context and execution shared across more than one team.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Finance integrations carry a different risk profile from the rest of the stack. A duplicated CRM record is annoying; a duplicated payment, a double-posted invoice, or an unauthorized write into Brex is a real financial and control problem.
That is why most finance teams end up doing the work manually. The available automation is fast but cannot demonstrate what it did, and a number without a traceable basis is unusable in a function where everything has to be defensible.
You're likely here because
- Recurring finance analysis is mostly export, match, and reformat
- Approval trails live in email rather than in a system
- AI answers cannot be traced back to a source anyone will accept
Record model
What a Brex integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Brex's.
Identity and matching
Brex identity is the card and the user it belongs to, not the vendor. Spend analysis by vendor requires normalising merchant strings, which arrive as raw descriptors rather than as clean names.
Start here
Detect transactions missing a receipt past the policy window and route the request to the cardholder with the transaction detail attached.
What this will not do
It will not enforce policy. Brex enforces its own controls; the integration handles the exceptions those controls surface.
The constraint to plan around
Transactions post in stages — authorisation, then settlement — and amounts change between the two. A workflow reading authorisations reports numbers finance will not recognise.
Build notes
What you actually have to reason about in Brex.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| merchant descriptor | raw and inconsistent, so vendor analysis requires normalisation rather than grouping |
| transaction status | pending authorisation versus settled, with amounts that change between them |
| card id / user id | the ownership chain for routing a receipt request |
| receipt match state | the compliance gap worth acting on |
| posted_at vs initiated_at | the two timestamps that make finance and cardholder views disagree |
Authentication
OAuth or API token with scoped access to transactions, users, and budgets. Financial data access should be read-only unless a specific write workflow justifies otherwise.
Events and delivery
Webhook coverage exists for transaction events; polling remains common for reconciliation passes. Because settlement amounts change, a reconciliation pass is needed regardless.
Workflow
How the Brex workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Read the source records
Connected Brex records replace the recurring export step, so the analysis starts from current data.
Step 02
Match and reconcile
Records are matched against the other systems involved, and anything that does not match becomes an explicit exception rather than a silent adjustment.
Step 03
Present the working queue
Exceptions and items needing attention are presented with owners, so the review is a queue rather than a highlighted spreadsheet.
Step 04
Stage the action for approval
Where an action is required, it is prepared with its supporting records and held for explicit human authorization.
Design decisions
The finance decisions this connection forces.
Each of these has to be settled before the Brex workflow is allowed to write anything.
Step 01
Start read-only and stay there longer than feels necessary
Read access to Brex delivers most of the reporting and reconciliation value with none of the write risk. Add write paths only when a specific, bounded workflow requires them.
Step 02
Keep authorization human
Anything that moves money, changes billing state, or affects a closed period requires an explicit human authorization step that is recorded, not inferred.
Implementation path
How to implement the Brex workflow.
- 01
Define the data boundary: which Brex records the workflow may read, and what is explicitly out of scope.
- 02
Start with a reporting or reconciliation workflow you already produce manually, so the output can be checked against a known-good answer.
- 03
Reconcile the connected output against the last two closed periods before anyone relies on it.
- 04
After receipt chasing works, add policy-exception reporting so the recurring exceptions drive a policy change rather than more chasing.
Governance
Controls that matter.
Control 01
Payment, billing, and period-affecting actions require explicit human authorization; automation prepares, people approve.
Control 02
Credentials are least-privilege and reviewed, with read and write scopes separated wherever the platform allows it.
Control 03
Every automated action leaves a record that can be reconciled against the source system.
Failure modes
How a Brex integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
Finance disputes the transaction amounts in a report.
Cause
Authorisation amounts were read rather than settled ones.
Fix
Reconcile on settled transactions and label pending figures clearly.
Symptom 02
Vendor spend analysis is fragmented.
Cause
Merchant descriptors are raw and inconsistent.
Fix
Normalise descriptors with a maintained mapping rather than grouping on the raw string.
Symptom 03
A limit change declines a legitimate purchase.
Cause
The automation acted on stale spend data.
Fix
Make limit changes a reviewed action rather than an automatic response.
What changes at scale
Transaction volume scales with headcount and card usage. Incremental reads on posting date are the sustainable pattern rather than full-period pulls.
Examples
What a working Brex workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Spend operations
With Brex connected read-only, the recurring view is assembled from live records rather than a fresh set of exports each cycle.
Reconciliation exception queue
Unmatched or unexpected items from Brex become a working queue with owners, instead of highlighted rows in a spreadsheet emailed around the team.
Limitations and considerations
What to validate before you depend on this.
- Transactions post in stages — authorisation, then settlement — and amounts change between the two. A workflow reading authorisations reports numbers finance will not recognise.
- Card and limit changes affect whether real purchases succeed. An automation adjusting limits can decline a legitimate transaction at the point of sale.
- When the expense policy itself is unclear. Automating exception handling against an ambiguous policy produces confident chasing of the wrong things.
- Nothing produced here is accounting, tax, or audit advice, and no output should be treated as a professional opinion.
- Write access to Brex carries real financial risk. Duplicate protection, idempotency, and an approval step are requirements rather than refinements.
FAQ
Brex integration questions.
What records does a Brex integration actually work with?
The primary records are Card, Transaction, Expense, Budget, User, and Receipt. Brex identity is the card and the user it belongs to, not the vendor. Spend analysis by vendor requires normalising merchant strings, which arrive as raw descriptors rather than as clean names.
What should the first Brex workflow be?
Detect transactions missing a receipt past the policy window and route the request to the cardholder with the transaction detail attached.
What will a Brex integration not do?
It will not enforce policy. Brex enforces its own controls; the integration handles the exceptions those controls surface.
What is the main constraint to plan around?
Transactions post in stages — authorisation, then settlement — and amounts change between the two. A workflow reading authorisations reports numbers finance will not recognise.
What changes about a Brex integration at scale?
Transaction volume scales with headcount and card usage. Incremental reads on posting date are the sustainable pattern rather than full-period pulls.
How does authentication work for Brex?
OAuth or API token with scoped access to transactions, users, and budgets. Financial data access should be read-only unless a specific write workflow justifies otherwise.
Does Brex support webhooks, and can they be trusted?
Webhook coverage exists for transaction events; polling remains common for reconciliation passes. Because settlement amounts change, a reconciliation pass is needed regardless.
What is the risk of writing to Brex?
Card and limit changes affect whether real purchases succeed. An automation adjusting limits can decline a legitimate transaction at the point of sale.
When is connecting Brex the wrong call?
When the expense policy itself is unclear. Automating exception handling against an ambiguous policy produces confident chasing of the wrong things.
What should a Brex integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Brex to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Can the workflow write into Brex?
Only where a specific bounded workflow requires it, with duplicate protection and an explicit human approval step. Most of the value is available read-only.
Is the output auditable?
Execution state and results return to the product surface, and analysis is grounded in connected records rather than an uploaded file, so an answer can be checked against its source.
Is this a replacement for the accounting system?
No. Brex stays authoritative. The workflow layer sits around it to remove the export, match, and reformat cycle.
How this access is governed
What ARIA is allowed to do in Brex, and who decides.
Connecting Brex is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.