FAR 4.6—Subpart 4.6

Scope of subpart.

FAR 4.600 is a short scope provision, but it is important because it tells readers what Subpart 4.6 is for: establishing uniform reporting requirements for the Federal Procurement Data System (FPDS). In practical terms, this means the subpart is the government-wide framework for collecting and reporting procurement data in a consistent way so agencies can track contract actions, support oversight, and produce reliable acquisition statistics. The section does not itself list the data elements or reporting procedures; instead, it sets the boundary for the subpart and signals that the detailed rules in the rest of Subpart 4.6 govern how procurement information is reported into FPDS. For contracting officers and acquisition staff, the significance is that FPDS reporting is not optional or ad hoc—it is a standardized compliance requirement tied to federal procurement transparency, management, and reporting accuracy. For contractors, the practical effect is indirect but real, because the contract information they provide, confirm, or trigger may be used to populate government reporting systems. This section therefore serves as the gateway to the government’s official procurement reporting regime.

Definitions.

FAR 4.601 is a definitions section for the contract action reporting rules in Subpart 4.6. It tells users exactly what counts as a "contract action," what must be reported as a contract action report (CAR) in the Federal Procurement Data System (FPDS), and what types of transactions are excluded from that reporting framework. It also defines "definitive contract" for FPDS purposes, clarifying that the term is used only for reporting and does not control the meaning of indefinite delivery vehicles under FAR Part 16. In addition, it defines "entitlement program" and "generic entity identifier," which are important for understanding certain FPDS data elements and reporting categories. Finally, it defines "indefinite delivery vehicle (IDV)" by reference to the ordering clauses that make a contract or agreement an IDV for reporting purposes. In practice, this section matters because accurate FPDS reporting depends on using these definitions correctly; misclassifying an action can lead to bad procurement data, reporting errors, and compliance problems.

General.

FAR 4.602 explains the role of the Federal Procurement Data System (FPDS) as the governmentwide web-based system agencies use to report contract actions. It describes why FPDS exists: to generate recurring and special reports for the President, Congress, GAO, executive agencies, and the public; to measure how federal contracting affects the economy and how well small business and socio-economic programs are participating; to track sustainable acquisition and high-performance sustainable building efforts; and to assess other policy and management initiatives such as performance-based acquisition and competition. The section also clarifies what FPDS does not cover, specifically certain acquisition information used in making award decisions, such as subcontracting, funding, and accounting data. Finally, it points users to the FPDS website for submission instructions, a list of reporting entities, technical and end-user guidance, a tutorial, and information about reports that are not generated in FPDS. In practice, this section is the foundation for understanding that FPDS is a reporting and oversight tool, not a complete procurement file or financial system, and that accurate data entry matters because it drives governmentwide reporting, policy analysis, and public transparency.

Policy.

FAR 4.603 implements the government-wide transparency policy for federal award reporting. It explains that unclassified Federal award data must be publicly accessible under the Federal Funding Accountability and Transparency Act, and it directs executive agencies to use the Federal Procurement Data System (FPDS) to report all unclassified contract actions above the micro-purchase threshold, plus any later modifications that change previously reported contract action report data even if the modification itself is for a smaller dollar amount. The section also covers reporting for assisted acquisitions and direct acquisitions, including the need to identify the Program/Funding Agency and Office Codes that show which agency and office provided the predominant funding, and it ties assisted acquisitions to socioeconomic credit for the requesting agency when applicable. It further requires requesting agencies to provide the proper agency/bureau component code in the written interagency agreement. Finally, it addresses mixed-funding actions by requiring agencies to report only the full appropriated portion of a contract action in FPDS when appropriated and non-appropriated funds are combined. In practice, this section is about accurate, complete, and standardized public reporting so the government can track spending, assign credit correctly, and maintain reliable procurement data.

Responsibilities.

