Previous Next

Subpart 4.6—Contract Reporting

4.600  Scope of subpart.

This subpart prescribes uniform reporting requirements for the Federal Procurement Data System (FPDS).

4.601  Definitions.

As used in this subpart—

“Contract action” means any oral or written action that results in the purchase, rent, or lease of supplies or equipment, services, or construction using appropriated dollars over the micro-purchase threshold, or modifications to these actions regardless of dollar value. Contract action does not include grants, cooperative agreements, other transactions, real property leases, requisitions from Federal stock, training authorizations, or other non-FAR based transactions.

“Contract action report (CAR)” means contract action data required to be entered into the Federal Procurement Data System (FPDS).

“Definitive contract” means any contract that must be reported to FPDS other than an indefinite delivery vehicle. This definition is only for FPDS, and is not intended to apply to Part 16.

“Entitlement program” means a Federal program that guarantees a certain level of benefits to persons or other entities who meet requirements set by law, such as Social Security, farm price supports, or unemployment benefits.

“Generic DUNS number” means a DUNS number assigned to a category of vendors not specific to any individual or entity.

“Indefinite delivery vehicle (IDV)” means an indefinite delivery contract or agreement that has one or more of the following clauses:

(1) 52.216-18, Ordering.

(2) 52.216-19, Order Limitations.

(3) 52.216-20, Definite Quantity.

(4) 52.216-21, Requirements.

(5) 52.216-22, Indefinite Quantity.

(6) Any other clause allowing ordering.

4.602  General.

(a) The FPDS provides a comprehensive web-based tool for agencies to report contract actions. The resulting data provides—

(1) A basis for recurring and special reports to the President, the Congress, the Government Accountability Office, Federal executive agencies, and the general public;

(2) A means of measuring and assessing the effect of Federal contracting on the Nation’s economy and the extent to which small, veteran-owned small, service-disabled veteran-owned small, HUBZone small, small disadvantaged, women-owned small business concerns, and AbilityOne nonprofit agencies operating under the Javits-Wagner-O’Day Act, are sharing in Federal contracts; and

(3) A means of measuring and assessing the effect of other policy and management initiatives (e.g., performance based acquisitions and competition).

(b) FPDS does not provide reports for certain acquisition information used in the award of a contract action (e.g., subcontracting data, funding data, or accounting data).

(c) The FPDS Web site,, provides instructions for submitting data. It also provides—

(1) A complete list of departments, agencies, and other entities that submit data to the FPDS;

(2) Technical and end-user guidance;

(3) A computer-based tutorial; and

(4) Information concerning reports not generated in FPDS.

4.603  Policy.

(a) In accordance with the Federal Funding Accountability and Transparency Act of 2006 (Pub. L. No. 109-282), all Federal award data must be publicly accessible.

(b) Executive agencies shall use FPDS to maintain publicly available information about all contract actions exceeding the micro-purchase threshold, and any modifications to those actions that change previously reported contract action report data, regardless of dollar value.

(c) Agencies awarding assisted acquisitions or direct acquisitions must report these actions and identify the Funding Agency Code from the applicable agency codes maintained by the National Institute of Standards and Technology (NIST) using NIST Special Publication 800-87, “Codes for the Identification of Federal and Federally Assisted Organizations,” at

(d) Agencies exempt from the FAR are encouraged to report contract actions in FPDS.

(e) Agencies awarding contract actions with a mix of appropriated and nonappropriated funding shall only report the full appropriated portion of the contract action in FPDS.

4.604  Responsibilities.

(a) The Senior Procurement Executive in coordination with the head of the contracting activity is responsible for developing and monitoring a process to ensure timely and accurate reporting of contractual actions to FPDS.

(b)(1) The responsibility for the submission and accuracy of the individual contract action report (CAR) resides with the contracting officer who awarded the contract action.

(2) When a contract writing system is integrated with FPDS, the CAR must be confirmed for accuracy prior to release of the contract award.

(3) When a contract writing system is not integrated with FPDS, the CAR must be submitted to FPDS within three business days after contract award.

(4) For any action awarded in accordance with FAR 6.302-2 or pursuant to any of the authorities listed at FAR Subpart 18.2, the CAR must be submitted to FPDS within 30 days after contract award.

(5) When the contracting office receives written notification that a contractor has changed its size status in accordance with the clause at 52.219-28, Post-Award Small Business Program Rerepresentation, the contracting officer must submit a modification contract action report to ensure that the updated size status is entered in FPDS-NG.

(c) The chief acquisition officer of each agency required to report its contract actions must submit to the General Services Administration (GSA), in accordance with FPDS guidance, by January 5, an annual certification of whether, and to what degree, agency CAR data for the preceding fiscal year is complete and accurate.

4.605  Procedures.

(a) Procurement Instrument Identifier (PIID). Agencies must have in place a process that ensures that each PIID reported to FPDS is unique, Governmentwide, and will remain so for at least 20 years from the date of contract award. Agencies must submit their proposed identifier format to the FPDS Program Management Office, which maintains a registry of the agency unique identifiers on the FPDS website, and must validate their use in all transactions. The PIID shall consist of alpha characters in the first positions to indicate the agency, followed by alphanumeric characters identifying bureaus, offices, or other administrative subdivisions. Other pertinent PIID instructions can be found at

