Airbase vs Stampli

Requirement evaluated: Rush/emergency payment workflow with compressed timeline and appropriate audit trail

For a $120M multi-location services company whose AP team of 3 currently routes approvals through email chains with no compressed-timeline mechanism, Airbase's Advanced Approvals module provides the foundation that can be configured to approximate a rush-payment workflow. Approval rules can be built on amount, vendor, department, subsidiary, and GL category, and approvers can act from desktop, Slack, mobile, or email, which shortens the physical round-trip time versus the buyer's current email chain process. The full audit trail is automatic: every action from request through payment is centrally recorded, with related email correspondence attached to the transaction record. …

Limitations: For this buyer's 6-location services company, there is no evidence of a native 'rush/emergency payment' workflow type with a built-in compressed timeline trigger or urgency flag; the buyer would need to configure a separate approval rule set that approximates expedited routing, which adds administrative overhead and ma …

Requirement evaluated: Rush/emergency payment workflow with compressed timeline and appropriate audit trail

For a $120M services company with a 3-person AP team managing bi-weekly check runs, the need for a rush/emergency payment path is real: a subcontractor holds work, a utility faces disconnection, or an insurance premium lapses. Stampli addresses part of this requirement through two mechanisms. First, its messaging layer includes an urgent flag feature: the urgent flag feature allows users to highlight time-sensitive requests, giving them special visual treatment in the interface and generating priority notifications to recipients, so critical issues stand out from routine communications and get addressed promptly. …

Limitations: For this buyer's AP team of 3 processing 1,800 invoices per month across two Sage Intacct entities, the gap is that Stampli's urgency tools operate at the messaging and notification layer, not at the approval chain architecture layer: there is no documented out-of-box rush workflow that structurally reduces approver st …

Requirement evaluated: 1099 preparation: automated classification, threshold tracking, and electronic filing

For a $120M services company processing 1,800 invoices per month with subcontractors, utilities, and professional services vendors, 1099 compliance touches a meaningful portion of that non-PO spend. Airbase addresses the classification and threshold-tracking legs of this requirement but stops short of the electronic filing leg. During vendor onboarding, Airbase collects W-9 information and validates the vendor's legal name and Taxpayer Identification Number against IRS records; it also flags any vendor who has not yet submitted a required W-9. …

Limitations: The electronic filing component of this requirement is a hard gap: Airbase exports a 1099-flagged vendor list but does not submit forms to the IRS, which means the buyer's AP team must separately subscribe to and operate Avalara, Tax1099, or an equivalent service, introducing a manual data handoff and a second vendor r …

Requirement evaluated: 1099 preparation: automated classification, threshold tracking, and electronic filing

This $120M multi-entity Sage Intacct shop needs three things from 1099 automation: vendor classification at onboarding, year-round threshold tracking, and IRS electronic filing. Stampli covers the first leg well: its Advanced Vendor Management module collects W-9 forms through a self-service vendor portal and stores Tax ID, entity type, 1099 flags, and W-9 expiration dates on each vendor record. On the Sage Intacct integration specifically, Stampli imports each vendor's 1099 status from Intacct and exports the same flags back at both vendor and invoice line levels, so year-end 1099 reports in Intacct stay accurate. …

Limitations: The buyer's requirement explicitly names threshold tracking and electronic filing, and both remain outside Stampli's scope: threshold monitoring and actual 1099 form generation and e-filing depend entirely on Sage Intacct's native capability, so Stampli adds no automation lift at the filing stage. …

Requirement evaluated: Real-time AP dashboard: invoice aging, approval queue depth, processing cycle time, spend by vendor/category/entity

For a $120M multi-location services company running 1,800 invoices per month across 2 Sage Intacct entities, Airbase's Spend Analytics module (airbase.com/pillars/real-time-reporting) delivers the core dashboard components this buyer requires. The platform monitors the time it takes to create, approve, and pay bills, tracks cycle time goals to avoid late fees, and supports productivity monitoring at both individual and team levels. On the spend dimension side, Airbase surfaces up-to-the-minute spend by department, vendor, category, or subsidiary across all spend types including corporate cards, POs, and expense reimbursements. …

