MineralTree vs BILL vs Medius for AP Automation

For this 3-person AP team at a $120M multi-location services company processing 1,800 invoices per month across two Sage Intacct entities, Medius Analytics is a dedicated, named module that delivers the full KPI set requested. The module provides pre-built dashboards and real-time reporting covering cycle times, touchless rates, cost per invoice, and exception rates: specifically, the Medius Analytics product page confirms it delivers 'pre-defined reports, dashboards and KPIs' including touchless and extraction rates with drill-down to individual supplier level, and the invoice automation product page explicitly states Medius 'surfaces comprehensive, real-time analytics on invoice status, exception rates, cycle times, and cost per invoice.' Discount capture rate is tracked as a named metric within Medius's analytics framework, documented in the Medius AP analytics blog as 'Discount Capture Rate indicates the extent to which available early payment discounts are being captured.' The platform also includes a published AP Benchmark Report drawing on thousands of customer data points, allowing this buyer to compare their own KPI results against peer benchmarks. Benchmarking and KPI access are built into the product, not a services add-on, as confirmed by a customer quote: 'Medius provides us with the KPIs and tools we need to identify issues, solve them and drive more automation across the entire process.'

For a 3-person AP team at a $120M services company moving off manual email-chain approvals, MineralTree offers a named analytics module, 'MineralTree Analytics,' embedded inside the TotalAP Invoice-to-Pay platform. The support center confirms a dedicated 'Analytics Reporting' article exists as a distinct help topic, and the June 2021 product launch documented that the module delivers real-time dashboards covering invoice aging, early pay discounts, rebates earned, and payment mix. The TotalAP product page states users can 'ditch the spreadsheets and access real-time dashboards that visualize KPIs such as invoice aging, payment mix, and rebates earned,' and the payment analytics blog confirms users can 'track the rate of error as a percentage of total invoices paid' and filter aggregate metrics by business unit, vendor, or time period. Of the buyer's five required KPIs, discount capture rate is explicitly confirmed as a named dashboard metric; exception rate is partially supported via error-rate tracking; and invoice aging proxies for cycle-time visibility. However, MineralTree's own blog content on cost-per-invoice walks through a manual labor-plus-infrastructure calculation formula rather than describing a system-generated widget, and no source documents a native touchless rate (straight-through processing percentage) or days-to-approve trend widget as a pre-built out-of-the-box dashboard KPI.

For a 3-person AP team at a $120M services company processing 1,800 invoices per month, BILL's native reporting operates through its 'Insights' module: BILL Insights offers out-of-the-box dashboards to optimize AP processes by identifying trends, opportunities, and potential savings. The module surfaces payment status, invoice volume trends, and approval activity using data captured from BILL's own workflow engine, meaning in-flight timing data (not just post-sync ERP data) is available. For the buyer's five named KPIs, coverage is uneven: average days to approve has reasonable support given that the audit trail captures every action with timestamps, enabling cycle-time calculations; however, discrete pre-built metrics for touchless rate, exception rate, and discount capture rate are not documented in any official help center content retrieved. BILL's blog marketing copy claims users can track essential metrics like PO cycle time, cost per invoice, and spend under management without manual data collection, but this is blog-tier content with no corresponding help center mechanism documented for cost-per-invoice benchmarking as a native widget. Separately, one of the main challenges with BILL is that some of the features and reporting customization can feel limited, consistent with the gap between the buyer's five-KPI requirement and what Insights demonstrably surfaces out of the box.

