Eleven owners, eleven five-line messages: spent against allocated, the three largest charges, anything recurring that started this period, days remaining. Four minutes to read and send.
Delegated budgets work until somebody checks them. Eleven owners, eleven mental models of their own spend, and a finance team that finds out on the 28th that one of them committed to an annual tool in week two.
A companion reads transactions, cards, budgets and users, and assembles one message per owner with the transactions underneath. It does all eleven while you read the first.
01
What should a budget owner receive each week?
Their own number, with the transactions under it.
Spent against allocated, the three largest charges, anything recurring that started this period, and how many days remain. Five lines.
A companion assembles one per owner and drafts them. You read eleven short messages and send them, which takes four minutes and replaces the conversation you would have had on the 28th.
02
Which receipts and memos are missing?
A companion reads the transactions, finds the ones with no receipt or a memo that says nothing, and groups them per person with dates and merchants so the request is specific.
Capture happens in the Brex app at the moment of purchase. What a companion adds is the accounting of which purchases never got one.
03
Paying twice for the same tool
Two teams with overlapping tools, a subscription renewed on a card while the invoice is also being paid, an annual plan bought three weeks after the monthly one.
Grouping transactions by vendor and by cadence exposes those with the specific charges attached. From there it is a conversation. Related habit: audit your saas subscriptions with ai.
04
Money movement stays inside Brex
Payments, transfers, card issuing, limit changes and approval chains belong inside the product with the people authorised to use them. This connection is a reading and drafting layer over the top.
The reachable surface follows the Brex public API, so confirm the object you want is exposed before you build a weekly routine around it. Finance patterns: ai for finance teams.
Yes. A companion reads budgets and transactions through a connected Brex account and drafts one short message per owner with the underlying charges attached. You send them.
Payments, transfers, card issuing and limit changes all stay inside Brex under its own approvals. This connection reads and drafts.
Yes. Connect the account and a companion reads transactions, cards, budgets and users, and tells each owner what they have actually spent this month. The actions available follow the Brex public API, and payments stay inside Brex.
Group transactions by vendor and by cadence. Overlapping monthly and annual plans, and the same vendor under two merchant names, show up straight away with the charges attached.
A companion finds the transactions with no receipt and drafts the ask to the right person, naming the specific charge. Capture and matching happen in Brex at the moment of purchase.