Previous PageTable Of ContentsNext Page


Part 504—Administrative Matters

Subpart 504.1—Contract Execution

504.101 Contracting officer’s signature.

Contract, contract modifications, blanket purchase agreements, and task and/or delivery orders may be executed manually or electronically using a digital signature. In the absence of the original contracting officer, another contracting officer with appropriate warrant authority may sign. Always type or stamp the name and title of the contracting officer signing the contract on the document, unless it is electronically signed. An electronic contract which includes the name of the contracting officer satisfies the typed, stamped or printed requirement found in FAR 4.101. GSA Order CIO 2162.1 (GSA Digital Signature Policy dated December 2, 2010) is the guidance for the use of digital signatures as the preferred means of providing signatures for GSA documents, forms, correspondence, and/or emails.

504.103 [Reserved]

Subpart 504.2—Contract Distribution

504.201 Procedures.

(a) The contracting officer must send documentation to the paying office on all contracts for which GSA generates a delivery or task order.

(b) The contracting officer must certify that the “Duplicate Original” is a true copy of the contract, modification, task and/or delivery order, if not electronically signed, by writing your signature, in ink, on the award or modification form (i.e., SF 26, 33, 1442, etc.). The contracting officer must certify all contracts except:

504.203 Taxpayer identification information.

FAR 4.203(a) does not apply to leases of real property (see 504.904) or FAR Part 38 Federal Supply Schedule Contracting.

Subpart 504.4—Safeguarding Classified Information Within Industry

504.402 General.

(a) This subpart prescribes procedures for safeguarding classified information required to be disclosed to contractors in connection with the solicitation of offers, and the award, performance, and termination of contracts.

(b) As used in this subpart, the term “Contractor(s)” means prospective contractors, subcontractors, vendors, and suppliers.

504.470 Acquisitions involving classified information.

HCA’s must consider how adequate security will be established, maintained, and monitored before accepting a reimbursable agreement for a requirement involving classified information. Further, HCAs are responsible for ensuring that the contracting officers, other procurement personnel, and contracting officer representatives (CORs) assigned to the acquisition have the appropriate security clearances, prior to accepting a reimbursable agreement involving access to, or generation of, classified information.

504.470-1 [Reserved]

504.470-2 [Reserved]

504.471 Processing security requirements checklist (DD Form 254).

(a) The contracting officer must prepare DD Form 254, Contract Security Classification Specification (illustrated in FAR 53.303-DD-254), for contracts involving contractor access to classified information. This form identifies for contractors the areas of classified information involved. The contracting officer may use written notice of classification for research or service contracts.

(b) Obtain instructions or guidance on completing DD Form 254 from the Security and Emergency Management Division, Office of Mission Assurance (OMA).

504.472 Periodic review.

(a) The contracting officer in coordination with the appropriate program security officer must review DD Form 254 at least once a year, or whenever a change in the phase of performance occurs, to determine if the classified information can be downgraded or declassified.

(b) The contracting officer must inform the contractor of the results of the review by one of the following means:

(c) The contracting officer must prepare a final checklist upon termination or completion of the contract in accordance with FAR 4.805-5.

504.473 Recurring procurement.

The contracting officer must prepare a new DD Form 254 only if a change occurs in either of the following:

(a) End item.

(b) Previous security classification.

504.474 Control of classified information.

(a) The contracting officer must record, mark, handle, and transmit classified information in accordance with the requirements of the Security Branch Chief, Security and Emergency Management Division, Office of Mission Assurance (OMA).

(b) The contracting officer must obtain the consent of the originating agency before releasing classified information to a contractor.

504.475 Return of classified information.

(a) Contracting officers must recover classified information, unless it has been destroyed as provided in Section 7 of Chapter 5 of the National Industrial Security Program Operating Manual (NISPOM). Information on NISPOM can be found at

(b) Contracting officers must ensure that classified information provided by the government is returned immediately after any of the following events:

(c) The Government agency that provided classified information to a GSA contractor is responsible for the return of the information.

504.476 Breaches of security.

GSA employees responsible for the protection of classified information must refer the facts of an unauthorized disclosure promptly to Security Branch Chief, Security and Emergency Management Division, Office of Mission Assurance (OMA).

Subpart 504.5—Electronic Commerce in Contracting

504.500 [Reserved].

504.502 Policy.

Use of electronic signatures is encouraged and can be used to sign and route documents in GSA’s IT systems to contractually obligate funds. The method of authentication used for electronic signatures shall be consistent with the level (1-4) determined from the e-authentication risk assessment in accordance with OMB M-04-04, E-authentication Guidance for Federal Agencies, and the respective technology safeguards applicable to that level or risk from National Institute of Standards and Technology 800-63, Electronic Authentication Guideline.

504.570 [Reserved].

Subpart 504.6—Contract Reporting

504.604 Responsibilities.