Limitations: The approval queue depth metric is documented primarily through the lens of 'bottleneck identification' rather than as a discrete, pre-built KPI widget showing live queue counts by approver or invoice age bucket; teams that need a real-time count of invoices sitting at each approval stage may need to configure custom r …

Requirement evaluated: Real-time AP dashboard: invoice aging, approval queue depth, processing cycle time, spend by vendor/category/entity

For a $120M multi-location services company currently managing AP entirely through email chains with no visibility tooling, Stampli delivers its analytics layer through a named module called Stampli Insights, which bundles Stampli Dashboards and Stampli Reports into the same AP workflow interface the 3-person team already uses. On the dashboard side, each dashboard displays a set of fixed KPIs, with real-time data on invoices currently being processed, including KPIs like Pending Routing, Pending Approval, and Urgent Invoices, with widgets showing metrics such as Days Pending Routing and Open Invoices by Amount - directly covering the buyer's approval queue depth and invoice aging requiremen …

Limitations: Entity-level filtering within Stampli Insights dashboard widgets is confirmed at the access-control and integration level (Intacct entity restrictions flow into Stampli automatically), but the product documentation does not explicitly show a dashboard-wide entity dimension toggle; the buyer should verify during demo th …

Requirement evaluated: Board-ready spend reports: quarterly spend summary by category with trend lines and vendor concentration metrics

For a $250M technology company currently flying blind with 35% maverick spend, Airbase's dedicated Spend Analytics module (launched June 2024) aggregates data across all three spend channels: accounts payable, corporate cards, and employee expenses, giving it the full spend footprint needed to reflect reality rather than just PO-backed transactions. The module surfaces spend broken down by department, vendor, subsidiary, and category with trend visualization across time periods, and users can filter by custom date ranges including quarterly windows. …

Limitations: For this buyer's CFO and board audience, the material gap is in the final presentation layer: Airbase does not appear to produce natively formatted, board-ready quarterly packages (PDF or slide-ready export with branded formatting and concentration metrics pre-calculated); finance staff will likely need to export raw d …

Requirement evaluated: Board-ready spend reports: quarterly spend summary by category with trend lines and vendor concentration metrics

For a $250M technology company moving from email-based purchasing to a structured P2P system, Stampli delivers board-ready spend reporting through two connected layers. First, Stampli Deep Finance is an agentic financial analyst that surfaces consultant-grade insights on spend, vendors, and performance without manual work. The help center documents explicit quarterly-cadence example prompts: "Deep Finance" is accessed from Dashboards & Reports in the left-hand menu and allows users to ask finance questions in plain language and explore on-demand analysis of spend data. …

Limitations: Deep Finance generates its analysis from invoice, payment, procurement, and Stampli Card data that flows through Stampli's own platform; spend that bypasses the system entirely (the buyer's current 35% maverick spend, until those transactions are brought into Stampli workflows) …

Requirement evaluated: Configurable retention policies aligned with our 7-year record retention requirement

For a $250M technology company that currently has no system-enforced record preservation, Airbase does automatically capture and store a comprehensive audit trail for every spend event: purchase requests, PO approvals, invoice activity, card transactions, and reimbursements. According to Airbase's own audit trail feature page, the platform captures transaction details as they happen and records them to 'an easily retrievable audit trail,' covering all purchase transaction elements regardless of payment method. The audit trail also syncs bidirectionally to the connected ERP (NetSuite in this buyer's case), so the general ledger receives a complete, audit-ready record of each event. …

Limitations: The buyer's requirement is not just record creation but enforced, configurable retention: a guarantee that POs, invoices, and approval logs cannot be deleted or become unavailable before 7 years have elapsed. …

Requirement evaluated: Configurable retention policies aligned with our 7-year record retention requirement

For a $250M technology company needing 7-year record retention with audit-grade retrievability, Stampli addresses part of this requirement through its core AP storage model: Stampli keeps the complete record together, with the invoice, its documents, coding history, and the immutable approval trail living as one retained object, so retention covers the evidence and the authorization, not just the document. …

Limitations: The buyer's requirement is specifically for configurable retention policies with a defined 7-year minimum; Stampli's terms of service explicitly disclaim retention compliance responsibility and reserve the right to change Transaction History duration, meaning the buyer cannot rely on Stampli's platform alone to satisfy …

