PartialProcurify
Requirement evaluated: PO status tracking: from approved through acknowledged, received, invoiced, and closed
For a finance team that wants to follow each PO from approval to close, Procurify tracks most of the chain but not every stage. Approved requests move into the Procurement list and become POs, and the PO can be emailed to the vendor, either automatically or manually. Purchasers select approved items, click Add to List, then Create Purchase Order or Create and Email PO. Procurify's fact sheet also says it tracks purchases from request to approval, PO, invoice, and payment. Receipt and invoicing are tracked per line: each line carries a Billing Status (Not Billed, Partially Billed, Billed, Over-Billed) and a Receive Status (Not Received, Partially Received, Received, Over-Received, Auto-Received). The Spend Insights PO-to-Bill dashboard follows every approved PO line from ordered, to received, to billed. Closing is mostly tied to receiving: POs automatically close when their items are fully received, and users can close or reopen a PO manually. Invoice matching against the PO runs through automated three-way matching.
Limitations: I found no vendor-acknowledgement status in Procurify's help center. The nearest feature is PO email tracking, which shows Failed to send, Sent on, or Open on, and confirms only that the recipient's email server received the message, so it does not show that the vendor accepted the order. The PO's closed state follows full receipt or a manual close, not completion of invoicing. A PO closes on full receipt even if bills are outstanding, and the billed status sits at line level. The dashboard also only counts receiving done in Procurify (received values come from receiving in Procurify only), so a team that doesn't receive in Procurify will see billed lines marked Not Received.
Re-verified 2026-11-03 against current vendor documentation. First evaluated in
GEP vs Procurify vs Basware for Procurement & P2P UnclearNo public documentation foundStampli
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 …