Medius Purchase-to-Pay

Name: Medius Purchase-to-Pay
Brand: Medius

Medius Purchase-to-Pay is a procure-to-pay automation platform that connects requisitioning, invoice capture and AP automation, and supplier payments into a single audited workflow for order-to-payment processing.

Est 2001|Valuation $24.1M|Raised $3.6M

LinkedIn 32K|Website|Web traffic 261K|FTEs 750|HQ Linköping, Ostergotland County, SE

MarketsSource-to-Pay

Platform CoversIntake-to-Pay B2B Payments Invoice Data Capture & Processing

Published Oct 15, 2026

01Common complaints

- Company sizes or stages where this product is overkill - Early-stage or small companies with low invoice volume may find the suite costly and complex relative to lightweight AP tools. - Industries or use cases where competitors are comparatively stronger - Global e-invoicing regulatory coverage / compliance networks - Basware or SAP Ariba may be preferable if the primary driver is global e-invoicing compliance and network connectivity. - Technical requirements that this product may not meet without validation - If an organization requires very deep, proven native coverage for a specific ERP transaction set (e.g., highly customized NetSuite flows), validate connector scope carefully—community comments suggest possible limitations. - Budget constraints - If an organization requires public, predictable pricing and low entry costs, vendors that publish entry pricing may be easier to budget than Medius’ quote-based approach. - Specific workflows or integrations where the product may struggle - If invoices routinely span multiple POs, include ambiguous descriptions, or require non-standard matching logic, some users report OCR and complex-bill handling as a limitation (anecdotal). - Red flags in the buying process - Pricing opacity without a detailed written quote that includes: - invoice volume bands - entity counts - implementation fees - integrations - ongoing support tiers - Current limitations acknowledged by the vendor - Medius marketing materials emphasize capabilities more than limitations; explicit limitations are not prominent on the main product pages. - Features on the roadmap - Not reliably available in public sources; buyers should request roadmap commitments in writing where relevant. - Scale limitations - G2 synthesis suggests performance issues with large data volumes in some customer environments. - Security or compliance gaps - Certifications are referenced (SOC 2 Type 2, ISO 27001), but detailed privacy compliance claims (GDPR/CCPA specifics, data residency) were not clearly documented in the public pages reviewed. - API limitations or integration constraints - Community claims suggest connector scope limitations in certain ERPs; treat as a due-diligence item requiring a technical validation workshop and reference calls.

Deal disqualifiers: what constitutes a weak fit

Very small businesses seeking an out-of-the-box AP solution with minimal configuration and minimal total cost
Organizations with highly unusual invoice formats or extremely complex matching logic that require bespoke handling (risk flagged in anecdotal reviews)
Teams lacking bandwidth for training and change management

02Why they buy

- Competitive advantages supported by customer feedback (not just vendor claims) - Invoice capture accuracy and high auto-routing rates are repeatedly cited in reviews. - Configurability of workflows and approval matrices is a recurring positive in reviewer feedback. - Features and capabilities emphasized by Medius relative to some competitors - The vendor positions the product as AP-first with integrated payments capabilities within the P2P flow. - Differentiation from competitors based on reviews - Reviews often highlight configurable workflows and invoice routing, though usability may vary between end users and administrators due to training/setup experiences. - Areas where competitors have advantages - Coupa: broader procurement/sourcing suite and ecosystem. - Basware/Ariba: perceived strengths in e-invoicing compliance and global network infrastructure. - Tipalti: published entry pricing and strong global payouts/payee onboarding.

03Field reports

