When a vendor sends a bill, it can be tempting to treat the paperwork as one continuous document. But understanding purchase order vs invoice helps growing businesses separate what they approved from what they owe. A purchase order (PO) is a buyer’s request and authorization for goods or services; an invoice is a seller’s request for payment after providing them or reaching an agreed billing point. Used together, they create a clearer trail from planned spending to recorded liability and payment.

Talk with Function about your bookkeeping needs

This guide explains the distinction, the practical workflow, how to compare documents, and what to do when details do not match. Specific requirements depend on your contracts, purchasing policy, accounting setup, and applicable rules. A PO does not replace a contract, and an invoice does not prove by itself that goods arrived or services were accepted.

What is the difference between a purchase order and an invoice?

A purchase order comes from the buyer. It documents an intended purchase and, subject to the organization’s policy and the vendor’s acceptance, authorizes a commitment. An invoice comes from the supplier. It states the amount being requested, the items or services billed, and payment instructions or terms. A PO is usually created before the purchase; the invoice is usually issued after delivery, completion, or another billing milestone specified in the agreement.

Comparison point	Purchase order	Invoice
Prepared by	Buyer	Supplier or service provider
Typical timing	Before ordering or work begins	After delivery, work, or an agreed billing milestone
Main purpose	Request and authorize a planned purchase	Request payment for a billed purchase
Typical details	Buyer and vendor, items, quantities, estimated or agreed prices, delivery terms, PO number	Supplier, invoice number and date, billed items, amounts, due date or terms, remittance instructions
Created by	Purchasing or another authorized buyer	Supplier accounts receivable or billing team
Financial effect	May record a commitment under the buyer’s process; not automatically an expense or payable	Can support recording an amount owed once goods or services and accounting treatment are verified
Key check	Was the purchase approved by the right person?	Is the charge accurate, authorized, and supported by delivery or work evidence?

For example, a company orders 20 monitors at an approved unit price. Its PO records the order. When the monitors arrive, the supplier sends an invoice. The buyer checks that the quantity and agreed price match, and that the delivery was received, before approving the bill for payment. The exact evidence needed depends on the company’s policy and the purchase.

Neither document has one universal legal effect in every situation. The PO, vendor acceptance, contract, purchase terms, and governing law can all matter. Treat the documents as evidence in a controlled process, not as substitutes for reviewing the underlying agreement.

Why are the two documents easy to confuse?

Both documents can list the same supplier, products, quantities, and prices. A purchase order may be copied into an invoice, and both can carry reference numbers. But they answer different questions: the PO asks, “What are we requesting and approving?” The invoice asks, “What is the supplier billing us for, and when is payment due?”

Confusion often arises when a small business does not use formal purchasing steps for every transaction. An owner may approve a purchase in an email, a card may be charged immediately, or a contractor may send a deposit request before work starts. Those arrangements can be valid, but the business still needs a consistent way to record authorization, receipt, and payment. A PO is one possible control; it is not necessary for every business or every purchase.

Another source of confusion is that a PO number on an invoice does not turn the invoice into a PO. The reference helps the buyer connect the supplier’s bill to the earlier authorization. Likewise, a PO does not tell the finance team that a delivery was completed, that hours were worked, or that the invoice amount is correct. Those facts need their own support.

What does each document do in the purchasing cycle?

The PO and invoice are two points in a wider chain. Understanding their roles is easier when each document is tied to a decision rather than viewed as a form to file. A workable sequence may include a purchase request, budget review, supplier quote, PO, agreement, delivery or service evidence, invoice, approval, payment, and bookkeeping entry. Some purchases omit a formal PO or use an agreement that performs several roles, but the underlying questions remain: who approved the commitment, what was received, what was billed, and what was paid?

The purchase request records the need

A purchase request is an internal explanation of what someone wants to buy and why. It can be a form, email, ticket, or other record. The requester may state the business purpose, desired timing, preferred supplier, estimated amount, and project or department. A request is not necessarily an authorization to order. The approver should be able to distinguish “please consider this” from “this purchase is approved.”

For a simple order, the request and approval may fit in one email thread. For a larger commitment, a structured request helps the reviewer evaluate alternatives, budget, scope, and timing. Whatever format the company chooses, retain the decision and the identity of the person who made it.

The quote and agreement define what is being bought

A supplier quote can provide a proposed price, quantity, description, and validity period. It may not settle every condition. The contract, statement of work, subscription terms, or accepted quote may also define delivery, service levels, deposits, cancellation, acceptance, renewals, taxes, or other terms. The PO should reference the relevant agreement where useful instead of trying to replace it with a brief line description.

Suppose a marketing firm requests design work. A PO line that says “design services” may not be enough to judge a later invoice. A statement of work that identifies the agreed deliverables, revision process, schedule, and billing stages gives the reviewer a better basis. The PO can identify the approved amount and reference that scope document. The invoice can then refer to the project and milestone billed.

The receiving record verifies performance

