Ivalua vs Stampli

Requirement evaluated: Vendor self-service portal: new vendor registration, W-9/W-8 submission, banking detail entry, invoice submission, payment status inquiry

For a multi-location services company replacing email-and-spreadsheet vendor onboarding, Ivalua delivers a dedicated, buyer-branded Supplier Portal that covers every sub-requirement the buyer named. New vendors register themselves directly through the portal (no AP staff involvement required to initiate), completing company information, tax IDs, and compliance attestations as part of a guided onboarding workflow; real customer implementations confirm a 'Register Now' self-service entry point with tax country and tax organization fields that trigger additional required documentation. …

Limitations: W-9 and W-8 collection is delivered through Ivalua's configurable document-upload and questionnaire framework during onboarding, rather than a native IRS e-form with automated TIN matching against IRS records; this covers the buyer's stated need for W-9/W-8 submission, but if the buyer requires automated TIN verificati …

Requirement evaluated: Vendor self-service portal: new vendor registration, W-9/W-8 submission, banking detail entry, invoice submission, payment status inquiry

For a $120M services company with a 3-person AP team currently handling all vendor communication by email, Stampli provides a dedicated external-facing Vendor Portal where suppliers log in with their own credentials to submit invoices directly, track invoice processing and payment status in real time, enter and update banking details (subject to an internal AP approval gate before changes take effect), and communicate with the AP team via in-portal messaging tied to specific invoices. …

Limitations: W-8 series coverage for foreign vendors is referenced in Stampli's general vendor management content but is not explicitly confirmed as a configured requirement in Advanced Vendor Management product documentation the same way W-9 is; buyers with a material volume of foreign vendors should verify W-8 form collection in …

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

For a $120M services company running two Sage Intacct entities, Ivalua addresses duplicate invoice detection through its Invoice Hub, a centralized intake layer that sits above connected ERP entities and processes all invoices before any posting occurs. Ivalua's Invoice-to-Pay product page explicitly names 'Trap duplicate invoices' as a named Invoice Hub control, alongside fraud blocking and tax validation; these checks fire at the point of submission, before an invoice reaches either Sage Intacct entity. …

Limitations: Ivalua's public documentation does not specify the exact field-level matching combination used for duplicate detection (vendor ID, amount, date, invoice number together) …

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

For a $120M services company running 2 Sage Intacct entities through a single Stampli account, Billy the Bot performs duplicate detection in three sequential stages before any invoice reaches the ERP. At upload, Billy checks whether a prior invoice in the system has the same file name, size, and content; if so, the invoice is blocked and an email notification fires. After coding and registration, Billy checks invoice number, vendor name, invoice date, and total amount against existing invoices; if any three of those four fields match, a duplicate warning appears on the invoice details screen. …

Limitations: The "actual duplicate" classification requires all three of invoice number, vendor name, and invoice year to match; the "potential duplicate" flag fires when any three of the four documented fields (invoice number, vendor name, invoice date, total amount) …

Requirement evaluated: Policy compliance reporting: percentage of spend through approved channels, contract compliance rate, approval policy adherence

For a $250M tech company currently running 35% maverick spend outside any procurement system, Ivalua addresses all three compliance reporting dimensions through its dedicated Spend Analysis module and integrated KPI dashboards. The Spend Analysis module aggregates data from ERP systems, AP, invoices, P-cards, travel, and external third-party sources into a single spend workbench, explicitly positioned as distinct from and more complete than ERP-native reports — meaning spend that never entered a PO in NetSuite can still be classified and surfaced once AP/invoice data is fed in. From that unified data set, Ivalua's procurement dashboards track: (1) …

Limitations: Approval policy adherence reporting is most complete for spend flowing through Ivalua's own intake and P2P workflows going forward; for the historical maverick spend that bypassed POs entirely before implementation, compliance metrics depend on the quality and completeness of AP/invoice data imported from NetSuite, and …

Requirement evaluated: Policy compliance reporting: percentage of spend through approved channels, contract compliance rate, approval policy adherence

For a $250M technology company trying to measure compliance after years of email-based approvals and 35% maverick spend, Stampli addresses this requirement across two layers. First, the platform maintains a comprehensive, timestamped, immutable audit trail of every request, approval, rejection, reassignment, and exception across both the procurement and AP sides of P2P: Stampli logs who took what action, when, and any comments provided, including initial submissions, approvals, rejections, questions, reassignments, and modifications; these records cannot be modified or deleted, ensuring data integrity for compliance and audit purposes. …