FAR 4.604 assigns responsibility for accurate and timely reporting of contract actions to the Federal Procurement Data System (FPDS). It covers three main areas: agency-level oversight by the Senior Procurement Executive and head of the contracting activity, the contracting officer’s responsibility for preparing, confirming, and correcting the individual Contract Action Report (CAR), and the annual agency certification of FPDS data completeness and accuracy by the chief acquisition officer. It also sets specific deadlines for completing CARs after award, including a standard three-business-day rule, a 30-day rule for certain actions under FAR 6.302-2 and subpart 18.2 authorities, and special update requirements for small business rerepresentation and SBA size protest decisions. In practice, this section is about data quality, accountability, and compliance: agencies must have a process to keep FPDS reporting current, and contracting officers must ensure the record matches the actual award and later status changes. Because FPDS data is used for oversight, reporting, and procurement analysis, errors or late entries can affect agency reporting integrity and create compliance issues.

Procedures.

FAR 4.605 sets the operating rules for how agencies and contracting officers identify and report contract actions in FPDS. It covers five main topics: procurement instrument identifiers (PIIDs), unique entity identifiers for successful offerors, use of generic entity identifiers in limited circumstances, special reporting for American Recovery and Reinvestment Act (ARRA) actions, and office codes for contracting and funding offices. The section exists to make federal procurement data accurate, traceable, and consistent governmentwide, so that each action can be uniquely tracked over time and tied to the correct contractor and offices. In practice, this means agencies must have internal controls for PIID uniqueness, contracting officers must capture the correct entity identifier from the awardee, and FPDS entries must follow specific coding rules. The limited generic-identifier exceptions are designed to protect sensitive awards or accommodate certain hard-to-identify contractors, but they do not eliminate the underlying requirement to obtain a unique entity identifier when required. The office-code rules also ensure that awards are attributed to the right contracting and funding organizations for reporting and oversight.

Reporting Data.

FAR 4.606 explains what contract and related procurement actions agencies must report to the Federal Procurement Data System (FPDS), what they may report only with approval, and what they must not report at all. It covers the minimum reporting universe for definitive contracts, purchase orders, imprest fund buys over the micro-purchase threshold, indefinite delivery vehicles (IDVs) such as task and delivery order contracts, GSA Federal Supply Schedules, blanket purchase agreements, basic ordering agreements, and all orders and calls placed under those vehicles. It also addresses reporting of Government purchase card data, the use of FPDS Express Reporting for consolidated vendor reporting, and the special approval process for reporting other actions such as micro-purchases, non-appropriated fund transactions, leases, grants, and entitlement actions. The section then lists categories excluded from FPDS reporting, including certain imprest fund and purchase card transactions, GSA stock and Global Supply orders, AbilityOne and service store purchases, non-appropriated fund activity card purchases, classified or national-security-sensitive actions, resale and concession activity, training expenditures not issued as orders or contracts, certain interagency agreements, and A-76 letters of obligation. Finally, it notes that agencies not subject to the FAR may still have reporting obligations under other authority, but they must obtain FPDS Program Office approval before reporting. In practice, this section is about data integrity and consistency: it tells agencies what must be captured in FPDS, what is optional but controlled, and what is excluded to avoid duplicate, sensitive, or non-procurement reporting.

Solicitation provisions and contract clause.

FAR 4.607 tells contracting officers when to include three specific solicitation/contract text items: the Women-Owned Business (Other Than Small Business) provision at 52.204-5, the Unique Entity Identifier provision at 52.204-6, and the Unique Entity Identifier Maintenance clause at 52.204-12. Its purpose is to ensure solicitations contain the right representations and identifier requirements based on the type of acquisition, the dollar threshold, whether the procurement is set aside for small business, where performance will occur, and whether the solicitation already includes the System for Award Management provision at 52.204-7 or otherwise meets the exception in 4.605(c)(2). In practice, this section is a placement rule: it does not create the substantive policy behind women-owned business or entity identification, but it tells the contracting officer exactly when those provisions and clauses must be inserted. For contractors, it signals when they must review and respond to women-owned business status questions and when they must provide and maintain a valid Unique Entity Identifier. For agencies and contracting officers, it is a compliance checkpoint that helps avoid defective solicitations, missing clauses, and downstream award or administration problems tied to entity registration and identification.