Accounts Payable & Receivable
Purchase Orders & 3-Way Matching
A purchase order is a buyer-issued document that commits to buy specified goods or services at agreed quantities and prices from a supplier. It formalizes the order, sets the commitment for budgeting, and becomes the reference document that goods receipts and invoices are matched against in the procure-to-pay cycle.
Real-world example
Procurement raises PO #4501 for 100 units at $25 each; the warehouse and AP later match deliveries and invoices to it.
Invoice Processing
Vendor Management
Purchase Orders & 3-Way Matching
Three-way matching compares three documents before an invoice is paid: the purchase order (what was ordered), the goods receipt note (what was received), and the supplier invoice (what is billed). If quantity and price agree across all three within tolerance, the invoice is approved; discrepancies raise an exception.
PO: 100 units @ $25 = 2,500
GRN: 100 units received
Invoice: 100 units @ $25 = 2,500 -> match, approve for payment
Real-world example
An invoice passes three-way match automatically because the PO, receipt, and invoice all show 100 units at $25.
Invoice Processing
Purchase Orders & 3-Way Matching
Payment Runs
Two-way matching compares the PO to the invoice only (used for services with no goods receipt). Three-way adds the goods receipt note. Four-way matching adds an inspection/quality certificate confirming the goods passed inspection. More match points give stronger control but require more documentation.
Real-world example
Consulting fees use two-way matching, inventory uses three-way, and regulated pharmaceutical receipts use four-way with a QC inspection.
Invoice Processing
Purchase Orders & 3-Way Matching
Vendor Management
A GRN is a record created when goods are received, documenting the items, quantities, and condition. It confirms delivery against the PO, triggers the inventory/expense entry via the GR/IR account, and provides the receipt evidence used in three-way matching against the invoice.
Real-world example
The warehouse scans a delivery and creates a GRN for 98 of 100 ordered units, so only 98 will match the invoice.
Invoice Processing
Reconciliations
Purchase Orders & 3-Way Matching
Matching tolerance is an allowed variance (absolute or percentage) between the PO/receipt and the invoice within which the system auto-approves rather than raising an exception. Small tolerances (e.g., 2% or $5) absorb rounding, freight, or minor price changes, reducing low-value exceptions while still catching material discrepancies.
PO price $25.00, invoice $25.30, tolerance 2% ($0.50):
Variance $0.30 < $0.50 -> auto-match.
Invoice $26.00: variance $1.00 > tolerance -> price exception.
Real-world example
Setting a 2% price tolerance eliminates hundreds of trivial rounding exceptions each month while still flagging real overcharges.
Invoice Processing
Purchase Orders & 3-Way Matching
Aging Analysis
Typical causes: price on the invoice differs from the PO; invoiced quantity exceeds the received quantity; goods received but no GRN posted; wrong PO referenced; unit-of-measure mismatch; freight or extra charges not on the PO; or partial deliveries. Each routes to the relevant party—buyer for price, warehouse for receipt—to resolve.
Real-world example
An invoice for 100 units fails matching because only 90 were received; the buyer confirms the rest are backordered and the invoice is short-paid to 90.
Invoice Processing
Payment Runs
Purchase Orders & 3-Way Matching
A PO can be received and invoiced in multiple tranches. Each goods receipt and invoice matches against the open (un-received/un-invoiced) PO quantity, drawing it down over time. The system tracks cumulative received and invoiced amounts so total invoiced never exceeds total received and ordered.
PO 100 units. Delivery 1: 60 (GRN + invoice 60). Delivery 2: 40.
Each invoice matches the received tranche; PO closes at 100 total.
Real-world example
A blanket PO for 1,000 units is drawn down across monthly deliveries, each matched to its own receipt and invoice.
Invoice Processing
Purchase Orders & 3-Way Matching
Reconciliations
A blanket PO is an agreement to buy up to a set quantity or value over a period at agreed prices, released in multiple deliveries. It reduces administrative effort for recurring purchases, locks in pricing, and lets each release be received and invoiced against the single umbrella PO until it is exhausted or expires.
Real-world example
A blanket PO covers a year's office supplies at fixed prices, with weekly deliveries released against it.
Vendor Management
Purchase Orders & 3-Way Matching
Credit Control
Raising a PO is a commitment only—no financial posting. On goods receipt, you debit inventory/expense and credit GR/IR. On invoice receipt, you debit GR/IR and credit accounts payable. On payment, you debit AP and credit bank. GR/IR nets to zero once receipt and invoice match, isolating timing differences.
PO: (no journal, commitment only)
GRN: Dr Inventory 2,500 Cr GR/IR 2,500
Invoice: Dr GR/IR 2,500 Cr AP 2,500
Payment: Dr AP 2,500 Cr Bank 2,500
Real-world example
Finance can see received-not-invoiced liabilities in the GR/IR balance even before invoices arrive.
Invoice Processing
Reconciliations
Purchase Orders & 3-Way Matching
Because goods receipts post to GR/IR independently of invoices, the open GR/IR balance at period-end represents goods/services received but not yet invoiced—a real liability. Finance accrues this automatically from GR/IR rather than estimating, improving accuracy. Conversely, invoiced-but-not-received items are investigated as possible errors or early billing.
Period-end open GR/IR (received, not invoiced) = $32,000
-> recognized as an accrued payable with no manual estimate.
Real-world example
Month-end accruals are driven straight from the GR/IR report, cutting manual accrual journals and audit queries.
Invoice Processing
Reconciliations
Aging Analysis