Medius vs Sage AP Automation

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

For your AP team processing CapEx invoices across two Sage Intacct entities, Medius enforces dual approval through its dimension-based approval rules engine inside MediusFlow. The trigger is the GL account (or coding dimension) assigned to the invoice, not the invoice amount: when an AP coder tags a line to a capital account range, the approval rules engine routes that invoice through a mandatory sequential approval hierarchy requiring each level to sign off before the next is unlocked. …

Limitations: The documented 4EP configuration example pairs the two-approver requirement with a dollar threshold ($1,000), so confirming that 4EP alone can fire at a $0 floor for CapEx coding rows (with no amount condition at all) …

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

For a multi-location services company running 1,800 invoices per month across 2 Sage Intacct entities, the dual-approver requirement for capital expenditures sits squarely in the pre-processing journey at the approval stage (stage 2 of 5: legitimacy and authorization before ERP posting). Sage Intacct's native AP module supports configurable, multi-level approval workflows: administrators define sequential or parallel approval chains, set thresholds, and route by dimension such as department or location. …

Limitations: The documented routing dimensions for Sage Intacct's native AP approval engine are amount thresholds, department, and location; GL-account-type triggering (the mechanism needed to enforce dual approval on every CapEx invoice regardless of dollar amount) …

Requirement evaluated: Approval bottleneck analysis: which approvers are slowest, which invoice types take longest

For your 3-person AP team processing 1,800 invoices monthly across two Sage Intacct entities, Medius addresses this requirement through its named Medius Analytics module, which is included in the vendor's modular suite. Medius's own documentation states that 'AP leaders can track bottlenecks by entity, approver, supplier, or category and take action before suppliers follow up,' directly matching your need to identify which approvers are slowest and which invoice types take longest. …

Limitations: A third-party review (research.com, 2026) notes 'limited customization options for reports, restricting tailored outputs,' which means buyers who need highly bespoke drill-down combinations beyond the pre-built dashboard views may hit constraints in report configuration. …

Requirement evaluated: Approval bottleneck analysis: which approvers are slowest, which invoice types take longest

For your 3-person AP team processing 1,800 invoices across 2 Sage Intacct entities, Sage AP Automation provides a real-time dashboard that surfaces current AP position and is documented as helping users 'identify bottlenecks and reduce risk.' At the workflow level, Sage AI identifies approval delays and escalates overdue approvals automatically, with a full audit trail logging every action with timestamps across the approval chain. Sage Intacct's native reporting engine can generate vendor-aging and approval status reports in real time, and a third-party implementation guide notes that approval turnaround time metrics can be tracked by building custom reports against Intacct's data. …

Limitations: The buyer's specific need, a pre-built report or dashboard that aggregates per-approver cycle times and segments elapsed time by invoice type, is not documented as an out-of-the-box capability; the available mechanism is current-state queue visibility plus AI-driven escalation, not historical performance analytics by a …

Requirement evaluated: The ERP integration must write back to Sage Intacct with full field fidelity: every dimension value coded at the line level (location, department, project, class, and all active custom dimensions) must post to Intacct as discrete dimension fields on the journal or AP transaction record, with no field collapsing, no memo-field workarounds, and no loss of dimensional granularity. Vendors must confirm whether their Intacct connector uses the Intacct XML API dimension framework or a reduced data model, and must identify any Intacct dimensions or custom segments their connector does not carry.

For a multi-entity SaaS company on Sage Intacct with location, department, project, class, and active custom dimensions coded at the line level, the critical issue is how Medius's Intacct connector is architected. Medius's own ERP integrations page discloses that its Sage Intacct integration is a pre-packaged solution delivered in partnership with Acuity Solutions, a UK-based Sage business partner, rather than a first-party, natively maintained Medius connector. …

Limitations: The Sage Intacct connector is partner-delivered via Acuity Solutions with no publicly documented confirmation that it carries all active custom dimensions (UDDs) as discrete Intacct dimension fields at the AP bill line level. …

Requirement evaluated: The ERP integration must write back to Sage Intacct with full field fidelity: every dimension value coded at the line level (location, department, project, class, and all active custom dimensions) must post to Intacct as discrete dimension fields on the journal or AP transaction record, with no field collapsing, no memo-field workarounds, and no loss of dimensional granularity. Vendors must confirm whether their Intacct connector uses the Intacct XML API dimension framework or a reduced data model, and must identify any Intacct dimensions or custom segments their connector does not carry.

For a multi-entity SaaS company with heavy dimensional reporting on Sage Intacct, Sage AP Automation is the ERP's own native built-in module, not a third-party connector. This eliminates the integration fidelity concern entirely: because bills are created and posted as native Intacct AP transaction records, there is no connector, no field collapsing, and no memo-field workaround possible. The module operates at pre-processing stages 1 and 2 (legitimacy and PO matching), and partially at stage 5 (dimension coding). …

