{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":50478,"path":"source-to-pay-operations/sourcing-and-procurement-operations/purchase-order.md","title":"Purchase order","bundle":null,"doc_type":null,"release":"australia","body":"\n# Purchase order\n\nA purchase order is a binding contract between a buyer and a supplier that authorizes a purchasing transaction. It contains the descriptions, quantities, prices, applicable discounts, payment terms, delivery dates, and other associated terms and conditions with the supplier.\n\nIn a purchase order, the key fields are the following:\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nDisplay name\n\n\n\nName of the purchase order for a supplier product.\n\n
\n\nNumber\n\n\n\nSystem-generated unique identifier of the purchase order.\n\n
\n\nERP number\n\n\n\nThe purchase order number that is synced from ERP systems.\n\n
\n\nVersion\n\n\n\nThe version of the purchase order. A revised purchase order has a higher version number.\n\n
\n\nBusiness owner\n\n\n\nThe user who placed the order.\n\n
\n\nStatus\n\n\n\nStatus of the purchase order.\n\n
\n\nPurchase requisition\n\n\n\nThe purchase requisition associated with this order.\n\n
\n\nPrimary contact\n\n\n\nPerson within the procurement team who can be contacted with questions about the order. This field is populated or updated with the same user in the **Assigned to** field on the purchase requisition.\n\n
\n\nSummary Details\n\n
\n\nSupplier\n\n\n\nSupplier who provides the product of this order.\n\n
\n\nOrder type\n\n\n\nIndicates if the purchase order is of the type **Standard** or **Blanket**.\n\n
\n\nTotal amount\n\n\n\nThe total cost of purchase requisition calculated as the sum from all related purchase lines.\n\n
\n\nReleased amount\n\n\n\nThe budget that is consumed so far.This field is visible for blanket order type.\n\n
\n\nShipping method\n\n\n\nDetails of the carrier, the applicable suppliers, and the valid delivery location countries for those suppliers.For more information on shipping methods and handling fees, see [Handling fees](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/handling-fees.md).\n\n
\n\nAccounting Details\n\n
\n\nCost center\n\n\n\nThe cost center incurring the expense of this order.This field is carried over from the related purchase requisition.\n\n
\n\nLegal entity\n\n\n\nInternal legal entity making this purchase.This field is carried over from the related purchase requisition.\n\n
\n\nPurchasing entity\n\n\n\nThe organizational entity associated with the business owner making this purchase.This field is carried over from the related purchase requisition.\n\n
\n\nPayment term\n\n\n\nThe agreed time and conditions of payment to the supplier.\n\n
\n\nReceived amount\n\n\n\nIndicates if the order is partially or fully delivered. This value is the sum of the receipt values in the child purchase order lines.This field is visible for standard order type.\n\n
\n\nReceived percent\n\n\n\nIndicates if the order is partially or fully delivered. This value is the sum of the receipt values in the child purchase order lines.This field is visible for standard order type.\n\n
\n\nInvoiced amount\n\n\n\nAmount invoiced for the product ordered. While other charges are added to the amount invoiced, discount amount is subtracted from it.This field is visible for standard order type.\n\n
\n\nAmount paid\n\n\n\nAmount paid for the product ordered.This field is visible for standard order type.\n\n
\n\nRemaining balance\n\n\n\nAmount due to the supplier for the order.This field is visible for standard order type.\n\n
During purchase order integration, any attachments with valid sys-ids are copied from the Inbound Purchase Order staging table record to this Purchase Order primary table record. This is done through a transform script, which is part of the Order stage transform map, triggered onAfter. Go to the purchase order record on the Purchase Order table based on the ERP number and purchase order number, and verify that your attachments are present on the target record. You can delete or rename attachments as needed, without creating duplicates.\n\nThe receipt fields \\(**Received amount** and **Received percent**\\) on the Accounting Details section of a purchase order are summations of the receipt fields on the child purchase order lines, which are populated based on the following conditions:\n\n- For purchase order line of goods:\n - When goods have been received: The received quantity is populated when a receipt is created. The received amount and received percent are calculated based on the received quantity.\n - When goods haven’t been received: The received amount is populated with the line amount invoiced \\(editable field\\) when the status of the invoice line associated with the purchase order line is Invoice Confirmed. The received quantity and received percent are calculated based on the received amount.\n- For purchase order line of services:\n\n **Note:** Business rules pertaining to handling state changes, handling tax and charges, default invoice fields, populating invoice line amounts, handling line total changes, and populating supplier products are available only if you haven't installed the Shopping Hub plugin and are still using the Source-to-Pay Common Architecture plugin.​\n\n - When the acknowledgment type is milestones:\n - If the milestone payout is amount, the received amount is populated accordingly. The received quantity and received percent are calculated based on the received amount.\n - If the milestone payout is a percentage, the received percent is populated accordingly. The received quantity and received amount are calculated based on the received percent.\n - When the acknowledgment type is service acknowledgment: The received amount is populated based on the approved invoice line amount. The received quantity and received percent are calculated based on the received amount.\n - When the acknowledgment type is a two-way match: The received amount is populated with the line amount invoiced \\(editable field\\) when the status of the invoice line associated with the purchase order line is Invoice Confirmed. The received quantity and received percent are calculated based on the received amount.\n\nFor more information on purchase order lines, see [Purchase order lines](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/accounts-payable-operations/purchase-order-lines.md).\n\nThe following are the key related lists of a purchase order record:\n\n\n
\n\nRelated list\n\n\n\nDescription\n\n
\n\nPurchase Order Lines\n\n\n\nLists the standard purchase order releases for a blanket purchase order.​\n\n
\n\nApproval Plans\n\n\n\nDisplays all the approval plans created against this purchase order.\n\n
\n\nReceipts\n\n\n\nProvides details of the receipts created for this purchase order. For details, see [Receipts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/receipts.md).This related list is visible for standard order type.\n\n
\n\nMilestones\n\n\n\nProvides details of the milestones for this purchase order. For details, see [Milestones](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/milestones.md).This related list is visible for standard order type.\n\n
\n\nInvoices\n\n\n\nProvides details of the invoices generated for this purchase order. For details, see [Invoices](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/invoices.md).This related list is visible for standard order type.\n\n
\n\nRelated Contracts\n\n\n\nProvides details of related contracts associated for this purchase order. For details, see [Contracts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/contracts.md).This related list is visible for standard order type.\n\n
\n\nPurchasing Permission\n\n\n\nCarried over from the related purchase requisition.This related list is visible for blanket order type.\n\n
\n\nPurchase Order Releases\n\n\n\nThis related list is visible for blanket order type.\n\n
\n\nPurchasing Tasks\n\n\n\nProvides information of tasks for this purchase order.\n\n
\n\nPurchase Order History\n\n\n\nList of purchase orders before the current revision. This related list is visible if the purchase order has revisions.\n\n
For a list of all purchase order states and the conditions that trigger each state change, see [Purchase requisition, purchase order, and sourcing request states](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/pr-po-sr-states.md).\n\n**Parent Topic:**[Sourcing and Purchasing Automation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/purchase-experience-workflow.md)\n\n"}}