Esker vs Medius

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

For a $120M multi-location services company with a 3-person AP team processing 1,800 invoices monthly across two Sage Intacct entities, Esker delivers KPI tracking through embedded, role-based dashboards built directly into its AP Automation module. As invoices move through the workflow: receipt, validation, matching, approval, and posting, the platform captures timestamped event data and surfaces it in real time without requiring manual exports or IT involvement. …

Limitations: Discount capture rate is documented in terms of flagging early payment windows and naming it as a KPI to improve, but Esker's materials do not explicitly describe a pre-configured 'capture rate percentage' widget in the way they describe process efficiency and exception rate metrics; your AP team should confirm during …

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

For a $120M multi-location services company replacing email-chain approvals with no current KPI visibility, Medius delivers these five metrics through its dedicated Medius Analytics module, which sits within the AP Automation platform and surfaces pre-defined dashboards and KPIs drawing from the invoice-to-pay workflow event database. <cite index="3-3,3-4,3-5">The module provides a full, real-time view into spend delivered through pre-defined reports, dashboards, and KPIs, including a dedicated Capture dashboard that surfaces touchless and extraction rates with drill-down to the individual supplier level.</cite> <cite index="11-13">Medius surfaces comprehensive, real-time analytics on invoic …

Limitations: <cite index="4-1,4-2">Analytics dashboards are presented from a dedicated analytics database with trend visualizations over time, but the data refresh cadence is not configurable by customers and is managed by Medius</cite>, meaning KPI views are not truly transaction-level real-time; for a team processing roughly 90 i …

Requirement evaluated: Positive pay file generation formatted for Bank of America

This $120M multi-location services company running bi-weekly check runs needs a positive pay file formatted to Bank of America's exact specification, exported as a post-payment deliverable from the AP platform. Esker Pay, Esker's payment automation module, supports check payments alongside ACH, wire, and virtual card, and the platform documents 'bank details verification and fraud detection' as a capability within its S2P payment workflow. However, that documented mechanism is supplier bank account verification at the point of onboarding, which validates that a supplier's account credentials are legitimate before payment is initiated. …

Limitations: Esker's published fraud-prevention content consistently frames the solution as supplier bank account verification and electronic payment migration, not positive pay file generation for paper check runs; this buyer should ask Esker directly whether the payment run workflow exports a configurable Bank of America-formatte …

Requirement evaluated: Positive pay file generation formatted for Bank of America

For a $120M multi-location services company running bi-weekly check runs through Bank of America, the critical question is whether Medius generates a formatted positive pay file that can be submitted directly to BoA's CashPro portal after each check run. Across four targeted searches of success.medius.com, medius.com product and payments pages, and general search terms combining 'Medius,' 'positive pay,' and 'Bank of America,' no documentation, help article, product page, or release note was found describing a positive pay file generation mechanism in any Medius module. …

Limitations: No public documentation confirms that Medius generates a bank-formatted positive pay file; the buyer should ask Medius directly whether a BoA-compatible positive pay export exists as a configured output of their check payment module, and whether it can be automated post-check-run rather than requiring a manual export f …

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/month across a diverse vendor base, Esker Synergy AI operates two complementary learning mechanisms inside its invoice capture stage. The first is passive auto-learning: each time an AP user corrects an extracted field during the validation form step, the system silently updates its extraction model so that the next invoice sharing that document structure is populated with higher accuracy without any manual intervention. …

Limitations: The teaching mechanism matches templates by document layout rather than by supplier identity, so if a vendor changes their invoice format, a new teaching rule must be created manually by a power user. …

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

For a 3-person AP team manually keying 1,800 invoices per month with no prior automation, Medius Capture addresses Stage 1 of the pre-processing journey (invoice capture and data extraction) using a multi-stage proprietary AI pipeline: Siamese CNNs for document classification, Markov models for line-item extraction, and a CNN-based coding engine called SmartFlow. …

