# PART 4

# ADMINISTRATIVE MATTERS

### 4.000 Scope of part.

This part prescribes policies and procedures relating to the administrative aspects of contract execution, contractor-submitted paper documents, distribution, reporting, retention, and files.

## SUBPART 4.1--CONTRACT EXECUTION

### 4.101 Contracting officer's signature.

Only contracting officers shall sign contracts on behalf of the United States. The contracting officer's name and official title shall be typed, stamped, or printed on the contract. The contracting officer normally signs the contract after it has been signed by the contractor. The contracting officer shall ensure that the signer(s) have authority to bind the contractor (see specific requirements in 4.102 of this subpart).

### 4.102 Contractor's signature.

(a) Individuals. A contract with an individual shall be signed by that individual. A contract with an individual doing business as a firm shall be signed by that individual, and the signature shall be followed by the individual's typed, stamped, or printed name and the words, "an individual doing business as . . . . . . . . . ."[insert name of firm].

(b) Partnerships. A contract with a partnership shall be signed in the partnership name. Before signing for the Government, the contracting officer shall obtain a list of all partners and ensure that the individual(s) signing for the partnership have authority to bind the partnership.

(c) Corporations. A contract with a corporation shall be signed in the corporate name, followed by the word "by" and the signature and title of the person authorized to sign. The contracting officer shall ensure that the person signing for the corporation has authority to bind the corporation.

(d) Joint venturers. A contract with joint venturers may involve any combination of individuals, partnerships, or corporations. The contract shall be signed by each participant in the joint venture in the manner prescribed in paragraphs (a) through (c) above for each type of participant.
When a corporation is participating, the contracting officer shall obtain from the corporation secretary a certificate stating that the corporation is authorized to participate in the joint venture.

(e) Agents. When an agent is to sign the contract, other than as stated in paragraphs (a) through (d) above, the agent's authorization to bind the principal must be established by evidence satisfactory to the contracting officer.

### 4.103 Contract clause.

The contracting officer shall insert the clause at 52.204-1, Approval of Contract, in solicitations and contracts if required by agency procedures.

## SUBPART 4.2--CONTRACT DISTRIBUTION

### 4.201 Procedures.

Contracting officers shall distribute copies of contracts or modifications within 10 working days after execution by all parties. As a minimum, the contracting officer shall--
(a) Distribute simultaneously one signed copy or reproduction of the signed contract to the contractor and the paying office;

(b) When a contract is assigned to another office for contract administration (see Subpart 42.2), provide to that office--

(1) One copy or reproduction of the signed contract and of each modification; and

(2) A copy of the contract distribution list, showing those offices that should receive copies of modifications, and any changes to the list as they occur;

(c) Distribute one copy to each accounting and finance office (funding office) whose funds are cited in the contract;

(d) When the contract is not assigned for administration but contains a Cost Accounting Standards clause, provide one copy of the contract to the cognizant administrative contracting officer and mark the copy "FOR COST ACCOUNTING STANDARDS ADMINISTRATION ONLY" (see 30.601(b));

(e) Provide one copy of each contract or modification that requires audit service to the appropriate field audit office listed in the "Directory of Federal Contract Audit Offices" (copies of this directory can be ordered from the U.S. Government Printing Office, Superintendent of Documents, Washington, DC 20402, referencing stock
numbers 008-007-03189-9 and 008-007-03190-2 for Volumes I and II, respectively); and

(f) Provide copies of contracts and modifications to those organizations required to perform contract administration support functions (e.g., when manufacturing is performed at multiple sites, the contract administration office cognizant of each location).

### 4.202 Agency distribution requirements.

Agencies shall limit additional distribution requirements to the minimum necessary for proper performance of essential functions. When contracts are assigned for administration to a contract administration office located in an agency different from that of the contracting office (see Part 42), the two agencies shall agree on any necessary distribution in addition to that prescribed in 4.201 above.

### 4.203 Taxpayer identification number information.

(a) If the contractor has furnished a taxpayer identification number (TIN) when completing the solicitation provision at 52.204-3, Taxpayer Identification, the contracting officer shall, unless otherwise provided in agency procedures, attach a copy of the completed solicitation provision as the last page of the copy of the contract sent to the paying office.

(b) If the TIN or corporate status is derived from a source other than the provision at 52.204-3, the last page of the contract forwarded to the paying office will be annotated to state the contractor's TIN and corporate status.

## SUBPART 4.3--PAPER DOCUMENTS

### 4.300 Scope of subpart.

This subpart provides policies and procedures on contractor-submitted paper documents.

### 4.301 Authority.

The authority for this subpart is established in Executive Order 12873, Sections 402(d) and 504, October 20, 1993.

### 4.302 Definition.

"Printing/copying double-sided," as used in this subpart, means printing or reproducing a document so that information is on both sides of a sheet of paper.

### 4.303 Policy.

It is the policy of the Government that a contractor submitting paper documents to the Government relating to an acquisition should, if possible, submit those documents printed/copied double-sided on recycled paper. If the contractor can only print/copy double-sided or use recycled paper, the contractor should accomplish whichever one the contractor has the ability to achieve.

### 4.304 Contract clause.

The contracting officer shall insert the clause at 52.204-4, Printing/Copying Double-Sided on Recycled Paper, in solicitations and contracts greater than the simplified acquisition threshold.

## SUBPART 4.4--SAFEGUARDING CLASSIFIED INFORMATION WITHIN INDUSTRY

### 4.401 Definitions.

