|
WORKFLOW |
How to automate multi-entity consolidation with Brex
Local-currency billing and three AI agent roles let subsidiaries stay out of each other's bank accounts while one review queue catches policy exceptions.
Multi-entity consolidation collapses when every foreign subsidiary runs USD cards and someone has to unwind FX markups, intercompany transfers and duplicate receipts at close. Brex addresses this by issuing local-currency cards and billing subsidiaries from their own local bank accounts in more than 50 countries, which means the intercompany transfer for routine operating spend often does not need to happen at all. The FX markup on USD cards is typically up to 3 percent per charge, per the Card Program Terms revised 7 April 2026, so eliminating that markup on local spend is a real line-item difference.
BY THE NUMBERS
|
83/100 AF SCORE, BREX |
6 weeks TIME TO LIVE, AS REVIEWED |
STEP BY STEP
Multi-entity consolidation in Brex, step by step
This workflow takes a controller from a scattered multi-entity card program to a single consolidated exception queue. Complete entity and banking setup before turning on the agent review layer.
1 |
Create a subsidiary entity for each legal entity in Brex and assign the correct local currency and billing country to each. |
2 |
Connect each subsidiary's local bank account as the settlement account so statements and reimbursements clear locally without an intercompany transfer. |
3 |
Upload your expense policy document and any relevant standard operating procedures to the audit agent configuration so it has the rules it will enforce. |
4 |
Set the review agent thresholds: define which transaction types and amounts qualify as low-risk for auto-approval and which must be escalated to a human queue. |
5 |
Connect your accounting system (QuickBooks Online, Xero or Puzzle) by OAuth so approved transactions export to the general ledger without a manual download step. |
6 |
Run a pilot cohort of one entity for two weeks, then open the exception queue each morning and paste the following prompt into Brex Assistant: 'List all expenses flagged by the audit agent in the last 7 days, grouped by entity and violation type, and note which are pending my review.' |
7 |
After the pilot, review the exception rate against your policy definitions; adjust the review agent thresholds if the queue contains items your policy would treat as routine. |
8 |
Roll out remaining entities one at a time, confirming local bank account connectivity and local-currency card issuance for each before moving to the next. |
The automation layer sits on top of that structure. Per Audit Friendly's Brex review, the platform runs three agent roles: an audit agent that checks every expense against the policy and standard operating procedures you upload and ranks violations by risk; a review agent that auto-approves low-risk items and escalates exceptions; and Brex Assistant, which handles employee-facing tasks like filing reimbursements and fetching receipts. The agents entered early access with the Fall Release on 4 November 2025. That layered model means a controller's queue at close contains flagged exceptions rather than every transaction.
Before treating automation as a closed loop, two things deserve attention. First, Brex chose a vendor-set FX rate that can vary by customer, so your actual cost of cross-border spend should be confirmed in the Card Program Terms rather than assumed from a list rate. Second, Capital One completed its acquisition of Brex on 7 April 2026, and the Platform Agreement and Card Program Terms both carry that revision date, so any contract signed before that date warrants a review against current terms. Brex assigns an implementation consultant on professional-services deals and says multi-entity setup can be live within six to eight weeks of kickoff.
For the workflow below, the goal is a single consolidated expense feed where local entities settle locally, the audit agent handles routine review, and a controller touches only the exception queue. QuickBooks Online, Xero and Puzzle connect by OAuth during onboarding, which covers the export step for most mid-market stacks. Measure success by tracking how many line items reach the controller's queue versus total expenses processed, and check that number against what your policy actually defines as an exception.
WORKED EXAMPLE
In practice
A controller managing four entities (two US, one UK, one Canada) needs a consolidated expense report for the month just ended, with exceptions sorted by risk level before close.
What came back. The assistant returned a table of approved spend by entity in local currency, a grouped list of flagged expenses ranked by risk level, and a note that the Canadian entity had one unresolved settlement confirmation. The UK entity showed three flagged items under the 'missing receipt' violation type, two of which had already been resolved by the employee; one remained open and was assigned to the controller's queue. One flagged item in the US entity had been auto-approved by the review agent but the assistant flagged it as borderline given the dollar amount, which warranted a manual look.
How it was checked. The controller cross-referenced the flagged open items against the audit agent's violation log in the Brex interface to confirm the assistant's list was complete and that no resolved items had been misclassified as open.
A constructed example. The prompt is usable as written; the figures show the shape of a result, not a measured one.
WHEN TO USE IT
| WHEN NOT TO
|
WHAT TO TAKE FROM THIS
| Confirm the FX rate and markup terms in the Card Program Terms before projecting savings across entities. | |
| Review the Platform Agreement against the 7 April 2026 revision date if your contract predates the Capital One acquisition. | |
| Audit agent automation requires uploading your policy and SOPs; default behavior without them is not equivalent. |
It's time to set up your holiday streaming campaign
Are you ready to reach holiday shoppers on CTV? For many streamers, the season is already underway.
Last year, according to Roku internal data, holiday content searches on Roku saw an 86% increase during October. And in November, those searches rise an average of 39% weekly. This surging holiday spirit is mirrored by consumer activity, as about half of Roku streamers shopped Black Friday and Cyber Monday deals in 2025.
Meeting those shoppers is easier than you might think. Begin with the seasonal outcome you hope to drive: awareness, online sales, leads, store visits, or another measurable goal. From there, define your audience, upload your creative, set the budget and campaign dates, and establish measurement before launching. You can even create a shoppable ad unit that lets streamers buy with a click of their remote.
Our holiday playbook offers a month-by-month guide to reaching shoppers during this all-important time of year.
First-time spenders get a $5,000 match on the first $5,000 spent with code BEEHIIV5K. Terms apply.
FROM OUR PARTNERS
QUESTIONS THIS ANSWERS
Can each subsidiary pay its Brex statement from a local bank account?
Yes. Per Audit Friendly's Brex review, subsidiaries can pay statements and reimbursements from local bank accounts, which avoids intercompany transfers for local operating spend.
How long does multi-entity Brex setup take?
Brex's enterprise page says as little as 6 to 8 weeks from kickoff when an implementation consultant is assigned on professional-services deals.
Are Brex reward points guaranteed?
No. The Rewards Terms revised 15 July 2026 state that points are not the customer's property and that Brex may change redemption ratios or revoke redemption with or without notice.
Agent readiness, pricing and go-live watchouts.
GO DEEPER
Go deeper
An original workflow written for practitioners. Replicate it in a sandbox first; nothing here replaces your review.
The modern accounting tech stack: tools, automations and workflows shaping the next generation of finance operations.
Modern Accounting · Audit Friendly Data · Accounting & Finance Jobs
Audit Friendly · accountingstack.ai

