Coupa vs Stampli vs Ariba for Procurement & P2P

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. The receiving transaction data model (documented in the Receipts API and the InventoryReceipt type) captures quantity, inspection code (pass/fail condition), item, order line reference, account, and timestamp, covering the buyer's required fields of quantity, condition, and date. Goods Receipts created in Coupa are also written back to the ERP via standard outbound interfaces, so NetSuite is kept in sync.

For a $250M tech company moving off email-based purchasing, Stampli's Receiving module (part of Stampli Procurement) covers the full receipt confirmation workflow as a distinct stage between PO issuance and AP invoice review. When a Stampli PO is created, a Procurement Specialist designates a receiver per PO line and sets a 'Receiving Required' flag along with an expected delivery date; the requester is assigned as the default receiver but can be changed at any time. When items are ready to receive, the assigned receiver gets an inbox notification and opens a dedicated Receiving tab (separate from the invoice view) where they enter quantity received, select the receipt date (defaulting to today, with future dates disabled), add free-text comments, and upload proof of delivery such as packing slip photos or PDFs at the line level. Partial shipments are handled natively: the system tracks 'Received' vs. 'To Receive' quantities per line, and the receiver repeats the process on subsequent deliveries until the line is fully received or manually closed. Once receipt data is recorded, Billy (Stampli's AI) surfaces quantity discrepancies to AP during invoice review: as of the March 2026 release, Billy flags any invoice line quantity that exceeds the received quantity, giving AP context for the three-way match without requiring AP staff to be the ones confirming physical delivery. A full audit trail logs every receipt action with the user and timestamp. Mobile receiving (iOS and Android) is also available, allowing warehouse or facilities staff to confirm deliveries on-the-go with camera-based photo attachments.

Your $250M technology company — currently relying on email and Slack for approvals with no formal receiving step — can configure SAP Ariba Buying's native Receiving module to enforce a buyer-side goods receipt confirmation before any invoice proceeds to payment. When a PO is issued, the system triggers an email notification to the designated receiver and surfaces a task in their To-Do list tied to the expected delivery date. The designated receiver role is configured through a Receipt Approval ruleset: the administrator defines which person or group is responsible for receiving against a given PO, making that user the first 'approver' who must complete the receipt fields before the document can advance. At the receiving step, the receiver logs quantity received (or monetary amount for services), notes any discrepancies or condition issues via the reject/discrepancy mechanism, and the system date-stamps the receipt. Ariba then performs a three-way match between the PO, the goods receipt, and the supplier invoice; if ReceivingType is set to anything other than 'No Receipt,' the match requires all three documents to align before payment is released. Partial receiving is natively supported: multiple receipt events can be recorded against a single PO line, and the PO status updates to 'Receiving' until all quantities are fulfilled. Administrators can also configure over- and under-receiving tolerances by absolute quantity, percentage, or line value.

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. As documented in Coupa's R35 release (Guided Experience), admins can highlight popular commodity categories and frequently used forms directly on the homepage, surfacing the right buying channels for each spend type (IT, facilities, professional services, marketing). The search bar co-exists as a secondary option, but tile-based category browsing is the primary visual interface. Behind the tiles, catalog content is delivered through hosted catalogs (curated item lists with images, pricing, and descriptions loaded from approved suppliers) and cXML punchout catalogs (where the tile launches the user into the supplier's own e-commerce storefront and returns the cart to Coupa for requisition and approval). The Coupa Advantage marketplace adds a pre-negotiated, contract-based shopping layer across categories, also accessible from this same interface.

For a $250M technology company with 35% maverick spend and no current procurement system, SAP Ariba Guided Buying directly addresses the requirement for category-based visual navigation rather than a plain search box. When employees log in, they land on a persona-based home page populated with clickable, image-bearing category tiles covering areas such as IT, facilities, marketing, and professional services (the spend categories this buyer uses most). Administrators configure up to four hierarchy levels of landing pages, each with custom tiles and images, so users click into a category before ever touching a search field. As the SAP help portal documents, landing pages are created specifically for purchases in categories like marketing, facilities, or IT, with tiles that can link to catalog items, PunchOut supplier sites, custom intake forms, or other SAP modules. The guided buying capability is included at no additional cost with SAP Ariba Buying and SAP Ariba Buying and Invoicing solutions, and forms, permissions, and system behavior are configurable per user persona, so each of the buyer's four US offices and Canadian development center can see a tailored category view rather than a generic search interface.

