Book a free consultation (opens in a new tab)

Purchase Module

Purchase and Procure to Pay Module Services

Not in one dramatic loss, but in small leaks nobody logs. A buyer rings their usual supplier instead of the contracted one.

  • 3Documents in every match
  • 2-5%Typical match tolerance
  • 3-4Approval tiers that hold

Why It Matters

Control is the whole point of this module

Maverick buying, price drift, double payment, loose sign-off

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.

  • 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.

  • 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

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 we set up when we configure purchasing

  • Approval matrix

    Value tiers, category rules and cost centre routing 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 absolute value, with a defined hold and escalation path on a failed match.

  • 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.

Why teams hand us the purchase module

  • We design the controls first

    Approval tiers, tolerance rules and the approved supplier list are agreed on paper before configuration, because they are business decisions.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

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.

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.

Related

The other services in this section, and related pages from TCB Infotech.

Put Controls Around Your Purchasing

No commitment. A practical look at your procure to pay process, whichever ERP you run.