Requirement evaluated: Contract repository: store agreements, track renewal dates, alert stakeholders 90/60/30 days before expiration

For a $250M technology company currently tracking zero contracts systematically, Airbase's Vendor Management module provides a meaningful starting point. Each vendor profile stores contracts, insurance certificates, and tax documentation centrally, and the platform's dedicated 'renewals' feature provides automated renewal planning with stakeholder notifications. A third-party review of the module documents that automated alerts fire at 30, 60, and 90 days before contract or document lapse, matching the buyer's required cadence. …

Limitations: The buyer's requirement for a true contract repository (searchable by metadata, with lifecycle status, expiration-date fields, and configurable multi-stakeholder alert rules) …

Requirement evaluated: Contract repository: store agreements, track renewal dates, alert stakeholders 90/60/30 days before expiration

Your company currently has no centralized contract repository and relies on email and shared drives. Stampli's Advanced Vendor Management (AVM) module addresses part of this gap: administrators can upload vendor agreements, contracts, W-9s, insurance certificates, and licenses directly to each vendor's profile under the Vendor Documents tab, where an expiration date field can be set per document. When a document approaches expiration, Stampli sends automatic email and in-app notifications to the assigned Vendor Manager, and can also notify the vendor to submit an updated document. …

Limitations: The documented expiration-alert mechanism does not confirm the buyer's required 90/60/30-day multi-threshold cadence or the ability to assign renewal alerts to specific named stakeholders across procurement, legal, and finance; the system appears designed for compliance-document refresh rather than full contract lifecy …

Requirement evaluated: Confidence scoring on extracted data so AP clerks know which fields to verify vs. which are high-confidence

For a $120M multi-location services company processing 1,800 invoices per month through a three-person AP team, this requirement asks whether Airbase surfaces per-field extraction reliability indicators so clerks know which fields to spot-check versus trust automatically. Airbase's documented extraction model operates on an auto-population basis: its intelligence uses a combination of rules, OCR, and generative AI to accurately populate invoice, bill, and PO details, with invoice fields automatically read, coded, and categorized. …

Limitations: Airbase's AP clerks receive no documented per-field confidence signal distinguishing high-confidence from low-confidence extractions; the model is auto-populate-and-route, which means clerks either trust all auto-filled fields or revert to verifying every field, exactly the manual burden this requirement was designed t …

Requirement evaluated: Confidence scoring on extracted data so AP clerks know which fields to verify vs. which are high-confidence

For a 3-person AP team processing 1,800 invoices per month across two Sage Intacct entities, Stampli's Billy operates a suggestion model at Stage 1 of the pre-processing journey: upon invoice receipt, Billy automatically extracts header and line-item data (vendor name, date, amounts, GL accounts, departments, custom dimensions) and pre-fills those fields as suggestions for clerk review. Once an invoice arrives, Billy instantly extracts data and makes it available in real time, continuously learning financial and managerial accounting processes, recognizing patterns, and suggesting the actions or entries that need to be made for each new invoice. …

Limitations: No documented evidence exists of per-field numeric confidence scores, color-coded certainty tiers (e.g., green/yellow/red by field), or threshold-based straight-through processing that bypasses clerk review when extraction confidence exceeds a configurable percentage. …

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

Your field team would use Airbase's native mobile app, available on iOS (15.1+) and Android, which Airbase describes as supporting 'an active on-the-go request and approval flow.' The app allows employees to create expense reports, capture receipts with the camera, manage card transactions, and track approval status from a smartphone. However, the upstream purchase request intake workflow — Airbase's Guided Procurement module, which is the mechanism for submitting a pre-purchase request before a PO is issued — is documented as a multi-step, multi-stakeholder web form ('Go to Request > Purchase, complete the Spend Intake form') with no documented equivalent in the native mobile app. …

Limitations: For a field team at a job site needing to initiate a new procurement request (not just capture a receipt or track an existing PO), Airbase's mobile app does not appear to support the full Guided Procurement intake form; the buyer should verify with Airbase whether the Spend Intake form is accessible and fully functiona …

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 requests and create service tickets directly from the Stampli mobile app on iOS or Android, without needing to return to a desktop. Stampli's P2P platform includes a mobile app offering user-friendly purchase request intake, supporting request types ranging from office supplies to IT equipment to travel. …

