Coupa vs Procurify

Requirement evaluated: Segregation of duties enforcement: requester ≠ approver ≠ receiver ≠ payment processor

For a technology company moving from email-and-Slack approvals to a structured P2P system, Coupa addresses the four-way segregation requirement through a combination of predefined roles and configurable approval controls. Coupa's role-based access control model includes distinct predefined roles: Requester (creates purchase requisitions), Approver (approves or rejects requisitions and invoices), and Receiver (confirms goods or services received), each assignable separately via user profiles. …

Limitations: Within Coupa, role permissions are additive rather than mutually exclusive, meaning SOD enforcement for the requester-approver-receiver triad requires careful administrative configuration and ongoing access reviews - a real-world case study found enterprises needing consultant-led role redesign post-deployment to close …

Requirement evaluated: Segregation of duties enforcement: requester ≠ approver ≠ receiver ≠ payment processor

For a $250M technology company moving from ad-hoc Slack/email approvals to a structured procure-to-pay system, Procurify enforces segregation of duties through a combination of distinct, non-overlapping role definitions and configurable self-approval controls. The platform defines five separate functional roles: Requester (submits purchase requests), Approver (reviews and approves or denies requests), Purchaser (creates POs from approved items), Receiver (marks items as passed or failed in the Receive module against the PO), and Accounts Payable (creates bills, processes payments, and reconciles). …

Limitations: Self-approval prevention is a global domain toggle, not a per-user or per-workflow setting, meaning it cannot be selectively disabled for certain departments or spend categories while left active for others. …

Requirement evaluated: The tool must function purely as a procurement enforcer and not require the buyer to rebuild, maintain, or duplicate budget structures inside the procurement platform itself. Budgets are authored exclusively in Workday Adaptive Planning, and the vendor's value proposition must be enforcement fidelity against externally composed budgets, not a competing budget-authoring workflow that would create a second source of truth.

For a buyer running budgets in Workday Adaptive Planning and enforcing them at requisition, Coupa's mechanism works as follows: budget values authored in Adaptive are pushed into Coupa's native Budget module via a documented REST API (`/api/budget_lines`) or a flat-file CSV SFTP import (the Budget Line Import and Budget Line Adjustment Import loaders). Budget lines can be configured by period, amount, cost center, location, or any other accounting code, and when a user creates a new requisition, a specific budget line is assigned to each item; lines are composed of a period, segment values, and an amount, and can be created through the UI or a bulk load. …

Limitations: The buyer requires a pure enforcer that does not require maintaining budget structures inside the procurement platform; Coupa's model requires pre-configuring budget periods and COA segment mappings natively in Coupa's UI before any API/CSV import can populate amounts, creating exactly the second source of truth the bu …

Requirement evaluated: The tool must function purely as a procurement enforcer and not require the buyer to rebuild, maintain, or duplicate budget structures inside the procurement platform itself. Budgets are authored exclusively in Workday Adaptive Planning, and the vendor's value proposition must be enforcement fidelity against externally composed budgets, not a competing budget-authoring workflow that would create a second source of truth.

This buyer distributes Adaptive Planning budgets to department owners and needs Procurify to act purely as an enforcement gate, not a budget authoring environment. Procurify does support budget import via CSV flat-file upload, allowing dollar amounts mapped to account codes, departments, locations, and date ranges to be loaded into the platform without using Procurify's native budget-building UI. …

Limitations: The buyer specifically requires no duplication of budget structures inside the procurement platform, but Procurify requires its own chart of accounts and department hierarchy to be kept current before any budget import will process; this is a structural maintenance burden that creates a second source of truth. …

Requirement evaluated: The procurement tool must import approved budgets directly from Workday Adaptive Planning on a scheduled or on-demand basis, mapping them to Sage Intacct dimensions and department structures without requiring manual re-entry. This integration is the foundation of enforcement: if the imported budget does not reflect the Adaptive-composed version with full dimensional fidelity, every downstream control is operating on stale or incomplete data.

