Esker vs Ivalua

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 services company moving off manual email-chain AP, Ivalua delivers KPI tracking through an AP-centric dashboard embedded directly in its AP Automation module (Invoice Hub). The platform captures workflow event data across invoice receipt, matching, approval, and payment, and surfaces those signals as real-time metrics. Ivalua explicitly names invoice cycle time, touchless processing rate, exception rate, early payment capture, and discounts as tracked metrics within built-in analytics and real-time dashboards: "Built-in analytics and real-time dashboards can help you track key metrics such as invoice cycle time, touchless processing rate, exception rate, early payment capture, or …

Limitations: Cost per invoice as a fully loaded metric (including FTE labor costs) requires the buyer to configure cost inputs; Ivalua's native feed computes processing transaction costs from workflow data but does not automatically pull FTE wage rates from payroll unless a separate data connection is built. …

Requirement evaluated: Multi-factor verification for banking change requests; we need systematic fraud prevention, not email-based trust

For a $120M services company whose AP team currently relies on email chains to process banking change requests, Esker addresses this through three layered mechanisms inside its Supplier Management module. First, suppliers authenticate into a self-service portal and submit their own banking updates directly, structurally removing AP staff from the email trust chain: Esker's supplier self-service portal enables vendors to complete and submit their account information, and they are notified when their changes have been reviewed and approved by the buyer. …

Limitations: The deepest layer of out-of-band identity verification depends on a separate contract with Sis ID; the press release explicitly states that customers must contract directly with Sis ID and supply their own credentials, meaning this capability is not bundled into the base platform. …

Requirement evaluated: Multi-factor verification for banking change requests; we need systematic fraud prevention, not email-based trust

For a $120M multi-location services company currently relying on email-based banking change approvals, Ivalua delivers a meaningful native control stack but stops short of full systematic fraud prevention without an add-on. At the native platform layer, payment automation enforces workflow-controlled approvals, segregation of duties, and bank account validation before payments are released, with built-in 2FA authentication and full audit trails to prevent unauthorized changes. …

Limitations: The native Ivalua platform covers 2FA portal authentication, configurable approval workflows, segregation of duties, and audit trails on banking changes, which eliminates email-based trust as the control mechanism. …

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 multi-location services company processing 1,800 invoices per month across a varied vendor base, Ivalua's Invoice Hub handles stage-1 capture using what it calls Hybrid Invoice Data Capture (IDC), a combination of OCR and cognitive AI that operates at the pre-processing journey stage before matching or approval routing. The cognitive layer uses image segmentation neural networks to locate and extract invoice fields rather than relying on fixed per-supplier templates, and it applies a statistical supplier identification model to recognize suppliers even when their names or logos vary across formats. …

Limitations: No public documentation confirms that operator corrections automatically retrain a per-supplier or per-tenant model in real time; the described mechanism is human-managed rule optimization layered on top of a shared cognitive model, which requires active AP team involvement to sustain accuracy gains across your specifi …

Requirement evaluated: Data encryption at rest and in transit

For this $120M multi-location services company moving 1,800 invoices per month through Esker's SaaS platform, encryption in transit is clearly and firmly documented: Esker's cloud platform provides data transfer by secure protocol (TLS), identical to those used for banking transactions. This applies to all user-to-platform and ERP integration traffic. For encryption at rest, however, Esker's own cloud platform page introduces a material qualifier: encrypted data at rest is listed as 'optional' on the platform. This means at-rest encryption is available but is not confirmed as a universal, enforced default across all storage layers, invoice document repositories, and ERP sync data. …

Limitations: The 'optional' qualifier on encrypted data at rest in Esker's own cloud platform documentation is a material gap: this buyer cannot assume that invoice documents, captured line-item data, and vendor banking records stored in Esker are encrypted at rest by default without confirming this configuration in writing during …

Requirement evaluated: Data encryption at rest and in transit

