1. IT Procurement System
  2. Features
  3. Supplier records
Feature · Supplier records

Supplier records

Keep supplier identity and eligibility beside purchasing work.

OverviewSupplier directory
IT Procurement System · Supplier records

Supplier directory

Suppliers

New
NameCodeContact nameAddressEligibility noteOrganization
Supplier 401CDE-906Contact 215D-15EN-559ORG-6865
Supplier 503CDE-616Contact 373G-23EN-176ORG-5090
Supplier 766CDE-722Contact 457P-2EN-412ORG-7111
Supplier 153CDE-875Contact 162W-22EN-391ORG-4707
Supplier 667CDE-878Contact 775T-5EN-594ORG-8498
6 of 6 records
Supplier 401Suppliers · SPP-25208
CodeCDE-906
Contact nameContact 215
AddressD-15
Eligibility noteEN-559
OrganizationORG-6865
Example screen with sample data

What you can do

Supplier records in daily work

A supplier record has a name, code, contact name, address and eligibility note under an organization. The Buyer selects that party as the counterparty on a purchase request. The note gives the reviewer a place to inspect why the party was considered eligible for the request.

Supplier eligibility is recorded as a note, not a comparison of competing offers. A supplier can appear on several requests within its organization. Read the contact and eligibility note in the context of the particular request being reviewed.

How the work is organized

  • Ownership. App Administrator maintains supplier records. Buyer selects the counterparty. Purchasing Approver checks the selected supplier.
  • Record context. Use the parent request and its organization when checking a related record, then confirm the selected supplier and owner where relevant.
  • Evidence. Keep the decision, accepted quantities, attachments and operation outcomes with the same purchase context so later review has the facts in order.

What to agree during setup

Agree who maintains supplier contact changes and eligibility notes. Check that a supplier belongs to the same organization as the request before it is used. Decide how inactive supplier records should be reviewed in existing requests, so historical decisions still show the party that was selected.

Rehearse a supplier contact change on a request already approved. The App Administrator can update the supplier record while the Purchasing Approver checks the recorded decision against the request revision. Agree who confirms eligibility before a new request uses that supplier.

Check the handoff on an actual case

Open an approved request and its supplier. Check the supplier code, organization and eligibility note against the decision date. Inspect the order reference on the request after the order reference is recorded. Keep changes to supplier details separate from the request revision being reviewed.

The Purchasing Approver should read the supplier note and organization beside the request. If a supplier detail changes later, the Auditor should still be able to explain the request decision from its own dated revision and evidence.

What your team sees

  • Supplier directory — Read active suppliers with their organization and eligibility note.
  • Purchase request worklist — See requests that name a supplier as counterparty.
  • Ordered requests — Check order references recorded against selected suppliers.

Follow the work through

Read request preparation, review and order and receipt reconciliation. The data model shows how the records connect.

What it keeps track of

Data model
Suppliers
Eligible supplier parties with contact, address and eligibility evidence.
Organizations
Legal entities that own procurement records, with time zone and reporting currency.
Purchase requests
IT purchase requests with lifecycle status, owner, counterparty and requested USD amount.

Who uses it

Permissions
App Administrator
Maintains supplier records and organization membership.
Buyer
Selects the counterparty.
Purchasing Approver
Checks the selected supplier.

Set up IT Procurement System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started