For physical goods, receipt may be documented by a packing slip, delivery confirmation, receiving log, or inspection note. For services, evidence may be an approved timesheet, milestone acceptance, project record, or confirmation from the person who requested the work. Evidence should fit the purchase. A delivery receipt may show that boxes arrived, but not necessarily that contents were complete or undamaged. A work update may show activity, but not necessarily that a contractual milestone was accepted.

Keep exceptions visible. If an order is short, damaged, delayed, or only partly complete, the receiving person should record that promptly. If service work is disputed or a deliverable needs correction, capture the issue and the next step. A finance reviewer who did not witness the transaction needs enough context to determine whether a bill should be approved, held, or partly disputed.

The invoice requests payment

The invoice is the supplier’s formal billing record. It normally identifies the supplier, invoice number and date, items or services, quantities, amount, tax or other charges when applicable, payment terms, and payment instructions. Its fields and legal requirements vary by transaction and jurisdiction, so a template should not be treated as a universal compliance checklist.

When an invoice arrives, the buyer should route it to a known review process. Confirm that the supplier and payment details are recognized, the invoice is not a duplicate, the billed work or goods are supported, and the amount agrees with authorized terms or an approved change. Payment instructions deserve particular care when they differ from prior records; verify changes through a trusted, independently known contact channel rather than relying only on a new message in the invoice email.

The payment record closes the transaction

Approval and payment are separate events. Approval confirms that the bill may proceed under the business’s rules. Payment records that funds were actually sent and helps reconcile the bank account. Retain the payment confirmation or transaction reference with the invoice and related documents. If a payment is returned, partially applied, or credited later, record that development as well.

A company should avoid treating a sent payment instruction as proof that a vendor received funds. The bank record, payment platform status, remittance advice, or supplier confirmation may provide different evidence. The appropriate evidence depends on the method and the business’s controls.

When should a business issue a purchase order?

Use a PO when documenting approval before a commitment will help the business control spending or coordinate a purchase. That is especially useful when several people request or approve purchases, orders involve multiple deliveries, a supplier needs written specifications, or the company wants to compare planned amounts with actual bills.

A practical policy can set thresholds and exceptions. For instance, management might require a PO for purchases above an internally chosen amount, recurring vendor commitments, equipment, or projects with multiple stages. The threshold is a company decision, not a universal rule. Keep the policy simple enough that staff can follow it and specify who can approve exceptions.

For very small, routine purchases, a card receipt and a clear approval record may be more efficient than a formal PO. For larger or recurring commitments, documenting the scope, amount, timing, and approver in advance may prevent disputes. Consider whether a contract, statement of work, or subscription agreement is also needed. A PO should not be assumed to include every term that belongs in a negotiated contract.

Information to include in a useful purchase order

• A unique PO number and issue date.
• The buyer’s legal or operating name and contact details, plus the supplier’s name.
• A clear description of each item or service, with quantities and units where relevant.
• Agreed unit prices, estimated total, currency, and any known shipping or other charges.
• Delivery location, requested date, service period, or milestones as applicable.
• Any relevant contract or quote reference, and the name or role of the approver.
• Instructions for the supplier to place the PO number on its invoice.

Do not treat a template’s fields as a substitute for commercial review. If tax, freight, deposits, cancellation terms, or acceptance criteria affect the deal, document them in the appropriate agreement and confirm how they should appear in the order and invoice.

What a PO policy should decide

A useful policy answers a few operating questions clearly. Which transactions require a PO? Who may create one? Who approves it? When must approval happen? Can a requester approve their own purchase? What happens when the supplier changes the scope or price? How are emergency purchases documented? Where are open POs reviewed and closed? If staff cannot answer these questions, a beautifully formatted template will not create a reliable control.

Keep the policy proportionate. A two-person business may use a short written procedure and owner approval. A larger business with multiple teams may need assigned approval limits and a purchasing system. The goal is not to imitate a large procurement department. It is to ensure commitments are visible and authorized at a level appropriate to the business.

How does the purchase-to-payment process work?

A useful process follows a traceable path from need to payment. The steps can be lightweight for a small team. The important thing is that the business can later answer who approved the commitment, what was received, what was billed, and who authorized payment.

1. Define the need. The requester describes the goods or services, timing, business purpose, and estimated cost. For a service, define the scope or deliverables clearly enough to evaluate the bill later.
2. Check budget and authority. An authorized person reviews the purchase under the company’s policy. Approval should happen before the business makes a commitment, when practicable.
3. Create and send the PO, if used. Assign a unique number, confirm the vendor and terms, and provide the document to the supplier. Retain the supplier’s acceptance or other confirmation where appropriate.
4. Receive the goods or service. Record delivery, completion, or milestone acceptance. Note partial shipments, damaged goods, disputed work, or other exceptions promptly.
5. Receive and review the invoice. Capture the invoice number and date, supplier, PO reference, line items, amounts, and due date. Check for duplicate submissions as well as accuracy.
6. Compare supporting documents. Match the invoice to the PO and evidence of receipt or service completion. If something differs, pause the disputed part and ask for clarification under the business’s policy.
7. Approve and record the bill. The appropriate reviewer confirms the charge and coding before it is recorded for payment. The record should identify the accounting period and category consistently with the company’s accounting process.
8. Pay and retain evidence. Pay according to approved terms, record the payment, and keep the PO, invoice, approval, and receipt or work evidence together in an accessible system.

