II_01 15 RFQ Feb 12 2026.docx

DOCX document 72 KB Posted

Attached to
Courier Services
Solicitation number
2032H8-26-Q-FMSS1
Issued by

About this file

This is a Request for Quotation (RFQ) for courier services in the Dallas-Fort Worth, Texas metropolitan area issued by the Internal Revenue Service. The requirement is set aside for Service Disabled Veteran Owned Small Businesses under FAR 13 Simplified Acquisition Procedures. The contractor must provide personnel, labor, equipment, supplies, vehicles, materials, and incidental items necessary to deliver boxes and mail to three IRS locations: 1100/1114 Commerce Street in Dallas, 4050 Alpha Road in Farmers Branch, and 5555 N. Beach Street in Fort Worth. The anticipated period of performance is March 1, 2026 through February 28, 2031, with four option periods. The NAICS code is 492110 (Couriers and Express Delivery Services) and the Federal Supply Classification is R602. The RFQ closing date is February 20, 2026 at 12:00 PM EST, with questions due by February 18, 2026 at 4:00 PM EST directed to Contract Specialist Katie Marrette (katie.r.marrette@irs.gov) and Contracting Officer Stacy Parran (stacy.n.parran@irs.gov).

Proposals must address two evaluation criteria: Technical Acceptability (Pass/Fail) and Price. The technical proposal must demonstrate comprehensive compliance with the Statement of Work and include an Initial Staffing Plan using the provided template that reflects the proposed labor mix for the base and option periods, identifies prime and subcontractor roles, and certifies that the small business prime contractor will perform at least 51 percent of the cost of contract performance with its own employees or similarly situated small business concerns as required by FAR 52.219-14. Award will be made to the technically acceptable bidder with the lowest evaluated price, calculated by adding the base period price, all four option periods, and 50 percent of the cost of the final option period. Monthly invoicing must be submitted electronically through the Invoice Processing Platform (IPP), and contractors must submit a monthly workforce report certifying ongoing compliance with the 51 percent performance requirement. Contractors and subcontractors must comply with extensive security, privacy, and records management requirements, including handling of Sensitive But Unclassified (SBU) information, Federal Tax Information (FTI), and Personally Identifiable Information (PII), and must complete mandatory IRS security training and nondisclosure agreements before accessing SBU information.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Subject:

DEPARTMENT OF THE TREASURY INTERNAL REVENUE SERVICE WASHINGTON, DC 20224

Request for Quote (RFQ) Courier Services, Dallas Forth Worth, TX

Closing Date: February 20, 2026 12:00 pm EST THIS IS A REQUEST FOR QUOTATION (RFQ) ONLY. This RFQ gives notice of a Service Disabled Veteran Owned set aside for commercial services, using the procedures in FAR 13-Simplified Acquisition Procedures. The NAICS code will be 492110 and the FSC is R602.

The IRS seeks quote from your firm to provide courier services in accordance with the attached scope of work. The anticipated period of performance is March 01, 2026 – February 28, 2031.

Any questions regarding this requirement must be submitted immediately via e-mail to Contract Specialist Katie Marrette at katie.r.marrette@irs.gov and Contracting Officer Stacy Parran at stacy.n.parran@irs.gov by February 18, 2026 at 4:00PM EST. Questions with the Government’s response will posted as an amendment to the RFQ.

Stacy Parran Contracting Officer

Attachments: Scope of Work

WD 2015-5227 Rev 27 12/03/2025
Attachment 3: Initial Staffing Plan Template
Attachment 4: Monthly Invoicing Report Template

Instructions

Your Request for Quote (RFQ) should specify the criteria in two parts: Technical Acceptability and Price.

Section 1: Technical Acceptability (Pass/Fail) These are the minimum, non-negotiable requirements that all bidders must meet. Bids are simply rated "acceptable" or "unacceptable"—no ranking is performed on the technical factors.

· Mandatory Requirement 1: Compliance with the Statement of Work (SOW)

· Criterion: The vendor must demonstrate a comprehensive understanding of and compliance with all tasks, deliverables, and performance standards detailed in the SOW.

· Evaluation: The proposal will be reviewed to ensure it clearly addresses and satisfies every requirement. Any failure to meet a mandatory SOW requirement will result in a rating of "unacceptable

· Mandatory Requirement 2: Initial Staffing Plan

· Offerors shall submit an initial staffing plan using the template at Attachment 3 as part of the technical proposal. The plan shall reflect the proposed labor mix for the base and each option period and identify prime and subcontractor roles.

· Evaluation: Prime Performance Threshold Certification. In accordance with FAR 52.219-14, Limitations on Subcontracting, offerors shall certify in their initial staffing plan that the small business prime contractor will perform at least 51 percent of the cost of contract performance incurred for personnel with its own employees or those of other similarly situated small business concerns. The staffing plan shall include a clear breakdown of prime versus subcontractor labor hours and cost by labor category for the base and each option period. This information shall be used by the CO to verify compliance at award.

· The staffing plan will be evaluated for realism, balance, subcontract management approach and compliance with 52.219-14, Limitations on Subcontracting.

For all bids found to be technically acceptable, the government will evaluate the proposed price to determine if it is fair and reasonable.

