← The journalBUYING / FIELD GUIDE

Purchase to pay, with approvals that don't stall

A clear purchase-to-pay flow from request to payment, with approvals that protect cash without slowing the business down.

Museum architecture with directional camera-motion blur.BUYING / SUNDIAL
Photography: Harrison Lin / Unsplash ↗ · Sundial motion treatment
THE PRACTICAL TAKEAWAY

Approve once, at the right point, against a clear limit. Then let receipts and invoices match against the order without asking anyone again.

Why buying gets stuck

Purchasing has two jobs that pull in opposite directions. It has to protect cash by making sure money is spent on the right things at the right price. And it has to get material to the people who need it quickly enough that work does not stop.

Most purchasing processes lean too far one way. Either anyone can buy anything and finance discovers the commitment when the invoice arrives, or every request needs three signatures and the shop floor waits a week for consumables. Both are common, and both are fixable with a clear flow and sensible approval rules.

The flow from need to payment

In Sundial's Buying module, purchase to pay is a chain of linked documents:

  • Material request: someone needs something. Raised by a person, by a reorder level or by production planning.
  • Request for quotation: sent to one or more suppliers when the price is not already agreed.
  • Supplier quotation: each supplier's offer, recorded so offers can be compared side by side.
  • Purchase order: the commitment to a supplier at an agreed price, quantity and date.
  • Purchase receipt: what actually arrived, recorded at the dock.
  • Purchase invoice: the supplier's bill, checked against the order and the receipt.
  • Payment: made against the invoice according to its terms.

Each document is created from the previous one, so items, quantities and prices carry forward without retyping, and any invoice can be traced back to the original request.

Approve once, at the right point

The purchase order is the point of commitment, so that is where approval usually belongs. Approving the request, the order and the invoice separately triples the waiting without adding much control.

Design approvals around a few rules:

  • Limits by amount. A department head approves up to one limit, a director above it. Set the limits in your currency and review them yearly.
  • Limits by type. Capital purchases and new suppliers may need finance approval regardless of amount.
  • Pre-approved paths. Repeat purchases from contracted suppliers at contracted prices can skip approval below a set value.

Sundial's workflows let you define these states and the roles that move documents between them. Every approval is recorded with a name and a time on the document itself.

Keep approvals moving

Most approval delays come from approvers who do not know something is waiting, or who cannot approve from where they are. A few practical measures help:

  • Approvers see their pending items in one list, with the amount, supplier, requester and budget position visible without opening the document.
  • Approvals can be given from a phone. Sundial's workspace works the same on desktop and phone.
  • Every approval role has a named deputy for leave and travel.
  • Anything waiting more than two business days is flagged to the requester and the approver's manager.

Showing the budget position next to the approval is especially useful. An approver who can see that a cost center is already at its budget limit will make a better decision than one looking at a single document in isolation.

Three-way match without manual checking

When the supplier's invoice arrives, it should match what was ordered and what was received. This is the three-way match: order, receipt and invoice agree on item, quantity and price.

Because the purchase invoice in Sundial is created from the order or the receipt, quantities and prices start out matching. Differences appear only where the supplier billed something different, which is exactly where someone should look. Set a tolerance for small rounding differences, and route anything above it back to the buyer rather than to the approver.

Paying on time, not early or late

Payment terms on the purchase order flow to the invoice, so each invoice carries a due date. The accounts payable list then shows what is due this week, what is overdue and what can wait. Paying on the due date, rather than when someone remembers, protects both cash and supplier relationships.

Where suppliers offer an early-payment discount, record it in the payment terms so it is visible when choosing what to pay.

Signs the process needs work

  • Invoices arriving for purchases with no order behind them.
  • Orders approved after the goods have already arrived.
  • Material requests waiting days for a quotation that could have come from a contracted price.
  • Approvers clearing large batches at once, which usually means they are not really reviewing.

We are building Sundial so an AI agent can draft the purchase order from an approved request, compare supplier quotations and wait for your approval before anything is sent. To walk through the flow on sample data, try the demo.