BILL vs Ariba vs Mekorma for AP Automation

For a $120M multi-location services company processing invoices and payments across two Sage Intacct entities, BILL addresses data encryption at the infrastructure and transport layers. On the at-rest side, BILL's security documentation states that 'BILL Accounts Payable and BILL Accounts Receivable ensures customer data is protected at rest with encryption' and applies 'an additional level of encryption to protect access to sensitive customer data from malicious applications.' The production environment runs on AWS across three physically separate availability zones, with continuous data backups to a secondary region, providing the encrypted storage substrate for all invoice documents, vendor records, and payment credentials. For data in transit, BILL uses Transport Layer Security (TLS) with industry-standard cipher suites across all customer-facing sessions, API calls to Sage Intacct, and inter-system communications, which BILL describes as 'bank-level protection during transfer.' Compliance attestation is provided through annual SOC 1 and SOC 2 Type II audits conducted by an independent CPA firm, covering AP, AR, and Spend and Expense products; BILL Spend and Expense also maintains PCI Level 1 compliance via annual Qualified Security Assessor audit, and AP/AR have achieved PCI Level 1 for virtual card and Pay by Card functions. Payment data specifically is protected by routing disbursements through a BILL clearing account, masking your bank account details from vendors entirely.

For a multi-location services company processing invoice documents and transactional data through SAP Ariba and SAP Business Network, encryption operates at the platform infrastructure level on behalf of all customers with no buyer-side configuration required. All data stored in SAP Ariba databases is encrypted using AES-256, and data moving between users, suppliers, and the Ariba Network is secured via TLS 1.2 or higher. SAP uses a centralized Key Management Service (KMS) to handle encryption keys, with a Bring Your Own Key (BYOK) option available for customers who require additional control over key management. Third-party attestation of these controls is current: SAP Ariba and SAP Business Network have a SOC 2 Type 2 audit report prepared by an independent third-party accountant, covering the period April 2023 to March 2024, against the trust principles of Security, Availability, Processing Integrity, and Confidentiality. SAP is also certified under ISO 27001 and ISO 22301.

For a $120M multi-location services company running Sage Intacct, Mekorma presents a foundational compatibility problem before encryption can even be evaluated: Mekorma is purpose-built for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica, and does not support Sage Intacct. On the encryption question itself, Mekorma's own published documentation does not include a trust center, security whitepaper, or product page that states specific cryptographic standards for the platform as a whole. The one encryption reference found in Mekorma's materials is narrow: the Payment Hub product page references 'encrypted signature storage' for electronic check signatures, which is a feature scoped to check-printing security rather than a statement about AES-256 encryption of stored invoice data or TLS enforcement for all data in transit. No SOC 2 Type II attestation, ISO 27001 certification, or explicit TLS/AES specification was found in any Mekorma-authored document across multiple searches.

For a 3-person AP team processing 1,800 invoices per month across two Sage Intacct entities, BILL's invoice capture stack works as follows. Vendors email invoices to a dedicated BILL inbox address (e.g., companyname@bill.com); 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 documents arrive, the Intelligent Virtual Assistant (IVA) uses machine learning to extract invoice information from documents in the inbox. IVA currently works on PDF, PNG, JPG, and JPEG type documents. On the header side, IVA pre-populates vendor name, invoice date, due date, amount, payment terms, and invoice number; if BILL is confident enough in the IVA-detected details, it surfaces an option to Quick Save the bill directly from the inbox. Fields flagged as lower confidence are held for human review rather than auto-posted, which protects Sage Intacct data integrity. For line-item data, BILL layers two mechanisms: Smart Data Entry (SDE) populates approvers and expense line items based on the most recent bill saved for that vendor, and the newer Invoice Coding Agent adds document-driven predictions. 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 extracts and inputs key invoice fields with almost 99% accuracy, and provides line item coding predictions for amounts, descriptions, and six specific coding fields. This covers pre-processing journey stage 1 (intake and legitimacy) and contributes to stage 5 (cost allocation via GL coding predictions), but stops short of automated 3-way matching confirmation at stage 4.

