FAR 4.605—Procedures.
Plain-English Summary
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.
Key Rules
PIIDs must be unique
Agencies must maintain a process that ensures every PIID reported to FPDS is unique governmentwide for solicitations, contracts, BPAs, basic agreements, BOAs, and orders. The PIID must remain unique for at least 20 years from the date of contract award.
Report the successful offeror’s identifier
The contracting officer must identify and report a unique entity identifier for the successful offeror on a contract action. That identifier must match the offeror’s name and address in the offer and resulting contract, and the SAM registration record.
Use the right solicitation provision
The contracting officer must ask the offeror for its unique entity identifier using the applicable solicitation provision: 52.204-6, 52.204-7, or 52.212-1, depending on the procurement. This ties the award record to the offeror’s registered identity.
Generic identifiers are limited exceptions
Generic entity identifiers may be used only in the specific situations listed in paragraph (c)(2). They do not replace the requirement for the contractor to have a unique entity identifier when the solicitation requires one.
Sensitive awards need a written file note
If specific public identification of the contractor could endanger the mission, contractor, or recipients, the contracting officer may use a generic identifier, but must place a written determination in the contract file supporting that decision.
ARRA actions must be flagged in FPDS
When entering data in FPDS, the contracting officer must follow FPDS instructions to identify any action funded in whole or in part by the American Recovery and Reinvestment Act of 2009.
Use AAC-based office codes
By March 31, 2016, agencies must use the Activity Address Code of the issuing contracting office as the contracting office code and the AAC of the funding office providing the predominance of funding as the program/funding office code.
Responsibilities
Agency
Establish and maintain a process that ensures PIIDs reported to FPDS are unique governmentwide and remain unique for at least 20 years. Also ensure office codes are assigned using the required AAC-based method.
Contracting Officer
Report the correct unique entity identifier for the successful offeror, obtain that identifier through the applicable solicitation provision, apply FPDS instructions for ARRA-funded actions, and document any decision to use a generic entity identifier under the mission-protection exception.
Offeror/Contractor
Provide a unique entity identifier when required by the solicitation and ensure the identifier corresponds to the name and address used in the offer and contract, as reflected in SAM registration.
FPDS/Data Entry Personnel
Enter procurement data in accordance with FPDS instructions, including PIIDs, entity identifiers, ARRA flags, and office codes, and ensure the reported data matches the underlying award record.
Integrated Award Environment (IAE) Program Office
Maintain the authorized generic entity identifiers that may be used in the limited circumstances allowed by FAR 4.605(c)(2).
Practical Implications
PIID management is a long-term data integrity issue, not just a clerical one; agencies need controls to prevent duplicate identifiers across the government and across many years of records.
Contracting officers should verify that the awardee’s identifier, legal name, and address all line up with SAM and the contract file before reporting the action, because mismatches can create FPDS errors and audit issues.
Generic entity identifiers are narrow exceptions, so they should not be used as a convenience when a real identifier can be obtained; if used for sensitive awards, the file must clearly justify the decision.
Office-code reporting affects workload, funding attribution, and oversight reporting, so agencies should confirm the correct AAC for both the issuing office and the predominant funding office before submission.
ARRA reporting is a special data element that must be captured exactly as FPDS requires; missing or incorrect flags can distort transparency reporting and historical records.
Official Regulatory Text
(a) Procurement Instrument Identifier (PIID) . Agencies shall have in place a process that ensures that each PIID reported to FPDS is unique Governmentwide, for all solicitations, contracts, blanket purchase agreements, basic agreements, basic ordering agreements, or orders in accordance with 4.1601 to 4.1603 , and will remain so for at least 20 years from the date of contract award. Other pertinent PIID instructions for FPDS reporting can be found at https://www.fpds.gov . (b) Unique entity identifier . The contracting officer shall identify and report a unique entity identifier for the successful offeror on a contract action. The unique entity identifier shall correspond to the successful offeror's name and address as stated in the offer and resultant contract, and as registered in the System for Award Management in accordance with the provision at 52.204-7 , System for Award Management. The contracting officer shall ask the offeror to provide its unique entity identifier by using either the provision at 52.204-6 , Unique Entity Identifier, the provision at 52.204-7 , System for Award Management, or the provision at 52.212-1 , Instructions to Offerors-Commercial Products and Commercial Services. (For a discussion of the Commercial and Government Entity (CAGE) Code, which is a different identifier, see subpart 4.18 .) (c) Generic entity identifier. (1) The use of a generic entity identifier should be limited, and only used in the situations described in paragraph (c)(2) of this section. Use of a generic entity identifier does not supersede the requirements of provisions 52.204-6 , Unique Entity Identifier or 52.204-7 System for Award Management (if present in the solicitation) for the contractor to have a unique entity identifier assigned. (2) Authorized generic entity identifiers, maintained by the Integrated Award Environment (IAE) program office ( http://www.gsa.gov/portal/content/105036 ), may be used to report contracts in lieu of the contractor's actual unique entity identifier only for— (i) Contract actions valued at or below $40,000 that are awarded to a contractor that is- (A) A student; (B) A dependent of either a veteran, foreign service officer, or military member assigned outside the United States and its outlying areas (as defined in 2.101 ); or (C) Located outside the United States and its outlying areas for work to be performed outside the United States and its outlying areas and the contractor does not otherwise have a unique entity identifier; (ii) Contracts valued above $30,000 awarded to individuals located outside the United States and its outlying areas for work to be performed outside the United States and its outlying areas; or (iii) Contracts when specific public identification of the contracted party could endanger the mission, contractor, or recipients of the acquired goods or services. The contracting officer must include a written determination in the contract file of a decision applicable to authority under this paragraph (c)(2)(iii). (d) American Recovery and Reinvestment Act actions. The contracting officer, when entering data in FPDS, shall use the instructions at https://www.fpds.gov to identify any action funded in whole or in part by the American Recovery and Reinvestment Act of 2009 (Pub. L. 111-5). (e) Office codes . Agencies shall by March 31, 2016— (1) Use the Activity Address Code (AAC), as defined in 2.101 , assigned to the issuing contracting office as the contracting office code, and (2) Use the AAC assigned to the program/funding office providing the predominance of funding for the contract action as the program/funding office code.