Fill and Sign the Bounce House Agreement Form

Fv Issuer Reporting Technical Specifications Document Ginnie Mae Reporting and Feedback System (RFS) Issuer Monthly Reporting Pool, Loan, and Security RPB Data Government National Mortgage Association Contract Number: C-OPC-22592 RFS Issuer Reporting Technical Specifications Document TABLE OF CONTENTS SECTION 1 – GENERAL INFORMATION ............................................................................................. 4 1.1 INTRODUCTION ..................................................................................................................................... 4 1.1.1 Modernization Objectives ...................................................................................................... 4 1.1.2 Operational Direction to Achieve Objectives ........................................................................ 4 1.1.3 Key Changes Summary.......................................................................................................... 4 1.2 PURPOSE ............................................................................................................................................... 5 1.3 USER TRAINING .................................................................................................................................... 5 SECTION 2 - SCOPE .................................................................................................................................. 6 2.1 ISSUER INBOUND DATA REPORTING TO RFS ........................................................................................ 6 2.2 EXCEPTION FEEDBACK FROM RFS........................................................................................................ 6 SECTION 3 – OVERVIEW OF CHANGES ............................................................................................. 8 3.1 GINNIE MAE ENTERPRISE PORTAL ....................................................................................................... 8 3.2 AREAS OF MONTHLY REPORTING THAT ARE CHANGING ..................................................................... 8 3.3 AREAS OF MONTHLY REPORTING THAT ARE NOT CHANGING ............................................................. 9 SECTION 4 – REPORTING SERVICES OFFERED BY GINNIE MAE .............................................11 4.1 CURRENT REPORTING ENVIRONMENT .................................................................................................11 4.2 RFS ISSUER REPORTING ENVIRONMENT..............................................................................................11 SECTION 5 – EXCEPTION FEEDBACK SERVICES OFFERED BY GINNIE MAE ......................12 SECTION 6 - PROCESSING AND TIMELINE ......................................................................................13 6.1 MONTHLY POOL AND LOAN LEVEL DATA INBOUND REPORTING AND PROCESSING SCHEDULE ..........14 6.2 EXCEPTION FEEDBACK PROCESSING....................................................................................................14 SECTION 7 - REPORTING REQUIREMENTS — ISSUER’S MONTHLY REPORTING RECORD LAYOUT AND DATA ELEMENTS DESCRIPTION ............................................................................17 7.1 OVERVIEW ...........................................................................................................................................17 7.2 USE OF THE “SUMMARIZATION FLAG” .................................................................................................19 7.3 RFS RECORD LAYOUT FORMATS ........................................................................................................19 SECTION 8 – RFS EXCEPTION FEEDBACK ERROR MESSAGE ...................................................47 SECTION 9 – EXCEPTION FEEDBACK ONLINE INFORMATION — RFS ...................................50 SECTION 10 – COMPLIANCE REVIEW REQUIREMENTS RELATED TO MONTHLY REPORTING ...............................................................................................................................................51 SECTION 11 – SECURITY........................................................................................................................52 SECTION 12 – ISSUER TESTING PROCEDURES ...............................................................................53 SECTION 13 – RFS COMMUNICATIONS AND FILE TRANSMISSION .........................................54 SECTION 14 – IRTS DOCUMENT HISTORY/CHANGES ..................................................................55 APPENDICES .............................................................................................................................................71 APPENDIX A – MONTHLY INBOUND REPORTING FILE -- EXAMPLES ......................................................71 APPENDIX B – EXCEPTION RECORD -- EXAMPLES ..................................................................................74 APPENDIX C – EXCEPTION MESSAGES ...................................................................................................77 APPENDIX D – GINNIE MAE UNIQUE LOAN ID.......................................................................................87 APPENDIX E – EXAMPLES OF ISSUER REPORTING SCENARIOS................................................................89 2 RFS Issuer Reporting Technical Specifications Document Issuer Reporting Technical Specifications Document For Ginnie Mae systems Reporting and Feedback System Version Change Page The Ginnie Mae Issuer Reporting Technical Specifications (IRTS) document is the specification document for the implementation of future Ginnie Mae systems related to the Business Process Improvement (BPI)/Reporting and Feedback System (RFS). This document may be enhanced and any further updates to the Ginnie Mae IRTS Document will be incorporated into future versions. The Ginnie Mae Issuer Reporting Technical Specifications Document version history: Document Version V1 V2 V3 V4 V5 V6 V6 (Revised) V7 Delivery Date May 8, 2007 June 6, 2007 January 18, 2008 July 31, 2008 February 25, 2009 May 17, 2010 June 1, 2010 March 4, 2011 Change Level Version 1.0 Version 2.0 Version 3.0 Version 4.0 Version 5.0 Version 6.0 Version 6.0 (Revised) Version 7.0 The descriptions of the changes to the Ginnie Mae IRTS document from version to version are detailed in Section 14 of this document. 3 RFS Issuer Reporting Technical Specifications Document SECTION 1 – GENERAL INFORMATION 1.1 Introduction The information in this document is presented to communicate the requirements for monthly reporting of pool, loan, and Security RPB. RFS is a system that is being implemented under Ginnie Mae’s BPI initiative. Ginnie Mae’s BPI involves specific modernization and operational objectives, in particular for Ginnie Mae’s RFS. 1.1.1 Modernization Objectives The specific modernization objectives are: • Establish an operating environment that reduces transaction costs for issuers and broker dealers. • Enable Ginnie Mae to operate in a highly optimized and less costly environment. • Improve the customer service provided to issuers. • Enable analysis of current data for trends, warnings, and performance. 1.1.2 Operational Direction to Achieve Objectives The operational objectives are: • Enhance the quality and frequency of data provided to stakeholders and customers. • Facilitate more rapid implementation of new Ginnie Mae products and programs. • Improve Ginnie Mae’s ability to monitor and manage risk of its underlying portfolio. • Develop a detailed technical architecture for IT modernization and organize resources to enhance Ginnie Mae’s business infrastructure. Ginnie Mae conducted internal process analysis sessions to identify areas and focus for improvement. Ginnie Mae continues to consult with business partners to determine opportunities for enhancement. Ginnie Mae’s objective is to increase and enhance the use of technology as a tool for conducting business with issuers and service bureaus. 1.1.3 Key Changes Summary • The monthly reporting schedule has been accelerated. Issuers will continue to use the month-end accounting cutoff dates that they use today. Refer to Section 6 for additional details. • Security RPB reporting will continue as is reported currently as well as to RFS. Security RPB exceptions will continue to be sent via e-Notification. Corrections must be made via GinnieNET. Refer to Section 3 for more details. • Selected reporting forms have been eliminated. RFS will produce the essential data from the forms. Refer to Section 3 for more details. • New data elements are being introduced at pooling and at monthly investor reporting. Edits and error messages have been added or changed. 4 RFS Issuer Reporting Technical Specifications Document 1.2 Purpose This document is an operational guide that informs issuers and service bureaus how to submit monthly pool administration data files to Ginnie Mae’s RFS. This IRTS document provides information about the files, records, and data elements that are required to transmit monthly data to RFS successfully. The IRTS document also provides files, records, and data descriptions for the messages that are returned to the issuers by the RFS. The information provided in this IRTS document is not intended to establish or change Ginnie Mae policy, regulations, or accounting guidelines as defined in the Ginnie Mae Mortgage Backed Securities (MBS) Guide with which all issuers must comply. This IRTS document assumes that the reader is familiar with the Ginnie Mae MBS Guide 5500.3, and in particular, Chapters 14, 17, 19, related appendices, forms, APMs, and MPMs. Issuers must refer to these regulatory and policy documents for compliance guidance related to pool accounting and administration. This document provides information to issuers and servicers about Ginnie Mae’s final requirements for monthly pool, loan package and loan level reporting processes. The document assumes that the reviewer is generally familiar with Ginnie Mae’s plan for streamlined and reengineered monthly reporting of security RPB, pool or loan package monthly data and loan level data reporting. Information about Ginnie Mae programs can be found on their website at www.ginniemae.gov. Go to www.ginniemae.gov/guide/guidtoc.asp for specific information about reporting requirements and the MBS Guide 5500.3. 1.3 User Training Ginnie Mae has published the RFS Training Presentation for its issuers and servicers to reference. This can be found on Ginnie Mae’s RFS and GinnieNET project web page, http://www.ginniemae.gov/issuers/rfs_toc.asp?Section=Issuers. 5 RFS Issuer Reporting Technical Specifications Document SECTION 2 - SCOPE The scope of this document encompasses monthly ‘inbound data’ submission of data files and the ‘outbound feedback’ messages related to processing results. The scope is essentially related to the “post origination and settlement” pool (and loan package) reporting. For purposes of this IRTS document, with respect to Ginnie Mae loan packages that are part of a multiple issuer pool, this document always refers only to the loan package. Also for purposes of this document, the term “pool” is used synonymously with “loan package.” This IRTS document does not cover or change anything related to pool origination and settlement or pool payment processes. Any changes in these areas will be documented in separate communications. 2.1 Issuer Inbound Data Reporting to RFS Inbound data reporting refers to the data submitted by the issuer or service bureau to RFS. For inbound reporting processes, the BPI enhancements focus specifically on the following: • • • • • Monthly reporting of security RPB data Monthly reporting of pool/loan package data elements Monthly reporting of loan level data elements Monthly reporting timeline New loan level data elements collected at the time of pooling, but also maintainable via monthly reporting. Specific information about the potential changes to reporting timelines and calendars, as well as detailed data element descriptions, is provided in the following pages. 2.2 Exception Feedback from RFS Exception Feedback refers to information provided back to the issuer or service bureau by RFS based on the monthly reporting of pool and loan level information. For Exception Feedback processing, the BPI enhancements focus specifically on exception feedback information to issuers associated with monthly reporting of pool and loan level information. This is a component of the new RFS. In the context of current reporting requirements, the potential changes described in this document would replace: 6 RFS Issuer Reporting Technical Specifications Document • • Current manual processes of notification when there are pool reporting exceptions Current e-Access IEDS screens and download files that contain loan level exception information. This document addresses the following general types of exception feedback: • • • • Exceptions related to reconciling pool/loan data to issuer reported security RPB Exceptions related to pool/loan data calculations and validation Exceptions related to Loan Matching to external agency files Exceptions related to individual data values reported, valid values, and conformance to reporting specifications. The detailed specifications are provided in subsequent sections of this document. 7 RFS Issuer Reporting Technical Specifications Document SECTION 3 – OVERVIEW OF CHANGES 3.1 Ginnie Mae Enterprise Portal Concurrently with the implementation of RFS, Ginnie Mae will implement a web-based, enterprise-wide portal for use by its issuers, service bureaus, and staff. RFS, including monthly issuer reporting, will be done through the Ginnie Mae Enterprise Portal (GMEP). Issuers must register for the GMEP in order to begin reporting through RFS. Further details can be found at http://ginniemae.gov/issuers/rfs_toc.asp?Section=Issuers. 3.2 Areas of Monthly Reporting That Are Changing With regard to “inbound” issuer reporting, the major changes include the following. • • • • • • • • • • Existing HUD-11710A and 11710E forms will no longer be reporting requirements; these will be used only for on-site compliance review. Ginnie Mae will discontinue the web-based features that allow issuers to input and/or print the 11710E, and 11710D forms. Elimination of the existing HUD-11748C form. Loan substitutions (per the MBS Guide 5500.3, Chapter 14) will be controlled by RFS. Issuers requesting loan substitutions will be required to contact RFS Operations Group to coordinate the assignment of a Ginnie Mae Unique Loan ID to the new loan. Consolidation and re-packaging of the data items currently collected by multiple reporting forms/systems. Elimination of the EDI ANSI x.12 (203 Transaction set). With the implementation of the RFS reporting, this standard will not be used for monthly reporting requirements. Elimination of ISDN as a telecommunications service for the secure transmission of monthly loan/pool level reporting data. For inbound reporting Ginnie Mae is specifying flat file, ASCII text format. Additional borrower information will be collected. At the loan level, Ginnie Mae will collect co-borrower information. Currently Ginnie Mae only collects information pertaining to one borrower. With RFS, Ginnie Mae will collect information pertaining to up to no more than five borrowers (primary borrower and up to four co-borrowers) for each loan record, as applicable to the particular loan. Ginnie Mae has implemented the Ginnie Mae Unique Loan ID (a unique loan identifier). This Unique Loan ID will be used by Ginnie Mae and by issuers to “uniquely” identify each loan in a Ginnie Mae pool. (Details provided in Appendix D, Ginnie Mae Unique Loan ID of this document.) Note that Ginnie Mae has standardized the terminology that is to be used for the Unique Loan Identifier. The “Unique Loan Identifier” (or “Unique Loan ID”) is the term that Ginnie Mae will use in its documentation and systems; this replaces references to 8 RFS Issuer Reporting Technical Specifications Document • “Unique Loan Key”, “Loan Key”, or “Loan ID”. Field 6 of the Loan Record, “Issuer Loan ID”, is unaffected by the “Unique Loan ID” name change. In this document the Ginnie Mae pool number field is defined as “alphanumeric.” The field size remains as length of six, and currently Ginnie Mae is continuing to use the six-digit pool numbers. However, to allow for more pool numbers within the current six-position pool number field, Ginnie Mae will begin assigning alphanumeric pool numbers assignment in the future. Ginnie Mae will communicate the details in an upcoming APM. Ginnie Mae is changing the monthly reporting of Pool Data and Loan Level Data, including changes to the exception feedback process when problems with the reported data occur. The major changes are described below. • • • • • • Issuers will continue reporting the monthly Security RPBs as is done currently. Security RPB exceptions will be sent via e-Notification. Issuers will correct exceptions via GinnieNET. In addition, the Security RPB is also to be reported to RFS per the IRTS (Pool Record, field 10). However, the official Security RPB is to be reported per the current process. Pool level and loan level reporting will be included in the RFS reporting stream. Therefore, pool level and loan level exceptions will be included in the RFS Exception Feedback functions. Modified reporting timeline is provided. See Figure 6.1.in Section 6. Changes to the exception feedback timeline such as updates/corrections can be made during the reporting period. The “severity level” ranking of exceptions is changing such that high priority exceptions can be easily distinguished from less critical exceptions. New functionality is provided that gives the issuer the option of making corrections online if the issuer chooses to do so; otherwise, the issuer can submit updated (“correction”) files. Note that either a complete file or a correction file can be submitted; however, the data record(s) must be the entire record, not just the updated fields. More exception information will be available both online via the internet and in downloadable files. Point-to-point service is available via secure file transfer protocol (sFTP) for inbound reporting. Issuers should contact the Ginnie Mae Help Desk, 1-800-234-4662, Option 1 to obtain a user id and password for inbound reporting using sFTP. 3.3 Areas of Monthly Reporting That Are Not Changing The pool administration, accounting, and reporting requirements that are not changing are below: • The policy regarding issuer monthly reporting cut-off period will not change. MBS Guide 5500.3, Section 17-3 will remain as is. 9 RFS Issuer Reporting Technical Specifications Document • • • • The policy regarding issuer responsibility to maintain all accounts and records relating to the pooled mortgages and securities, and maintaining them in accordance with sound accounting practices and in a manner that will permit Ginnie Mae or its representatives to examine and audit them at any reasonable time will not change. MBS Guide 5500.3, Section 17-2 will remain as is. Issuers will continue to be required to produce the HUD 11710D form as a monthly reporting instrument (through GinnieNET); additionally, issuers will continue to be required to produce the 11710D for on-site or other such compliance reviews. Issuers will continue to be required to produce the HUD 11710A and the HUD 11710E forms, but only for on-site or other such compliance reviews. The accounting procedures will remain unchanged; only the reporting requirements will change. Issuers will continue to be responsible for reporting monthly security RPBs. Issuers will continue to be responsible for reporting loan level and pool level data elements each month and responding to exception conditions. 10 RFS Issuer Reporting Technical Specifications Document SECTION 4 – REPORTING SERVICES OFFERED BY GINNIE MAE 4.1 Current Reporting Environment Ginnie Mae is providing a range of services for issuer reporting of monthly security RPB, monthly pool accounting data, or monthly loan level data under RFS. In general, the current services provided include the following. • • • • Bulk/Large Volume electronic transmission of data—this is essentially “point-topoint” telecommunications and transfer of data from issuer computing platform to Ginnie Mae platform. Direct data entry, using online screens—this is essentially either GinnieNET direct data entry or RFS direct data entry. File Upload (import)—this is essentially either GinnieNET file upload or RFS file upload from the Internet. Physical Media—Ginnie Mae will no longer accept physical media, such as cartridge or tapes, except as a contingency. 4.2 RFS Issuer Reporting Environment Reporting will be streamlined and consolidated. Ginnie Mae will continue to offer a broad range of services that will support issuers regardless of size, reporting volume, or program area participation. The services that Ginnie Mae will offer in support of the streamlined and enhanced monthly reporting include: • Direct data entry, using online screens—this will be Internet Web-based direct data entry into RFS. The enhanced systems will all be Internet, Web-based applications. (Direct data entry is not the focus of this IRTS Document.) • File Upload (import)—RFS will provide functionality for file import that is Internet Web-based upload using the HTTPS protocol. This functionality can be used for all reporting submissions that are 5MB or less in size. • Secure File Transfer Protocol (SFTP)—RFS will support Internet-based file transfer for monthly reporting data submission using the secure file transfer protocol (SFTP). Ginnie Mae has chosen the WS_FTP product for secure data transmission between the issuer and Ginnie Mae. Any issuer can use this capability; however, it must be used if the issuer submits any data files larger than 5MB in size. 11 RFS Issuer Reporting Technical Specifications Document SECTION 5 – EXCEPTION FEEDBACK SERVICES OFFERED BY GINNIE MAE Exception feedback associated with pool and loan data reporting will be streamlined and consolidated under the RFS. Ginnie Mae is providing a range of services that will support issuers regardless of size, reporting volume, or program area participation. The exception feedback services include the following. • • • • • • Notification of exceptions via Ginnie Mae’s e-Notification. On a routine basis, Ginnie Mae will post notices to issuers’ mailboxes on e-Notification indicating that there are exceptions associated with the reported data. Issuers can go online to RFS to view the exception status of the reported data. Online exception feedback information is accessible via the Internet. The online screens will provide exception information at all levels from the issuer summary level, to individual pool level, to the detailed loan level. Option to use direct data entry online to make changes and/or corrections. These enhanced functions will be Internet Web-based applications. Exception file download function (CSV files with exception records) that will be Internet-based. Secure FTP—Internet-based exception file transfer using a secure FTP will allow issuers to download exception files securely. Online summary display screen that is generated by RFS. This gives the equivalent of the HUD-11710D form information; this should be retained in the issuer’s files. Ginnie Mae’s RFS will provide a range of secure services to issuers and service bureaus. 12 RFS Issuer Reporting Technical Specifications Document SECTION 6 - PROCESSING AND TIMELINE The graphic below represents the processing timeline for both security RPB and pool/loan level reporting. These two reporting processes remain separate and distinct from one another. Issuers are to report their security RPB data to the CPTA and the RFS is used by Issuers to report their monthly pool/loan level data. Timeline for Ginnie Mae Issuers to Submit Monthly MBS Data Security RPB and Pool and Loan Data Reporting Beginning on 26 Calendar Day th 2 nd BUSINESS DAY RPB Reporting SUBMIT SECURITY RPBs USING CURRENT PROCESSES BY CLOSE OF BUSINESS Pool/Loan Data Reporting SUBMIT ACCOUNTING DATA ( POOL /LOAN ) TO RFS BY CLOSE OFBUSINESS rd 3 BUSINESS DAY Submit Corrections via Ginnie NET 4 th BUSINESS DAY th 10 th th 5 –9 BUSINESS DAY BUSINESS DAY SUBMIT FINAL SECURITY RPBs USING CURRENT PROCESSES BY CLOSE OF BUSINESS Submit Corrections via RFS SUBMIT FINAL ACCOUNTING DATA ( POOL /LOAN ) TO RFS BY CLOSE OF BUSINESS Figure 6.1-Timeline for Ginnie Mae Issuer Reporting Monthly MBS Data As the diagram above shows, initial reporting of the security RPB must be reported by close of business on the 2nd business day each month, with final security RPB values reported by close of business on the 4th business day. Refer to Chapter 19, Reporting Remaining Principal Balances, in the Ginnie Mae MBS Guide for more details on the RPB reporting process and timeline. The monthly investor reporting processing timeline has not changed and requires that Issuers make their initial submission of pool and loan-level data by close of business on the 2nd business day, with final corrections reported by close of business on the 10th business day. Please also refer to Ginnie Mae processing timeline published in APM 09 – 11, which outlines the processing timelines for both security RPB and pool/loan-level reporting. Note: All stated times in this document refer to Eastern Standard Time. Close of Business (COB) is 7:00 PM. Beginning of Business (BOB) is 6:00 AM. 13 RFS Issuer Reporting Technical Specifications Document 6.1 Monthly Pool and Loan Level Data Inbound Reporting and Processing Schedule The RFS monthly reporting schedule is as follows: • Monthly reporting from issuers is due no later than COB on the 2nd business day of the month. Issuers will report loan and pool accounting data. Issuers may begin reporting to RFS after their internal (month-end) cut-off date (see MBS Guide Section 17.3); however, files received early by RFS will be held until the initial RFS production jobs begin for the month. • Issuers may submit more than one file per day. Each file may contain data for one or more issuers and one or more pools. If corrections are required, a file containing only corrected records may also be submitted. The file format is the same regardless of whether it is an initial submission, a subsequent submission, or a correction submission. There is no special file format for corrections. The correction files referred to above apply to any of the record types in Section 7. • Final pool/loan level reporting and corrections are due no later than COB on the 10th business day. Corrections to non-RPB related data items will be accepted and processed through the 10th business day of the reporting month (see Figure 6.2, Error and Warning Level Definitions later in this document). Please note that the Security RPB, reported on the monthly report of pool and loan level data, shall equal the RPB that was reported to the CPTA by the fourth business day. Issuers can submit multiple files during the reporting period. RFS will automatically detect file submissions and place them in a first-in-first-out processing queue. 6.2 Exception Feedback Processing The RFS exception feedback process and timeline is as follows: • • • • Issuer monthly inbound data reporting/files will be processed essentially “upon receipt” by RFS Exception information will be available to issuers essentially “upon completion of processing” of the reported data If the issuer has exceptions, the system will automatically generate a notice and post it to the issuer’s e-Notification box The online exception feedback process will allow issuers to request, view, and/or download exception information, by severity level. Exception processing will begin as soon as possible after receipt of the issuer file. Each time data is reported, an exception information/download file is created. Issuers then may submit correction files as soon as they are ready for transmission. If there are no exceptions, a positive confirmation will be provided. The file naming convention for exception files is: 14 RFS Issuer Reporting Technical Specifications Document Exception_iiii_yyyymm_ddhhmi.csv where: • • • iiii yyyymm ddhhmi is the issuer number is the reporting period is the date and time in which the file was created Ginnie Mae anticipates the following schedule for issuer follow-up on monthly reporting exceptions. • • • Issuers will immediately follow-up on all exceptions related to loan and pool accounting data. These exceptions would be available no later than the beginning of business (BOB) on the 3rd business day. Issuers will immediately follow-up on these same exceptions through the 10th business day, as applicable based on any subsequent data submitted by the issuer. Missing pools and missing loans not reported on the second business day are considered exceptions and must be submitted/corrected immediately. RFS allows for continued correction to non-RPB related data during the reporting period, after the 4th business day and through the 10th business day. It is understood that some types of exceptions require more research during the reporting period or in a subsequent period, depending on the data condition and research required. The monthly schedule for RFS exception processing and follow-up is summarized in the table below. Table 1 – Monthly schedule for RFS Exception Processing Summary RFS Activity Schedule RFS Opens for Receipt/Input of Data any time after midnight on the 25th. Ginnie Mae anticipates that the telecommunications infrastructure will be in place to accept the files at that time; files will be held for the initial RFS production job for the reporting period. RFS Monthly Inbound File Processing and Exception Feedback RFS Monthly Inbound File Processing and Exception Feedback—non-RPB related corrections RFS Closes—All Processes 15 RFS open for receipt of files 26th calendar day of the month 2nd Business Day through 10th Business Day; processes files as received 10th Business Day COB 24th Calendar Day RFS Issuer Reporting Technical Specifications Document The figure below shows the anticipated severity levels and timelines for resolving monthly reporting exceptions. RFS Pool Accounting and Exception Feedback Error and Warning Level Definitions SEVERITY LEVEL SEVERITY DESCRIPTION Fatal Ø Issuer File cannot be processed Ø Must be resolved immediately upon notification; Issuers will be contacted by phone for file problems Error Ø Record cannot be processed; inbound data is "Held" pending a resolution Ø Must be resolved for record to be processed Critical High Ø Security RPB Validation-related warnings; Data elements included in the calculations Ø Resolve exceptions no later than 10th business day Ø Loan Data used in Calculations (non Security RPB) Ø Pool and Pool Master Calculations (non Security RPB) Ø Multifamily Loan Calculations (non Security RPB) Resolve exceptions no later than 10th business day Ø Medium Low Ø Single Family Loan Matching and/or Suspense Ø Resolve, if feasible given the data condition, in the current reporting period; otherwise next reporting period Ø Loan Data Elements not used in Calculations or matching; or problems with "Other" pool related data elements Ø Resolve if feasible given the data condition, in the current reporting period; otherwise next reporting period Figure 6.2 Error and Warning Level Definitions Issuers will be able to go online to RFS and request exception information by individual severity level (or all). This would also apply to the download file of exception information. 16 RFS Issuer Reporting Technical Specifications Document SECTION 7 - Reporting Requirements — Issuer’s Monthly Reporting Record Layout and Data Elements Description 7.1 Overview Ginnie Mae RFS accepts six upload record formats. These upload files are used by issuers for their monthly pool administration reporting to Ginnie Mae. The six types of records that may be included are listed below. • • • • • • H – Header issuer record This mandatory record is a control record. This record is always present in the submission file. P – Pool record This record contains data elements related to the Ginnie Mae pool, including the Security RPB; one record reports on one pool. A file would typically have one pool record for each pool reported by the issuer. It is not mandatory that a submission file always have Pool records. L – Loan record This loan level record contains data elements related to the loans associated with the pool records, one record for each loan. A file would have one loan record for each loan reported by the issuer. It is not mandatory that a submission file always have Loan records. S – Sensitive loan record This loan level record contains “static” information and personally identifiable information (PII). It is typically not reported and is only reported if there is a change to the data, or if there is a reporting exception message that requires correction of the data. A file would typically have relatively few or no Sensitive loan records. V – Various loan record This loan record contains various other “static” information related to the loan. It is typically not reported, and is only reported if there is a change to the data, or if there is a reporting exception message that requires correction of the data. A file would typically have relatively few or no various loan records. T – Trailer issuer record This mandatory record is a control record. This record is always present in the submission file. This record contains summarization numbers from other records. This record also contains a flag to indicate that the issuer’s submission of data is complete. All submission files must have a header record, trailer record and some number of individual records depending on the issuer data for that particular submission. Typically, a single submission file would have a header, all of the individual records as applicable for the reporting period, and a trailer record. For follow-up submissions and for corrections, 17 RFS Issuer Reporting Technical Specifications Document the submission file can have a header, any combination of detail records, and a trailer. Multiple files can be submitted during the reporting period. Multiple issuer data can be submitted in a single submission. In this case, the submission file must have a header, detail records, and trailer for each different issuer’s data. The submission file would have multiple sets of header, detail records, and trailer for the number of the issuer’s data that is being reported. For a submission file that contains data for only one issuer ID, the file naming convention is: rfsyyyymmss.iiii where: • “rfs” is constant • “yyyymm” is the reporting year/month • “ss” is a file sequence number; the default value is 01; if needed this number should be incremented by one for every subsequent file submitted during the same reporting period. (For example, if an issuer submits four files during a given reporting period the valid formats would be rfsyyyymm01.iiii, rfsyyyymm02.iiii, rfsyyyymm03.iiii, and rfsyyyymm04.iiii). • “iiii” is the issuer ID # for the issuer Additionally, for a submission file that contains data for more than one issuer ID, the file naming convention is: rfsyyyymmss.iiiim where: • “iiii” is the issuer ID # for any of the issuers represented in the file. (For example, if a single submission file contains data for issuer with issuer ID#'s 9997, 9998, and 9999, the valid formats would be any of the following: rfsyyyymmss.9997m, rfsyyyymmss.9998m, or rfsyyyymmss.9999m). • “m” is constant. Upload file formats are variable-length records (see the “Remarks” column of each upload file layout for additional information). Unless otherwise noted in the “Remarks” column, fill character fields to the right with spaces and fill numeric fields to the left with leading spaces or zeroes. Decimal points are part of the field lengths – include decimal points for dollar amounts, interest and other rates. Use a leading hyphen or dash “-” to indicate negative numbers. Fields designated as signed in the record layout require a “+”, “-”, or “space” as the first character. The symbols “+”, “-“, and “space” are the only valid values; a space in a signed field implies positive. Refer to Appendix A for the full set of file failure conditions and instructions for proper record processing. For each submission file received, a functional acknowledgement file is produced to provide the issuer feedback on the status of the submission file. The Functional Acknowledgement file naming convention is: 18 RFS Issuer Reporting Technical Specifications Document fayyyymmss.9999 where: • fa is constant • yyyymm is the reporting period • ss is the file sequence number • 9999 is the issuer ID 7.2 Use of the “Summarization Flag” Note that the RFS Trailer Record has a “Summarize Flag”. If the flag is set to “Y”, RFS will use this indicator to proceed with summarization of loan detail to the pool level. The purpose of the “Summarize Flag” is the file indicator to RFS that the issuer reporting/file submission is complete. If the flag is set to “N”, RFS will accept the submission but will not proceed with the summarization of loan data to the pool level. If the file submission contains reporting data for a single issuer, the flag set to “Y” will indicate that this entire submission (and any previous submissions this reporting period) is complete and should be fully processed by RFS. For a file submission that contains reporting data for multiple issuers, the flag is set on the trailer record for each issuer reporting data. The flag is applicable only for that particular issuer. If the file submission is a final update of reporting data (to one or more previous file submissions this period, whether the flag was “Y” or “N”) set the flag to “Y”. The expectation is that issuers will use the “Summarize Flag” for all their upload file submissions. Ginnie Mae recognizes that some file submitters need to submit their data in multiple files, such that the complete set of data for an issuer may arrive in two or more files. Generally, the expectation for a multiple file submission is that the last file will have the Summarize Flag set to “Y.” However, if an issuer cannot be certain that multiple files will always be submitted in the same order (e.g. File 1, File 2, File 3 in one month, but File1, File 3, File 2 in an ensuing month), it is permissible for an issuer to set all Summarize Flags to “N” and to use the RFS Pool Accounting web module to initiate summarization. An issuer with a web account (similar to today’s e-Access accounts) may log in, after all files have been uploaded and processed by RFS, and use the “Summarize Pools” function in RFS Pool Accounting. Online use of the “Summarize Pools” function is equivalent to a “Y” in the “Summarize Flag” field of the Trailer Record. 7.3 RFS Record Layout Formats In this document, each upload file layout is followed by the definitions of each field in the record layout, which are numbered to correspond to the file layout. The definitions are followed by exception messages that may occur if business rules are not observed. Italicized exception messages result from inconsistencies between pool and loan level reporting. These exceptions may occur when the loans are summarized to the pool level. 19 RFS Issuer Reporting Technical Specifications Document H - Header issuer record Field # Field Name Start End Type Length 1 Record Type 1 1 Character 1 2 Issuer ID 2 5 Numeric 4 3 Record Date 6 11 Date 6 Remarks Constant H - Header YYYYMM 1. Record Type: The letter H as the first character in a record identifies it as a header record. This record must precede all records that correspond to the issuer. 2. Issuer ID: Issuer number Ginnie Mae assigned to the issuer organization. 3. Record Date: The Ginnie Mae reporting month being reported to Ginnie Mae. • E-RFS200 Reporting Period must be specified. • E-RFS201 Reporting Period must be a valid year and month. • E-RFS202 Reporting Period must be in YYYYMM format e.g. 200601. • C-RFS204 Reporting Period for this pool was not received by Ginnie Mae. • E-RFS205 Reporting Period no loans or pools have been reported. 20 RFS Issuer Reporting Technical Specifications Document P - Pool record Field # Field Name Start End Type 1 Record Type 1 1 Character 1 Constant P - Pool 2 Pool ID 2 7 Character 6 Must be a valid Ginnie Mae pool. 3 Adjust FIC 8 19 Numeric 12 99999999.99 Signed Field 4 Pool FIC 20 30 Numeric 11 99999999.99 5 Servicing Fee 31 41 Numeric 11 99999999.99 6 Weighted Average Interest Rate 42 48 Numeric 7 99.9999 7 Net Adjust RPB 49 62 Numeric 14 9999999999.99 Signed Field 8 Deferred GPM Interest 63 73 Numeric 11 99999999.99 9 Serial Note 74 86 Numeric 13 9999999999.99 10 Security RPB 87 99 Numeric 13 9999999999.99 The reported security RPB for the reporting period 11 T&I Escrow Balance 100 111 Numeric 12 99999999.99 Signed Field 12 P&I Fund Balance 112 123 Numeric 12 99999999.99 Signed Field 13 Other Balance 124 135 Numeric 12 99999999.99 Signed Field 14 Replacement Reserve Balance 136 146 Numeric 11 99999999.99 15 Construction Loan Principal Balance 147 158 Numeric 12 99999999.99 Signed Field 16 P&I Account Number 159 168 Character 10 17 P&I Bank ID 169 177 Character 9 18 T&I Account Number 178 187 Character 10 19 T&I Bank ID 188 196 Character 9 20 Replacement Reserve Account Number 197 206 Character 10 21 Replacement Reserve Bank ID 207 215 Character 9 22 Construction Loan Principal Account Number 216 225 Character 10 23 Construction Loan Principal Bank ID 226 234 Character 9 24 Filler 235 246 Character 12 21 Length Remarks RFS Issuer Reporting Technical Specifications Document Field # 25 Field Name Filler Start 247 End Type 255 Character Length Remarks 9 1. Record Type: The letter P will be the first character on each pool record. 2. Pool ID: The Ginnie Mae Pool identifier assigned by Ginnie Mae at pooling to the pool/loan package. Exception Messages • E-RFS100 Pool ID must be specified. • E-RFS102 Pool ID must be 6 characters. • E-RFS103 Pool ID not found for this issuer number. • E-RFS104 Pool ID is associated with another issuer. • E-RFS105 Pool ID is on file but has not been issued yet. • E-RFS106 Pool ID has been terminated. • E-RFS107 Pool ID previously reported as paid-off. • H-RFS109 Pool ID should have loan activity reported for this period. • L-RFS110 Pool ID activity for this period belongs to another issuer. • E-RFS111 Pool ID no activity reported this period. 3. Adjust FIC: A signed field. The amount of adjustment, if any, to the pool FIC for the current Reporting Month. Exception Messages • H-POOL050 FIC Adjustment should be specified when interest rate changed during the reporting period. • E-POOL051 FIC Adjustment must be numeric. • E-POOL052 FIC Adjustment must include a decimal point. • E-POOL053 FIC Adjustment must include a sign in first position. • L-POOL054 FIC Adjustment should equal the difference between the opening and closing Fixed Installment Constant (FIC) for the pool minus the FIC for loans liquidated during the reporting period. 4. Pool FIC: Dollar amount of the Fixed Installment Control for this pool for this reporting period. Exception Messages • E-POOL100 Pool FIC must be specified for amortizing pools. • E-POOL101 Pool FIC must be numeric. • E-POOL103 Pool FIC must include a decimal point. 5. Servicing Fee: Dollar amount of the Servicing Fee as calculated per the Ginnie Mae MBS Guide. If the issuer calculates a Servicing Fee value that is negative, report “zeroes” to RFS. Exception Messages • E-POOL150 Servicing Fee must be specified. • E-POOL151 Servicing Fee must be a positive numeric or zero. • E-POOL152 Servicing Fee must include a decimal point. 22 RFS Issuer Reporting Technical Specifications Document • H-POOL153 Servicing Fee should be within a dollar of calculated servicing fee. 6. Weighted Average Interest Rate: The weighted average interest rate per the Ginnie Mae MBS Guide. The exception message POOL200 below applies to Ginnie Mae II pools and to Ginnie Mae I Manufactured Housing pools. Issuers may provide this value for other pools but will not receive POOL200 if not provided. Exception Messages • E-POOL200 Weighted Average Interest Rate must be specified. • E-POOL201 Weighted Average Interest Rate must be numeric. • C-POOL202 Weighted Average Interest Rate should be greater than Security Interest Rate by between .5 and 1.5 for Ginnie Mae II pools issued prior to July 2003. • C-POOL203 Weighted Average Interest Rate should be greater than Security Interest Rate by between .25 and .75 for Ginnie Mae II pools issued after June 2003. • E-POOL204 Weighted Average Interest Rate must include a decimal point. 7. Net Adjust RPB: A signed field. Adjustment to principal remitted to security holders. (For construction and serial note pools, this value must be zero.). This is a new pool level collection field. Exception Messages • E-POOL300 Net RPB Adjustment must be numeric. • C-POOL301 Net RPB Adjustment should not cause Total Principal Remitted to be negative. • C-POOL302 Net RPB Adjustment should be within tolerance when Loan FIC is adjusted for growing equity. • C-POOL303 Net RPB Adjustment should be within a dollar of FIC Adjustment made for growing equity. • C-POOL304 Net RPB Adjustment should not be less than FIC Adjustment made for growing equity when a curtailment exists. • C-POOL305 Net RPB Adjustment should not be less than Interest Adjustment made for Curtailment when an FIC was also adjusted for growing equity. • C-POOL306 Net RPB Adjustment should not be less than (interest adjustment made for Curtailment) and FIC Adjustment made for growing equity. • E-POOL308 Net RPB Adjustment must include a decimal point. • E-POOL309 Net RPB Adjustment must include a sign in first position. 8. Deferred GPM Interest: Deferred Interest paid holders (GPM only): For GPM pools only, the dollar amount that is attributed to interest previously deferred and added to the principal of each loan that was paid to security holders in the current reporting month. Exception Messages • L-POOL350 Deferred GPM Interest should not be entered for non-GPM pools (GT, GP). • E-POOL351 Deferred GPM Interest must be numeric. • L-POOL352 Deferred GPM Interest should be positive. 23 RFS Issuer Reporting Technical Specifications Document • • L-POOL353 Deferred GPM Interest should be less than sum of Scheduled Principal, Liquidations, and Curtailments. E-POOL354 Deferred GPM Interest must include a decimal point. 9. Serial Note: Serial Notes principal available for distribution to holders. This field is only used for Serial Note pools. The monthly serial notes accounting schedule, Form 1710B is described in Appendix VI-12 of the Ginnie Mae MBS Guide. Exception Messages • L-POOL400 Serial Note should not be entered for non-SN pools. • E-POOL401 Serial Note must be numeric. • L-POOL402 Serial Note should be a multiple of $25,000 when not final installment. • E-POOL404 Serial Note must include a decimal point. 10. Security RPB: The Security remaining unpaid principal dollar amount of this pool as of the end of this reporting period. The current process for Security RPB reporting (initial reporting and corrections through GinnieNET) will continue as-is until further notice. The official Security RPB is to be reported per the current process. Exception Messages • C-POOL450 Security RPB is missing. • E-POOL451 Security RPB must be numeric. • C-POOL452 Security RPB should equal prior month Security Remaining Principal Balance minus (Total Principal or Serial Notes). • C-POOL453 Security RPB should equal prior month Security Remaining Principal Balance plus current months draws for construction loans unless there was a liquidation. • C-POOL454 Security RPB should equal the RPB due to CPTA by 4th business day. • C-POOL455 Security RPB should equal prior month Security Remaining Principal Balance minus Serial Notes for Pool Type SN. • E-POOL456 Security RPB must include a decimal point. • C-POOL457 Security RPB should equal Initial Pool UPB for the reporting period in which it is issued. 11. T&I Escrow Balance: A signed field. The dollar amount of the balance of tax and insurance account applicable to this pool as of the reporting period. Include any funds advanced by the issuer for individual mortgage deficit escrow. Exception Messages • E-POOL500 Tax & Insurance Balance must be specified. • E-POOL501 Tax & Insurance Balance must be numeric. • L-POOL502 Tax & Insurance Balance should not be greater than the Original Principal Amount. • L-POOL503 Tax & Insurance Balance should not equal zero two months in a row. • L-POOL504 Tax & Insurance Balance should not be negative. • E-POOL505 Tax & Insurance Balance must include a sign in first position. 24 RFS Issuer Reporting Technical Specifications Document • E-POOL506 Tax & Insurance Balance must include a decimal point. 12. P&I Fund Balance: A signed field. The dollar amount of the balance in the Principal and Interest account for this pool as of the reporting period. Exception Messages • L-POOL550 Principal & Interest Balance should be specified. • E-POOL551 Principal & Interest Balance must be numeric. • L-POOL552 Principal & Interest Balance should equal (last months fund balance plus Principal and Interest activity this month minus (this months servicing fee and last months cash distribution to holders)). • E-POOL553 Principal & Interest Balance must include a decimal point. • E-POOL554 Principal & Interest Balance must include a sign in first position. 13. Other Balance: A signed field. The dollar amount of the balance of other funds. • E-POOL601 Other Fund Balance must be numeric. • E-POOL602 Other Fund Balance must include a decimal point. • E-POOL603 Other Fund Balance must include a sign in first position. 14. Replacement Reserve Balance: Total dollar amount of all repair and replacement funds applicable to the pool as of the reporting period. Applies to Multifamily only. Exception Messages • L-POOL650 Replacement Reserve Balance should not be entered for a Single Family Pool Type. • E-POOL651 Replacement Reserve Balance must be numeric. • E-POOL652 Replacement Reserve Balance must include a decimal point. 15. Construction Loan Principal Balance: A signed field. The principal portion of the payment collected when construction has not been completed prior to the required commencement of amortization. Exception Messages • L-POOL700 Construction Loan Principal Balance should not be specified for a Single Family Pool Type. • E-POOL701 Construction Loan Principal Balance must be numeric. • E-POOL702 Construction Loan Principal Balance must include a decimal point. • E-POOL703 Construction Loan Principal Balance must include a sign in first position. 16. P& I Account Number: The custodial bank account number holding the principal and interest for this pool. Exception Messages • E-POOL751 P&I Account Number must be specified. 17. P&I Bank ID: The American Bankers Association routing number of the custodial bank where the principal and interest of the pool is held. Exception Messages • L-POOL750 P&I Bank ID should be a valid American Bankers Association 25 RFS Issuer Reporting Technical Specifications Document • routing number. E-POOL752 P&I Bank ID must be specified. 18. T&I Account Number: The custodial bank account number holding the taxes and insurance for this pool. Exception Messages • E-POOL801 T&I Account Number must be specified. 19. T&I Bank ID: The American Bankers Association routing number of the custodial bank where the taxes and insurance of the pool is held. Exception Messages • L-POOL800 T&I Bank ID should be a valid American Bankers Association routing number. • E-POOL802 T&I Bank ID must be specified. 20. Replacement Reserve Account Number: The custodial bank account number holding the repair and replacement fund for this Multifamily pool. 21. Replacement Reserve Bank ID: The American Bankers Association routing number of the custodial bank holding the repair and replacement fund for this Multifamily pool. Exception Messages: • L-POOL850 Replacement Reserve Bank ID should be a valid American Bankers Association routing number. 22. Construction Loan Principal Account Number: The custodial bank account number. 23. Construction Loan Principal Bank ID: The American Bankers Association routing number of the custodial bank. Exception Messages • L-POOL900 Construction Loan Principal Bank ID should be a valid American Bankers Association routing number. 24. Filler: Reserved for future use. 25. Filler: Reserved for future use. 26 RFS Issuer Reporting Technical Specifications Document L - Loan record Field # Field Name Start End Type 1 Record Type 1 1 Character 1 2 Unique Loan ID 2 10 Numeric 9 3 Pool ID 11 16 Character 6 Must be a valid Ginnie Mae pool. 4 Loan Type 17 19 Character 3 FHA, FH1, FMF, RHS, RMF, PIH, VAG, VAV 5 Case Number 20 34 Character 15 6 Issuer Loan ID 35 54 Character 20 7 First Payment Date 55 62 Date 8 MMDDYYYY 8 Loan Maturity Date 63 70 Date 8 MMDDYYYY 9 Loan Interest Rate 71 77 Numeric 7 99.9999 10 Loan OPB 78 90 Numeric 13 9999999999.99 11 Loan FIC 91 101 Numeric 11 99999999.99 12 Last Installment Paid Date 102 109 Date 8 MMDDYYYY 13 In Foreclosure Flag 110 110 Character 1 N or Y (default N) 14 Delinquent Interest 111 121 Numeric 11 99999999.99 15 Delinquent Principal 122 134 Numeric 13 9999999999.99 16 Prepaid Interest 135 145 Numeric 11 99999999.99 17 Prepaid Principal 146 158 Numeric 13 9999999999.99 18 Install Interest 159 169 Numeric 11 99999999.99 19 Install Principal 170 182 Numeric 13 9999999999.99 20 Curtailment 183 195 Numeric 13 9999999999.99 21 Adjust Interest 196 207 Numeric 12 99999999.99 Signed Field 22 Net Adjust UPB 208 221 Numeric 14 9999999999.99 Signed Field 23 Loan UPB 222 235 Numeric 14 9999999999.99 Signed Field 24 Removal Date 236 243 Date 8 MMDDYYYY 25 Removal Reason 244 244 Numeric 1 1, 2, 3, 4, 5, 6 26 Liquidation Interest Due 245 255 Numeric 11 99999999.99 27 Liquidation Principal Remitted 256 268 Numeric 13 9999999999.99 28 Liquidation Principal Balance 269 282 Numeric 14 9999999999.99 Signed Field 27 Length Remarks Constant L – Loan RFS Issuer Reporting Technical Specifications Document Note: Reporting Loans in the loan record: In RFS there is no separate reporting record for liquidations. The loan record is used to report one of two scenarios: a.) active loans or b.) active loans that are being liquidated in the current period. Instructions for reporting active loans: • Report data in fields 1 through 23 • RFS assumes that the loan record represents an active loan as of the end of the reporting period Instructions for reporting active loans that are being liquidated in the current period: • Report data in fields 1 through 28 • Issuer must report a value in Field 25 - Removal Reason. This indicates to RFS that the Issuer is reporting a loan that is being liquidated • In Field 23 - Loan UPB report the amount of the principal balance remaining on the loan after application of the last installment received from the mortgagor 1. Record Type: The letter L will be the first character on each loan record. 2. Unique Loan ID: A number assigned by Ginnie Mae, which uniquely identifies this loan. This is a new loan level collection field. See the appendix to this document, which provides additional Unique Loan ID information. Exception Messages • E-RFS150 Ginnie Mae Unique Loan ID must be specified. • E-RFS151 Ginnie Mae Unique Loan ID must be numeric. • E-RFS152 Ginnie Mae Unique Loan ID could not be found. • E-RFS153 Ginnie Mae Unique Loan ID is assigned to another issuer and a different pool. • E-RFS154 Ginnie Mae Unique Loan ID is assigned to another issuer. • E-RFS155 Ginnie Mae Unique Loan ID belongs to another pool. • E-RFS156 Ginnie Mae Unique Loan ID must not be reported for a previously liquidated loan. 3. Pool ID: The Ginnie Mae Pool identifier assigned by Ginnie Mae at pooling to the pool/loan package. Exception Messages • E-RFS100 Pool ID must be specified. • E-RFS102 Pool ID must be 6 characters. • E-RFS103 Pool ID not found for this issuer number. • E-RFS104 Pool ID is associated with another issuer. • E-RFS105 Pool ID is on file but has not been issued yet. • E-RFS106 Pool ID has been terminated. • E-RFS107 Pool ID previously reported as paid-off. • H-RFS109 Pool ID should have loan activity reported for this period. • L-RFS110 Pool ID activity for this period belongs to another issuer. 28 RFS Issuer Reporting Technical Specifications Document • E-RFS111 Pool ID no activity reported this period. 4. Loan Type: A code, which denotes the government agency, associated with this loan. Exception Messages • E-NOTE050 Loan Type must be specified. • E-NOTE051 Loan Type must be valid. • M-NOTE054 Loan Type RMF should be CL, CS, LS, or PN pool type only. • M-NOTE055 Loan Type FH1 should be pool type MH. • E-NOTE056 Loan Type FMF must be pool type: CL, CS, LM, LS, PL, PN, or RX. • M-NOTE057 Loan Type PIH should be pool type: BD, GA, GD, GP, GT, SF, or SN. • M-NOTE058 Loan Type (FHA, RHS, VAG, or VAV) should be pool type: AF, AQ, AR, AS, AT, AX, BD, FB, FL, FS, FT, GA, GD, GP, GT, JM, QL, RL, SF, SL, SN, TL, or XL. • E-NOTE059 Loan Type must be RMF or FMF for a CL, CS, LS, or PN pool type. 5. Case Number: The Case Number to be reported per Ginnie Mae APM 02-17 (e.g., FHA, RHS, PIH, or VA). It must be the same Case Number that was reported (on the Schedule of Pooled Mortgages) to GinnieNET at the time of pool origination. All Case Numbers must contain 15 character positions. The first character is a zero followed by the two digit state code, then the three-digit country code, and a nine-digit number. Exception Messages • M-NOTE100 Case Number should be specified. • M-NOTE101 Case Number should be numeric. • M-NOTE102 Case Number should be 15 digits long. • M-NOTE103 Case Number should be unique for loan. Another Case Number exists for this pool, address, Unique Loan ID, and Social Security Number. • M-NOTE104 Case Number change is suspended. • M-NOTE110 FHA Case Number 1st two digits should be zeroes. • M-NOTE111 FHA Case Number 3rd through 5th digits should match an FHA field office code. • M-NOTE112 FHA Case Number 12th digit should equal the computed check value. • M-NOTE113 FHA Case Number last 3 digits should match an ADP code for the Section of the Housing Act. • M-MAT001 Case Number for this loan should match the external agency file. • M-NOTE120 VA Case Number 1st three digits should be zeroes. • M-NOTE121 VA Case Number 4th through 7th digits should match VA jurisdiction/origin codes. • M-NOTE123 VA Case Number 8th digit should match a VA loan type. • M-NOTE130 RHS Case Number 1st digit should be zero. • M-NOTE131 RHS Case Number 2nd through 6th digits should match a state/county code. • M-NOTE140 PIH Case Number 1st six digits should be zeroes. • M-NOTE141 PIH Case Number 7th through 9th digits should match an area code. 29 RFS Issuer Reporting Technical Specifications Document • • • M-NOTE150 FHA Title 1 Case Number 1st three digits should be zeroes. M-NOTE160 FHA Multifamily Case Number 1st seven digits should be zeroes. M-NOTE161 FHA Multifamily Case Number 8th through 10th digits should match an FHA field office code. 6. Issuer Loan ID: The number assigned by the issuer to uniquely identify the loan to their internal system. Exception Messages • E-NOTE200 Issuer Loan ID must be specified. • L-NOTE201 Issuer Loan ID should be a unique id for this issuer number. 7. First Payment Date: The date in which the first monthly installment payment was due in accordance with the mortgage/note. Exception Messages • E-NOTE250 First Payment Date must be specified. • E-NOTE251 First Payment Date must be a valid year, month and day. • E-NOTE252 First Payment Date must be in MMDDYYYY format e.g. 01012006. • H-NOTE253 First Payment Date should not be more than one month after issue date for Single Family loans. • H-NOTE254 First Payment Date should match calculated value based on Original Principal Amount, Loan Interest Rate, Loan FIC, and Loan Maturity and Pool Type is SF. 8. Loan Maturity Date: The maturity date of this loan in accordance with mortgage/note. Exception Messages • E-NOTE300 Loan Maturity Date must be specified. • E-NOTE301 Loan Maturity Date must be a valid month. • E-NOTE302 Loan Maturity Date must be a valid day of the month. • E-NOTE303 Loan Maturity Date must be in MMDDYYYY format e.g. 01152036. • H-NOTE304 Loan Maturity Date should be after First Payment Date. • H-NOTE305 Loan Maturity Date should not be more than one month greater than the Pool Maturity Date. • M-MAT005 Loan Maturity Date should match the external agency file. 9. Loan Interest Rate: The interest rate of the loan. Exception Messages • E-NOTE350 Loan Interest Rate must be specified. • E-NOTE351 Loan Interest Rate must be numeric. • H-NOTE352 Loan Interest Rate should be greater than zero. • H-NOTE353 Loan Interest Rate should be greater than Security Interest Rate by between .5 and 1.5 for Ginnie Mae II pools except MH issued prior to July 2003. • H-NOTE354 Loan Interest Rate should be greater than Security Interest Rate by between .25 and .75 for Ginnie Mae II pools except MH issued after June 2003. • L-NOTE355 Loan Interest Rate should be the same as other loans in Ginnie Mae I pool except MH. 30 RFS Issuer Reporting Technical Specifications Document • • • E-NOTE356 Loan Interest Rate must include a decimal point. M-NOTE357 Loan Interest Rate change is suspended. M-MAT003 Loan Interest Rate should match the external agency file. 10. Loan OPB: Original Principal Balance, the dollar amount of the original loan principal balance as stated on the mortgage note. Exception Messages • E-NOTE450 Original Principal Amount must be specified. • E-NOTE451 Original Principal Amount must be numeric. • H-NOTE452 Original Principal Amount should be greater than zero. • M-NOTE453 Original Principal Amount should be within 50 dollars of calculated value based on Loan Interest Rate, Loan FIC, and loan duration. • M-MAT002 Original Principal Amount for this loan should match the external agency file. • M-NOTE455 Original Principal Amount change is suspended. • E-NOTE456 Original Principal Amount must include a decimal point. 11. Loan FIC: The current fixed installment constant of principal and interest payments for this loan. Exception Messages • C-NOTE400 Loan FIC should be specified except CL and CS pools. • C-NOTE401 Loan FIC should be blank for construction loan. • E-NOTE402 Loan FIC must be numeric. • C-NOTE403 Loan FIC should be greater than zero for amortized project loan. • E-NOTE405 Loan FIC must include a decimal point. 12. Last Installment Paid Date: The loan amortization schedule date of the last installment payment received. If the borrower has not made any payment to the loan and if there is no Last Installment Paid Date, do not report a value in this field (report blank in this field). Exception Messages • H-LOAN100 Last Installment Paid Date should be specified. • E-LOAN101 Last Installment Paid Date must be a valid year and month. • E-LOAN102 Last Installment Paid Date must be in MMDDYYYY format e.g. 07012007. • H-LOAN103 Last Installment Paid Date should be greater than or equal to First Payment Date for Single Family loans. • H-LOAN104 Last Installment Paid Date should not be after Loan Maturity Date. 13. In Foreclosure Flag: A flag that indicates whether or not this loan is in foreclosure. Exception Messages • E-LOAN700 In Foreclosure Flag must be either N or Y. • L-LOAN701 In Foreclosure Flag should not be Y for non-delinquent loan. 14. Delinquent Interest: The total interest portions of delinquent installments due for this loan. This is the interest portion of unpaid installments that are delinquent (or in 31 RFS Issuer Report