For a $120M multi-location services company running sensitive AP data across 2 Sage Intacct entities, Ivalua's security architecture addresses the encryption requirement at the platform infrastructure level, not within a specific AP workflow step. According to Ivalua's published technical architecture document filed with the GSA, data at rest and in transit is protected using industry-standard AES-256 encryption, and web traffic between Ivalua servers and external systems is encrypted using TLS (HTTPS) up to AES-256, with AS2 protocol communications using RSA 2048-key X.509 certificates. …

Limitations: The fact sheet provided contains no security-specific primary or supporting claims, so the encryption evidence comes entirely from Ivalua's technical architecture document and platform page rather than AP-module-specific documentation. …

Requirement evaluated: Duplicate invoice detection across vendor, amount, date, and invoice number; must catch cross-entity duplicates

For a $120M services company running 1,800 invoices per month across 2 Sage Intacct entities, Esker's duplicate detection operates at the platform validation layer, before any invoice is posted to Intacct. During the invoice validation stage, AP is alerted to any invoice that resembles one already processed: the system compares values in different fields including vendor name, part number, date, and total amount to prevent double invoice entry and subsequent double payment. This check is a named discrete capability within Esker's AP module: duplicate detection is listed alongside invoice data extraction, automatic matching, and exceptions handling as a core AP function. …

Limitations: The cross-entity duplicate detection scope is the material unresolved question for this buyer: if Esker's detection index is maintained per Intacct entity rather than as a unified cross-entity pool, same-vendor invoices submitted to both entities will not be flagged, which is precisely the failure mode the buyer is try …

Requirement evaluated: Duplicate invoice detection across vendor, amount, date, and invoice number; must catch cross-entity duplicates

For a $120M multi-entity services company routing invoices across two Sage Intacct entities, Ivalua's Invoice Hub is the primary mechanism for duplicate prevention. The Invoice Hub product page explicitly names 'Trap duplicate invoices' as a discrete feature alongside blocking fraudulent invoices and validating tax compliance, and the payments module separately lists 'Built-in duplicate payment detection controls' as a first-class capability. The detection runs at the pre-processing stage: the moment an invoice arrives in the Invoice Hub, Ivalua checks the supplier and validates its content before further processing, meaning flagging happens before the invoice enters approval workflow. …

Limitations: The material ceiling for this buyer is the unconfirmed cross-entity scope: if Ivalua's duplicate detection is scoped to the buying entity at the time of intake rather than querying a global invoice repository spanning both Sage Intacct entities, the buyer's cross-entity duplicate risk goes unaddressed entirely, which i …

Requirement evaluated: Approved POs push to NetSuite automatically; payment status syncs back

For a $250M technology company replacing manual NetSuite data entry, Esker offers a pre-built NetSuite integration delivered through B.Workshop, a certified Esker partner integrator for Oracle NetSuite, as part of Esker's ERP Connectivity Suite. B.Workshop is a certified integrator for Oracle JD Edwards and Oracle NetSuite, and has created pre-built integrations linking Esker with both ERP platforms. On the procurement side, Esker's procurement module offers pre-built connectors providing out-of-the-box integration with popular ERP systems including NetSuite. …

Limitations: Esker's NetSuite connector is delivered via its certified partner B.Workshop rather than a first-party native SuiteApp; the mechanism explicitly documented covers AP invoice push and master data sync, but neither the automatic PO push on approval nor the inbound payment status sync from NetSuite back to Esker is confir …

Requirement evaluated: Approved POs push to NetSuite automatically; payment status syncs back

For a $250M NetSuite shop moving off manual email/Slack approvals, Ivalua delivers ERP synchronization through its built-in Integration Hub (also called the Integration Workplace), which supports bidirectional data flows via APIs, ETL, and EAI connectors without requiring third-party middleware. The Integration Hub orchestrates enterprise systems in real time, with a built-in integration layer that requires no middleware. Automation tools sync data bidirectionally using APIs or native connectors, so PO numbers, line items, and status updates are mirrored automatically with no manual entry required. …