"Classified acquisition" means an acquisition that consists of one or more contracts in which offerors would be required to have access to classified information (Confidential, Secret, or Top Secret) to properly submit an offer or quotation, to understand the performance requirements of a classified contract under the acquisition, or to perform the contract.

"Classified contract" means any contract that requires, or will require, access to classified information (Confidential, Secret, or Top Secret) by the contractor or its employees in the performance of the contract. A contract may be a classified contract even though the contract document is not classified.

"Classified information" means any information or material, regardless of its physical form or characteristics, that is owned by, produced by or for, or under the control of the United States Government, and determined pursuant to Executive Order 12356, April 2, 1982 (47 FR 14874, April 6, 1982) or prior orders to require protection against unauthorized disclosure, and is so designated.

### 4.402 General.

(a) Executive Order 10865, February 20, 1960 (25 FR
1583, February 25, 1960), entitled "Safeguarding Classified Information Within Industry," as amended by Executive Order 10909, January 17, 1961 (26 FR 508, January 20, 1961), forms the basis for agency regulations concerning safeguarding the release of classified information to U.S. industry.

(b) The Department of Defense (DOD) has incorporated the requirements of these Executive Orders into the Defense Industrial Security Program (DISP), administered by the Defense Investigative Service, 1900 Half Street SW, Washington, DC 20324, (Director for Industrial Security). The following DOD publications implement the program:

(1) Industrial Security Regulation (ISR) (DOD 5220.22-R).

(2) Industrial Security Manual for Safeguarding Classified Information (ISM) (DOD 5220.22-M).

(c) Procedures for the protection of information relating to foreign classified contracts awarded to U.S. industry, and instructions for the protection of U.S. information relating to classified contracts awarded to foreign firms, are prescribed in Section VIII of the ISR.

(d) Part 27, Patents, Data, and Copyrights, contains
policy and procedures for safeguarding classified information in patent applications and patents.

### 4.403 Responsibilities of contracting officers.

(a) Presolicitation phase. Contracting officers shall review all proposed solicitations to determine whether access to classified information may be required by offerors, or by a contractor during contract performance.

(1) If access to classified information of another agency may be required, the contracting officer shall--

(i) Determine if the agency is covered by the DISP; and

(ii) Follow that agency's procedures for determining the security clearances of firms to be solicited.

(2) If the classified information required is from the contracting officer's agency, the contracting officer shall follow agency procedures.

(b) Solicitation phase. Contracting officers shall--

(1) Ensure that the classified acquisition is conducted as required by the DISP or agency procedures, as appropriate; and

(2) Include (i) an appropriate Security Requirements clause in the solicitation (see 4.404), and (ii) as appropriate, in solicitations and contracts when the contract may require access to classified information, a requirement for security safeguards in addition to those provided in the clause (52.204-2, Security Requirements).

(c) Award phase. Contracting officers shall inform contractors and subcontractors of the security classifications and requirements assigned to the various documents, materials, tasks, subcontracts, and components of the classified contract as follows:

(1) Agencies covered by the DISP shall use the Contract Security Classification Specification, DD Form 254. The contracting officer, or authorized representative, is the approving official for the form and shall ensure that it is prepared and distributed in accordance with Section VII of the ISR.

(2) Contracting officers in agencies not covered by the DISP shall follow agency procedures.

### 4.404 Contract clause.

(a) The contracting officer shall insert the clause at 52.204-2, Security Requirements, in solicitations and contracts when the contract may require access to classified information, unless the conditions specified in paragraph (d) below apply.

(b) If a cost contract (see 16.302) for research and development with an educational institution is contem-
plated, the contracting officer shall use the clause with its Alternate I.

(c) If a construction or architect-engineer contract where employee identification is required for security reasons is contemplated, the contracting officer shall use the clause with its Alternate II.

(d) If the contracting agency is not covered by the DISP and has prescribed a clause and alternates that are substantially the same as those at 52.204-2, the contracting officer shall use the agency-prescribed clause as required by agency procedures.

## SUBPART 4.5--ELECTRONIC COMMERCE IN CONTRACTING

### 4.500 Scope of subpart.

This subpart provides policy and procedures for the establishment and use of the Federal Acquisition Computer Network (FACNET) as required by Section 30 of the Office of Federal Procurement Policy (OFPP) Act (41 U.S.C. 426).

### 4.501 Definitions.

"ANSI X.12" means the designation assigned by the American National Standards Institute (ANSI) for the structure, format, and content of electronic business transactions conducted through Electronic Data Interchange (EDI). ANSI is the coordinator and clearinghouse for national standards in the United States.

"Electronic commerce (EC)" means a paperless process including electronic mail, electronic bulletin boards, electronic funds transfer, electronic data interchange, and similar techniques for accomplishing business transactions. The use of terms commonly associated with paper transactions (e.g., "copy", "document", "page", "printed", "sealed envelope" and "stamped") shall not be interpreted to restrict the use of electronic commerce.

"Electronic data interchange (EDI)" means a technique for electronically transferring and storing formatted information between computers utilizing established and published formats and codes, as authorized by the applicable Federal Information Processing Standards.

"Federal Acquisition Computer Network (FACNET)" means the Governmentwide Electronic Commerce/

Electronic Data Interchange (EC/EDI) systems architecture for the acquisition of supplies and services that provides for electronic data interchange of acquisition information between the Government and the private sector, employs nationally and internationally recognized data formats, and provides universal user access.

"Full FACNET" means an agency has certified that it has implemented all of the FACNET functions outlined in 4.504, and more than 75 percent of eligible contracts (not otherwise exempted from FACNET) in amounts exceeding the micro-purchase threshold, but not exceeding the simplified acquisition threshold (see Part 13), were entered into by the agency during the preceding fiscal year using FACNET.