(b) Data Universal Numbering System (DUNS). The contracting officer must identify and report a DUNS number (Contractor Identification Number) for the successful offeror on a contract action. The DUNS number reported must identify the successful offeror’s name and address as stated in the offer and resultant contract, and as registered in the Central Contractor Registration (CCR) database in accordance with the clause at 52.204-7, Central Contractor Registration. The contracting officer must ask the offeror to provide its DUNS number by using either the provision at 52.204-6, Data Universal Numbering System (DUNS) Number, the clause at 52.204-7, Central Contractor Registration, or the provision at 52.212-1, Instructions to Offerors—Commercial Items.

(1) Notwithstanding the inclusion of the provision at 52.204-6 in the associated solicitation or except as provided in paragraph (b)(2) of this section, the contracting officer shall use one of the generic DUNS numbers identified in CCR to report corresponding contract actions if the contract action is—

(i) With contractors located outside the United States and its outlying areas as defined in 2.101 who do not have a DUNS number, and the contracting officer determines it is impractical to obtain a DUNS number;

(ii) With students who do not have DUNS numbers;

(iii) With dependents of veterans, Foreign Service Officers, and military members assigned overseas who do not have DUNS numbers; or

(iv) For classified or national security.

(2) In accordance with agency procedures, authorized generic DUNS numbers found at may be used to report contract actions when—

(i) Specific public identification of the contracted party could endanger the mission, contractor, or recipients of the acquired goods or services; or

(ii) The agency determines it is impractical to obtain a DUNS number.

(c) The contracting officer, when entering data in FPDS, shall use the instructions at to identify any action funded in whole or in part by the American Recovery and Reinvestment Act of 2009 (Pub. L. 111-5).

4.606  Reporting Data.

(a) Actions required to be reported to FPDS.

(1) As a minimum, agencies must report the following contract actions over the micro-purchase threshold, regardless of solicitation process used, and agencies must report any modification to these contract actions that change previously reported contract action data, regardless of dollar value:

(i) Definitive contracts, including purchase orders and imprest fund buys over the micro-purchase threshold awarded by a contracting officer.

(ii) Indefinite delivery vehicle (identified as an “IDV” in FPDS). Examples of IDVs include the following:

(A) Task and Delivery Order Contracts (see Subpart 16.5), including—

(1) Government-wide acquisition contracts.

(2) Multi-agency contracts.

(B) GSA Federal supply schedules.

(C) Blanket Purchase Agreements (see 13.303).

(D) Basic Ordering Agreements (see 16.703).

(E) Any other agreement or contract against which individual orders or purchases may be placed.

(iii) All calls and orders awarded under the indefinite delivery vehicles identified in paragraph (a)(1)(ii) of this section.

(2) The GSA Office of Charge Card Management will provide the Government purchase card data, at a minimum annually, and GSA will incorporate that data into FPDS for reports.

(3) Agencies may use the FPDS Express Reporting capability for consolidated multiple action reports for a vendor when it would be overly burdensome to report each action individually. When used, Express Reporting should be done at least monthly.

(b) Reporting Other Actions. Agencies may submit actions other than those listed at paragraph (a)(1) of this section, and must contact the FPDS Program Office at if they desire to submit any of the following types of activity:

(1) Transactions at or below the micro-purchase threshold, except as provided in paragraph (a)(2) of this section.

(2) Any non-appropriated fund (NAF) or NAF portion of a contract action using a mix of appropriated and nonappropriated funding.

(3) Lease and supplemental lease agreements for real property.

(4) Resale activity (i.e., commissary or exchange activity).

(5) Revenue generating arrangements (i.e., concessions).

(6) Training expenditures not issued as orders or contracts.

(7) Grants and entitlement actions.

(8) Interagency agreements, also known as interservice level agreements, memoranda of understanding, or memoranda of agreement.

(9) Letters of obligation used in the A-76 process.

(c) Actions not reported. The following types of contract actions are not to be reported to FPDS:

(1) Imprest fund transactions below the micro-purchase threshold, including those made via the Government purchase card (unless specific agency procedures prescribe reporting these actions).

(2) Orders from GSA stock and the GSA Global Supply Program.

(3) Purchases made at GSA or AbilityOne service stores, as these items stocked for resale have already been reported by GSA.

(4) Purchases made using non-appropriated fund activity cards, chaplain fund cards, individual Government personnel training orders, and Defense Printing orders.

(5) Actions that, pursuant to other authority, will not be entered in FPDS (e.g., reporting of the information would compromise national security).

(d) Agencies not subject to the FAR may be required by other authority (e.g., statute or OMB) to report certain information to FPDS.

4.607  Solicitation Provisions.

(a) Insert the provision at 52.204-6, Data Universal Numbering System (DUNS) Number, in solicitations that—

(1) Are expected to result in a requirement for the generation of a CAR (see 4.606(a)(1)); and

(2) Do not contain the clause at 52.204-7, Central Contractor Registration.

(b) Insert the provision at 52.204-5, Women-Owned Business (Other Than Small Business), in all solicitations that—

(1) Are not set aside for small business concerns;

(2) Exceed the simplified acquisition threshold; and

(3) Are for contracts that will be performed in the United States or its outlying areas.

Previous Next