Limitations: The buyer's requirement spans five dimension types (location, department, project, class, and custom dimensions), but Sage's official help documentation explicitly confirms AI/ML auto-coding for only three of those (GL account, location, department); coverage of project, class, and especially custom dimensions by the A …

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

For a multi-location services company currently keying invoices manually, Medius Capture directly addresses stage 1 of the pre-processing journey (invoice legitimacy and data extraction) through a proprietary multi-stage AI pipeline. The capture engine uses Siamese CNNs for document classification, tree-based ensembles for confidence scoring, and Markov models for line-item extraction, trained since 2016 on 2.4 billion+ invoice field data points, including over 393 million real-world human corrections on edge cases such as tax codes and cost centers. …

Limitations: The 95%+ precision benchmark is reached after two invoices per supplier, but your mix includes niche subcontractors and one-off service providers that may appear infrequently; those low-volume suppliers will take longer to accumulate enough data points to achieve high touchless rates, and the AP team will need to monit …

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 across facilities suppliers, subcontractors, utilities, and professional services vendors, Sage AP Automation's learning mechanism works as follows: when your team reviews a draft bill created by the AI and posts corrections, those corrections are sent back to the Sage Network to update the ML model for your company specifically. …

Limitations: Training occurs exclusively in the production environment, not in a sandbox, so you cannot pre-train the model on historical invoices before go-live. The model also requires consistent, repeated corrections before it applies a learning signal, meaning your team may need to correct the same vendor field multiple times b …

Requirement evaluated: The AP automation tool must perform line-item OCR and structured data extraction that produces discrete, addressable line rows from every invoice, because the buyer's cost allocation model (location, department, project, class, and custom dimensions applied at the line level) is meaningless if the system only captures header-level data. Vendor must demonstrate line-item extraction accuracy on multi-line invoices, not header-only capture, as the pre-condition for any downstream coding or matching.

For a multi-entity SaaS company on Sage Intacct with line-level dimension coding across location, department, project, class, and custom dimensions, Medius Capture addresses this requirement at Stage 1 of the pre-processing journey with dedicated line-item extraction that goes well beyond header capture. The module uses OCR, AI, and ML to extract discrete, addressable line rows from every invoice format (PDF, paper, XML, EDI), and its product page explicitly commits to 'accurately capturing information from invoice headers and line-items then automatically matching them against single or multiple POs and receivables' — the product page for healthcare and retail both state that 'Medius Invoic …

Limitations: Medius documents line-item capture as a feature that 'requires that your environment has support and functionality for line interpretation' and must be enabled per vendor in administration, meaning complex or low-quality supplier invoice layouts may still fall to human-in-the-loop correction via Capture Verify before d …

Requirement evaluated: The AP automation tool must perform line-item OCR and structured data extraction that produces discrete, addressable line rows from every invoice, because the buyer's cost allocation model (location, department, project, class, and custom dimensions applied at the line level) is meaningless if the system only captures header-level data. Vendor must demonstrate line-item extraction accuracy on multi-line invoices, not header-only capture, as the pre-condition for any downstream coding or matching.

For a multi-entity SaaS company on Intacct that codes every invoice across location, department, project, class, and custom dimensions at the line level, Sage AP Automation's native AI (the 'Automated Bill Entry' / Sage AI capability built into Sage Intacct) does perform true line-item extraction: <cite index="3-7">Sage AI correctly identifies the vendor, amount, dates, and line items</cite>, and <cite index="8-4,8-12">the 2026 R1 release added AI-powered data extraction and line-level PO matching as native capabilities</cite>. …

Limitations: The buyer's specific pain point, that their current tool auto-codes only a few header fields while they need per-line dimension coding across location, department, project, class, and custom dimensions, is not resolved by Sage AI's native extraction. …

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

For a multi-location services company with subcontractor, facilities, and professional-services POs, Medius operates at pre-processing stages 2 and 5 (PO match and cost allocation) and explicitly supports 2-way matching as a configurable match type for service-based purchases. The Medius glossary directly answers the buyer's scenario: 'Can invoice matching be tailored for service-based purchases without a goods receipt? Yes. …

Limitations: The product definition documentation confirming the 2-way matching policy is drawn from MediusFlow/D365 integration specs dated 2017-2018; configuration options for the current Sage Intacct connector should be verified with Medius directly to confirm that the 2-way match policy is available and configurable at the PO-t …

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