For a recurring service, the company may not create a new PO every month. It can instead document the approved agreement, billing schedule, and review procedure, then check each invoice against the contract and evidence that the service period is correct. The process should fit the transaction rather than produce paperwork with no control value.

The U.S. Federal Acquisition Regulation describes a government purchase order form designed for certain simplified, on-the-spot transactions; its provisions are specific to federal purchasing, not a general rule for private businesses. See Federal Acquisition Regulation Part 13 for that limited context. Private businesses should follow their own agreements and policies rather than assume government procedures apply to them.

What is three-way matching, and when is it useful?

Three-way matching compares three records: the purchase order, evidence that goods were received or services performed, and the supplier’s invoice. The goal is to confirm that the business approved the purchase, received what it agreed to receive, and is being billed according to the agreement. It is a review control, not a guarantee that a transaction is valid or free of error.

For a goods purchase, receiving evidence may be a packing slip or a record made by the person who checked the delivery. For services, it might be an approved time record, milestone sign-off, or confirmation that the billing period matches the agreement. The right record varies. The person reviewing an invoice should know what counts as adequate evidence for the transaction.

Matching can be exact or tolerance-based. A company may permit minor rounding or a documented freight charge, while requiring review for quantity or price differences. Set tolerances deliberately and document who may approve deviations. A tolerance is not permission to ignore unexplained changes.

Example: a standard goods order

Imagine the approved PO lists 12 office chairs at $240 each, for a line total of $2,880 before any applicable additions. The delivery record shows 12 chairs received in good condition. The invoice lists 12 chairs at the approved price and identifies the same PO. The reviewer checks supplier identity, invoice number, quantity, unit price, arithmetic, and payment terms. If everything agrees and the approver’s records are complete, the bill can move through the business’s normal approval and payment process.

Now imagine that the invoice lists 13 chairs. The reviewer should not simply accept the extra line because it is small. The receiving record supports 12, and the PO authorizes 12. Ask whether an additional chair was requested and delivered, whether it belongs to another order, or whether the invoice contains a mistake. If the extra chair was legitimately approved, retain the change authorization and receipt. If not, ask for a corrected invoice or other appropriate resolution.

Example: a partial shipment

Suppose a business orders 100 units, but the first delivery contains 60. A supplier invoices the full order. The PO may show 100, and the invoice may show 100, but the receiving record supports only 60 delivered so far. The reviewer should check the delivery terms and billing agreement before approving the full amount. The correct treatment depends on whether the contract allows billing in advance or by order rather than by delivery.

If the agreement permits billing on shipment, the evidence and contract may support the invoice despite the partial delivery. If billing is due only after receipt, the business should ask the supplier to clarify or revise the bill. A useful record states the open quantity, expected balance delivery, and how the invoice will be handled. This prevents the next reviewer from mistaking an intentional split shipment for a duplicate or an unexplained shortfall.

Example: service billed by milestone

A consultant’s agreement might specify a deposit and later milestone payments. The invoice may not correspond to a conventional receipt of goods, but it should still be checked against the approved scope, milestone, and contract terms. A PO can reference the engagement, while a written acceptance or project update supports the milestone review. The existence of a PO alone does not establish that the milestone was completed.

For instance, a project has three milestones with separate amounts. The first invoice requests the agreed deposit, the second bills after delivery of a defined draft, and the final bill follows approval of completed work. The reviewer should identify which stage the invoice covers and find the evidence required by the agreement. If the supplier bills the second milestone before the work is submitted, the invoice needs clarification rather than a guess based on the total project value.

Example: recurring software or maintenance

A recurring vendor may charge monthly under a signed agreement rather than receive a new PO each cycle. The original approval can identify the service, renewal period, price basis, cancellation terms, and budget owner. Each invoice still needs a review for the correct period, authorized amount, unexpected add-ons, duplicate billing, and status of the agreement. The reviewer may rely on a recurring schedule, but should not assume that every charge remains correct indefinitely.

When the price changes at renewal, compare the new invoice to the renewal terms and any approval needed under policy. Retain the renewal notice and updated authorization. If seats, locations, or usage affect the amount, identify the person responsible for validating those quantities. A consistent monthly check can be brief while still catching an abandoned subscription or an unapproved expansion.

What should you do when the PO and invoice do not match?

Do not assume every difference is an error, but do not approve unexplained differences automatically. First identify exactly what changed: quantity, unit price, tax, freight, dates, supplier identity, payment instructions, or the scope billed. Then compare the records with the quote, contract, change approval, delivery evidence, and company policy.

