A structured guide to give requesters, buyers, approvers, stores and finance teams shared definitions for controlled procurement. Use it to define scope, collect evidence, test exceptions and assign accountable decisions.
Procurement Glossary should help accountable teams give requesters, buyers, approvers, stores and finance teams shared definitions for controlled procurement. It should make the required records, owners, decisions, assumptions and acceptance evidence explicit.
Use the guide as a decision framework. It does not replace qualified legal, tax, accounting, security or operational judgement where those responsibilities apply.
Test these governance risks before relying on a plan, estimate, comparison or vendor claim.
Teams compare products or start work without agreed decisions, boundaries, exclusions and acceptance criteria.
Business, finance, data and IT owners are consulted after design choices have already become expensive.
Presentation statements are treated as accepted capability, cost or readiness without representative proof.
Support, upgrades, data quality, access review, change and exit are omitted from the initial decision.
Apply the framework to the organisation's actual scope, records, responsibilities and risk.
Internal request to procure a defined good or service for an approved need. Requester, purpose, budget and required date are stated.
Controlled invitation for suppliers to quote against a common requirement. Scope, due date and communication history are retained.
Evidence-based comparison of supplier offers using approved commercial and technical criteria. Assumptions and non-price factors are visible.
Authorised commitment specifying supplier, item or service, quantity, price and terms. Changes follow approval and supplier acknowledgement.
Elapsed time between agreed procurement events such as order and receipt. The measurement boundary and calendar are defined.
Record of goods accepted, rejected or held at a receiving boundary. Quantity and condition reconcile to source documents.
Comparison of purchase order, goods receipt and supplier invoice before payment. Differences require documented resolution.
Governed assessment of supplier delivery, quality, cost and service performance. Formula, period, owner and corrective action are explicit.
Publish the business boundary, exclusions and assumptions used by the guide.
Name who prepares, reviews, approves and can change material decisions.
Retain the guidance, evidence and decision version used at each project gate.
Make material claims traceable to approved records and acceptance evidence.
Move from a clear decision through representative evidence to an approved next stage.
State the decision, sponsor, scope, exclusions and acceptance method.
Assemble representative purchase requests, approvals, supplier quotations, bid comparisons, purchase orders, receipt inspections, invoices and supplier scorecards.
Cover normal work, failure, correction, reconciliation and recovery.
Assign gaps, assumptions, dependencies, costs and risks to named owners.
Proceed only when evidence and responsibilities meet accepted criteria.
Use this matrix as a starting point and adapt it to the approved business scope.
| Area | Practical definition | Evidence to review | Control to validate |
|---|---|---|---|
| Purchase requisition | Internal request to procure a defined good or service for an approved need | Request and approval record | Requester, purpose, budget and required date are stated. |
| Request for quotation | Controlled invitation for suppliers to quote against a common requirement | RFQ issue and supplier responses | Scope, due date and communication history are retained. |
| Bid comparison | Evidence-based comparison of supplier offers using approved commercial and technical criteria | Comparison statement and source quotations | Assumptions and non-price factors are visible. |
| Purchase order | Authorised commitment specifying supplier, item or service, quantity, price and terms | Approved order and revision history | Changes follow approval and supplier acknowledgement. |
| Lead time | Elapsed time between agreed procurement events such as order and receipt | Order, promise and receipt timestamps | The measurement boundary and calendar are defined. |
| Goods receipt | Record of goods accepted, rejected or held at a receiving boundary | Receipt and inspection evidence | Quantity and condition reconcile to source documents. |
| Three-way match | Comparison of purchase order, goods receipt and supplier invoice before payment | Order, receipt and invoice records | Differences require documented resolution. |
| Supplier scorecard | Governed assessment of supplier delivery, quality, cost and service performance | Approved KPI sources | Formula, period, owner and corrective action are explicit. |
Use bounded examples and retain actual evidence, gaps and decisions.
Use representative request and approval record to test the normal case, one exception, correction and accountable approval.
Use representative rfq issue and supplier responses to test the normal case, one exception, correction and accountable approval.
Use representative comparison statement and source quotations to test the normal case, one exception, correction and accountable approval.
Use representative approved order and revision history to test the normal case, one exception, correction and accountable approval.
Use representative order, promise and receipt timestamps to test the normal case, one exception, correction and accountable approval.
Use representative receipt and inspection evidence to test the normal case, one exception, correction and accountable approval.
Use representative order, receipt and invoice records to test the normal case, one exception, correction and accountable approval.
Use representative approved kpi sources to test the normal case, one exception, correction and accountable approval.
TradeX can organise workflows and evidence. Accountable professionals still interpret requirements and approve decisions.
Record scope, volume, quality, resource and timing assumptions rather than presenting them as facts.
Mark vendor statements, planned capability and observed results as different evidence classes.
Business, finance, legal, security and operational owners approve decisions within their responsibility.
Version scope, design, cost, data and acceptance changes with impact and approval.
Do not hide gaps, rejected data or unresolved defects merely to pass a project gate.
Include support, access review, backup, upgrades, change, data export and exit from the beginning.
Every material conclusion should identify its source, owner, effective date and approval.
| Source record | Relevant context | Responsible use |
|---|---|---|
| Request and approval evidence | Need, owner, budget and authority | Confirm ownership, effective date, accepted status and approval before reliance. |
| Quotation and bid records | Supplier offer, assumptions and comparison | Confirm ownership, effective date, accepted status and approval before reliance. |
| Purchase order | Commitment, terms, revision and acknowledgement | Confirm ownership, effective date, accepted status and approval before reliance. |
| Receipt and inspection evidence | Quantity, condition, acceptance and rejection | Confirm ownership, effective date, accepted status and approval before reliance. |
| Invoice, payment and supplier performance | Match, exception, settlement and score | Confirm ownership, effective date, accepted status and approval before reliance. |
Direct answers for business, finance, operations and IT reviewers.
Procurement Glossary is a practical TradeX knowledge resource designed to give requesters, buyers, approvers, stores and finance teams shared definitions for controlled procurement. It defines the evidence, ownership and controls needed to make the topic usable in a real evaluation or implementation.
Business sponsors, finance leaders, operations heads, process owners, data owners and IT teams can use it to prepare decisions and evidence. External advisers can support the work, but accountable business owners should approve scope and acceptance.
Start with the business outcome, scope, owner and acceptance method. Identify entities, sites, processes, users, records, integrations, exclusions and the decisions that require qualified professional review.
Use representative purchase requests, approvals, supplier quotations, bid comparisons, purchase orders, receipt inspections, invoices and supplier scorecards. Preserve source references, dates, owners, status, corrections and reconciliation rather than relying only on presentation summaries.
Convert each material claim into a scripted scenario, required evidence and acceptance criterion. Record whether capability is standard, configured, add-on, custom, dependent, manual or unavailable.
Include software, hosting, implementation, migration, integration, devices, training, internal effort, support, upgrades, change and exit. Separate one-time, recurring and contingent costs using common assumptions.
Assign risk owners, due dates, mitigations and escalation. Test data quality, access, integration failure, backup restoration, cutover, fallback and vendor support before production dependence.
Use finance- and operations-approved baselines with defined formulas, periods, volumes and exclusions. Distinguish implementation effects from price, mix, seasonality and business growth.
No software can guarantee business outcomes. TradeX can support configured workflows, controls and evidence. Results depend on scope, data, ownership, adoption, integrations and ongoing management action.
Bring the approved scope and a small set of representative records, exceptions and reports. Quantbit can map a bounded workshop or demonstration with named owners, gaps and next decisions.
Use connected guidance before approving selection, implementation and lifecycle decisions.
Bring representative scope, records, exceptions and decision evidence. Quantbit will map a bounded workshop.