For a $120M multi-location services company with 55% PO-based invoices covering subcontractors, facilities, and supplies, Sage AP Automation's native matching engine operates at pre-processing stage 2 (PO match) without requiring a stage 4 receipt confirmation step. The official Sage Intacct help documentation states directly that 'Automated transaction matching supports 2-way matching of vendor invoices to purchasing transactions,' with no goods receipt required to complete the match. The mechanism works through configurable transaction definition mapping in the Purchasing module: the AP team maps a source transaction definition (a service PO) …

Limitations: The documentation specifies that a vendor invoice can match to only one source transaction at a time, meaning a single service invoice cannot span multiple open service POs in a single automated match step without posting the first match first. …

Requirement evaluated: The system must maintain an immutable, timestamped audit trail that records every change to dimension coding at the line level, every approval action and approver identity, and every edit made between initial extraction and final ERP posting. The trail must be non-editable after the fact and exportable for audit purposes, satisfying the buyer's stated requirement for an immutable audit trail across the full pre-processing journey.

For a multi-entity SaaS company on Sage Intacct coding invoices across five or more dimensions, Medius maintains a dedicated Invoice Log embedded in every invoice window that records who made changes, when, and what was changed in the coding lines, currency, and amounts across the full pre-processing journey from capture through payment. <cite index="11-1">The Invoice Log section records information about who has made changes to the invoice, when, and what has been changed in the coding lines, currency, amount, etc.</cite> Critically, this log is structurally separated from the live coding data: <cite index="13-1,13-4">all coding rows are deleted when restarting an invoice, while the process …

Limitations: Medius documentation does not explicitly state that the Invoice Log is formally non-editable by administrator-level users or publish technical proof of an append-only database architecture, so the buyer cannot independently verify the tamper-proof standard from published docs alone and should confirm this during procur …

Requirement evaluated: The system must maintain an immutable, timestamped audit trail that records every change to dimension coding at the line level, every approval action and approver identity, and every edit made between initial extraction and final ERP posting. The trail must be non-editable after the fact and exportable for audit purposes, satisfying the buyer's stated requirement for an immutable audit trail across the full pre-processing journey.

For a multi-entity SaaS company on Sage Intacct coding invoices across location, department, project, class, and custom dimensions, Sage AP Automation (native to Intacct) does maintain an audit trail that covers approval actions and bill-level changes. The official Intacct AP product page confirms 'centralized, electronic access to bills, approvals, payment status, posting details, and audit trails,' and the Sage blog confirms 'automatic audit trails are provided... …

Limitations: The documented audit trail confirms logging of approvals and changes inside posted Intacct transactions, but explicit evidence of a non-editable, exportable audit log capturing every dimension coding edit at the line level across the full pre-processing journey (draft extraction through final posting) …

Requirement evaluated: For a multi-entity SaaS company on Sage Intacct, the AP tool must support Intacct's native multi-entity and shared services architecture: invoices must be codeable to the correct entity at the line level, intercompany transactions must be handled within the AP workflow, and the integration must post to the correct subsidiary ledger in Intacct without requiring AP staff to switch between separate system instances. Vendors must clarify whether their Intacct integration supports Intacct's multi-entity shared services model or treats each entity as an isolated connection.

For a multi-entity SaaS company on Sage Intacct, Medius's connection to Intacct is not a first-party native integration: it is a pre-packaged connector delivered in partnership with Acuity Solutions, a UK-based Sage business partner. <cite index="31-5">Medius has a pre-packaged integration with Sage X3 and Intacct in partnership with Acuity Solutions.</cite> This partner-mediated architecture means the depth of multi-entity support depends on what Acuity's connector exposes, not on Medius's core platform capabilities. Medius's own integration data model uses generic dimension slots (DIMENSION1 through DIMENSION12) …

Limitations: The absence of documented evidence for Intacct's multi-entity shared services model within the Medius-Acuity connector is a material ceiling: the buyer cannot verify whether intercompany transactions are handled within the AP workflow, whether the integration posts to the correct subsidiary ledger without manual entity …

Requirement evaluated: For a multi-entity SaaS company on Sage Intacct, the AP tool must support Intacct's native multi-entity and shared services architecture: invoices must be codeable to the correct entity at the line level, intercompany transactions must be handled within the AP workflow, and the integration must post to the correct subsidiary ledger in Intacct without requiring AP staff to switch between separate system instances. Vendors must clarify whether their Intacct integration supports Intacct's multi-entity shared services model or treats each entity as an isolated connection.

For a multi-entity SaaS company on Sage Intacct, Sage AP Automation is the native AP layer inside Intacct itself, which means there is no integration gap between the AP pre-processing workflow and the ERP's multi-entity engine. The mechanism is Intacct's top-level shared environment: an AP clerk logs in once at the top level and can process bills across all entities without switching instances. …