· Lowest Evaluated Price:

· Criterion: The vendor must submit a firm-fixed price for the task order.

· Evaluation: Among all vendors rated "technically acceptable," the award will be made to the one with the lowest total evaluated price.

The IRS will evaluate the submitted firm, fixed-price quote to determine if the quoter’s overall price reflect a clear understanding of the requirements, and are consistent with the quoter’s technical response. Price analysis will be used to verify that the overall firm, fixed-price is fair and reasonable. For purposes of evaluation, the total evaluated price shall include the base period, option periods (four options), to include the option under FAR 52.217-8, and all other costs or prices, as applicable. Price will be evaluated but will not be assigned an adjectival rating. The Government will evaluate the price quote to determine if the total evaluated price is fair and reasonable, reflects a clear understanding of the requirements, and is consistent with the Quoter’s technical response. The Government may use various price analysis techniques and procedures to ensure a fair and reasonable price. Examples of such techniques include but are not limited to a comparison of proposed prices received in response to the solicitation. Normally, adequate price competition establishes a fair and reasonable price. The Government will evaluate quotations for award purposes by adding the total price for all options to the total price for the basic requirement. The Government may determine that a quote is unacceptable if the option prices are significantly unbalanced. Evaluation of options shall not obligate the Government to exercise the options. Note: Evaluation of the option under FAR 52.217-8, Option to Extend Services, will be accomplished by using the pricing offered for the last option period. For evaluation purposes only, fifty percent of the cost offered for the last option period will be added to the base and all other options to arrive at a total price.

The following NOTICE is included for compliance with new executive orders issued:

NOTICE

“System updates may lag policy updates. The System for Award Management (SAM) may continue to require entities to complete representations based on provisions that are not included in agency solicitations. Examples include 52.222-25, Affirmative Action Compliance, and paragraph (d) of 52.212-3, Offeror Representations and Certifications—Commercial Products and Commercial Services. Contracting officers will not consider these representations when making award decisions or enforce requirements. Entities are not required to, nor are they able to, update their entity registration to remove these representations in SAM.”

NOTICE OF MONTHLY DELIVERABLE REQUIREMENT

Post‑Award Monthly Workforce Report (Recurring Deliverable). Contractors shall submit the workforce report using the template at Attachment 4 with each invoice submitted.

(1) Monthly Prime Contractor Certification. Contractors shall include with each monthly workforce report a certification signed by an authorized company officer affirming that, based on current performance data, the small business prime and its similarly situated subcontractors collectively performed at least 51 percent of the total contract cost for personnel during the reporting period. This information shall be used by the CO to verify compliance throughout performance.

The following provisions and clauses will be incorporated into the subsequent award:

52.217-5 Evaluation of Options (Jul 1990)

Except when it is determined in accordance with FAR 17.206(b) not to be in the Government's best interests, the Government will evaluate offers for award purposes by adding the total price for all options to the total price for the basic requirement. Evaluation of options will not obligate the Government to exercise the option(s).

52.217-8 Option To Extend Services (Nov 1999)

The Government may require continued performance of any services within the limits and at the rates specified in the contract. These rates may be adjusted only as a result of revisions to prevailing labor rates provided by the Secretary of Labor. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed 6 months. The Contracting Officer may exercise the option by written notice to the Contractor within 30 days of contract expiration.

52.217-9 Option To Extend the Term of the Contract (Mar 2000)

(a) The Government may extend the term of this contract by written notice to the Contractor within 10 days of contract expiration; provided that the Government gives the Contractor a preliminary written notice of its intent to extend at least 60 days before the contract expires. The preliminary notice does not commit the Government to an extension.

(b) If the Government exercises this option, the extended contract shall be considered to include this option clause.

(c) The total duration of this contract, including the exercise of any options under this clause, shall not exceed 66 months.

PART II

ADDENDUM TO FAR 52.212-4, Contract Terms and Conditions--Commercial Items

(OCT 2018)

The terms and conditions for the following clauses are hereby incorporated into this solicitation and resulting contract as an addendum to FAR clause 52.212-4 (Oct 2018) by reference.

52.203-3 Gratuities (Apr 1984) 52.203-17 Contractor Employee Whistleblower Rights and Requirement To Inform Employees of Whistleblower Rights (Apr 2014) 52.204-4 Printed or Copied Double-Sided on Postconsumer Fiber Content Paper (May 2011) 52.204-13 System for Award Management Maintenance (Oct 2018) 52.212-4 Contract Terms and Conditions—Commercial Items (October 2018) 52.224-1 Privacy Act Notification (Apr 1984) 52.224-2 Privacy Act (Apr 1984) 52.228-5 Insurance – Work on a Government Installation (Jan 1997) 52.232-18 Availability of Funds (Apr 1984) 52.232-19 Availability of Funds for the Next Fiscal Year (Apr 1984) 52.232-39 Unenforceability of Unauthorized Obligations (Jun 2013) 52.232-40 Providing Accelerated Payments to Small Business Subcontractors (Dec 2013) 52.237-2 Protection of Government Buildings, Equipment, and Vegetation (Apr 1984) 52.239-1 Privacy Security Safeguards (Aug 1996)

