RFI for 1099 Pro_v1 (CO1.30.26) final.docx

DEFENSE FINANCE AND ACCOUNTING SERVICE

PROJECT MANAGEMENT CENTER OF EXCELLENCE

Page 21 of 33 RFI for 1099

Request for Information (RFI)/ Notice of Sources Sought for 1099 Replacement Defense Finance and Accounting Service (DFAS) Date: 01/30/2026

1.0 PURPOSE

The Defense Finance and Accounting Service (DFAS), on behalf of the Department of War (DoW), is issuing a Request for Information (RFI) for the services specified in the attached DRAFT Performance Work Statement (PWS). The purpose of this RFI is to identify qualified vendors and their potential solutions for a comprehensive, modern software platform to replace the legacy Filing Information Returns Electronically (FIRE) system.

DFAS, Contract Services Directorate is seeking sources to provide a solution and capability statements for a cloud-native, secure, and fully compliant information return filing solution that meets the new Internal Revenue Service (IRS) Information Returns Intake System (IRIS) A2A interface requirements.

2.0 BACKGROUND

The IRS is executing a mandatory technological modernization, transitioning from the legacy FIRE system to the new IRIS platform. IRIS and its Application-to-Application (A2A) interface will become the sole method for electronic bulk filing, requiring a shift from legacy flat-file formats to a structured XML schema. Consequently, DFAS requires a new software solution natively compatible with these specifications.

A back-up self-contained portable desktop solution runnable in a Windows environment that can produce both IRIS XML reporting format and local print is also required. The vendor must provide regular updates and patches for this self-contained portable desktop solution.

This initiative aligns with a broader DoW strategic imperative for digital transformation and the acquisition of adaptable, secure systems. The new solution is expected to enhance data interoperability, automate workflows, and improve operational efficiency. The solution will be deployed on a Government-provided Joint Warfighting Cloud Capability (JWCC) environment, accredited at FedRAMP Impact Level 5 (IL5).

3.0 DESCRIPTION OF REQUIREMENTS & DESIRED CAPABILITIES

Requirements are further detailed in the attached Draft Performance Work Statement. In summary, the ideal provider will have verifiable experience and expertise in solutions that can provide the following capabilities:

3.1 Functional Capabilities

· Form Support & Volume: Ability to create, manage, validate, and correct a wide range of information returns (including W-2C, 1099-NEC, 1099-MISC, etc.) with the capacity to process over 130,000 forms.

· IRS IRIS Compatibility: Full compatibility with the IRS IRIS A2A platform, including XML generation, transmission, and submission tracking.

· User Experience: A modern, intuitive, web-based UI with a central dashboard, guided step-by-step workflows, clear actionable error handling, and responsive design for multiple devices.

· Data Management: Capabilities for importing data from CSV and direct links, exporting to formats like Excel, and supporting bulk editing.

· State Filing: Comprehensive support for the IRS Combined Federal/State Filing (CF/SF) Program and capabilities for direct-to-state filing.

· Vendor API Access: A secure, RESTful API (JSON format) allowing DoW vendors to programmatically access their tax forms via a CAGE code. The API must provide a secure, time-limited download URL for each form in PDF format, with a preference for OAuth 2.0 authorization.

· Recipient Delivery: An integrated service to print and mail physical copies and a secure portal for electronic delivery.

3.2 Data Management and Validation

· Data Migration: A described approach to analyzing and migrating historical data (at least 5 years) from the legacy FIRE system, ensuring data integrity and completeness.

· Data Validation: A multi-layered validation framework, including real-time IRS TIN Matching. The system must quarantine records that fail validation in a dedicated rework queue for user correction

3.3 Security and Compliance

· DoD Compliance: The ability to comply with DoDI 8510.01 (RMF), DISA STIGs (configured to avoid CAT 1-3 violations), and NIST SP 800-53, with a process for tracking vulnerabilities on a POAM using tools like Fortify or ACAS.

· Identity and Access (ICAM): Support for DoD Common Access Card (CAC) / Public Key Infrastructure (PKI) authentication and enforcement of both Role-Based (RBAC) and Attribute-Based Access Control (ABAC) to support a Zero Trust framework.

· Information Handling: The capability to handle and protect Controlled Unclassified Information (CUI) and Personally Identifiable Information (PII) in accordance with DoD Instruction 5200.48.

· Certifications: The ability to meet FedRAMP Moderate baseline requirements, CMMC Level 2, and DoD 5015.02-STD for records management.

· Section 508: Full compliance with the applicable accessibility standards at 36 CFR 1194.

3.4 Technical Architecture and Methodology

· Architecture: The solution must be based on a non-proprietary, object-oriented codebase. The use of low-code/no-code platforms is prohibited.