Limitations: The native AP Automation agent's AI coding and approval workflows are less configurable than purpose-built third-party AP tools (such as Stampli or Rillion), which offer more dynamic mid-flow stakeholder routing and higher-accuracy dimension auto-coding across a full custom dimension set. …

Requirement evaluated: Virtual card program with rebate revenue; we want to shift 30%+ of spend to virtual card

For a US-based multi-location services company aiming to convert 30%+ of AP spend to virtual card, Medius delivers this through Medius Payments (their own payment module, priced separately from the core AP automation product). Once invoices are approved in the AP workflow, Medius Payments routes each payment to the optimal method: virtual card, ACH, wire, or check. For virtual card transactions, Medius issues a unique, single-use card number tied to a specific invoice and dollar amount; after the supplier processes it, the card self-destructs, closing the payment loop back to the ERP. …

Limitations: Virtual cards through Medius Payments are available for US-based businesses only, which is not a blocker for this buyer but would be relevant if international supplier payments were added later. …

Requirement evaluated: Payment reconciliation with automatic journal entries back to Sage Intacct

Because Sage AP Automation is a native Sage Intacct module rather than a third-party integration, there is no separate sync step between the payment action and the GL: the AP subledger and the general ledger are the same system. When your AP team executes a payment run (check, ACH, or virtual card), Sage Intacct records an AP payment transaction (APPYMT) that immediately closes the open bill in the AP subledger and posts the corresponding debit and credit entries to the configured cash and AP liability GL accounts in real time. …

Limitations: For the buyer's current bi-weekly check runs and monthly ACH batches, the standard native workflow requires the AP team to generate and confirm the ACH file inside Sage Intacct's Cash Management module before the payment is disbursed to the bank; this is an in-system step, not a manual re-import, but it does require a …

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

As a $120M multi-location services company operating 2 Sage Intacct entities with a third planned, you need an AP layer that can route invoices to the right entity-scoped workflow, post to the correct entity's GL, and scale to a third entity without re-implementation. Medius's own platform supports multi-entity environments through a 'company' construct with entity-scoped accounting templates, entity-aware approval routing, and virtual-company-level analytics visible from a single login, as documented in the Medius Success Portal. …

Limitations: The Sage Intacct connector is partner-delivered via Acuity Solutions, not a Medius-native integration, and its per-entity GL mapping, Intacct dimension carriage, and multi-entity field fidelity are not publicly documented; the buyer must verify these specifics with Medius and Acuity before contracting to confirm the co …

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

For this 6-location, 2-entity services company, Sage AP Automation (the AP Automation agent embedded natively inside Sage Intacct) handles dimension coding as a first-class function rather than an afterthought. When an invoice arrives by email or upload, Sage AI extracts vendor details, amounts, dates, and line items, then automatically attributes dimensions and creates a pre-populated draft bill. Sage's own product page describes the AP Automation agent as automating 'account and dimension coding' directly within the Intacct data model, covering the full set of Intacct's built-in dimensions: Location, Department, Project, Customer, Class, Vendor, Employee, and Item. …

Limitations: Sage does not publish a detailed breakdown of exactly which custom-dimension types (user-defined objects, statistical dimensions, etc.) the AI auto-codes versus which require manual selection during review; buyers with highly customized Intacct schemas should confirm with Sage that all user-defined GL dimensions are su …

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, <cite index="4-1,4-13">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.</cite> The buyer's AP team creates and issues onboarding forms in Medius Supplier Onboarding; <cite index="24 …

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: 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 that needs vendors to self-register, submit W-9/W-8 forms, enter banking details, submit invoices directly, and check payment status without calling AP, Sage AP Automation (powered by Beanworks/Quadient) does not offer this capability. Across all published primary feature documentation for the product, including the official Sage US and Canada marketplace feature pages, every listed capability is internal-team-facing: invoice ingestion, AI-assisted coding, PO matching, approval routing, and payment release. …

Limitations: Every sub-component of this requirement (new vendor registration, W-9/W-8 collection, banking detail entry, vendor-submitted invoices, and payment status inquiry) is absent from Sage AP Automation's documented feature set. …

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

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

For a $120M multi-location services company running Sage Intacct, the AP Automation module is a native, first-party capability built directly into the Sage Intacct cloud platform. Because it runs within the Sage Intacct US production environments, it falls under the same SOC 2 Type II audit scope that Sage Intacct maintains on an annual basis. Sage's official Information Security Management Program page states that Sage Intacct holds a SOC 2 Type II opinion from an independent third-party audit firm, renewed once per year, and that the controlled report is available to customers and prospective customers under NDA upon request. …

Limitations: No publicly available source explicitly lists the AP Automation module by name as a separately scoped component within the SOC 2 Type II report; coverage follows from AP Automation being native to the Sage Intacct platform, which is explicitly in scope. …