How Brex works

Requirement evaluated: Per-vendor duplicate sensitivity configuration for vendors that legitimately reuse invoice numbers (e.g., recurring rent or utility billing)

For a $120M services company routing 1,800 invoices per month through Brex Bill Pay, including a significant recurring non-PO population (utilities, subscriptions, rent), the platform does flag potential duplicate bills during the pre-processing stage before payment. Brex's detection system analyzes multiple data points simultaneously, examining invoice amounts, dates, vendor information, and line-item details to identify potential duplicates, and automatically flags suspected duplicates for review. The Bills queue includes a dedicated "Duplicate bills" filter so AP staff can isolate and action those flags in batch. …

Limitations: For this buyer's recurring non-PO invoice population (rent, utilities, subscriptions), vendors that legitimately reuse invoice numbers on a fixed cycle will generate false-positive duplicate flags on every billing cycle with no documented mechanism to suppress or tune detection for those specific vendors. …

Requirement evaluated: Clear exception categories: price variance, quantity variance, missing PO, missing receipt, duplicate, vendor mismatch

For a $120M multi-location services company processing 1,800 invoices per month with 55% PO-based spend across two Sage Intacct entities, Brex Bill Pay addresses several but not all of the six required exception categories. On the pre-processing journey, Brex operates at stages 1 (legitimacy), 2 (PO match), and partially at stage 5 (GL coding). For PO-based invoices, Brex AI matches an imported invoice to an open PO pulled from a connected ERP via its two-way accounting integration, surfacing quantity variances and unit-price drift at the line level without an AP analyst rekeying line tables; if no match is found, Brex flags the invoice rather than passing it through. …

Limitations: Brex's matching is two-way (invoice-to-PO), so the 'missing receipt' exception category, which requires a formal goods-receipt or service-completion confirmation against the invoice before payment, is not natively enforced; this is a material gap for the buyer's 55% PO-based invoice volume involving facilities, supplie …

Requirement evaluated: Two-way matching for service POs where no goods receipt applies

For a multi-location services company with 55% PO-based invoices covering facilities, supplies, and subcontractors processed across two Sage Intacct entities, Brex Bill Pay delivers the exact matching workflow the buyer needs. Brex's documented PO matching feature, explicitly labeled 'Matching bills to purchase orders (2-way match)' in its help center, pulls open POs from connected ERPs including Sage Intacct and automatically matches incoming invoices against them by vendor, PO number, and amount, with no goods receipt required to initiate or complete the match. …

