These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Supplier Portal
- Features
- Performance and evidence
Performance and evidence
Use receipt history and decision records to assess suppliers and reconcile buying activity.
OverviewPublished supplier scorecards×
SCM with Supplier Portal · Performance and evidence
New
Published supplier scorecards
Supplier performance
| Scorecard number | Period | Supplier | On time delivery pct | Quality score | Published at | |
|---|---|---|---|---|---|---|
| SP-50814 | PRD-945 | VND-223 | 86 | 25 | 15 Oct | |
| SP-34316 | PRD-367 | VND-156 | 80 | 15 | 06 Oct | |
| SP-25915 | PRD-363 | VND-169 | 99 | 20 | 08 Oct | |
| SP-34337 | PRD-856 | VND-222 | 76 | 50 | 10 Oct | |
| SP-62416 | PRD-343 | VND-082 | 98 | 30 | 08 Oct |
6 of 6 records
PRD-945Supplier performance · SP-50814
SupplierVND-223
On time delivery pct86
Quality score25
Published at15 Oct
What you can do
Performance and evidence
Supplier Performance keeps a period scorecard with on-time delivery, quality and price competitiveness results. A published scorecard identifies the supplier, reporting period, calculation date and publisher. Procurement Manager reviews the period packet before publication; Controller and Viewer can read the published position within their scope.
How the work is organized
- Publish a defined period. Keep the supplier, coverage and publisher on each scorecard.
- Explain exceptions. Trace rejected and excluded receipt lines back to the source.
- Reconcile effects. Compare approval authority, event history and allocation movements.
A scorecard should be read with its underlying order and receipt population. Receipt lines carry accepted and rejected quantities, a promise-date snapshot and any approved exclusion. This lets the team explain why a late or defective line affected the result and why a particular line was excluded. The coverage description tells readers what period and purchasing population the score represents. Other evidence answers a different question: who authorized a buying action and what effect was posted. Spend approvals hold a versioned decision and scoped allowance. Approval steps identify the tier and assigned approver. Procurement events retain source identity and revision; commitment allocations carry signed effects. Migration batches separate cutover baselines from live buying activity. Integration deliveries show whether a configured destination acknowledged a specific event.
What to agree during setup
Agree the scorecard period, quality exclusions and who can publish results. Define the control totals for historical migration. Choose which event destinations need acknowledgement and who reconciles failed deliveries. Decide which aggregate results a Viewer may read and which source records stay restricted.
Check the handoff on an actual case
Select a supplier with one on-time receipt and one rejected line. Review the promise snapshot, quality quantity and any exclusion approval before publishing the period packet. Compare the published result with the receipt evidence. Then inspect a purchase order approval and its signed allocation, and reconcile the event delivery status with the configured destination.
What your team sees
- Published supplier scorecards — Period results with delivery and quality measures.
- Open order board — Current order states used to investigate the source population.
Follow the work through
Start with the request and review path, then check the supplier delivery path. Review implementation choices with the owners before the first operating cycle.
What it keeps track of
Data model- Supplier performance
- Period scorecard per supplier: on-time delivery, quality, price competitiveness.
- Receipt line items
- Per-line received quantity against a PO line.
- Spend approvals
- Versioned authority request and frozen decision for a complete source revision.
- Approval steps
- One row per approval tier a requisition, purchase order or amendment passes through.
- Procurement events
- Durable once-only business event and migration provenance.
- Commitment allocations
- Immutable signed effects of a business event on a PO line and its funding authority.
- Migration batches
- Reviewed cutover batches for master data, authority, commitments and accepted-quantity baselines.
- Integration deliveries
- Per-event destination outbox for an explicitly configured connection.
Who uses it
Permissions- Procurement Manager
- Reviews and publishes results.
- Controller
- Reconciles authority and commitments.
- Viewer
- Reads permitted aggregate results.
- Buyer
- Explains source cases.
- Receiving Clerk
- Records the inspection that supplies quality evidence.
- Before publication, Procurement Manager checks whether an excluded line has a reason and approval, and whether the scorecard period still matches the receipts being discussed.
Set up SCM with Supplier Portal your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.