For a $120M services company running two Sage Intacct entities, MineralTree's TotalAP platform connects to Intacct via a direct API integration with no middleware layer. The mechanism works as follows: an Accounting Manager authenticates using Intacct admin credentials inside MineralTree to initiate the sync; from that point forward, MineralTree pulls all Intacct objects bidirectionally, including bills, vendors, accounts, dimensions, credits, and more, and posts approved invoices back to Intacct at the entity level. The integration is documented as API-based, not file-based: as the support documentation states, 'when MineralTree posts invoices, payments, or any changes to your ERP, we are doing so through an API connection,' and any subsequent changes made in MineralTree are also reflected in Intacct. For this buyer's two-entity Intacct setup specifically, MineralTree offers a documented configuration choice: sync to the top level (all entities consolidated in one MineralTree company) or sync each entity to its own MineralTree company; the top-level sync is the correct path for a centralized AP team that processes across both entities. The Sage Intacct Marketplace lists MineralTree as a direct-integration partner, confirming 2-way syncing of invoice header and line items, vendor credits, multi-currency, and dimensions. Additionally, MineralTree and Sage have a formal embedded partnership: Vendor Payments powered by MineralTree is fully embedded within Sage Intacct, allowing payments to be initiated directly inside the ERP without separate logins or a settlement account.

For a $120M services company running 2 Sage Intacct entities, BILL connects directly to Intacct via Sage Intacct's XML Web Services API: a dedicated non-billable sync user (XML_Bill.com) is created inside Intacct and credentialed within BILL's Sync settings, with no third-party middleware broker required. The integration is listed on the Sage Intacct Marketplace as a preferred partner connector. List objects including Vendors, Chart of Accounts, Departments, Locations, and Items receive a documented 2-way sync, and User Defined Dimensions sync across bills and transactions to preserve the buyer's Intacct configuration. However, the transaction-level sync is asymmetric in the standard configuration: bills, vendor credits, and payments flow from BILL into Intacct, but only unpaid bills flow back from Intacct into BILL, not paid bills or full payment status updates. For the buyer's 2-entity Intacct environment, BILL offers two sync paths: top-level sync (both entities share one BILL connection) or entity-level sync (BILL scopes to one Entity ID at a time). The entity-level path carries a documented constraint that bills coded to that sync will ONLY post to that entity and cannot be coded to any other entity, which creates operational friction if the AP team processes invoices across both entities from a single BILL workflow. Sync cadence is scheduled at least once daily, with a manual 'Sync Now' option available; real-time sync is not offered. A Sage Intacct Customization Services subscription is required for the integration to function.

For this buyer's two-entity Sage Intacct environment, Medius does not offer the same class of natively owned, internally maintained connector it provides for SAP, Microsoft Dynamics, Oracle, and NetSuite. Instead, Medius has a pre-packaged integration with Sage X3 and Intacct in partnership with Acuity Solutions, a UK-based Sage VAR. A CB Insights press snippet confirms the mechanism: Medius signed agreements with UK-based VARs including Acuity Solutions, under which the partners "developed pre-packaged connectors between Medius AP Automation and the ERP." By contrast, Medius has fully managed integrations to leading ERP solutions from Microsoft, Oracle NetSuite, Oracle JDE, Oracle Fusion, Infor, and SAP so that master data is accurately transferred from the ERP application to Medius AP Automation — Sage Intacct is not in that tier. Medius Connect, the umbrella integration layer, also exposes "Medius iPaaS" to seamlessly connect Medius to ERPs and a wide range of third-party systems, meaning an iPaaS component exists within the Medius Connect architecture, which is the anti-pattern the buyer explicitly wants to avoid. No public documentation found from Medius or Acuity Solutions quantifies which Sage Intacct dimensions, custom segments, or multi-entity fields the connector syncs bidirectionally, leaving field fidelity for the buyer's two-entity setup undocumented.

For a services company like this buyer, where roughly 55% of invoices are PO-based (facilities, supplies, subcontractors) and no warehouse receipt transaction will exist for service POs, MineralTree's TotalAP platform for Sage Intacct offers two explicitly documented matching paths. The first is 'standard matching': MineralTree automatically syncs POs from Intacct, and when new invoices are received, its PO matching algorithm intelligently links line-items from invoices to line-items in purchase orders and automatically applies the proper coding; receipt-based matching is a separate, optional path only activated for customers who use the Intacct PO Receivers workflow to track receipt of ordered items. This means service POs, where no goods receipt transaction will ever exist, proceed through the standard two-way path without being blocked or generating false exceptions. At the line level, match tolerance is the margin of error accepted between invoices and purchase orders, evaluated on cost per unit for items and total amount for expenses. When a mismatch is present, the incorrect field is highlighted in red, and users can click an alert icon to learn more about why the mismatch occurred. This places MineralTree at pre-processing stages 2 (PO match) and parts of stage 3 (terms verification by amount tolerance), with the approval chain covering stage 1 (legitimacy); stage 4 (receipt confirmation) is deliberately bypassed for service POs, which is the correct behavior here.