In accordance with FAR 4.604, the Senior Procurement Executive (SPE) has implemented the following policies to monitor and ensure the accurate and timely input of data into FPDS. Additional guidance is available on the GSA Acquisition Portal (

(a) Contract writing systems.

(b) Quarterly Reviews.

(c) Annual Reviews.

504.605 Procedures.

(a) Uniform procurement instrument identification. This subpart:

(b) Transition of procurement instrument identifier (PIID) numbering. Effective October 1, 2017, all components shall comply with the PIID numbering requirements of FAR subpart 4.16 and this subpart for all new solicitations, contracts, orders, and agreements issued, and any amendments and modifications to those new actions.

(c) Policy.

(d) Activity Address Codes (AACs).

Service/Office Code

Letter Designation

Office of the Administrator


Office of the Chief Financial Officer


Office of Human Resources Management


Office of Mission Assurance


Office of Small Business Utilization


Office of GSA IT


Civilian Board of Contract Appeals


Office of Administrative Services


Office of Inspector General


Office of General Counsel


Office of Governmentwide Policy


Public Buildings Service


Federal Acquisition Service


Congressional & Intergovernmental Affairs


Technology Transformation Service


Office of Communications and Marketing


504.605-70 Federal Procurement Data System—Public Access to Data.

(a) The FPDS database. The General Services Administration awarded a contract for creation and operation of the Federal procurement Data System (FPDS) database. That database includes information reported by departments and agencies as required by FAR subpart 4.6. One of the primary purposes of the FPDS database is to provide information on Government procurement to the public.

(b) Fee for direct hook-up. To the extent that a member of the public requests establishment of real-time integration of reporting services to run reports from another application, a one-time charge of $2,500 for the original integration must be paid by the requestor. This one-time charge covers the setup and certification required for an integrator to access the FPDS database and for technical assistance to help integrators use the web services. The fee will be paid to the FPDS contractor and credited to invoices submitted to GSA by the FPDS contractor.

504.606 Reporting Data.

(a) Reporting requirements. Detailed specification of FPDS data reporting requirements is contained in the FPDS-NG FAQs document (available at Reporting offices are encouraged to use automated information systems for FPDS data reporting, provided that the systems contain all required FPDS data elements via the machine-to-machine process and the automated acquisition system has received the proper certification from the FPDS system manager.

(b) The GSA FPDS Sustainability Coding Guidelines at must be followed when selecting codes for the following sustainability data elements:

Subpart 504.8—Government Contract Files

504.800 Scope of subpart.

This subpart prescribes a standard contract file format for all contracts that exceed the simplified acquisition threshold, except leases of real property. This subpart may be applied to purchases using simplified acquisition procedures.

504.802 Contract files.

(a) File standardization. The contracting officer must place all information and documentation required by FAR 4.802 and 4.803 in the contract file and organize the file in the standard contract file format as set out in 504.803.

(b) Responsibility for files.

(c) Transfer of responsibility for contract files.

504.803 Contents of contract files.

(a) Arrangement.

(b) Tab contents. The following instructions apply to contract actions up to award. Contracting activities may develop further guidance on tabbing postaward actions tailored to their requirements. Tab the contract file as specified below:

(c) Index.

504.804-5 Procedures for closing out contract files.

(a) HCAs are directed to take appropriate steps to ensure that physically completed contracts are formally closed in accordance with the procedures at FAR 4.804, GSAM 504.804-5, and guidelines provided below for simplified acquisitions and contracts with residual balances. HCAs are reminded that when closing out contract actions at FAR 4.804-1(a)(2), (3), and (4), the contracting officer shall use the closeout procedures at FAR 4.804-5. However, these closeout actions may be modified to reflect the extent of administration that has been performed. Contracting activities that have supplemented the FAR procedures with instructions pertinent to the specific contract types, business systems, and resources employed are encouraged to continue the use of such supplements.

(b) Contracting officers must be vigilant and proactive with respect to proper contract closeout procedures. They must not allow completed contracts to remain open indefinitely or allow a failure to conduct timely closeout to violate regulatory or statutory requirements, or negatively impact GSAs accurate and timely financial reporting.

(c) Under FAR 4.804-1(a)(1), the contracting officer only needs evidence of receipt of goods and services and final payment to closeout the contract files. For contracts awarded under the simplified acquisition procedures, contracting officers shall ensure that the contract award document and the statement of work includes the following statement:

“For payment purposes, the contractor shall mark its final invoice for payment as Final Invoice for Payment.”

(d) Cancellation of open items with residual balances.

(e) These actions by the SSO funds managers shall be considered an internal financial accounting action and shall have no bearing on the Government’s rights and duties under the contracts until the contracting officer officially closes the contract.

(f) Non-contracting officer acquisitions. For newly created open items that did not require the signature of a contracting officer (GSAM 501.603-1(f)) the funds manager has the authority to correct or cancel any open item not deemed valid. Examples of such document types include micropurchases using the governmentwide commercial purchase card, internal GSA orders and security clearances (e.g., IX, IY, GX). The funds managers should follow the financial systems procedures outlined in this memorandum for cancellation and should inform the originator of the open item of the cancellation.

504.805 Storage, handling, and disposal of contract files.

The contracting officer’s accountability for contract files ends when the following three conditions exist:

(a) The files’ retention period expires.

(b) The contracting officer receives the notice of disposal from the National Archives and Records Administration.

(c) The records liaison officer whose organization has functional responsibility for the files approves disposal.

Subpart 504.9— Taxpayer Identification Number Information

504.902 General.

(a) Debt collection. The Debt Collection Improvement Act of 1996 requires each contractor doing business with GSA to furnish its Tax Identification Number (TIN). The Government is required to include with each certified voucher prepared and submitted to a disbursing official, the TIN of the contractor receiving payment under the voucher. The TIN may be used by the Office of Financial Policy and Operations to collect and report on any delinquent amounts arising out of the contractor's relationship with the Government.

(b) Information reporting to the IRS. The TIN is also required for Office of Financial Policy and Operations reporting of certain contract information (see FAR 4.903) and payment information (see GSAM 504.904) to the IRS.

504.904 Reporting contract information to the IRS.

(a) The Office of Financial Policy and Operations reports to IRS on payments made to certain contractors for services performed and to lessors for providing space in buildings. This is required by 26 U.S.C. 6041 and 6041A and implemented in 26 CFR. To assist the Office of Financial Policy and Operations in reporting to the IRS, contracting officers must indicate on obligating documents sent to Finance (e.g., purchase, delivery, or task orders; contracts; the GSA Form R-620 for leases; or certified invoices) the contractor's organizational structure (e.g., corporation, partnership) and taxpayer identification number (TIN).

Subpart 504.11-- System for Award Management

504.1103 Procedures.

In addition to the requirements found in FAR 4.1103, prior to awarding a contractual instrument the contracting officer must--

(a) Verify that the prospective contractor’s legal business name, Doing-Business-As (DBA) name (if any), physical street address, and Data Universal Number System (DUNS) number or DUNS+4 number, as found in the System for Award Management (SAM), match the information that will be included in the contract, order, or agreement resulting from the vendor's quote or proposal. Correct any mismatches by having the vendor amend the information in the SAM and/or the quote or proposal. The SAM information can be accessed through the SAM website ( by creating a user account.

(b) Ensure that the contractor’s address code exists in Pegasys and that it is SAM enabled with the contractor’s DUNS or DUNS+4 number. This can be done by searching Pegasys records using the contractor’s Taxpayer Identification Number (TIN). If no code exists, request that a new address code be established by the Finance Center for SAM compliance.

(c) Ensure that the contractor’s identifying information is correctly placed on the contractual instrument, using special care to ensure that the legal name and “remit to” name match exactly. (Note: Lockbox names or numbers should not be used to replace the contractor’s name in the remittance block on the contractual instrument.)

(d) Unless one of the exceptions to registration in SAM applies (see FAR 4.1102(a)), the contracting officer must not award a contract to a prospective contractor who is not registered in SAM. If no exceptions are applicable, and the needs of the requiring activity allows for a delay in award, see FAR 4.1103(b)(1).

Subpart 504.13--Personal Identity Verification of Contractor Personnel

504.1301 Policy.

Contracting officers must follow the procedures contained in CIO P2181.1--GSA HSPD-12 Personal Identity Verification and Credentialing Handbook, which may be obtained from the CIO Office of Enterprise Solutions, to ensure compliance with Homeland Security Presidential Directive-12 (HSPD-12) ``Policy for a Common Identification Standard for Federal Employees and Contractors,'' Office of Management and Budget Memorandum M-05-24, and Department of Commerce FIPS PUB 201.

504.1303 Contract clause.

Insert the clause at 552.204-9, Personal Identity Verification Requirements, in solicitations and contracts when it is determined that contractor employees will require access to federally controlled facilities or information systems to perform contract requirements.

Subpart 504.16—Unique Procurement Instrument Identifiers

504.1603 Procedures.

(a) Elements of a PIID. The PIID consists of 13 alphanumeric characters as follows:



Content Description Location



Activity Address Code

See 504.605(c)



Last Two Digits of Fiscal Year of Number Assignment




Instrument Code

See 504.1603(b)



Serial Number

See 504.1603(c)


(b) Procurement Instrument Type Codes. Indicate the type of instrument consistent with the letter designation provided in FAR 4.1603(a)(3). The letter designations for the identified type of instruments unique to agency policy are identified as follows:


Letter Designation

Purchase orders (open market simplified acquisition) - manual


Request for information


Standing price quote (SPQ)


(c) Serial Number Codes.

Subpart 504.70—[Reserved]

Previous PageTop Of PageTable Of ContentsNext Page