Limitations: The two most specific metrics the buyer named, percentage of spend through approved channels and contract compliance rate, are not documented as named, calculated report outputs in Stampli. Spend that bypasses Stampli entirely (the buyer's current 35% problem) …

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

For a $250M tech company running NetSuite, Ivalua's Integration Hub provides a built-in integration layer with bidirectional data flow support via APIs, ETL, and EAI, eliminating the need for third-party middleware. Once a PO is approved in Ivalua, the platform pushes PO data (numbers, line items, status) to the connected ERP automatically, and can receive payment and invoice status updates back in return, as documented in Ivalua's PO automation content: 'automation tools sync data bi-directionally using APIs or native connectors.' However, Ivalua's documented prebuilt ERP connectors name SAP (a dedicated Plug & Play connector), Oracle, Workday, and Microsoft Dynamics. …

Limitations: NetSuite is absent from Ivalua's enumerated list of prebuilt ERP connector targets (SAP, Oracle, Workday, Microsoft Dynamics), meaning the buyer should expect an implementation services engagement to configure the NetSuite API/ETL connection rather than a plug-and-play deployment; timeline and depth of the payment-stat …

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

For a company currently running all procurement through email and manually creating POs in NetSuite, Stampli addresses this requirement across two distinct flows. First, on the upstream side: Stampli's Procurement module lets employees submit purchase requests that go through configurable approval workflows; once approved, Stampli exports approved data back to NetSuite to create purchase orders, mirroring the ERP's PO requirements and reducing manual entry. Buyers can also choose whether to approve POs in Stampli before exporting to the ERP, or use NetSuite's built-in approval workflows, providing flexibility to match the organization's processes. …

Limitations: The Procurement module (which handles upstream PO creation and export to NetSuite) is a separately licensed add-on to Stampli's core AP product; buyers starting only with invoice processing would need to add this module to cover the full approved-PO-push side of this requirement. …

Requirement evaluated: Intake forms configurable by purchase category (IT hardware, software, professional services, facilities, marketing) with category-specific required fields

For a technology company replacing ad-hoc email/Slack procurement with a structured intake layer, Ivalua's Intake Management module directly addresses this requirement. The platform's no-code configuration layer lets procurement administrators define distinct request types per spend category; IT hardware, software, professional services, facilities, and marketing each get their own form template with category-specific required fields. …

Limitations: Ivalua's configuration depth is an enterprise capability: third-party reviews consistently flag a steep learning curve and longer implementation timelines, meaning this buyer will need professional services investment to properly stand up five category-specific form templates and their conditional field logic. …

Requirement evaluated: Intake forms configurable by purchase category (IT hardware, software, professional services, facilities, marketing) with category-specific required fields

For this $250M technology company coming from email-based purchasing, Stampli's Employee Purchasing Portal addresses the category-specific intake requirement through configurable 'request types,' each carrying its own distinct field set, required fields, and policy guidelines. Administrators can configure different request types for various departments, where IT purchases require different information than marketing services or travel requests. Different policies can be established for different request types, displayed directly within the request form, and enforced through required fields, spending limits, preferred vendor requirements, or mandatory approvals. …

Limitations: Stampli's category intake operates via distinct request-type templates rather than within-form conditional show/hide logic; buyers requiring sub-category branching (e.g., a software request that reveals SaaS vs. perpetual license sub-fields) may hit a configuration ceiling. …

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: Budget hierarchy: company → division → department → project → GL code

For a $250M tech company needing budget control at company, division, department, project, and GL code levels, Stampli's Budget Management module lets finance define budget lines structured by department, GL account, project, company entity, or combinations of those dimensions, with each line carrying allocated amounts by fiscal period. Auto-assignment rules (supporting up to 7 configurable fields drawn from Stampli PO, ERP PO, and invoice header and line fields, including subsidiary, vendor, and GL account) automatically match purchase requests to the correct budget line at submission time, before any PO or commitment is created. …

Limitations: Stampli's documented budget model uses flat multi-dimensional budget lines (e.g., a department + project + GL combination on one line) rather than a strict parent-child tree where a company-level envelope automatically constrains division envelopes, which in turn constrain department envelopes; the buyer's full 5-level …

Requirement evaluated: Automated three-way matching: PO to receipt to invoice with configurable tolerance (2% price, 5% quantity)

For a $250M technology company currently reconciling POs manually in NetSuite, Ivalua's AP Automation module handles the full three-way match within a single Source-to-Pay platform. Three-way matching is a core part of Ivalua's PO automation: the platform links the PO, invoice, and goods receipt into a single workflow for real-time comparison of quantities, prices, and delivery confirmations automatically, and if everything aligns the invoice moves straight through for payment. …

Limitations: While Ivalua documents configurable 'cost tolerance' and 'volume tolerance' as distinct exception types, public documentation does not explicitly confirm that these two tolerance percentages (2% price, 5% quantity) …

Requirement evaluated: Automated three-way matching: PO to receipt to invoice with configurable tolerance (2% price, 5% quantity)

For this $250M technology company moving from email-based approvals to a formal P2P workflow, Stampli's PO Matching module covers the full three-way match chain: PO, goods receipt (receiving records), and vendor invoice. Invoices are matched to purchase orders and receiving records, and the system flags discrepancies so they can be reviewed before payment. The matching engine operates at the line level, not just header totals: it automatically identifies exact matches between header and line-level PO data, matches items with identical descriptions, quantities, rates, and amounts, and flags discrepancies when line items do not match. …

Limitations: The buyer requires two independently configurable tolerance thresholds (2% price, 5% quantity as separate parameters); Stampli's public product documentation confirms 'customer-defined tolerances' but does not specify whether price and quantity tolerances are set independently or whether tolerances can be configured pe …

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 escalation: if approver has not acted within 48 hours, escalate to their manager with notification

For a 3-person AP team currently managing approvals through email chains, Stampli replaces that process with a configurable workflow engine that monitors approver response time and automatically acts when SLAs lapse. Stampli's documented escalation model works in two stages: automated reminders fire first, then, if the approver has still not acted after the configured wait period, escalation rules reroute the approval to an alternate or the approver's manager after the SLA lapses, with the escalation logged in the audit trail. …

Limitations: The most detailed escalation configuration documentation available from Stampli's help center describes this mechanism in the context of procurement request workflows; the invoice-specific approval help article (help.stampli.com/en/articles/2992566-approving-invoices) …

Requirement evaluated: Approval bottleneck analysis: which approvers are slowest, which invoice types take longest

For a 3-person AP team at a $120M multi-location company currently running on email-chain approvals with no baseline metrics, Ivalua provides approval workflow analytics through its AP Automation module and its Analytics and Insights reporting layer. Ivalua includes an AP-centric dashboard with analytics so the team can monitor performance within the AP Automation workflow. Automating invoice intake, routing, and approvals reduces cycle times, and real-time dashboards alongside audit trails give stakeholders full visibility into invoice status and potential bottlenecks. …

Limitations: The buyer's requirement has two dimensions: category-level cycle time (documented as a platform capability) and named-approver-level response time ranking (not documented as a pre-built report; requires custom configuration of the Analytics and Insights module). …

Requirement evaluated: KPI tracking: average days to approve, touchless rate, cost per invoice, exception rate, discount capture rate

For your 3-person AP team running about 1,800 invoices a month across 2 Intacct entities (soon 3), Stampli's Dashboards & Reports area is the in-product place to track KPIs, and it sits in the pre-processing stage between invoice arrival and ERP export. The Invoice Lifecycle Dashboard shows average lifecycle time, average time at each stage (Coding & Routing, Invoice Approvals, authorized for payment), and rejected and canceled invoices with top rejection reasons. …

Limitations: I found no documented in-product tile or report for touchless rate, cost per invoice or discount capture rate. Exception rate is only visible as rejections and cancellations (plus a 'rejected for incorrect coding' count), not as a rate against total volume or as a mismatch or hold rate. …

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: 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: Complete audit trail: every action timestamped with user ID, viewable by invoice or by user

For a multi-location services company currently relying on email chains and manual keying with no audit record outside Sage Intacct, Ivalua provides a built-in audit trail that operates entirely within its AP automation layer, upstream of the ERP sync. As Ivalua's own product documentation describes, every action, edit, and approval is automatically recorded, creating a transparent, verifiable history for every invoice. …

Limitations: Help-center documentation confirming a dedicated 'view by user' audit interface (as distinct from filtering AP reports by user) was not located during research; the cross-user axis appears to be surfaced through Ivalua's AP reporting module rather than a standalone user-activity log, so your team should confirm during …

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

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: Learning capability: accuracy should improve over time on our specific vendor invoice formats

For a multi-location services company currently doing all capture manually, Ivalua's Invoice Hub uses document agents that apply hybrid OCR and LLM techniques to read invoices based on document structure rather than fixed vendor templates, with the vendor claiming 95-97% extraction accuracy at the point of capture. The IVA agentic layer, launched via IVA Studio, claims platform-level self-improvement: it 'maintains memory of interactions, self-improving automatically,' and 'skills turn individual expertise into team capabilities, building institutional knowledge that compounds with every interaction.' At the extraction stage specifically, the LLM-based approach interprets layouts semanticall …

Limitations: The specific mechanism this buyer's requirement calls for, where AP staff corrections feed back into a per-vendor extraction model that becomes measurably more accurate over time on that vendor's specific layout, is not documented in Ivalua's product materials; what is documented is platform-wide IVA 'compounding intel …

Requirement evaluated: Automatic extraction of: vendor name, invoice number, date, PO number, line items, amounts, tax, and payment terms

For a 3-person AP team currently keying 1,800 invoices per month from email and mail into Sage Intacct manually, Stampli's AI (Stampli AI, previously branded as Billy the Bot) takes over at the point of invoice receipt. Invoices arrive via email to a dedicated Stampli inbox or are uploaded directly; the AI then immediately extracts header and line-level fields without human intervention. Stampli's own product documentation confirms the extracted fields include vendor name, invoice number, PO number, line items, product descriptions, prices, credit/payment terms, and taxes, using a combination of OCR, machine learning, and natural language processing. …

Limitations: Line-item extraction accuracy on varied or lower-quality invoice formats (scanned paper, non-standard layouts from subcontractors or facilities vendors) improves over time as the system learns vendor-specific patterns; a third-party analysis notes that Stampli uses historical invoice data from specific vendors to impro …

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

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

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 …

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 …

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

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 …