1. Pause the affected approval. Follow internal policy for disputed or incomplete bills. Avoid delaying unrelated, undisputed invoices unnecessarily.
2. Describe the discrepancy precisely. Record the PO line, invoice line, amount or quantity difference, and the supporting document reviewed.
3. Ask the right person to resolve it. The requester can confirm whether extra work was authorized; the receiving person can confirm delivery; the vendor can explain its billing. Use a known contact channel if payment instructions changed.
4. Document the resolution. Keep an approved change, corrected invoice, credit memo, receipt, or written explanation with the transaction.
5. Update records consistently. If an authorized change alters the commitment, preserve the original and record the change rather than silently replacing history.
6. Approve only what is supported. Apply the company’s review and payment controls, including any required separation of duties.

Common mismatches include a price increase that was not approved, a duplicate invoice, a vendor’s different legal name, missing units, unexpected freight, a wrong billing period, or a charge for work outside scope. Sometimes the PO was created from an outdated quote, or the invoice uses a different unit of measure. Specific documentation makes the question easier to answer and provides a useful audit trail.

A mismatch triage example

Assume an invoice is $4,180 while the PO is $4,000. Do not start by assuming the additional $180 is either acceptable or improper. Separate the amount into line items: is there a newly billed delivery charge, a changed unit price, tax, or added work? Check the quote and agreement for those terms. Then verify whether a person with authority approved the difference and whether any goods or work related to it were received.

If the $180 is a contractually stated freight charge and the delivery record supports the order, document that explanation and apply the normal approval rule. If it is additional labor requested informally, ask the requester and approver for evidence of authorization. If no one can substantiate it, contact the vendor for a corrected invoice or further detail. Keep the decision visible so a later reviewer can understand why the amount was paid, revised, or disputed.

For a quantity mismatch, make the numbers explicit. If the PO requests 50 units and the invoice bills 48, check whether two units remain on backorder, were canceled, or were delivered separately. If 50 were billed but only 48 received, consult the agreement to see whether billing is based on shipment, order, or accepted delivery. Do not let a generic “quantity difference” note substitute for recording which units are open and who will follow up.

Handle payment-detail changes carefully

A change to a supplier’s bank account or remittance instructions is not an ordinary line-item mismatch. Treat it as a separate verification issue. Use a contact number or address already on file, not contact information supplied only in the message requesting the change. Follow the company’s approval and vendor-maintenance procedure, and retain evidence of the verification. If there is uncertainty, pause payment and escalate to the designated owner.

This process need not imply that every change is suspicious. Vendors legitimately update accounts or billing systems. The point is to verify an important change through a trusted route and keep the approval trail. A fast payment made to incorrect instructions can be difficult to reverse, so a short check can be worthwhile.

How do purchase orders and invoices fit into bookkeeping?

Bookkeeping records completed financial activity in a consistent way. A PO helps explain an intended or authorized commitment, while an invoice and evidence of receipt may support recording a payable or expense under the business’s accounting method and policies. A payment record then shows when the cash left the business. The timing and account treatment should be determined with the organization’s accounting process; paperwork labels alone do not settle recognition.

This distinction helps avoid two opposite mistakes. Recording every PO immediately as an expense can misstate activity if the purchase has not been delivered or otherwise incurred under the applicable accounting treatment. Waiting to organize invoices until payment can also obscure bills that have been received but remain unpaid. A business needs a process for capturing commitments where useful and recording actual transactions at the appropriate time.

For cash planning, open POs can help managers see expected spending that has not yet appeared as a paid bill. They are not the same as actual cash outflow, and an open commitment may change or be canceled. Accounts payable reports, bank activity, unpaid bills, expected receipts, and upcoming commitments each answer different questions. A forecast is more useful when it distinguishes actuals from estimates and identifies the assumptions behind them.

Accurate, organized records also make it easier to see which vendor bills belong to which period, budget, project, or location. To learn how consistent records support reporting, explore Function’s bookkeeping services and financial workflow platform. The relevant service scope depends on the engagement; bookkeeping does not automatically include every tax filing or advisory service.

Commitments, bills, expenses, and cash are not the same

These terms often appear together in reports, but they describe different stages. A commitment is an approved future purchase or obligation under the company’s process. A bill is a supplier’s request that may need review. An expense or other accounting entry reflects treatment under the company’s accounting method. A cash payment is the movement of funds. The same transaction may appear at different times in different views.

Consider equipment ordered in March, delivered in April, invoiced in April, and paid in May. A purchasing report might show the commitment in March. The accounting treatment may depend on the asset and the business’s accounting policies, rather than the date typed on the PO. Accounts payable may show a bill after it is received and reviewed. Cash reporting shows the outflow in May. Each report can be useful, provided its dates and purpose are understood.

Likewise, a deposit invoice issued before work begins does not automatically mean the entire project has been completed. The agreement and accounting policy determine how the payment is recorded and tracked. Keep the deposit connected to the contract, invoice, payment, and later settlement. If the project is canceled or changes, document the refund, credit, or revised scope rather than leaving the original deposit unexplained.

Use coding that supports later questions

When recording a bill, assign the appropriate account and any relevant project, department, location, or other tracking dimension used by the business. A line description such as “vendor services” may be technically recorded but not useful for management if the business cannot tell which project or activity it supported. Coding should be consistent with the chart of accounts and established bookkeeping policy.