The terms and conditions for the following clauses are hereby incorporated into this solicitation and resulting contract as an addendum to FAR clause 52.212-4 clauses by full text 52.204-21 Basic Safeguarding of Covered Contractor Information Systems (Jun 2016)

(a) Definitions. As used in this clause– “Covered contractor information system” means an information system that is owned or operated by a contractor that processes, stores, or transmits Federal contract information.

“Federal contract information” means information, not intended for public release, that is provided by or generated for the Government under a contract to develop or deliver a product or service to the Government, but not including information provided by the Government to the public (such as on public websites) or simple transactional information, such as necessary to process payments.

“Information” means any communication or representation of knowledge such as facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audiovisual (Committee on National Security Systems Instruction (CNSSI) 4009).

“Information system” means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information (44 U.S.C.

3502).

“Safeguarding” means measures or controls that are prescribed to protect information systems.

(b) Safeguarding requirements and procedures.

(1) The Contractor shall apply the following basic safeguarding requirements and procedures to protect covered contractor information systems. Requirements and procedures for basic safeguarding of covered contractor information systems shall include, at a minimum, the following security controls:

(i) Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).

(ii) Limit information system access to the types of transactions and functions that authorized users are permitted to execute.

(iii) Verify and control/limit connections to and use of external information systems.

(iv) Control information posted or processed on publicly accessible information systems.

(v) Identify information system users, processes acting on behalf of users, or devices.

(vi) Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.

(vii) Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse.

(viii) Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.

(ix) Escort visitors and monitor visitor activity; maintain audit logs of physical access; and control and manage physical access devices.

(x) Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.

(xi) Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.

(xii) Identify, report, and correct information and information system flaws in a timely manner.

(xiii) Provide protection from malicious code at appropriate locations within organizational information systems.

(xiv) Update malicious code protection mechanisms when new releases are available.

(xv) Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.

(2) Other requirements. This clause does not relieve the Contractor of any other specific safeguarding requirements specified by Federal agencies and departments relating to covered contractor information systems generally or other Federal safeguarding requirements for controlled unclassified information (CUI) as established by Executive Order 13556.

(c) Subcontracts. The Contractor shall include the substance of this clause, including this paragraph (c), in subcontracts under this contract (including subcontracts for the acquisition of commercial items, other than commercially available off-the-shelf items), in which the subcontractor may have Federal contract information residing in or transiting through its information system.

(End of clause)

1052.210-70 Contractor Publicity (Apr 2015) The Contractor, or any entity or representative acting on behalf of the Contractor, shall not refer to the supplies or services furnished pursuant to the provisions of this contract in any news release or commercial advertising, or in connection with any news release or commercial advertising, without first obtaining explicit written consent to do so from the Contracting Officer. Should any reference to such supplies or services appear in any news release or commercial advertising issued by or on behalf of the Contractor without the required consent, the Government shall consider institution of all remedies available under applicable law, including 31 U.S.C. 333, and this contract. Further, any violation of this clause may be considered as part of the evaluation of past performance.

(End of Clause)

IR1052.224-9000 Safeguards Against Unauthorized Disclosure of Sensitive But Unclassified Information (Apr 2024)

1. Treasury Directive Publication 15-71 (TD P 15-71), Chapter III – Information Security, Section 24 – Sensitive But Unclassified Information defines SBU information as ‘any information, the loss, misuse, or unauthorized access to or modification of which could adversely affect the national interest or the conduct of Federal programs, or the privacy to which individuals are entitled under Section 552a of Title 5, United States Code (USC) (the Privacy Act) but which has not been specifically authorized under criteria established by an executive order or an act of Congress to be kept secret in the interest of national defense or foreign policy.’ SBU may be categorized in one or more of the following groups—

· Federal Tax Information (FTI), including any information on or related to a tax return

· Returns and Return Information

· Sensitive Law Enforcement Information

· Employee and Personnel Information

· Personally Identifiable Information (PII)

· Information Collected or Created from Surveys

· Other Protected Information

2. Tax return or tax return information disclosed to the contractor can be used only for a purpose and to the extent authorized herein, and willful disclosure of any such tax return or tax return information for a purpose and to the extent unauthorized for provision of appraisal services to assist with the valuation of conservation easements constitutes a felony, punishable upon conviction by a fine of as much as $5,000 or imprisonment for as long as five (5) years, or both, together with the costs of prosecution. Any such knowing or negligent unauthorized disclosure of tax return or tax return information may also result in an award of civil damages in an amount not less than $1,000 plus costs with respect to each instance of unauthorized disclosure. These penalties are prescribed by the Internal Revenue Code, Sections 7213 and 7431; see also 26 CFR § 301.6103(n)-1.

3. Contractors who perform work at contractor (including subcontractor) managed sites using contractor or subcontractor managed IT resources shall adhere to the general guidance and specific privacy and security control requirements contained in Publication 4812, Contractor Security & Privacy Controls, IRM 10.23.2 - Personnel Security, Contractor Investigations, IRM 10.5.1 Privacy Policy, and IRM 10.8.1 - Information Technology (IT) Security, Policy and Guidance. Publication 4812 and IRM 10.5.1, 10.8.1 and 10.23.2 provide comprehensive lists of all security, privacy, information protection and disclosure controls and guidance.