Limitations: No pre-built, named NetSuite connector is documented in Ivalua's integration catalog; the buyer would need to build and configure the NetSuite connection through Ivalua's Integration Workplace APIs and EAI tools, adding implementation effort and timeline risk compared to vendors with a certified NetSuite SuiteApp. …

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 moving off email-based approvals and needing to demonstrate audit readiness, Ivalua's platform carries both SOC 2 attestation reports and ISO 27001 certification. Ivalua's CISO confirmed in a public press release that the platform holds 'existing SOC 1 and SOC 2 attestation reports' alongside ISO 27001, and Ivalua's own procurement platform page lists SOC 2 among its active certifications alongside AES-256 encryption, SSO/SAML, and SIEM/IDS/IPS monitoring on a multi-instance SaaS architecture. A more recent third-party source (December 2025) also lists 'SOC 1 and SOC 2 attestation reports' as part of Ivalua's current security certification portfolio. …

Limitations: Public disclosures consistently reference 'SOC 2 attestation reports' without specifying which Trust Service Criteria (security only, or also availability/confidentiality) …

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. Captured data is automatically checked using 2-way or 3-way matching against an existing purchase order; if there are no exceptions, touchless processing can create the invoice for payment without the need for user validation. …

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: Automatic match-and-pass for invoices within tolerance, reducing AP workload to exceptions-only review

For a company moving from email-and-Slack approvals with 35% maverick spend, Ivalua's AP Automation module (part of its Procure-to-Pay suite) delivers the exceptions-only AP model the buyer is targeting. The matching engine, which Ivalua calls 'Smart Matching,' links the PO, goods receipt, and supplier invoice into a single workflow and performs real-time three-way matching at the line level: it compares invoiced quantities, unit prices, and totals against both the approved PO and the goods/service receipt confirmation. …

Limitations: The three-way match depends on goods receipt records being created in Ivalua; the buyer currently has no procurement system and no systematic receiving workflow, so the AP team will need to establish receipt-confirmation discipline during implementation before touchless rates ramp up. …

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: Native, pre-built, bidirectional integration with Sage Intacct (not middleware-dependent)

Your team runs 2 Sage Intacct entities and needs a pre-built, bidirectional connector that syncs vendors, GL codes, POs, approved invoices, and payment status between Ivalua and Intacct without custom development or middleware. Ivalua's Integration Hub offers prebuilt ERP connectors, but every named target in Ivalua's published integration documentation is SAP, Oracle, or Microsoft: the platform page lists 'leading enterprise systems like SAP, Oracle, and Microsoft' as the recipients of its prebuilt connectors, and the multi-ERP integration page identifies a dedicated SAP Plug & Play connector as its flagship. …

Limitations: No pre-built, certified Sage Intacct connector exists in Ivalua's documented integration library or the Sage Intacct Marketplace; any connection would require custom implementation using Ivalua's generic ETL/API layer, conflicting directly with the buyer's 'not middleware-dependent' and 'pre-built' requirements. …

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: Dual approval requirement for all capital expenditures regardless of amount

For a $120M services company running two Sage Intacct entities, Ivalua's platform-level workflow engine addresses the dual-approval CapEx requirement through category-based routing conditions, not dollar thresholds. Ivalua's eProcurement module explicitly supports CapEx as a recognized spend type within its workflow logic: the product page states that 'flexible workflows adapt to any purchasing process, from services to CAPEX and inventory-based spend.' An admin uses the no-code workflow designer to define a routing branch that fires when an invoice is classified as a capital expenditure (via GL account range, spend category tag, or a custom CapEx field set at the coding stage), and that bra …

Limitations: Ivalua is an enterprise source-to-pay suite scaled for large, complex organizations; a $120M, 200-employee company should validate during scoping that the CapEx classification field (GL account range or spend category) …

Requirement evaluated: Automatic remittance advice sent to vendors upon payment