For a multi-location services company where 55% of invoices are PO-based and many involve subcontractors or facilities with no warehouse receipt, Medius explicitly supports two-way matching as a receipt-free path for service POs. The Medius glossary directly states: "Can invoice matching be tailored for service-based purchases without a goods receipt? Yes. 2-way or contract-based matching can be used for services." At the product mechanism level, Medius's official SAP integration guide confirms that "two-way match orders will not trigger delivery-related deviations, as they do not rely on receipt" -- meaning the matching engine has a distinct invoice-to-PO-only path that bypasses the goods receipt layer entirely. Operationally, this works through Medius's "PO Invoice" connection step (formerly labeled "Orderbased"): the system pulls PO line data from Sage Intacct, compares invoice header and line amounts to the PO, and auto-connects within configurable tolerances. "Connection tolerances are a useful way to remove frustrations in the connection process. An admin or AP user can specify an acceptable range (tolerance) in amount or percentage, for which automatic connection should happen on header- or line-level when the amounts are not an exact match. This can be done on the company and supplier levels." Tolerance rules are configurable by value, percentage, or both, and can be set at either the company or individual supplier level, which allows tighter controls on high-value subcontractor POs and looser tolerances on recurring facilities spend. Within the pre-processing journey, this covers Stage 2 (PO match) with automated exception routing for deviations; Stage 4 (receipt confirmation) is intentionally bypassed for service PO invoice types, which is the correct behavior for this buyer's use case.

For a multi-location services company with 55% PO-based invoices (facilities, supplies, subcontractors) running on Sage Intacct, BILL offers PO-to-invoice two-way matching without any goods receipt requirement. For Sage Intacct customers, PO capabilities and two-way matching are available as part of the subscription, and BILL explicitly positions two-way matching for service-based businesses that process invoices for services or goods where they are not recording receipt of services or items, noting that a two-way match between the PO and invoice may be sufficient in this case. The mechanism is a user-initiated PO link: when creating a bill, BILL automatically shows the most recent open POs for the selected vendor; the AP user clicks to select or types a PO number to narrow results, and once a PO is selected, line items populate based on the items on the PO, with a Qty on bill field editable to bill for some or all PO items. POs originate in Sage Intacct and flow into BILL read-only: POs must be created and maintained in Sage Intacct; they are view-only in BILL and sync one-way from Sage Intacct to BILL. During review, BILL surfaces variance alerts to reduce payment errors, and once matching is complete the bill is automatically sent through the payment approval workflow, which is preassigned by the administrator. This covers pre-processing stage 2 (PO match) only; stage 4 (receipt confirmation) is bypassed by design for service POs, which is the correct architecture here. The ceiling: BILL's matching is a manually-initiated link-and-review step with variance alerting, not an automated tolerance-rule engine with configurable exception routing. There is no documented mechanism in BILL for setting percentage or dollar-amount tolerance thresholds within BILL's own matching layer for Sage Intacct users. Additionally, BILL does not support linking a bill to multiple POs within BILL itself; if a bill is created linked to multiple POs in Sage Intacct, it will sync to BILL but will not link to any POs, which is a real constraint for subcontractor invoices that span multiple service POs.