4. Eligibility, Fitness and Suitability. Contractor (including subcontractor) personnel hired for work within the United States or its territories and possessions and who require staff-like access, wherever the location, to IRS-owned or controlled facilities or work on contracts that involve the design, operation, repair, or maintenance of information systems, and/or require staff-like access to SBU information, must meet the eligibility requirements under IRM 10.23.2, Personnel Security, Contractor Investigations, and shall be subject to security screening and investigative processing, commensurate with the position sensitivity level, and in accordance with IRM 10.23.2, and TD P 15-71. Contractor (including subcontractor) personnel must be found both eligible and suitable, and approved for staff-like access (interim or final) by IRS Personnel Security prior to starting work on the contract/order, and before being granted access to IRS information systems or SBU information.

5. General Conditions for Allowed Disclosure. Any SBU information, in any format, made available to or created by the contractor (including subcontractor) personnel shall be treated as confidential information and shall be used only for the purposes of carrying out the requirements of this contract. Inspection by or disclosure to anyone other than duly authorized officer or personnel of the contractor (including subcontractor) shall require prior written approval of the IRS. Requests to make such inspections or disclosures shall be addressed to the CO. Access to SBU information shall be provided on a “need to know” basis. SBU information shall never be indiscriminately disseminated, and no person shall be given access to (or allowed to retain) more SBU information than is needed for performance of their duties, and for which that individual has been authorized to receive as a result of having been successfully investigated, adjudicated, trained to receive, and what is strictly necessary to accomplish the intended business purpose and mission.

6. Nondisclosure Agreement. Consistent with TD P 15-71, Chapter II, Section 2, and IRM 10.23.2.15 - Nondisclosure Agreement for Sensitive but Unclassified Information, each contractor (including subcontractor) personnel who requires staff-like access to SBU information shall complete, sign, and submit to Personnel Security – through the CO (or COR, if assigned) — an approved Nondisclosure Agreement prior to being granted staff-like access to SBU information under any IRS contract or order.

7. Training. All Contractor personnel assigned to this contract with staff-like access to SBU information must complete IRS-provided privacy and security awareness training, including the Privacy, Information Protection, and Disclosure training, as outlined in IR1052.224-9001 Mandatory IRS Security Training for Information Systems, Information Protection and Facilities Physical Access. Contractor personnel required to take the Unauthorized Access to Taxpayer Data training must attest to understanding the penalties for unauthorized access, as instructed by the COR.

8. Encryption. All SBU information must be protected at rest, in transit, and in exchanges (i.e., internal and external communications). The contractor (including subcontractor) shall employ encryption methods and tools to ensure the confidentiality, integrity, and availability of SBU information.

9. Particularly relevant to this clause are the updated sections to IRM 10.8.1 and Publication 4812 regarding email and text messages, alternative work sites, and incident management:

· For email and text messaging, the contractor shall abide by IRM 10.8.1.4.17.2.2 “Electronic Mail (Email) Security”, IRM 10.5.1.6.8 “Email” plus all subsections, and IRM 10.8.2.2.1.18 “Contractor”; or Pub. 4812 section 28.3.1 “Electronic Mail (Email) Security,”. Included are requirements on encryption, subject line content, and restrictions on personal email accounts.

· For alternate work sites the contractor shall abide by IRM 10.8.1.4.11.16 “PE-17 Alternate Work Site” or Publication 4812 section 21.16 “PE-17 Alternate Work Site,”. Included are requirements for incident reporting, encryption, and secure access.

10. Incident and Situation Reporting. Contractors and subcontractors are required to report a suspected or confirmed breach in any medium or form, electronically, verbally or in hardcopy form immediately upon discovery. All incidents related to IRS processing, information or information systems shall be reported immediately upon discovery to the CO, COR, and CSIRC. Contact the CSIRC through any of the following methods:

CSIRC Contacts:

Telephone: 240.613.3606 E-mail to csirc@irs.gov In addition, if the SBU information is or involves a loss or theft of an IRS IT asset, e.g., computer, laptop, router, printer, removable media (CD/DVD, flash drive, floppy, etc.), or non-IRS IT asset (BYOD device), or a loss or theft of hardcopy records/documents containing SBU data, including PII and tax information, the contractor shall report the incident/situation to the Treasury Inspector General for Tax Administration (TIGTA) hotline at (800) 366-4484.

11. Staff-Like Access to, Processing and Storage of Sensitive but Unclassified (SBU) Information. The contractor (including subcontractor) shall not allow contractor or subcontractor personnel to access, process, or store SBU on Information Technology (IT) systems or assets located outside the continental United States and its outlying territories.

Contractors (including subcontractors) utilizing their own IT systems or assets to receive or handle IRS SBU data shall not commingle IRS and non-IRS data.

12. Disposition of SBU Information. All SBU information processed during the performance of this contract, or to which the contractor (or subcontractor) was given staff-like access (as well as all related output, deliverables, or secondary or incidental by-products, information or data generated by the contractor or others directly or indirectly from the source material), regardless of form or format, shall be completely purged from all data storage components of the contractor’s or subcontractor facilities and computer systems, and no SBU/Personally Identifiable Information (PII) information will be retained by the contractor either--