"Governmentwide FACNET" means that the Federal Government has certified its FACNET capability, and more than 75 percent of eligible contracts (not otherwise exempted from FACNET) in amounts exceeding the micro-purchase threshold, but not exceeding the simplified acquisition threshold (see Part 13), entered into by the executive agencies during the preceding fiscal year were made through full FACNET.

"Interim FACNET" means a contracting office has been certified as having implemented a capability to provide widespread public notice of, issue solicitations, and receive responses to solicitations and associated requests for information through FACNET. Such capability must allow the private sector to access notices of solicitations, access and review solicitations, and respond to solicitations.

"Transaction Set" means the data that is exchanged to convey meaning between Trading Partners engaged in EC/EDI.

"Value-Added Network (VAN)" means an entity that provides communications services, electronic mailboxing and other communications services for EDI transmissions.

"Value-Added Service (VAS)" means an entity that provides services beyond communications to its customers. These services may range from translation and segregation of the data to complete turn-key business systems support for customers.

### 4.502 Policy.

(a) The Federal Government shall use FACNET whenever practicable or cost effective.

(b) FACNET is the preferred method of soliciting and receiving quotes and providing notice of Government purchase requirements exceeding the micro-purchase threshold and not exceeding the simplified acquisition threshold (see13.103(b)).

(c) Contracting officers may use FACNET for any contract action governed by the FAR, unless specifically exempted (see 4.506 and 13.106-1(a)(2)).

(d) Before using FACNET, or any other method of electronic data interchange, the agency head shall ensure that the electronic data interchange system is capable of ensuring authentication and confidentiality commensurate with the risk and magnitude of the harm from loss, misuse, or unauthorized access to or modification of the information.

### 4.503 Contractor registration.

(a) In order for a contractor to conduct electronic commerce with the Federal Government, the contractor must provide registration information to the Central Contractor Registration.

(b) The contractor will be required to submit information in accordance with the Federal implementation conventions of the ASC ANSI X.12 transaction set for contractor registration.

### 4.504 FACNET functions.

(a) FACNET will permit agencies to do the following electronically--

(1) Provide widespread public notice of contracting opportunities, and issue solicitations;

(2) Receive responses to solicitations and associated requests for information;

(3) Provide widespread public notice of contract awards and issuance of orders (including price);

(4) Receive questions regarding solicitations, if practicable;

(5) Issue contracts and orders, if practicable;

(6) Initiate payments to contractors, if practicable; and

(7) Archive data relating to each procurement action.

(b) FACNET will permit the private sector to do the following electronically--

(1) Access notices of solicitations;

(2) Access and review solicitations;

(3) Respond to solicitations;

(4) Receive contracts and orders, if practicable;

(5) Access information on contract awards and issuance of orders; and

(6) Receive payment by purchase card, electronic funds transfer, or other automated means, if practicable.

### 4.505 FACNET certification.

#### 4.505-1 Interim certification.

(a) A contracting office is considered to have implemented interim FACNET if--

(1) The contracting office--

(i) Has implemented the FACNET functions described in 4.504(a)(1) and (2), and (b)(1), (2), and (3); and

(ii) Issues notices of solicitations and receives responses to solicitations in a system having those functions;

(2) The contracting office can use FACNET for contracts, not otherwise exempted (see 4.506), that exceed the micro-purchase threshold but do not exceed the simplified acquisition threshold; and

(3) The senior procurement executive of the agency, or the Under Secretary of Defense for Acquisition and Technology for the military departments and defense agencies, has certified to the Administrator of OFPP that the contracting office has implemented interim FACNET.

(b) The senior procurement executive of the agency, or the Under Secretary of Defense for Acquisition and Technology for the military departments and defense agencies, shall notify the private sector via the Commerce Business Daily that a contracting office of the agency has certified interim FACNET. The notice shall establish a date after which it will be required that all responses to solicitations issued by the contracting office through FACNET, must be submitted through FACNET, unless otherwise authorized.

#### 4.505-2 Full certification.

(a) An agency is considered to have implemented full FACNET if--

(1) The agency has implemented all of the FACNET functions described in 4.504;

(2) During the entire preceding fiscal year, more than 75 percent of the agency's eligible contracts, not otherwise exempted (see 4.506), that exceeded the micro-purchase threshold but did not exceed the simplified acquisition threshold, were entered into via FACNET; and

(3) The head of the agency, with the concurrence of the Administrator of OFPP, has certified to the Congress that the agency has implemented full FACNET. For the Department of Defense, the certification shall be made by the Secretary of Defense for the Department as a whole.

(b) Eligible contracts do not include any class or classes of contracts that the Federal Acquisition Regulatory Council determines, after October 13, 1997, are not suitable for acquisition through FACNET.

#### 4.505-3 Governmentwide certification.

The Federal Government is considered to have implemented Governmentwide FACNET if--

(a) During the preceding fiscal year, at least 75 percent of eligible contracts entered into by executive agencies, that exceeded the micro-purchase threshold but did not exceed the simplified acquisition threshold, were made via full FACNET; and

(b) The Administrator of OFPP has certified implementation of Governmentwide FACNET to the Congress.

#### 4.505-4 Contract actions excluded.

For purposes of calculating the percentage of FACNET use referred to in 4.505-2 and 4.505-3, actions issued against established contracts, such as delivery orders, task orders, and in-scope modifications, shall not be included.

### 4.506 Exemptions.