Limitations: The 95% precision benchmark is for SmartFlow's GL coding suggestions on non-PO invoices; Medius does not publish a comparable per-supplier format accuracy lift curve or a time-to-stabilization figure for extraction fields specifically (as opposed to coding), so the buyer cannot pre-validate how quickly a new, complex s …

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

For a $120M services company processing 1,800 invoices per month across two Sage Intacct entities, 1099 compliance requires three integrated capabilities: automated vendor classification from W-9 entity type data, year-round threshold tracking aggregating payments per vendor against IRS minimums, and electronic filing with the IRS or a certified filing partner. Esker's Supplier Management module does collect W-9 documents as part of vendor onboarding verification, with one press release confirming the solution verifies 'bank details, VAT number, D-U-N-S Number, W9, insurance certificates' as part of onboarding data collection. …

Limitations: Esker captures W-9 documents during supplier onboarding but has no documented native engine for 1099 vendor classification, payment threshold aggregation, or IRS electronic filing; the buyer would need to rely entirely on Sage Intacct's native 1099 module or a separate standalone tax filing tool such as Avalara 1099 an …

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

For a $120M services company with subcontractors, utilities, and professional services vendors flowing through Sage Intacct, 1099 preparation requires automated vendor classification, cumulative threshold tracking, and direct IRS e-filing. Medius does not provide this capability. Medius's compliance architecture is built entirely around VAT, GST, and global e-invoicing mandates: its compliance page explicitly describes coverage as 'VAT and GST compliant in Tier 1 and Tier 2 countries' and focuses on European regulatory frameworks such as France's PDP mandate and UK Making Tax Digital, with no reference to US 1099 obligations, W-9 collection, TIN validation, or IRS FIRE/IRIS e-file integratio …

Limitations: Medius provides no 1099 classification, threshold tracking, or electronic filing capability: this buyer would need to rely on Sage Intacct's native 1099 module or a standalone tax filing tool (Sovos, Avalara, Track1099) entirely outside the Medius platform, negating any integrated AP-to-compliance workflow benefit.

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

For this buyer's mix of facilities, supplies, and subcontractor service POs (roughly 55% of 1,800 monthly invoices), Esker's AP automation module applies configurable matching logic that operators select at the document or workflow level. Two-way matching (PO versus invoice only) and three-way matching (PO plus goods receipt plus invoice) are both available as distinct processing modes within the platform, meaning service POs, where no warehouse receipt record exists or is meaningful, are routed through the two-way path without requiring a goods-receipt step to unlock the invoice for coding or approval. …

Limitations: Granular documentation on how Esker configures service-line-specific match fields (for example, toggling off quantity comparison on unit-less service lines, or setting separate tolerance percentages per PO category) …

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

For a $120M services company where 55% of invoices are PO-backed (including subcontractors and facilities spend with no physical goods receipt), Medius supports PO-to-invoice matching that operates on value and amount comparison rather than requiring a delivery confirmation record. When an order invoice enters the system, <cite index="29-1,29-3">it is automatically matched against the purchase order, and based on how the matching goes, the invoice receives a matching status.</cite> The key configuration mechanism for service POs is the `MatchOrderInvoiceAmount` system parameter: <cite index="28-1">administrators activate this parameter and enter the maximum permitted deviation in currency un …

