Date: 2026-05-13 Product: Brex (brex.com) -- Corporate Cards + Spend Management Platform, San Francisco (US) / Amsterdam (EU) Purpose: Evaluate Brex's API capabilities for Orcha integration -- specifically for a German customer evaluating Brex as a Pleo alternative for employee credit cards while continuing to use Orcha for AP invoices and DATEV for accounting.
Brex is NOT an ERP or accounting system. Like Pleo, Ramp, Payhawk, and Moss, it is a spend management platform that handles:
Brex sits upstream of the ERP -- it captures, codes, and approves expenses, then exports pre-accounted data to the customer's actual accounting/ERP system (NetSuite, Sage Intacct, QuickBooks, Xero, Microsoft Dynamics 365 Business Central, Workday Financials, Oracle Fusion Cloud, SAP Concur, etc.).
Brex is the second-largest US spend-management fintech (behind Ramp), known for an unusually mature API surface and first-class developer tooling. In April 2026, Brex shipped an official MCP server (Beta) for AI assistants, putting it on the leading edge of the agent-integration trend. (developer.brex.com/changelog)
Implication for Orcha: Brex is a peer (spend management) layer, not a target system to push invoices into. For the customer scenario in scope (German company, Orcha = AP, DATEV = accounting, Brex considered for cards), the integration question is narrower:
However, the gating question is whether Brex can service the customer at all. See section 1.
Brex secured its EU Payment Institution license via the Netherlands on 7 August 2025 and is operating a phased rollout. German-headquartered companies cannot directly sign up as Brex customers in mid-2026; the company is onboarding "select" EU customers and expects to be fully operational "in early 2026" -- a target that is now slipping into the broader 2026 calendar. (brex.com/journal/press/brex-secures-eu-payment-institution-license, tech.eu)
The relevant facts:
| Question | Answer | Source |
|---|---|---|
| Can a German-HQ company sign up for Brex today (May 2026)? | NOT GENERALLY -- phased rollout with "select" customers via a partner-led GTM (Navan, Zip). No public self-serve EU signup yet. Pre-EU-license customers had to be US-HQ or US-domiciled. | tech.eu |
| Can Brex issue EUR cards to a German entity? | YES IN PRINCIPLE under the new EU PI license (Netherlands), which provides EU/EEA passporting rights to all 30 EU/EEA countries including Germany. Direct EU card issuance is the headline service of the license. | brex.com/journal/press/brex-secures-eu-payment-institution-license |
| Which European countries are covered? | All 30 EU/EEA states via Dutch PI passporting. UK requires a separate license (in progress, no public ETA). | paymentexpert.com |
| Multi-currency? | YES. Brex globally supports 60+ currencies. Locally issued cards in 50+ countries on the Enterprise tier (Smart Card / Enterprise plan). Essentials and Premium include "1 local card program" only. | brex.com/pricing |
| EUR billing for German customer? | YES (post-launch) under the EU PI license -- direct EUR settlement, EUR-funded cards, EU SEPA direct debits, and SEPA credit transfers all included in the licensed services. | brex.com/journal/press/brex-secures-eu-payment-institution-license |
| PSD2 / SCA compliance? | YES, native. As an EU-licensed Payment Institution under PSD2, Brex must comply with PSD2 + SCA requirements. Locally-funded reimbursements explicitly require SCA enrollment for the funding admin in EU/UK regions. | brex.com/support/locally-funded-reimbursements |
| EU offices? | Amsterdam, Netherlands -- ~12 staff across sales, ops, customer success as of August 2025. | brex.com/journal/press/brex-secures-eu-payment-institution-license |
| Existing EU footprint? | ~1,500 customers with EU operations (pre-license; these were US-HQ entities running EU subsidiaries). | brex.com/journal/press/brex-secures-eu-payment-institution-license |
| DATEV integration? | NO. Not listed in Brex's ERP integration documentation. Not mentioned in EU launch materials. CSV / Custom Accounting export is the only path for non-supported ERPs. | brex.com/support/brex-erp-integrations |
| ZUGFeRD / XRechnung support? | NO public mention. | n/a |
| German-language UI / VAT compliance? | PARTIAL. "No VAT documentation" is explicitly listed as an Essentials-tier limitation, implying VAT support exists on higher tiers but is not detailed publicly. | costbench.com/software/expense-management/brex |
Bottom line: Brex is further along the EU runway than Ramp (Brex has the license + 9 months on the ground; Ramp's direct-EU onboarding begins summer 2026), but the practical onboarding pipeline is partner-led and "select-customer" only. For a German Mittelstand company that uses DATEV today and won't migrate, Brex faces the same disqualifying gap as Ramp: no DATEV integration, no native ZUGFeRD/XRechnung handling, no German-language UI confirmation. Brex's go-to-market is explicitly tuned to multinational US-anchored customers with European subsidiaries (Ooni, Navan customers, etc.), not to German-HQ SMBs with German accountants.
The rest of this document continues for comparison reference and to inform Orcha's roadmap thinking if/when Brex builds DATEV support.
| Capability | Public API | Via Zapier | Via Workato | Via Make | Via DATEV | Via CSV | Verdict |
|---|---|---|---|---|---|---|---|
| Read card transactions (settled only) | YES (GET /v2/transactions/card/primary) |
YES ("Pending Card Transactions" trigger, Search Card Transactions action) | YES (HTTP/native partner) | NO native | N/A (no DATEV) | YES (export) | Available now (settled only) |
| Read pending card transactions | LIMITED -- not in main Transactions API; Zapier trigger exists for pending but the API itself is settlement-delayed | YES (instant trigger) | YES via Zapier passthrough | NO | N/A | NO | Limited |
Real-time webhooks (EXPENSE_PAYMENT_UPDATED, ACCOUNTING_RECORD_READY_FOR_EXPORT, TRANSFER_PROCESSED, TRANSFER_FAILED, USER_UPDATED, REFERRAL_*) |
YES | N/A | YES | NO | N/A | N/A | Available (8 event types) |
transaction.created real-time event |
NO -- closest is EXPENSE_PAYMENT_UPDATED (near-real-time once settled); the Transactions API itself is settlement-delayed |
NO | NO | NO | N/A | N/A | Settlement delay (gap) |
| Read expenses + receipts | YES (Expenses API, GET /v1/expenses, GET /v1/expenses/{id}) |
YES | YES | NO | N/A | YES | Available now |
| Receipt upload | YES (POST /v1/expenses/card/{expense_id}/receipt_upload returns pre-signed S3 URL, 30-min PUT window) |
NO | YES | NO | N/A | N/A | Available now |
| Receipt download (binary or signed URL) | NOT EXPLICITLY DOCUMENTED -- receipts are stored and matched server-side but API endpoint for direct binary download is not surfaced in public spec; receipt object reference is exposed on expense. URL longevity unclear. | NO | NO | NO | N/A | NO | Gap / undocumented |
| Read vendors | YES (GET /v1/vendors) |
YES (Find Vendor) | YES | NO | N/A | YES | Available now |
| Write vendors | YES (POST /v1/vendors, PUT /v1/vendors/{id}, DELETE /v1/vendors/{id}) |
YES (Create Vendor, Update Vendor) | YES | NO | N/A | YES | Available now |
| Read chart of accounts | PARTIAL -- Accounting API (Alpha) returns accounting records, not a managed chart-of-accounts entity. CoA is pulled from the connected ERP, not stored independently in Brex. | NO | partial | NO | N/A | YES (via integration) | Read via ERP sync |
| Write chart of accounts | NO -- there is no POST /accounts equivalent. Brex's model is to sync CoA FROM the customer's ERP, not own a master list. |
NO | NO | NO | N/A | NO | Not supported |
| Read/write cost centers, departments, projects, custom dimensions | YES via Fields API (GET/POST/PUT/DELETE /v1/fields, batch create up to 1,000 field values) |
YES (Create Department, Create Location) | YES | NO | N/A | YES | Available now (Fields API, Beta) |
| Read/write tax codes | NO dedicated tax-code API. Tax handling is via custom fields and ERP-side mapping. No direct VAT-code CRUD. | NO | NO | NO | N/A | partial | Not supported (gap vs Pleo/Ramp) |
| Read employees / users | YES (Team API) | YES (Find User) | YES | NO | N/A | YES | Available now |
| Write users / departments / locations | YES (Team API) | YES (Create User, Create Department, Create Location, Update User, Set User Limit) | YES | NO | N/A | YES | Available now |
| Card management (issue/suspend/terminate virtual + physical) | YES (Team API + POST /v1/cards/...) |
YES (Create Card, Email Card Details, Set Spending Limit) | YES | NO | N/A | NO | Available now |
| Push bills/invoices into Brex | NOT directly via API -- Brex has Bill Pay (BillPay product), but bill upload via API is not a documented endpoint. Bills enter via email forwarding, dashboard upload, or ERP sync. | NO | NO | NO | N/A | NO | Not via API |
| Mark records as exported / synced | YES (POST /v3/accounting/records/export-results) |
NO | YES | NO | N/A | N/A | Available now (Accounting API, Alpha) |
| Trigger/manage approvals | PARTIAL -- approvals configured in dashboard; approve/reject endpoints not publicly surfaced. | NO | partial | NO | N/A | N/A | Limited |
| Budgets read/write | YES (Budgets API: create, update, get) | YES (Create/Update Budget, Get Budget) | YES | NO | N/A | NO | Available now |
| Travel data (trips) | YES (Travel API, read-only) | NO | partial | NO | N/A | N/A | Read only |
| DATEV bidirectional sync | NO | N/A | N/A | N/A | NOT SUPPORTED | N/A | NOT available |
Overall assessment: Brex has a strong, modern REST API with good event coverage, full CRUD on vendors/users/fields/budgets, and a free-tier Developer API. However, three notable gaps stand out vs Ramp and Pleo:
transaction.created real-time webhook. The Transactions API returns settled transactions only; the EXPENSE_PAYMENT_UPDATED webhook fires only once a payment posts. This is worse than Ramp's transactions.authorized event.Plus the receipt download endpoint is not clearly documented, which is a question mark for receipt-fetching workflows (the Pleo concern about 24-hour URL expiry has no Brex public answer).
| API | Base URL | Purpose |
|---|---|---|
| Production REST API | https://platform.brexapis.com/ (canonical), historical references to api.brex.com |
Main REST API across all product surfaces |
| Staging Environment | Separate staging URL (Pipedream lists "Brex (Staging)" as a separate app) | Test environment -- not a sandbox; does not work with customer tokens |
| Developer Portal | https://developer.brex.com/ |
Documentation hub, OpenAPI spec, changelog |
| OpenAPI Spec | https://developer.brex.com/_bundle/openapi/<api>.yaml (per-API bundles) |
Machine-readable spec per API surface |
| MCP Server (Beta) | Released April 2026 | First-class MCP integration for Claude, ChatGPT, Cursor |
| Postman Collection | Public collection at postman.com/brex-api/brex-developer/ |
Pre-built request library |
| API | Status | Scope |
|---|---|---|
| Transactions API | GA | Card + cash transactions (settled), accounts, statements |
| Expenses API | GA | View, update card expenses; receipt match + receipt upload |
| Team API | GA | Users, locations, departments, cards |
| Payments API | GA | Vendors (full CRUD), ACH, domestic wires, checks |
| Budgets API | GA | Budgets + budget programs |
| Onboarding API | GA | Referrals, prefilled signup |
| Travel API | GA | Read trips made in Brex Travel |
| Webhooks API | GA | Event subscriptions (8 event types) |
| Fields API | Beta | Custom accounting fields + options (cost centers, projects, custom dimensions) |
| Accounting API | Alpha | Accounting records, export-result tracking, ERP integration management |
| Method | Details |
|---|---|
| OAuth 2.0 | Primary mechanism for partner / third-party apps |
| User Tokens (API Keys) | Generated by account or card admins from the Brex dashboard. Bearer-token auth (Authorization: Bearer <token>). All admins receive email notification when a token is created or revoked. |
| Scopes | Per-resource, read/write split. Documented scopes include transactions.card.readonly, transactions.cash.readonly, expenses.card.readonly, plus equivalents for team, vendors, budgets, accounting |
| Token issuance | Dashboard-based for User Tokens; OAuth 2.0 authorization-code flow for partner apps |
| MCP Server | Authentication via Brex token for the user account, exposed via MCP protocol |
Retry-After header includedACCOUNTING_RECORD_READY_FOR_EXPORT (Alpha, Nov 2025)EXPENSE_PAYMENT_UPDATED -- requires expenses.card.readonly + CARD_ADMIN roleREFERRAL_ACTIVATEDREFERRAL_APPLICATION_STATUS_CHANGEDREFERRAL_CREATEDTRANSFER_PROCESSEDTRANSFER_FAILEDUSER_UPDATEDNotable absence: no TRANSACTION_CREATED, EXPENSE_CREATED, or CARD_AUTHORIZED event. This is a meaningful gap for real-time spend analytics use cases vs Ramp.
/v1/webhooks/secrets semantics)Webhook-Signature header; apps should validate against all currently-active keysConfidence: HIGH for vendors, users/team, custom fields, budgets, cards. MEDIUM-LOW for CoA / tax codes (not supported as primary objects).
| Endpoint | Method | Operation | Confidence |
|---|---|---|---|
| Create vendor | POST /v1/vendors |
New vendor record (incl. company_name) |
HIGH (documented + Zapier) |
| Update vendor | PUT /v1/vendors/{id} |
Modify vendor | HIGH (documented + Zapier) |
| Delete vendor | DELETE /v1/vendors/{id} |
Remove vendor | HIGH (documented) |
| Create user | Team API | Add team member | HIGH (Zapier confirms) |
| Update user | Team API | Modify user, including spending limits | HIGH (Zapier confirms "Set User Limit") |
| Create department | Team API | New department | HIGH (Zapier confirms) |
| Create location | Team API | New location | HIGH (Zapier confirms) |
| Create card | Team API | Issue virtual or physical card | HIGH (Zapier confirms) |
| Suspend / terminate card | Team API | Lifecycle ops | HIGH (documented) |
| Create custom field | POST /v1/fields |
New field definition | HIGH (Fields API, Beta) |
| Create custom field values | POST /v1/fields/.../values (batch up to 1,000) |
New options for a field | HIGH (Fields API, Beta) |
| Update / delete field | PUT/DELETE /v1/fields/{id} |
Modify field | HIGH (Fields API, Beta) |
| Update expense (coding) | PUT /v1/expenses/card/{expense_id} |
Apply category, memo, field values | HIGH (documented) |
| Create receipt upload | POST /v1/expenses/card/{expense_id}/receipt_upload |
Returns pre-signed S3 URL (30-min PUT window) | HIGH (documented) |
| Create receipt match | POST /v1/expenses/card/receipt_match |
Smart-match receipts to transactions | HIGH (documented) |
| Create budget | Budgets API | New budget | HIGH (Zapier confirms) |
| Update budget | Budgets API | Modify budget | HIGH (Zapier confirms) |
| Create transfer | Payments API | ACH / wire / check | HIGH (documented) |
| Create accounting integration | POST /v3/accounting/integration |
Hook up an ERP | HIGH (documented) |
| Mark records as exported | POST /v3/accounting/records/export-results |
Close the loop after external export | HIGH (documented, Alpha) |
| Create webhook subscription | Webhooks API | Subscribe to events | HIGH (documented) |
| Object | Write Support | Notes |
|---|---|---|
| Chart of accounts | NO API | Brex syncs CoA from ERP via integration; no direct CRUD endpoint |
| Tax codes / VAT rates | NO dedicated API | Custom fields can model this but no first-class tax-code object |
| Bills / invoices | NO API | Bills enter via email or dashboard; no POST /bills endpoint |
| Approval rules / policies | NO API | Configured in dashboard; not surfaced as a write endpoint |
| Bank account info on vendor | UNDOCUMENTED | POST /v1/vendors accepts company_name; full bank-detail support not in public docs |
| Platform | Brex Connector? | Details |
|---|---|---|
| Zapier | YES -- official, well-developed | 3 instant triggers (Pending Card Transactions, Transfer Processed, Transfer Failed) + 15+ actions (create cards, vendors, users, departments, locations, budgets, transfers; set spending limits; email card details) + 10+ search actions (find users, cards, vendors, departments, locations; search cash + card transactions; get budgets; retrieve card numbers by ID). Most comprehensive iPaaS coverage of any spend-mgmt tool examined. |
| Workato | YES -- listed on Brex integrations page | Native connector; specific recipe inventory not enumerated publicly |
| Make | NO native | HTTP module + custom OAuth setup required |
| n8n | NO native, generic HTTP only | n8n docs explicitly direct users to "Add the HTTP Request node ... and authenticate it using a generic authentication method" -- no first-party node |
| Celigo | NO | Not in marketplace |
| Pipedream | YES (incl. separate Staging app) | Pre-built actions for limit-setting, account listing, transaction search |
| Windmill | YES (community) | Hub scripts for receipt upload, vendor creation |
| Brex MCP Server | YES -- first-party, April 2026 | Direct natural-language access for Claude, ChatGPT, Cursor; Brex is one of the first spend-mgmt tools to ship MCP |
Conclusion: Brex's iPaaS coverage is strong via Zapier + Workato + Pipedream + MCP. The MCP server is a forward-looking differentiator: if Orcha (which is itself heavily Claude-integrated) wants to expose Brex data through an agent layer, a wrapper around Brex MCP is the fastest path.
| System | Connection Type | Direction | Plan Required |
|---|---|---|---|
| Microsoft Dynamics 365 Business Central | API | Bidirectional | All paid |
| Oracle NetSuite | API | Bidirectional | All paid |
| Oracle Fusion Cloud | API (add-on) | Bidirectional | Enterprise (custom) |
| QuickBooks Online | API | Export | All |
| QuickBooks Desktop | Manual export | Export | All |
| Sage Intacct | API | Bidirectional | All paid |
| Xero | API | Bidirectional | All |
| Workday Financials | API (add-on) | Bidirectional | Enterprise |
| SAP Concur | API | Bidirectional | All |
| Campfire | API | Bidirectional | All |
| Digits | API | Read | All |
| Everest | API | -- | All |
| Expensify | API | -- | All |
| Hanover Park | API | -- | All |
| Puzzle | API | -- | All |
| Rillet | API | -- | All |
| DATEV | NONE | -- | -- |
| SAP S/4HANA | NONE (Concur is the SAP path) | -- | -- |
ADP Workforce Now, BambooHR, Deel, Gusto, Justworks, Paychex, Paylocity, Rippling, TriNet, UKG, Zenefits
Coupa, GEP, Zip
Navan (deep partnership: "BrexPay for Navan"), Conferma, Lyft Business, Sabre, Uber for Business
Fintua, VAT IT
ChatGPT, Claude, Microsoft Teams, Slack, Pipedream, Workato, Zapier, Zoom, WhatsApp
transaction.created. Closest is EXPENSE_PAYMENT_UPDATED, which fires only on settled+posted state.Webhook-Signature header| Plan | Monthly | API Access | Notes |
|---|---|---|---|
| Essentials | $0 / user / month (free, interchange-funded) | YES -- Brex API access included | Capped at 2 entities (1 global), no advanced ERP integrations beyond QuickBooks/Xero, no customizable expense policies, no local card issuance, no VAT documentation |
| Premium | $12 / user / month | YES -- full API access | Multi-entity, customizable ERP + HRIS integrations, advanced approvals, live budgets |
| Smart Card | Custom | YES | Local-currency cards in 50+ countries, procurement-focused |
| Enterprise | Custom | YES + named account manager | Unlimited entities, local card issuance, collections, reimbursements in 50+ countries |
API access is a FREE feature, available on all plans -- including Essentials ($0/user). This puts Brex in the same camp as Ramp (both interchange-funded, both free Developer API) and ahead of Pleo (Advanced tier required, ~$99/user/month).
transactions.card.readonly, expenses.card.readonly, etc.)EXPENSE_PAYMENT_UPDATED, ACCOUNTING_RECORD_READY_FOR_EXPORT)| Capability | Brex | Orcha |
|---|---|---|
| Invoice capture (OCR) | YES (Bill Pay, email forwarding) | YES (core product) |
| Invoice data extraction | YES | YES (core product) |
| Pre-accounting (account coding) | YES (AI-powered) | YES (core product) |
| Cost center assignment | YES (Fields API, custom fields) | YES |
| Approval workflows | YES (Premium+) | Depends on customer |
| Payment processing | YES (ACH, wires, checks; EU SEPA on new EU license) | NO |
| Corporate cards | YES (physical + virtual) | NO |
| Employee reimbursements | YES (incl. SCA-secured for EU) | NO |
| Push to ERP | YES (native connectors to 15+ systems, but no DATEV) | YES (via integration) |
| MCP / agent surface | YES (April 2026) | YES (Orcha is Claude-native) |
Scenario A: Orcha pushes reference data INTO Brex
Scenario B: Orcha reads card transaction data FROM Brex
EXPENSE_PAYMENT_UPDATED for change notificationstransaction.created event -- settlement delay (1-3 business days typical for card networks) means Orcha's unified spend view is always 1-3 days behind on card data, vs near-real-time for AP invoicesScenario C: Orcha replaces Brex's invoice/bill features
Scenario D: Orcha pushes invoices into Brex
POST /bills API. Invoices enter via email forwarding or dashboard upload.POST /bills endpoint.Based on the public OpenAPI surface (the full schema is in transactions_api.yaml not fully extracted via WebFetch, but the documented endpoint + Truto integration guide + Zapier action descriptions confirm):
| Field | Available? | Notes |
|---|---|---|
| Amount | YES | Numeric + currency |
| Currency | YES | ISO 4217 |
| FX rate / original currency | LIKELY (multi-currency platform) | Not explicitly confirmed in public docs |
| Merchant name | YES | Counterparty name |
| Merchant MCC | YES | Brex categorizes by merchant categories (brex-merchant-categories doc) |
| Raw descriptor | LIKELY | Standard for card networks |
| Category (Brex internal) | YES | Auto-applied by Brex AI |
| GL account mapping | VIA ERP sync | Not stored as native Brex field; flows via Accounting integration |
| Cost center | YES (via Fields API custom field) | Customer-defined |
| Tax code | NOT FIRST-CLASS | Only as custom field |
| Employee (cardholder) | YES | Via Team API user reference |
| Card last-4 | YES | Standard card object |
| Virtual vs physical | YES | Card type |
| Approval status + approver | PARTIAL | Approvals modeled at expense level; approver chain visible but not freely manipulable via API |
| Receipt download | UNCLEAR | Receipt upload is documented (S3 pre-signed PUT, 30-min); receipt-fetch endpoint not surfaced publicly. May require dashboard access or undocumented endpoint. |
| Expense type | YES (Expenses API) | |
| Memo / notes | YES | Editable via PUT /v1/expenses/card/{expense_id} |
| Receipt attached (boolean) | YES | Expense object exposes receipt match state |
Critical unknown: receipt download URL longevity. Pleo's 24-hour URL expiry is a known headache; Brex's public docs are silent on whether receipts are fetchable via API at all post-upload. This needs verification with Brex developer support before any production design. (Open question.)
| Dimension | Brex | Pleo | Ramp |
|---|---|---|---|
| German-HQ customer can sign up today? | NOT GENERALLY (phased EU rollout) | YES (operational since years) | NO (summer 2026 waitlist) |
| EU PI license? | YES (Aug 2025, Netherlands) | YES (DK) | Pending (Billhop acquisition, UK + SE) |
| DATEV integration? | NO | YES (1-click) | NO |
| ZUGFeRD / XRechnung? | NO | Partial (e-invoice support) | NO |
| Real-time transaction webhook? | NO (transaction.created missing) |
YES (export-job webhook), settlement-delayed too | YES (transactions.authorized) |
| Receipt URL longevity? | UNCLEAR (no public doc) | 24-hour expiry (known issue) | Documented in Receipts API |
| API on free tier? | YES ($0 Essentials) | NO (Advanced $99/user/mo) | YES (free Developer API) |
| Full CRUD on vendors? | YES | YES | YES |
| Full CRUD on CoA? | NO (sync-from-ERP only) | YES | YES |
| Full CRUD on tax codes? | NO (custom fields only) | YES (Tax Codes API) | YES (Tax Code + Tax Rate API) |
| Push bills via API? | NO | NO | YES |
| MCP / agent integration? | YES (April 2026, official) | NO | YES (3 MCP servers) |
Brex sits between Pleo (mature EU presence, less API depth) and Ramp (deeper API, later EU arrival). For a German customer using DATEV today, Pleo is the only operationally viable choice. Brex and Ramp are both "watch this space" rather than "act now".
| Orcha Need | Brex Support | Endpoint(s) | Confidence | Notes |
|---|---|---|---|---|
| Sync chart of accounts INTO Brex | NOT SUPPORTED | N/A | HIGH | Brex syncs CoA from ERP, not reverse |
| Sync cost centers / departments INTO Brex | FULL (read + write) | Fields API, Team API | HIGH | Beta status on Fields API |
| Sync tax codes INTO Brex | NOT SUPPORTED (first-class) | Custom fields workaround | MEDIUM | Workaround fragile for German VAT |
| Sync vendors INTO Brex | FULL (read + write) | Payments API | HIGH | Full CRUD |
| Push incoming invoices | NO | N/A | HIGH | Email-only |
| Attach documents to invoices | PARTIAL | Receipt upload endpoints (S3 pre-signed PUT) | HIGH | Bills/invoices NOT covered by receipt API; only card expenses |
| Manage approvals | LIMITED | N/A | HIGH | Dashboard-configured only |
| Read card transactions | YES (settled) | Transactions API, Expenses API | HIGH | Settlement-delayed |
| Real-time card transactions | NO | N/A | HIGH | No transaction.created event |
| Track status changes | YES (limited events) | Webhooks API (8 events) | HIGH | EXPENSE_PAYMENT_UPDATED, ACCOUNTING_RECORD_READY_FOR_EXPORT |
| Read employees | YES | Team API | HIGH | Full search + retrieve |
| Write employees | YES | Team API | HIGH | Full CRUD |
| Receipt download | UNCLEAR | N/A (undocumented) | LOW | Open question for Brex support |
For the specific customer profile in the brief -- German company, DATEV for accounting, Orcha for AP invoices, evaluating Pleo alternatives for employee credit cards -- Brex fails on three criteria simultaneously:
Recommendation: do not advance Brex in this customer's evaluation. Pleo remains the best fit for the German + DATEV + Orcha customer profile. Brex's strengths (free-tier API, MCP server, mature Zapier connector, full vendor + user CRUD, EU PI license) are real, but they are oriented toward US-anchored multinationals (Ooni, Navan partners), not toward DATEV-bound German SMBs.
| Approach | Cost | Complexity | Value | Verdict |
|---|---|---|---|---|
| Read card transactions via Transactions + Expenses APIs | $0 (free API) | Medium | Medium for non-DATEV customers | For US/global customers only |
| Sync vendors via Payments API | $0 | Low | Medium | Useful when both systems coexist |
| Sync cost centers via Fields API | $0 | Medium (Beta) | Medium | Useful when both systems coexist |
| Wrap Brex MCP server in Orcha agent layer | $0 + dev time | High | High (future) | Worth tracking; not now |
| Build DATEV-Brex bridge | $$$ | High | LOW for now | Don't build until Brex ships native DATEV |
| No Brex integration | $0 | None | Customer-specific | Recommended for this German DATEV customer |
For the customer in scope: do not pursue Brex. Stick with Pleo as the recommended cards provider, and continue using Orcha for AP + DATEV for accounting.
For Orcha as a product: add Brex to the "monitor" list. Re-evaluate in 12 months when (a) Brex's EU rollout has reached general availability for German-HQ customers, (b) a DATEV connector ships or third-party connector emerges, and (c) the receipt download API behaviour is publicly documented. Brex's API is well-built and its MCP-first stance aligns with Orcha's direction -- the gating issues are go-to-market and German-locale specifics, both of which are likely to improve in 2026-2027.