>
Contact Let's Talk
Home › ERP › Procurement

Procurement software and e-procurement systems that hold the control

Most procurement software is bought to speed up purchase orders and ends up judged on something else entirely: whether the organisation still pays for goods it never received. We implement e-procurement and purchase-to-pay across SAP MM and Ariba, Oracle Fusion Cloud Procurement, Microsoft Dynamics 365 and MJC’s Xtreme Industry ERP — designing the three-way match, the release strategy and the vendor master controls first, and the user interface second.

3-way
Match as the core control
4
Procurement platforms
GSTR-2B
Reconciled to the purchase register
ISO 27001
Certified information security

The controls we design before anything is configured

  • Three-way match rules and tolerance limits, by material group
  • Release strategy mapped to document characteristics, not to job titles
  • Vendor bank-detail change with an out-of-band call-back step
  • Catalogue and contract pricing so free-text stays the exception
  • Contract expiry, auto-renewal and escalation-clause alerts
  • Supplier IRN and GSTIN validation before an invoice is parked
Where the money actually goes

Procurement does not leak at the purchase order. It leaks between three documents

A purchase order, a goods receipt and a supplier invoice describe the same transaction three times, from three different parties, at three different moments. Everything procurement software is meant to protect lives in whether those three descriptions agree before money moves. That is the three-way match, and it is the only control in purchase-to-pay that reliably prevents paying for what was not delivered — not approval hierarchies, which authorise intent rather than verify receipt.

The honest difficulty is tolerance design. A match that demands exact agreement on price and quantity generates an exception on almost every invoice: rounding on freight, a part-delivery, a unit-of-measure conversion, a rate difference of a few paise. Accounts payable then drowns, ages out its own queue, and someone grants a blanket release to clear month end. Set tolerances too wide and the control becomes theatre — a five per cent quantity tolerance on a high-value commodity is an invitation. The work is per-material-group tolerance keys and price-unit discipline, so genuine exceptions are rare enough to be investigated properly.

The second structural problem is spend nobody can see. Maverick spend — buying outside the process, on a credit card, a verbal order, or an invoice that arrives with no purchase order behind it — is the reason category negotiations fail. You cannot commit volume you cannot measure, and the supplier knows it. Policy does not fix this. The compliant path has to be genuinely faster than the workaround: a catalogue item that takes four clicks and is approved in an hour beats a procurement policy memo every time. An e-procurement system earns its licence fee by winning that race, not by adding a gate.

Invoices paid on a two-way matchPrice and PO agree, receipt is never checked, and short deliveries are absorbed silently.
No-PO invoices arriving in APSpend is committed before procurement sees it, so there is nothing left to negotiate.
Release strategy broken by a reorgA new cost centre or plant falls outside the characteristics, and the document releases itself.
Input tax credit lost at GSTR-2BMismatches surface months later, after the window to chase the supplier has closed.
Capabilities

What we configure in a procurement and source-to-pay implementation

Each of these is a distinct object set with its own masters, documents and reconciliations. Weakness in any one of them shows up as either a payment loss or a queue of frustrated requisitioners.

Three-way matching and invoice tolerances

The invoice is blocked until purchase order, goods receipt and invoice reconcile within a defined tolerance. We design the tolerance set per material group and per value band, because the right limit for packaging consumables is wrong for a bearing assembly.

  • Quantity, price and schedule tolerance keys set separately for lower and upper limits
  • Absolute and percentage limits together, so a small percentage on a large value still stops
  • Service entry sheets substituting for goods receipt on service lines, with acceptance recorded
  • Blocked-invoice ageing report and a named release authority — never a blanket month-end release

Requisition to purchase order and release strategies

Approval routing is where procurement software is configured badly most often. In SAP, release strategies fire against document characteristics — purchasing group, plant, material group, total value — not against a person. Elsewhere it is workflow rules on the same fields. Either way, the rule is only as good as the characteristic coverage.

  • Release codes, prerequisites and release groups mapped to a documented delegation of authority
  • Value bands that account for currency and for the line-versus-header value question
  • Substitution and escalation rules so approvals do not park in an absent approver’s inbox
  • A characteristic-coverage test that proves no combination of plant and cost centre escapes a strategy

Supplier onboarding and vendor master control

