Building a supplier scorecard that survives the supplier review

Five metrics that can be defended line by line, where each comes from in SAP, and the three arguments a supplier will make about your numbers.

A supplier scorecard is only worth building if it survives contact with the supplier. Most do not, because they are assembled by hand from a spreadsheet nobody can reconstruct, and the first time a vendor disputes a number the whole exercise quietly ends.

A defensible scorecard needs two properties: every figure traces back to a document in SAP, and the same calculation was run every day rather than assembled at quarter end.

Five metrics, and where each comes from

Five is enough. Scorecards with fifteen metrics do not get read, and the extra ten are usually derivable from these.

The three arguments a supplier will make

"That PO was changed after we confirmed it"

Frequently true, and it makes a confirmation look stale when the supplier did nothing wrong. Decide the rule in advance: does a quantity or date change reset the confirmation clock? Whatever you choose, write it down and apply it to everyone.

"We delivered on time, your receiving took three days to book it"

Also frequently true, and it is the reason on-time delivery should be measured against the goods receipt posting date with a stated tolerance, not against whenever the paperwork cleared. If your own GR lag is material, publish that number too. It buys more credibility than any amount of argument.

"Those lines were never expected to be confirmed"

This is the confirmation control key problem, and the supplier is right. Lines with no key set expect nothing, so they should be excluded from the denominator rather than counted as failures.

Follow-up is what generates the data

The scorecard is not a separate reporting exercise. It is the residue of having chased things properly — every follow-up sent, against which PO lines, with what value attached, timestamped.

Which is why follow-up is worth automating even if you never look at a scorecard. The drafts are transcription: the PO number, material, pending quantity, delivery date and days pending are already sitting in the exception row. Writing them into a sentence by hand is the least valuable thing in the process, and the log it leaves behind is the most.

• Group by supplier, not by line — twelve pending confirmations against one vendor is one conversation
• Keep a human approval step until the drafts have been watched for a month
• Log what was sent, to whom, when, and the value it covered

One number for the monthly review

If you present one figure per supplier, make it pending value rather than any percentage. Percentages invite argument about methodology. The rupee value of orders that supplier is currently holding up invites a conversation about what to do next, which is the conversation you wanted.