Skip to main content
Purchase Module

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.

Procure to Pay Chain
Illustrative
One order, six documents, one place where they have to agree
Purchase requisition
PR-1042 · Raised by production · 40 units
Submitted
Approval
Value tier 2 · Department head
Approved
Purchase order
PO-2210 · Call-off on agreement AG-07 · 40 at 118.00
Sent
Goods receipt
GRN-3391 · 38 of 40 received · balance open
Partial
Three-way match
Order40 at 118.00
Receipt38 received
Invoice38 at 119.50
Price variance 1.3 percent, inside the 2 percent tolerance. Cleared.
Supplier invoice
INV-8814 · 38 units · 4,541.00
Matched
Payment
Due in 30 days · accrual cleared on match
Scheduled
Two units still on order, so the line stays open and the accrual stays visible at period end.
3
Documents in every match
2-5%
Typical match tolerance
3-4
Approval tiers that hold
0
Failed projects since 2021
Why It Matters

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.

The Four Quiet Leaks

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.
Comparing supplier invoices against purchase orders and contracted prices
Requisition and Approval

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.
A department head reviewing purchase requisitions and approval limits
What The Module Covers

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.

📝
Requisition and approval
An internal request with quantity, need-by date, cost centre and reason, routed by value tier and category. The approver is chosen by the document, not by who is available. Budget availability is checked here, while it can still change the answer.
📊
RFQ and supplier comparison
One request out to several suppliers, quotes back on the same lines, compared on landed cost rather than unit price. The reason the winning supplier won is written on the record, so the decision survives the buyer leaving.
📋
Purchase orders and agreements
Orders against a supplier, with terms, delivery schedule and tax. Blanket orders hold a contracted price and volume across a period, and call-off orders draw against them, so the agreed rate is applied by the system instead of recalled from memory.
📦
Goods receipt and returns
Partial receipts against an open order line, over and under delivery tolerance, rejection on arrival and return to vendor with a debit note. Receipt is also the accounting event that turns a purchase into stock with a value.
✅
Invoice matching and AP handoff
Order, receipt and invoice compared on quantity and price within tolerance. Matched invoices clear the goods received not invoiced accrual and post to payables. Mismatches are held and routed with the variance shown, not silently paid.
🏢
Supplier master and performance
One controlled vendor record per supplier, with approved lists by category, and on-time delivery, rejection rate and price variance measured from transaction history so the annual review runs on data rather than on impressions.
How It Works

The procure to pay cycle, end to end

1
Requisition
The department states what it needs, how many, by when and against which cost centre. No supplier contact yet, and no commitment.
2
Approval
Routed by value tier and category to the person who carries the budget. The need and the spend are approved as two separate decisions.
3
Purchase order
Raised against an approved supplier, priced from the agreement if one exists, with terms, tax and a delivery schedule the supplier confirms.
4
Goods receipt
What arrived is counted against what was ordered. Partials leave the line open, rejections go back, and the accrual is posted.
5
Match and pay
Order, receipt and invoice compared on quantity and price. Inside tolerance it clears to payables and pays on terms. Outside it, it waits.
What Is Included

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 Changes

What controlled purchasing actually buys you

Zero
Invoices paid without a match
One
Record per supplier
Real
Landed cost in the margin
Less
Buying outside agreements
Clean
Goods received not invoiced
Evidence
In every supplier review
Why Us

Why teams hand us the purchase module

1
We design the controls first
Approval tiers, tolerance rules and the approved supplier list are agreed on paper before anything is configured, because they are business decisions, not settings.
2
We clean the vendor master
Duplicate supplier records are where both honest error and outright fraud live. We de-duplicate and verify bank details before the first order is raised.
3
Matching is automatic or it fails
If someone has to open three documents by hand, matching stops happening in the first busy week. We set it up so only the exceptions need a human.
4
Landed cost done properly
For importers this is the difference between a margin figure you can act on and one that is quietly wrong by the cost of freight and duty.
5
We make the right path the easy one
Most purchasing problems are not solved by a better buyer. They are solved by making the controlled path faster than the workaround, and we design for that.
6
Platform neutral advice
We deliver on ERPNext, Odoo and SAP. The control design is the same on all three, so we have no reason to push you towards one of them.
FAQ

Purchase module questions

What is a three-way match and why does it matter?
A three-way match compares the purchase order, the goods receipt and the supplier invoice before anything is paid. The order says what you agreed to buy and at what price, the receipt says what actually arrived, and the invoice says what you are being asked to pay. If all three agree on quantity and price within tolerance, the invoice is cleared for payment automatically. If they do not, it is held and routed to whoever can explain the difference. It matters because it is the only control that catches a price that crept above the agreed one, a quantity billed but never delivered, and a second copy of an invoice already paid last month.
How are approval limits configured?
Usually by value tier and by category, sometimes by cost centre as well. A common shape is that a supervisor clears anything up to about 50,000, a department head up to about 250,000, and a director or the board above that, with capital items and anything outside the approved supplier list routed separately regardless of value. The system holds the matrix, so the approver is decided by the document rather than by who happened to be in the office. Keep the tiers few and the approvers named. A matrix with nine levels gets bypassed within a month.
How do we stop people buying outside agreed suppliers?
Not with a policy email. You stop maverick buying by making the controlled path the easier one. Put the approved supplier and the contracted price on the requisition screen so ordering correctly takes fewer clicks than ringing a supplier direct. Then block or flag purchase orders raised against suppliers outside the approved list for that category, and report the exceptions weekly by requester. Most purchasing problems are not solved by a better buyer, they are solved by making the controlled path easier than the workaround.
Does the module handle landed cost?
Yes, and for importers it is the part worth setting up carefully. Freight, duty, insurance, clearing and port charges arrive on separate invoices, often weeks after the goods. A landed cost voucher apportions those charges across the receipt lines, by value, by weight or by volume depending on the charge, and writes the result into the item cost. Without it your unit cost is the supplier price alone, which means your gross margin report is wrong by whatever the freight and duty came to, and on imported goods that is rarely a small number.
How are partial and over deliveries treated?
A purchase order line stays open until it is fully received or closed by hand, so a partial receipt posts the quantity that arrived and leaves the balance outstanding on the order. Over delivery is governed by a tolerance, often around 5 percent or a small absolute quantity, set per item or per category. Inside tolerance the extra is received and matched. Outside it the receipt is blocked until someone with authority accepts the excess or rejects it. Rejected goods go out on a return to vendor with a debit note, so stock and the payables position both stay right.
How does purchasing connect to accounts payable?
Goods receipt is the accounting event, not the purchase order. Receiving the goods debits stock or expense and credits a goods received not invoiced accrual, so the cost sits in the right period even though no invoice has arrived. When the supplier invoice comes in and matches, the accrual is cleared and a payables balance is created against the vendor. That accrual is the period-end number your finance team will ask about, and it is also the quickest health check on your purchasing data: if it is large and old, receipts and invoices are not being matched.

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.

Purchase Module Features

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.

Core Features

From an internal request to a matched invoice

Sourcing and Agreements

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.
Comparing supplier quotations on landed cost before awarding a purchase order
Receipt and Matching

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.
Matching a supplier invoice against the purchase order and goods receipt note
Supplier Master and Performance

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.
A purchasing team running a supplier performance review from transaction data
What You Get

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.