The vendor master is the most attacked object in any finance system. Bank-detail change requests are the standard payment-diversion route, and they arrive on convincing letterhead. The control is an out-of-band verification call to a number already on file, performed by someone who cannot also release the payment.

  • Supplier self-registration capturing GSTIN, PAN, MSME status, bank details and compliance documents
  • Bank-detail change as a sensitive field with dual authorisation and a recorded call-back to a pre-existing number
  • Segregation between the role that maintains the vendor and the role that releases payment
  • De-duplication on PAN, GSTIN and bank account before creation, with a periodic duplicate-vendor sweep

Catalogues, punchout and free-text requisitions

Free-text requisitions are where price leakage happens: the buyer types a description, a price and a supplier, and no contract rate is applied. Catalogue coverage is the single most useful metric in an e-procurement rollout, because every percentage point moved from free-text to catalogue is a price you already negotiated.

  • Internal catalogues built from contract items, with contract price pulled onto the requisition automatically
  • Punchout to supplier-hosted catalogues over cXML or OCI, returning a priced shopping cart
  • Free-text requisitions routed to a buyer for sourcing rather than converting straight to a purchase order
  • Catalogue-versus-free-text coverage reporting by category, used to drive the next sourcing wave

RFQ, sourcing events and award

RFQ software is only useful if the comparison is like-for-like. Most sourcing disputes come from suppliers quoting different incoterms, payment terms, packaging or validity and being compared on headline rate alone.

  • RFQ from requisition or from a sourcing project, with a sealed response window and an audit trail
  • Landed-cost comparison normalising freight, duty, incoterms and payment terms across quotations
  • Technical and commercial evaluation kept separate, with technically-unqualified bids excluded before price is opened
  • Award creating the outline agreement or contract directly, so the negotiated price becomes the buying price

Contract lifecycle management

Contracts fail on dates, not on drafting. An auto-renewal that passes unnoticed locks in last year’s rate for another term, and an unindexed escalation clause quietly raises the rate without a negotiation ever taking place.

  • Contract register with expiry, notice-period and auto-renewal dates driving staged alerts before the notice window closes
  • Price-escalation clauses modelled against their index, so a claimed increase can be checked rather than accepted
  • Release order value and quantity tracked against the contract ceiling, with consumption reporting
  • Clause library and approval workflow for deviations, so legal reviews exceptions rather than every document

Spend analysis and supplier consolidation

Spend analysis software is a classification problem before it is a reporting problem. Until every transaction carries a category, the numbers argue with each other. The useful split is addressable spend — where a sourcing decision can still change the price — against non-addressable spend such as statutory levies and regulated utilities.

  • Category taxonomy applied to transaction history, with rules plus manual review of the unclassified tail
  • Addressable versus non-addressable split, so savings effort is aimed at spend that can actually move
  • Supplier fragmentation analysis: how many suppliers serve one category, and what consolidation would be worth
  • Tail-spend and no-PO spend reporting, which is usually the first honest picture of maverick buying

GST, TDS and e-invoice validation on the buy side

Indian procurement carries statutory work the global product does not ship with. Input tax credit is lost quietly — not by error in your ledger, but because a supplier never filed. Reconciliation of GSTR-2B against the purchase register is the control that catches it while the supplier can still be chased.

  • GSTR-2B to purchase register reconciliation with supplier-wise mismatch follow-up and an ITC-at-risk view
  • Reverse charge determination and self-invoicing where the supplier is unregistered or the service is notified
  • TDS under section 194Q on purchases past the annual threshold, with interaction against the supplier’s TCS position
  • Supplier IRN and QR validation on inbound e-invoices before the invoice is parked, and GSTIN status checks at onboarding
Diagnostic

Where procurement leaks money, and the control that closes each gap