Do not create excessive categories just because a PO has many lines. A small business needs enough detail to answer decisions it actually makes. If the company wants to compare equipment spending by location, a location field may be useful. If a project manager needs to track contractor costs to a client engagement, project coding may help. Review the level of detail periodically so the process stays understandable.

Use the document trail to investigate unusual results

When a monthly expense changes sharply, the PO and invoice trail can help explain whether the change came from a new commitment, a one-time delivery, a price adjustment, a billing correction, or a misclassification. The records do not explain themselves; a reviewer still needs to connect them to the business purpose and accounting entry. If the team records descriptions and approvals consistently, the investigation is faster and less dependent on memory.

For a business preparing reports for management, lenders, or investors, traceability can support confidence in the underlying figures. It does not guarantee that every report is complete or that a transaction has a particular accounting treatment. It gives the reviewer a path to supporting records and makes unresolved questions visible for appropriate follow-up.

How can a small business keep the process practical?

A purchasing workflow should be strong enough to catch meaningful errors and simple enough to use every time. A small business can start with a few decisions: which purchases require advance approval, who can approve them, what evidence is required, where records are stored, and who reviews bills before payment.

Set approval roles and limits

Write down who may request, approve, receive, code, and pay purchases. In a small team, one person may have more than one role, but consider whether a second review is appropriate for larger or unusual payments. If the owner approves everything, define a backup for absences and a method to document approval.

Approval limits should reflect the business’s risk and operating needs. A fixed threshold may be easy to follow, but purchase type can matter too: a recurring subscription, equipment order, or new vendor may deserve review even when the first bill is modest. Review the limits when the business adds locations, teams, or new purchasing responsibilities.

Separate duties where practical. The person requesting a purchase can describe the need; another person may approve it; someone else may confirm receipt; and a designated reviewer can approve payment. A very small company may not have enough staff for complete separation. In that case, an owner can perform a secondary review of supporting records or bank activity. Document the compensating check instead of pretending that roles are fully separate.

Use a consistent identifier

Give each PO a unique number and ask vendors to put it on invoices. If the business does not use POs for a transaction, use another clear reference, such as a contract, project, or approval record. Consistent identifiers help connect emails and documents without forcing every small expense into a formal system.

Choose a numbering method people can apply without confusion. A sequential number may be enough. A company could add a year or department prefix if that helps users find records, but avoid a complicated pattern that staff must decode. Do not reuse a PO number for a different purchase, even after an order is closed. When a supplier omits the reference, the reviewer can search by supplier, amount, and date, then ask for a corrected invoice if policy requires it.

Keep document versions and change approvals

Store the original PO, revisions, invoice, delivery evidence, and approval together. When quantity or price changes, retain the revised authorization and note who approved it. This helps explain why the final invoice differs from the first estimate. Avoid overwriting records in ways that remove the history needed for review.

Use clear file names or system fields: supplier, document type, identifier, date, and project can all help retrieval. The business should decide where the authoritative record lives. If an approval is in email but the invoice is in an accounting tool and the PO is in a shared drive, link or reference them consistently. Multiple copies are not a problem when staff know which version is current and how revisions are recorded.

Make exceptions visible

Urgent purchases, card transactions, deposits, and emergency repairs may not follow the normal sequence. Define how to document them after the fact, who reviews the exception, and how quickly the paperwork must be completed. An exception path should be clear, not an unrecorded alternative to controls.

For an emergency repair, the business may need to authorize work before a formal PO can be created. The requester can record the issue, reason for urgency, supplier, expected cost, and person authorizing the work. After the immediate need is handled, attach the invoice and service report, explain why the ordinary order step was skipped, and obtain any required review. The goal is to preserve a defensible record without delaying a necessary response.

Card purchases also need a record. A card transaction may be paid quickly, but the bank feed alone may not identify the business purpose or items received. Retain the receipt, note the requester and purpose, and connect it to a project or approval where relevant. If the purchase was made outside policy, record the exception and resolution rather than altering the description to make it appear preapproved.

Review open commitments

Periodically compare open POs with actual invoices and delivery status. Close or update orders that are complete, canceled, or no longer expected. This reduces the risk that a stale commitment is mistaken for current planned spending. If the company uses forecasts, identify open commitments separately from paid expenses and unpaid invoices.

A simple open-order review can ask: Is the order still active? Has anything been delivered? Is there an invoice pending? Has the supplier confirmed the remaining amount? Did an authorized person change or cancel the work? Is the balance still relevant to the current forecast? Write down the action owner and due date when an answer is not available. Otherwise, an old PO can remain on a report long after the business has forgotten why it exists.

Plan for staff turnover and handoffs

Purchasing records often become hard to understand when the person who requested the work leaves or changes roles. A good process stores approval and scope in a shared record rather than relying only on private inboxes or verbal explanations. Use a short note to identify the business owner of an open project and the person who can confirm receipt or milestone completion.