Limitations: The default Medius order matching flow includes an 'Awaiting delivery' status that holds invoices when a PO has no registered delivery record in the purchasing system; for service POs, this queue must be bypassed through configuration (using value-based `MatchOrderInvoiceAmount` parameters rather than quantity/receipt …

Requirement evaluated: Sync scope: chart of accounts, departments, classes, locations, projects, vendor master, items, and custom segments

For a $250M NetSuite-based technology company needing broad master data sync, Esker delivers its NetSuite connectivity through B.Workshop, a certified integrator for Oracle NetSuite that has built pre-built integrations linking Esker with the NetSuite platform. The mechanism uses REST APIs for real-time data exchange, and Esker's Oracle integration page describes 'automatic master data synchronization' to support AP and order management automation. This covers the core AP master data layer — vendor master and chart of accounts are the documented anchor objects — and the connector is framed as a pre-built, REST-based package rather than a custom SuiteScript bundle. …

Limitations: The critical gap for this buyer is custom segments: NetSuite custom segments require explicit connector support and API permissions ('Custom Segments' and 'Custom Record Types' access on the integration role), and Esker's published NetSuite documentation does not confirm this capability — meaning the buyer may face man …

Requirement evaluated: Sync scope: chart of accounts, departments, classes, locations, projects, vendor master, items, and custom segments

For a $250M technology company running NetSuite as its ERP of record, Medius delivers its NetSuite data sync through two integrated mechanisms: the Medius Connect fully managed ERP connector and the certified 'Built for NetSuite' SuiteApp (Medius Procurement for NetSuite), which is built directly on the Oracle NetSuite SuiteCloud Platform. The Medius Connect page explicitly states that 'master data is accurately transferred from the ERP application to Medius AP Automation' for NetSuite, and the Built for NetSuite press release confirms the SuiteApp 'leverages NetSuite's integrated business system to manage supplier master data and financial account details,' covering vendor master and chart …

Limitations: Custom segments, which this buyer may use for project tagging or additional cost dimensions in NetSuite, are not explicitly documented in any Medius-published source found; the buyer should require Medius to confirm custom segment read scope in writing before contracting. …

Requirement evaluated: PO status tracking: from approved through acknowledged, received, invoiced, and closed

For a $250M technology company currently tracking POs manually in NetSuite with 35% maverick spend, Esker's Procurement module within its Source-to-Pay suite provides end-to-end PO lifecycle visibility. Once a requisition is approved and a PO is issued, Esker centrally tracks every transaction from request through receipt of goods or services, covering the approved, acknowledged (buyer can confirm approvals received and place the order), received (goods receipt recorded and matched), invoiced, and closed stages. …

Limitations: Esker's documentation describes the full lifecycle at a process level but does not enumerate every discrete status label (e.g., a formal 'closed' status distinct from 'paid') in publicly available product pages; buyers should confirm exact status taxonomy and any configurable status names during a demo. …

Requirement evaluated: PO status tracking: from approved through acknowledged, received, invoiced, and closed

For a $250M technology company moving off email/Slack approvals, Medius covers the PO lifecycle through its combined Medius Procurement and Medius AP Automation modules, which together form the P2P suite. <cite index="26-8">The P2P system automates and connects every step, including approvals, purchase orders, goods receipt, invoice capture, and payment.</cite> On the upstream side, <cite index="10-32">Medius automates buying processes, including workflow approvals and generating POs for automatic distribution.</cite> For the downstream invoiced-to-closed transition, <cite index="12-4">the ability to automatically match invoice line details against purchase orders, goods receipts, and/or con …

Limitations: Medius's documented evidence for discrete PO status stages centers on the AP-side transitions (goods receipt matching, invoice matching, payment); the "acknowledged" stage as a named, supplier-driven PO status transition is not explicitly documented in publicly accessible materials. …

Requirement evaluated: Services catalog: pre-defined service offerings from preferred vendors (e.g., standard consulting day rates)

For a technology company currently buying consulting and professional services through ad-hoc email/Slack requests with no catalog enforcement, Esker's Procurement module (part of its Source-to-Pay suite) provides an internal hosted catalog within its guided buying experience. <cite index="1-1,1-2">Esker users are granted access to products from preferred suppliers, allowing purchases to align with procurement policies, and requesters select items they want from a catalog of approved items.</cite> Admins can <cite index="16-5">create an internal e-commerce-like web store by broadcasting hosted catalogs or giving access to suppliers' online catalogs</cite>, and <cite index="16-1">control buyi …

Limitations: The critical buyer use case, pre-loading standard consulting day rates as structured service catalog entries selectable by end-users (e.g., 'Senior Consultant Day Rate: $2,400/day, Preferred Vendor: Accenture'), is not explicitly documented in any Esker product or help content found; all catalog examples reference gene …

Requirement evaluated: Services catalog: pre-defined service offerings from preferred vendors (e.g., standard consulting day rates)

For a $250M technology company dealing with 35% maverick spend and no formal catalog discipline, Medius Procurement delivers an internal catalog mechanism that directly addresses this requirement. Administrators load approved goods and services items into an internal catalog with negotiated pricing tied to preferred vendors; end users then search and browse that catalog using a consumer-style shopping experience to create requisitions rather than free-texting requests. …

Limitations: The Medius Procurement module is a separately priced add-on; the core AP automation product in the fact sheet does not include catalog buying. Specific documentation on time-and-materials billing units (e.g., per-day, per-hour unit-of-measure configuration for service line types) …

Requirement evaluated: Mobile approval with full invoice image view; approvers must be able to act from their phone in under 30 seconds

For a 3-person AP team at a $120M services company routing 1,800 invoices per month for approval across 6 office locations, Esker's dedicated mobile app, Esker Anywhere, directly addresses this requirement. Approvers receive instant push notifications of pending invoices, open the app on their Apple or Android device, view the full invoice image as received by the accounting department, review key invoice data and prior approvers' comments, then approve, hold, or return the invoice; all in a single, purpose-built mobile interface available 24/7. …

Limitations: No published data confirms a specific 'under 30 seconds' benchmark; the speed claim depends on network connectivity and how quickly each approver can load and review the invoice image on their device. …

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: <cite index="33-15">setting this to 'No' means that a person who has reviewed a coding row can never approve the same row.</cite> 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: Native, pre-built, bidirectional integration with Sage Intacct (not middleware-dependent)

Your company runs two ERP entities in Sage Intacct, so the integration mechanism must connect directly to Sage Intacct's Web Services API and carry vendor master, GL codes, dimensions, and payment status bidirectionally. Esker does offer pre-built, native Sage ERP connectors through its Connectivity Suite, but the connectors documented on Esker's own Sage integration page cover Sage X3, Sage FRP 1000, and Sage 100 only. Sage Intacct is not named on that page, and Esker does not appear in the Sage Intacct Marketplace AP Automation category, where certified Sage Intacct connectors from vendors such as Stampli, Tipalti, and BILL are listed. One published Esker case study (People's Care) …

Limitations: Esker's pre-built Sage connectivity is documented exclusively for Sage X3, Sage FRP 1000, and Sage 100. For a buyer whose books of record live in Sage Intacct, no native connector is evidenced, meaning any Esker-to-Intacct data flow would require a custom API build or third-party middleware, directly contradicting the …

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: SOC 2 Type II certification (current, not in-progress)

For a $120M services company requiring a current SOC 2 Type II report before deploying AP automation, the publicly documented picture for Esker is materially incomplete. Esker's primary platform-wide certifications are ISO 27001 (for its Information Security Management System, renewed via A-lign) and SOC 1 Type 2 under SSAE 18 and ISAE 3402, which validate internal control processes for on-demand services. Esker's own security datasheet confirms that SOC 2 Type II examination was completed in 2020, but scoped only to the Collections Management solution, not to the AP automation module. Esker's customer-confidence page (updated March 2026) …

Limitations: The buyer's requirement is a current SOC 2 Type II report, and the most recent public evidence shows Esker's SOC 2 Type II scope is limited to the Collections Management module as of 2020; the AP platform's documented certifications are ISO 27001 and SOC 1 Type 2 (SSAE 18), which do not satisfy a SOC 2 Type II requirem …

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 for the platform

For a $250M technology company whose CFO needs audit-ready compliance documentation, Esker holds both SOC 2 Type 2 and SOC 1 Type 2 attestations (issued under SSAE 18 and ISAE 3402) covering its on-demand cloud automation platform, as documented in Esker's published CIO security ebook and its compliance software page. The platform also carries ISO 27001:2022 certification, renewed annually by an independent third-party auditor, as confirmed in Esker's 2024 Impact Report. …

Limitations: Esker does not publish the SOC 2 Type 2 report publicly; per standard industry practice the detailed report is available to customers and prospects under NDA through the account team, so the buyer should request it during due diligence and confirm the current report vintage and Trust Services Criteria in scope before c …

Requirement evaluated: SOC 2 Type II certification for the platform

For a $250M technology company evaluating Medius as its first formal procurement platform, SOC 2 Type II compliance is directly confirmed. Medius maintains an annual SOC 2 Type 2 report alongside SOC 1 Type 2, SOC 3, and ISO 27001:2022 certifications, all accessible through its dedicated Trust Center at trust.medius.com, powered by SafeBase. The SOC 2 Type 2 report is listed as a private document, meaning your security or IT team can request access (typically via a digital NDA workflow through the Trust Center portal) and receive the full attestation report covering the audit period. …

Limitations: Medius does not publicly specify which product modules are within the SOC 2 Type II audit scope; the buyer should confirm during due diligence that the specific modules they will use (particularly any T&E or sourcing components from post-acquisition integrations) …

Requirement evaluated: Supplier performance scorecards: on-time delivery rate, quality issues, invoice accuracy, responsiveness

For a $250M technology company with both indirect and direct spend portfolios, Esker's Supplier Management module (part of its Source-to-Pay suite) provides a centralized performance dashboard where procurement and AP teams can track supplier KPIs in real time. The platform explicitly supports tracking of predefined performance metrics against compliance and operational thresholds, and its AI-powered inquiry management feature specifically enables teams to monitor response times and inquiry trends at the supplier level: the product page states users can 'Track inquiry trends, monitor response times and gain actionable insights to drive continuous improvement.' Invoice accuracy is reinforced …

Limitations: The mechanistic evidence for on-time delivery rate (auto-calculated from PO committed date vs. actual goods receipt date) and quality issue tracking (discrete defect counts from goods receipt inspections) …

Requirement evaluated: Centralized supplier database with self-service onboarding portal: vendors enter their own info, upload W-9, insurance, banking

For a $250M technology company currently managing 800+ vendors through email and manual NetSuite entry, Medius delivers this requirement through two integrated, named modules: Medius Supplier Onboarding and the Medius Supplier Portal. The flow is invitation-driven: your team creates and issues onboarding forms inside Medius Supplier Onboarding, and those forms are made available in the Medius Supplier Portal for each vendor to access and complete independently. Suppliers register, record, and update their own details in a single cloud-based location — including banking and contact information — without requiring your AP or ops team to key data on their behalf. …

Limitations: Medius's public documentation confirms banking/payment detail self-service and general regulatory document collection, but does not explicitly name W-9 collection or insurance certificate tracking with expiration alerts as discrete, labeled features — buyers should verify these specific US tax and insurance document wo …

Requirement evaluated: Automatic match-and-pass for invoices within tolerance, reducing AP workload to exceptions-only review

For a $250M technology company currently relying on manual AP and email approvals, Esker's AP Automation module delivers the exact exceptions-only workflow the buyer needs. When a PO-linked invoice arrives (via email, EDI, supplier portal, or mail), Esker's AI extracts header and line-item data and immediately runs a 2-way or 3-way match against the corresponding PO and goods receipt. …

Limitations: Esker's documentation confirms tolerance management for retail scenarios (price/quantity variance detection), but the specific configuration mechanism for defining numeric tolerance thresholds (e.g., a configurable percentage band per vendor or line type) …

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

For a $250M technology company coming from a fully manual, email-based process, Medius delivers automated three-way matching as a core capability of its AP Automation module. When an invoice arrives, Medius's AI-powered capture extracts line-item data (vendor name, PO number, quantities, unit prices) and automatically connects it to the corresponding purchase order and goods receipt (GDR) already synced from NetSuite. …

Limitations: Medius relies on goods receipt data being registered and synced from NetSuite into Medius for the third leg of the match; since this buyer currently has no receiving process or system discipline, the ops team will need to establish a goods receipt confirmation workflow in NetSuite before three-way matching can operate …

Requirement evaluated: Policy engine that prevents purchasing from non-approved vendors in categories where preferred vendors exist

For a company dealing with 35% maverick spend and 800+ active vendors, Esker's Procurement module addresses this requirement at the requisition creation stage, before any PO reaches NetSuite. When a requester initiates a purchase, <cite index="28-4">the solution enforces internal policies by enabling every spend request to get the required authorization and allowing users to shop from a list of items from approved vendors.</cite> Practically, <cite index="21-6,21-7">Esker users are granted access to products from preferred suppliers, keeping purchases in line with company procurement policies, and requesters select items from a catalog of approved items.</cite> This catalog-based control is …

Limitations: Public documentation confirms the catalog and approved-vendor restriction model but does not explicitly detail whether the policy engine supports a configurable hard block (requester cannot proceed) …

Requirement evaluated: Complete audit trail meeting SOX-adjacent control requirements for our IPO preparation

For a company preparing for an IPO, Medius provides a centralized, AP-side audit trail that captures every action taken across the invoice-to-pay lifecycle. <cite index="16-22,16-23">AP automation maintains compliance by creating well-organized workflows and maintaining clear audit trails, including generating detailed audit trails for every action taken on an invoice and enforcing approval hierarchies and role-based access controls.</cite> <cite index="0acd0c8e-5ffc-4d74-be76-7c3e3af721a7">Every invoice is automatically archived, ensuring accuracy, traceability, and audit confidence at any time.</cite> On the controls side, <cite index="7-1,7-3">automated vendor onboarding workflows and seg …

Limitations: Medius's audit trail is strongest on the AP side (invoice receipt, matching, approval, payment); upstream procurement controls (purchase requisition creation and pre-PO approval) …

Requirement evaluated: Tail spend analysis: identify high-transaction-count, low-dollar vendors for consolidation

For a company like yours trying to collapse 800+ active vendors to a defensible subset, Esker's e-procurement module tracks every transaction from requisition to payment and surfaces that data through customizable KPI dashboards. The platform documents that its 'granular data lets you search for spending patterns to identify potential savings,' and its supplier management module adds a supplier-level dashboard showing performance and relationship data. …

Limitations: Esker's analytics are documented primarily as process efficiency and budget compliance tools, not as a dedicated tail spend identification engine. Your ops team would likely need to export transaction-level spend data and construct the transaction-count-vs.-dollar-volume analysis in a separate tool (e.g., Excel or a BI …

Requirement evaluated: Spend dashboards: real-time spend by vendor, category, department, location, and period

For a $250M technology company currently flying blind on 35% of its spend, Medius delivers this requirement through its dedicated Medius Analytics module, a separately licensed product that sits alongside AP Automation and Procurement. <cite index="32-1">The module provides "a full, real-time view into how money is spent across your organization delivered through pre-defined reports, dashboards and KPIs,"</cite> with named sub-sections in the product documentation covering AP Insights, Invoice Process Insights, User Insights, and a Procurement Dashboard. …

Limitations: Some dashboard gadgets in Medius Spend Management rely on a scheduled ETL job rather than a live data feed, meaning <cite index="13-4">"displayed data is based on ETL reporting data"</cite> for those panels, which introduces a batch-refresh lag rather than truly instantaneous data. …