Limitations: The offline sync capability documented in Stampli's mobile help center is explicitly scoped to expense/receipt capture; there is no documented offline mode for purchase requisition or PO creation, which could be a gap for job sites with unreliable connectivity. …

Requirement evaluated: Payment reconciliation with automatic journal entries back to Sage Intacct

For a 3-person AP team moving 1,800 invoices per month across two Sage Intacct entities, Airbase handles payment reconciliation through a documented bi-directional sync architecture. When a bill payment is executed in Airbase (ACH, check, or virtual card), Airbase writes the payment back to Sage Intacct as a paired Bill plus Payment record, automatically clearing the open payable in the AP subledger and posting the corresponding cash or clearing account entry without manual re-keying. …

Limitations: The full body of the 'Sync Bill Payments to Sage Intacct' help article was not rendered by search, so the precise field mapping (payment date, reference number, clearing account designation) …

Requirement evaluated: Virtual card program with rebate revenue; we want to shift 30%+ of spend to virtual card

For a $120M multi-location services company looking to shift 30%+ of spend to virtual card, Stampli offers two complementary native mechanisms within Stampli Direct Pay. The first is Stampli Card: when an invoice is approved, the AP team can pay the vendor using a single-use virtual card generated per transaction; the vendor receives card details via the Stampli Vendor Portal or a secure link and processes it to collect funds. Vendor Managers can invite vendors to accept card payments in bulk from the Vendor Management screen. …

Limitations: The rebate ceiling is documented at 'up to 1%' with no publicly enumerated volume tiers, so the buyer cannot negotiate a higher rate through platform volume alone; actual rebate earned will also depend on whether vendors are enrolled in the Paymode network (for E-Payments) …

Requirement evaluated: Per-vendor duplicate sensitivity configuration for vendors that legitimately reuse invoice numbers (e.g., recurring rent or utility billing)

For a services company processing 1,800 invoices per month across recurring vendor categories like rent and utilities, Airbase provides system-level duplicate invoice detection: the platform automatically flags potential duplicate invoices by comparing attributes including invoice number, vendor, and amount at the time of bill creation. This operates during the pre-processing legitimacy check (Stage 1 of the pre-processing journey) before a bill is posted to Sage Intacct. …

Limitations: For this buyer's 45% non-PO invoice mix, which includes utilities, subscriptions, and insurance policies that commonly reuse invoice numbers on a recurring cycle, Airbase's uniform duplicate detection will generate false-positive flags on legitimate invoices with no documented per-vendor override or sensitivity configu …

Requirement evaluated: Per-vendor duplicate sensitivity configuration for vendors that legitimately reuse invoice numbers (e.g., recurring rent or utility billing)

For a services company processing recurring vendor invoices from landlords, utilities, and subscription providers who legitimately reuse invoice numbers, Stampli's Billy the Bot runs a three-stage duplicate detection process. At the registration stage, Billy separates flags into two categories: 'actual duplicates' (invoice number + vendor name + invoice year/date all match, which triggers a hard warning requiring cancellation or editing to proceed) and 'potential duplicates' (any other combination of three matching fields). …

Limitations: The per-vendor disable setting covers only the 'potential duplicate' warning tier; the 'actual duplicate' hard flag (triggered by an exact match of invoice number, vendor name, and invoice year) …

Requirement evaluated: SOC 2 Type II certification (current, not in-progress)

For a $120M multi-location services company evaluating security posture before committing to an AP automation platform, Airbase (now operating under Paylocity following acquisition) maintains an annually renewed SOC 2 Type II attestation conducted by independent, reputable CPA firms. The official Airbase security policy page states that audits cover controls related to financial reporting, security, confidentiality, and availability, with each control tested for both design appropriateness and operating effectiveness. …

Limitations: Because Airbase was acquired by Paylocity relatively recently, buyers should confirm during the sales process that the SOC 2 Type II report scope explicitly covers the Airbase spend management modules (AP automation, bill pay, guided procurement) …

Requirement evaluated: Data encryption at rest and in transit