For a 3-person AP team processing 1,800 invoices per month from email and mail, MineralTree's Invoice Capture module (part of TotalAP) addresses Stage 1 of the pre-processing journey by eliminating manual keying at the point of arrival. Each MineralTree account receives a unique company email address at ap-docs.com; vendors and staff forward invoice PDFs or image attachments directly to that address, and documents automatically land in the MineralTree Inbox without any manual upload step. From there, as the official support article documents, the process uses OCR plus a human review, achieving approximately 99.5% accuracy. The FAQ page confirms the scope of extraction: when you email or upload vendor invoices directly into MineralTree Invoice-to-Pay, it automatically extracts the document's header and line-level information. On format breadth, MineralTree supports 18 file formats and offers header and line-level invoice capture, making it a highly versatile solution. The human-in-the-loop layer is the key mechanism for achieving accuracy above the 95% buyer threshold: MineralTree combines the power of OCR with machine learning and human-in-the-loop validation to achieve 99% accuracy on every invoice.

For a $120M services company currently keying invoices manually from email and mail, Medius Capture addresses Stage 1 of the pre-processing journey by automatically ingesting and extracting invoice data before any human touch. The mechanism works as follows: each legal entity in Medius is assigned a dedicated capture email address; AP staff forward or suppliers send invoices directly to that address, and the system imports the invoice within 3-5 minutes into a 'Capture Verification queue.' Medius's native embedded capture solution automatically ingests invoices arriving by paper, email, EDI, and e-invoice, converting them to a structured digital format. The extraction engine is a distinct product module, Medius Capture, which uses intelligent technology such as optical character recognition (OCR), artificial intelligence (AI), and machine learning (ML) to intuitively extract relevant data from paper and digital invoices including PDF, e-invoices, and EDI, eliminating the need for manual checks and reviews. Critically for this buyer's mix of PO and non-PO invoices, the system accurately captures information from invoice headers and line-items then automatically matches them against single or multiple POs and receivables. The AI layer is not template-based: Medius Capture uses AI and ML to improve accuracy and reduce manual work, and the system can learn from past invoices, adjust to new formats, and process various layouts without needing templates. On top of OCR, invoice coding is applied automatically by proprietary machine learning models, including Siamese CNNs for document classification and SmartFlow, a proprietary CNN that reaches 95%+ coding precision after just two invoices, trained on the customer's historical actions and enriched by 2.4 billion+ invoice field data points across Medius's global customer base. For low-confidence extractions, invoices can be configured to bypass manual validation and go straight through to workflow once a minimum data capture confidence level has been met; invoices where data capture accuracy falls outside the predefined confidence levels will be moved to a separate work queue, where they can be manually verified and corrected by an AP department member. Medius Capture has been refining its AI and machine learning algorithms since 2016, learning from hundreds of millions of invoices to deliver high touchless capture rates.

For a 3-person AP team receiving 1,800 invoices per month by email and mail, BILL offers a layered capture architecture. Invoices emailed to a dedicated @bill.com Inbox address are automatically ingested; a unique Inbox email address is generated, which can be provided to vendors so they can email bills directly into the account for processing. Once in the Inbox, BILL's Intelligent Virtual Assistant (IVA) applies machine learning to pre-populate bill fields: IVA is a feature that uses advanced technologies like machine learning to extract invoice information from documents in your Inbox. If BILL is confident enough in the IVA-detected details, the AP user sees bill details and an option to Quick Save the bill directly from the Inbox. A more recent Invoice Coding Agent layer extends this to multi-line bills: the BILL Invoice Coding Agent dynamically codes multi-line bills based on previous coding behavior, using historical coding and allocation patterns to deliver cleaner, more accurate bills with less manual effort. The agent claims to extract and input key invoice fields with almost 99% accuracy, and provides line item coding predictions for amounts, descriptions, and six specific coding fields. For documents where IVA confidence falls below threshold, a paid add-on called Auto Bill Entry delegates extraction to a third-party service: Auto Bill Entry extracts bill information from documents in the Inbox and turns it into a bill ready for review within one business day, using CloudFactory as a third-party provider. When neither IVA nor ABE produces usable output, the fallback is Click and Capture: for documents or fields IVA is unable to process, Click and Capture enables clickable copy-and-paste from the document image to the Bill Summary or Expense Details windows. This places the capture mechanism at pre-processing stage 1 (legitimacy and data ingestion) and partially at stage 5 (GL coding via the Coding Agent), but it does not advance to stages 2 or 3 without separate PO matching configuration.