For a buyer running budgets in Workday Adaptive Planning and enforcing them in Coupa against Sage Intacct dimensions, Coupa provides two documented ingestion mechanisms: a Budget Line Import via CSV flat file deposited to an SFTP path (./Incoming/BudgetLines/) and a Budget Lines REST API that accepts POST calls keyed on budget segment and period. Coupa supports budgeting on any number of COA segments, and budget lines can be loaded or adjusted through the UI, a CSV file, or the APIs. …

Limitations: There is no native, scheduled Adaptive Planning-to-Coupa budget connector; the buyer must build or procure middleware (Boomi, MuleSoft, Workato, etc.) to automate the sync, which introduces implementation risk and a potential staleness window that directly undermines the dimensional fidelity the buyer identifies as the …

Requirement evaluated: The procurement tool must import approved budgets directly from Workday Adaptive Planning on a scheduled or on-demand basis, mapping them to Sage Intacct dimensions and department structures without requiring manual re-entry. This integration is the foundation of enforcement: if the imported budget does not reflect the Adaptive-composed version with full dimensional fidelity, every downstream control is operating on stale or incomplete data.

This buyer composes budgets in Workday Adaptive Planning and needs them imported directly into Procurify on a scheduled or on-demand basis, mapped to Sage Intacct dimensions, without manual re-entry. Procurify does support budget import via CSV file upload: the import article outlines how to load budget data into Procurify; the template is for uploading a budget that commences immediately after import, and Account Codes must be pre-imported before budgets can be loaded. The import maps to Location, Department, and Account Code fields, and Procurify uses 'Location' and 'Department' as labels, though custom organizational categories are supported. …

Limitations: Procurify has no native, scheduled integration with Workday Adaptive Planning; budget data from Adaptive must be manually exported as a CSV and re-uploaded into Procurify, directly violating the buyer's requirement for automated dimensional fidelity. …

Requirement evaluated: The system must support configurable approval routing for requisitions that exceed a soft-stop threshold, routing the override request to a designated budget owner or finance approver for the relevant department or dimension before the commitment proceeds. This is implied by the soft-stop model the buyer described: a soft stop without a structured approval path is just a dismissible warning, not a control.

For a mid-market buyer whose Adaptive Planning budgets are imported into Coupa as budget lines, Coupa closes the soft-stop approval gap through two interlocking native mechanisms. First, each budget line carries an 'Owner Is Approver' flag that can be set to trigger routing only when the budget is exceeded, meaning the named budget owner is inserted into the requisition approval chain as a mandatory approver at the point of submission — not as a post-hoc notification. …

Limitations: Dimension-aware dynamic resolution of the budget owner depends on the 'Owner Is Approver' flag being correctly populated on each imported budget line — if the Adaptive Planning-to-Coupa budget import does not carry that owner assignment per department or cost center, the escalation chain must be manually configured per …

Requirement evaluated: The system must support configurable approval routing for requisitions that exceed a soft-stop threshold, routing the override request to a designated budget owner or finance approver for the relevant department or dimension before the commitment proceeds. This is implied by the soft-stop model the buyer described: a soft stop without a structured approval path is just a dismissible warning, not a control.

For a mid-market Sage Intacct buyer that needs a soft stop to trigger a mandatory escalation to a department budget owner rather than a dismissible warning, Procurify's Approval Routing Groups deliver most of the structural pieces but have a documented gap in the budget-overage-to-escalation link. The Approval Routing system is the core approval mechanism in Procurify, routing requests to the appropriate individual based on team hierarchy and the approval thresholds configured. …

Limitations: The native budget overage mechanism does not automatically re-route a requisition to a designated budget owner or finance approver when the budget threshold is crossed; the documented workaround requires a manually toggled custom field, which breaks the automatic, dimension-aware escalation the buyer's soft-stop model …

Requirement evaluated: Budget enforcement must operate at the intersection of multiple Sage Intacct dimensions simultaneously (for example, department plus project plus location) so that a requisition cannot circumvent a departmental limit by coding to an unrestricted dimension combination. The buyer stated enforcement must work 'by dimension and department,' implying multi-dimensional budget pools rather than flat cost-center-only controls.

For a mid-market company using Sage Intacct dimensions and budgets built in Adaptive Planning, Coupa enforces multi-dimensional budget pools at the requisition stage through its account-segment architecture. Administrators choose which segments to budget on when creating budget periods; they can budget on a full accounting string (for example, Cost Center-GL-Expense Type) or on partial segments of the string. Budget lines can be configured and defined by period, amount, cost center, location, or any other accounting code, and when a user creates a new requisition, a specific budget line is assigned to each requested item. …

