Making a purchase order takes a minute and determines how much work an invoice generates weeks later. Three fields cause nearly all the trouble, and all three are trivial to get right at creation and awkward to correct afterwards. The rest of the document is bookkeeping; these three are where the future exceptions are decided.
The right legal entity
Groups invoice from entities whose names differ from the trading name you deal with. An order raised against the wrong entity produces an invoice that will not match, and the usual fix, creating a second supplier record, splits payment history and disables duplicate detection. Confirm the entity once at supplier setup and the problem disappears permanently.
Agreed units of measure
Ordering by case and being invoiced by unit produces a quantity mismatch every single time, and it is nobody's error. Agreeing the unit with the supplier and recording it on the order is a one-off conversation that removes a permanent exception source. It is the single most common avoidable mismatch in most payables queues.
What the price includes
Unit price, and whether delivery, packaging or tax are inside it. An order silent on freight will mismatch every invoice that adds it, which looks like a tolerance problem and is really an unstated assumption. Being explicit is what makes tolerance a real control rather than a general allowance for surprises.
Questions people ask about how to make a po
What are the essential fields?
Unique number, date, supplier legal entity, lines with description, quantity, unit of measure and price, delivery address and date, and your payment terms.
Should the order be sent as a PDF?
Whatever the supplier can process reliably. What matters is that your reference is somewhere they will find it and quote it back.
Can an order be changed?
Yes, as a dated revision rather than an overwrite, and above a threshold it should go back for approval.