The following are exempted from the use of FACNET as specified and shall not be considered when determining compliance with the requirements to implement FACNET:

(a) Interim FACNET. (1) Classes of procurements exempted by the head of the contracting activity after a written determination is made that FACNET processing of those procurements is not cost-effective or practicable; and specific purchases for which the contracting officer determines that it is not practicable or cost-effective to process via FACNET. Such determinations shall be centrally maintained at the contracting office.

(2) Contracts that do not require notice under Subpart 5.2.

(b) Full FACNET. Contracts awarded by a contracting office (or a portion of a contracting office), if the office is exempted from use of FACNET by the head of the agency, or the Secretary of Defense for the military departments and defense agencies. Any such exemption shall be based on a written determination that FACNET processing is not cost-effective or practicable for the contracting office, or portions thereof. Determinations shall be maintained in the office of the senior procurement executive, or the Under Secretary of Defense for Acquisition and Technology for the military departments and defense agencies.

### 4.507 Contract actions using simplified acquisition procedures.

Contracting officers shall refer to section 13.106 for evaluation and documentation requirements when awarding contracts using simplified acquisition procedures.

## 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 Record requirements.

(a) Each executive agency shall establish and maintain for a period of 5 years a computer file, by fiscal year, containing unclassified records of all procurements exceeding $25,000.

(b) With respect to each procurement carried out using competitive procedures, agencies shall be able to access from the computer file, as a minimum, the following information:

(1) The date of contract award.

(2) Information identifying the source to whom the contract was awarded.

(3) The property or services obtained by the Government under the procurement.

(4) The total cost of the procurement.

(5) Those procurements which result in the submission of a single bid or proposal so that they can be separately categorized and designated noncompetitive procurements using competitive procedures.

(c) In addition to paragraph (b) of this section with respect to each procurement carried out using procedures other than competitive procedures, agencies shall be able to access from the computer file--

(1) The reason under Subpart 6.3 for the use of such procedures; and

(2) The identity of the organization or activity which conducted the procurement.

(d) In addition to the information described in paragraphs (b) and (c) of this section, for procurements in excess of $25,000, agencies shall be able to access information on the following from the computer file:

(1) Awards to small disadvantaged businesses using either set-asides or full and open competition.

(2) Awards to business concerns owned and controlled by women.

(3) The number of offers received in response to a solicitation.

(4) Task or delivery order contracts.

(5) Contracts for the acquisition of commercial items.

(e) This information shall be transmitted to the Federal Procurement Data System in accordance with agency procedures.

### 4.602 Federal Procurement Data System.

(a) The FPDS provides a comprehensive mechanism for assembling, organizing, and presenting contract placement data for the Federal Government. Federal agencies report data to the Federal Procurement Data Center (FPDC), which collects, processes, and disseminates official statistical data on Federal contracting. The data provide (1) a basis for recurring and special reports to the President, the Congress, the General Accounting Office, Federal executive agencies, and the general public; (2) a means of measuring and assessing the impact of Federal contracting on the Nation's economy and the extent to which small, small disadvantaged and women-owned small business concerns are sharing in Federal contracts; and (3) data for other policy and management control purposes.

(b) The FPDS Reporting Manual provides a complete list of reporting and nonreporting agencies and organizations. This manual (available at no charge from the General Services Administration, Federal Procurement Data Center, 7th & D Streets, SW, Room 5652, Washington, DC 20407, telephone (202) 401-1529, FTS 441-1529, FAX (202) 401-1546) provides the necessary instruction to the data collection point in each agency as to what data are required and how often to provide the data.

(c) Data collection points in each agency report data on SF 279, Federal Procurement Data System (FPDS)-- Individual Contract Action Report, and SF 281, Federal Procurement Data System (FPDS)--Summary Contract Action Report ($25,000 or Less), or computer-generated equivalent. Although the SF 279 and SF 281 are not mandatory for use by the agencies, they do provide the mandatory format for submitting data to the FPDS.

(d) The contracting officer shall obtain and report a Contractor Establishment Code for each awardee from information on file or available to the contracting office. The contracting office or other designated agency office shall request a code using the procedures in the FPDS Reporting Manual or in accordance with agency procedures. Requests for codes shall be made by Government offices and only for the apparent awardees.

### 4.603 Solicitation provision.

The contracting officer shall insert the provision at 52.204-5, Women-Owned Business, in all solicitations that are not set aside for small business concerns and that exceed the simplified acquisition threshold in Part 13, when the contract is to be performed inside the United States, its territories or possessions, Puerto Rico, the Trust Territory of the Pacific Islands, or the District of Columbia.

## SUBPART 4.7--CONTRACTOR RECORDS RETENTION

### 4.700 Scope of subpart.

This subpart provides policies and procedures for retention of records by contractors to meet the records review requirements of the Government. In this subpart, the terms "contracts" and "contractors'' include "subcontracts" and "subcontractors."

### 4.701 Purpose.

The purpose of this subpart is to generally describe records retention requirements and to allow reductions in the retention period for specific classes of records under prescribed circumstances.

### 4.702 Applicability.

(a) This subpart applies to records generated under contracts that contain one of the following clauses:

(1) Audit and Records--Sealed Bidding (52.214-26).

(2) Audit and Records--Negotiation (52.215-2).

(3) Audit--Commercial Items (52.215-43).

(b) This subpart is not mandatory on Department of Energy contracts for which the Comptroller General allows alternative records retention periods. Apart from this exception, this subpart applies to record retention periods under contracts that are subject to Chapter 137, Title 10, U.S.C., and the Federal Property and Administrative Services Act of 1949, as amended, 40 U.S.C. 471, et seq.

