Brex vs Medius

Requirement evaluated: Unified payment hub supporting ACH, check, wire transfer, and virtual card from a single interface

For a 3-person AP team at a $120M multi-location services company currently managing payments across disconnected bank portals, Brex Bill Pay consolidates all four payment rails into a single dashboard. Within the Bill Pay module, users upload invoices, route them through approval flows, and then pay via ACH, domestic or international wire, check, or Brex card, with the result synced to the connected ERP. The product supports scheduling one-time or recurring ACH payments, checks, or wires, including international wires in foreign currency, from any connected bank account, with Brex's enhancements having opened up access to third-party bank accounts for greater funding flexibility. …

Limitations: Unlike wire transfers and ACH payments, one-time virtual card bills are not processed automatically: either the designated cardholder or the vendor must manually process the payment using the provided card details, which introduces a manual step that breaks true straight-through processing for card-based disbursements. …

Requirement evaluated: Unified payment hub supporting ACH, check, wire transfer, and virtual card from a single interface

For a $120M multi-location services company currently running fragmented bi-weekly check runs and monthly ACH batches through manual bank portals, Medius Payments consolidates all disbursement rails into a single interface. The module, branded as Medius Payments (built on the acquisition of OnPay Solutions and launched as an evolution of Medius Pay), covers all four rails the buyer requires: ACH, check, wire, and virtual card for US-based operations are handled in a single consolidated process for each supplier, with no need to log into a separate bank portal for ACH transmission. …

Limitations: Wire transfer execution is file-based: Medius formats the wire instruction and transmits it via secure FTP to the client's bank wire desk rather than executing it through a direct real-time bank API, which may introduce a processing lag for urgent wires compared to fully in-bank wire execution. …

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

For a 3-person AP team processing 1,800 invoices per month, Brex Bill Pay operates at stage 1 of the pre-processing journey (invoice capture and data extraction). When an invoice arrives via email forward, drag-and-drop upload, or vendor upload link, Brex AI technology immediately captures data from PDFs and email attachments and automatically extracts key information like amounts, due dates, and vendor details. The underlying extraction engine is LLM-based: Brex evolved its invoice scanning from traditional OCR technology with 80% accuracy to advanced LLM-powered technology that delivers 97% accuracy and blazing-fast line itemization. …

Limitations: The documented extraction mechanism is a shared LLM model fine-tuned at the Brex platform level, not a customer-specific learning engine that builds vendor-level recognition profiles from this buyer's correction history. …

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 a varied vendor mix of facilities, subcontractors, utilities, and subscriptions, Medius addresses this requirement through two named, integrated modules: Medius Capture and SmartFlow. Medius Capture uses OCR, AI, and machine learning to extract header and line-item data from paper and digital invoice formats; Medius Capture has been refining its AI and Machine Learning algorithms since 2016, learning from hundreds of millions of invoices to deliver 100% touchless capture rate. …

Limitations: Medius's published learning claims (95% precision, learns after two invoices) are marketing-tier commitments; granular technical documentation on whether AP user corrections explicitly retrain a per-customer model versus operating on aggregate cross-customer patterns was not surfaced in available help-center documentat …

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

For a $120M services company with 55% PO-based invoices covering facilities, supplies, and subcontractors, the matching ceiling matters directly for roughly 990 invoices per month. Brex's bill pay module performs automated two-way PO matching: when an invoice arrives, the AI scans it and attempts to match it to an open PO synced from the ERP, surfacing the PO number, date, and remaining available amount for AP review; if no automatic match is found, it presents the open POs for that vendor for manual selection. Brex AI matches the imported invoice to an open PO in the ERP "via our two-way accounting integrations," framing the mechanism explicitly as two-way. …

Limitations: Brex's matching architecture is two-way (invoice to PO) with no documented goods receipt confirmation as a native third leg, leaving the buyer exposed to paying for undelivered or short-shipped goods on their facilities, supplies, and subcontractor invoices without a warehouse or project team sign-off step in the syste …

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

For this buyer's 55% PO-based invoice volume covering facilities, supplies, and subcontractors, Medius executes automated three-way matching by synchronizing vendor ledgers, purchase order details, and goods receipts from Sage Intacct into the matching engine, then comparing the inbound invoice against all three documents before routing. To enable automated 3-way matching, Medius requires that master data including vendor ledgers, purchase order details, and goods receipts synchronize seamlessly between the ERP system and the AP automation solution. When all data aligns within applied tolerance levels, the invoice flows touchless to ERP posting without manual review. …

Limitations: The goods receipt must originate in Sage Intacct (or be registered there by the receiving team) before the match can execute; if the buyer's receiving staff delays entry of goods receipts into Sage Intacct, invoices will queue in an exception state awaiting the receipt record rather than routing automatically. …

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