Limitations: Coupa budgets only reflect transactions that happen within Coupa (POs, invoices, expense reports); any spend that bypasses Coupa and hits Sage Intacct directly requires a manual budget-amount reduction to keep remaining balances accurate. Additionally, Sage Intacct dimensions (department, project, location) …

Requirement evaluated: Budget enforcement must operate at the intersection of multiple Sage Intacct dimensions simultaneously (for example, department plus project plus location) so that a requisition cannot circumvent a departmental limit by coding to an unrestricted dimension combination. The buyer stated enforcement must work 'by dimension and department,' implying multi-dimensional budget pools rather than flat cost-center-only controls.

For a buyer on Sage Intacct that needs budget enforcement at the intersection of multiple dimensions simultaneously, Procurify enforces budgets across three native organizational axes: Location, Department, and Account Code. Budget pools are defined by combining these dimensions (for example, a single pool covering the Marketing department across specific account codes at a given location), and the system can block approvals when a budget ceiling is hit: requests cannot be approved if a budget is exceeded and Allow Budget Overage is disabled. …

Limitations: Procurify's enforcement pool covers up to three axes (Location, Department, Account Code) simultaneously, but it does not natively map to an arbitrary combination of Sage Intacct dimensions such as a standalone Project dimension; a requester who codes a requisition to a different account code that sits under a separate …

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

For a technology company moving from ad hoc Slack/email approvals to a policy-enforced procurement system, Coupa's Approval Chains framework is the direct mechanism. Administrators configure chains on requisitions by setting dollar-amount conditions, priority order, and individual or group approvers: the five-tier matrix (auto-approve under $1K, department head at $1K-$10K, VP at $10K-$50K, VP+Finance at $50K-$100K, and VP+Finance+CFO above $100K) maps directly to this framework. The platform's 'Parallel Approvals' feature, explicitly documented in the Workflows and Approvals section of compass.coupa.com, handles the joint-approval tiers ($50K-$100K and $100K+) …

Limitations: Configuration of these chains requires an implementation setup effort; the chains are rule-driven but not self-configuring, so the buyer's IT or implementation team must translate the five-tier matrix into Coupa's approval chain definitions during onboarding. …

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

For a technology company moving from email-and-Slack approvals to a structured five-tier policy, Procurify's Approval Routing module handles the full requirement directly. Admins configure approval groups under Settings > Manage Approval Routing, assigning each approver (or role-holder) a dollar threshold; thresholds define each approver's approval limit, so a Level 1 approver set to $999.99 handles sub-$1,000 requests, while a Level 2 approver set to $0 catches everything above that ceiling. When a request exceeds an approver's threshold it automatically requires the approval of a higher-level approver. …

Limitations: Approval Pools, the feature that routes a request to all designated approvers within a level simultaneously, uses first-responder logic: the system registers the very first action it receives and disregards subsequent responses. …

Requirement evaluated: Every soft-stop override must be captured in a persistent, tamper-evident audit trail that records the requester's identity, the budget dimension breached, the overage amount at time of override, and any approver who authorized the exception. The buyer specifically cited override audit trails as a requirement, and this log must be queryable for compliance review without manual reconstruction.

For a mid-market company trying to enforce budget at requisition time and audit every soft-stop override, Coupa assembles the required evidence across several linked components rather than a single pre-built log. When a requisition breaches a budget line, Coupa can be configured to require a justification note and route the document to a budget-exception approver: the platform is designed to avoid spend exceeding authorized thresholds and provide visibility to the budget owner in the case of justifiable exceptions for exceeding budget in some required scenarios. …

Limitations: No publicly documented, pre-built 'Budget Override Audit Log' report surfaces the overage delta and budget dimension as discrete fields in a single tamper-evident artifact; a compliance reviewer must join the Approvals API records, Budget Line data, and requisition history to reconstruct the four-field log this buyer r …