The leakWhy it happensThe control that fixes itWhere it lives in the system
Paying for goods not receivedInvoice matched to the purchase order only; receipt is never verified against itMandatory goods-receipt-based invoice verification, with quantity tolerance kept tight on high-value groupsPurchase order item flags plus invoice-verification tolerance keys
Price paid above the negotiated rateRequisition raised as free text, so no contract condition is appliedContract or catalogue reference enforced for covered categories; free text routed to a buyerCatalogue, outline agreement and requisition source-determination rules
Maverick and no-PO spendThe compliant path is slower than a phone call, so people route around itFast catalogue path with low-value auto-release, plus a no-PO invoice exception report with an ownerRequisition templates, release strategy value bands, AP exception queue
Payment diverted by a fraudulent bank changeA change request on letterhead is actioned by the same team that releases paymentSensitive-field dual authorisation and a call-back to a number already on file; vendor maintenance separated from payment releaseVendor master sensitive-field workflow and role design
Duplicate suppliers and duplicate paymentsThe same supplier exists under variant names and both records transactCreation-time de-duplication on PAN, GSTIN and bank account, plus a periodic duplicate sweep and mergeVendor master validation rules and a data-quality job
Approval bypassed after a reorganisationA new plant, purchasing group or cost centre falls outside every release characteristicCharacteristic-coverage test rerun as part of any org-structure change, with a catch-all strategy as backstopRelease strategy classification and change-control checklist
Contract rate rising without negotiationAuto-renewal or an escalation clause passes unchallengedStaged alerts before the notice window closes; escalation claims checked against the stated indexContract register dates and escalation-clause fields
Input tax credit lostSupplier has not filed, and the mismatch is found after the claim windowMonthly GSTR-2B to purchase register reconciliation with supplier-wise follow-up and payment hold where neededPurchase register extract, reconciliation report, payment block reason code
Savings claimed but never realisedThe negotiated price is agreed in a sourcing document and never becomes the buying priceAward writes the price into the contract or outline agreement that requisitions then source fromSourcing-to-contract-to-requisition price chain

An honest word on platform choice. A dedicated source-to-pay suite — SAP Ariba, Oracle Procurement Cloud, Coupa and their peers — earns its licence and integration cost when supplier collaboration itself is the workload: a large active supplier base onboarding and re-certifying continuously, frequent competitive sourcing events, punchout catalogues across many categories, and a network effect from suppliers already transacting on the same platform. Below that, the procurement module already inside your ERP plus real discipline on tolerances, catalogues and vendor master is better value, because the failures you are trying to fix are process failures that a second system will faithfully reproduce. The test is not your turnover — it is how many suppliers you actively transact with, how often you genuinely re-source a category, and whether your suppliers would log in to a portal at all. We will work through those three with you before anyone quotes licences.

How we deliver

How a procurement implementation runs without stopping the buying

Purchasing cannot pause for a project. Open orders keep receiving, invoices keep arriving, and the statutory clock on input tax credit keeps running. The sequence below is built around that constraint.

01

Spend and leakage baseline

We classify a full year of purchase transactions into categories, then measure the things that predict trouble: share of spend on no-PO invoices, share of requisition lines that are free text, invoices released without a goods receipt, and supplier count per category. This is the baseline the project is later judged against, and it is produced from your own data before any design decision is taken.

02

Vendor master cleanse and onboarding design

Duplicates are identified on PAN, GSTIN and bank account, then merged or blocked with the transaction history preserved. In parallel we design the onboarding pack, the sensitive-field workflow for bank details including the call-back step, and the role split between vendor maintenance and payment release. Nothing is loaded until the de-duplication rules are agreed.

03

Control design: tolerances, release strategies, matching rules

We sit with procurement, stores and accounts payable together and set tolerance keys per material group, define release characteristics against the delegation of authority, and decide which categories require goods-receipt-based invoice verification. The output is a control matrix signed by finance, because these are finance’s controls being configured into procurement’s system.

04

Catalogues, contracts and sourcing content

Existing contracts are loaded as outline agreements with their prices, ceilings and expiry dates, so requisitions source from them automatically. High-frequency items become catalogue entries; where suppliers support it we set up punchout. The target is stated plainly: the categories that must reach catalogue coverage first, and by when.

05

Pilot on one plant and two categories

We go live on a single plant with one indirect and one direct category, running one full cycle end to end: requisition, release, purchase order, goods receipt, invoice, match exception, payment, and one GSTR-2B reconciliation. Blocked-invoice volume on the pilot is the signal for whether tolerances are set sensibly before anyone else is switched on.

06

Cutover with open purchase orders carried over

Open purchase orders migrate with their delivered and invoiced quantities intact, or the three-way match breaks on the first part-receipt after go-live. Open goods receipts awaiting invoice, and invoices parked awaiting receipt, are both migration objects in their own right. Cutover is timed to a month end so the purchase register has a clean boundary.

07

AP exception desk and spend review handover

After go-live we work alongside accounts payable until blocked-invoice ageing, the no-PO exception report, the duplicate-vendor sweep and the GSTR-2B reconciliation run as a monthly rhythm your team owns. The quarterly spend review, with catalogue coverage and supplier fragmentation on it, is handed over as a standing agenda rather than a report we produce.

Related

