Brex
From card swipes to Brex bill pay to employee reimbursements, if it happens in Brex, it posts in DualEntry.
Overview
The Brex integration connects Brex's spend management layer to DualEntry's general ledger. Transactions coded by your team in Brex post automatically as double-entry journal entries in DualEntry, no manual re-entry required.
DualEntry is the source of truth for your chart of accounts. GL accounts and classifications are pushed from DualEntry to Brex so employees always code against your actual account structure. Vendors are created automatically from Brex merchant data.
Data flows via Brex's official Accounting Partner API using OAuth 2.0 and real-time webhooks.
Credit card transactions
Statement payments
Reimbursements
Bills & bill payments
Rewards
Vendors
Accounts (CoA)
Departments / classes
Data synced
The integration syncs the following data types:
Posts as double-entry journal entry with vendor, amount, and GL code
Card statement payment records linked to the corresponding liability account
Employee reimbursement requests with GL coding applied in Brex
Payment records linked to the originating reimbursement
Bill records with line items and GL classification
Payment records linked to bills; voids handled automatically
Brex rewards posted to the mapped income account
Auto-created from Brex merchant data; deduplication by name
Creates, updates, and archives GL accounts in Brex to match DualEntry
DualEntry Classifications pushed to Brex as Department and Class options
Key Features
- Chart of accounts push
DualEntry pushes your GL account structure to Brex automatically. Employees coding in Brex always see your actual accounts - Real-time sync via webhooks
Brex webhooks push transaction data to DualEntry as it happens. - Multi-entity support
Each Brex legal entity maps to a separate company in DualEntry. Multiple business units under one Brex account post to the correct books automatically. - Department & class mapping
Brex's Department and Class fields map to DualEntry Classifications. Coding applied in Brex flows through to the correct dimensions in your books. - Automatic vendor creation
Merchants from Brex card activity are created as vendor records in DualEntry automatically - OAuth connection
The integration authenticates via Brex's official Accounting Partner API with OAuth 2.0. No shared credentials or CSV exports..
FAQ
The integration uses Brex webhooks to push transaction data in real time. Chart of accounts and classification changes in DualEntry sync to Brex automatically.
Your team codes in Brex, applying GL accounts, departments, and classes to transactions where the spend already lives. Those codes carry through to DualEntry automatically when the transaction syncs.
Updates to transactions in Brex, including coding changes and voids, are reflected in DualEntry on the next sync.
Yes. Each Brex legal entity maps to a separate company in your DualEntry org. Transactions post to the correct entity's books automatically.