When responsibilities change, hand over open commitments explicitly. List active suppliers, open POs, expected invoices, disputed items, recurring renewals, and payment changes under review. A handoff does not need to be elaborate; it needs to prevent a bill from being approved based on assumptions no one can verify.

How do different purchase types change the review?

The same basic questions apply across purchases, but the evidence differs. A box of supplies, monthly software subscription, construction milestone, and professional-services engagement do not have identical receiving records. A useful policy describes the evidence expected for common transaction types rather than forcing every transaction into one rigid form.

Physical goods

For goods, compare the ordered and received quantities, item descriptions, condition, delivery location, and any agreed shipping arrangements. If goods arrive in multiple shipments, record what arrived and what remains. If items are damaged or wrong, note the issue before approving the full bill and follow the return or replacement process. A carrier’s proof of delivery may establish that a package reached a location, but the responsible person may need to confirm that the contents match the order.

For products sold by weight, length, case, or other units, check that the PO and invoice use comparable measures. A unit conversion can make two matching totals look different or conceal a quantity error. If the supplier uses a different unit than the buyer, document the conversion and the basis used. Avoid changing quantities in the accounting record merely to force a match without explaining the conversion.

Professional services

For services, the purchase description should be specific enough to evaluate billing. Depending on the agreement, that may mean hours, deliverables, dates, milestones, or a fixed monthly scope. The person who understands the work should confirm that the billed period or milestone is consistent with the engagement. Finance can verify arithmetic and approval, but may not know whether a particular deliverable was accepted.

Time-based billing needs careful comparison of approved rates, recorded hours, and relevant work periods. Fixed-fee work may instead be checked against deliverables or milestones. A retainer may cover access or availability rather than a discrete output; the agreement should explain the billing basis. Do not use a generic receipt requirement that does not fit the service being purchased.

Travel, expenses, and reimbursements

Travel or reimbursable expenses may be governed by a policy or engagement agreement rather than a conventional PO. The reviewer can check business purpose, dates, category, required receipts, authorization, and whether the expense falls within agreed limits. If a supplier invoices pass-through costs, compare the invoice detail to the contract and supporting receipts when required. Record exceptions and approvals rather than assuming the presence of a vendor invoice resolves policy questions.

Subscriptions and renewals

Subscriptions can begin with a modest monthly amount and grow through added users, usage, or upgrades. The original approval should identify the owner, plan or service, renewal date, and cancellation process. Before a renewal, confirm that the business still needs the service and whether terms or pricing have changed. The invoice should be reviewed against the current agreement, not simply the first PO from years earlier.

Assign a renewal owner and maintain a calendar or system reminder. When a team member leaves, update the service owner. If the service is canceled, retain confirmation and check the next billing cycle for a final charge or credit. A recurring invoice is still a new billing event, even if the original approval remains relevant.

What tools can help organize POs and invoices?

A spreadsheet and shared document folder may be sufficient for a low volume of purchases if access, naming, approval, and backup practices are clear. As invoice volume or the number of approvers grows, accounting or payable tools may help route documents and track status. Choosing a tool should follow the process design; software cannot determine whether a purchase was actually authorized or received.

Before adopting a tool, map the steps that matter: request, approval, PO creation, receipt, invoice capture, review, coding, payment, and storage. Then decide which steps the system should support and which require a human check. Test ordinary and exceptional cases: partial delivery, amended order, recurring service, duplicate invoice, and a bill without a PO.

Consider these questions when comparing options:

• Can the tool preserve the PO number and attach supporting documents to the bill?
• Can approvals be assigned by role or amount, and can the history be reviewed?
• Can it flag duplicate invoice numbers or amounts for investigation?
• Can it distinguish a purchase commitment from a recorded bill and a completed payment?
• Can the accounting team export or review the information without losing context?
• Does the workflow suit current vendor volume and the company’s accounting setup?

A tool’s feature list is not proof that it will fit a business’s policies or recordkeeping needs. Define ownership for vendor setup, payment-detail changes, exception reviews, and access permissions. Keep human review for decisions that require contractual judgment or confirmation that work was completed.

When a spreadsheet is enough

A spreadsheet can work when purchases are relatively few, the number of approvers is small, and users can reliably update the same record. Useful columns might include PO number, supplier, requester, approver, date, purpose, estimated amount, status, expected delivery, invoice number, amount billed, amount paid, and link to supporting documents. The team should define who maintains the sheet, how changes are recorded, and how the file is backed up.

Watch for warning signs that the spreadsheet has outgrown its role: several conflicting copies, approvals buried in messages, forgotten open orders, repeated data entry, or difficulty determining which bills are waiting on a person. Those problems do not automatically mean a particular software purchase is necessary. First identify the missing control or information, then compare tools that address it.

When workflow software may help

As volume increases, a workflow tool may route bills to reviewers, retain supporting documents, track exceptions, or connect purchasing and bookkeeping records. Evaluate the actual steps it supports, how it handles unusual cases, who can change vendor details, and whether the history can be reviewed. Ask how the tool handles a bill with no PO, a credit memo, partial receipts, a corrected invoice, and a duplicate submission.

