Procurement transparency for public sector on Dynamics 365 Finance

Public procurement has one requirement commercial procurement does not: it must be seen to be fair. Thresholds decide which procedure applies, competing bids must be evaluated against published criteria, the decision must be documented, and the spend must be reportable — to auditors, to elected members, and under freedom-of-information regimes to anyone who asks. Dynamics 365 Finance and Supply Chain Management provides the workflow, policy, and audit machinery; the tendering portal and the statutory notices remain outside it. This guide walks the procurement cycle from a transparency standpoint. For fund accounting, budget control, and encumbrance, see public sector features.

Policies encode the rules

Purchasing policies are the mechanism for turning procurement regulations into system behaviour. Policy rules are assigned to organisation hierarchies — a legal entity, a department, a fund — and cover:

• Requisition control: who may raise requisitions, for which categories, and whether a catalogue item is required.
• Purchase order creation and consolidation: whether requisitions become orders automatically or wait for a buyer.
• RFQ requirements: the rule that requisitions above a threshold amount must go through a request for quotation before an order can be raised. This is the rule that implements "three quotes above this value" and "formal tender above that value".
• Purchase agreement application: lines must draw down from an existing framework agreement where one exists for the category.
• Category access: which procurement categories each part of the organisation may buy from.

Set the thresholds to match the regulation, tie them to the organisation hierarchy that mirrors delegated authority, and review them when the regulation changes. The policy is the documented control; auditors can read it directly.

Requisition to approval

Purchase requisitions with workflow are the entry point for controlled spend. The workflow routes by amount, category, and organisation — through a line manager, a budget holder, and above a threshold a procurement officer — with the purchase requisitions and approvals guide covering the configuration. Budget control checks the fund at submission and reserves it as a pre-encumbrance, so that a requisition cannot proceed against an exhausted budget; the budget control guide covers the mechanics.

The transparency value is the workflow history: who approved what, when, with what comment, held on the requisition and reportable. A requisition approved outside the system — an email chain and a manually raised order — has no such history, and the policy should make that path impossible rather than merely discouraged.

Requests for quotation and scored bids

For competitive procedures, the request for quotation (RFQ) is the in-product mechanism. An RFQ is issued to selected vendors or opened for response, vendors reply with prices and delivery, and the replies are compared. Two features carry the fairness burden:

• Vendor collaboration lets vendors see the RFQ and submit their bid through the portal, with a timestamp, rather than by email to a buyer. The vendor collaboration guide covers the setup. Sealed-bid behaviour — nobody sees replies until the deadline — is a process control on top of it, not a lock in the product.
• Scoring criteria on the RFQ let evaluators rate each bid against weighted criteria — price, quality, delivery, sustainability — with the scores recorded per evaluator and per reply. The award recommendation is then a documented calculation, not a buyer's preference. Configure the criteria before the RFQ is issued; adding them afterwards is exactly what a losing bidder's challenge will point to.

The RFQ, replies, scores, and award create a complete record of the competition. What the RFQ does not do is publish the notice in the official journal, run a full e-tendering procedure with clarifications and standstill periods, or handle the structured questionnaires that formal tenders require. Public bodies use their jurisdiction's e-tendering platform for that, and the F&O RFQ either mirrors the result or is skipped for formal tenders, with the award recorded directly as a purchase agreement.

Framework agreements

Public bodies buy most routine goods and services under frameworks. Purchase agreements model them: a vendor, a validity period, committed quantities or values by category or item, prices, and release orders drawn against them. Policy can require that lines in a category use the framework, and consumption against the agreement is visible, which is what a compliance review checks first. The sales and purchase agreements guide covers the mechanics.

The audit trail

Every document in the cycle carries its workflow history, its change history where database logging is enabled, and its posting trail. For public bodies the additional habits are enabling the database log on vendor bank details and vendor master changes (the classic fraud vector), keeping document attachments — the specification, the evaluation report, the conflict-of-interest declarations — on the RFQ or agreement rather than in a shared drive, and retaining procurement records for the statutory period. Financial reporting and Power BI over the purchasing tables give auditors and members the spend by vendor, category, and procedure.

Publishing spend

Many jurisdictions require publication of spend above a threshold, contracts awarded, and supplier lists. The data is in F&O; the publication is a scheduled export. Azure Synapse Link or the data lake export feeds a reporting layer from which the open-data file or the transparency report is produced with the required fields and redactions; the data lake export guide covers the plumbing. Do not build the transparency report as a direct query against production.

Where Business Central fits

Smaller public bodies — parish and town councils, arm's-length bodies, schools trusts — run Business Central, which has purchase quotes, approval workflows by amount, and dimensions for fund and cost centre, but no purchasing policies, no RFQ with scoring, and lighter budget control. It is adequate where the procurement regulation is simple and the formal tenders run on the national portal anyway. The transparency burden is then met by the approval workflow history and a spend export, and the bid evaluation record lives with the portal.

The gap to name early

The product provides the controlled process and the evidence. It does not know the regulation — the thresholds, the standstill periods, the publication obligations — and the implementation must encode them in policy, workflow, and procedure. Procurement teams should own that configuration alongside finance, because the first time a threshold changes and the policy does not, the audit finding will be theirs.