Appendix 2- Requirements Matrix.xlsx
XLSX spreadsheet 74 KB Posted
- Attached to
- USDA Loan Modernization
- Solicitation number
- Not on record
About this file
This document is a comprehensive Requirements Matrix for the USDA Loan Modernization project, detailing extensive technical and functional requirements for a new loan management system across Rural Development (RD) and Farm Service Agency (FSA) programs. The matrix outlines critical system capabilities across multiple domains including intake, origination, servicing, accounting, construction management, and general system requirements, with each requirement marked as "MUST" and categorized by specific sub-processes and functionalities.
The requirements encompass robust features such as configurable workflows, comprehensive underwriting capabilities, multi-stakeholder access management, document management, integration with government-wide systems, reporting functionalities, and compliance tracking. Key focus areas include creating a unified, secure platform that supports loan application processes from pre-application through closing and servicing, with specific attention to supporting both direct and guaranteed loan programs across various agricultural and rural development contexts. The system must enable seamless interactions between customers, lenders, and agency staff, provide advanced data management and integration capabilities, and ensure compliance with federal regulations and financial reporting standards.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Loan Platform Modernization SOO_Draft.docx | DOCX document | |
| Appendix 4- Pain Points.docx | DOCX document | |
| Appendix 3- Stakeholders and Users.docx | DOCX document | |
| Appendix 1- USDA Enterprise Systems.docx | DOCX document | |
| Final RFI_USDA Loan Platform Modernization RFI.docx | DOCX document | |
| Appendix 5- Metrics.docx | DOCX document |
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
Description Note: This is a requirement matrix provided for context. Requirements will evolve.
To be transparent, separate tabs are provided for RD and FSA requirements, however have been notated where common items exist.
RD
| # | Mission Area/Agency | Category | Process | Sub-Process | Requirement | Priority | FSA Requirement # |
| 1 | RD | Intake | Intake | Inquiry | (Pre-Application) Solution will allow customers and lenders to utilize program inquiry and eligibility tools. Tools may be used by authenticated and unauthenticated users. |
Comment:
| Examples of inquiry tools include (not limited to) Self Assessment Tool, Eligibility Mapper, and Contact Use Case Functionality (unauthenticated users), Income Calculator, etc. | MUST | 35 | ||||
| 2 | RD | Intake | Intake | Lender Approval (Guaranteed Programs) | (Pre-Application) Solution will allow non-regulated lenders to submit applications to USDA to become an approved non-regulated lender. Solution will allow the ability to track Lender Agreements for all lenders to include expiration dates. Solution will maintain a list of approved non-regulated lenders linked to this site so that those inquiring can determine if they have already been approved by the Agency. Solution will also track approved lenders with active Lender Agreement. |
Comment:
| System functionality to include (but not limited to) Approved Lender vs Non-Approved Lender Intake Tracks, user agreement certification, and Lender Designation statuses (to include where lender has authority to lend (specific state(s), nation wide, etc) and regulated or non-regulated status). Solution should also allow regulated lenders the same abilities, but can vary by program. | MUST | 147 | ||||
| 3 | RD | Intake | Intake | User Access (Authentication) | Solution will include robust identity and access management standards for authentication and authorization implementations to enhance security and compliance. |
Comment:
| Access to an intake system likely to utilize, interface with or perform similar functinalies as: Identity, Credential, and Access Management (ICAM), User Verification, login tracking, CRM integration, login.gov. | MUST | 21 | ||||
| 4 | RD | Intake | Intake | Account Management (Authorization) | Solution will include customer relationship manager (CRM) functionality or integration. |
Comment:
| Items to be included in CRM include (but not limited to) entity information, customizable fields, CRM integration, define roles, assign users, permission management, archived applications, capture principals of an organization (e.g., DO Not Pay (DNP)), notify principal updates, many to many user access capabilities with flexibility on varying levels of account access depending on account contact relationship, and delegated authority, etc. Solution must have the ability to authorize users based on program. | MUST | 14 | ||||||
| 5 | RD | Reserved | Reserved | Reserved | Reserved | Reserved | Reserved | |
| 6 | RD | Intake | Intake | Service Area | Solution must include integrations or the ability to obtain geospacial and demographic data from the customer. |
Comment:
| Integrations (i.e. census), must send map file to geospatial warehouse (GDW), must write demographic information of service area (via API calls) to application, drawing/edit/upload a shapefile of a service area, service area/GIS driven scores, eligibility validations (within map validations) | MUST | 61 | ||||
| 7 | RD | Intake | Intake | Preapplication Submittal (if applicable) | Solution will allow customers and lenders to manually enter and upload required pre-application information. Solution must have configurable workflows and allow Agency staff to assign and track work across all levels of the organization. This will include two-way integrations with other systems. |
Comment:
| Eligibility review/SFH self assessment, invite to full app | MUST | common | ||||
| 8 | RD | Intake | Intake | Application Portal | Solution will allow customers and lenders to manually enter and upload required application information. Solution must have configurable workflows and allow Agency staff to assign and track work across all levels of the organization. This will include two-way integrations with other systems. |
Comment:
Examples of information to be captured and configurable workflows include (but not limited to): financial information, document upload/scanning functionality, loan origination wizard(quick app, short loan, long loan, etc.) - configurable capabilities, landing page, AI PER Reader or ePER module that prefills application questions (including technical or engineering information), environmental intake (sub-process), customization/templates/template libraries, automated summary page (validation rules), turbo tax like system, start and stop application(saving as we go), funding opportunity application windows, withdrawal capabilities, help features/user support docs, eligibility criteria configurable capabilities, document upload & document management functionality, evaluation Criteria (not applicable to all programs or funding opportunities), funding allocation (prioritizing & reordering applications), workflow transfer from broker to approved lender (Gtd), and ability to transfer an application to a new lender (Gtd). MUST 36 9 Intake Intake Rules Engine Solution will allow integration with a configurable rules engine.
Comment:
| Rules engine configurations will include (but not limited to) configurable rule sets by program and product, rules managed by program staff, allow for multiple rule sets per program or product. | MUST | 23 | ||||
| 10 | RD | Intake | Intake | Application Submission | Solution will allow customers and lenders to e-sign and submit and/or allow automated application submission capabilities. Solution must have configurable workflows and allow Agency staff to assign and track work across all levels of the organization. This will include two-way integrations with other systems. |
Comment:
| custom triggers, integrations, census data, e-signatures, cost overrun feature triggered from advance of funds | MUST | 36-40 | ||||
| 11 | RD | Intake | Intake | Application Programming Interfaces (API) | Solution shall have the ability to integrate with all critical Agency sub-systems and internal/external partner systems. | |
| Comment: This includes, but is not limited to: Do Not Pay, CAIVRS, HUD total Scorecards, Moody's, Eligibility, PFCS, etc.; outside software integrations (i.e. B2G, QuickBooks, etc.); other internal integrations , external integration, and interfaces to accept electronic payments. | MUST | 5, 14, 48, 61, 75, 76, 81, 82, 99, 130 | ||||
| 12 | RD | Intake | Intake | Application Review | Solution must allow for configurable application review workflows and allow Agency staff to assign and track work across all levels of the organization. This will include two-way integrations with other systems. |
Comment:
| Rules Engine rule sets may be integrated to validate complete applications, program/project eligibility, budget approval, financial feasibility report analysis, Lender's credit analysis, etc. Workflow routing will likely be needed for technical/architectural reviews, financial reviews, service area validation review, environmental review (subprocess), engineering review, appraisal review. Configurable scoring/review features may be needed. Additionaly, the solutions will include repositories for help features for agency staff. Solution must include review approval routing workflow. | MUST | 42-61 | ||||
| 13 | RD | Intake | Intake | Notifications | Solution must allow for configurable automated bidirectional notifications. |
Comment:
| Examples include but are not limited to: external notification, workflow review notifications & workflow tracking, automated internal notifications, permission driven notifications, flexibility in configuring notifications, appeal right notifications, tracking capabilities, customer tracking (status of app), employee metric tracking capabilities, time stamped notes, application tracking - export reports, tracking by program, preference saving capabilities, change in applicaiton status (application approval status, return capabilities, approval capabilities, rejected capabilities, not approved with appeal rights, eligible but not approved). | MUST | 16-19 | ||||
| 14 | RD | Intake | Intake | Tracking Capabilities | Solution must have configurable metrics tracking capabilities for internal and external users, the ability to export the results into various formats, and export/report preference-saving capabilities. |
Comment:
| Examples of metrics tracking include (not limited to): date & time stamped notes & user name, application and review status tracking by program, state, or office, etc. | MUST | 33 | ||||
| 15 | RD | Intake | Intake | Application/Approval Status | Solution must include configurable application approval statuses and bi-directional workflows. |
Comment:
| Examples of statuses and workflows include but are not limited to: Return Status (allows applicant to resubmit application), approval status, rejected status, not approved with appeal rights status, eligible but not approved status, application approval/rejection workflow, bi-directional workflow to accept or reject application. | MUST | 17-18 | ||||
| 16 | RD | Intake | Intake | Public Notice (Statutory) | Solution must include for statutory reporting integrations and/or configurable capabilities. |
Comment:
| deduplication (protected areas), searchable map database of pending and approved broadband projects (statutory) | MUST | RD only | ||||
| 17 | RD | Intake | Intake | Records Management | Solution will include integrations with or capabilities for records management. |
Comment:
| Retain applications in accordance with record retention schedule (driven off Application Status), Purge In-progress applications (not submitted after 'X' amount of time or after window end date) | MUST | common | ||||
| 18 | RD | Intake | Intake | Environmental | Solution must allow customer to manually enter and/or upload environmental information/documentation as required per program. Solution must allow for configurable workflows and allow Agency staff to assign and track work accross all levels of the organization. This will include two-way integrations with other systems. |
Comment:
Requirements must be coordinated with RD's Environmental and Historic Preservation Division (EHPD), and the USDA Permitting and Technology Working Group. This coordinated effort includes incorporating revised NEPA and USDA Implementation Procedures of NEPA. All of this is already being coordinated and captured as a part of the current RPS DME IT effort. Most of these requirements are in an automated system already (and can be exported from JIRA). These requirements can be shared. At a high level, requirements include:
| • | Web-based Portal with Customer-facing interface for partial self-service | |||||||
| • | Integration with other agency geospatial databases for resource analysis | |||||||
| • | Automated transfer of application data or case data from portal to other relevant systems, to and from other agencies or shared services | |||||||
| • | Use defined decision logic to classify level of environmental review and triage | |||||||
| • | Use geospatial data review to automate screening for extraordinary circumstances | |||||||
| • | Use conditional questions/business rules for further analysis and inform workflow for tasks/actions | |||||||
| • | Configure application to support Agency staff reviews and feedback | |||||||
| • | Case management and automation tools for email to send and receive notifications and task data, track milestones for customer and Agency | |||||||
| • | Document management for customer upload documents, summary output for customer | |||||||
| • | Ability to save environmental process at any point | |||||||
| • | Ability to import and read customer submitted documents | |||||||
| • | Ability to adopt other Agency's Environmental documents | |||||||
| • | Produce Agency decision document/Administrative record with direct transfer to Agency record storage systems | |||||||
| • | Agency dashboard for reporting, milestones, and project management | |||||||
| • | Automation of template letters and forms | |||||||
| • | Public notices publication link to hosted location | |||||||
| • | Public comments submission and analysis | |||||||
| • | Ability to update and supplement environmental documentation and findings | |||||||
| • | Ability to have various user roles: ie Customer, Customer Representative, Preparer, Reviewer, Approver, Admin, Auditor, Regional/National Office | |||||||
| • | Flexibility for updating environmental requirements, rules, policy, executive orders, special initiatives, emergency orders | MUST | 57-61 | |||||
| 19 | RD | Origination | Origination | Customer Communication | Solution shall communicate securely with customer to include configuarable bidirectional messaging between internal and external customers. All messaging shall be logged and part of the case record. | MUST | 18 | |
| 20 | RD | Origination | Origination | Workflow Automation/Task Management | Solution must have configurable workflows and allow Agency staff to assign and track work across all levels of the organization. This will include two-way integrations with other systems. | MUST | 33 | |
| 21 | RD | Origination | Origination | Underwriting (Configurable/Customizable) | Solution shall provide comprehensive underwriting capabilities for all RD loan Programs. This solution will have configurable Scoring Capabilities (Scorecard), provide funding availailabilty, create customer triggers (for example, criteria for funding) , support loan and/or grant assistance based on the customer's capacity, test for customer's capacity to obtain other credit. Integrate with data that includes market and industry trends, credit risk models, pull credit from other vendors or services. Customizable underwriting by (and within) programs, to include the ability to overwrite the test for other credit, program funding source and loan/grant determinations. Analyize and Determine risk (repayment ability, credit, test for other credit). Ability to add comments for key milestones, justify business decisions. | MUST | 62-114 | |
| 22 | RD | Origination | Origination | Funding (Deal) Structure | Solution will allow customized loan/grant screens to show the appropriate data field and transactions for each program areas. Solution will analyze pertinent data fields and provide recommendations based on Agency Critera. | MUST | 104 | |
| 23 | RD | Origination | Origination | Custom Rules-Engine | Solution shall provide custom and configurable rules engine with multiple rules sets based on each program requirements. Rule sets must be versioned and provide ability to run simulations using existing data. Ability to include other appliciable Federal (non-RD) and environmental requirements. | MUST | 104 | |
| 24 | RD | Origination | Origination | Approvals | Solution shall include workflow automation, generation of funding conditions, allow multiple levels of approval, allow establishment of proxies for approvals. Communicate outcome (approve, deny, etc) to customer, generate essential documents for additional levels of review and/or approval. The generation of funding conditions must be editable and open to Agency-added conditions. | MUST | 104-117 | |
| 25 | RD | Origination | Origination | Obligations | Solution shall provide a customizable template library, secure digital signatures, two-way secure document exchange. integration with General Ledger, 'smart' record retention, intergrate with other critical platforms identified (to include but not limited to: Servicing, Funds Control, ECF, etc.), automated systems approval (for example GRH delegated authority. | MUST | common | |
| 26 | RD | Origination | Origination | Document Creation | Solution shall automate generation of all Agency and customer legal and programmatic documents required for obligation and closing of the loan. | MUST | 118-122 | |
| 27 | RD | Origination | Origination | API'S and Integrations | Solution shall integrate with all critical Agency sub-systems and internal/external partner systems - this includes Do Not Pay, CAIVRS, HUD total Scorecards, Moody's, Eligibility, PFCS, Credit Repositories or Credit Providers, etc. | MUST | 5, 14, 48, 61, 75, 76, 81, 82, 99, 130 | |
| 28 | RD | Origination | Origination | Closing | Solution shall include configurable automations of the closing process such as generation of closing docs - to include legal documents such as Mortgages, Promissary notes, State required docs, required forms, etc. Obtain digital signatures from all parties and automated Agency acceptance of application. Solution shall include automation of and integrations with internal and external systems for functions such as (not limited to) accepting electronic payments and fees, validating principals of customer organizations, and flow of information into servicing systems. System must include bidirectional workflows for accepting and rejecting applications and the ability to track the secondary market purchaser (gtd programs). | MUST | 115-128 | |
| 29 | RD | General System Requirements | General System Requirements | Roles & Permissions | The solution will support anonymous access by borrowers and Lenders to inquire about Rural Development programs and services (no authentication required). |
Comments:
• Anonymous users will be allowed to enter project information to see if they meet basic eligibility requirements. (Rural Area, Borrower Eligibility, project eligibility, eligible use of funds.)
| • Manually entered data by anonymous users will be retained for 60 days. Authenticated stakeholders will be able to pull up borrower information and push through for processing. | MUST | common | ||||
| 30 | RD | General System Requirements | General System Requirements | Roles & Permissions | The solution will allow authenticated user access. |
Comment:
| USDA roles TBD | MUST | common | ||||
| 31 | RD | General System Requirements | General System Requirements | Roles & Permissions | The solution will support the following Agency user roles and permission. |
Comment: Examples of Agency user roles and permissions include...
| • | Application Acceptor: Able to view all applications and accept/return the application once the customer submits the application for review | |||||
| • | Application Approver: Able to view all applications and approve/return screens associated with the specific project functions (Construction, Engineering, Environmental, Financial). | |||||
| • | Condition of Records: Accountants that perform audits of applicants and borrower’s financial information. | |||||
| • | Load Legacy System: Able to view all applications and push the application to the appropriate legacy system once the application is accepted by the “application acceptor.” | |||||
| • | Program Admin: Able to update data maintained on the administration web page and able to view all applications. Make corrections and reroute workflow tasks as needed. Justification required. | |||||
| • | Request to Obligate: Employees that perform funding request activities. Account for Separation of Duties if needed (request to confirm) | |||||
| • | Obligation Correction: Provide the ability to correct obligation | |||||
| • | Reserve Coordinator: Coordinator for Committee Reviews that determines escalation and review path. | |||||
| • | Reviewer: Employee that work on processing and underwriting loan applications (e.g. analysts, GFR’s, loan specialists). | |||||
| • | Tier1 Approver: Leadership that has approval authority to confer with reviewer recommendations (e.g. Branch Chiefs). | |||||
| • | Tier2 Approver: Leadership that has approval authority to confer with branch chief recommendations and approve loan funding (e.g. Directors) | |||||
| • | Tier3 Approver: Leadership that has approval authority to confer with branch chief recommendations and approve loan funding (e.g. Assistant Administrator, AA Loan Committee Members)) | |||||
| • | Tier4 Approver: Leadership that has approval authority to confer with branch chief recommendations and approve loan funding (e.g. administrators, Senior Loan Committee Members). | |||||
| • | Viewer: Able to view applications | |||||
| • | Environmental and Technical Reviewer: Ability to view environmental or technical reviews and provide comments, should allow for outside USDA access to work with other agencies or consultants, need the ability to account for 3rd party review | |||||
| • | National Technical Reviewer – Ability to review and provide technical review | |||||
| MUST | 21 | |||||
| 32 | RD | General System Requirements | General System Requirements | Roles & Permissions | The solution will support the following Customer/Lender user roles and permission. |
Comment: Examples of customer/lender user roles and permissions include...
| • | Customer/Lender Representative with Final Submit Authority: Allows the user to enter application into the loan management system and perform a preliminary and final submission of the application for all of the lender’s branches. | |||||
| • | Customer/Lender Representative: Allows the user to enter application into loan management system and perform preliminary submission of the application for all of the lender’s branches. | |||||
| • | Customer/Lender Viewer: Allows user view only capability of all applications associated with the customer/lender Tax ID for all branches. | |||||
| • | Branch Representative with Final Submit Authority: Allows the user to enter application into the loan management system and perform a preliminary and final submission of the application for only the lenders branch for which the user is associated. | |||||
| • | Branch Representative: Allows the user to enter application into loan management system and perform preliminary submission of the application for only the lender branch for which the user is associated. | |||||
| • | Branch Viewer: Allows user view only capability of the branch for which the user is associated. | |||||
| • | Customer/Lender Agent: Allow the user to enter applications on behalf of a Customer/Lender and perform preliminary submissions. When the Customer/Lender Agent has completed their portion of the application process, the Customer/Lender Agent will release the application to the Customer/Lender for underwriting processing. | MUST | common | |||
| 33 | RD | General System Requirements | General System Requirements | Roles & Permissions | The solution will support authenticated RD staff with appropriate roles & permission accessing the application from integrated existing Agency application systems, such as GLS, CPAP, PFCS, etc. |
Comments:
| This will likely require that systems mentioned above be updated to support this need. User roles and permission will need to be sync’d across systems. Integrated access users may invoke system directly or from an integrated application. | MUST | common | ||||||
| 34 | RD | General System Requirements | General System Requirements | Roles & Permissions | Solution will support the need for Other Agency/Lender roles | MUST | common | |
| 35 | RD | General System Requirements | General System Requirements | User Interface | Solution will serve as a single access point for customers, lenders and USDA RD staff for all loan application information |
Comment:
| GLS is still system of record for all Guaranteed Loans. CLSS is the system of record for all CF, WEP, RBCS programs; AMAS is the system of record for all Multi-Family loans; LoanServ is the system of record for all Single Family Direct Housing loans. Subject to change. | MUST | common | ||||
| 36 | RD | General System Requirements | General System Requirements | User Interface | Solution will link to existing website that provides general information about the RD programs |
Comment:
| Need to coordinate with Office of External Affairs to implement updates to RD website for smooth transition upon effective date of production of loan management system | MUST | common | ||||
| 37 | RD | General System Requirements | General System Requirements | User Interface | Solution shall support portal functionality for USDA staff, customers, and lenders. |
Comment:
| Examples of portal functionality needed include but not limited to: When USDA staff log-on they will see applications assigned to them or the state/program office they support. When customers and lenders log-on they will see any current applications in the que and the status of submitted applications | MUST | common | ||||
| 38 | RD | General System Requirements | General System Requirements | User Interface | Solution will support search functionality. |
Comment:
| This would include searching by customer, lender, status, area of interest, loa or application ID, Tax ID, etc. Staff should be able to refine search using any metadata being capture as part of the application process. This would include searching for individual documents or content within a document (full text searching). Solutions will support exporting search results. | MUST | common | ||||
| 39 | RD | General System Requirements | General System Requirements | User Interface | Solution shall support touch devices and mobile-friendly interfaces throughout the loan lifecycle. |
Comment:
| Phones, tablets, touch screen devices. Application and mobile friendly interface | MUST | common | ||||||
| 40 | RD | General System Requirements | General System Requirements | User Interface | Solution will support modern browser access and functionality (i.e. Edge, Chrome, Safari, Firefox, etc) | MUST | common | |
| 41 | RD | General System Requirements | General System Requirements | User Interface | Solution will provide help functionality throughout the loan lifecycle to assist staff, customers and lenders with data input and staff underwriting. Examples of help funcitonality include data input examples, regulatory references, etc. | MUST | 10 | |
| 42 | RD | General System Requirements | General System Requirements | Reporting Requirements | Solution must have capabillity to run a wide array of reports, to include custom and predefined reports. Report functionality must include retainability of customized reports per user. |
Comment:
| Examples of reports include (not limited to): Number of inquiries by program; Number of filed Preliminary eligibility reviews; Number of complete/incomplete applications; End of the year reporting, etc.; approved/eligible customers/lenders report by area of interest (AOI), obligations, loan closings, caseload, servicing due dates, delinqeuncy, portfolio reports etc. by office, State, and program | MUST | 2 | ||||
| 43 | RD | General System Requirements | General System Requirements | Reporting Requirements | The solution shall support the delivery of generated reports through a variety of methods including (but not limited to): | |
| • | To a display device, | |||||
| • | As a collection of exported data, | |||||
| • | As a file (or attachment to an email, ensure excel is supported) |
Comments:
| The ability to export the “report” in a form that is useful to the user is very important. This is even more important when you consider anonymous users (non-authenticated) who are not able to retain information. | MUST | common | ||||
| 44 | RD | General System Requirements | General System Requirements | Integration Requirements | The solutions shall interface with the “Integration Layer” (MuleSoft) to manage the business rules. |
Comment:
| Application data will be passed through MuleSoft to check and validate the data. “Services” will be created to support bi-directional data exchange between the loan management system and back-end legacy systems. | MUST | common | ||||
| 45 | RD | General System Requirements | General System Requirements | Integration Requirements | The Solution shall support the ability to access and exchange data with internal and external sites. |
Comment:
| Esamples of systems include but not limited to RD Rural Area Eligibility Map, Census, Treasury, etc. | MUST | common | ||||||
| 46 | RD | General System Requirements | General System Requirements | Integration Requirements | The Solution shall ingest customer/lender data from existing Agency Loan source systems. | MUST | common | |
| 47 | RD | General System Requirements | General System Requirements | Integration Requirements | The solution shall be integrated throughout all loan mangement platforms. | MUST | common | |
| 48 | RD | General System Requirements | General System Requirements | Integration Requirements | The solution must allow loan status/workflow data to be available and transparent to internal and external stakeholders after initiatiating an application and throughout the loan lifecycle. | MUST | common | |
| 49 | RD | General System Requirements | General System Requirements | Integration Requirements | Solution must contain or support integration with a Rules Engine to support complex business rule requirements | MUST | 8 | |
| 50 | RD | General System Requirements | General System Requirements | Integration Requirements | Solution must allow documents and forms created, uploaded and stored in the loan management system to be compliant with federal record retention policies. | MUST | common | |
| 51 | RD | General System Requirements | General System Requirements | Integration Requirements | Solution will integrate with a data warehouse to send application data for reporting purposes and integration with existing business reporting needs. Solution will have ability to integrate data with existing data visualization systems and processes. | MUST | common | |
| 52 | RD | General System Requirements | General System Requirements | Document Management Requirements | Solution will support the uploading of supporting documentation for various file types, such as: PDF, PDF/A, TIFF, GIFF, AutoCAD, JPEG, PNG, ASCII Text, Microsoft products, GIS file types GeoJSON, Binary files, XML, etc. |
Comment:
| File type requirements are based on Program needs and review requirements | MUST | common | ||||||
| 53 | RD | General System Requirements | General System Requirements | Document Management Requirements | Solution will support the ability for USDA staff to download, review and export documents submitted as part of the application. | MUST | common | |
| 54 | RD | General System Requirements | General System Requirements | Document Management Requirements | Solution will support the versioning of certain documents submitted as part of the application | MUST | common | |
| 55 | RD | General System Requirements | General System Requirements | Document Management Requirements | Solution will support the acceptance of scanned applications, reporting documents and compliance-based documents for manual entry. | MUST | common | |
| 56 | RD | General System Requirements | General System Requirements | Document Management Requirements | Solution will support 508 compliant documents. | MUST | common | |
| 57 | RD | General System Requirements | General System Requirements | Document Management Requirements | Solution will support optical character recognition (OCR) of documents with the appropriate metadata (i.e doc types, title, date etc), and automate OCR data import. | MUST | 20 | |
| 58 | RD | General System Requirements | General System Requirements | Document Management Requirements | Solution will support digital signatures when a wet signature is not required. | MUST | common | |
| 59 | RD | General System Requirements | General System Requirements | Communication Requirements | Solution will support bi-directional communication between authenticated internal and external stakeholders. | MUST | 18 |
| 60 | RD | General System Requirements | General System Requirements | Communication Requirements | Solution will track all inquiries and questions sent and received by specific internal and external stakeholders. | MUST | common |
| 61 | RD | General System Requirements | General System Requirements | Communication Requirements | Solution will support event driven bi-directional notifications between internal and external stakeholders. | ||
| MUST | common | ||||||
| 62 | RD | Servicing | Servicing | Customer Communication | Solution will include a secure portal environment that is customer driven for customer contact information to create, store, retrieve and ability to use multiple commication mechanisms. |
Solution will include online resource for customers to access self-help tools.
Comment:
| Examples of items to be included in communication include email, generated letters, certified mail, etc. | MUST | common | ||||||
| 63 | RD | Servicing | Servicing | Graduation | The system will provide the ability to identify and notify borrowers on certain criteria for the review of graduation per program regulations. | MUST | common | |
| 64 | RD | Servicing | Servicing | Guaranteed Lender Delinquency | The system will provide the ability to automate lender delinquency performance metrics. | MUST | common | |
| 65 | RD | Servicing | Servicing | Guaranteed Lender Performance | The system will provide the ability to automate scorecard based on lender performance metrics and complete multiple types of compliance reviews. |
Comment:
| Examples of items to be included in compliance reviews include desk, random selection, targeted selection, on-site and file reviews. | MUST | common | ||||
| 66 | RD | Servicing | Servicing | Document Storage | Solution will support the uploading, reviewing, and downloading of supporting documentation for various file types: PDF, PDF/A, TIFF, GIFF, AutoCAD, JPEG, PNG, ASCII Text, Microsoft products, GIS file types GeoJSON, Binary files. |
Comment:
| File type requirements are based on Program needs and review requirements | MUST | common | ||||||
| 67 | RD | Servicing | Servicing | Automatice Reminders / notifications | Solution will facilitate automatice reminders / notifcations to customer, lender, and agency communications regarding the routine & non-routine servicing actions (not limited to): Submission of annual Audit and/or Financial report; Annual Energy Performance reports; Changes in Collateral; Transfer and Assumption; mergers; subordination of lien position; repurchases; additional expenditures and loans; Lender Failure and borrower default; Protective advances; Liquidations and bankruptcy; litigation; loss calculations and payments; and future recovery, Servicing and Compliance-based submissions, etc. | MUST | common | |
| 68 | RD | Servicing | Servicing | Loan Management | The solution will have the ability to view, report, and manage loans by different stakeholder types including lender, borrower, agency staff, etc. | MUST | common | |
| 69 | RD | Servicing | Servicing | Loan Management | The solution will have the ability for multiple stakeholder types to access various capabilities to update and manage thier loan. |
Comment:
| Examples of access capabilities include mobile device, make payments, online history, loan details, amount due, request servicing actions, edit account information, receive and send secure msg, ultimate recipient reporting, UCC renewals linked to state sites, etc. | MUST | common | ||||
| 70 | RD | Servicing | Servicing | Internal Loan Management | The solution will have the ability for agency staff to complete obligations, disbursements, and complete servicing actions. |
Comment:
| Examples of servicing actions include re-ams, deferrals, loan adjustments, appeals, unauthorized assistance, tennant vouchers, rental assistance, payment assistance, transfers / mergers, mortgage recovery advance, configurable servicing items and due dates, etc. | MUST | common | ||||
| 71 | RD | Servicing | Servicing | Internal Loan Management | The solution will have the ability for Guarantee loan processing. |
Comment:
| Examples of Guarantee fee processing include collection of fees, loss payment, lender certification, lender monitoring, etc. | MUST | common | ||||
| 72 | RD | Servicing | Servicing | Non Routine Servicing Actions | The solution will have the ability to configure non-routine servicing actions. |
Comment:
| Examples of non-servicing actions include parity requests, subordination requests, changes in organization structure, reassignment of loans internally, debt service withdrawl request, application of inncurrence of additional debt, request for grant disposition instructions, etc. | MUST | common | ||||||
| 73 | RD | Servicing | Servicing | Workflow Automation | The solution will have the ability to configure multiple workflows per program and servicing action. | MUST | 149, 152 | |
| 74 | RD | Servicing | Servicing | Escrow Management | The solution will have the ability to configure multi-type management for to gernerate annual escrow statesments, generate insurance and tax payments, and processing insurance claims, and force place insurance. | MUST | RD only | |
| 75 | RD | Servicing | Servicing | Print & Mail | The solution will have the ability of automation of print and mail including handling of rejected certified mail, remittance notification, options for electronic statements, etc. | MUST | 18, 25, 35 | |
| 76 | RD | Servicing | Servicing | Recapture | The solution will have the ability to compute the amount of recapture at time of pay-off and collect. | MUST | common | |
| 77 | RD | Servicing | Servicing | Rate Tables | The solution will have the ability to link, maintain calculate, adjust Rate Tables such as Interest, Subsidy etc. | MUST | common | |
| 78 | RD | Servicing | Servicing | General Security Mainenance | The solution will have the ability to maintain various User Role Designation with various levels. | MUST | 21 | |
| 79 | RD | Servicing | Servicing | Cushion of Credit | The solution will have the ability to configure special legislative customer initiatives to include Cushion of Credit payments and savings flexibilities. | MUST | RD only | |
| 80 | RD | Servicing | Servicing | Integrations/ API | The solution will have the ability to interface with multiple government wide systems such as Treasury, USDA applications, Social Security Administration applications, DOJ applications etc. | MUST | common | |
| 81 | RD | Servicing | Servicing | Online History | The solution will have the ability to maintain a full scope transactional on demand history with roll on ruff off configuration capabilities. | MUST | common | |
| 82 | RD | Servicing | Servicing | Call Center Integration | The solution will have the ability to intergrade and manage workflow call center functions with live chat, AI Reponses, call back and answer features. | MUST | common | |
| 83 | RD | Servicing | Servicing | Property Management | The solution will have the functionality to manage foreclosed properties, sale of real estate properties, substitution of collateral, environmental management, real estate owned inventory etc. | MUST | 93, 149, 150 | |
| 84 | RD | Servicing | Servicing | Property Management | The solution will have the ability to track maintenance costs (program loan cost expense). | MUST | common | |
| 85 | RD | Servicing | Servicing | Program Security & Maintenance | The solution will have the ability to track all routine servicing actions as well as have the ability to provide reports of servicing action due dates. |
Comment:
| Examples of servicing actions include (not limited to): manage and capture property related insurance, security inspections, fidelity bonds, warranty inspections, uniform commercial code filings, risk and resiliency assessments and emergency response plans. etc. | MUST | 129 | ||||||
| 86 | RD | Servicing | Servicing | Complliance Reviews | The solution will have the ability to ensure compliance with internal and external auditors. | MUST | 34 | |
| 87 | RD | Servicing | Servicing | Complliance Reviews | The solution will have the ability to ensure lender compliance with regulations and laws. | MUST | 34 | |
| 88 | RD | Servicing | Servicing | Complliance Reviews | The solution will have the ability to receive automated notifications on ongoing program requirements such as proect performance, status reports, delinquency, current insureance etc. | MUST | 148 | |
| 89 | RD | Servicing | Servicing | Complliance Reviews | The solution will have the ability to capture and mark Improper payments in compliance with Payment Integretity Information Act. | MUST | 48 | |
| 90 | RD | Servicing | Servicing | Mandatory Reporting | The solution will have the ability to produce Key Performance Indicators by Program Type. | MUST | common | |
| 91 | RD | Servicing | Servicing | Mandatory Reporting | The solution will have the ability to interface or communicate data points regarding customer delinquiency to Credit Bureau. | MUST | common | |
| 92 | RD | Servicing | Servicing | Statements | The solution will have the ability to produce monthly, quarterly, annual customer statements, IRS documentation, audit statements and escrow statements in various file formats with export capability. | MUST | 17 | |
| 93 | RD | Servicing | Servicing | Collections | The solution will have the ability for collection hub that allows for automated recovery, debt settlements, foreclosure / cash recovery, acceleration, deed in lieu, short sale, recapture, Treasury Offset Program, etc. | |||
| The solution will have the ability for monotoring and reporting (Federal Financing Bank daily file transfer that has all new obs, notes and advances. Transmission of FFB quarterly payment paid by agency. | MUST | 156 | ||||||
| 94 | RD | Accounting | Accounting | Funds Control | The solution will have the ability to establish, maintain and track Budgetary Funds Control for multiple programs and to flag transactions not in compliance with the Anti-Deficiency Act. | MUST | 165 | |
| 95 | RD | Accounting | Accounting | Funds Control | The solution will be compliant with federal budgetary requirements and support the capability to process all budgetary entries such as allotments, obligations, and disbursements. | MUST | 165 | |
| 96 | RD | Accounting | Accounting | Funds Control | The solution will have the ability to capture, input, store and calculate Credit Reform Subsidy amounts utilizing the stored subsidy rates for all loan obligations. | MUST | 165 | |
| 97 | RD | Accounting | Accounting | General Ledger | The solution will establish and maintain a adaptable and configurable master general ledger table in accordance with USSGL, FASAB, GAAP, SFFAS and Credit Reform Act Guidance. | MUST | 163 | |
| 98 | RD | Accounting | Accounting | General Ledger | The solution will have the ability to calculate the value of a general ledeger entry and create automated general ledger entries based on loan account events (such as delinquencies and interest accruals). | MUST | 163, 161 | |
| 99 | RD | Accounting | Accounting | General Ledger | The solution will have the ability to reference and query detailed historical general ledger entries. | MUST | 163 | |
| 100 | RD | Accounting | Accounting | General Ledger | The solution will have the ability for bi-directional transfer/upload of daily financial files with USDA's core SAP financial system. | MUST | 163 | |
| 101 | RD | Accounting | Accounting | Cash Management | The solution will have the ability to manage incoming payments by automatically applying/posting cash and ability to redirect payment transactions that are unidentified. | MUST | 160 | |
| 102 | RD | Accounting | Accounting | Cash Management | The solution will have the ability to securely capture and store data for electronic funds transfers. | MUST | 160 | |
| 103 | RD | Accounting | Accounting | Cash Management | The solution will have the ability to accept and apply third party payments. | MUST | 160 | |
| 104 | RD | Accounting | Accounting | Cash Management | The solution will have the ability to collect and process refunds. | MUST | 160 | |
| 105 | RD | Accounting | Accounting | Reporting | The solution will have the ability to create and process IRS Required forms. | MUST | 164 | |
| 106 | RD | Accounting | Accounting | Reporting | The solution must include configurable file and data capabilities for all DATA Act Reporting Requirements. In addition, system must be able create and transmit files. | MUST | 164 | |
| 107 | RD | Accounting | Accounting | Reporting | The solution will have the ability to capture, manage, customize and report on Unliquidated Obligations based on ULO certification critieria established by USDA. | MUST | 164 | |
| 108 | RD | Accounting | Accounting | Reporting | The solution will have the ability for ad-hoc queries, dashboards, filtering, and export capabilities in multiple file formats. | MUST | 164 | |
| 109 | RD | Accounting | Accounting | Reporting | The solution will have the ability to create a dynamic portfolio report (delinquencies / caseloads) | MUST | 164 | |
| 110 | RD | Accounting | Accounting | Interfaces | The solution will have the ability to interface with multiple internal and external applications government-wide. | MUST | 5 | |
| 111 | RD | Accounting | Accounting | Credit Reform | The solution will have the ability to execute all required steps in accordance with Credit Reform requirements. All transactional data must be available at the program or risk category level and fiscal year of obligation. Perform calculations based on loan account information to be used in credit reform reporting. | MUST | 159 |
112 RD Accounting Accounting Debt Management The solution will have the ability to determine, manage and age debt, such as delinquencies and defaults. MUST 158 113 RD Accounting Accounting Debt Management The solution will be compliant with Treasury's Debt management regulations, including referring and transmitting eligible debt to Treasury for Treasury Offset Program (TOP) and Cross-servicing. MUST 158
| 114 | RD | Accounting | Accounting | Debt Management | The solution will have the ability to mark customers that have met suspension and debarment threshold/requirements. | MUST | 158 |
| 115 | RD | Accounting | Accounting | PLCE/Cost Items (keep it w/ the loans) | The solution will have the work flow to capture, track and link cost items, including Program Loan Cost Expense, to an existing loan. | MUST | 164 |
| 116 | RD | Accounting | Accounting | PLCE/Cost Items (keep it w/ the loans) | The solution will have the ability to record and link cost items to USDA contract application. | MUST | 164 |
| 117 | RD | Accounting | Accounting | Interfaces | The solution will have the ability to interface with Treasury (TOP, CROSS, SPS, SAMs, CARS), IRS, OMB-FMS, OMB CSC Tool, Federal Financing Bank, DOJ payments, Payment Integrity Act of 2019 (PIIA), and all USDA accounting systems. | MUST | 158 |
| 118 | RD | Accounting | Accounting | Location Look up | The solution will have the ability to determine agency office for servicing, communication, and mailing per program |
Reporting capabilities.
| MUST | 25 | ||||
| 119 | RD | Accounting | Accounting | Collections | The solution will have the a Customer Portal to set up payments / view account information such as summary, due dates, online history, and status, etc. |
The solution will have the ability to accept multiple payment mechanisms such as PAD, REX, Fedwires, lockbox, pay.gov, paper checks, mobile, etc.
The solution will have the ability categorize, track, and manage funds by cohort, FY, and disposition (suspense, escrow, MRA)
| The solution will have the ability to split payments to apply to multiple accounts. | MUST | 167 | ||||||
| 120 | RD | Accounting | Accounting | DIsbursements | The solution will have the ability to create, stop and modify distirbutions via multiple mechanisms, for two-way interface with Treasury for advances, payments, and collections, for escrow disbursements / voids and integration with outside banks and closing agents, and daily / monthly reporting functionality. | MUST | 117 |
| 121 | RD | Accounting | Accounting | Balancing / System Reconciliation | The solution will have the ability for daily reconciliation of transactions, and for workflows to recieve and manage criminal restitution, skip tracing capabilities, escrow reconciliation, suspense / deposit funds, and system / account adjustments. | MUST | 164 |
| 122 | RD | Accounting | Accounting | Auditing / Compliance | The system will have the capability for raw data download / upload, for audit trail for all financial transactions, to create, monitor, and report on workflows, and for Internal / external compliance review and Notice of Funding Availability (NOFA) review Process. | MUST | 168 |
| 123 | RD | Accounting | Accounting | Receivable Management | The solution will have the ability to create multiple receivable types and to create parent child recievable accounts. |
Comment:
| Examples of receivable types include cost items, improper payments, fraud, MFH / SFH unautorized assistance, acquired property, inaccurate information, etc. | MUST | 169 | ||||||
| 124 | RD | Accounting | Accounting | Customer Statements | The solution will have the ability the create, notify, service, and distribute to internal and external customers multipe statement types (quarterly, annual, billing, audit confirmations, etc.) | MUST | 17 |
| 125 | RD | Construction | Construction | Pay Requests | The solution will enable customers to submit both reimbursement and advance payment requests based on their approved scope of work and budget. | |
| Comment: Additionally, users will be able to view details of both current and past payment requests. | MUST | RD only | ||||
| 126 | RD | Construction | Construction | Budget Funding Category Flow From Application | The solution will enable customers to monitor budget items and categories based on the approved work plan and budget data submitted through the intake system. |
Comment:
| The system will display detailed budget information, including category-level and line-item breakdowns, showing both the allocated amounts and the funds spent, reimbursed, or advanced to date. | MUST | RD only | ||||||
| 127 | RD | Construction | Construction | Change Orders/Contract Amendments | The system must support change orders and contract amendments, allowing for updates to the scope of work, budget allocations, and related documentation while maintaining a clear audit trail of all modifications. | MUST | RD only | |
| 128 | RD | Construction | Construction | Do Not Pay API | The system must incorporate an API connection to the U.S. Treasury’s Do Not Pay (DNP) portal (https://fiscal.treasury.gov/DNP/) to prevent improper payments. This integration should allow real-time or scheduled checks against DNP databases as part of the payment approval workflow. DNP must be pulled for entity and principals. | MUST | RD only | |
| 129 | RD | Construction | Construction | Compliance Check | The system must support compliance checks by implementing automated validations and configurable rules to ensure adherence to applicable federal laws and existing Rural Development servicing requirements. It should also be capable of flagging non-compliant entries, tracking their resolution status, and maintaining a complete audit trail of all compliance-related activities. | MUST | RD only | |
| 130 | RD | Construction | Construction | Integrate Associating Records EG: Intake, Origination, Servicing | The system must support integration and association of related records across key loan/grant lifecycle stages—such as intake, origination, construction monitoring and servicing—to ensure continuity, traceability, and efficient data management throughout the program workflow. | MUST | RD only | |
| 131 | RD | Construction | Construction | Interim FInancing Tracking | The system must support monitoring of interim financing activities, including tracking of construction draws, approved change orders, budget shortfalls, budget reallocations, and the injection of additional funding. This functionality should ensure real-time visibility into financial adjustments and maintain a complete audit trail to support compliance, reporting, and decision-making throughout the project lifecycle. | MUST | RD only | |
| 132 | RD | Construction | Construction | Communications | (Requested Actions-Agency to Applicant) The system must facilitate automated, two-way communication between the agency and the customer for key actions—such as requests for concurrence on change orders, budget modifications, and other relevant activities. Notifications should be configurable and trackable, and must include appropriate documentation to ensure transparency, accountability, and timely responses from both parties. | MUST | RD only |
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 .