↑↓ move · ⏎ open · esc close
Requisition · Source · Receive · Reconcile
// Solutions · Procurement & Supply Chain
Procurement fails quietly: a requisition approved by email, a PO raised after the goods arrived, an invoice paid without anyone confirming delivery. This connects requisition, sourcing, ordering, receipt and inventory so each step references the last one and the trail closes.
// The chain
That single rule is what closes the loop. A purchase order cannot exist without an approved requisition behind it, and an invoice cannot be released without both a PO and a receipt to match against.
Requires
A budget line
Adds
Specification, quantity, justification, cost centre
Requires
An approved requisition
Adds
Shortlist, responses side by side, award reasoning
Requires
An awarded RFQ
Adds
Agreed price, terms, delivery date, amendment history
Requires
An open PO line
Adds
Quantity received, condition, rejections, stock update
Requires
A matched PO + GRN
Adds
Payment release — or an exception nobody can quietly clear
// What you get
Each document is created from the one before it, so retrospective purchase orders and unmatched invoices stop being possible rather than merely discouraged.
Requests raised with specification, budget line and justification, then routed through the authority matrix before any commitment is made to a supplier.
Quotation requests issued to a shortlist, responses captured side by side, and the award decision recorded with its reasoning for later scrutiny.
Orders raised from approved requisitions with agreed pricing and terms, amendments version-controlled, and delivery dates tracked against promise.
Receipts booked against the order with quantity and condition recorded, feeding straight into stock so inventory reflects reality rather than intent.
Invoice, order and receipt matched automatically within tolerance, with anything outside it queued for a human rather than paid on trust.
On-time delivery, quality rejections, price movement and responsiveness tracked per supplier — so renewal conversations start from evidence.
// The scorecard
On-time delivery, rejection rate, price movement and responsiveness accumulate from the documents themselves. Nobody has to compile it, which is why it still exists when the contract comes up.
Vendor performance · trailing 12 months
| Supplier | On time | Rejected | Price Δ | Response |
|---|---|---|---|---|
| Supplier A | 96% | 0.4% | +1.2% | Same day |
| Supplier B | 81% | 2.1% | +6.8% | 2–3 days |
| Supplier C | 64% | 5.7% | +11.4% | 5+ days |
| Supplier D | 92% | 0.9% | −0.4% | Same day |
Illustrative scorecard · example figures, not client data
// How we get there
We usually start where the leakage is worst — most often uncontrolled spend before the PO, or invoices paid without a receipt.
Follow recent purchases end to end and find where the trail breaks — verbal orders, retrospective POs, receipts nobody booked.
Agree categories, authority limits, tolerance thresholds, supplier master data and the documents each step must produce.
Configure requisition, RFQ, PO, receipt and matching flows, migrate the supplier and item masters, and pilot with one category.
Roll out to remaining categories and sites, switch on vendor scoring once there is enough history, and tune tolerances.
// FAQ
With an explicit emergency path rather than a bypass. Defined roles can commit up to a stated limit outside the normal chain, but the request is flagged, the justification is captured and it is reported afterwards — so exceptions stay visible and countable instead of becoming the norm.
Yes. Tender pursuits carry their own approval ladder, document set and submission deadlines, and the sourcing records are kept in the audit-ready form public-sector scrutiny expects. Sector-specific requirements are confirmed against your own procurement rules during design.
No. Each solution is a configured slice of the same platform, so you can start with one department and add another later without a migration or a second integration to maintain. What you do get from the start is one data fabric underneath — so when the second solution arrives it already recognises your people, approvals and records.
Yes. Most engagements leave existing line-of-business systems in place and integrate with them through APIs, scheduled syncs or event feeds. Where an existing system is genuinely the blocker we will say so, and that becomes an Application Modernization conversation rather than something we quietly work around.
// Get started
That number is usually the business case. We can help you establish it in a short review before committing to anything larger.
// Pairs well with
Chat with us on WhatsApp
Pick the team you need — we'll open the chat.
Ask Teky Bot
AI-assisted · replies may contain mistakes
Please don't share passwords or personal data. AI processes your messages. See our Privacy Policy.
We set no cookies of our own and run no trackers — just two on-device preferences (theme, this notice). The Google Map on our Contact page can set Google's. Details in our Cookie Policy and Privacy Policy.
