{"id":2105,"date":"2026-10-30T10:53:16","date_gmt":"2026-10-30T10:53:16","guid":{"rendered":"https:\/\/procureclix.com\/blog\/?p=2105"},"modified":"2026-11-13T06:20:45","modified_gmt":"2026-11-13T06:20:45","slug":"what-is-a-purchase-order","status":"publish","type":"post","link":"https:\/\/procureclix.com\/blog\/what-is-a-purchase-order\/","title":{"rendered":"What Is a Purchase Order? Guide, Process and Example"},"content":{"rendered":"<h2><span class=\"ez-toc-section\" id=\"Key_Takeaways\"><\/span>Key Takeaways<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li>A purchase order (PO) is a formal document a buyer sends to a supplier to request goods or services at agreed quantities, prices, delivery dates, and payment terms. It turns an internal request into an external commitment.<\/li>\n<li>A PO gives procurement, operations, receiving, and finance one shared version of the order, which helps prevent unauthorized spend, wrong deliveries, and invoice disputes.<\/li>\n<li>A usable PO carries a unique number, buyer and supplier details, specific line items, quantities and prices, delivery instructions, and terms. Vague line descriptions cause more disputes than pricing does.<\/li>\n<li>ProcureClix connects purchase requisitions, configurable approvals, <a href=\"https:\/\/procureclix.com\/blog\/rfi-vs-rfp-vs-rfq\/\">sourcing and RFx<\/a>, purchase orders, goods receipt, invoice processing, and three way matching in a structured, audit ready workflow, providing visibility from the initial request through downstream purchasing and invoice processes.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Introduction\"><\/span>Introduction<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Picture a Tuesday afternoon at a plant. A conveyor motor has failed, the line has lost half a shift, and the maintenance supervisor is not waiting on paperwork. They call a supplier they have used before, get a verbal price, and ask for overnight shipping. Three weeks later, accounts payable has a $6,800 invoice with no approved order, no agreed price to check it against, no proof of what arrived, and nobody willing to say \u201cyes, I own this.\u201d<\/p>\n<p>A purchase order prevents that conversation, not because paperwork is virtuous, but because five groups need the same facts. Procurement needs to know the price was negotiated, the requestor needs confidence the right part is coming, the supplier needs a firm instruction, receiving needs to know what arrives and when, and finance needs to know the money was committed on purpose. The mechanics are the same for a plant ordering bearings, a utility buying long-lead transformers, or a distribution center covering peak season.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"What_Is_a_Purchase_Order\"><\/span>What Is a Purchase Order?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A purchase order is a numbered commercial document issued by a buyer to a supplier that states the goods or services ordered, agreed pricing, quantities, delivery requirements, and payment terms. It is normally created after an internal <a href=\"https:\/\/procureclix.com\/blog\/what-is-purchase-requisition\/\">purchase requisition<\/a> has been approved. A requisition is an internal ask; a PO is an external commitment.<\/p>\n<p>Procurement is the whole discipline of sourcing, negotiating, and managing suppliers. Purchasing is the transactional slice of it, and the PO sits inside purchasing as the formal record that authorizes one specific buy. You can buy without a PO, but you lose the control and the audit trail. Once the appropriate approvals are complete, the PO is created and sent to the supplier, the requesting team relies on it to track the purchase, and accounts payable uses it to help validate the invoice.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"What_Information_Should_a_Purchase_Order_Include\"><\/span>What Information Should a Purchase Order Include?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Treat this as the minimum-fields list.<\/p>\n<table>\n<caption>Purchase order fields and why they matter<\/caption>\n<thead>\n<tr>\n<th>Field<\/th>\n<th>What it should show<\/th>\n<th>Why it matters<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>PO number<\/td>\n<td>A unique reference number<\/td>\n<td>Lets buyers, suppliers, receiving, and AP track the same order<\/td>\n<\/tr>\n<tr>\n<td>Buyer and supplier<\/td>\n<td>Legal entities, contacts, addresses<\/td>\n<td>Prevents orders or bills going to the wrong entity<\/td>\n<\/tr>\n<tr>\n<td>Line items<\/td>\n<td>Description, part number, or scope<\/td>\n<td>Reduces wrong-item and wrong-service disputes<\/td>\n<\/tr>\n<tr>\n<td>Quantity and price<\/td>\n<td>Quantity, unit of measure, agreed unit price<\/td>\n<td>Supports budget control and invoice matching<\/td>\n<\/tr>\n<tr>\n<td>Delivery details<\/td>\n<td>Ship-to location, date, receiving contact<\/td>\n<td>Gets goods to the right plant or dock<\/td>\n<\/tr>\n<tr>\n<td>Payment terms<\/td>\n<td>Net terms, currency, tax treatment<\/td>\n<td>Gives AP a basis for scheduling payment<\/td>\n<\/tr>\n<tr>\n<td>Terms and conditions<\/td>\n<td>Contract reference, warranty, quality requirements<\/td>\n<td>Ties the order to the commercial agreement<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The line description deserves extra attention. \u201cReplacement bearing\u201d tells a supplier almost nothing. A usable maintenance line includes the manufacturer part number, the specification or equivalent-approval rule, the unit of measure, and the required-by date. A PO does not need to restate every negotiated term. It can reference a contract number, statement of work, or catalog item and let that agreement carry the detail.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"How_Does_the_Purchase_Order_Process_Work\"><\/span>How Does the Purchase Order Process Work?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The process runs in seven steps. <a href=\"https:\/\/procureclix.com\/blog\/what-is-purchase-order-approval\/\">Approval rules and thresholds<\/a> differ by company, spend level, and category, but the handoffs stay broadly the same, whether you are buying gearboxes or contract welders.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"1_A_Team_Identifies_a_Need\"><\/span>1. A Team Identifies a Need<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A usable request includes the business need, quantity and unit of measure, required-by date, cost center or work order, and a preferred supplier if there is a reason for one. \u201cWe need tires\u201d is a conversation. \u201c24 EA, 295\/75R22.5 drive position, required 18 Nov, cost center 4120\u201d is a request someone can act on.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"2_The_Request_Becomes_a_Purchase_Requisition\"><\/span>2. The Request Becomes a Purchase Requisition<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A requisition is an internal request for approval to buy, and the PO is the external document sent after approval. The requisition exists so the commitment is reviewed before anyone tells a supplier to ship. Once a PO leaves the building you have committed, and renegotiating afterward is a weaker position. A non-catalog request may also <a href=\"https:\/\/procureclix.com\/rfq-software.html\">convert to an RFQ<\/a> before a PO is issued.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"3_The_Right_People_Approve_the_Spend\"><\/span>3. The Right People Approve the Spend<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Approval is where most of the control lives. Typical checks cover budget availability, delegated authority, supplier status, contract coverage, and technical sign-off. Proportion matters: for example, a routine $400 item might need one supervisor, while a $40,000 unplanned repair might pull in operations, finance, and procurement. Set thresholds from your own risk tolerance and delegation policy.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"4_Procurement_Creates_and_Sends_the_Purchase_Order\"><\/span>4. Procurement Creates and Sends the Purchase Order<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>The buyer builds the PO from the approved requisition, pulling pricing from the contract or catalog rather than retyping a quote. Wherever possible, the supplier should have the PO before they fulfill, because a PO raised after the goods arrive documents the purchase without controlling it. Whether you send it by email, portal, or EDI matters less than whether it is traceable.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"5_The_Supplier_Confirms_Changes_or_Rejects_the_Order\"><\/span>5. The Supplier Confirms, Changes, or Rejects the Order<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Issuing a PO is not the same as having an order. Suppliers push back on lead times, add minimum order quantities or freight, or propose substitutes. Ask for written confirmation of price, availability, and delivery date, especially for critical spares and long-lead materials, and keep it attached to the PO record.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"6_Your_Team_Receives_the_Goods_or_Confirms_the_Service\"><\/span>6. Your Team Receives the Goods or Confirms the Service<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Receiving confirms what actually arrived. For a partial receipt, record what came (8 of 10 gearboxes) and leave the line open, because closing a PO on close-enough paperwork is how you pay for gearboxes still in a supplier\u2019s warehouse. Services need a service-entry confirmation that the work was performed to scope.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"7_AP_Matches_the_Invoice_and_Schedules_Payment\"><\/span>7. AP Matches the Invoice and Schedules Payment<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><a href=\"https:\/\/procureclix.com\/resources\/glossary\/3-way-matching.html\">Three-way matching<\/a> checks whether what was ordered, received, and billed all agree. AP compares the PO, the receiving record, and the invoice, and schedules payment if they line up. Exceptions such as price variances, damaged goods, and duplicates are normal, but each needs a named owner and a resolution path, because an exception in a shared inbox is just aging.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"What_Does_a_Purchase_Order_Look_Like\"><\/span>What Does a Purchase Order Look Like?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A purchase order is typically a one-page commercial document: a header with buyer, supplier, delivery, and payment terms, numbered line items, and a notes field. This simplified, illustrative example is a plant maintenance order, the kind of buy that causes disputes.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Purchase Order No.<\/th>\n<td>PO-104582<\/td>\n<\/tr>\n<tr>\n<th>Buyer<\/th>\n<td>Northline Components, Plant 3<\/td>\n<\/tr>\n<tr>\n<th>Supplier<\/th>\n<td>Industrial Motion Supply Co.<\/td>\n<\/tr>\n<tr>\n<th>Ship to<\/th>\n<td>Northline Components, 1450 Foundry Road, Bay 4 Receiving<\/td>\n<\/tr>\n<tr>\n<th>Requested delivery<\/th>\n<td>15 December 2026<\/td>\n<\/tr>\n<tr>\n<th>Payment terms<\/th>\n<td>Net 30<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<table>\n<thead>\n<tr>\n<th>Line<\/th>\n<th>Description<\/th>\n<th>Qty.<\/th>\n<th>Unit price<\/th>\n<th>Total<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>1<\/td>\n<td>SKF 22218 EK spherical roller bearing, or approved equivalent<\/td>\n<td>4 EA<\/td>\n<td>$385.00<\/td>\n<td>$1,540.00<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td>Expedited freight<\/td>\n<td>1 LOT<\/td>\n<td>$175.00<\/td>\n<td>$175.00<\/td>\n<\/tr>\n<tr>\n<td><strong>Total<\/strong><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><strong>$1,715.00<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><em>Notes: Supplier must provide a certificate of conformity. Delivery appointment required.<\/em><\/p>\n<p>Each element does work. The PO number gives five teams one reference. The exact part number protects reliability, and \u201cor approved equivalent\u201d gives the supplier flexibility without letting them decide what is close enough. Freight on its own line means the charge was approved in advance, and the certificate requirement tells receiving what to check.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"What_Are_the_Main_Types_of_Purchase_Orders\"><\/span>What Are the Main Types of Purchase Orders?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>PO types define whether a PO covers one specific transaction, expected future demand, recurring purchases, or a contract-backed commitment.<\/p>\n<table>\n<caption>Types of purchase orders<\/caption>\n<thead>\n<tr>\n<th>PO type<\/th>\n<th>Best used when<\/th>\n<th>Example<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Standard<\/td>\n<td>You know the exact item, quantity, price, and delivery date<\/td>\n<td>12 replacement valves for a scheduled outage<\/td>\n<\/tr>\n<tr>\n<td>Planned<\/td>\n<td>You expect future purchases but not exact delivery dates<\/td>\n<td>Forecast monthly packaging material demand<\/td>\n<\/tr>\n<tr>\n<td>Blanket<\/td>\n<td>You buy recurring items from one supplier up to a limit or period<\/td>\n<td>A 12-month MRO supply agreement across plants<\/td>\n<\/tr>\n<tr>\n<td>Contract<\/td>\n<td>A supplier agreement sets terms and individual releases follow<\/td>\n<td>A contracted engineering-services provider<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Terminology is not standardized, so check how your ERP configures these types before you write policy. Blanket POs suit repeatable, low-risk spend like fasteners or lubricants, but they are a poor fit for open-ended \u201cmiscellaneous\u201d buying, where the limit becomes a budget people spend down.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"How_Is_a_Purchase_Order_Different_From_an_Invoice_Requisition_and_Sales_Order\"><\/span>How Is a Purchase Order Different From an Invoice, Requisition, and Sales Order?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Same transaction, four documents, two companies.<\/p>\n<table>\n<caption>Purchase-related documents compared<\/caption>\n<thead>\n<tr>\n<th>Document<\/th>\n<th>Created by<\/th>\n<th>Sent to<\/th>\n<th>Main purpose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Purchase requisition<\/td>\n<td>Internal requestor<\/td>\n<td>Internal approvers<\/td>\n<td>Requests permission to buy<\/td>\n<\/tr>\n<tr>\n<td>Purchase order<\/td>\n<td>Buyer or procurement<\/td>\n<td>Supplier<\/td>\n<td>Formally places and documents the order<\/td>\n<\/tr>\n<tr>\n<td>Sales order<\/td>\n<td>Supplier<\/td>\n<td>Supplier\u2019s internal teams<\/td>\n<td>Tells the supplier how to fulfill the order<\/td>\n<\/tr>\n<tr>\n<td>Invoice<\/td>\n<td>Supplier<\/td>\n<td>Buyer\u2019s AP team<\/td>\n<td>Requests payment after delivery or a milestone<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>In sequence: your plant submits a requisition, procurement turns it into a PO, and the supplier enters that PO into its own system as a sales order. After delivery the supplier sends an invoice, and AP runs the three-way match before paying. That is why PO numbers must be unique and appear on everything downstream.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Are_Purchase_Orders_Legally_Binding\"><\/span>Are Purchase Orders Legally Binding?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A PO can become legally binding when the supplier accepts it, but its legal effect depends on the PO terms, the underlying contract, applicable law, and how acceptance occurs. With a contract-backed PO, a master agreement governs and the PO is a release under it. With a standalone PO, the PO may form the contract once the supplier accepts or begins performance. With conflicting terms, your PO carries your terms and the supplier\u2019s acknowledgement carries theirs, a \u201cbattle of the forms\u201d that only surfaces in a dispute.<\/p>\n<p>For complex construction, engineering, utility capital projects, or multi-year service commitments, put <a href=\"https:\/\/procureclix.com\/solutions\/procurement-contract-management-software.html\">a proper contract<\/a> behind the PO and treat the PO as the release mechanism. This article offers operational guidance, not legal advice. For high-value, regulated, or disputed purchases, involve legal counsel.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"What_Are_the_Benefits_and_Limits_of_Using_Purchase_Orders\"><\/span>What Are the Benefits and Limits of Using Purchase Orders?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>POs give you <a href=\"https:\/\/procureclix.com\/blog\/automated-spend-analysis\/\">spend visibility<\/a>, clearer supplier instructions, approval control, invoice accuracy, and an audit trail, but only when they are raised before the buy and filled in properly.<\/p>\n<ul>\n<li><strong>Spend visibility:<\/strong> A PO shows committed spend before the invoice arrives, so finance can <a href=\"https:\/\/procureclix.com\/solutions\/procurement-spend-analysis-software.html\">track spend in-period<\/a> rather than in arrears.<\/li>\n<li><strong>Clear supplier instructions:<\/strong> Specific items, locations, and terms cut back-and-forth and fulfillment errors.<\/li>\n<li><strong>Approval control:<\/strong> A working PO process stops people committing company funds without the authority to do so.<\/li>\n<li><strong>Invoice accuracy:<\/strong> PO and receipt records give AP a basis for catching price variances, quantity mismatches, and duplicate billing.<\/li>\n<li><strong>Audit trail:<\/strong> There is an answer to who approved a purchase, what was ordered, and whether it arrived that does not depend on anyone\u2019s memory.<\/li>\n<\/ul>\n<p>The limits are just as real. <a href=\"https:\/\/procureclix.com\/blog\/what-is-purchase-order-automation-software-end-manual-po-chaos-today\/\">Manual processing<\/a> through email and spreadsheets creates version-control problems, so the control exists on paper but not in practice. After-the-fact POs document a purchase without preventing anything, and a PO with a vague description and the wrong price just formalizes bad information.<\/p>\n<p>A real-life example of the limits. A March 2023 internal audit at the City of York Council in the UK found that retrospective PO raising was still happening, an issue flagged in the previous audit too, with 55% of 2022 invoices dated on or before the PO date. The council\u2019s report to its audit committee describes a \u201cNo Purchase Order No Pay\u201d policy and notes that new starters had been trained by colleagues in practices that did not follow it, so it added mandatory corporate training and began monitoring requests for retrospective POs. The lesson is that a PO only controls spend when it is raised before the buy.<\/p>\n<p>The IIA\u2019s Three Lines Model, published in 2020, places responsibility for managing risk and operating controls with operational management, the first line. A PO is the evidence that a control was applied. It is not the control by itself.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"When_Should_You_Use_a_Purchase_Order\"><\/span>When Should You Use a Purchase Order?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Use a PO for any external supplier purchase where money is committed in advance and someone needs to verify what arrived, and write down the exceptions so nobody has to guess. POs suit inventory and raw materials, MRO parts, equipment and capital items, recurring services, and project spend. Documented exceptions typically include regulated utility payments, payroll, taxes, rent and leases, approved corporate-card programs for low-value consumables, and emergency buys under a written exception process.<\/p>\n<p>Emergencies are where policies quietly fall apart. A line-down event legitimately needs materials faster than a standard cycle allows. What is not legitimate is skipping the record: raise the PO promptly afterward with a named approver and review why it happened. Reviewing emergency buys monthly often exposes a stocking or contract gap. Three mistakes to avoid:<\/p>\n<ul>\n<li><strong>Splitting purchases:<\/strong> Breaking a $28,000 buy into four $7,000 orders to stay under a threshold defeats the control, and it is one of the first patterns internal audit looks for.<\/li>\n<li><strong>Vague lines:<\/strong> \u201cMaintenance supplies, 1 LOT\u201d gives receiving nothing to check and AP nothing to match.<\/li>\n<li><strong>Closing POs too early:<\/strong> Keep the PO open until goods and services are delivered, credits are applied, and invoice exceptions are resolved.<\/li>\n<\/ul>\n<p>A useful test: can your AP team tell whether an invoice is authorized without searching someone\u2019s inbox? If not, PO coverage needs attention first.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Conclusion_A_Purchase_Order_Is_a_Control_Point_Not_Just_a_Form\"><\/span>Conclusion: A Purchase Order Is a Control Point, Not Just a Form<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A purchase order gives everyone involved in a purchase a shared, traceable record before money leaves the business. The best PO processes are proportionate: no six approvals for a stocked consumable, and genuinely stronger checks, usually with a contract behind the PO, for a long-lead transformer or a multi-year service. If you are building from scratch, define the required fields, tie approval rights to value and risk, enforce unique PO numbers, and make receipt confirmation non-negotiable, then <a href=\"https:\/\/procureclix.com\/blog\/procure-to-pay-automation\/\">automate the handoffs<\/a> causing delays. <a href=\"https:\/\/procureclix.com\/solutions\/best-procure-to-pay-software-solutions.html\">Cloud-based procurement platforms<\/a> can keep approvals and records in one place, and you can <a href=\"https:\/\/procureclix.com\/schedule-a-demo.html\">book a ProcureClix demo<\/a> to see requisition approvals and sourcing events on one workflow.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Frequently_Asked_Questions_About_Purchase_Orders\"><\/span>Frequently Asked Questions About Purchase Orders<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"What_is_a_purchase_order_number\"><\/span>What is a purchase order number?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A PO number is a unique identifier assigned to each PO so buyers, suppliers, receiving teams, and AP can track the same order through delivery, invoicing, and payment. The format matters far less than uniqueness. Never reuse a number, because the second use will eventually be matched to the wrong invoice, and require suppliers to quote it on packing slips and invoices.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Is_a_purchase_order_the_same_as_an_invoice\"><\/span>Is a purchase order the same as an invoice?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>No. The buyer creates a PO before delivery to authorize and document a purchase, while the supplier creates an invoice after delivery, or at an agreed milestone, to request payment. The PO states what you agreed to buy and the invoice states what the supplier says you owe, and AP checks one against the other before paying.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Is_a_purchase_order_legally_binding\"><\/span>Is a purchase order legally binding?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>It may become legally binding once a supplier accepts it, in writing or by beginning performance. Whether it does depends on the PO terms, any existing supplier contract, how acceptance occurred, and applicable law. For major purchases, regulated buying, or disputes over terms, get legal review rather than relying on the PO alone.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_is_the_difference_between_a_purchase_requisition_and_a_purchase_order\"><\/span>What is the difference between a purchase requisition and a purchase order?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A requisition is an internal request for permission to buy, and a PO is the approved order sent to the supplier. The sequence is fixed: requisition, approval, then PO. If POs are raised without an approved requisition behind them, the approval step is not doing anything.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn what a purchase order is, what it includes, how the PO process works, and how it differs from an invoice or requisition. See a PO example and template.<\/p>\n","protected":false},"author":3,"featured_media":2107,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2105","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"acf":{"pc_author":null},"_links":{"self":[{"href":"https:\/\/procureclix.com\/blog\/wp-json\/wp\/v2\/posts\/2105","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/procureclix.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/procureclix.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/procureclix.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/procureclix.com\/blog\/wp-json\/wp\/v2\/comments?post=2105"}],"version-history":[{"count":3,"href":"https:\/\/procureclix.com\/blog\/wp-json\/wp\/v2\/posts\/2105\/revisions"}],"predecessor-version":[{"id":2196,"href":"https:\/\/procureclix.com\/blog\/wp-json\/wp\/v2\/posts\/2105\/revisions\/2196"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/procureclix.com\/blog\/wp-json\/wp\/v2\/media\/2107"}],"wp:attachment":[{"href":"https:\/\/procureclix.com\/blog\/wp-json\/wp\/v2\/media?parent=2105"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/procureclix.com\/blog\/wp-json\/wp\/v2\/categories?post=2105"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/procureclix.com\/blog\/wp-json\/wp\/v2\/tags?post=2105"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}