For a $120M, 2-entity Sage Intacct customer running 1,800 invoices per month, Brex offers a native, self-serve Sage Intacct connector that Brex's own documentation describes as one that 'does not require any additional cost,' with setup completed directly inside the Brex dashboard by enabling Web Services in Intacct, creating a Web Services User, selecting entities, and mapping GL accounts, departments, and custom dimensions. The help center publishes the full configuration walkthrough, including entity selection and field mapping steps, positioning this as a guided self-setup rather than a professional services engagement. …

Limitations: The buyer's 2-entity Sage Intacct configuration sits precisely at the threshold where Brex's standard self-serve setup transitions into complexity-triggered professional services fees; whether integration setup is truly included at no extra cost depends on tier placement and contract negotiation, not a published blanke …

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

This buyer runs 2 Sage Intacct entities and needs the connector configuration, field mapping, and go-live setup included in the base implementation fee rather than billed as a separate SOW. Medius does offer a pre-packaged Sage Intacct integration, but the architecture here is materially different from its flagship ERP connectors: Medius has a pre-packaged integration with Sage X3 and Intacct in partnership with Acuity Solutions, a UK-based Sage specialist, rather than through Medius's own 'fully managed' connector infrastructure that covers SAP, Oracle, NetSuite, Infor, and Microsoft Dynamics. …

Limitations: The Sage Intacct integration is partner-delivered through Acuity Solutions, a UK-only Sage specialist, not a Medius-managed first-party connector. This creates a real risk that integration setup, chart-of-accounts mapping, and multi-entity configuration for this buyer's 2 Intacct entities will be scoped and billed as a …

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: Segregation of duties enforcement: person who enters cannot approve, person who approves cannot process payment

For a 3-person AP team at a multi-location services company, Medius enforces all three legs of segregation of duties through distinct, system-level mechanisms rather than policy-only controls. First, the `AllowInspectAndAttest` system parameter controls whether the user who reviewed and coded an invoice can also approve it: setting this to 'No' means that a person who has reviewed a coding row can never approve the same row. Second, Medius includes a configurable Four Eyes Principle (4EP) …

Limitations: All three controls (AllowInspectAndAttest, Four Eyes Principle, Pay Approver Role) are configurable settings that must be deliberately activated during implementation; they are not all enabled out-of-the-box, so the buyer's implementation team must confirm each is turned on and that no threshold-based bypass exists (fo …

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 two Sage Intacct entities, Medius addresses this requirement through Medius Analytics, a dedicated reporting module with out-of-the-box dashboards that are automatically available upon deployment. The module delivers a real-time spend analysis view covering cashflow, costs, and forecasts through pre-defined reports, dashboards, and KPIs, with drill-down capability to the individual supplier level for vendor performance monitoring. …

Limitations: Documentation confirms the named dashboards and the supplier- and dimension-level filtering mechanism, but the exact out-of-the-box layout of a 'top vendors' ranked list or an explicit MoM trend chart is not shown in public help articles; buyers should request a live demo of the Cashflow and Overview dashboards to conf …

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 self-service portal: new vendor registration, W-9/W-8 submission, banking detail entry, invoice submission, payment status inquiry

For a $120M services company currently managing vendor onboarding entirely via email and manual data entry into Sage Intacct, Medius offers a dedicated, supplier-only self-service portal that covers all five sub-requirements in the buyer's ask. On the registration and onboarding side, a dedicated self-serve portal gives suppliers the flexibility to respond to onboarding forms from all of their customers in one place; it is vendor management software that puts the onus on the supplier to onboard and maintain their details in a secure, self-service online portal. …

Limitations: Medius's onboarding questionnaires are configurable for document upload including tax forms, but no Medius documentation explicitly confirms a native W-9/W-8 collection workflow with IRS TIN matching or automated validation; buyers with high volumes of subcontractors who need structured, validated tax-form collection s …

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: Data encryption at rest and in transit

For a $120M multi-location services company handling invoice data, vendor credentials, and payment information across two Sage Intacct entities, Medius provides encryption controls at both the storage and transmission layers. On the storage side, Medius explicitly documents AES-256 encryption across its infrastructure, which is hosted in Microsoft Azure data centers with customer data separated into unique SQL databases per customer. On the transmission side, Medius's Trust Center confirms that Transport Layer Security (TLS) …

Limitations: Medius's publicly accessible Trust Center pages confirm AES-256 and TLS but do not enumerate the specific TLS version floor (1.2 vs. 1.3) in free-text form; buyers with contractual requirements for a minimum TLS version should request the full SOC 2 Type 2 report and Qualys detail from trust.medius.com to confirm. …