A purchase order is created in a minute and determines how much work the invoice generates weeks later. Three of its fields are where future exceptions are decided, and a fourth thing, the sequence of approval and issue, decides whether the whole document is a control or a formality. Getting all four right is not extra work; it is the same work done attentively.
The legal entity and the units
Order from the entity that will actually invoice you, which for a group is often not the trading name you deal with. And record the unit of measure the supplier bills in. Getting either wrong produces a mismatch on every invoice from that supplier, permanently, and both are settled once at supplier setup rather than per order.
An explicit price basis
State whether the unit price includes delivery, packaging and tax. An order silent about freight will mismatch every invoice that adds it, and that presents as a tolerance problem when it is really an unstated assumption. Being explicit keeps tolerance tight enough to catch genuine price movement rather than absorbing everything.
Approval before issue
Approve it before the supplier is told, because the commitment exists once they act on it. Then record that it was sent, and when. Approving after issue is reviewing a decision already made, and recording the send is what answers whether the supplier ever received the order, which is the first question in most delivery disputes.
Questions people ask about how to create purchase order
What are the essential fields?
Unique number, date, supplier legal entity, lines with description, quantity, unit and price, delivery address and date, and your payment terms.
Can we amend after sending?
Yes, as a dated revision, resent to the supplier, with re-approval above a threshold.
What if the price is unknown?
An estimate marked as such, or a not-to-exceed value, so the match has something to compare against.