Requirement evaluated: Every soft-stop override must be captured in a persistent, tamper-evident audit trail that records the requester's identity, the budget dimension breached, the overage amount at time of override, and any approver who authorized the exception. The buyer specifically cited override audit trails as a requirement, and this log must be queryable for compliance review without manual reconstruction.

For a mid-market buyer on Sage Intacct that needs a tamper-evident, dimension-tagged override log for compliance review, Procurify's mechanism works as follows. When the Budget Overage feature is enabled, an approver who attempts to approve an over-budget order request sees a prompt: 'There is insufficient budget to approve this order. Do you want to approve it anyway?' — confirming the soft-stop trigger exists at the requisition stage. When the allowed budget overage feature is enabled, order requests can be approved even if they exceed the budget, and attempting to approve an over-budget request generates the warning 'There is insufficient budget to approve this order. …

Limitations: The audit log is embedded at the bottom of each individual order request and does not surface as a standalone, filterable compliance report aggregating override events by budget dimension, overage amount, or department — meaning a compliance reviewer must open individual records or manually reconstruct a cross-request …

Requirement evaluated: Automatic PO closure when fully received and invoiced, with alerts for POs open longer than 90 days

For a $250M technology company currently running all purchasing through email and Slack approvals, Coupa addresses both parts of this requirement but with an important gap on the aging-alert side. On automatic PO closure: Coupa's procurement module tracks PO status through its full procure-to-pay lifecycle and documents a 'Closed' status defined as the PO being received and then closed, either manually or automatically within Coupa (IQVIA/RFS supplier guides, sourced from Coupa's own status definitions). The closure trigger is the completion of 3-way matching: invoices are automatically matched to approved POs with configurable tolerances, and Coupa's Process Automator (Coupa Autobot) …

Limitations: Coupa does not appear to offer a pre-configured, buyer-defined aging threshold alert (e.g., 90 days open) as a native out-of-the-box PO notification; the buyer would need to build this as a scheduled custom report or a Process Automator rule, which requires implementation effort and ongoing maintenance. …

Requirement evaluated: Automatic PO closure when fully received and invoiced, with alerts for POs open longer than 90 days

For a $250M technology company replacing email-and-Slack purchasing with a structured procure-to-pay workflow, Procurify handles PO lifecycle management through three connected modules: Purchasing (PO creation and approval), Receive (goods receipt), and Accounts Payable (bills/invoicing). Purchase Orders automatically close when all items in the order are fully received; a manual close option also exists for cases where items will not arrive from the vendor. Once a PO is created, the Receive module comes into play: when items are delivered, the team marks them as 'pass' or 'fail' against the PO and shipping documents, confirming arrival in satisfactory condition. …

Limitations: Auto-closure fires on receipt completion alone, not on the conjunction of full receipt plus fully matched and posted bill, so POs covering the buyer's direct materials ($30M) can close before AP processing is complete, leaving a gap in the 'fully invoiced' half of the requirement. …

Requirement evaluated: When the responsible person selects the virtual card path, the system must issue a single-use or vendor-locked virtual card with spend limits tied to the approved request amount, and subsequently reconcile the card transaction back to the originating SAP cost object without requiring manual journal entries.

For this buyer's intake-to-payment scenario, Coupa Pay handles the virtual card path as follows: once the responsible person selects the virtual card payment route post-approval, Coupa Pay issues a per-transaction unique card number authorized exclusively for the designated supplier and the approved request amount, with configurable spending limits, expiration dates, and merchant restrictions enforced at the point of purchase. vCards use a unique 15- or 16-digit virtual card number that is automatically generated, with payment authorized only for the designated supplier and a designated amount. …

Limitations: Payment method routing (virtual card vs. PO vs. service ticket) is primarily configured at the supplier-payment-account level via rules rather than as an explicit per-request human decision branch; buyers will need to confirm that their implementation supports a responsible-person-driven selection UI at the post-approv …

Requirement evaluated: When the responsible person selects the virtual card path, the system must issue a single-use or vendor-locked virtual card with spend limits tied to the approved request amount, and subsequently reconcile the card transaction back to the originating SAP cost object without requiring manual journal entries.