For a $120M services company processing 1,800 invoices/month in Sage Intacct, SAP Ariba's invoice capture capability is delivered through SAP Ariba Central Invoice Management (recently renamed SAP Ariba Invoicing), which uses SAP's Document Information Extraction (DOX) service as its underlying AI/OCR engine. When an invoice arrives, the system ingests PDFs (both text-based and image/scanned), and email-attached documents via an automated email extraction workflow; the solution enables centralized invoice processing with embedded OCR capabilities and automated workflows. DOX extracts relevant data from invoices and leverages pre-trained machine learning models to identify header fields and line items. When a scanned document is uploaded, the service first converts content to text via OCR, then identifies header fields (invoice number, date, total amount) and line items (products or services, quantities, prices). Against each extracted data field, the system surfaces a confidence range, and accountants can annotate and correct extractions directly in the document; these corrections are stored as templates that continuously improve the extraction process, reducing repetitive manual work over time. However, the critical constraint for this buyer is ERP compatibility: SAP Ariba Central Invoice Management is currently optimized for SAP S/4HANA Cloud Public Edition, and all documented connected systems are SAP S/4HANA variants. There is no native integration path documented between SAP Ariba Central Invoice Management and Sage Intacct, meaning extracted invoice data cannot post directly to the buyer's ERP without custom middleware or a separately sourced third-party connector.

Your team runs on Sage Intacct, and this is the threshold issue: Mekorma does not integrate with Sage Intacct. The vendor's own positioning explicitly scopes the product to Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica. No Sage Intacct connector, marketplace listing, or certified integration exists. Setting the platform mismatch aside, Mekorma does have an Invoice Capture feature for Dynamics GP users, but it is powered by Microsoft Power Platform and AI Builder and extracts only four header-level fields: Invoice Number, Invoice Date, Amount, and Due Date. Line-item data extraction is not part of the documented mechanism. For Business Central users, Mekorma defers to a third-party partnership with SignUp Software rather than providing a native capture engine. Neither path reaches Sage Intacct, and neither path delivers the header-plus-line-item extraction depth the buyer requires.

For your 3-person AP team processing 1,800 invoices monthly across 2 Sage Intacct entities, BILL provides spend analytics through its native Insights module and its reporting layer. The reporting page documents the ability to filter and group data by date range, vendor, category, and department, with payment-by-vendor views directly inside the platform. For vendor-level trending, G2 reviewers confirm that BILL's Insights views show month-over-month and year-over-year changes in vendor spend, addressing two of your three named sub-dimensions. For GL category spend, BILL's own product-updates changelog documents that the native Insights dashboard surfaces only the top five AP expense accounts over a selected time period, a feature added specifically in response to user feedback that it was difficult to answer questions like how much was spent on a given category in a specific month. Full GL category breakdowns beyond those five accounts require exporting transaction data to CSV or Excel for manual analysis, or relying on Sage Intacct's own GL reporting after sync.

For a $120M services company running Sage Intacct, Mekorma cannot deliver this requirement on two independent grounds. First, Mekorma is purpose-built for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica: it has no documented integration with Sage Intacct and does not appear in the Sage Intacct Marketplace partner directory. Second, even within the Dynamics environments it does support, Mekorma's reporting layer is limited to payment-execution records: an Audit Log of posted check and EFT batches (filterable by checkbook, batch, and posting date), a Payment Inquiry screen showing processed payments by vendor ID, date, and payment method, and a one-time Excel export from the vendor ledger used during Remote Payment Services onboarding to assess payment-mix. None of these constitute spend analytics. There is no pre-built dashboard for top-vendor rankings by total spend, no GL account category breakdown, and no month-over-month trending view anywhere in Mekorma's documented product set.