Limitations: Brex's matching architecture is 2-way only; there is no 3-way match capability, which is appropriate for this buyer's service POs but means the platform cannot enforce receipt-based verification for any goods-based PO lines (the buyer's facilities and supplies spend) if that control is ever required. …

Requirement evaluated: Automated three-way matching: invoice to PO to goods receipt, with configurable tolerance (2% price, 5% quantity)

For your 1,800-invoice-per-month operation on Sage Intacct, Brex Bill Pay handles the invoice-to-PO leg of matching: its AI scans uploaded invoices and automatically identifies a corresponding open PO from your connected ERP, surfacing the PO number, date, and remaining available amount for AP review. As Brex's own bill pay documentation states, "Brex AI will also match your imported invoice to an open PO in your ERP via our two-way accounting integrations, helping to simplify the procure-to-pay process and further automate accounting." This covers pre-processing stage 2 (PO match), but the matching architecture is consistently described as two-way across Brex's product documentation and sup …

Limitations: For your facilities, supplies, and subcontractor invoices (your PO-based 55%), the absence of goods receipt integration means Brex cannot confirm delivery before releasing a match for payment, which is the core control three-way matching provides; the buyer's tolerance configuration requirement (2% price, 5% quantity a …

Requirement evaluated: 1099 preparation: automated classification, threshold tracking, and electronic filing

For your 3-person AP team processing subcontractors, professional services, and other 1099-reportable spend across two Sage Intacct entities, Brex handles the vendor-side data capture and classification steps but stops short of electronic filing. On the classification side, each vendor record in the Brex dashboard includes a 1099-eligibility toggle; admins can filter the vendor table to view all 1099-eligible vendors and apply filters by eligibility status, business type, W-9 receipt, and tax information status. …

Limitations: Electronic filing is not a native Brex capability: Brex exports 1099 data for use by a third-party filing service, so your team will need to manage a separate filing workflow outside Brex. …

Requirement evaluated: Vendor communication log: track every inquiry and response to eliminate the 6 hours/week our team spends on status calls

Your AP team fields roughly 6 hours of vendor status calls per week, and eliminating that load requires either a supplier self-service portal (vendors check invoice receipt, approval stage, and payment date on their own) or a structured, per-invoice communication thread that timestamps every AP-vendor exchange. Brex's Bill Pay module does send a single outbound email to a vendor's address when payment is initiated — the AP team can store a default vendor email on the bill record and toggle that notification on or off — but that covers only the final payment trigger, not the upstream stages (invoice received, approved, scheduled) where most status calls originate. …

Limitations: For a 3-person AP team processing 1,800 invoices per month across facilities, subcontractors, utilities, and professional services vendors, the absence of any structured vendor communication channel means status inquiries will continue to arrive by phone and email at roughly the current rate; Brex's single payment-conf …

Requirement evaluated: Multi-factor verification for banking change requests; we need systematic fraud prevention, not email-based trust

For a $120M multi-location services company replacing email-based banking-change trust with systematic fraud prevention, Brex provides several overlapping controls but not a dedicated MFA challenge or dual-approval gate specifically triggered when an existing vendor's banking details are edited. At the account level, Brex mandates 2FA for every user login, supporting authenticator apps or SMS, and this requirement cannot be disabled once set. …

Limitations: The buyer's specific requirement is systematic fraud prevention at the moment of a banking-detail change on an existing vendor record; Brex's documented controls address that risk only partially through login-level 2FA, role-restricted access, and a vendor self-service portal for initial setup, but none of these mechan …

Requirement evaluated: Vendor performance visibility: on-time payment rate, average payment cycle, dispute frequency

Your AP team of three needs to look across 1,800 monthly invoices and ask: are we paying Vendor X on time, how long does our cycle typically run for subcontractors, and which vendors generate the most disputes? Brex's bill pay module tracks the status of each individual bill in real time (scheduled, processing, processed, denied, canceled) and syncs completed payment records to your Sage Intacct entities via a one-directional push. However, across four targeted searches of Brex's help center, no native analytics layer surfacing on-time payment rate, average payment cycle duration, or dispute frequency aggregated at the vendor level was found. …

Limitations: Vendor-level performance analytics (on-time payment rate, average days to pay, dispute frequency trends over time) are not available as a native Brex dashboard. A buyer willing to pay cannot purchase this capability from Brex at any tier; the mechanism does not exist in the product, and any such analytics would require …

Requirement evaluated: Touchless processing target: 40%+ of PO invoices should require zero manual intervention from capture through posting

For your 3-person AP team processing 1,800 invoices per month in Sage Intacct, Brex Bill Pay delivers meaningful capture and coding automation but stops short of a fully zero-touch pipeline for PO invoices. On the capture side, invoices forwarded by email or uploaded directly are scanned by Brex's LLMs at the line-item level, auto-populating all required fields with a documented accuracy rate above 90%, and the Policy Engine can auto-approve bills that satisfy configured rules without requiring a human click, triggering automatic payment on the scheduled date. …

Limitations: PO import for matching is not documented for Sage Intacct (only NetSuite and QuickBooks Online are supported), so the buyer cannot leverage Brex's AI auto-match on their existing PO dataset, and Brex offers only 2-way matching with no receipt-confirmation mechanism, meaning goods-based PO invoices (facilities, supplies …

Requirement evaluated: Learning capability: accuracy should improve over time on our specific vendor invoice formats

For a multi-location services company processing 1,800 invoices per month across mixed vendor formats, Brex's Bill Pay platform ingests invoices via email forwarding, direct upload, or vendor submission, then applies OCR and LLM-based extraction to pre-fill payment draft fields including vendor details, amounts, due dates, and line items. When the AI misreads a field, the AP team corrects it manually through the bill review interface, and Brex's product documentation states that 'the platform learns from these corrections to improve future accuracy' (brex.com/spend-trends/cash-flow-management/ocr-invoice-processing). …

Limitations: The documented learning mechanism appears to operate at the account or model level broadly rather than building vendor-specific extraction profiles; for a buyer whose 55% PO-based spend involves recurring subcontractor and facilities vendors with distinct invoice formats, there is no documented evidence that high-volum …

Requirement evaluated: Confidence scoring on extracted data so AP clerks know which fields to verify vs. which are high-confidence

For your 3-person AP team processing 1,800 invoices per month, Brex Bill Pay uses an LLM-powered extraction engine to auto-populate invoice fields (vendor name, date, amount, line items, PO reference, payment terms) as a draft the moment an invoice is uploaded or forwarded by email. The Brex support documentation describes the review step this way: 'When you upload an invoice, we'll use AI to pre-fill the text from the invoice to the fields. If AI reads these fields incorrectly, you can manually adjust them.' The system does flag certain document-level exceptions for human review: invoices with poor image quality, PO matching failures, and structural anomalies surface for clerk attention. …

Limitations: Brex's exception model is document-level and mismatch-triggered: a bill gets flagged when it cannot be matched to a PO or when image quality is poor, but fields that were extracted incorrectly with apparent confidence produce no distinct signal to the clerk. …

Requirement evaluated: AI/OCR-powered extraction from PDF, image, and email-embedded invoices with 95%+ accuracy on header and line-item data

For a 3-person AP team processing 1,800 invoices per month across PDFs, scanned mail, and email-borne invoices, Brex Bill Pay offers multi-channel invoice ingestion: drag-and-drop dashboard upload, bulk upload, and a dedicated email forwarding address (bills@brex.com or a unique per-account address) where vendors can send invoices directly. The team can forward emailed invoices to a Brex-assigned address, and invoices accepted as attached PDF, PNG, JPG, or email body text are processed automatically. …

Limitations: Brex's own product content discloses 90%+ accuracy as the planning figure, and independent third-party testing found 87% on header fields for non-standard invoice layouts; the buyer's 95% threshold is not reliably met for the full invoice mix (mail-scanned, unusual vendor formats, or complex multi-page utility and subc …

Requirement evaluated: SOC 2 Type II certification (current, not in-progress)

For a $120M services company evaluating Brex as an AP automation platform, the SOC 2 Type II requirement is met through Brex's formal, independently audited compliance program. Brex's dedicated security page (brex.com/trust) states the company is SOC 1 Type II, SOC 2 Type II, and PCI-DSS certified, and confirms it is 'audited by major external auditing firms and regulators.' The Data Processing Addendum (brex.com/legal/dpa) further specifies that Brex is 'regularly audited against SSAE 18 SOC 2 standards by independent third party auditors,' confirming the ongoing audit cadence that distinguishes Type II from a point-in-time Type I. …

Limitations: The SOC 2 Type II report is available on request via the Trust Portal rather than as a direct public download, so your procurement team will need to submit a request and may be asked to acknowledge an NDA before receiving the full report. …

Requirement evaluated: AI-powered anomaly detection for unusual invoice patterns (spike in amount, new bank account, unusual vendor behavior)

For a $120M multi-location services company processing 1,800 invoices per month across two Sage Intacct entities, Brex's AI layer (Brex AI) operates at the pre-payment stage and covers two of the three anomaly scenarios the buyer requires. On duplicate detection and amount anomalies: Brex's own content states that bill pay 'checks for duplicates or anomalies before payments go out,' and a third-party reviewer testing Brex AI confirmed it flagged a duplicate charge from a vendor and a subscription renewal with a price increase among real transactions. …

Limitations: Bank account change detection with a mandatory re-verification hold before payment release is described only in Brex marketing content as a general AP automation capability, not as a specifically documented mechanism in Brex's bill pay help center; this is the buyer's highest-risk control gap. …

Requirement evaluated: SSO integration with Microsoft Azure AD

For a 200-employee services company standardized on Microsoft Azure AD (Entra ID), Brex provides a documented SAML 2.0 federation path where Azure AD acts as the identity provider and Brex acts as the service provider. An account admin navigates to Security > Authentication > Setup Single Sign-On in the Brex dashboard, selects SAML as the integration type, and supplies the Azure AD Single Sign-On URL, Issuer URL, and X.509 signing certificate; Brex returns an Assertion Consumer Service (ACS) URL and Entity ID to configure on the Azure side. …

Limitations: Brex's own documentation explicitly states that OIDC is not supported with Microsoft Entra ID; SAML is the required protocol, so your Azure AD team must configure a SAML enterprise application rather than an OIDC app registration. Advanced SSO functionality is available on Brex's Premium tier ($12/user/month) …

Requirement evaluated: Role-based access control with entity-level restrictions

For a two-entity services company running Sage Intacct, Brex offers entity-aware organizational structure but not entity-scoped AP transaction visibility. Users can be assigned to a specific legal entity at the profile level during invitation, and Brex lets you manage spend across multiple subsidiaries from a single dashboard, with entities configured separately for Bill Pay by navigating to Team > Entities, where each entity requires its own default payment account. …

Limitations: For this buyer's two-entity Sage Intacct setup, Brex's bill pay permissions are account-wide: a user granted AP clerk or Bookkeeper access will see and be able to action invoices across both entities, with no documented entity-scoped visibility restriction in the Bills tab. …

Requirement evaluated: Spend analytics: top vendors, spend by GL category, month-over-month trending

For a 3-person AP team processing 1,800 invoices per month across 2 Sage Intacct entities, Brex provides a unified spend dashboard that claims to aggregate corporate card spending, employee reimbursements, and bill payments in a single view with real-time data. Brex's reporting page describes the ability to "track all spend in one place" and to see how spend is tracking across cards, reimbursements, and bill payments — all in one dashboard. Within the Bills module itself, the Bills view supports filtering by vendor and GL account, and an admin can download the bill view by clicking Download and choosing a file format, with the export including the columns shown in the current filtered view. …

Limitations: The buyer's core ask — a pre-built analytics view showing top AP vendors by invoice spend, spend by Sage Intacct GL category, and month-over-month trending across both Sage Intacct entities — is not fully evidenced in Brex's help documentation; the documented pre-built top-vendor and trend chart features are explicitly …

Requirement evaluated: Real-time AP dashboard: invoice aging, approval queue depth, processing cycle time, spend by vendor/category/entity

For a $120M, 2-entity Sage Intacct company processing 1,800 invoices monthly, Brex's Bills module provides a real-time bill management queue where AP staff can filter open bills by vendor, due date, billed entity, GL account, payment date, and approval status — the 'For approval' and 'Tasks' views show which bills are pending and who holds the next approval step. …

Limitations: Brex's help center does not document a formal AP aging report with time-bucket groupings or a cycle-time metric widget for bill pay, which are two of the four sub-components the buyer explicitly requires; those metrics appear in marketing blog content but not in product documentation as verified features. …

Requirement evaluated: Spend analytics: top vendors, spend by GL category, month-over-month trending

For a $120M multi-location services company running 1,800 invoices/month through Sage Intacct, Brex surfaces spend data through a 'Reports > Spend' section in its dashboard. The platform tracks spend across cards, reimbursements, and bill payments in one dashboard, without switching between platforms or manually compiling data from multiple sources. Admins can run spend reports compiled from card expense and reimbursement details, narrowed by spend over time, spend limits, categories, users, merchants, or departments. The built-in reporting tools also support vendor spending concentration analysis and opportunities for consolidation. …

Limitations: Brex's spend analytics are demonstrably stronger for corporate card transactions than for AP bill pay invoices, which make up effectively 100% of this buyer's 1,800-invoice monthly volume. …

Requirement evaluated: Export to Excel and scheduled report delivery to Controller and CFO

For a $120M services company needing to keep the Controller and CFO informed on a recurring basis, Brex covers the export side of this requirement clearly: admins can download spend reports, transaction tables, and accounting journal entries as XLSX, CSV, PDF, HTML, or TXT files directly from the Brex dashboard. The spend reports module lets users configure widget-based views filtered by department, budget, merchant, or user, save snapshots under 'Reports > Your reports,' and export those snapshots on demand by clicking Download. The accounting journal export follows the same pattern: admins select transactions, choose format, and download. …

Limitations: The scheduled push-to-email half of this requirement, delivering a report to the Controller and CFO on a defined cadence without requiring a dashboard login, has no documented native mechanism in Brex; the buyer would need to manually export and forward files, or configure a Workato or Zapier workflow, to replicate sch …

Public documentation covers the area and does not answer this requirement either way.

Requirement evaluated: Integration setup assistance included in implementation; not a separate SOW or additional cost

For your 2-entity Sage Intacct environment, Brex documents a self-serve connection. Your admin creates a Brex role and a Web Services user in Intacct, completes the connection, then maps GL accounts once per entity (Brex Sage Intacct integration help article). Bill Pay then syncs one way from Brex to Intacct: vendors and bills sync once a bill is fully approved, and a vendor is created in Intacct if no name match is found (Brex 'Syncing your bills' article). The fact sheet also says Brex automates GL coding by entity and maps bill pay transactions to ERP fields and GL codes. This work sits in the invoice-coding and payment-sync stages, not in receipt confirmation. …

Limitations: Brex's day-one onboarding connection covers QuickBooks Online, Xero and Puzzle, not Sage Intacct, so your Intacct setup falls to the documented admin steps. Top-level posting also requires contacting Support. …

Requirement evaluated: Support for Sage Intacct dimensions: Location, Department, Class, Project, Customer, and custom dimensions

For a two-entity Sage Intacct environment processing 1,800 invoices per month, Brex connects via a direct API integration that imports Sage Intacct accounting data into the Brex platform, where it becomes available as selectable fields during invoice coding and bill submission. Brex's Sage Intacct integration product page explicitly enumerates the following synced dimension objects: Department, Vendors, Customers, Projects, Employee, Class, Credit Card Accounts, and User Defined Dimensions. …

Limitations: The Sage Intacct integration setup prompts the user to 'select the entity you want to connect to Brex,' which may require separate integration configuration steps for each of the buyer's two Intacct entities; this should be confirmed during implementation scoping to ensure each entity's distinct dimension lists (e.g., …

Requirement evaluated: Multi-entity support within the integration; we operate 2 entities in Intacct and plan to add a third

For a two-entity Intacct organization planning to add a third, Brex manages multi-entity integration through a single unified dashboard rather than requiring separate vendor subscriptions per entity. During setup, the buyer creates one Intacct Web Services User credentialed at the top level and grants it access to whichever entities need to connect with Brex; the integration then pulls each entity's chart of accounts, vendors, and GL fields into Brex. Under 'User entities,' the admin assigns the Intacct entities to be accessed and allows top-level access. Once connected, Brex's direct integration enables tracking and export to multiple entities within a single Sage Intacct account. …

Limitations: The bill pay sync from Brex to Sage Intacct is one-directional: the Sage Intacct integration with bill pay is a one-directional sync from Brex to Sage Intacct, where bills created in Brex sync over to Sage Intacct, so edits made directly in Intacct do not flow back to Brex. …

Requirement evaluated: Custom field mapping between the AP platform and Intacct

For a $120M multi-location services company running 1,800 invoices/month across two Sage Intacct entities, Brex's mechanism works in two layers. First, the Fields Library (introduced in Brex's Spring 2025 release) serves as a centralized hub where admins can view, configure, and manage all ERP-sourced fields alongside custom Brex fields; admins can then toggle field visibility specifically for bills, meaning Intacct dimensions such as departments, locations, and custom dimensions surface inside Brex's bill coding and approval workflow. …

Limitations: The documented bill pay sync to Sage Intacct enumerates standard fields (vendor, GL account, payment) without confirming that custom Intacct dimensions coded during bill review in Brex are written back to Intacct via the direct sync; this buyer's AP team should verify whether their specific Intacct custom dimensions (e …

Requirement evaluated: Payment approval workflow: all payment batches require CFO or Controller electronic approval before release; approval thresholds can be set per bank account

For your 3-person AP team sending bi-weekly check runs and monthly ACH batches out of Sage Intacct, Brex's Bill Pay approves each bill's payment individually. It does not approve a whole batch. A drafter or AP clerk uploads or emails in an invoice, and Brex AI fills the draft. The drafter picks the funding account and send date on that bill (Brex Bill pay and Brex Essentials/Premium Bill pay implementation guides). The bill then moves through the approval chain set in the Bill pay policy, which Brex says can be tailored by amount, vendor and employee role (Brex bill pay product page; Approval chains help article). …

Limitations: I found no documentation of a payment-batch release gate, or of approval thresholds set per bank account. Thresholds are based on bill amount, vendor and role, and the funding account is picked bill by bill. …

Requirement evaluated: International wire payments to 8 overseas vendors with multi-currency support; the platform should select the optimal international method per destination country rather than requiring the AP clerk to choose manually

For your 8 overseas vendors, Brex supports outbound international payments through multiple rails: SWIFT-based international wires (in USD or local currency), local rail transfers, and SEPA for European destinations, across 120+ countries per Brex's documented coverage. Brex can facilitate transactions to all listed locations with available currency options, and bills can be paid via international wire using either a Brex business account or an external bank account as a funding source. …

Limitations: Brex presents payment method selection (international wire vs. local rail, USD vs. local currency) as a manual clerk decision at the time of each payment, which is precisely the workflow the buyer wants to eliminate. …

Requirement evaluated: Early payment discount detection: auto-flag invoices with discount terms (2/10 net 30) and alert AP when deadline approaches

For a $120M services company processing 1,800 invoices per month across 2 Sage Intacct entities, the specific requirement is automated detection of early payment discount terms (e.g., 2/10 net 30) on inbound supplier invoices, with a proactive AP alert as the discount deadline approaches. Brex Bill Pay's AI extracts invoice data into a draft bill when invoices are uploaded or emailed to a unique Brex inbox, and the bill pay form captures a due date field; however, no documentation in Brex's help center or product pages describes a discrete mechanism for parsing discount terms (the '2/10' portion of 2/10 net 30), auto-flagging those invoices as discount-eligible, or triggering a time-sensitiv …

Limitations: No verified product mechanism exists in Brex's documented feature set for parsing the discount portion of split payment terms (e.g., 2/10 net 30) from supplier invoices and generating a separate, discount-deadline-specific alert to AP before the 10-day window closes. …

Requirement evaluated: Positive pay file generation formatted for Bank of America

This $120M services company needs to generate a Bank of America-formatted positive pay file after each check run so that BofA can match and validate issued checks before they clear. Brex's bill pay module does not support this workflow at any level. Brex's documented payment methods for bill pay are virtual card, ACH, domestic wire, and international wire; physical check issuance exists only through Brex's own banking product (backed by Column N.A.), where checks are mailed by Brex via USPS directly from its own infrastructure. …

Limitations: Brex's check disbursement is locked to its own banking infrastructure and cannot produce a Bank of America-formatted positive pay file; buyers who require positive pay compliance with an external bank like BofA would need to either abandon Brex checks entirely, move to ACH-only payments through Brex, or maintain a para …

Requirement evaluated: Mobile approval with full invoice image view; approvers must be able to act from their phone in under 30 seconds

For a multi-location services company moving off email-chain approvals, Brex Bills handles approval routing at stage 2 of the pre-processing journey (legitimacy review and approval chain), before payment execution. When a bill is submitted, approvers receive a push notification to the Brex iOS or Android app and can navigate to a dedicated Tasks inbox to act. Brex's own help documentation confirms approvers can approve bills directly from the app by going to Tasks, clicking on a bill, and selecting Approve or Deny — a flow Brex describes as completable "in a few taps" from the task inbox. …

Limitations: The material gap for this buyer is confirmation that the uploaded vendor invoice PDF or image is viewable inline within the Brex mobile app during the approval step, without a separate download or desktop redirect; Brex documentation confirms the mobile approval tap-flow but does not explicitly address inline invoice d …

Requirement evaluated: Approval delegation with automatic expiration (e.g., delegate to backup for 5 business days while on PTO)

For a 3-person AP team at a 2-entity Sage Intacct company, Brex's approval chain management covers the core need: multi-level, sequential approval chains for bills can be configured per amount and vendor, and admins can reassign approval chain responsibilities when a user is no longer available. Brex's help center documents that when an approver is deactivated or offboarded, account and card admins receive an alert and can transfer approval chain responsibilities to active users. A Brex marketing blog also references 'delegation options for approvers on leave' as part of intelligent approval routing. …

Limitations: The documented mechanism is admin-initiated manual reassignment of the approval chain, not a self-expiring delegation: the chain stays with the backup until an admin manually reverses it, creating the risk of forgotten delegation that persists past the approver's return. …

Requirement evaluated: Segregation of duties enforcement: person who enters cannot approve, person who approves cannot process payment

For a 3-person AP team at a $120M multi-location services company needing to enforce that the invoice drafter cannot approve and the approver cannot release payment, Brex covers the first boundary (enter vs. approve) natively but covers the second boundary (approve vs. pay) only partially. On the drafter-cannot-approve control: Brex's role architecture separates 'draft bills' from 'approve payments' as distinct, independently assignable permissions within the Manage Bills toggle, and a dedicated 'AP clerk' role is explicitly scoped to drafting and editing bills while requiring approval for outbound transfers. …

Limitations: The self-approval guardrail is described as requiring Brex to enable it (not a default-on setting the buyer controls directly), and the full three-way duty separation (enter, approve, pay) …

Requirement evaluated: Configurable multi-step approval routing by: dollar threshold, department, GL account, vendor, entity, expense type, and project

For this multi-location services company processing 1,800 invoices per month across two Sage Intacct entities, Brex routes bill pay approvals through its Policy Engine. Admins configure a dedicated Bill Pay rule group within the Default policy section; using the Policy Engine, bills can be dynamically routed for approval based on attributes of the bill, specifically Amount and Vendor. The broader Policy Engine, which covers card expenses and reimbursements in addition to bill pay, gives admins the flexibility to create dynamic rules based on factors such as amount, expense type, role, merchant, and more. …

Limitations: The buyer's requirement spans seven routing dimensions (dollar threshold, department, GL account, vendor, entity, expense type, and project); Brex's documented bill pay approval routing covers only two of these natively (amount and vendor), meaning department-by-department approver chains, GL-account-triggered escalati …

Requirement evaluated: Card transactions flow through the same coding, approval, and audit trail as invoices, not a separate system

For a 3-person AP team at a $120M multi-location services company currently managing everything in email and Sage Intacct, Brex does bring card transactions and invoices into a shared platform environment, but the degree of unification has a material boundary. Card transactions land in Brex's Expenses tab, where AI categorizes them, auto-matches receipts, and applies GL coding rules; bills (invoices) are managed separately in Brex's Bill Pay module, with their own queue, approval policy configuration via the Policy Engine, and multi-level approval chains. …

Limitations: Card transactions and invoices share approval-chain infrastructure and GL coding rules in Brex, but they do not flow through a single unified processing queue: cards are managed in the Expenses tab and bills in the Bill Pay module, which means the AP team will still context-switch between two views rather than working …