· DevSecOps: A description of the vendor's methodology for integrating security into a CI/CD pipeline (e.g., SAST, DAST, SCA) to support a Continuous Authority to Operate (cATO). This includes providing security data to Government SIEM/SOAR tools.

· Deployment: The proposed methodology for phased, iterative deployment of software modules into a production environment.

3.5 Sustainment and Support

· Maintenance: An approach to providing ongoing adaptive, corrective, and preventative maintenance, including annual IRS tax updates and release notifications.

· Customer Support: A description of 24/7/365 customer support offerings, including response times based on issue severity and access to a self-service portal.

· Training and Documentation: An outline of the proposed approach to end-user training, knowledge transfer, and the suite of documentation provided (user manuals, O&M manuals, technical guides, etc.)

4. INFORMATION REQUESTED

Information is requested to gain an understanding of how your solution can satisfy the inquiry described in the attached Draft Performance Work Statement. Please provide a comprehensive response to this RFI to include the following:

· A description of the proposed solution.

· A project plan with a detailed timeline to be implemented before the end of FY26.

· A cost breakdown.

· Recent and relevant contracts (last 3 years), including the contract number, and dollar value for procurements you have offering this service (see paragraph 10).

5. RESPONSES

Responses to this RFI shall address all items listed in Section 3 Scope of Work, Section 4 Department of War Requirements, Section 5 Technical Requirements, and Section 6 Deliverables listed above and shall not exceed 5 pages. Responses shall be e-mailed as either a PDF or MS Word attachment and must include a cover letter with the institution’s name, points of contact (address, phone number, and e-mail), DUNS Number and CAGE code. DFAS requests a response by February 27, 2026. Please e-mail responses by the date shown above to the attention of Marlon Garcia at Marlon.i.garcia.civ@mail.mil. DFAS may establish a dialog with vendors who respond if needed to gain a better understanding of their service offerings or capabilities.

6. PROVIDER CAPABILITY & EXPERIENCE:

The Government has additional questions vendors shall address to be considered:

1. DoD Security Compliance and ICAM Integration:

Describe your company's experience delivering and maintaining software solutions within a DoD Impact Level 5(IL5) environment. Please provide specific examples of projects where you have achieved and maintained compliance with DISA STIGs, obtained an Authority to Operate (ATO) under the RMF, and integrated with DoD CAC/PKI. How will your proposed solution integrate with DoW-approved identity providers to enforce attribute-based access control (ABAC) and support a Zero Trust framework?

2. IRS IRIS A2A Experience and High-Volume Processing:

Detail your experience with the new IRS Information Returns Intake System (IRIS) A2A platform. Describe a past project where your solution managed high-volume (e.g., 100,000+) information return submissions via the IRIS A2A API. How does your solution handle the tracking of submission statuses, processing of acknowledgements, and managing the complete lifecycle of error corrections directly through the API?

3. Technical Architecture and "Software Factory" Approach:

Detail your proposed solution's technical architecture. Explain how it is modular to support future enhancements and how it will be deployed (e.g., cloud-native, on-premises). Describe your "software factory" methodology, including the specific CI/CD tools used for your development pipeline, your process for automated regression and security testing (SAST/DAST), and how you manage software release upgrades and patch deployments in a high-security government environment.

4. Data Migration and External API Strategy:

Provide a detailed methodology for migrating five years of historical data from the legacy IRS FIRE format into your proposed solution, including your approach to data validation and ensuring integrity. Furthermore, describe your technical plan for developing the required API that allows DoW vendors to access their tax forms from PIEE MyInvoice, specifically how you would secure this access keyed on a vendor's CAGE code.

5. Data Rights and Intellectual Property:

In accordance with Section 9, provide a comprehensive breakdown of your proposed data rights model. Clearly delineate which components of your solution are considered Commercial-Off-The-Shelf (COTS) or pre-existing (and their proposed licensing terms) versus which components would be custom-developed for this contract. Confirm that the government will receive Unlimited Rights to all custom code, custom-developed interfaces, documentation, and data schemas created under this contract.

6. Records Management and DoD 5015.02-STD Certification:

Pursuant to the requirement in Section 4, please provide either: a) a copy of your solution's current DoD 5015.02-STD 'Electronic Records Management Software Applications Design Criteria Standard' certification for all records-generating components, or b) a detailed plan with specific milestones and timelines for achieving this certification prior to the proposed system deployment date.

7. Customer Support Structure and SLA Adherence:

Regarding the Customer Support requirements in Section 10, describe the structure of your support organization. Please confirm that your support staff are U.S. persons operating within the Continental United States (CONUS). Detail the specific procedures for ticket intake, triage, and internal escalation that enable you to guarantee the specified response times (e.g., 30 minutes for 'Critical' issues) on a 24/7 basis.

8. Section 508 Compliance and Accessibility:

In relation to the 508 Compliance requirements in Section 10, please provide a current and completed Voluntary Product Accessibility Template (VPAT) for your proposed solution. If certain components are not fully compliant, specify each standard that is not met and provide the justification and market research demonstrating that your product is the most compliant available to satisfy the solicitation’s functional requirements.

9. Implementation Timeline and Project Plan:

Provide a draft Project Plan that details all major phases from contract award to final deployment, ensuring project completion before the end of Fiscal Year 2026. The plan must include estimated timelines for critical milestones, including but not limited to: legacy data migration, RMF security control implementation, Authorization to Operate (ATO) activities, user acceptance testing (UAT), and training for DFAS personnel.

10. Transition-Out Plan and Data Portability:

Regarding the Transition-Out Plan required in Section 6, please provide a detailed description of your methodology for transitioning the system, operations, and all government data to the government or a successor contractor at the end of the contract. Your response must specifically address the procedures for complete data extraction, the non-proprietary formats you will use (e.g., CSV, XML), and the knowledge transfer process (including documentation and training) required to ensure government personnel or a new vendor can fully operate and maintain the system independently.

11. Past Performance and Client References:

Please respond to the contact listed below with no more than three pages explaining in detail the magnitude of your experience in the above-mentioned subject matter area. Provide a list of no more than five (3) of your most recent and relevant contracts. Recent means contracts performed or completed within five years from the Sources Sought due date. For contracts that are currently being performed, the vendor must have performed at least six months of service for the contract to be evaluated. Relevant means similar in scope and complexity to the solicited work. Furnish the following information for each contract referenced:

(1) Company/Division name

(2) Description of Service

(3) Contracting Agency/Customer

(4) Contract Number

(5) Contract Dollar Value

(6) Period of Performance

(7) Verified, up-to-date name, address, email and phone number of the contracting officer/POC

(8) Comments regarding compliance with contract terms and conditions

(9) Comments regarding any known performance deemed unacceptable to the customer, or not in accordance with the contract terms and conditions.

(10) Explanation of why their contract is relevant to the solicited work.

Relevancy Table

12. Annual IRS Updates and Maintenance Process:

Regarding the maintenance requirements in Section 6, please describe your lifecycle process for providing adaptive, corrective, and preventative maintenance. Specifically, how do you proactively manage and deploy the mandatory annual IRS tax law and form updates? What is your standard timeline for analyzing, developing, testing, and releasing these critical updates to ensure your clients remain in compliance well before the start of each filing season?

13. Detailed Pricing and Cost Structure:

To support the evaluation of "Cost-effectiveness" (Section 8), please provide a detailed explanation of your complete pricing model. Clarify all potential costs over the life of the contract, including any initial one-time licensing or implementation fees, recurring annual subscription costs, fees based on the volume of forms processed, and any separate costs for ongoing maintenance, major version upgrades, and technical support.

14. Technical Implementation of TIN Matching:

Section 3.1 requires 'TIN Matching with the IRS.' Please describe your technical approach to this feature. Does your solution support real-time interactive TIN matching for individual entries, bulk file matching for large datasets, or both? Detail your experience with the IRS's On-Line Taxpayer Identification Number (TIN) Matching Program and how your system presents match/mismatch results to the user for resolution.

15. Commercial Product Feature Comparison:

Section 3.1 states the software should include functionalities "comparable to leading commercial products." Please identify 2-3 products you consider your primary competitors and provide a feature comparison matrix. This matrix should detail how your proposed solution meets or exceeds their capabilities, particularly regarding high-volume A2A e-filing, automated error correction workflows, and the user experience for managing large datasets.

7. DISCLAIMER

This is a request for information only. It is not a Request for Proposal, a Request for Quotation, an Invitation for Bids, a solicitation, or an obligation on the part of the Government to acquire any products or services. No entitlement to payment of direct or indirect cost or charges to the Government will arise as a result of a contractor submission of responses to this announcement or the Government’s use of such information.

In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. This RFI is issued solely for information and planning purposes and does not constitute a solicitation. Neither unsolicited proposals nor any other kind of offers will be considered in response to this RFI. Responses to this notice are not offers and will not be accepted by the Government to form a binding contract. Responders are solely responsible for all expenses associated with responding to this RFI. All information received in response to this RFI that is marked Proprietary, will be handled accordingly. Responses to the RFI will not be returned. At this time, questions concerning the composition and requirements for future RFPs will not be entertained.

image1.png