· When it has served its useful, contractual purpose, and is no longer needed to meet the contractor’s (including subcontractor) other, continuing contractual obligations to the IRS or

· When the contract expires, or is terminated by the IRS (for convenience, default, or cause).

The contractor (including subcontractor) shall completely purge from its systems and any other storage, all SBU data, including PII and tax information (originals, copies, and derivative works) within 30 days of the point at which it has served its useful contractual purpose, or the contract expires or is terminated by the IRS (unless, the CO determines, and establishes, in writing, a longer period to complete the disposition of SBU data including PII and tax information).

The contractor shall provide to the IRS a written and signed certification to the COR that all SBU materials/information (i.e., case files, receipt books, PII and material, tax information, removable media (disks, CDs, thumb drives)) collected by, or provided to, the contractor have been purged, destroyed, or returned.

13. Records Management.

A. Applicability This language applies to all Contractors whose personnel create, work with, or otherwise handle Federal records, as defined in Section B, regardless of the medium in which the record exists. Contractor/subcontractor personnel are bound by the Records Management by Federal Agencies (44 U.S.C. Chapter 31) regarding the care and retention of federal records.

B. Definitions "Federal record" as defined in 44 U.S.C. § 3301, includes all recorded information, regardless of form or characteristics, made or received by a Federal agency under Federal law or in connection with the transaction of public business and preserved or appropriate for preservation by that agency or its legitimate successor as evidence of the organization, functions, policies, decisions, procedures, operations, or other activities of the United States Government or because of the informational value of data in them.

The term Federal record:

1. includes [Agency] records;

2. does not include personal materials;

3. applies to records created, received, or maintained by Contractors pursuant to their [Agency] contract; and

4. may include deliverables and documentation associated with deliverables.

C. Requirements

1. Contractor shall comply with all applicable records management laws and regulations, as well as National Archives and Records Administration (NARA) records policies, including but not limited to the Federal Records Act (44 U.S.C. chapters 21, 29, 31, 33), NARA regulations at 36 CFR Chapter XII Subchapter B, and those policies associated with the safeguarding of records covered by the Privacy Act of 1974 (5 U.S.C. 552a). These policies include the preservation of all records, regardless of form or characteristics, mode of transmission, or state of completion.

2. In accordance with 36 CFR 1222.32, all data created for Government use and delivered to, or falling under the legal control of, the Government are Federal records subject to the provisions of 44 U.S.C. chapters 21, 29, 31, and 33, the Freedom of Information Act (FOIA) (5 U.S.C. 552), as amended, and the Privacy Act of 1974 (5 U.S.C. 552a), as amended and must be managed and scheduled for disposition only as permitted by statute or regulation.

3. In accordance with 36 CFR 1222.32, Contractor shall maintain all records created for Government use or created in the course of performing the contract and/or delivered to, or under the legal control of the Government and must be managed in accordance with Federal law. Contractors shall ensure that all IRS data and IRS-derived data are in commercially available or open and non-proprietary format for transition (back to IRS) in accordance with the National Archives and Records Administration (NARA) disposition guidance.

4. IRS and its contractors are responsible for preventing the alienation or unauthorized destruction of records, including all forms of mutilation. Records may not be removed from the legal custody of IRS or destroyed except for in accordance with the provisions of IRM 1.15.5, Relocating/Removing Records, the agency records schedules and with the written concurrence of the CO. Willful and unlawful destruction, damage or alienation of Federal records is subject to the fines and penalties imposed by 18 U.S.C. 2701. In the event of any unlawful or accidental removal, defacing, alteration, or destruction of records, Contractor must immediately notify the appropriate CO. The CO must report the loss using the PII Breach Reporting Form. Privacy, Governmental Liaison and Disclosure (PGLD, Incident Management) will review the PII Breach Reporting Form and alert the Records and Information Management (RIM) Program Office that a suspected records loss has occurred. The agency must report promptly to NARA in accordance with 36 CFR 1230.

5. The Contractor shall immediately notify the appropriate CO immediately upon discovery of any inadvertent or unauthorized disclosures of information, data, documentary materials, records, or equipment. Disclosure of non-public information is limited to authorized personnel with a need-to-know as described in the [contract vehicle]. The Contractor shall ensure that the appropriate personnel, administrative, technical, and physical safeguards are established to ensure the security and confidentiality of this information, data, documentary material, records and/or equipment is properly protected. The Contractor shall not remove material from Government facilities or systems, or facilities or systems operated or maintained on the Government's behalf, without the express written permission of the Head of the Contracting Activity. When information, data, documentary material, records and/or equipment is no longer required, it shall be returned to IRS control or the Contractor must hold it until otherwise directed. Items returned to the Government shall be hand-carried, mailed, emailed, or securely electronically transmitted to the CO or address prescribed in the [contract vehicle]. Destruction of records is EXPRESSLY PROHIBITED unless in accordance with Paragraph (4).

6. The Contractor is required to obtain the approval of the CO prior to engaging in any contractual relationship (sub-contractor) in support of this contract requiring the disclosure of information, documentary material and/or records generated under, or relating to, contracts. The Contractor (and any sub-contractor) is required to abide by Government and [Agency] guidance for protecting sensitive, proprietary information, and controlled unclassified information.

7. The Contractor shall only use Government IT equipment for purposes specifically tied to or authorized by the contract and in accordance with IRS policy.

8. The Contractor shall not create or maintain any records containing any non-public IRS information that are not specifically tied to or authorized by the contract.

9. The Contractor shall not retain, use, sell, or disseminate copies of any deliverable that contains information covered by the Privacy Act of 1974, Internal Revenue Code section 6103, or that which is generally protected from public disclosure by an exemption to the Freedom of Information Act.

10. IRS owns the rights to all data and records produced as part of this contract. All deliverables under the contract are the property of the U.S. Government for which IRS shall have unlimited rights to use, dispose of, or disclose such data contained therein as it determines to be in the public interest. Any Contractor rights in the data or deliverables must be identified as required by FAR 52.227-11 through FAR 52.227-20.

11. Training. All Contractor personnel assigned to this contract who create, work with, or otherwise handle records are required to take IRS-provided records management training. The Contractor is responsible for confirming training has been completed according to agency policies, including initial training and any annual or refresher training.

D. Flow down of requirements to subcontractors

1. The Contractor shall incorporate the substance of this language, its terms, and requirements including this paragraph, in all subcontracts under this [contract vehicle], and require written subcontractor acknowledgment of same.

2. Violation by a subcontractor of any provision set forth in this language will be attributed to the Contractor.

3. Other Safeguards. [Insert any additional disclosure safeguards provided by the Program Office/COR or that the CO determines are necessary and in the best interest of the Government and not addressed elsewhere in the contract. If none are entered here, there are no other safeguards applicable to this contract action.]

(End of Clause)

IR1052.232-9001 Electronic Invoicing and Payment Requirements for the Invoice Processing Platform (IPP) (Jul 2019)

(a) Definitions:

"Short payment" as used in this clause means the partial payment of an invoice for goods/services actually rendered at the time of payment when the invoice includes additional goods/services that have not yet been provided/rendered.

"Short payment" example: The contract requires the delivery of a set number of items, with the price, delivery location, and delivery due date also specified. The vendor delivers 50% of the items as specified but invoices for 100% of the items. Before implementation of the IPP, the IRS would have paid the vendor for the items delivered and instructed the vendor to re-invoice the IRS when the balances of the items were delivered. In other words, the IRS would "short pay" the invoice since the IRS did not remit payment for the full invoice amount. With implementation of the IPP, the IRS can no longer do this because the IRS cannot accept an electronic invoice that includes items not yet received. The IRS will reject the invoice. The vendor needs to submit an invoice for only the items received by the IRS (in this case, 50%), and, if these items meet all other contract terms and conditions, the IRS will pay the invoiced amount. The vendor submits subsequent invoice(s) for items as they are delivered and accepted.

(b) The Invoice Processing Platform (IPP) is a secure Web-based electronic invoicing and payment information service available to all Federal agencies and their suppliers. Effective October 1, 2012, invoicing for payment through the IPP will be mandatory for all new contract awards. Additional information regarding the IPP may be found at the IPP website address https://www.ipp.gov. Contractors must complete the contractor point of contact information below and submit it with their proposal submissions. Contractors may contact the IPP Helpdesk for assistance via e-mail at ippgroup@stls.frb.org or via phone at (866) 973-3131. Once a contract award has been made, the contractor will be contacted by the IPP via e-mail to set-up an account. It will be necessary for contractors to login to their IPP accounts every 90 days to keep their IPP accounts active.

(c) Contractor Point of Contact Information Contractor Name: ______________________________________________________ Contractor IPP Point of Contact Name: ______________________________________________________ Contractor Phone Number: ______________________________________________________ Contractor E-mail Address: ______________________________________________________

(d) Electronic Invoicing and Payment Requirements Vendor invoices submitted electronically through the IPP should be in the proper format and contain the information required for payment processing. To be approved for payment, a "proper invoice" must list the items specified in FAR 52.232-25 (a)(3)(i) through (a)(3)(x), or in the case of a Commercial Item Contract, the items included in 52.212-4(g)(1)(i) through (g)(1)(x).

If the vendor is offering a discount via the IPP, the discount must be reflected on the invoice. The vendor will select 'Create Invoice'. The IPP system will default to 'Net 30 Prompt Pay' under the Payment Terms dropdown box. The vendor will select from 54 different discount options for the invoice that is being created. If the vendor chooses to offer a discount on the invoice screen, the information will interface to the payment system for processing. Discounts that are offered on attachments rather than the invoice itself cannot be accepted.

Under this contract, the following documents are required to be submitted as an attachment to the invoice (Contracting Officer fills in additional documentation that must be furnished by the contractor (e.g. timesheet)). Please do not submit into IPP any documentation/attachments that conflict with what is stated on the invoice:

Payment and Invoice Questions For payment and invoice questions, contact the Ancillary Systems at (304) 254-3372 or via e-mail at cfo.fm.ipp.customer.support@irs.gov.

(e) Waiver If the Contractor is unable to use the IPP for submitting payment requests starting on October 1, 2012, then a waiver form must be completed and submitted with the contractor's proposal submission for review and approval by the Contracting Officer based on one of the conditions listed in the waiver. The vendor will be notified prior to award as to whether their request for waiver has been approved or denied. If the waiver is granted, then a copy of the waiver must be submitted with each paper invoice that the vendor submits to the payment office or the invoice will be returned.

(f) Short Payment Short payment on vendor submitted invoices will no longer be processed or paid. If any portion of the invoice does not meet the requirements for a proper invoice, the entire invoice shall be rejected and returned to the vendor unpaid.

IRS Invoice Processing Platform (IPP) Waiver Form The IRS invoicing and payment requirements clause (IR1052.232-9000) requires that all invoices under awards made (or effective) on or after October 1, 2012, be submitted electronically via the IPP unless a waiver is requested and granted. If the Contractor is unable to submit its invoice through the IPP, the Contractor shall complete this waiver form indicating the reason for the waiver request by selecting the appropriate box below and providing a narrative summarizing in detail the circumstances requiring a waiver. For a solicitation, submit the waiver form with the proposal submission. For a modification that incorporates the IPP clause into an existing contract, submit the waiver form with the modification. The CO will notify the vendor via e-mail or another appropriate means of communication prior to award as to whether their waiver has been approved or denied. If the waiver is granted, then a copy of the approved waiver must be submitted with each invoice that the vendor submits to the payment office or the invoice will be returned.

Reason for requesting a waiver of the requirement to submit an electronic invoice via the IPP:

[ ] 1. Submission of invoices through IPP would impose a hardship on an individual (includes employees and sole proprietors) due to: either a physical or mental disability; a geographic, language, or literacy barrier; or an undue financial burden. The requirement to submit invoices through the IPP is automatically waived for all individuals who do not have payment capability using ACH with a U.S. financial institution.

[ ] 2. The political, financial or communications infrastructure where the place of business is located does not support access to the IPP for submitting invoices electronically.

[ ] 3. The contractor is located within an area designated by the President of the United States or an authorized agency administration as a disaster area. (Please identify area/location.)

[ ] 4. The submission of invoices electronically may pose a threat to national security, the life or physical safety of an individual may be endangered, or a law enforcement action may be compromised.

[ ] 5. The agency does not expect to receive more than one invoice from the same contractor within a one-year period. i.e., the invoice submission is non-recurring.

[ ] 6. The contractor customarily submits a high volume of invoices on a regular basis via file format, not currently supported by the IPP (i.e., uses a file format other than XML or CSV) and the high volume of invoices would cause a significant burden to the contractor if submitted through the IPP individually. If utilizing this exception, please identify the file formats supported by your invoicing system so that the IPP may consider implementing the requested file format at a later date. File format(s) used: ___________ [ ] 7. Other - Please explain: ______________________________________________________ Attach a separate sheet of paper with a summary narrative substantiating the circumstances for the waiver exception selected from above (1 through 7).

Waiver Submitted By:

Contractor Name

_________________________________________________
___________________
Name of Person Submitting Request for Waiver
Title

Signature of Person Submitting Request for Waiver

_________________________________________________
___________________
E-mail Address
Phone No.
_________________________________________________
___________________
Contract/Order No.
Date Submitted

Waiver Approved By:

Contracting Officer's Name Printed

_________________________________________________
___________________
Contracting Officer's Signature
Date

IR1052.232-9001 Electronic Invoicing and Payment Requirements for the Invoice Processing Platform (IPP) (JUL 2019) Definitions:

"Short payment" as used in this clause means the partial payment of an invoice for goods/services rendered at the time of payment when the invoice includes additional goods/services that have not yet been provided/rendered.

“Short payment” example: The contract requires the delivery of a set number of items, with the price, delivery location, and delivery due date also specified. The vendor delivers 50% of the items as specified but invoices for 100% of the items. Before implementation of the IPP, the IRS would have paid the vendor for the items delivered and instructed the vendor to re-invoice the IRS when the balances of the items were delivered. In other words, the IRS would "short pay" the invoice since the IRS did not remit payment for the full invoice amount. With implementation of the IPP, the IRS can no longer do this because the IRS cannot accept an electronic invoice that includes items not yet received. The IRS will reject the invoice. The vendor needs to submit an invoice for only the items received by the IRS (in this case, 50%), and, if these items meet all other contract terms and conditions, the IRS will pay the invoiced amount. The vendor submits subsequent invoice(s) for items as they are delivered and accepted.

The Invoice Processing Platform (IPP) is a secure Web-based electronic invoicing and payment information service available to all Federal agencies and their suppliers. Effective October 1, 2012, invoicing for payment through the IPP will be mandatory for all new contract awards. Additional information regarding the IPP may be found at the IPP website address https://www.ipp.gov. Contractors must complete the contractor point of contact information below and submit it with their proposal submissions. Contractors may contact the IPP Helpdesk for assistance via e-mail at ippgroup@stls.frb.org or via phone at (866) 973-3131. Once a contract award has been made, the contractor will be contacted by the IPP via e-mail to set-up an account. It will be necessary for contractors to login to their IPP accounts every 90 days to keep their IPP accounts active.

Contractor Point of Contact Information Contractor Name: Contractor IPP Point of Contact Name: Contractor Phone Number: Contractor E-mail Address:

Electronic Invoicing and Payment Requirements Vendor invoices submitted electronically through the IPP should be in the proper format and contain the information required for payment processing. To be approved for payment, a “proper invoice” must list the items specified in FAR 52.232-25 (a)(3)(i) through (a)(3)(x), or in the case of a Commercial Item Contract, the items included in 52.212-4(g)(1)(i) through (g)(1)(x).

If the vendor is offering a discount via the IPP, the discount must be reflected on the invoice. The vendor will select 'Create Invoice'. The IPP system will default to ‘Net 30 Prompt Pay’ under the Payment Terms dropdown box. The vendor will select from 54 different discount options for the invoice that is being created. If the vendor chooses to offer a discount on the invoice screen, the information will interface to the payment system for processing. Discounts that are offered on attachments rather than the invoice itself cannot be accepted.

Under this contract, the following documents are required to be submitted as an attachment to the invoice (Contracting Officer fills in additional documentation that must be furnished by the contractor (e.g., timesheet)). Please do not submit into IPP any documentation/attachments that conflict with what is stated on the invoice:

1052.201-70 Contracting Officer's Representative (COR) Appointment and Authority (APR 2015)

(a) The COR is Kimberly Horton, 4050 Alpha Road, Farmers Branch, TX 75244 (469) 804-0706

(b) Performance of work under this contract is subject to the technical direction of the COR identified above, or a representative designated in writing. The term “technical direction” includes, without limitation, direction to the contractor that directs or redirects the labor effort, shifts the work between work areas or locations, and/or fills in details and otherwise serves to ensure that tasks outlined in the work statement are accomplished satisfactorily.

(c) Technical direction must be within the scope of the contract specification(s)/work statement. The COR does not have authority to issue technical direction that:

(1) Constitutes a change of assignment or additional work outside the contract specification(s)/work statement;

(2) Constitutes a change as defined in the clause entitled “Changes”;

(3) In any manner causes an increase or decrease in the contract price, or the time required for contract performance;

(4) Changes any of the terms, conditions, or specification(s)/work statement of the contract;

(5) Interferes with the contractor's right to perform under the terms and conditions of the contract; or

(6) Directs, supervises or otherwise controls the actions of the Contractor's employees.

(d) Technical direction may be oral or in writing. The COR must confirm oral direction in writing within five workdays, with a copy to the Contracting Officer.

(e) The Contractor shall proceed promptly with performance resulting from the technical direction issued by the COR. If, in the opinion of the Contractor, any direction of the COR or the designated representative falls within the limitations of (c) above, the Contractor shall immediately notify the Contracting Officer no later than the beginning of the next Government work day.

(f) Failure of the Contractor and the Contracting Officer to agree that technical direction is within the scope of the contract shall be subject to the terms of the clause entitled “Disputes.”

IR1052.242-9000 Post Award Evaluation of Contractor Performance (Aug 2025) Interim and final evaluations of contractor performance will be prepared on this contract in accordance with FAR 42.15. The Assessing Official (AO) will prepare a final performance evaluation at the time the work on the contract is completed. In addition to the final evaluation, interim evaluations will be prepared annually to coincide with the anniversary date of the contract. [** If evaluations are conducted annually, modify the above sentence appropriately.] The past performance evaluation process is a paperless process using the Contractor Performance Assessment Reporting System (CPARS). CPARS is a web-based system that allows for electronic processing of the performance evaluation report.

Once the Contractor is registered in CPARS, they will automatically receive an email from the CPARS site with detailed login instructions. Further details, systems requirements, and training information for CPARS is available at the cpars.gov website and in the CPARS User Manual. Online Training for Contractors, and a practice CPARS application are available at the cpars.gov site as well.

Interim and final evaluations are sent to the Contractor for their review and comment as soon as the evaluation is rated. If the Contractor elects not to provide comments, they should acknowledge receipt of the evaluation by indicating "No comment" and then sign and date the form. If the Contractor does not sign and submit the form within 60 days, it will automatically be returned to the Government.

If the contractor disagrees with the ratings, they may indicate that they do not concur with the ratings and provide feedback supporting their disagreement prior to signing the report. When the AO receives this disputed report, they cannot complete the CPARS until they forward the report to a Reviewing Official (RO). The RO reviews the CPARS and determines if the ratings should be revised or not. If the RO decides no changes are necessary, the RO can sign and immediately complete the CPARS. However, if the RO determines that the ratings should be revised, they must send the report back to the AO through the CPARS system. Once the necessary changes are made to the Ratings, the AO sends the report back to RO for completion. The Reviewing Official must be a ‘level-above’ the AO, typically the AO’s supervisor.

The following guidelines apply concerning the Contractor's use of the past performance evaluation:

· Protect the evaluation as "source selection information." After review, transmit the evaluation by completing and submitting the form through CPARS. If for some reason the Contractor is unable to view and/or submit the form through CPARS, contact the Contracting Officer for further instructions.

· Strictly control access to the evaluation within the Contractor's organization. Ensure the evaluation is never released to persons or entities outside of the Contractor's control.

· Prohibit the use of or reference to evaluation data for advertising, promotional material, pre- award surveys, responsibility determinations, production readiness reviews, or other similar purposes.

· A copy of the completed past performance evaluation will be…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .