How to Read a Purchase Order (PO): Every Field Explained

A purchase order has three parts: a header that identifies the order (PO number, dates, buyer and supplier), a line-item table that lists what is being bought (SKU, description, quantity, unit of measure, unit price, line total), and a footer with terms and totals. That is how to read a PO: work top to bottom and you know exactly what was ordered, from whom, at what price, and on what terms. Once you understand the fields, the only real work left is getting them out of the document and into your system.

Upload a purchase order above and you get every one of those fields back as clean Excel, CSV, or JSON in seconds: PO number, vendor, ship-to and bill-to, each line item with its quantity and unit price, and the totals. That turns a PDF you would otherwise read and retype into data you can drop straight into your records.

The three parts of a purchase order

Almost every PO, no matter which system created it, follows the same layout. The header sits at the top, the line items run down the middle in a table, and the terms and totals close it out. Knowing which part you are looking at makes the whole document easy to scan.

Reading the header

The header is the identity of the order. The PO number is the unique reference both sides use to track it through fulfillment, receiving, and payment; quote it on every email, packing slip, and invoice tied to the order. The order date establishes when the commitment was made. The buyer and supplier blocks name the two parties and their contacts. Watch the two addresses carefully: ship-to is where the goods physically go, and bill-to is where the invoice goes, and they are often different locations within the same company.

Reading the line items

The line-item table is the heart of the PO and the part that matters most for accuracy. Each row is one thing being bought, with a SKU or item code that maps to the supplier's catalog, a description, a quantity, a unit of measure, a unit price, and a line total (quantity multiplied by unit price). The field people misread most often is unit of measure: ordering 10 cases is not the same as ordering 10 each, and getting it wrong is how a small order arrives ten times too large. When a PO runs to dozens or hundreds of rows across several pages, reading every line correctly by eye is exactly where manual entry breaks down, which is why purchase order line item extraction captures the whole table instead of leaving you to copy it.

Reading the terms and totals

The footer is where the money and the conditions live. The subtotal adds up the line totals, then tax and shipping are added to reach the grand total, which is the amount the buyer is committing to. Payment terms (for example Net 30) state when payment is due, and the delivery date or required-by date sets the expectation for fulfillment. These fields are what accounts payable checks the supplier's invoice against later in a three-way match, so they need to be read and recorded accurately, not skimmed.

What fields are on a purchase order?

A purchase order carries roughly 25 to 30 distinct fields, split across three zones: header fields that identify the order, line-item fields that describe what is being bought, and totals and terms that close it out. Not every PO uses every field, and no two suppliers lay them out the same way, but the set below covers what you will find on almost any US business purchase order.

Header fields

Line-item fields

Totals and terms fields

The fields that cause the most trouble downstream are the three that look boring: unit of measure, ship-to versus bill-to, and the per-line delivery date. Each one is easy to skim past and expensive to get wrong.

What a purchase order looks like on the page

A purchase order looks like an invoice turned around. There is a header block at the top with the PO number, date, buyer, and supplier, two address blocks for ship-to and bill-to, a table in the middle with one row per item, and a totals box in the lower right. Terms and an approval signature sit at the bottom. Most run one to two pages.

For a labeled walkthrough of a sample order, see what a purchase order looks like. The layout is conventional rather than standardized. A PO out of SAP, one out of QuickBooks, and one a small supplier built in Excel all carry the same information in visibly different places, which is exactly why reading them at volume by eye is slow, and why template-based tools struggle where AI extraction beats plain OCR. There is no fixed template, only a fixed set of things that have to be on the page.

From reading the PO to using its data

Understanding the fields is step one; the practical job is capturing them. If the PO arrived as a PDF or a scan, AI extraction reads it the same way you just did, by meaning rather than position, and returns structured rows. For photographed or scanned paper orders specifically, the purchase order image to Excel converter handles the ones with no text layer at all. From there you can convert the purchase order to Excel or export it to CSV and import the data into your ERP. Teams clearing a stack of supplier orders use bulk purchase order processing to do the whole batch at once, and accounts payable groups rely on purchase order extraction for AP teams to turn the same documents into match-ready data. If you are still choosing a tool for this, the roundup of the best purchase order OCR software compares what each one actually reads.

The PO is only the first document in a chain. Once goods arrive and the supplier bills you, your AP team matches the invoice back to these same PO fields (the two documents are easy to confuse, so it helps to know how a purchase order differs from an invoice), which is the work an accounts payable automation platform handles end to end. The invoice itself often needs the same field-by-field capture, which is what invoice data extraction does on the billing side. And businesses that process many document types beyond POs, such as contracts, packing slips, and receipts, often standardize on a broader document data extraction platform for all of them.