For a buyer routing an approved intake request to the virtual card path, Procurify offers its 'Spending Card' product: spending cards are company-issued purchase cards linked directly to the Procurify account, enabling team members to make purchases while adhering to pre-set spending limits, with every transaction automatically tracked and recorded. Cards are issued in partnership with Airwallex and are available as both physical and virtual cards. Virtual Spending Cards support online, recurring, and one-off purchases, and can be allocated to specific vendors or projects to simplify reporting and reconciliation. …

Limitations: The absence of a native SAP integration is the critical ceiling for this buyer: reconciling card transactions back to an originating SAP cost object without manual journal entries requires a custom CSV/API workaround involving a SAP consultant, which by definition reintroduces the manual intervention the buyer is tryin …

Requirement evaluated: Automatic routing to the right approver based on category, amount, department, and location

Your current process has department heads approving over Slack or email, with ops creating POs in NetSuite afterward. Coupa moves that decision into the requisition. Coupa generates approvals from a user's management hierarchy and from custom approval chains. If the requester's self-approval limit is below the requisition total, Coupa adds their next approver and keeps climbing until someone's limit is high enough. Layered on top, approval chains add approvers based on triggers, and admins configure each chain's users, priority and conditions. The documented chain conditions include accounts, commodity, item and requester (equals/contains operators), plus a total comparator. …

Limitations: Department and location routing depends on NetSuite segments being synced into Coupa's chart of accounts and lookup values, and on the ship-to or on-behalf-of user, so the NetSuite master data and the approval chain design must be built carefully up front. …

Requirement evaluated: Guided buying: when an employee searches for a product category, surface preferred/contracted vendors and catalog items first

For this $250M technology company trying to reduce 35% maverick spend and consolidate 800+ vendors, Procurify operates at the intake stage through two complementary mechanisms. First, admins pre-load a Product Catalog of frequently purchased items, each associated with one vendor and a pre-negotiated price; when an employee creates an Order Request, they can search this catalog and add items with the vendor already populated. …

Limitations: The surfacing mechanism is passive rather than dynamic: employees choose from a catalog or a preferred-vendor dropdown rather than experiencing active search-time re-ranking that promotes contracted items when they type a category term. …

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

For a $250M technology company with 800+ active vendors and 35% maverick spend, Coupa's dedicated Spend Analysis module is the operational home for tail spend identification. The module ingests transactional data directly from Coupa's own requisition, PO, invoice, and payment flows and applies an AI-powered classification engine trained on more than $8 trillion in spend data to normalize supplier names and categorize transactions automatically. …

Limitations: Because Coupa's analytics layer analyzes data that flows through Coupa itself, the buyer's historical spend currently locked in NetSuite and unstructured email/Slack approvals will not appear in tail spend views until either migrated into Coupa or imported via flat file; this means initial tail spend reports will be li …

Requirement evaluated: Hard-stop at budget limit with CFO override; soft warning at 80% utilization

For a $250M technology company trying to eliminate 35% maverick spend, Procurify's Budget Overage toggle (Settings > Manage Budgets) delivers a genuine hard stop: requests cannot be approved if a budget is exceeded and Allow Budget Overage is disabled. When a request hits or exceeds the allocated budget and the toggle is off, no approver in the chain can advance it. There is also an inline warning mechanism: when you create a Purchase list or create or edit a Purchase Order, a warning will appear notifying the user of the overage. …

Limitations: The buyer requires a configurable 80% soft warning threshold and a CFO-only override at the hard stop; Procurify's knowledge base documents neither a percentage-based pre-overage warning nor a role-scoped bypass permission, meaning the soft-warning leg of the dual-threshold requirement is unconfirmed and the override c …

Requirement evaluated: Simple receipt confirmation workflow: designated receiver confirms delivery with quantity, condition, and date

For this $250M technology company replacing ad-hoc Slack/email approvals with a structured procurement system, Coupa's native receiving module covers stage 4 of the pre-processing journey: the point at which goods or services physically arrive and a designated user confirms them before the invoice is matched. The workflow works as follows: once a PO is issued, the designated end user or central receiving team logs into Coupa and creates a receipt against the open order line. Coupa's Glossary and Implementation Options documentation confirm that the customer enters the receipt and the invoice is then matched against it, enabling three-way matching before payment is released. …