Do not automate an unclear process simply because the tool offers an automation feature. If the business has not decided who may authorize changes, the system cannot make that policy decision. If the receiving record is incomplete, automatic matching may flag a discrepancy but cannot confirm whether the goods were actually accepted. Technology is most useful when responsibilities and evidence standards are already understood.

Which common mistakes should you avoid?

• Calling the documents interchangeable. The PO records the buyer’s side of a planned purchase; the invoice is the supplier’s bill.
• Assuming a PO proves receipt. Keep delivery or service evidence where needed.
• Paying an invoice just because it includes a PO number. Review the billed items, amounts, and approval evidence.
• Using a PO as a complete contract. Confirm scope, acceptance, cancellation, and other terms in the appropriate agreement.
• Ignoring changes. Document authorized changes and retain the history.
• Creating a process no one follows. Right-size approval steps, define exceptions, and make responsibilities clear.
• Mixing planned commitments with actual spending. Label forecasts and open POs clearly so reports distinguish them from incurred costs and cash payments.
• Leaving records scattered. Store related approvals and evidence where the person reviewing or reconciling the transaction can find them.

More failure patterns to watch

Approving from memory. A requester may remember that a supplier was asked to do additional work, but the reviewer needs a traceable approval and description. Capture changes when they occur instead of reconstructing them months later.

Assuming similar totals mean the documents agree. The invoice and PO might have the same total while quantities and unit prices differ. Compare meaningful line details, not just the bottom line. Conversely, different totals may have a valid explanation such as tax or freight, but the explanation needs to be documented.

Ignoring duplicate bills. A supplier might resend an invoice after a delayed response, or a bill may be submitted to more than one inbox. Check invoice numbers and other identifying details before payment. A duplicate flag should prompt investigation, since vendors can legitimately reuse formats or issue corrected versions; it should not automatically reject a bill without review.

Letting exceptions become the standard. If every purchase arrives without approval, a policy that technically requires approval is not helping. Find out whether the steps are unclear, too slow, or assigned to unavailable people. Improve the process and monitor exceptions instead of allowing routine bypasses.

How should you choose a process for your business?

Start with the risks and decisions in your purchasing cycle, not with a form template. If spending is centralized and low volume, a documented approval and invoice review may be enough. If teams make purchases independently, vendor bills are frequent, or projects involve many deliveries, POs and matching controls may provide more visibility. The right design depends on transaction volume, contract terms, internal roles, and the cost of an error.

Try a short pilot using real examples from different purchase types. Trace one routine order, one recurring service, one partial delivery, and one change to scope. Can the team identify the approver, amount authorized, goods or work received, invoice status, and payment? Where information is missing, improve the process before adding more tools or fields.

Review the workflow after it has been used for a few weeks. Ask staff which steps prevent mistakes and which create unnecessary delay. Keep controls that protect the business, simplify redundant steps, and revise approval limits when purchasing responsibilities change. A usable process is one the team can apply consistently and explain later.

A simple design exercise

Take a recent vendor purchase and trace it from the first request to the bank transaction. Write down the date and source of each approval, the scope agreed, the document that records the commitment, proof of receipt or work, invoice review, accounting entry, and payment record. Mark every point where the reviewer had to rely on memory or search several systems. Those gaps are practical improvement targets.

Next, select a purchase that did not go smoothly: an invoice paid late, unexpected price change, duplicate bill, or delivery shortfall. Identify whether the cause was missing authorization, unclear scope, delayed receipt confirmation, incomplete invoice detail, or a routing problem. Fix the cause rather than adding a step that does not address it. For example, if invoices are delayed because no one knows who confirms service completion, assign a clear reviewer instead of requiring a more elaborate PO form.

Finally, write the proposed process in plain language. A staff member should be able to tell what to do before placing an order, where to send a bill, who confirms receipt, and how to raise a mismatch. Test the instructions with someone who did not design them. If the person must interpret ambiguous terms, revise the procedure before rolling it out.

What should a useful monthly review include?

PO and invoice controls are not only about individual payments. A periodic review helps management understand commitments still in progress and identify bills that need attention. The review can be short, but it should distinguish open commitments, received invoices, disputed amounts, unpaid bills, and payments in transit.

Start with the open-PO list. Ask whether each order is active, complete, canceled, or awaiting a delivery or milestone. Compare the remaining balance with supplier updates and project plans. Close completed orders under the company’s process, and retain documentation for cancellations or scope reductions. Do not close an order merely to make a report look clean if goods or services remain outstanding.

Next, review invoices awaiting action. Group them by reason: missing approval, missing receipt evidence, price or quantity dispute, incomplete supplier details, coding question, or scheduled payment. Assign an owner and a next action to each category. A list that says “pending” without explaining what is pending does not help the team resolve a bottleneck.

Then compare due dates and payment plans with expected cash needs. An unpaid invoice is not necessarily overdue; it may be awaiting a contractually agreed due date or a review. An open PO is not necessarily payable; it may represent future delivery. Keep the categories separate so management does not confuse expected spending with current obligations or actual cash movement.

