# Procure to pay explained: steps and AP tool coverage **URL:** https://payablesbrief.com/guides/procure-to-pay/ **Published:** 2026-11-12 **Modified:** 2026-11-12 **Author:** Payables Brief desk > Procure to pay explained step by step, with which of 22 AP platforms cover requisition, purchase order and goods receipt. --- Guide # Procure to pay explained: steps and AP tool coverage Procure to pay runs from purchase request to payment. 17 of 22 AP platforms name a requisition step, and 9 of 22 cover requisition, purchase order and receipt. [Payables Brief desk](https://payablesbrief.com/about/) Updated 12 November 2026 In brief - Procure to pay (P2P) runs from a purchase request to payment: requisition, approval, purchase order, receipt, invoice match and payment. - AP automation starts at the invoice, and procure to pay starts at the request. - 17 of 22 AP platforms name a requisition step, 14 create purchase orders and 9 create receipts. - 5 of 22 start at the invoice: Melio, Nanonets, Routable, Vic.ai and MineralTree. - 9 of 22 cover requisition, purchase order and receipt, and 5 of them name all three without an add-on label: AvidXchange, Yooz, Coupa, Basware and Esker. Procure to pay (P2P) is the chain of steps from a purchase request to the payment of the supplier’s invoice: requisition, approval, purchase order, goods receipt, invoice match and payment. Accounts payable automation covers the last three, and procure to pay adds the first three. Of 22 AP platforms, 17 name a purchase-request step, 14 create purchase orders and 9 create goods receipts. Five start at the invoice: Melio, Nanonets, Routable, Vic.ai and MineralTree. Nine cover requisition, purchase order and receipt, and four of those nine sell them as add-ons. The shared document is the purchase order. It is created from an approved request, and the invoice is matched against it. [Three-way match](https://payablesbrief.com/guides/three-way-match/) adds the goods receipt as a third document. ## The steps from request to payment | Step | What happens | Document | | --- | --- | --- | | Requisition | An employee asks to buy something, with a reason, an amount and a cost center | Purchase requisition | | Approval | A budget owner or manager approves by amount or department | Approved requisition | | Purchase order | The approved request becomes an order sent to the supplier | Purchase order | | Goods receipt | The team confirms what arrived and in what quantity | Goods receipt or receiving note | | Invoice match | The supplier’s invoice is compared with the order and the receipt | Matched invoice | | Payment | The approved invoice is paid | Payment record | The first four steps belong to procurement and the team that orders. The last two belong to accounts payable. The [invoice approval workflow guide](https://payablesbrief.com/guides/invoice-approval-workflow/) covers who signs at the invoice step, and [OCR invoice capture](https://payablesbrief.com/guides/ocr-invoice-capture/) covers how the invoice gets into the system before the match. ## Purchase requisition and purchase order A purchase requisition is internal. It records that someone wants to buy something and routes that request for approval, and nothing is committed to a supplier yet. A purchase order is external. It goes to the supplier, states the items, prices and terms, and becomes the document the invoice is checked against. A purchase order and an invoice differ in direction. The order is the buyer’s commitment to buy, and the invoice is the supplier’s request for payment. An invoice with no purchase order behind it is a non-PO invoice, and it goes straight to approval without a match. ## Which AP vendors cover which step Figures as of 12 November 2026. “Yes” means the vendor names the step in its product. “Some plans” and “Add-on” mean it sits on a higher plan or costs extra. “Partial” means the step is only partly in the product, such as receipts imported from an ERP. The last four rows are procure-to-pay vendors with their own [cost records](https://payablesbrief.com/cost/). | Vendor | Requisition | PO creation | Goods receipt | Source | | --- | --- | --- | --- | --- | | [AvidXchange](https://payablesbrief.com/cost/avidxchange/) | Yes | Yes | Yes | [avidxchange.com/products/avidbuy](https://www.avidxchange.com/products/avidbuy/) | | [Airbase](https://payablesbrief.com/cost/airbase/) | Yes | No credit | No credit | [paylocity.com/products/finance/guided-procurement](https://www.paylocity.com/products/finance/guided-procurement/) | | Basware | Yes | Yes | Yes | [basware.com/en/solutions/e-procurement](https://www.basware.com/en/solutions/e-procurement/) | | [BILL](https://payablesbrief.com/cost/bill-com/) | Some plans | Some plans | No credit | [bill.com/pricing](https://www.bill.com/pricing) | | [Brex](https://payablesbrief.com/cost/brex/) | Yes | Some plans | No credit | [brex.com/support/managing-purchase-orders](https://www.brex.com/support/managing-purchase-orders) | | [Corpay](https://payablesbrief.com/cost/corpay/) | Yes | Yes | No credit | [corpay.com/ap-automation/po-automation](https://www.corpay.com/ap-automation/po-automation) | | [Coupa](https://payablesbrief.com/cost/coupa/) | Yes | Yes | Yes | [coupa.com/products/procure-to-pay/procurement](https://www.coupa.com/products/procure-to-pay/procurement/) | | [Emburse](https://payablesbrief.com/cost/emburse/) | Add-on | Yes | Add-on | [emburse.com/products/enterprise/invoice-management](https://www.emburse.com/products/enterprise/invoice-management) | | Esker | Yes | Yes | Yes | [esker.com/solutions/procurement](https://www.esker.com/solutions/procurement/) | | [Medius](https://payablesbrief.com/cost/medius/) | Yes | Yes | No credit | [medius.com/solutions/medius-procurement-solutions](https://www.medius.com/solutions/medius-procurement-solutions/) | | Melio | No credit | No credit | No credit | [meliopayments.com/pricing](https://meliopayments.com/pricing/) | | [MineralTree](https://payablesbrief.com/cost/mineraltree/) | No credit | No credit | No credit | [support.mineraltree.com](https://support.mineraltree.com/hc/en-us/articles/218112883-Purchase-Order-Matching) | | Nanonets | No credit | No credit | No credit | [nanonets.com/solutions/operations](https://nanonets.com/solutions/operations) | | [Paystand](https://payablesbrief.com/cost/paystand/) | Yes | No credit | No credit | [paystand.com/payables](https://www.paystand.com/payables) | | Quadient AP | Some plans | Some plans | Partial | [quadient.com/en-us/ap-automation-plans](https://www.quadient.com/en-us/ap-automation-plans) | | [Ramp](https://payablesbrief.com/cost/ramp/) | Add-on | Add-on | Add-on | [support.ramp.com/purchases-orders-in-ramp](https://support.ramp.com/purchases-orders-in-ramp) | | [Rillion](https://payablesbrief.com/cost/rillion/) | Add-on | No credit | No credit | [rillion.com/pricing](https://www.rillion.com/pricing/) | | Routable | No credit | No credit | No credit | [routable.com/features/po-matching](https://www.routable.com/features/po-matching/) | | [Stampli](https://payablesbrief.com/cost/stampli/) | Add-on | Add-on | Add-on | [stampli.com/procurement](https://www.stampli.com/procurement) | | [Tipalti](https://payablesbrief.com/cost/tipalti/) | Add-on | Add-on | Add-on | [tipalti.com/procurement](https://tipalti.com/procurement/) | | Vic.ai | No credit | No credit | No credit | [vic.ai/accounts-payable/po-matching](https://www.vic.ai/accounts-payable/po-matching) | | [Yooz](https://payablesbrief.com/cost/yooz/) | Yes | Yes | Yes | [getyooz.com/solution-p2p-automation](https://www.getyooz.com/solution-p2p-automation) | | [Precoro](https://payablesbrief.com/cost/precoro/) | Yes | Yes | Yes | [precoro.com/pricing](https://precoro.com/pricing/) | | [Procurify](https://payablesbrief.com/cost/procurify/) | Yes | Yes | Yes | [procurify.com/pricing](https://www.procurify.com/pricing/) | | [Zip](https://payablesbrief.com/cost/zip/) | Yes | Yes | No credit | [ziphq.com/products/procure-to-pay](https://ziphq.com/products/procure-to-pay) | | [Order.co](https://payablesbrief.com/cost/order-co/) | Yes | Yes | No credit | [order.co/procurement-software](https://www.order.co/procurement-software/) | Of the 22 AP platforms, 13 do not create a goods receipt in the product, and several of them match invoices to receipts that live in the ERP. MineralTree states that purchase orders and receipts stay in the accounting system, with MineralTree matching against them. Routable’s matching can hold a payment while a bill waits for a receipt, and it does not create the receipt. The pattern splits the 22 vendors in three. Five name the full chain without an add-on label: AvidXchange, Yooz, Coupa, Basware and Esker. Four sell it as add-ons: Ramp, Tipalti, Stampli and Emburse. The other thirteen cover part of the chain or none of it, and five of them start at the invoice. ## What the front half costs Procurement is a separate line at Ramp, Tipalti and Stampli. [Precoro](https://payablesbrief.com/cost/precoro/) lists Core from $499 a month and Automation from $999, billed annually, and its AP Module is a separate product from $499. [Ramp](https://payablesbrief.com/cost/ramp/) lists $15 per user a month on its Plus plan plus a platform fee. [Tipalti](https://payablesbrief.com/cost/tipalti/) lists $99 a month for Accounts Payable. Neither lists a price for its procurement add-on. Order.co prints a flat fee of $1,000 to $5,000 a month on an annual contract for its procurement and AP platform. Coupa, Procurify, Medius, Airbase and Zip quote only. The [procure-to-pay software ranking](https://payablesbrief.com/best/procure-to-pay-software/) orders nine tools by list price, and the [Coupa alternatives ranking](https://payablesbrief.com/best/coupa-alternatives/) orders eight by how much of the chain they cover. AP-only teams with no purchase orders can skip both and start from the [AP automation ranking](https://payablesbrief.com/best/ap-automation-software/). ## Where procure to pay joins AP The purchase order is where the two halves join. An invoice with a purchase order can be matched automatically, and one without goes to a person. Of 22 AP platforms, 17 name three-way matching, so the match step is covered far more widely than the steps before it. Vendor master data is the other join. A new supplier needs a W-9, a tax ID check and verified bank details before the first purchase order goes out, and the [vendor onboarding software ranking](https://payablesbrief.com/best/vendor-onboarding-software/) compares the platforms on those four checks. The ERP sets which documents sync, and the [NetSuite](https://payablesbrief.com/erp/netsuite/) and [Sage Intacct](https://payablesbrief.com/erp/sage-intacct/) hubs list which AP vendors connect. ## Frequently asked questions - What is procure to pay? Procure to pay is the chain from a purchase request to payment: requisition, approval, purchase order, goods receipt, invoice match and payment. It joins the buying side to the accounts payable side with the purchase order as the shared document. - What is the difference between a purchase requisition and a purchase order? A purchase requisition is an internal request to buy something, and it needs approval. A purchase order is the document sent to the supplier once the request is approved, and it states what is ordered, at what price and on what terms. - What is the difference between a purchase order and an invoice? A purchase order is the buyer's commitment to buy, and an invoice is the supplier's demand for payment. The invoice is matched against the purchase order, and against the goods receipt in three-way match, before it is paid. - What is the difference between procure to pay and AP automation? Procure to pay covers the purchase request, approval, purchase order and receipt before an invoice arrives. AP automation starts at the invoice: capture, matching, approval and payment. - Which AP vendors cover the whole procure-to-pay chain? 9 of 22 AP platforms cover requisition, purchase order and receipt: AvidXchange, Yooz, Coupa, Basware and Esker name all three without an add-on label, and Ramp, Tipalti, Stampli and Emburse sell them as add-ons.