BILL (Bill.com) vs MineralTree

Requirement evaluated: KPI tracking: average days to approve, touchless rate, cost per invoice, exception rate, discount capture rate

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. …

Limitations: At least three of the five buyer-named KPIs (touchless/straight-through rate as a discrete percentage, cost-per-invoice benchmarking, and early payment discount capture rate) …

Requirement evaluated: KPI tracking: average days to approve, touchless rate, cost per invoice, exception rate, discount capture rate

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. …

Limitations: The buyer's three most operationally critical AP-automation KPIs, specifically touchless/straight-through rate, days-to-approve cycle-time trending, and cost-per-invoice as a system-calculated metric, are not evidenced as native dashboard widgets in MineralTree Analytics; cost-per-invoice in particular is framed in ven …

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

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. …

Limitations: BILL's two-way matching for Sage Intacct is a manual PO-selection and variance-alert workflow rather than an automated tolerance-rules engine: there is no documented configurable price or quantity variance threshold, and automated exception routing based on match outcome is absent. …

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

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 orde …

Limitations: The standard matching tolerance is a global setting and cannot be configured at the vendor or PO type level, meaning the buyer cannot set tighter tolerances for fixed-fee subcontractor service POs versus looser tolerances for time-and-materials engagements. …

Requirement evaluated: Automatic combination of multiple approved invoices to the same vendor into a single payment, with the matching criteria used for combination clearly stated

For a 3-person AP team processing 1,800 invoices per month across two Sage Intacct entities, BILL's payment consolidation works as follows: administrators enable the feature globally under Payables Preferences, then activate it per vendor by checking 'Combine payments' under Payment Processing on each vendor record. Once enabled, BILL automatically combines multiple approved bills to the same vendor into a single check or ACH (ePayment) disbursement. …

Limitations: BILL can combine a maximum of 35 bills per single consolidated payment; vendors with more than 35 open approved invoices in a payment run will require a second payment. Card payments (virtual card, BILL Divvy Card) …

Requirement evaluated: Automatic combination of multiple approved invoices to the same vendor into a single payment, with the matching criteria used for combination clearly stated

For a multi-location services company running 1,800 invoices per month through Sage Intacct, MineralTree's payment grouping feature directly addresses this requirement. When paying multiple invoices to the same vendor, the default setting in MineralTree is to group them into one payment amount, with the individual invoices itemized on the remittance sent to the vendor. This behavior is on by default across all payment methods and is controlled at the vendor profile level: if a specific vendor requires one payment per invoice, the AP team edits that vendor's profile and checks the 'disable payment grouping' checkbox. …

Limitations: The published documentation confirms that the primary grouping criterion is same vendor (payee), with the vendor-profile toggle as the override mechanism; however, the documentation does not explicitly enumerate secondary matching criteria such as same payment method, same Intacct entity, or same currency, which the bu …

Requirement evaluated: Native, pre-built, bidirectional integration with Sage Intacct (not middleware-dependent)

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. …

Limitations: Transaction-level sync is one-directional by default (BILL to Intacct), not fully bidirectional: only unpaid bills return from Intacct to BILL, meaning payment status and reconciliation data do not flow back symmetrically. …

Requirement evaluated: Native, pre-built, bidirectional integration with Sage Intacct (not middleware-dependent)

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. …

Limitations: Vendor payment voids executed inside Intacct do not automatically sync back to MineralTree; the AP team must manually void in both systems. Intacct's native allocation field is not directly replicated in MineralTree; allocations must be handled by manually creating additional line items, which adds a small process step …

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

For a $120M multi-location services company evaluating BILL as its first AP automation layer, SOC 2 Type II is a completed, annually renewed audit rather than a point-in-time snapshot or an in-progress effort. BILL's dedicated security pages confirm that the company undergoes an annual SOC 1 and SOC 2 Type II audit by a leading national CPA firm, covering BILL Accounts Payable, BILL Accounts Receivable, and BILL Spend and Expense. The completed report is available to account administrators and accountants upon request, delivered under a non-disclosure agreement (NDA). …

Limitations: BILL does not publicly name the specific CPA firm conducting the audit (the security page references 'a leading national CPA firm'), and the full report is restricted-use under NDA rather than publicly downloadable. …

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

For your 2-entity Sage Intacct environment, MineralTree holds a current SOC 2 Type II attestation, completed by an independent third-party auditor against AICPA's five Trust Service Criteria: Security, Availability, Processing Integrity, Confidentiality, and Privacy. MineralTree's TotalAP product page states that "security policies and platform are regularly audited to ensure compliance with some of the strictest standards, including Sarbanes-Oxley (SOX), SOC 1 Type 2, SOC 2 Type 2, and SOC2+/HIPAA." Post-acquisition, the parent company GTreasury has codified this commitment contractually: GTreasury's Security Addendum commits to causing "a third-party independent auditor to, at least annual …

