Startup Purchase Orders: Use a Practical Three-Way Match

A startup can lose control of spending long before it needs a large finance system. Someone approves a subscription, another person receives an invoice, and a third person pays it without knowing whether the agreed service was delivered. A three-way match connects approval, receipt, and billing before payment.

The process does not need to be bureaucratic. It needs clear fields, ownership, exceptions, and a record that can be checked. Keep it proportionate to the purchase and use qualified accounting and tax guidance for the company's jurisdiction.

Define the three records

The purchase order or equivalent approval states supplier, scope, quantity, price, currency, tax treatment where known, delivery or service period, payment terms, budget owner, and approval. The receipt record confirms what was actually delivered or accepted. The invoice states what the supplier is asking to be paid.

For services, receipt is not a box arriving. It may be an accepted milestone, enabled software entitlement, verified consulting deliverable, or agreed monthly service. Name the person qualified to confirm it. Finance should not infer technical acceptance merely from an invoice.

Match the meaningful fields

Compare supplier identity, purchase reference, line items, quantity, unit price, currency, service period, taxes, and total. Use a defined tolerance only where appropriate and approved. A small rounding difference differs from an extra month or a changed payment currency.

Watch partial delivery and partial billing. A purchase for ten devices may arrive in two shipments. Track cumulative received and invoiced quantities so the second invoice cannot accidentally pay for the first shipment again. Preserve the links between records.

Separate approval from payment

Where staffing allows, the requester should not be the only approver and payer. In a very small company, use a second-person review for higher-value or unusual purchases. Record authority thresholds and escalation rather than asking staff to guess who can approve an exception.

Supplier bank changes need independent verification through a known channel. A perfectly matched invoice can still contain fraudulent payment instructions. Never rely only on the new email, phone number, or document supplied with the change request.

A subscription example

A team approves twelve software seats for one year. The invoice charges fifteen seats and adds an implementation fee not in the order. The service owner confirms only twelve seats were requested and enabled. Finance holds the disputed lines and asks the supplier for a corrected invoice.

The accepted portion can proceed under the company's policy while the exception remains documented. The team does not edit the supplier's invoice to make it match. It retains the original, correction, communication, and final approval so the payment history is explainable.

Handle exceptions explicitly

Common categories include missing approval, no receipt confirmation, price difference, duplicate invoice, incorrect tax, wrong entity, wrong currency, and disputed scope. Give each an owner, next action, and deadline. A held invoice should not disappear from cash planning just because payment is paused.

Emergency purchases can use a documented fast path with retrospective evidence, but the exception should not become the default. Record why ordinary approval was impractical and who accepted the urgency. Review repeated exceptions for a broken purchasing workflow.

Prevent duplicate payments

Use supplier ID, invoice number, amount, currency, date, and purchase reference together. Invoice numbers can contain spacing or punctuation differences, but normalization should not collapse distinct records blindly. Flag possible duplicates for review rather than automatically deleting them.

Check credits and cancellations against the original invoice. A credit note reduces an obligation only according to its scope and accounting treatment. Preserve the relationship and avoid paying an invoice in full while the credit is stranded in a separate folder.

Build a simple tracker

Use columns for approval ID, supplier, scope, budget owner, approved amount, currency, receipt status, invoice ID, invoice amount, difference, exception, due date, payment status, and evidence link. Keep actual payment confirmation distinct from approved-for-payment status.

Restrict access because supplier banking and invoices can contain sensitive information. Store documents in the approved system and use links in the tracker. Do not email a broad spreadsheet containing every bank account merely to make approvals convenient.

Close the loop

After payment, reconcile the bank transaction, invoice balance, and accounting entry. Track overdue invoices and unresolved disputes. For recurring purchases, review renewal dates and unused entitlements before the next commitment begins.

Document the distinction between accepted delivery and an invoice received by email. For a consulting milestone, the technical owner should confirm the agreed deliverable, while finance verifies billing. A supplier’s statement that the work is finished cannot replace the customer’s acceptance record.

Conclusion

A three-way match makes spending concrete: approved scope, accepted delivery, and accurate billing. Match important fields, verify payment changes independently, record exceptions, and reconcile the final transaction. The result is a small control that reduces costly mistakes without turning every purchase into a large project.