How to read a purchase order on screen in your ERP

Reading a PDF is one job. Reading the same order inside the system that created it is another, because every ERP splits the document across screens in its own way. Here is where the fields you just learned actually live.

SAP

Use transaction ME23N to display a purchase order. The screen is divided into three stacked areas: the header, the item overview, and the item detail. The PO number sits at the top of the screen next to the name of whoever created it, and you can collapse the header to give the item grid more room. The item overview is your line-item table. Select a line and the item detail section below it opens a set of tabs, which is where the useful detail hides: account assignment, delivery address, invoice receipt settings, and Purchase Order History. That last tab is the one to learn, because it lists every goods receipt and invoice posted against that line, which tells you at a glance whether the order is partly received or fully billed. There is more on that screen in purchase order history in SAP.

Oracle Fusion Cloud

Orders live in the Purchase Orders work area, found through Manage Orders. Oracle nests the document three levels deep, and the distinction matters when you are reading one. The line carries what you are buying and the unit price. Each line has one or more schedules, which carry the quantity, the promised date, and the ship-to location. Each schedule has distributions, which carry the account coding and the split across cost centers or projects. So a single line ordered for two delivery dates and charged to two departments is one line, two schedules, and up to four distributions. If a total looks wrong, the answer is usually a schedule you did not scroll to.

Microsoft Dynamics 365

In Dynamics 365 Finance, open Accounts payable and then All purchase orders. The detail page has a header view and a line view, and you toggle between them; people who cannot find the payment terms or the delivery address are almost always looking at the line view. In Business Central the equivalent is the purchase order card, with the header fields on the General and Invoicing sections and the grid underneath.

NetSuite and QuickBooks

NetSuite shows the order as a transaction record with the item lines on the Items subtab, and the related item receipts and vendor bills linked from the record itself, which is the fastest way to see what has been received against it. QuickBooks Online keeps purchase orders under Expenses, with a status of Open or Closed and a link to whatever bill was created from it. Neither shows you a schedule or distribution layer, because neither has one.

Where do you find the purchase order number?

On a printed or PDF purchase order the PO number is in the header, usually top right, labeled PO Number, Purchase Order No, or simply Order Number. Do not confuse it with the vendor quote number or the requisition number printed near it. In SAP it appears at the top of the ME23N screen; in most other systems it is the document number on the record itself.

What is a purchase order line?

A purchase order line is one item being bought: a part number or description, a quantity, a unit of measure, a unit price, and an extended amount. A single PO can carry one line or several hundred. The line is the level at which goods are received, invoiced, and matched, which is why partial deliveries close some lines and leave others open.

Frequently asked questions

How do you read a purchase order?

To read a purchase order (PO), read it top to bottom in three parts. The header identifies the order with its PO number, dates, buyer, supplier, and ship-to address. The line-item table lists each product with its SKU, quantity, unit of measure, and unit price. The footer shows the subtotal, tax, shipping, grand total, payment terms, and delivery date.

What is a PO number on a purchase order?

A PO number is the unique reference assigned to a purchase order so both buyer and supplier can track it through fulfillment, receiving, and payment. It appears in the header and should be quoted on every related email, packing slip, and invoice, because accounts payable uses it to match the supplier's invoice back to the original order.

What are line items on a purchase order?

Line items are the individual products or services being bought, listed one per row in the body of the PO. Each line typically carries a SKU or item code, a description, a quantity, a unit of measure, a unit price, and a line total. The line items define exactly what the supplier must deliver and what the buyer will be charged.

What is the difference between ship-to and bill-to on a PO?

Ship-to is the address where the goods are physically delivered, while bill-to is the address where the invoice should be sent. They are often different within the same company, for example shipping to a warehouse but billing to a central accounts payable office, so both need to be read separately.

What does unit of measure mean on a purchase order?

Unit of measure states how each line-item quantity is counted, such as each, case, box, pallet, or pound. It matters because the same quantity means very different amounts depending on the unit; ordering 10 cases is not the same as 10 each. Misreading the unit of measure is a common cause of over- and under-ordering.

What do payment terms like Net 30 mean on a PO?

Payment terms state when the buyer must pay after receiving the invoice. Net 30 means payment is due within 30 days of the invoice date. The terms appear in the footer of the PO and carry over to the supplier's invoice, where accounts payable uses them to schedule payment and avoid late fees or missed early-payment discounts.

The single field that causes the most downstream trouble is the reference at the top of the order. If you are unsure what it is for or where it should appear later, see what a PO number is.