Related solutions and platforms

ERP for manufacturingWhere procurement meets the bill of materials, MRP and subcontracting. ERP for distributorsThe buy side when supplier schemes and claims are a second income stream. Inventory managementGoods receipt, valuation and the stock side of the three-way match. Warehouse managementPutaway and inspection between the delivery note and the goods receipt. Enterprise solutionsWhere procurement sits inside a wider finance and operations landscape. SAP servicesSAP MM, S/4HANA sourcing and procurement, and Ariba implementation. Oracle servicesOracle Fusion Cloud Procurement, sourcing and supplier portal. Microsoft servicesDynamics 365 procurement and sourcing, and Business Central purchasing. Xtreme Industry ERPOur own ERP, with Indian GST, TDS and e-invoice handling built in. Talk to usBring a year of purchase data and your vendor master; we will show you the leaks.
Questions we get

Procurement software, answered

What is three-way matching and why does it matter more than approvals?
Three-way matching checks that the purchase order, the goods receipt and the supplier invoice agree on quantity and price before payment is released. Approvals authorise an intention to buy; only the match verifies that what was ordered actually arrived. Where matching is manual or the invoice is checked against the purchase order alone, short deliveries and quantity inflation are absorbed without anyone noticing them.
How should invoice matching tolerances be set?
Per material group and per value band, using an absolute limit alongside the percentage one. Too tight and accounts payable is buried in exceptions, ages out its queue and eventually grants blanket releases at month end, which destroys the control. Too loose and the tolerance simply defines how much you are willing to overpay. The target is a blocked-invoice volume small enough that every exception is genuinely investigated.
What is maverick spend and can a system stop it?
Maverick spend is buying that happens outside the procurement process, typically as a no-PO invoice, a card purchase or a verbal order. A system does not stop it by adding gates, because the workaround exists precisely because the official path is slow. It reduces when the compliant path is faster: catalogue items with contract pricing, low-value auto-release, and a no-PO exception report with a named owner rather than a policy reminder.
Why do approval workflows break after a reorganisation?
Because release strategies fire on document characteristics rather than on people. In SAP a strategy is matched against fields such as purchasing group, plant, material group and total value. Create a new plant or cost centre that no strategy covers and the document releases with no approval at all, silently. Any org-structure change should therefore re-run a characteristic-coverage test, with a catch-all strategy configured as a backstop.
How do we protect against supplier bank-detail fraud?
Treat bank details as a sensitive field with its own workflow: dual authorisation, and a verification call placed to a contact number already held on file rather than any number on the request. The person who maintains the vendor record must not be the person who releases payment. Requests arriving by email on convincing letterhead are the normal shape of this fraud, so the call-back is the control that matters.
Is a dedicated source-to-pay suite worth it, or is the ERP module enough?
It depends on supplier collaboration volume rather than turnover. A suite such as SAP Ariba, Oracle Procurement Cloud or Coupa earns its cost when you are continuously onboarding and re-certifying a large active supplier base, running frequent competitive sourcing events and operating punchout catalogues across categories. Below that, your ERP's own procurement module with disciplined tolerances, catalogues and vendor master control is better value and less to integrate.
Where is input tax credit actually lost on purchases?
In the gap between your purchase register and GSTR-2B. Credit depends on the supplier having filed, so an invoice you hold correctly can still be unclaimable. Reconciling the purchase register against GSTR-2B every month, supplier by supplier, surfaces the mismatch while the supplier can still be chased or the payment held. Found at year end, the same mismatch is simply a loss.
What breaks first when you migrate open purchase orders?
The three-way match. If an open purchase order arrives in the new system without its already-delivered and already-invoiced quantities, the next part-receipt matches against the full order value and the invoice passes when it should block. Open goods receipts awaiting invoice, and parked invoices awaiting receipt, are separate migration objects that are routinely forgotten and then reappear as unexplained GR/IR balances.
Can you compare quotations properly if suppliers quote different terms?
Only by normalising them first. Headline rate is not comparable across different incoterms, payment terms, packaging, minimum order quantities and validity periods. We build the comparison on landed cost with freight, duty and the financing value of payment terms brought in, and keep technical evaluation separate so technically unqualified bids are excluded before commercial envelopes are opened.

Let's build what's next — together.

Whether it's setting up your India GCC, modernizing your enterprise stack, or hiring 50 engineers in 30 days — we'd love to scope it with you.

Schedule a Call → Email Business Team