Data Panda brings your Brex data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
Brex was started in 2017 in San Francisco by Henrique Dubugras and Pedro Franceschi, two Brazilian founders who had built and sold the payments company Pagar.me before going through Y Combinator. The product began as a corporate charge card aimed at venture-backed startups, then grew into spend management with Brex Empower, then added bill pay, travel and global payments. The customer base now runs from seed-stage startups to companies like DoorDash, OpenAI and Reddit.
The reason to pull Brex into a warehouse is that the card sees the spend first. Card transactions, expense submissions, vendor payments, travel bookings and budget caps live inside Brex hours or days before they reach NetSuite or Sage Intacct. Joined to your CRM, your HRIS and your accounting ledger, that early signal is how finance answers questions about department burn, policy drift and travel-versus-budget without waiting for the close.
Department burn, policy violations and travel drift on a live timeline instead of a month-end PDF.
Let the rest of the stack react to a card swipe the same hour Brex sees it.
Use Brex history to predict overruns and catch the receipt that never arrives.
Internal tools around the spend data that is otherwise stuck in the Brex console.
A list of concrete reports, automations and AI features we have built on Brex data. Pick the one that matches your situation.
Which department is going to blow its quarterly budget if nothing changes?
In-month spend velocity per cost centre projected against the budget that approved it. Surfaces the team whose burn is on track for an overrun two or three weeks before the close, instead of after, with the largest contributing vendors next to it.
How much of our card programme is dead weight?
Cards that have been issued but not used in the last quarter, broken down by department and by manager. Separates the cards a leaver kept from the cards a current employee never activated, so the cleanup is targeted instead of a blanket revoke.
Where are reimbursements stuck and why?
Median days from expense submission to pay-out per approver and per entity, with the slowest approvers at the top. Joined to the policy-violation list, you see whether the delays are caused by genuine policy questions or by approvers sitting on the inbox.
Department burn, policy-violation rate and reimbursement cycle time tied to the budget the board signed off on. Month-end stops being the moment finance discovers a team blew through its quarterly cap two weeks ago.
Travel and entertainment spend tied to the customer accounts and opportunities it was meant to support. The deal that consumed three flights and a steak dinner shows up next to its closed-won number, so account economics are not folded into a generic T&E line.
Vendor concentration, duplicate SaaS subscriptions and card-issued-versus-active rates. The operational decisions about which vendors to consolidate and which cards to revoke run on data instead of on a quarterly audit.
Card transactions, expense reports and bill payments from Brex post to Sage Intacct as journal entries with department, location and project dimensions already filled in. The general ledger reflects what the card saw within hours, so accruals at month-end stop being a guessing game.
Travel, entertainment and customer-event charges in Brex are matched to the Salesforce account or opportunity they were booked against. Account-level cost-to-serve and per-deal T&E sit next to closed-won, so account economics get the same scrutiny as pipeline.
Out-of-policy charges and budget-cap breaches push to the cardholder's manager in Slack the same hour Brex flags them, with the vendor, the amount and the policy rule attached. Quiet violations stop accumulating into a quarterly clean-up exercise.
Brex charges tagged to a customer or prospect post to the HubSpot company timeline, so account managers see the dinner, the conference badge and the demo travel in the same view as emails and meetings. Account investment becomes visible to the team that owns the relationship.
You keep the reporting tool you already have. We connect it to the warehouse where your Brex data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Yes. Each Brex entity lands in its own schema with a shared chart of accounts and cost-centre dimension on top, and original-currency amounts are kept alongside the converted figure. Group reporting and per-entity reporting both stay possible without losing the FX detail.
Receipt metadata, OCR-extracted line items and free-text memos sync alongside the transaction record so they stay queryable in the warehouse. The receipt files themselves stay in Brex; we keep the references so an automation or app can deep-link back to the original.
We review your Brex setup and the systems around it. Together we pick the first thing worth building.