A vendor invoice arrives for a quantity larger than what was actually received. The purchase order says one thing, the packing slip says another, and the invoice a third — and by the time anyone in accounts payable notices the discrepancy, the invoice has already been paid, because nothing in the process required the three documents to actually agree before payment went out.
Creating a purchase order in Business Central is genuinely simple. The part that actually protects a business — matching what was ordered, received, and invoiced before money moves — depends on functionality most companies never fully configure, leaving the whole process resting on someone manually eyeballing three documents and hoping they catch a mismatch.
The Three-Way Match Problem
A purchase order, a receipt, and a vendor invoice each represent a different moment in the same transaction — what was ordered, what actually arrived, and what the vendor is billing for. When all three agree, payment is straightforward. When they don't, someone needs to catch the discrepancy before it's paid, not after.
Business Central's structure naturally supports this: posting a purchase receipt separately from posting the invoice creates distinct records for what was ordered versus what was received, and the invoice can then be checked against both. The gap isn't in the platform's capability — it's that a lot of companies post receipts and invoices together, in a single step, specifically because it's faster, which quietly collapses the three-way check into a single step where nothing is actually being compared.
Over-Receipt and Quantity Discrepancies
A related, common issue: a vendor ships more than what was ordered, or invoices a quantity that doesn't match either the order or the receipt. Without a deliberate process step forcing comparison — someone specifically checking received quantity against ordered quantity before invoice posting — these discrepancies get absorbed silently, either overpaying a vendor or accepting stock that was never actually authorized for purchase.
This is a process discipline issue more than a configuration issue: the data needed to catch the discrepancy already exists in the separate purchase order, receipt, and invoice records. The fix is making comparison a required step before payment, not assuming it happens naturally because the documents are all sitting in the same system.
Approval Workflows for Purchase Documents
Business Central ships with ready-to-use approval workflow templates specifically for purchase documents — covered in more depth elsewhere on this site — and a properly configured purchase approval workflow is one of the most direct ways to insert a genuine second set of eyes before a purchase order commits the business to a vendor obligation at all, not just before payment. Companies running a single basic approval, or none, are relying entirely on whoever creates the PO exercising good judgment alone, with no structural check in place.
Requisition Worksheets for Planned, Not Reactive, Purchasing
The Requisition Worksheet lets purchasing decisions be driven by actual demand — sales orders, reorder points, production requirements — rather than reactive, ad hoc ordering whenever someone notices stock running low. This is also the tool used to generate purchase orders for drop shipments and special orders directly from linked sales orders, pulling order details automatically rather than requiring manual re-entry. Companies that skip this and create every purchase order manually, one at a time, lose the planning visibility this worksheet is specifically built to provide.
What Well-Managed Purchase Order Processing Looks Like
A mature process treats the purchase order, the receipt, and the invoice as three distinct checkpoints, each posted separately rather than collapsed together, with a genuine comparison step before payment authorization. Approval workflows add a review layer at the commitment stage, before the order is even placed. Purchasing decisions flow from actual demand through the Requisition Worksheet rather than from whoever happened to notice a shortage first. None of this requires custom development — it requires using functionality that's typically already sitting in the environment, configured deliberately rather than bypassed for speed.
Where to Start
If your accounts payable team is currently trusting vendor invoices without a documented three-way match against the purchase order and receipt, that's the highest-priority gap to close first. From there, it's worth checking whether purchase approval workflows are actually configured beyond a single basic sign-off, and whether purchasing is being driven by the Requisition Worksheet or by ad hoc requests as shortages get noticed.