For a multi-location services company moving from manual email-and-spreadsheet AP to an automated platform, data protection must cover every touchpoint: invoice ingestion, in-platform processing, ERP sync to Sage Intacct, and payment execution. Stampli addresses all of these on its published Security Policy and Practices page. All data sent to or from Stampli is encrypted in transit using 256-bit encryption. API and application endpoints are TLS/SSL only, using only strong cipher suites. Data at rest is encrypted using an industry-standard AES-256 encryption algorithm. …

Limitations: Stampli's security policy page does not specify the minimum TLS version enforced (e.g., TLS 1.2 vs. 1.3), nor does it detail key management practices such as rotation schedules or HSM usage; buyers with formal information security policies requiring those specifics should request Stampli's full security whitepaper or d …

Requirement evaluated: Support for Sage Intacct dimensions: Location, Department, Class, Project, Customer, and custom dimensions

For your two-entity Sage Intacct environment, Airbase codes invoices (bills) using a system of Line Level Tags and Transaction Level Tags that map to Sage Intacct's dimension fields. The bill export documentation explicitly lists Department and Location as Sage Intacct-specific dimension fields carried on bill transactions, and a separate help article confirms that Sage Intacct users can set Project as a GL line-level tag, meaning Project coding can be applied per invoice line to support split allocations across your 6 locations and subcontractor projects. …

Limitations: Airbase's documented Sage Intacct dimension coverage is limited to Department, Location, and Project; Class, Customer, and any user-defined/custom dimensions the buyer has configured in Sage Intacct are not documented as supported in the bill coding or sync workflow, meaning those dimensions would require manual coding …

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: Multi-entity support within the integration; we operate 2 entities in Intacct and plan to add a third

For your 2 Intacct entities (with a third coming), Stampli connects once to Intacct through a Web Services user and syncs both the top-level organization and entity data, including vendors, GL accounts, locations and POs, into a single Stampli account. Stampli uses a Web Service User to automatically sync top level organization and entity data into Stampli. Stampli mirrors Intacct's multi-entity hierarchy in one unified platform and imports and enforces the same entity-level user restrictions configured in Intacct. …

Limitations: Stampli pays from one entity at a time: invoices from different locations or bank accounts become separate payments, even for the same vendor, and credits and prepayments cannot cross entities. …

Requirement evaluated: Budget data pulled from NetSuite for real-time budget enforcement

For a $250M tech company replacing email-and-Slack approvals with a formal procurement system, Airbase offers genuine pre-approval spend controls through its Spend Controls module: finance administrators configure hard-block and soft-warning policies, spending limits by role and expense type, and card-level limits on virtual and physical cards, all of which fire at the point of requisition submission or card use. The NetSuite integration is deep and bi-directional for GL coding: Airbase pulls chart-of-accounts dimensions (departments, classes, custom segments) …

Limitations: The budget enforcement mechanism in Airbase is configured within Airbase, not pulled live from NetSuite's budget records, so the buyer cannot use NetSuite as the single source of truth for budget limits. …

Requirement evaluated: Budget data pulled from NetSuite for real-time budget enforcement

For a $250M company currently running all budget oversight through NetSuite, Stampli offers a fully functional internal Budget Management module that enforces spend before commitment: when an employee submits a purchase request or a PO line is created, Stampli displays the applicable allocated, committed, spent, and remaining amounts in real time and can warn or hard-block a transaction when the budget would be exceeded. Stampli's Budget Management provides real-time visibility and control over organizational spending, allowing finance leaders to make informed spending decisions before a purchase occurs, with budget oversight integrated directly into the approval workflow. …

Limitations: The buyer's core requirement is budget data pulled from NetSuite for enforcement, but Stampli's documented limitation is that its budgets do not synchronize with an ERP budget module (Stampli Budget Management help article, updated 2026-07-13). …

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

For a technology company coming from a fully manual, email-and-Slack approval environment, Airbase's AP Automation module covers the full matching journey your AP team needs. Invoices arrive via email, bulk upload, or the vendor portal; OCR and AI extract line-level data automatically. The platform then runs automated 2-way matching (PO vs. invoice) for service purchases where no goods receipt exists, and automated 3-way matching (PO, goods receipt, and invoice) for direct materials spend, comparing price and quantity against tolerance thresholds and flagging duplicates and partial receipts. …

