The purchase order process for a small business: from request to paid supplier invoice

The purchase order process is the sequence a business follows to buy goods or services: someone requests what is needed, a buyer raises a purchase order with a supplier, the goods are received and checked, the supplier's invoice is matched against the order and the receipt, and only then is the invoice paid. Each step leaves a document, and the documents point at each other.

For a small company the point is not bureaucracy. It is having one record of what was agreed, so that the person who pays the invoice can see what the person who ordered actually ordered, and the person who received the delivery actually counted. This guide walks through each step, the controls worth keeping, and where small teams can safely cut corners.

The four documents and the order they come in

The chain matters more than any single document. An invoice with no order behind it means someone bought without agreement. A receipt with no order means goods arrived that nobody can price. An order with no receipt after its delivery date means a supplier is late and nobody has noticed.

Step 1: the requisition says what and why

A requisition is an internal ask: the shop floor needs consumables, marketing needs laptops. It exists before a supplier is chosen, which keeps two decisions apart: whether to buy at all, and from whom. The requisition carries the department, the items with estimated quantities and prices, and a short justification.

Approval happens here, on the estimate, before anyone talks to a supplier. A sensible small-company rule is an approval threshold: below a set amount the requester's manager approves; above it, the owner does. Keep the rule written down and short, because a threshold nobody remembers is applied inconsistently.

The requisition also gives the buyer room to compare. Two or three quotes for anything above the threshold, attached to the requisition, are usually enough to show the order went to a sensible supplier at a sensible price.

Small teams can skip requisitions for routine reorders of stock items. Those are triggered by stock levels rather than by a person's request, and the purchase order itself is enough of a record.

Step 2: the purchase order is the commitment

The purchase order is the central document of purchasing. It names one supplier and lists the lines: item, quantity, agreed unit price, and the expected delivery date. It should also carry the payment terms you agreed, such as prepayment or 30 days, because those decide when finance must have the money ready.

Three habits make orders reliable:

• The total is never typed by hand. It is the sum of the lines. A hand-typed total is how a 1,200 order becomes a 12,000 invoice that "matches".
• Lines are locked once the order is sent. Changes after sending go through a revised order, so the version the supplier saw is the version you match against.
• Supplier terms live on the supplier record. Typical lead time, currency, payment terms and the supplier's price list belong in one place, so every order starts from them instead of from memory.

Step 3: the goods receipt records what arrived

When the delivery comes in, someone counts it and records a goods receipt against the order: what arrived, in what quantity, into which warehouse. This is the step most small companies skip, and it is the one that keeps stock figures true.

Posting the receipt does three things at once. It adds the goods to stock, so they become available to sell. It records a debt to the supplier for what was received. And it updates the item's average cost using the price on the order, which is what later makes your profit figures honest. A cost price typed into a product card by hand, months ago, is the usual reason margin reports disagree with the bank account.

Partial deliveries are normal. Record what arrived; the order shows as partially received, and the rest arrives on a later receipt. If the supplier will not deliver the remainder, close the order as short-delivered so it stops appearing as late. For what each stock number means once goods are on the shelf, see on hand, reserved and available.

A receiving checklist for whoever signs for deliveries

1. Find the order the delivery belongs to before opening the boxes. No order, no signature: the delivery waits while someone finds out who bought it.
2. Count against the order lines, not against the supplier's delivery note. The delivery note says what the supplier thinks they sent.
3. Check condition. Damaged items are received separately or refused, with a photo and a note on the receipt.
4. Choose the warehouse the goods go to, so stock is counted in the right place from the first minute.
5. Post the receipt the same day. A receipt left as a draft for a week means a week of stock figures that are wrong.

Step 4: match, then pay

Three-way matching is the control at the end of the chain. Before an invoice is approved, each line is compared across three documents:

1. Order: was this item ordered, and is the invoiced price the agreed price?
2. Receipt: did this quantity actually arrive?
3. Invoice: is the supplier billing for exactly that?

Lines that agree are approved. Lines that do not go back with a specific question: billed for 100, received 90; billed at 4.20, agreed 3.90. Services, which have no physical receipt, are matched two ways (order and invoice) plus a confirmation from whoever received the service.

Payment then follows the terms on the order. Paying early loses cash you could use; paying late costs supplier goodwill and sometimes interest. A weekly list of supplier invoices due in the next seven days is enough planning for most small companies.

Where small teams can cut corners, and where they cannot

Cut freely: requisitions for routine stock reorders, approval chains for small amounts, formal supplier evaluations for one-off purchases. Do not cut: the order for anything you will receive into stock, the receipt for anything that changes stock, and the match before payment. Those three are what keep stock, cost and supplier debt correct, and errors in them compound quietly for months.

The other control worth keeping, even in a small team, is a separation of duties where it is cheap. The person who raises an order and the person who approves its payment should not be the same, at least above a threshold. When the team is too small for that, the owner can review a weekly list of paid supplier invoices with their orders and receipts beside them. Ten minutes a week is enough to spot a supplier billed twice or an order that nobody can explain, and the fact that someone looks is itself most of the protection.

How Nextora handles purchasing

Nextora's ERP area follows the same chain: supplier order → receipt → supplier invoice → payment. A requisition records a department's request with its lines and estimated amount, and its expanded row shows the orders raised from it. On a purchase order, the + button creates the header (supplier and dates) and lines are added on the order page; line amounts and the order total are calculated by the database, never typed. Mark as sent locks the lines. The program does not email the supplier; the button records that you sent the order.

When goods arrive, Receive creates a receipt pre-filled with everything still outstanding. Once it is posted, the goods enter stock, the entries are booked by the organization's chart of accounts, the average cost is recalculated, and the order becomes partially or fully received by itself. A short delivery can be closed once its receipts are posted, and a wrong receipt can be cancelled from the document chain at the bottom of the order, which reverses the entries and corrects the average cost.

The supplier record holds payment terms, currency, typical lead time and a price list with minimum order quantities, and a What we owe the supplier block shows received, paid and outstanding amounts with open invoices and due dates. The ERP home lists supplier invoices due within seven days and those past due. The ERP page shows purchasing alongside stock and sales.

The sales side mirrors this chain in reverse; quote to cash walks through it, and CRM vs ERP explains where purchasing sits relative to the customer records.