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 SupportedZip
Requirement evaluated: PO status tracking: from approved through acknowledged, received, invoiced, and closed
For a $250M technology company replacing ad hoc email and Slack approvals, Zip covers the full PO lifecycle natively within its procure-to-pay platform. Once a purchase request clears the approval workflow, Zip automatically generates a PO and delivers it to the supplier through its Vendor App portal — this is the 'approved through acknowledged' handoff, where the supplier receives the PO directly in Zip's portal rather than via email. …
Limitations: Help-center documentation confirms that the supplier portal delivers POs and enables vendor-side interaction, but does not explicitly document a distinct 'acknowledged' status label that is updated by a supplier confirmation action separate from PO delivery — the acknowledged stage is effectively PO delivery to the Ven …