Finally, look for recurring patterns. Are particular vendors frequently submitting invoices without PO references? Are approvals often late for one department? Are price changes appearing after renewals? Does receiving information arrive after the invoice? Such patterns may indicate that a supplier instruction, internal handoff, agreement term, or approval assignment needs attention.

What should growing businesses consider as they scale?

As a company adds employees, vendors, customers, and projects, a process based on one owner’s memory can become hard to maintain. More people may be authorized to make purchases, and no single person may know whether a supplier’s work is complete. The PO-to-invoice process can provide a common record of what was approved, what was received, and what remains unresolved.

Growth does not mean every company needs the same level of procurement formality. A services business with few recurring expenses may prioritize contract references, milestone approvals, and time records. A company buying inventory may need stronger quantity and receiving controls. A professional-services firm may track spend by engagement and client project. A business with several locations may need location-specific approval and delivery records. The appropriate design follows the work and the risks.

Consider which information leaders need to make decisions. If a manager needs to understand committed spending by department, capture department consistently. If cash forecasts need to account for expected equipment purchases, identify open commitments separately from invoices already received. If project margins matter, code relevant supplier costs to the correct project. Add fields only when someone will use the information and the team can maintain it accurately.

Reliable records can support a wider financial workflow: bookkeeping, reporting, cash planning, tax-ready records, and strategic decisions. These activities are related but not automatically identical services or one universal package. Function describes itself as a connected financial service partner combining bookkeeping and related support with a technology-supported workflow. The actual services and responsibilities depend on the agreed scope; a PO process by itself does not establish that Function performs purchasing approvals or vendor payments for a particular company.

To learn how consistent records support reporting, see Function’s bookkeeping services, financial workflow platform, and pricing information. Public prices are advertised starting points; scope, eligibility, expense limits, billing terms, and engagement documents determine what applies. Bookkeeping is not automatically the same as tax filing, and services should be confirmed for the specific engagement.

How can Function support reliable financial records?

Purchase-order workflows are part of a broader operating picture: approved spending, vendor bills, cash movement, and reporting should connect to the company’s books. Function describes its work as a connected financial service partner, combining bookkeeping and related support with a technology-supported workflow. The actual services and responsibilities depend on the agreed scope; a PO process by itself does not establish that Function performs purchasing approvals or vendor payments for a particular company.

For growing businesses, clean records can make it easier to review expenses, understand obligations, and prepare financial reports. Function’s pricing page describes service starting points and scope distinctions. Actual fees, eligibility, expense limits, billing terms, and engagement documents control what applies. A bookkeeping package should not be confused with a tax filing engagement.

When evaluating support, explain how purchasing and billing work today. How many vendor bills arrive each month? Who approves purchases? Where are orders, agreements, and receipt records stored? Which bills are commonly delayed or disputed? What reports need better supporting detail? These questions help define a practical bookkeeping workflow without assuming that an outside provider takes over purchasing decisions or payment authorization.

Schedule a 30-minute discovery conversation

Frequently asked questions

Is a purchase order the same as an invoice?

No. A PO is prepared by the buyer to document a planned purchase and approval. An invoice is prepared by the supplier to request payment for billed goods or services.

Which comes first, the PO or the invoice?

Usually the PO comes first when a business uses one, because it documents approval before ordering. An invoice follows delivery, work, or an agreed billing milestone. Some transactions follow different contract terms, such as a deposit or advance bill.

Can a supplier send an invoice without a purchase order?

Yes. A company may not require POs for every purchase, and some businesses use contracts, card approvals, or other records instead. Follow the buyer’s policy and confirm the invoice is authorized and supported before payment.

Does every invoice need to match a PO exactly?

Not necessarily. Approved changes, taxes, freight, partial deliveries, or contract billing terms can produce differences. Review each variance against the agreement and supporting records, and document the resolution.

Does a purchase order guarantee that an invoice should be paid?

No. A PO is not proof that goods arrived, work was completed, the amount is correct, or the bill is not a duplicate. Review authorization, performance or receipt, invoice details, and applicable terms before approving payment.

Can a small business use an invoice instead of creating a PO?

It may, if its policy and transaction needs allow another way to document approval. An invoice is still the supplier’s bill, not a record of the buyer’s advance authorization. Keep evidence of who approved the purchase, what was agreed, and what was received.

What if the supplier invoices before delivery?

Check the contract or accepted terms. A deposit, advance payment, or milestone invoice may be allowed, but the PO alone does not establish that payment is due. Verify the billing stage and retain the agreement and approval with the invoice.

What if the invoice has no PO number?

Follow the company’s process for bills without a PO. Search for an approved contract, email, card transaction, or other reference, and ask the requester to confirm the business purpose. Do not invent a PO number or approve a bill solely to clear a queue.

The clearest process keeps approval, delivery or work evidence, the invoice, and payment connected without confusing planned commitments with completed transactions. Choose controls your team can use consistently, and make each exception traceable.