Limitations: The 'condition' capture is structured as an inspection code (pass/fail or configurable codes) rather than a free-text condition narrative, so buyers who need detailed condition notes will need to use the attachment or comment fields. …

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

For a $250M tech company moving off email/Slack-based approvals with 35% maverick spend, Procurify's Automated 3-Way Matching module operates at the full receiving-and-invoice stage of the AP lifecycle. The feature matches items across purchase orders, invoices, and receipts, automating both two-way and three-way matching, and identifies and flags variances in unit cost and received quantity with immediate notifications. On the receiving side, recording the arrival of goods automatically updates Accounts Payable for invoice matching, and a goods receipt must be recorded to facilitate the 3-way match process. …

Limitations: Approval workflows delegate bills for approval based on pre-configured workflows and conditions, which may mean that even matched invoices still pass through a lightweight approval step rather than bypassing human review entirely. …

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

For a $250M technology company with 35% maverick spend and 800+ active vendors, Coupa addresses rate card management through three interlocking mechanisms that operate at the requisition stage, well before a PO is issued. First, contracted pricing is loaded into Coupa's hosted catalog or punchout catalog as supplier item records, each linked to a contract record in the Contract Management module (CLM/CLMA); supplier item details such as price, supplier, contract, and savings are managed directly in Coupa for each item. …

Limitations: The hard price lock at requisition creation is strongest when purchases route through catalog items linked to a contract; free-form (non-catalog) requisitions can still be submitted with an ad-hoc price, so this buyer will need to invest in loading their active vendor agreements as catalog items and contract records du …

Requirement evaluated: Vendor deduplication: identify and merge the 800+ vendor records into a clean master list

For a team trying to collapse 800+ vendor records into one clean master list, Procurify has no merge function. Its help center says it does not currently support merging two vendors together. The workaround is manual. Users export and bulk-update vendors through the CSV import (UPDATE or IGNORE in the Action on Duplicate column), then decommission each duplicate by hand. They also repoint any Product Catalog items to the preferred vendor (decommissioning is recommended over deleting for vendors with historical spend, and catalog items must be moved to the preferred vendor). Procurify also has no duplicate detection tool. It offers prevention instead: a Disable Vendor Creation toggle that stops requesters from suggesting new vendors and prevents duplicate vendors. With Master Data Sync, vendors are controlled in the accounting system, and a vendor deactivated there is deleted from Procurify on the next sync. So any consolidation has to be done outside Procurify, in the ERP or accounting system or in a spreadsheet.

Limitations: Historical spend stays split across the old and new vendor records, because transactions are not re-pointed. Deleting a duplicate instead would remove its history from Reports (and break any QuickBooks Desktop vendor mapping). NetSuite-integrated domains are told not to update or import vendors by CSV in Procurify, so the 800+ cleanup would have to happen in NetSuite.

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

For a $250M technology company currently relying on email and Slack approvals with no procurement system, Coupa's shopping experience directly addresses the 'not just a search box' requirement. Coupa's Guided Buying module presents employees with a configurable homepage that features category tiles as the primary navigation entry point: users click a relevant category tile, drill down through sub-categories, and reach a results page showing applicable supplier catalogs, preferred suppliers, and request forms — without ever needing to know a product name or supplier to start. …

Limitations: The depth and organization of the category tile hierarchy depends on admin configuration at implementation; a company with no existing commodity taxonomy (as is likely given 800+ unrationalised vendors) will need to invest time upfront defining spend categories before the visual interface can guide buyers effectively. …

Requirement evaluated: Guided buying experience: search shows preferred/contracted options first with savings vs. off-contract alternatives

For a buyer coming from a zero-PO environment with 35% maverick spend, Procurify addresses the 'preferred first' part of guided buying through two mechanisms. First, administrators tag vendors as Preferred, and when a requester creates an Order Request, only Preferred vendors appear in the vendor drop-down by default; non-preferred vendors are hidden unless the buyer explicitly selects an 'Other' option, which can itself be disabled to enforce channel compliance entirely. …

Limitations: For this buyer's specific need, Procurify can enforce compliance by restricting vendor selection to the preferred list and channeling purchases through a price-anchored catalog, but it does not appear to show requesters a side-by-side savings comparison (contracted price vs. off-contract price) …