Purchasing Without Controls Is Where Money Leaks Quietly
Not in one dramatic loss, but in small leaks nobody logs. A buyer rings their usual supplier instead of the contracted one. A price drifts three percent above the agreement and no one compares. An invoice gets paid twice because two people were chasing the same supplier. An approval happens because whoever was nearest signed it. The purchase module closes those gaps by making every order pass through a requisition, an approval and a match before money moves.
50+ ERP and software projects. Zero failed projects since 2021.
Control is the whole point of this module
Everything else purchasing software does is convenience. The part that pays for the project is the set of controls that stop spend happening outside an agreement, above a price, or twice. None of them are difficult. Most organisations simply never put them in.
Maverick buying, price drift, duplicate payment, casual approval
Maverick buying is when someone orders outside the agreed supplier because it was faster, and you lose the contracted price and the volume rebate at the same time. Price drift is when the invoice is a few percent above the agreement and nobody compares, month after month. Duplicate payment happens when the same invoice arrives by post and by email and two people process it. Casual approval is the spend signed off by whoever was nearest rather than by whoever carries the budget. Each one is small. Together, on a business buying steadily, they are usually a few percent of purchase spend.
- Contracted price applied by the system, not remembered by a person.
- Duplicate invoice numbers blocked at entry against the same vendor.
- Every approval recorded against a value tier, with a name and a timestamp.

The cheapest control most organisations skip
A requisition is just an internal request: someone says what they need and why, before anyone talks to a supplier. It costs nothing and it separates two decisions that get muddled constantly. Approving the need is an operational call, made by the person who knows whether the department can manage without. Approving the spend is a financial call, made against a budget and a value tier. When you only have a purchase order, both decisions collapse into one signature and the budget holder usually finds out afterwards. Put the requisition in and you also get the first honest record of demand, which is what makes purchase history worth analysing later.
- Approval limits by value tier, by category and by cost centre.
- Capital items routed separately whatever the value.
- Budget checked at requisition, not discovered at invoice.

Six areas, from the internal request to the supplier review
These are the working parts of procure to pay. Get the first five right and the sixth writes itself, because supplier performance is nothing more than a report over transactions you already recorded properly.
The procure to pay cycle, end to end
What we set up when we configure purchasing
Approval matrix
Value tiers, category rules and cost centre routing, written down and configured, with a deputy named for every approver so nothing stalls on one person's leave.
Clean supplier master
Duplicate vendor records merged, tax and bank details verified, payment terms set per supplier, and approved supplier lists built by purchase category.
Agreements and call-offs
Blanket orders holding contracted price and volume over a period, with call-off orders drawing against them and the remaining volume visible on the agreement.
Match tolerance rules
Quantity and price tolerances set per category, usually a small percentage or a small absolute value, with a defined hold and escalation path when a match fails.
Landed cost setup
Freight, duty, insurance and clearing apportioned onto receipt lines by value, weight or volume, so the item cost carries the real cost of getting it here.
Supplier scorecard
On-time delivery, quality rejection rate and price variance reported from your own purchase history, ready for the first supplier review after go-live.
What controlled purchasing actually buys you
What this connects to
Purchasing sits between the decision to buy and the moment the goods become stock, and the history it leaves behind is what any spend analysis is built on.
Why teams hand us the purchase module
Purchase module questions
What is a three-way match and why does it matter?
How are approval limits configured?
How do we stop people buying outside agreed suppliers?
Does the module handle landed cost?
How are partial and over deliveries treated?
How does purchasing connect to accounts payable?
Put Controls Around Your Purchasing
Book a free consultation. We will walk through how you buy today, where approvals actually happen, what your vendor master looks like, and what a requisition to payment chain with automatic matching would change for your finance and purchasing teams.
Book a Free Consultation →No commitment. A practical look at your procure to pay process, whichever ERP you run.
What Is Inside the Purchase Module
Six documents, one chain, and a set of rules that decide when money is allowed to move. Here is what each part does, where the controls sit, and the detail that usually gets skipped in a demo and then hurts at the first period end.
From an internal request to a matched invoice
Quotes compared on landed cost, prices held in an agreement
One request for quotation goes out to several suppliers on identical lines, and the responses come back onto a single comparison. The comparison is on landed cost, not unit price, because a supplier who is two percent cheaper per unit and charges freight separately is often the more expensive one. The reason the winner won is recorded on the document. Where you buy the same item repeatedly, a purchase agreement or blanket order fixes price and volume across a period and call-off orders draw against it, so the contracted rate is applied by the system rather than recalled by whoever raises the order.
- Identical RFQ lines out, comparable quotes back.
- Landed cost comparison including freight, duty and clearing.
- Blanket orders with remaining volume visible on the agreement.

What arrived, what was ordered, what you were billed
Goods receipt records the quantity that actually turned up against the order line. Partial receipts leave the balance open, over deliveries are checked against a tolerance before they are accepted, and anything rejected on arrival goes back on a return to vendor with a debit note. Receipt also posts the accrual for goods received not invoiced, so the cost lands in the right period. When the invoice arrives, the three-way match compares order, receipt and invoice on quantity and price. Inside tolerance it clears the accrual and posts to payables without a human. Outside it, it is held with the variance shown and routed to someone who can settle it.
- Partial receipt, over and under delivery tolerance, return to vendor.
- Goods received not invoiced accrual posted at receipt.
- Only the exceptions reach a person, which is what makes AP scale.

One record per supplier, and a review that runs on data
A controlled vendor master is a quiet control that does a lot of work. Duplicate supplier records let the same invoice be paid twice under two codes, hide how much you actually spend with one company, and are the standard route for payment fraud, because a second record with different bank details looks ordinary. So new suppliers are created by a small number of people, bank detail changes are verified out of band, and approved supplier lists are held per purchase category. On top of that clean data the system tracks on-time delivery, quality rejection rate and price variance against agreement, which turns the annual supplier review from a conversation about impressions into one about numbers.
- Vendor creation and bank detail changes as controlled actions.
- Approved supplier lists by purchase category.
- On-time delivery, rejection rate and price variance from real history.

Everything the purchase module gives you
Requisition workflow
Internal requests with cost centre, need-by date and reason, routed by value tier and category, with a named deputy for every approver.
RFQ comparison sheet
Quotes from several suppliers on the same lines, ranked on landed cost, with the award reason recorded against the chosen supplier.
Agreements and call-offs
Contracted price and volume held for a period, with call-off orders drawing down against the agreement and the balance always visible.
Receipt and return handling
Partial receipts, tolerance on over and under delivery, rejection at the dock and return to vendor with the matching debit note.
Automatic three-way match
Order, receipt and invoice compared on quantity and price, cleared inside tolerance and held with a stated variance outside it.
Landed cost apportionment
Freight, duty, insurance and clearing spread onto receipt lines by value, weight or volume, so item cost reflects what the goods really cost.