### 4.703 Policy.

(a) Except as stated in 4.703(b), contractors shall make available records, which includes books, documents, accounting procedures and practices, and other data, regardless of type and regardless of whether such items are in written form, in the form of computer data, or in any other form, and other supporting evidence to satisfy contract negotiation, administration, and audit requirements of the contracting agencies and the Comptroller General for (1) 3 years after final payment or, for certain records, (2) the period specified in 4.705 through 4.705-3, whichever of these periods expires first.

(b) Contractors shall make available the foregoing records and supporting evidence for a longer period of time than is required in 4.703(a) if--

(1) A retention period longer than that cited in 4.703(a) is specified in any contract clause; or

(2) The contractor, for its own purposes, retains the foregoing records and supporting evidence for a
longer period. Under this circumstance, the retention period shall be the period of the contractor's retention or 3 years after final payment, whichever period expires first.

(3) The contractor does not meet the original 90-day due date for submission of final indirect cost rate proposals specified in subparagraph (d)(2) of the clause at

52.216-7, Allowable Cost and Payment, and subpara-
graph (c)(2) of the clause at 52.216-13, Allowable Cost
and Payment--Facilities. Under these circumstances, the retention periods in 4.705 shall be automatically extended one day for each day the proposal is not submitted after the original 90-day due date.

(c) Nothing in this section shall be construed to preclude a contractor from duplicating or storing original records in electronic form unless they contain significant information not shown on the record copy. Original records need not be maintained or produced in an audit if the contractor or subcontractor provides photographic or electronic images of the original records and meets the following requirements:

(1) The contractor or subcontractor has established procedures to ensure that the imaging process preserves accurate images of the original records, including signatures and other written or graphic images, and that the imaging process is reliable and secure so as to maintain the integrity of the records.

(2) The contractor or subcontractor maintains an effective indexing system to permit timely and convenient access to the imaged records.

(3) The contractor or subcontractor retains the original records for a minimum of one year after imaging to permit periodic validation of the imaging systems.

(d) If the information described in paragraph (a) of this section is maintained on a computer, contractors shall retain the computer data on a reliable medium for the time periods prescribed. Contractors may transfer computer data in machine readable form from one reliable computer medium to another. Contractors' computer data retention and transfer procedures shall maintain the integrity, reliability, and security of the original computer data. Contractors shall also retain an audit trail describing the data transfer. For the record retention time periods prescribed, contractors shall not destroy, discard, delete, or write over such computer data.

### 4.704 Calculation of retention periods.

(a) The retention periods in 4.705 are calculated from the end of the contractor's fiscal year in which an entry is made charging or allocating a cost to a Government con-
tract or subcontract. If a specific record contains a series of entries, the retention period is calculated from the end of the contractor's fiscal year in which the final entry is made. The contractor should cut off the records in annual blocks and retain them for block disposal under the prescribed retention periods.

(b) When records generated during a prior contract are relied upon by a contractor for cost or pricing data in negotiating a succeeding contract, the prescribed periods shall run from the date of the succeeding contract.

(c) If two or more of the record categories described in 4.705 are interfiled and screening for disposal is not practical, the contractor shall retain the entire record series for the longest period prescribed for any category of records.

### 4.705 Specific retention periods.

The contractor shall retain the records identified in 4.705-1 through 4.705-3 for the periods designated, provided retention is required under 4.702. Records are identified in this subpart in terms of their purpose or use and not by specific name or form number. Although the descriptive identifications may not conform to normal contractor usage or filing practices, these identifications applyto all contractor records that come within the description.

#### 4.705-1 Financial and cost accounting records.

(a) Accounts receivable invoices, adjustments to the accounts, invoice registers, carrier freight bills, ship-
ping orders, and other documents which detail the
material or services billed on the related invoices: Retain 4 years.

(b) Material, work order, or service order files, consist-
ing of purchase requisitions or purchase orders for material
or services, or orders for transfer of material or supplies: Retain 4 years.

(c) Cash advance recapitulations, prepared as posting entries to accounts receivable ledgers for amounts of expense vouchers prepared for employees' travel and related expenses: Retain 4 years.

(d) Paid, canceled, and voided checks, other than those issued for the payment of salary and wages: Retain 4 years.

(e) Accounts payable records to support disbursements of funds for materials, equipment, supplies, and services, containing originals or copies of the following and related documents: remittance advices and statements, vendors' invoices, invoice audits and distribution slips, receiving and inspection reports or comparable certifications of receipt and inspection of material or services, and debit and credit memoranda: Retain 4 years.

(f) Labor cost distribution cards or equivalent documents: Retain 2 years.

(g) Petty cash records showing description of expenditures, to whom paid, name of person authorizing payment, and date, including copies of vouchers and other supporting documents: Retain 2 years.

#### 4.705-2 Pay administration records.

(a) Payroll sheets, registers, or their equivalent, of salaries and wages paid to individual employees for each payroll period; change slips; and tax withholding statements: Retain 4 years.

(b) Clock cards or other time and attendance cards: Retain 2 years.

(c) Paid checks, receipts for wages paid in cash, or other

evidence of payments for services rendered by employees: Retain 2 years.

#### 4.705-3 Acquisition and supply records.

(a) Store requisitions for materials, supplies, equipment, and services: Retain 2 years.

(b) Work orders for maintenance and other services: Retain 4 years.

(c) Equipment records, consisting of equipment usage and status reports and equipment repair orders: Retain 4 years.

(d) Expendable property records, reflecting accountability for the receipt and use of material in the per-
formance of a contract: Retain 4 years.

