Vendor performance tracking for public sector on Dynamics 365

Public bodies are required to buy fairly, and increasingly required to show that the suppliers they keep buying from actually perform. Contract management regimes, audit offices, and value-for-money reviews all ask the same questions: did the vendor deliver on time, was the quality right, were the invoices accurate, and was the framework used as intended? Dynamics 365 Finance and Supply Chain Management captures the transactional evidence for all four as a by-product of normal purchasing. It does not ship a vendor scorecard. This guide covers where the evidence lives, how to turn it into a score, and the process rules that apply when the score has consequences. For the competition side, see procurement transparency.

The evidence is already there

Most vendor-performance programmes fail by starting with a survey. Start with the transactions.

Delivery performance. Every purchase order line has a requested date, a confirmed date from the vendor's acknowledgement (through vendor collaboration or keyed by the buyer), and an actual receipt date from the product receipt. On-time is actual against confirmed; in-full is received quantity against ordered. Both are queries over the purchase line and receipt tables, and the only setup decision is which date counts as the promise — insist on confirmed dates, or the measure is against the buyer's wish rather than the vendor's commitment.

Quality. Where goods are inspected, quality orders at receipt record pass or fail per test, and nonconformances record what was wrong and what was done. Vendor-related nonconformances by vendor and period are the quality measure; the quality management guide covers the setup. For services, quality is a rating on the purchase order line or on a case, which brings the evaluation criteria below into play.

Invoice accuracy. Invoice matching produces price variances and quantity variances per invoice; the share of a vendor's invoices that match first time and the value of variances are the accuracy measure. Vendors that consistently invoice above the agreed price are found here, not in a survey.

Agreement compliance. Purchase agreements record committed prices and quantities; releases against them show whether the vendor honoured the framework price and whether the organisation used the framework rather than buying off-contract. Off-contract spend by category is as much a measure of the buyers as of the vendor.

Responsiveness. Time from RFQ issue to reply, and from order to acknowledgement, both timestamped when vendor collaboration is used.

Adding judgement: vendor evaluation criteria

Supply Chain Management includes vendor evaluation criteria: named criteria grouped and assigned to procurement categories, against which users rate vendors after purchases. The ratings aggregate to a vendor's score per category and are visible on the vendor and in the RFQ comparison. It is a lightweight mechanism — a small set of criteria, a star scale, comments — and that is its virtue. Use it for the things transactions cannot measure: communication, problem resolution, professionalism on site.

Two rules make it defensible in a public body: ratings are entered against a specific purchase or contract, not free-floating, and the raters are the people who received the goods or service, not procurement. A rating without a transaction behind it is an opinion, and opinions are what a supplier challenge will attack.

Certifications and compliance

Public bodies must confirm vendors hold required certifications — insurance, safety, data protection, professional accreditation — and that they remain current. Vendor certifications on the vendor record hold the certification type, number, and expiry, with alerts as expiry approaches; the alerts and notifications guide describes the alert mechanism. Policy can prevent orders to vendors whose mandatory certification has lapsed, either by putting the vendor on hold or through a workflow check. Debarment and exclusion lists maintained by governments are external; checking them is a step in vendor onboarding and periodic review, typically a Power Automate flow calling the list's service where one exists, and a manual check where it does not.

The scorecard

With the evidence in place, the scorecard is a Power BI model over purchase lines, receipts, quality orders, invoice matching, agreements, evaluation ratings, and certifications, keyed on vendor and procurement category. Weight the measures per category — delivery matters more for goods, ratings more for services — and publish a score per vendor per quarter. The Power BI for Dynamics 365 guide covers the data path; Synapse Link or the data lake export is the right source for this volume. Keep the weighting simple and documented, because the vendor will ask for it.

Consider also giving vendors sight of their own score through vendor collaboration or a Power Pages page. Supplier-relationship programmes that share the score get fewer challenges and better performance than ones that spring it at contract review.

Consequences, and the process around them

This is where public sector differs from private. A private company can quietly stop buying from a vendor. A public body that excludes a vendor from a framework, declines to renew, or scores it down in a competition on the basis of past performance must follow a fair process: the vendor must have known the criteria, been told of poor performance, and had the chance to improve. The system supports this with the vendor hold status and its reason codes, the documented ratings and their dates, and correspondence stored against the vendor — but the process is the contract manager's, and the score should feed a conversation before it feeds a decision.

Using past performance in a new competition is regulated in most jurisdictions and permitted only where announced in the procurement documents. The RFQ scoring criteria can include it; whether they may is a legal question to settle before the criteria are published.

Business Central bodies

Business Central records receipts, invoice variances, and vendor blocked status, and has no evaluation criteria or certification tracking. Smaller public bodies build the delivery and invoice-accuracy measures in Power BI from BC's purchase and receipt data, hold certifications as attributes or a small custom table with expiry, and record service ratings in a Dataverse or SharePoint list. That is enough for a body with a few hundred vendors; it is the argument for Supply Chain Management for one with thousands.

Start small

Delivery on-time and invoice first-time-match for the top fifty vendors by spend, reviewed quarterly with the contract managers. Add quality and ratings once those two numbers are trusted. Vendor-performance programmes that launch with a twelve-measure scorecard and a survey to every supplier produce a report nobody reads and a set of scores nobody will defend.