Medius vs Precoro

Requirement evaluated: Matched invoices push to NetSuite AP for payment processing (or integrate with our AP automation tool)

For a $250M technology company running NetSuite as its ERP and currently processing POs manually, Medius delivers a purpose-built, certified integration that pushes matched and approved invoices directly into NetSuite AP for payment processing. Medius holds 'Built for NetSuite' SuiteApp certification across its Procurement, AP Automation, and Pay modules, meaning the integration follows NetSuite's own platform development standards and does not require custom connectors or third-party middleware. …

Limitations: The depth of the NetSuite write-back (which specific vendor bill fields, subsidiary dimensions, and custom segments are populated) is not enumerated in publicly available documentation; buyers running a complex NetSuite OneWorld configuration with many custom segments should validate field-level mapping during a proof …

Requirement evaluated: Matched invoices push to NetSuite AP for payment processing (or integrate with our AP automation tool)

For a NetSuite shop like yours that currently manually creates AP records, Precoro's native two-way NetSuite integration handles this requirement directly. <cite index="6-2,6-3,6-4,6-5">Precoro's AI turns supplier invoices of diverse formats into structured documents, matches them to approved POs, and then automatically syncs approved transactions with NetSuite, eliminating duplicate entries.</cite> On the AP push specifically: <cite index="10-12,10-15">invoices land in NetSuite under Transactions → Payables → Enter Bills → List, and once an invoice is created in Precoro, it is sent to NetSuite automatically.</cite> The trigger is approval status: <cite index="2-12">when the document acquire …

Limitations: <cite index="2-13,2-14">Invoice field synchronization operates one-way (Precoro to NetSuite); changes made in NetSuite after the push are not transferred back into Precoro</cite>, so any post-push edits must be managed in NetSuite directly. …

Requirement evaluated: Policy compliance reporting: percentage of spend through approved channels, contract compliance rate, approval policy adherence

For a $250M technology company currently operating with 35% maverick spend and no structured procurement system, Medius addresses all three dimensions of this requirement across its combined AP Automation, Analytics, and Procurement modules. On spend-through-approved-channels: Medius captures every invoice at line-level detail and provides real-time insight into non-PO and off-contract invoices, so procurement can see exactly where spend falls outside policy and measure what proportion moves through PO-backed, contract-backed channels versus not (Medius Procurement Professionals page). …

Limitations: Full compliance reporting across all three dimensions (maverick spend percentage, contract compliance, approval adherence) is most complete when both the Medius Procurement module and the AP Automation/Analytics modules are deployed together; the Procurement module is available as part of a subscription package rather …

Requirement evaluated: Policy compliance reporting: percentage of spend through approved channels, contract compliance rate, approval policy adherence

For a technology company coming from an email/Slack approval environment with 35% maverick spend, Precoro addresses all three dimensions of this requirement through its Spend Management and Analytics suite. For approved-channel spend visibility: <cite index="21-1">the product page documents the ability to monitor actual versus planned spend across departments, projects, and suppliers, and to spot off-policy purchases, duplications, and top spending categories using prebuilt spend and performance dashboards.</cite> For contract compliance: <cite index="29-4,29-5,29-6">procurement reports help businesses ensure purchasing activities align with company policies, dashboards show whether the comp …

Limitations: Precoro's compliance reports are constructed from a custom report builder rather than delivered as a pre-packaged scorecard with a single "% of spend through approved channels" KPI out of the box; the buyer's CFO will need to configure the relevant views using the available data points and filters. …

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

For a $250M technology company moving off email-and-Slack approvals, Medius's P2P platform covers most of the required PO lifecycle stages within a single platform. Purchase requests are raised by employees, approvals are automatically routed, and POs are generated instantly inside Medius; the 'approved' stage is natively tracked. When invoices arrive, AI captures and matches them against POs and goods receipts (three-way match), advancing the PO through the 'received' and 'invoiced' stages, with every step described as auditable and synced to the ERP in real time (Medius P2P platform page). …

Limitations: For this buyer's specific requirement of tracking all five discrete stages (approved, acknowledged, received, invoiced, closed), the 'acknowledged' milestone is the material gap: Medius does not explicitly document supplier PO acknowledgment as a named, auto-promoted status in its native procurement module, and the exi …

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

For a $250M tech company currently tracking nothing beyond email-and-Slack approvals, Precoro's Purchase Orders module delivers a named, discrete status for every stage the buyer requires, all visible from the PO management list without opening individual documents. After a PO clears the approval workflow, it carries an 'Approved' status; Precoro then tracks supplier-side acknowledgment through a dedicated sending sub-status on the PO itself: 'Not Sent,' 'Sent,' 'Message Received' (supplier opened the email), and 'Confirmed' (supplier confirmed taking the order into work). …

Limitations: Supplier 'acknowledgment' is captured either via email open/confirmation tracking or through the Supplier Portal; suppliers who neither open the PO email nor use the portal will leave the PO in 'Sent' rather than 'Confirmed,' so the buyer should plan a Supplier Portal onboarding effort alongside rollout to maximize ack …

Requirement evaluated: Rate card management: contracted pricing loaded into the system so PO prices auto-validate against the agreement

For a $250M technology company trying to eliminate the 35% maverick spend problem, Medius offers two modules that work together but cover different stages. Medius Contract Management serves as a cloud-based repository for supplier agreements, and its own documentation states that 'when contract management is connected to accounts payable processes, organizations can validate supplier invoices against contract terms automatically'; however, this is invoice-level downstream validation, not upstream PO price blocking at the time of requisition creation. …

Limitations: The buyer's requirement is upstream enforcement: a PO price that exceeds the contracted rate should be caught before it is issued to the supplier. Medius's documented price control lives primarily in AP-layer three-way matching and in a Contract Management module that is both a paid add-on and focused on CLM lifecycle …

Requirement evaluated: Rate card management: contracted pricing loaded into the system so PO prices auto-validate against the agreement

This $250M tech company needs contracted pricing loaded against specific vendors so that PO line prices are automatically validated against the agreement, not just tracked. Precoro's approach assembles this capability from three intersecting mechanisms rather than a single dedicated rate-card module. First, the internal catalog stores approved items with fixed prices and SKUs; administrators can enable 'Restrict Catalog Items Editing' to lock the Price, Currency, and Unit fields so requesters cannot override contracted rates when adding catalog items to PRs or POs (from Precoro help.precoro.com/how-to-set-up-a-purchase-requisition-module). …

Limitations: Precoro has no native rate-card object that stores contracted per-item prices tied to a supplier agreement and auto-validates PO line prices against those rates at order creation; the catalog price-lock plus tolerance-rate mechanism is a workaround that requires manual catalog maintenance and does not prevent a buyer f …

Requirement evaluated: Category-based shopping with visual interface; not just a search box

This $250M technology company wants employees to browse pre-approved spend categories visually, without needing to know item names or SKUs upfront. Medius Procurement, the eProcurement module that sits alongside the core AP automation platform, addresses catalog discovery through two mechanisms. First, <cite index="22-7">the eProcurement software allows users to find what they need using a sophisticated search feature</cite>: this is search-first, exactly what the buyer is trying to move beyond. …

Limitations: The buyer's indirect spend skews heavily toward services categories (IT, facilities, professional services, marketing) that will not have punchout-enabled supplier storefronts, leaving those categories accessible only via search or free-text entry. …

Requirement evaluated: Category-based shopping with visual interface; not just a search box

This $250M tech company needs employees across four US offices and a Canadian development center to browse pre-approved spend categories visually, without knowing item names or SKUs upfront. Precoro's internal catalog module allows admins to load approved items with images, prices, and SKUs, and items can be grouped using an 'Item Groups' feature and tagged with categories via a custom drop-down field. …

Limitations: Precoro's catalog navigation is a filter-on-a-list model, not a category-tile or hierarchical browse model: employees must open a document first and then narrow a flat item list by category filter, which is materially different from the 'category-based shopping with visual interface' the buyer specified. …

Requirement evaluated: Mobile submission capability; our field team needs to submit requests from job sites

This buyer's field team needs to originate purchase requisitions from job sites, which requires mobile PR creation, not just mobile approval. Medius's documented mobile capability centers on a responsive web interface (no native app required) that allows users to access and act on documents from any HTML-compliant browser on phones or tablets. <cite index="35-1,35-2,35-3">Medius's responsive web design supports consistent use across PCs, laptops, tablets, and mobile devices with no app to download, and the mobile-friendly interface allows users to access, authorize, and comment on documents.</cite> However, every mobile-specific reference found is approval-centric: <cite index="16-1,16-5">Me …

Limitations: The material ceiling for this buyer is that Medius's mobile capability is structured around approver workflows (reviewing and approving invoices and requisitions in queue), not around field-side requisition origination. …

Requirement evaluated: Mobile submission capability; our field team needs to submit requests from job sites

Your field team members at job sites can submit purchase requisitions directly from Precoro's native iOS and Android mobile app, available on both the App Store and Google Play. <cite index="15-4,15-5,15-6">The Precoro mobile app allows users to work effectively even when away from their PC; leading actions explicitly include creating purchase requisitions, purchase orders, and receipts, as well as approving or rejecting documents with a single click.</cite> <cite index="2-2,2-3">The App Store listing confirms field users can "create purchase requests, POs, and receipts from the palm of your hand" and approve or reject documents with a single click.</cite> The mobile app also supports attach …

Limitations: Precoro's own product page notes that <cite index="1-26,1-27">the mobile procurement platform provides key features of the web version but not all web version functionalities are available yet, with active work underway to expand capabilities.</cite> There is no documented offline mode, which could be a friction point …

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

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

This buyer is moving from a zero-visibility state (35% maverick spend, email-based approvals, manual NetSuite PO entry) to a system that needs to surface spend across vendor, category, department, location, and period in real time. Precoro's Spend Management module delivers exactly this dimension set: <cite index="1-1">the platform lets users explore spending by category, supplier, department, and location to understand financial flow in depth,</cite> and <cite index="4-9">provides real-time spend tracking by department, project, or location so finance teams gain full visibility into where every dollar is going.</cite> The reporting engine is the primary mechanism: <cite index="12-24">users …

Limitations: The dashboard operates on procurement data captured inside Precoro; any spend that continues to flow outside the system (legacy email POs, direct card purchases not submitted as expense reimbursements) will remain invisible until the buyer achieves full adoption. …

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: Simple receipt confirmation workflow: designated receiver confirms delivery with quantity, condition, and date

For this $250M technology company replacing an email/Slack approval process, Precoro delivers receipt confirmation through a dedicated Receipts module with its own scoped user role. <cite index="13-32,13-33">A receipt is a document confirming delivery and listing items and their quantities; assigned people can make receipts after inspecting delivered goods.</cite> The workflow is receiver-driven, not AP-driven: <cite index="19-6">only users with Create Receipt Roles can access the 'Purchase Order is waiting for Receipt' notification letter</cite>, meaning an office manager, warehouse staff, or IT asset owner can be designated as a receiver without being given full procurement or invoice acce …

Limitations: Condition/quality status (e.g., accepted, damaged, rejected) and an explicit receiver-entered actual delivery date are not native out-of-the-box fields on the receipt form; the buyer would need to configure custom fields for receipts to capture these, adding a setup step that most buyers can handle but that is not zero …

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: Our specific rules: under $1,000 auto-approved against budget, $1,000-$10K department head, $10K-$50K VP, $50K-$100K VP + Finance, over $100K VP + Finance + CFO

This $250M technology company needs a five-tier dollar-threshold approval chain, including auto-approval under $1,000, single approver at $1K-$10K, escalating to a three-party requirement (VP + Finance + CFO) above $100K. Precoro's Approval Workflow module, configured under Configurations > Approval Workflow, directly supports this structure. Administrators define each approval step and set per-approver dollar thresholds using 'From,' 'From To,' and 'Less or equal' range conditions; for example, a department head approver can be scoped to documents from $1,000 to $10,000, a VP approver from $10,000 to $50,000, and so on, with documents below $1,000 bypassing all steps via the 'Less or equal' …

Limitations: The auto-approval for sub-$1,000 purchases is conditional on the Approval Review feature being configured so that documents falling outside any defined threshold range do not silently bypass the workflow; admins must ensure the 'Less or equal $999' condition is explicitly set and budget validation is active. …