(e) Receiving and inspection report records, consisting of reports reflecting receipt and inspection of supplies, equipment, and materials: Retain 4 years.

(f) Purchase order files for supplies, equipment, material, or services used in the performance of a contract; supporting documentation and backup files including, but not limited to, invoices, and memoranda; e.g., memoranda of negotiations showing the principal elements of subcontract price negotiations (see 52.244-1 and 52.244-2): Retain 4 years.

(g) Production records of quality control, reliability, and inspection: Retain 4 years.

### 4.706 [Reserved]

## SUBPART 4.8--GOVERNMENT CONTRACT FILES

### 4.800 Scope of subpart.

This subpart prescribes requirements for establishing, maintaining, and disposing of contract files for all contractual actions. The application of this subpart to contracts awarded using the simplified acquisition procedures covered by Part 13 is optional. (See also documentation requirements in 13.106-2).

### 4.801 General.

(a) The head of each office performing contracting, contract administration, or paying functions shall establish files containing the records of all contractual actions.

(b) The documentation in the files (see 4.803) shall be sufficient to constitute a complete history of the transaction for the purpose of--

(1) Providing a complete background as a basis for informed decisions at each step in the acquisition process;

(2) Supporting actions taken;

(3) Providing information for reviews and investigations; and

(4) Furnishing essential facts in the event of litigation or congressional inquiries.

(c) The files to be established include--

(1) A file for cancelled solicitations;

(2) A file for each contract; and

