A purchase order log template is a simple register for tracking purchase orders from request through approval, delivery, and invoice matching. Use the blank template below as a printable starting point, then adjust its fields to match your organization’s purchasing process.
What a Purchase Order Log Tracks
A purchase order (PO) is a document that records a buyer’s request to purchase specified goods or services from a supplier. A purchase order log is not the PO itself: it is a central index of POs and their progress. The log helps staff answer practical questions such as whether a request has been approved, when an order was sent, and whether the goods have arrived.
Without a shared record, details may be scattered across emails, paper forms, and individual spreadsheets. A log gives authorized users a consistent place to see the status of each order. It can also help an organization spot pending approvals, follow up on overdue deliveries, and identify orders that still need an invoice or receipt recorded.
The log does not replace the underlying documents. Keep the approved request, PO, supplier confirmation, delivery record, and invoice in the organization’s designated filing system, and use the log to point to or summarize them. Follow your own approval and record-retention procedures; a log alone does not establish that a purchase was authorized.
Printable Purchase Order Log Template
Blank template — one row per purchase order
| PO number | Request date | Requester | Supplier | Department or project | Item or service summary | Amount | Approval status | Date sent | Expected delivery | Received date | Invoice status | Closed date | Notes or document location |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Fictional sample — for illustration only
| PO number | Request date | Requester | Supplier | Department or project | Item or service summary | Amount | Approval status | Date sent | Expected delivery | Received date | Invoice status | Closed date | Notes or document location |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| PO-2026-014 | 2026-03-04 | Jordan Lee | Example Paper Supply | Operations | Printer paper, 20 cartons | 480.00 USD | Approved | 2026-03-06 | 2026-03-13 | 2026-03-12 | Awaiting invoice | Fictional record; delivery note filed |
Use the organization’s preferred date and currency formats. Add rows as needed and store supporting documents separately.
Choosing Useful Fields
The right columns make the log easy to update without turning it into a second copy of every purchasing document. Start with fields that let a coworker identify the order, understand its current state, and find the supporting records.
- PO number: Use the identifier assigned to the order. A consistent numbering method makes lookup and cross-referencing easier.
- Request and requester: Record when the purchase was requested and who initiated it. These details help resolve questions about timing or purpose.
- Supplier and summary: Name the supplier and briefly describe the goods or service. Keep the description concise; refer to the PO for full specifications.
- Department, project, or cost reference: Include whichever internal label your organization uses to group or route purchases.
- Amount and currency: Record the order value in a consistent format. If an order changes, note the revised amount and where the change was approved rather than silently overwriting history.
- Status dates: Dates for approval, sending, expected delivery, receipt, and closure show where an order is in its life cycle.
- Invoice status and notes: These fields help staff follow up on unfinished steps and find a document or explanation when needed.
Some organizations also need a requester’s contact, approver, shipping location, partial-delivery details, or a link to a digital folder. Add those only when they serve a defined task. Avoid putting sensitive personal or payment information in a broadly shared log.
How to Use the Log
Assign someone to maintain the register, even if several people can submit updates. Agree on when a row is created, which status labels are allowed, and who records changes. A consistent routine is more useful than a complicated spreadsheet that is updated irregularly.
- Log the request: Add a row when a purchase request enters the process. If your organization assigns a PO number only after approval, use a temporary request reference and fill in the PO number later.
- Record the decision: Update the approval status and date when the required review is complete. Do not mark a request approved merely because a draft PO exists.
- Record dispatch: Enter the date the approved PO was sent to the supplier, and note any confirmation or document location.
- Track delivery: Update the expected date if the supplier provides a change. When goods or services arrive, record the receipt date and flag partial or disputed deliveries in the notes.
- Follow the invoice and closeout: Mark whether the invoice has arrived and whether the organization’s required checks are complete. Close the row when the purchasing process is finished under internal procedure.
For example, a request for office chairs may be approved and ordered in one week but delivered in two shipments. Keep one row for the PO, record the first receipt date, and explain that the delivery was partial. Update the row when the balance arrives rather than creating a second PO entry for the same order. If separate POs were actually issued, give each its own row.
Adapting the Template to Your Process
A small team with occasional purchases may need only a printed register, a PO number, supplier, summary, amount, status, and dates. A team handling many orders may benefit from filters, a separate tab for closed POs, or a field for the person responsible for the next follow-up. The template is a framework, not a requirement to use every column.
Decide how to handle changes before they occur. If a supplier revises a delivery date, update the expected date and add a short note about the change. If the order value changes, record the new amount and preserve a reference to the approved change. Do not use an ambiguous status such as “in progress” when a more specific label—such as “awaiting approval,” “sent,” or “partially received”—would tell a colleague what action is pending.
For a shared spreadsheet, use a single source of truth and limit editing rights to people who need them. Protect headers and formulas if present, and use filters or frozen header rows to make a long register easier to navigate. For a paper log, write legibly, use the same status terms throughout, and file pages so that completed orders remain retrievable.
Common Problems and Practical Controls
Several avoidable issues make a PO log unreliable. A few simple controls can prevent many of them:
- Duplicate or missing numbers: Assign numbers through one agreed method and check the sequence before issuing a new one. Never reuse a number just because an earlier request was cancelled; mark the earlier record accordingly.
- Out-of-date statuses: Set a regular review interval that fits the volume of purchasing. Review open rows for missing approvals, late deliveries, and invoices that need follow-up.
- Inconsistent wording: Use a short approved set of status labels. “Received,” “partially received,” and “not received” are clearer than several informal variations.
- Overwriting changes: Keep a brief note of material revisions and where the supporting approval is stored. A log should help users understand what changed, not obscure the previous record.
- Confusing an order with an invoice: A PO records an order; an invoice requests payment. Record both milestones distinctly and follow the organization’s process for checking them against receipt information.
- Excessive detail: Do not paste full quotations, bank details, or long specifications into a general register. Keep the log concise and store documents in an appropriate controlled location.
A log can support review, but it does not by itself prevent unauthorized purchases, prove that goods were received, or ensure an invoice is correct. Those checks depend on the organization’s procedures, supporting records, and assigned responsibilities.
Spreadsheet, Paper Log, or Purchasing System?
A paper log is straightforward to print and can suit a low-volume process where staff work with physical files. Its drawbacks are that searching, sharing updates, and reviewing many open orders take more effort. A spreadsheet is flexible and can be sorted by supplier, status, or date, but it needs clear ownership and sensible access controls to avoid conflicting copies or accidental edits.
A dedicated purchasing system may be appropriate when an organization needs linked approvals, document storage, or coordinated work across many users. It may take more setup and administration than a basic register. The useful choice depends on order volume, internal controls, staff capacity, and existing recordkeeping—not on a general rule that one format is best for everyone.
Whichever format you use, retain the underlying records according to your organization’s policy and make sure the log can be reconciled with them. If a purchasing, tax, or contractual situation requires professional interpretation, ask a qualified professional.
Frequently Asked Questions
What is the difference between a purchase order and a purchase order log?
A purchase order is the order document for a particular purchase. The log is a register that lists orders and summarizes their status so staff can track them.
What should a purchase order log include?
At minimum, include an order identifier, request date, requester, supplier, brief description, amount, approval status, and relevant progress dates. Add fields for invoices, receipt, or project references if your process needs them.
Should cancelled purchase orders stay in the log?
Usually, keeping a clearly marked cancelled entry helps explain gaps in numbering and preserves a record of what happened. Follow your organization’s retention and recordkeeping rules.
Can I use one row for several deliveries?
Yes, when the deliveries relate to one PO. Record the partial receipt and remaining quantity or details in the notes, or add a delivery-tracking field. Use separate rows when separate POs were issued.
How often should I update a purchase order log?
Update it when a meaningful event occurs, such as approval, sending, a delivery change, receipt, or invoice arrival. Review open entries on a regular schedule suited to the purchasing volume so missed follow-ups are visible.