Procurement

Procurement Records for Federally Funded Purchases

Organize a procurement file around the documented procedures, decision evidence, contractor oversight, and conflict checks relevant to a federally funded purchase.

By Remizen Editorial · · 3 min read

This guide helps organize records for a purchase under a covered U.S. federal award. The Uniform Guidance applies to covered awards, subject to the award terms and recipient circumstances; the organization must also consider applicable state, local, and tribal requirements and the purchase rules relevant to its situation. Section 200.318(a) requires recipients and subrecipients to maintain and use documented procurement procedures consistent with those laws and the standards in sections 200.317–200.327. The file below is a practical way to show how the organization followed its own applicable procedure; it does not invent a universal threshold or replace those detailed requirements.

Open a file before the purchase decision

Identify the requester, need, estimated scope, funding source, and person responsible for the procurement. Link the transaction to the organization’s current written procedures and determine which competition, approval, or other process those procedures call for. Record the need and the basis for the selected approach before a commitment is made. Section 200.318(d) says procedures must avoid unnecessary or duplicative items; the file can preserve the need statement and any appropriate comparison or consolidation consideration. Do not assume a familiar vendor or an available budget line alone explains why the purchase was selected.

Preserve selection and relationship evidence

Keep the solicitation or request, offers received, evaluation notes, selection rationale, approvals, and communications relevant to the decision when they are part of the applicable process. Record who participated and the criteria used so a later reviewer can reconstruct how the result followed the documented procedures. Section 200.318(c) requires written standards of conduct addressing conflicts for employees involved in contract selection, award, and administration, and restricts participation by people with a real or apparent conflict. Retain any declarations, recusals, reviews, or other conflict-handling evidence the organization’s standards require. Keep the executed contract or purchase order, amendments, and key specifications with the selection record.

Worked example: selecting a data-collection service

A project team requests a data-collection service for an award activity. The file begins with the need, scope, award connection, and procedure the organization determined applies. The buyer retains the vendor responses and evaluation notes, including how the selected offer met the documented requirements. A team member discloses a relationship with one vendor; the procurement lead follows the organization’s written conflict procedure, records the member’s recusal, and ensures the evaluation is completed by authorized reviewers. The purchase order identifies the deliverables and dates. During performance, the project owner records delivery and any issue against the specifications. The file demonstrates the organization’s process without claiming the same selection method fits every purchase.

Document performance and exceptions

Section 200.318(b) requires oversight to ensure contractors perform according to contract or purchase-order terms, conditions, and specifications. Preserve proportionate evidence of delivery review, acceptance, problems raised, corrective follow-up, and invoice approval. If competition or a required record is missing, do not backdate or reconstruct an unsupported decision as though it happened contemporaneously. Escalate the gap to procurement and grants staff, document what evidence is actually available, and follow the organization’s process for deciding whether further action is needed. Consult sections 200.319–200.327 and award conditions for requirements beyond the general standards in section 200.318.

Procurement file checklist

  • Link the need and funding to the applicable written procurement procedure.
  • Retain the decision, review, approval, and selection evidence the process calls for.
  • Document conflict review and any required recusal or resolution.
  • Keep the contract, purchase order, amendments, delivery review, and invoice support.
  • Escalate missing records or unclear requirements; never invent a threshold or backdate evidence.

Sources and further reading

  • Procurement Approval Workflows

    A procurement approval workflow routes a proposed purchase to the people who need to assess its business case, budget, supplier, and risk before commitment. Learn how to design clear, proportionate review steps.

  • What Is Procurement?

    Procurement is the organized process an organization uses to identify needs, evaluate suppliers, obtain goods and services, and manage the commitments that follow. This guide explains its stages and how finance teams contribute.

  • Purchase Orders vs Employee Expenses

    A purchase order documents an approved supplier purchase before fulfillment; an employee expense documents a business cost after it is incurred. This comparison shows how to classify transactions and keep the records connected.

  • Financial Controls for Employee Spending

    Learn how practical controls can prevent, detect, and resolve issues in employee spending while keeping legitimate purchases workable. The guide covers authority, documentation, review, access, and ongoing monitoring.