(3) A file such as a contractor general file, containing documents relating--for example--to (i) no specific contract, (ii) more than one contract, or (iii) the contractor in a general way (e.g., contractor's management systems, past performance, or capabilities).

### 4.802 Contract files.

(a) A contract file should generally consist of--

(1) The contracting office contract file, which shall document the basis for the acquisition and the award, the assignment of contract administration (including payment responsibilities), and any subsequent actions taken by the contracting office;

(2) The contract administration office contract file, which shall document actions reflecting the basis for and the performance of contract administration responsibilities; and

(3) The paying office contract file, which shall document actions prerequisite to, substantiating, and reflecting contract payments.

(b) Normally, each file should be kept separately; however, if appropriate, any or all of the files may be combined; e.g., if all functions or any combination of the functions are performed by the same office.

(c) Files shall be maintained at organizational levels that shall ensure--

(1) Effective documentation of contract actions;

(2) Ready accessibility to principal users;

(3) Minimal establishment of duplicate and working files;

(4) The safeguarding of classified documents; and

(5) Conformance with agency regulations for file location and maintenance.

(d) If the contract files or file segments are decentralized (e.g., by type or function) to various organizational elements or to other outside offices, responsibility for their maintenance shall be assigned. A central control and, if
needed, a locator system should be established to ensure the ability to locate promptly any contract files.

(e) Contents of contract files that are proprietary or source selection information as defined in 3.104-4 shall be protected from disclosure to unauthorized persons (see 3.104-5).

(f) Agencies may retain contract files in any medium (paper, electronic, microfilm, etc.) or any combination of media, as long as the requirements of this subpart are satisfied.

### 4.803 Contents of contract files.

The following are examples of the records normally contained, if applicable, in contract files:

(a) Contracting office contract file. (1) Purchase request, acquisition planning information, and other presolicitation documents.

(2) Justifications and approvals, determinations and findings, and associated documents.

(3) Evidence of availability of funds.

(4) Synopsis of proposed acquisition as published in the Commerce Business Daily or reference thereto. (5) The list of sources solicited, and a list of any firms or persons whose requests for copies of the solicitation were denied, together with the reasons for denial.

(6) Set-aside decision.

(7) Government estimate of contract price.

(8) A copy of the solicitation and all amendments thereto.

(9) Security requirements and evidence of required clearances.

(10) A copy of each offer or quotation, the related abstract, and records of determinations concerning late offers or quotations. Unsuccessful offers or quotations may be maintained separately, if cross-referenced to the contract file. The only portions of the unsuccessful offer or quotation that need be retained are--

(i) Completed solicitation sections A, B, and K;

(ii) Technical and management proposals; (iii) Cost/price proposals; and

(iv) Any other pages of the solicitation that the offeror or quoter has altered or annotated.

(11) Contractor's contingent fee representation and other certifications and representations.

(12) Preaward survey reports or reference to previous
preaward survey reports relied upon.

(13) Source selection documentation.

(14) Contracting officer's determination of the contractor's responsibility.

(15) Small Business Administration Certificate of Competency.

(16) Records of contractor's compliance with labor policies including equal employment opportunity policies.

(17) Cost or pricing data and Certificates of Current Cost or Pricing Data or a required justification for waiver, or information other than cost or pricing data.

(18) Packaging and transportation data.

(19) Cost or price analysis.

(20) Audit reports or reasons for waiver.

(21) Record of negotiation.

(22) Justification for type of contract.

(23) Authority for deviations from this regulation, statutory requirements, or other restrictions.

(24) Required approvals of award and evidence of legal review.

(25) Notice of award.

(26) The original of (i) the signed contract or award, (ii) all contract modifications, and (iii) documents supporting modifications executed by the contracting office.

(27) Synopsis of award or reference thereto.

(28) Notice to unsuccessful quoters or offerors and record of any debriefing.

(29) Acquisition management reports (see Subpart 4.6).

(30) Bid, performance, payment, or other bond documents, or a reference thereto, and notices to sureties.

(31) Report of postaward conference.

(32) Notice to proceed, stop orders, and any overtime premium approvals granted at the time of award.

(33) Documents requesting and authorizing modification in the normal assignment of contract administration functions and responsibility.

(34) Approvals or disapprovals of requests for waivers or deviations from contract requirements.

(35) Rejected engineering change proposals. These proposals may be filed separately for early disposal (see 4.805(h)).

(36) Royalty, invention, and copyright reports (including invention disclosures) or reference thereto.

(37) Contract completion documents.

(38) Documentation regarding termination actions for which the contracting office is responsible.

(39) Cross-references to pertinent documents that are filed elsewhere.

(40) Any additional documents on which action was taken or that reflect actions by the contracting office pertinent to the contract.

(41) A current chronological list identifying the awarding and successor contracting officers, with inclusive dates of responsibility.

(42) All certifications required by 3.104-9(e)(1).

(43) For contracts and contract modifications in excess of $100,000, a record of all persons or classes of persons authorized to have access to proprietary or source selection information and, to the maximum extent practicable, the names of all individuals within the class.

(b) Contract administration office contract file. (1) Copy of the contract and all modifications, together with official record copies of supporting documents executed by the contract administration office.

(2) Any document modifying the normal assignment of contract administration functions and responsibility.

(3) Security requirements.

(4) Cost or pricing data, Certificates of Current Cost or Pricing Data, or information other than cost or pricing data; cost or price analysis; and other documentation supporting contractual actions executed by the contract administration office.

(5) Preaward survey information.

(6) Purchasing system information.

(7) Consent to subcontract or purchase.

(8) Performance and payment bonds and surety information.

(9) Postaward conference records.

(10) Orders issued under the contract.

(11) Notice to proceed and stop orders.

(12) Insurance policies or certificates of insurance or references to them.

(13) Documents supporting advance or progress payments.

(14) Progressing, expediting, and production surveillance records.

(15) Quality assurance records.

(16) Property administration records.

(17) Documentation regarding termination actions for which the contract administration office is responsible.

(18) Cross reference to other pertinent documents that are filed elsewhere.

(19) Any additional documents on which action was
taken or that reflect actions by the contract administration office pertinent to the contract.

(20) Contract completion documents.

(c) Paying office contract file. (1) Copy of the contract and any modifications.

(2) Bills, invoices, vouchers, and supporting documents.

(3) Record of payments or receipts.

(4) Other pertinent documents.

### 4.804 Closeout of contract files.

#### 4.804-1 Closeout by the office administering the
contract.

(a) Except as provided in paragraph (c) below, time standards for closing out contract files are as follows:

(1) Files for contracts using simplified acquisition procedures should be considered closed when the contracting officer receives evidence of receipt of property and final payment, unless otherwise specified by agency regulations.

(2) Files for firm-fixed-price contracts, other than those using simplified acquisition procedures, should be closed within 6 months after the date on which the contracting officer receives evidence of physical completion.

(3) Files for contracts requiring settlement of indirect cost rates should be closed within 36 months of the month in which the contracting officer receives evidence of physical completion.

(4) Files for all other contracts should be closed within 20 months of the month in which the contracting officer receives evidence of physical completion.

(b) When closing out the contract files at 4.804-1(a)(2), (3), and (4), the contracting officer shall use the closeout procedures at 4.804-5. However, these closeout actions may be modified to reflect the extent of administration that
has been performed. Quick closeout procedures (see 42.708) should be used, when appropriate, to reduce administrative costs and to enable deobligation of excess funds.

(c) A contract file shall not be closed if (1) the contract is in litigation or under appeal, or (2) in the case of a termination, all termination actions have not been completed.

#### 4.804-2 Closeout of the contracting office files if another office administers the contract.

(a) Contract files for contracts using simplified acquisition procedures should be considered closed when the contracting officer receives evidence of receipt of property and final payment, unless otherwise specified by agency regulation.

(b) All other contract files shall be closed as soon as practicable after the contracting officer receives a contract completion statement from the contract administration
office. The contracting officer shall ensure that all contractual actions required have been completed and shall prepare a statement to that effect. This statement is authority to close the contract file and shall be made a part of the official contract file.

#### 4.804-3 Closeout of paying office contract files.

The paying office shall close the contract file upon issuance of the final payment voucher.

#### 4.804-4 Physically completed contracts.

(a) Except as provided in paragraph (b) below, a contract is considered to be physically completed when--

(1)(i) The contractor has completed the required deliveries and the Government has inspected and accepted the supplies;

(ii) The contractor has performed all services and the Government has accepted these services; and

(iii) All option provisions, if any, have expired; or

(2) The Government has given the contractor a notice of complete contract termination.

(b) Facilities contracts and rental, use, and storage agreements are considered to be physically completed when--

(1) The Government has given the contractor a notice of complete contract termination; or

(2) The contract period has expired.

#### 4.804-5 Detailed procedures for closing out contract files.

(a) The office administering the contract is responsible for initiating (automated or manual) administrative closeout of the contract after receiving evidence of its physical completion. At the outset of this process, an initial contract funds status review shall be accomplished, and where appropriate, excess funds identified to the contracting office. When complete, the administrative closeout procedures shall ensure that--

(1) Disposition of classified material is completed;

(2) Final patent report is cleared;

(3) Final royalty report is cleared;

(4) There is no outstanding value engineering change proposal;

(5) Plant clearance report is received;

(6) Property clearance is received;

(7) All interim or disallowed costs are settled;

(8) Price revision is completed;

(9) Subcontracts are settled by the prime contractor;

(10) Prior year indirect cost rates are settled;

(11) Termination docket is completed;

(12) Contract audit is completed;

(13) Contractor's closing statement is completed;

(14) Contractor's final invoice has been submitted; and

(15) Contract funds review is completed and deobligation of any excess funds is recommended.

(b) When the actions in paragraph (a) of this subsection have been verified, the contracting officer administering the contract shall ensure that a contract completion statement, containing the following information, is prepared:

(1) Contract administration office name and address (if different from the contracting office).

(2) Contracting office name and address.

(3) Contract number.

(4) Last modification number.

(5) Last call or order number.

(6) Contractor name and address.

(7) Dollar amount of excess funds, if any.

(8) Voucher number and date, if final payment has been made.

(9) Invoice number and date, if the final approved invoice has been forwarded to a disbursing office of another agency or activity and the status of the payment is unknown.

(10) A statement that all required contract administration actions have been fully and satisfactorily accomplished.

(11) Name and signature of the contracting officer.

(12) Date.

(c) When the statement is completed, the contracting officer shall ensure that--

(1) The signed original is placed in the contracting office contract file (or forwarded to the contracting office for placement in the files if the contract administration office is different from the contracting office); and

(2) A signed copy is placed in the appropriate contract administration file if administration is performed by a contract administration office.

### 4.805 Storage, handling, and disposal of contract files.

(a) Agencies shall prescribe procedures for the handling, storing, and disposing of contract files. Such procedures shall take into account documents held in other than paper format, such as microfilm and various electronic media. The original medium on which the document was created may be changed to facilitate storage as long as the requirements of Part 4, law and other regulations are satisfied. The process used to create and store records must record and reproduce the original document, including signatures and other written and graphic images completely, accurately, and clearly. Data transfer, storage, and retrieval procedures shall protect the original data from alteration. Unless law or other regulations require signed originals to be kept, they may be destroyed after the record copies on alternate media and copies reproduced from the record copy are verified to be accurate, complete and clear representations of the originals. Agency procedures for contract file disposal shall include provisions that the documents specified in paragraph (b) of this section shall not be destroyed before the times indicated. When original documents have been converted to alternate media for storage, the requirements in paragraph (b) of this section shall apply to the record copies on the alternate media instead of the original documents.

(b) If administrative records are mixed with program records and cannot be economically segregated, the entire file should be kept for the period of time approved for the program records. Similarly, if documents, specified below, are part of a subject or case file which documents activities

different from those specified below, they should be treated in the same manner as the files of which they are a part.

(c) Documents listed in subparagraph (b)(1) shall not be destroyed until final clearance or settlement.

## SUBPART 4.9--INFORMATION REPORTING TO THE INTERNAL REVENUE SERVICE

### 4.900 Scope of subpart.

This subpart provides policies and procedures applicable to reporting contract and payment information to the Internal Revenue Service (IRS).

### 4.901 Definitions.

"Common parent," as used in this subpart, means that corporate entity that owns or controls an affiliated group of corporations that files its Federal income tax returns on a consolidated basis, and of which the offeror is a member.

"Corporate status," as used in this subpart, means a designation as to whether the offeror is a corporate entity, an unincorporated entity (e.g., sole proprietorship or partnership), or a corporation providing medical and health care services.

"Taxpayer Identification Number (TIN)," as used in this subpart, means the number required by the IRS to be used by the offeror in reporting income tax and other returns.

### 4.902 Contract information.

(a) 26 U.S.C. 6050M, as implemented in 26 CFR, requires heads of Federal executive agencies to report certain information to the IRS.

(b)(1) The required information applies to contract modifications--

(i) Increasing the amount of a contract awarded before January 1, 1989, by $50,000 or more; and

(ii) Entered into on or after April 1, 1990.

(2) The reporting requirement also applies to certain contracts and modifications thereto in excess of $25,000 entered into on or after January 1, 1989.

(c) The information to report is--

(1) Name, address, and the Taxpayer Identification Number (TIN) of contractor;

(2) Name and TIN of common parent (if any);

(3) Date of the contract action;

(4) Amount obligated on the contract action; and

(5) Estimated contract completion date.

(d) Transmit the information to the IRS through the Federal Procurement Data System (see subpart 4.6 and implementing instructions).

### 4.903 Payment information.

(a) 26 U.S.C. 6041 and 6041A, as implemented in 26 CFR, in part, require payors, including Federal Government agencies, to report to the IRS payments made to certain contractors.

(b) The following payments are exempt from this reporting requirement:

(1) Payments to corporations. However, payments to corporations providing medical and health care services or engaged in the billing and collecting of payments for such services are not exempted.

(2) Payments for bills for merchandise, telegrams, telephone, freight, storage, and similar charges.
(3) Payments of income required to be reported on
an IRS Form W-2 (e.g., contracts for personal services).

(4) Payments to a hospital or extended care facility described in 26 CFR 501(c)(3) that is exempt from taxation under 26 CFR 501(a).

(5) Payments to a hospital or extended care facility owned and operated by the United States, a state, the District of Columbia, a possession of the United States, or a political subdivision, agency, or instrumentality of any of the foregoing.

(6) Payments for any contract with a state, the District of Columbia, a possession of the Untied States, or a political subdivision, agency, or instrumentality of any of the foregoing.

(c) The following information is required to provide reports to the IRS:

(1) Name, address, and TIN of contractor.

(2) Corporate status (see 4.901).

(d) Transmit to paying offices the information specified in 4.203.

### 4.904 Solicitation provision.

The contracting officer shall insert the provision at 52.204-3, Taxpayer Identification, in solicitations, unless the TIN of each offeror has previously been obtained and is known.