- Review platform snapshots (high-level) - G2 - Vendor profile shows a mid-to-high rating across a moderate number of reviews. - Pros commonly mentioned: invoice capture accuracy, configurable workflows, automation-related efficiencies. - Cons commonly mentioned: setup complexity, UI feeling dated (in some reviews), training requirements, performance issues at scale. - TrustRadius - Medius score shown as a mid-range value with a small sample of reviews. - TrustRadius lists a published starting price but does not provide full pricing transparency. - Gartner Peer Insights / Gartner Reviews - Gartner’s public vendor review landing page indicates Medius has an overall rating in the solid range and shows presence across relevant markets (including S2P / AP applications). Some parts of Gartner Peer Insights are gated. - Direct quotes (positive and negative) — with attribution - G2 (positive) - “The accuracy of capturing invoice information, the ability to auto route nearly all of the invoices for approval…” — G2 reviewer (public G2 review). - G2 (negative) - “The setup of Medius was very difficult and took longer than anticipated.” — G2 reviewer (public G2 review). - “It requires extensive training to understand the tool and use it effectively…” — G2 review excerpt (public G2 review). - Reddit (negative / cautionary, NetSuite context) - “Medius is more expensive… The system is not ready to handle extremely complex bills… and the OCR isn't great.” — anecdotal comment from an r/Netsuite discussion comparing AP automation tools. - Reddit (integration limitation claim, NetSuite context) - A user claimed procurement integration limitations (e.g., receipts/POs) beyond vendor bills/bill credits in the native integration. This is anecdotal and should be verified with Medius’ current NetSuite connector documentation and reference customers. - Common criticisms and complaints (support issues, bugs, missing features) - Implementation/setup complexity and longer-than-expected timelines (G2) - Training/learning curve (G2) - Performance concerns with larger data volumes (G2 review summary) - OCR/capture quality concerns in some real-world invoice edge cases (community anecdote) - Why customers chose this product over alternatives - Common reasons in reviews and materials include: - Stronger invoice capture and routing automation cited by reviewers - Configurability of approvals/workflows - ERP integration packages that vendors emphasize - Why some customers left for competitors (churn reasons) - Not well documented in the accessible sources. Indirect signals suggest: - Some buyers may prefer simpler mid-market tools if they find enterprise AP suites heavy to implement. - Some may prefer alternatives with broader supplier network/e-invoicing compliance (often attributed to other major vendors in market discussions). - Specific outcomes customers achieved (with metrics when available) - Vendor case study (Bohus) - Vendor-published case study reports significant annual savings and a substantial increase in touchless PO invoice processing (moving from a minority share to a high-majority share on the cited example). - Note: these are vendor-published case studies; methodology, baselines, and how savings are calculated are not independently audited in the public materials.

Case Studies

- Bohus (Furniture retailer, Norway) — Medius AP Automation - Reported context - handles several hundred thousand invoices per year - ERP: SAP - Retail footprint: dozens of stores; annual sales in the billions of NOK - Reported results (vendor-published) - Vendor reports significant annual cost savings (vendor-published) - Touchless PO invoice processing reportedly increased from a minority of invoices to a large majority; different vendor materials cite different baselines and endpoints - Critical evaluation - Savings are not independently audited in the public materials. - Framing savings as equivalent to multiple full-time salaries is a common ROI trope that can be sensitive to local labor costs and baseline process maturity. - Buyers should request: - Baseline definitions (what counted as “touchless”) - Whether savings are hard-dollar reductions or time-reallocated estimates - Implementation costs included/excluded - Additional customer stories (high level) - Medius customer stories page references touchless capture targets (e.g., a high proportion processed touchlessly in some stories), but many details require downloading gated content.

04Best fit

Company sizes: specific employee counts and revenue ranges

- Based on review platform demographics and Medius/SolutionMap positioning, a typical fit often appears to be: - Mid-market organizations up through upper mid-market and divisional enterprise units (companies that are larger than small businesses but not necessarily enterprise headquarters) - Multi-entity organizations and enterprise divisions that need stronger controls and ERP integration - Note: these ranges are inferred from positioning and review platform patterns, not an official Medius statement.

Industries and verticals where adoption is strongest (with customer examples)

Retail (example customer noted)
Manufacturing and distribution
Multi-entity services firms with ERP complexity

Roles and personas

Decision makers
- CFO, VP Finance, Controller
- Head of Procurement / VP Procurement (especially for full P2P)
- IT / ERP integration leaders (for connector scope and security)
End users
- AP managers, AP specialists
- Budget owners / department approvers
- Procurement operations

Pain points and challenges the product addresses

Manual invoice entry and approval bottlenecks
Limited spend visibility across non-PO spend
Policy compliance, duplicate invoices, and fraud risk
ERP fragmentation across multiple ERPs/entities

Qualification criteria: what constitutes a strong fit

Organizations with a meaningful invoice volume where automation is likely to materially reduce manual workload
Organizations that need configurable approvals, coding, and audit trails
Organizations willing to invest in integration and process standardization

05The pitch

What the product does (core value proposition in objective terms)

- Medius Purchase-to-Pay (P2P) is a procure-to-pay automation platform that connects requisitioning/procurement, invoice capture & AP automation, and supplier payments into a single workflow with shared data and auditability. (Medius describes it as “procurement + AP + payments” on one platform.) - Core functional blocks commonly associated with the P2P suite include: - Requisition to PO (shopping-style buying, approvals, PO creation) - Invoice to approval (invoice capture, 2/3-way matching, exceptions) - Approval to payment (check/ACH/card workflows, payment approvals) - Vendor-stated implementation speed: vendor cites a relatively short go-live timeframe (measured in weeks) for the full P2P suite, with faster timelines for AP-only deployments.

Target market and market positioning

Medius is primarily positioned for mid-market and upper mid-market organizations that prioritize shorter deployment timelines and ERP connectivity, but it also sells into larger/global enterprises (multi-entity, multi-ERP).
Analyst-style segmentation appears in Medius-published Spend Matters SolutionMap excerpts that describe a primary target segment in midmarket and upper-midmarket customers.

Get a comprehensive analysis of Medius Purchase-to-Pay including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →