Workday Sourcing vs Esker vs Medius for Procurement & P2P

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. The Oracle NetSuite SuiteApp documentation for Medius Procurement explicitly describes 'internal catalogs with select goods and services setup for your organization' alongside 'punchout to supplier catalogs with negotiated item and pricing,' meaning a standard consulting day rate can be configured as a named catalog item at a contracted unit price, selected by the requester, and routed through a pre-defined approval workflow before a PO is auto-generated. This catalog-gated buying mechanism sits at the front of Medius's P2P process: it operates before requisition submission, so all spend is channeled through approved items and pricing before any PO is created. The capability lives in the Medius Procurement module, which is licensed separately from the core AP automation product.

Your company's challenge, replacing email/Slack approvals and curbing 35% maverick spend with enforced preferred-vendor service selections, requires an internal catalog where admins pre-load service line items (e.g., 'consulting day rate, Vendor X, $2,500/day') that end users pick rather than free-typing. That catalog and guided-buying mechanism lives in Workday Procurement, not in Workday Strategic Sourcing. Workday Procurement explicitly documents an Item Master catalog with configurable units of measure (including time-based UOMs), pre-set pricing that auto-populates when a user selects an item, preferred-item surfacing during requisition search, and an 'Intelligent Intake' layer that routes users to approved channels from internal catalogs and integrated marketplaces. Workday Strategic Sourcing, the evaluated product, is scoped to upstream source-to-contract work: building and running RFPs, RFIs, and RFQs, managing supplier responses, and executing contracts. Its own datasheet describes the product as a tool to 'build and launch RFPs, RFIs, and RFQs quickly' and to 'streamline the source-to-contract process,' with no documented internal services catalog or end-user guided buying interface. Accessing the services catalog mechanism requires separately licensing Workday Procurement, a distinct Workday product.

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. 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. Admins can create an internal e-commerce-like web store by broadcasting hosted catalogs or giving access to suppliers' online catalogs, and control buying from only approved vendors and preferred catalog product listings. Esker's own procurement metrics content confirms the platform supports hosted catalogs for goods and services with the greatest order volumes where users can easily create new requisitions. The catalog is tied to the requisition-to-PO workflow: a requester selects a catalog item, the system auto-routes the requisition through an approval workflow, and a PO is generated. However, no Esker documentation found explicitly describes configuring service-specific line items with time-based units (e.g., per day, per hour) or consulting day rates as a distinct catalog entry type. The catalog mechanism is described consistently as covering 'goods and services' but the line-item unit configuration for T&M-style services is not documented.

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. However, Esker's published documentation does not enumerate whether departments, classes, locations, projects, items, and — most critically — custom segments are included in the NetSuite sync scope for its procurement module. The field-level mapping for the buyer's full 8-object list (chart of accounts, departments, classes, locations, projects, vendor master, items, custom segments) is not documented in any publicly accessible Esker help center article or data sheet, and independent user validation of Esker's NetSuite integration specifically is sparse compared to its SAP coverage.

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 of accounts. The Medius blog on NetSuite integration further confirms that 'vendor master data remains synchronized automatically' and that Medius 'maintains financial accuracy across approval hierarchies and reporting frameworks' in NetSuite environments, consistent with syncing standard organizational dimensions (departments, classes, locations). However, Medius's publicly accessible documentation does not enumerate a full object-by-object sync scope for the NetSuite connector, and no Medius-authored source explicitly confirms sync of NetSuite custom segments, which is the most buyer-critical item not covered by the SuiteCloud standard object set.

For a $250M tech company running NetSuite as its ERP, the critical question is whether Workday Strategic Sourcing can pull and sync NetSuite's chart of accounts, departments, classes, locations, projects, vendor master, items, and custom segments so that procurement coders never have to re-key or maintain a parallel master data set. Workday's own product pages state that Workday Strategic Sourcing 'integrates with any finance or procurement system,' but no official Workday help center article, technical datasheet, or published connector specification was found that documents a NetSuite integration at the object level this buyer requires. The product's documented integration depth is with Workday Financial Management and Workday Procurement, where a shared data model exists natively. For NetSuite specifically, the only Workday-ecosystem NetSuite connector found in the Workday Marketplace is scoped to Workday Adaptive Planning (not Strategic Sourcing), and the Celigo Workday-NetSuite prebuilt template covers HR employee records only, not procurement master data.

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. Specifically, Esker's AP module performs seamless three-way matching of purchase orders, receipts, and invoices with full audit trails, and the platform holds invoices in a 'waiting for goods receipt' state until a GRN is created, at which point the invoice automatically re-enters the validation queue. Suppliers also receive 24/7 self-service access to invoice payment status, closing the loop on the invoiced and closed stages.

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. The P2P system automates and connects every step, including approvals, purchase orders, goods receipt, invoice capture, and payment. On the upstream side, Medius automates buying processes, including workflow approvals and generating POs for automatic distribution. For the downstream invoiced-to-closed transition, the ability to automatically match invoice line details against purchase orders, goods receipts, and/or contracts allows teams to resolve discrepancies in invoices, POs, and receivables, covering the received and invoiced stages. Supplier-facing visibility is available through the Medius Supplier Portal, which allows buyers and suppliers to track orders, raise concerns, and communicate, ensuring both parties are on the same page throughout the vendor lifecycle; the portal's documentation includes a dedicated "Orders" section for suppliers. For spend visibility, configurable dashboards provide a live view of purchasing activity, invoice status, and payment timing. However, the evidence for a buyer-facing PO tracker showing all five stages (approved, acknowledged, received, invoiced, closed) as discrete, named status labels on a single PO record is not explicitly documented: the "acknowledged" stage in particular, meaning a supplier-driven confirmation of PO receipt that advances a named PO status field, is only obliquely supported by the Supplier Portal's Orders section and the P2P FAQ's description of the workflow as including "order placement with suppliers, despatch, acknowledging receipt of goods and services, and processing of invoices." The system's primary design emphasis is on AP automation and invoice-status visibility rather than a procurement-side PO status state machine.

This $250M technology company on NetSuite needs a tool that tracks a PO from the moment it is approved all the way through supplier acknowledgment, goods or services receipt, invoicing, and final closure. Workday Strategic Sourcing's documented scope ends well before that chain begins: the product covers source-to-contract activities, specifically intake request management, RFP/RFI/RFQ events, reverse auctions, supplier negotiations, and contract lifecycle management. Its own product page states it 'streamlines the source-to-contract process,' and its datasheet and industry use-case pages list no capability for PO issuance status, supplier acknowledgment of issued POs, goods receipt confirmation, invoice matching, or PO closure. The post-award PO execution stages the buyer requires are handled by the separate Workday Procurement module within Workday Financial Management, which presupposes Workday Financials as the ERP; because this buyer runs NetSuite, even that adjacent module is not in scope here.