For a 3-person AP team at a $120M multi-location services company currently sending remittance advice manually (or not at all), Esker addresses supplier payment visibility primarily through its supplier portal rather than through event-triggered outbound remittance delivery. Esker's AP automation module gives suppliers direct, self-service access to invoice and payment status via an online portal, reducing inbound status inquiry calls to the AP team. Separately, Esker's Synergy AI layer can automatically sort and generate responses to inbound supplier inquiries about payment status, including overdue payment reminders and payment confirmation questions. …

Limitations: The primary documented supplier communication mechanism is portal-based self-service access, which places the discovery burden on each vendor and requires portal adoption; for the 1,800 invoices per month this buyer processes across facilities, subcontractor, subscription, and utility vendors, those vendors must active …

Requirement evaluated: Unified payment hub supporting ACH, check, wire transfer, and virtual card from a single interface

For a $120M multi-location services company currently running bi-weekly check runs and monthly ACH batches through Sage Intacct manually, Ivalua offers a dedicated Payments module that consolidates all four required rails into a single governed platform. The module explicitly covers ACH, check, EFT, and cross-border transfers on one side, and virtual card issuance (both single-use V-cards and P-cards) …

Limitations: Ivalua's documented native ERP connector list emphasizes SAP, Oracle, Workday, and Microsoft Dynamics; Sage Intacct-specific connector documentation was not surfaced in this search, so the buyer should confirm whether the Sage Intacct integration carries full payment postback fidelity (entity-level GL entries, payment …

Requirement evaluated: Self-service request portal where any employee can submit a purchase request without training; must be simpler than email

For a 450-person technology company currently routing purchase requests through email and Slack, Esker's Purchasing module gives every employee a self-service online requisition portal that directly replaces that email workflow. Requesters log in and either browse a catalog of pre-approved supplier items (internal hosted catalog or PunchOut to live supplier storefronts like an embedded shopping cart), create a requisition directly from a supplier quotation, or fill a structured online request form. Once submitted, Esker auto-routes the requisition to the correct approvers based on a preconfigured buying policy so the requester never has to identify who needs to sign off. …

Limitations: Esker's intake is a structured portal and catalog model, not a conversational or chat-embedded experience; employees accustomed only to composing emails will need a brief orientation to the interface, even if the catalog browse and auto-routing eliminate all procurement knowledge requirements. …

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

For this $250M technology company coming from a fully manual email-and-Slack approval process, Ivalua's Intake Management and eProcurement modules intercept spend at the purchase requisition stage, before any financial commitment is made. When an employee submits a request, the platform's configurable workflow engine evaluates the requisition against rules built on multiple simultaneous dimensions: spend threshold, cost center/department, spend category, geography/location, and budget owner. …

Limitations: The primary sources are Ivalua marketing and product blogs rather than granular help-center documentation, so the exact configuration interface (e.g., whether rules are built in a visual no-code workflow designer or require scripted conditions) …

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

Requirement evaluated: Automated PO distribution to vendors via email or vendor portal

For a finance team that wants approved purchases to reach vendors without manual sending, Esker's Purchasing module converts an approved request into a PO and sends it to the supplier. It then manages acknowledgements, changes and receipt in the same process (Esker E-Procurement page). Esker's product summary lists "purchase order distribution" as a feature. Its DeliveryWare documentation describes automated PO delivery that assembles the PO document package and sends it in the formats and via the transports suppliers can most efficiently process, with delivery-status notification. Suppliers can also use Esker's supplier self-service portal to interact with buyers on orders. This covers the order-placement and supplier-collaboration stages, and Synergy AI can compare supplier PO acknowledgements against the original order.

Limitations: I found no support.esker.com help article that documents the exact channels (email, portal, EDI, fax), per-supplier delivery preferences or bounce handling for PO sending. The DeliveryWare and solution-summary PDFs are older material, so confirm in a demo that email and portal delivery are configurable per vendor in the current release.

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

Requirement evaluated: A single request can produce mixed outcomes: a PO for some line items, a virtual card for others, and a service ticket for internal work