Limitations: Public documentation from Airbase describes tolerance thresholds as part of the matching logic, but granular configuration options (e.g., whether tolerance rules can be set by percentage vs. dollar amount at the line-item vs. header level, or per-vendor or per-category) …

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

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

Limitations: Stampli does not offer a structured 'condition' dropdown or inspection field; condition documentation relies on free-text comments and photo attachments per PO line, which satisfies the functional need but is less structured than a formal quality-inspection field. …

Requirement evaluated: PO change order workflow: amendments require re-approval if they exceed original amount by more than 10% or $5,000

For a finance team that wants PO amendments to go back for approval only when they grow more than 10% or $5,000 over the original, Airbase has approval rules but nothing documented that works on the size of the change. Airbase Approval Policy rules combine conditions (for example, department and a spend amount such as 'greater than or equal to USD 500') with an ordered list of approvers. POs created in Airbase can go through the approval cycle if the Approval Policy dictates it, and requests go to approvers in the order listed in the rule. Policies for purchase orders can be specific to a department, spend threshold, or expense category. Airbase works at the PO request and approval stage, then bill matching and receipts. Receipts are created against POs, and PO and receipt details sync to NetSuite every 6 hours. I found no public help article describing a change-order or amendment flow that compares the amended total to the original PO and re-triggers approval on a percentage or dollar variance.

Limitations: Approval thresholds are set on a spend amount. The public documentation does not show a condition for 'amended total exceeds original by more than 10% or $5,000', so the buyer would likely need a workaround. That could be a threshold on the new total, or a manual re-request or Workflow Builder process. The documentation also does not say what happens to approval status when an already-approved PO is edited.

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: PO change order workflow: amendments require re-approval if they exceed original amount by more than 10% or $5,000

For this $250M technology company, the key question is whether Stampli can automatically detect that an already-approved PO has been amended, compute the delta from the original approved amount, and re-route that PO through an approval chain when the delta exceeds 10% or $5,000 (whichever comes first). Stampli's documented approval engine handles initial PO request routing with configurable dollar thresholds and condition-based rules: it can assign approvers based on amount, department, vendor, and other criteria, and it supports multi-level escalation. …

Limitations: No documented evidence was found of a Stampli mechanism that fires on PO amendment, computes the delta from the originally approved PO amount, and enforces re-approval when the delta exceeds either 10% or $5,000; without this specific change-order re-approval trigger, the buyer would need to rely on manual process disc …

Requirement evaluated: Hosted catalog for frequently purchased items with pre-negotiated pricing (office supplies, IT peripherals, standard software)

This $250M technology company needs employees to open a pre-loaded shopping interface, select pre-negotiated items (office supplies, IT peripherals, standard software), and have contract pricing automatically populate the requisition -- the mechanism that prevents the maverick spend currently running at 35%. Airbase's procurement module does not provide this. Its guided procurement capability operates as a form-based intake and stakeholder routing layer: Airbase guides employees to gather the right information and documentation needed by all stakeholders before a purchase is made, with a configurable process that reflects company policies and responds to different transaction types. …

Limitations: Without a hosted catalog, employees at this company would still enter free-text descriptions and choose vendors manually inside Airbase intake forms -- the same pattern that currently produces 35% maverick spend, now with a PO wrapper but no price or supplier control. …

Requirement evaluated: Price comparison when same item is available from multiple sources

For your move from email and Slack requests to controlled buying, Stampli gives requesters price-bearing sources inside the purchase request, but no documented tool that compares one item's price across vendors. Admins keep preferred item lists per request type with an editable name, price and link (Stampli Preferred Items page), and AI item suggestions can be limited to uploaded catalogs or preferred lists, with rates drawn from catalog costs (Stampli AI-Powered Item Suggestions page). Requesters can also choose Shop vendor sites inside a request and punch out to Amazon Business, where they see live pricing and the organization's negotiated pricing. …

Limitations: I found no side-by-side or ranked comparison of the same item across catalogs, punchout vendors or preferred-item entries. Your requesters would have to open each punchout or catalog source separately and compare prices themselves, which weakens the push to consolidate 800+ vendors toward fewer than 300. …