For a $250M technology company replacing email-and-Slack purchasing, Stampli's guided buying experience operates through two mechanisms rather than a single visual category storefront. First, the Employee Purchasing Portal presents employees with customizable request type forms organized by purchasing need (IT hardware, office supplies, software licenses, travel, services), and within those forms a 'preferred items' list surfaces pre-approved options that procurement teams have curated; employees can also describe what they need in natural language and Stampli's AI structures the request (Stampli Employee Purchasing Portal, help.stampli.com). Second, a punchout capability lets employees click 'Shop vendor sites' from inside a purchase request and see a tile list of connected vendors (including Amazon Business); they shop that vendor's live storefront and the cart returns into Stampli automatically for approval, budget check, and PO creation (Connected Vendor Shopping, api.intercom.io/articles/15649166; Amazon Business Punchout, api.intercom.io/articles/16989332). The gap relative to the buyer's requirement is that neither mechanism delivers a category-first browsing hierarchy: the request-type selector is a form picker, not a visual tile grid organized by spend category, and the punchout tile list is vendor-organized, meaning employees must already know which supplier to shop rather than starting from a category need like 'Facilities' or 'IT' and discovering relevant suppliers and items beneath it.

For a $250M tech company operating across 4 US offices and a Canadian development center, Coupa delivers role-based access control through a layered three-part model. First, predefined system roles (Requester, Buyer, Approver, and others) define what each user can do at the module and action level; administrators can also create custom roles by selecting granular permission sets, and users can hold multiple roles simultaneously with additive permissions. Second, Content Groups (also called Business Groups in Coupa's back-end API) restrict which objects a user can access: suppliers, catalogs, contracts, and other transactional content are assigned to named groups, and once a supplier content group is configured, users outside that group cannot select those suppliers when creating requisitions or invoices. Third, User Groups implement a documented four-tier hierarchy: License groups, Roles groups (what users can do), Access Segregation groups scoped to region or department (what users can access), and optional sub-groups; nested groups inherit permissions from parent groups, letting an admin model the company's full org chart without per-user configuration. The Departments API is explicitly designed to 'mimic your business operating structure and organize content groups and users accordingly,' completing the entity and department-level isolation layer. Approval chains can be scoped to match these group memberships, so spending authority and transaction visibility both respect the same org boundaries.

For a $250M technology company with 4 US offices and a Canadian development center, Stampli delivers role-based access control across both its AP and procurement modules through a documented set of named roles that control visibility, permitted actions, and scope independently. On the AP side, roles determine what a user can see, what they can do, and which parts of Stampli they can access; and a System Admin can grant Reviewer access scoped by GL account, department, shipment number, or another invoice field - meaning a department manager in the Toronto office can be restricted to reviewing only their entity's invoices. On the procurement side, Stampli provides 11 precisely crafted roles covering the entire procurement lifecycle, with function-based permissions that ensure perfect separation of duties by mapping system permissions to organizational responsibilities, and role-specific interfaces that show users exactly what they need based on their organizational function. Approval routing reinforces these data boundaries: approval workflows can be configured based on numerous factors including department, request amount, subsidiary, and other criteria. Stampli also introduced a dedicated Budget Admin role to support better separation of duties between Procurement and Finance/AP teams, allowing organizations to give users access to budget-related settings without also granting broad procurement administrative permissions, reflecting a principle-of-least-privilege design. Entity-level scale is confirmed by the fact that 15,000 entities are represented across Stampli's customer base.

For a multi-office technology company moving from ad-hoc email purchasing to a governed procurement system, SAP Ariba delivers role-based access control through two interlocking layers. First, a Groups and Roles system assigns every user to one or more system groups (Purchasing User, Invoice Manager, Procurement Manager, Customer Administrator, and others), where each group grants a specific functional permission set; system groups provide functional area and access-level permissions, and each access level grants a unique set of permissions that does not necessarily grant all permissions of lesser access levels. Customers can create custom child groups that inherit from system groups, so a company can define named roles (e.g., Requester-US-West, Approver-Canada-Dev) that combine the right permission sets for each office or department. A custom group inherits privileges from all its parent groups, and these relationships are called Group-to-Child Group mappings. Second, Purchasing Units (also called procurement units) enforce entity and department-level data segregation: a purchasing unit is an SAP Ariba concept that lets you separate spend activities by entities such as departments, business units, purchasing organizations, cost centers, divisions, and so on. Once a user is mapped to a purchasing unit, approval requests are sent only to approvers relevant for that purchasing unit, and when users perform searches, run reports, or perform manage operations, the data they see is restricted to specific purchasing units. Suppliers visible in requisition choosers, contract selections, and invoice reconciliation queues are all filtered to the user's assigned purchasing unit and its hierarchy. The Visibility Control feature places visibility constraints on search results, user pick lists, and reporting, and differentiating sets of data and associating users with purchasing units affects which data users can see in choosers, search results, and reports. Purchasing units can be mapped to the buyer's NetSuite org structure or defined natively in Ariba. You can make the purchasing unit object specific to the SAP Ariba solution, or you can map purchasing units to objects defined in your ERP system. The supporting fact sheet also confirms built-in policy checks, audit rules, approvals, and proactive guidance happen automatically in real time, reinforcing that the RBAC layer feeds into the broader compliance and audit posture the buyer requires.