For a technology company trying to eliminate email-and-Slack approvals, Ivalua's Intake Orchestration module provides a single centralized hub where an employee submits one request and the platform's AI-guided workflow engine automatically routes each element to a different process path. A single submission can be automatically routed to the right process flow, including IT, HR, Expense, Travel, or Accounts Payable, with AI-based triage and system integration. …

Limitations: The service ticket path for internal work lines requires configuring the Integration Hub's API handoff to an ITSM platform (such as ServiceNow), adding implementation effort and a dependency on that integration being live before the mixed-outcome flow works end-to-end. …

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: Preferred vendor lists by category with contract terms visibility

For a technology company like yours with 800+ active vendors and 35% maverick spend, Ivalua addresses this requirement through a combination of its Supplier Management module and Contract Lifecycle Management (CLM) module, both operating on a single unified supplier record. Approved suppliers are stored in a searchable directory that carries preferred vendor flags, contract status, risk ratings, and performance data by category, so procurement teams can segment and surface the right vendors for each spend type. …

Limitations: The depth of configuration for category-specific preferred vendor rules and the granularity of contract metadata surfaced inline during requisition will depend on implementation effort; Ivalua's platform is highly configurable but that configurability requires structured setup during deployment, which may extend time-t …

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

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

For a finance team that wants to find high-transaction-count, low-dollar vendors to consolidate, Esker offers spend visibility dashboards rather than a dedicated tail spend module. Esker's AP dashboards display live analytics including spend by category, volume and supplier, and they are customizable (Esker AP KPI ebook; Esker AP datasheet). AP managers get views of spend by category, volume and supplier plus spend analysis and trend. Procurement adds committed-spend and budget-consumption visibility before invoices arrive (Esker e-procurement page). A user could build or filter a supplier-by-volume and supplier-by-amount view to spot long-tail vendors manually, and Esker's tail spend content describes spend analysis and supplier rationalization as the approach. The documentation does not describe a built-in tail spend or Pareto segmentation, a transaction-count-versus-dollar threshold, or consolidation recommendations. Esker acts at the requisition, PO and invoice stages, so this is retrospective and in-flight spend reporting, not a sourcing-opportunity analytics engine.

Limitations: I found no public Esker documentation of a tail spend report, ABC/Pareto banding, configurable low-dollar and high-count thresholds, or automated vendor-consolidation suggestions. The buyer would likely have to assemble the analysis from supplier volume and spend dashboards, or export to a BI or spend-analytics tool.

Requirement evaluated: Budget hierarchy: company → division → department → project → GL code

For a $250M technology company currently managing no procurement system and facing 35% maverick spend, Ivalua's Budget Management module (listed under Additional Solutions) lets administrators configure budgets by fiscal year, cost center, organization, project, and chart of accounts: dimensions that map directly to the buyer's required company → division → department → project → GL code hierarchy. Budgets can be imported from a financial system such as NetSuite and structured with a configurable chart of accounts, then tracked at the budget-line level as spend progresses. …

Limitations: Official help-center documentation (help.ivalua.com) was not publicly accessible during this evaluation, so the specific UI steps for configuring parent-child rollup rules across all five hierarchy levels could not be verified at the article level; buyers should request a configuration walkthrough during a demo. …

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

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 …

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

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

For your situation, where requests now arrive by email and Slack and 35% of spend has no PO, Ivalua eProcurement gives requesters one homepage to start from. Ivalua's eProcurement datasheet shows a procurement homepage with Category Shortcuts (for example Facilities and Equipment), item shortcuts with images, shopping lists, previously purchased items and browse history, all feeding an Add to Cart flow. The same datasheet describes a central entry point for all requests with smart routing to the right buying channel, which covers hosted catalogs, punchout, free-text and service requests. …

Limitations: The documents show category shortcuts and image-based item tiles on a configurable homepage. They do not show a standard, out-of-the-box visual category tree with drill-down, so the exact look for your IT, facilities, marketing and travel categories will probably be set up during implementation. …