Limitations: The SOC 2 Type II report is not publicly downloadable; your team will need to formally request it during vendor evaluation or contracting, at which point you will be required to sign a confidentiality agreement before receiving the report. …

Requirement evaluated: Automatic extraction of: vendor name, invoice number, date, PO number, line items, amounts, tax, and payment terms

For a company currently keying invoices manually from email and mail into Sage Intacct, BILL offers two stacked AI extraction layers. The first is the Intelligent Virtual Assistant (IVA): a feature that uses machine learning to extract invoice information from documents in the Inbox. IVA attempts to pre-populate header-level fields including vendor name, invoice number, invoice date, due date, total amount, and payment terms. If IVA detects a payment term that differs from the vendor's profile, the AP user is prompted to set a preference for which source to treat as default going forward. …

Limitations: IVA will only make predictions for a bill from the first page of a document, requiring manual Click and Capture for multi-page invoices, which is a real friction point for subcontractor and facilities invoices that frequently run to multiple pages. …

Requirement evaluated: Automatic extraction of: vendor name, invoice number, date, PO number, line items, amounts, tax, and payment terms

For a 3-person AP team currently keying invoices by hand into Sage Intacct, MineralTree's Invoice Capture feature sits at pre-processing Stage 1 (legitimacy and data ingestion) and partially Stage 2 (PO matching). When an invoice arrives by email or scanned mail, your team forwards or uploads it to a dedicated MineralTree inbox. The system then applies OCR combined with human-in-the-loop validation to extract both header and line-level fields: returned data includes header-level information such as vendor name, invoice number, and invoice amount, and line-level data is also available. …

Limitations: Line-item extraction (required for your 55% PO-based volume and for coding non-PO line detail) is configurable rather than on by default: invoices can be captured at either the header-summary level or by line and header, and line-level capture must be enabled to take advantage of line-level PO matching. …

Requirement evaluated: Rush/emergency payment workflow with compressed timeline and appropriate audit trail

For your 3-person AP team on Sage Intacct, BILL has no dedicated rush or emergency workflow. It does give you three separate pieces you could combine. First, approvals: approval policies and approval groups route bills automatically (fact sheet: "Auto-Route bills for approval based on your company's policies"), and approvers or approval groups can be added, updated, removed, or reminded while a bill is in approval. Second, an override: Administrators can pay unapproved bills, as long as those bills have the required approvers assigned. …

Limitations: Nothing in the documentation I found lets you flag a bill as rush, shorten the approval chain, set escalation timers or auto-reroute an unavailable approver. Reminders can only go to the next approver in sequence, and a rush would be handled by manually editing approvers or having an admin pay a bill before it is appro …

Requirement evaluated: Dual approval requirement for all capital expenditures regardless of amount

For a multi-location services company needing dual approval on every CapEx invoice regardless of dollar amount, MineralTree's approach involves two layered mechanisms. First, invoice approval rules can be built on GL account coding: invoices can be routed for approval automatically based on class, vendor, or GL account coding, so your team would create a rule tied to each CapEx GL account code and assign the two required approvers to that rule. …

Limitations: The 'approval by all' enforcement is a company-wide global setting per the configuration that applies to all invoices within your organization and cannot be changed for specific vendors: activating it to enforce dual CapEx approval forces the same requirement onto every invoice across the company. …

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

For your 3-person AP team paying about 1,800 invoices a month through checks and ACH, BILL offers a native 1099 Filing module under the Tax Compliance menu. It collects W-9s automatically with the W-9 Agent, categorizes payments, and creates and e-files 1099-NEC or 1099-MISC forms. Users mark vendors as 1099-eligible, then use Prep & File 1099s to map each vendor to a 1099 box number. BILL's product page says it files with the IRS and all 50 states and delivers forms via USPS or by email. Because payments run through BILL's AP (card, ACH, and check per the fact sheet), this sits in the payment and compliance stage after the pre-processing journey. …

Limitations: The Intacct sync is the weak point for classification. The 1099 flag syncs only when a vendor is first created, and new vendors default to form type NEC, box 1. The GL-level 1099 category does not sync to Intacct, and changes to GL accounts are not applied retroactively. …

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

For your 3-person AP team processing 1,800 invoices monthly across two Sage Intacct entities, MineralTree's Analytics module (available in TotalAP packages) provides visual dashboards that can be filtered by vendor, business unit, or time period. Documented KPIs include invoice aging, payment mix, days payable outstanding, average invoice processing time, and vendor spend totals. …

Limitations: Two of the three requested metrics — on-time payment rate per vendor and dispute frequency per vendor — are not documented as pre-built, natively computed KPIs in MineralTree's Analytics module; they would require the buyer to export raw payment data via Search Page Reports and calculate them offline. …