# Brex

## Overview

The [Brex](https://www.brex.com/) 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.

## Data synced

The integration syncs the following data types:

- **Credit card transactions**  
  Brex → DualEntry  
  Posts as double-entry journal entry with vendor, amount, and GL code

- **Statement payments**  
  Brex → DualEntry  
  Card statement payment records linked to the corresponding liability account

- **Reimbursements**  
  Brex → DualEntry  
  Employee reimbursement requests with GL coding applied in Brex

- **Reimbursement payments**  
  Brex → DualEntry  
  Payment records linked to the originating reimbursement

- **Bills**  
  Brex → DualEntry  
  Bill records with line items and GL classification

- **Bill payments**  
  Brex → DualEntry  
  Payment records linked to bills; voids handled automatically

- **Rewards**  
  Brex → DualEntry  
  Brex rewards posted to the mapped income account

- **Vendors**  
  Brex → DualEntry  
  Auto-created from Brex merchant data; deduplication by name

- **Accounts (CoA)**  
  DualEntry → Brex  
  Creates, updates, and archives GL accounts in Brex to match DualEntry

- **Departments / classes**  
  DualEntry → Brex  
  DualEntry Classifications pushed to Brex as Department and Class options

## **Key Features**

1. **Chart of accounts push**  
   DualEntry pushes your GL account structure to Brex automatically. Employees coding in Brex always see your actual accounts

2. **Real-time sync via webhooks**  
   Brex webhooks push transaction data to DualEntry as it happens.

3. **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.

4. **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.

5. **Automatic vendor creation**  
   Merchants from Brex card activity are created as vendor records in DualEntry automatically

6. **OAuth connection**  
   The integration authenticates via Brex's official Accounting Partner API with OAuth 2.0. No shared credentials or CSV exports.

## FAQ

**How does data sync between Brex and DualEntry?**  
The integration uses Brex webhooks to push transaction data in real time. Chart of accounts and classification changes in DualEntry sync to Brex automatically.

**Does my team code transactions in Brex or DualEntry?**  
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.

**What happens if a transaction is modified in Brex after it has synced?**  
Updates to transactions in Brex, including coding changes and voids, are reflected in DualEntry on the next sync.

**Does the integration support multiple legal entities?**  
Yes. Each Brex legal entity maps to a separate company in your DualEntry org. Transactions post to the correct entity's books automatically.
