Three-way match
Pay for what you ordered and what arrived. Nothing more.
The problem
A supplier bills 1,000 units at $52. You ordered at $50 and received 960. Pay from the invoice alone and you have overpaid by $4,000 plus sales tax, and nobody will notice until an audit, if then.
The flow, step by step
1. Purchase order. Every purchase starts with an approved purchase order in Buying: items, quantities, rates and taxes.
2. Purchase receipt. When goods arrive, the store records a purchase receipt against the PO for the quantity actually received. Rejected quantity can go to a separate warehouse.
3. Purchase invoice from the receipt. Accounts create the purchase invoice from the receipt (or the PO). Quantities and rates carry over, so the default is to bill what was received at the agreed rate.
4. Enforce the order. Buying settings can require a purchase order before any receipt or invoice, and a receipt before any invoice. Settings can also keep the rate fixed across the purchase cycle.
5. Tolerance. An over-billing allowance sets how far an invoice may exceed the order. Anything beyond it is blocked.
6. Pay. Only submitted invoices reach the payables report and the payment run.
What the team sees
On the PO: received percentage and billed percentage side by side. A PO that is 96% received and 100% billed stands out immediately.
Accounts see every invoice tied to its receipt and order. Auditors can open any payment and walk back to the order that authorized it.
In the Kestrel Workspace sample, a supplier invoice for 1,000 units is created from a receipt of 960, so the bill raised in the system is $48,000 plus sales tax, not $52,000.
With AI (coming to Sundial)
On the Sundial roadmap: an agent that reads an incoming supplier invoice PDF, matches it to the order and receipt, and flags any line that differs before a person approves. In design; not shipped.

