Yes, these can be redacted from the public version.
Questions & Answers
No, RT256 would not be double counted. Outward substitutions should capture outward flows from the pool other than the other defined fields like Warranty Subs (i.e. if the loan no longer meets eligibility criteria but hasn't breached a warranty). So the set of flow items in the pool node should be a complete set and none of the values should be duplicating each other.
Monthly reporting is required for all securities, including those that have a coupon payment frequency greater than one month. The reporting date should be on the monthly anniversary of the regular payment date. For any fields relating to distributions these should be recorded as zeros ("0") if no distribution is set to occur in that reporting period.
A dwelling type which had not been previously occupied would be considered as ‘new’.
If a loan exits the pool then limited fields for that loan must still be reported for the period in which the loan exited the pool. The fields to be reported are: RL001, RL002, RL003, RL004, RL009, RL010, RL012, RL013, RL026, RL049, RL054 and RL055.
The RBA will make an allowance for a small amount of missing data in information providers' reporting. This will be determined case by case.
When a bankruptcy history is not available past 7 years prior to the loan settlement date, the RBA is willing to accept an answer based on 7-year history. In this situation, please mark ‘True’ if a borrower was bankrupt at any point within 7 years prior to the loan settlement date, otherwise indicate ‘False’. If a 7-year history is not available please refer to the 'No Data' policy in the table outlining implementation arrangements.
Please refer to the ‘No Data’ policy in the table outlining implementation arrangements.
When a bankruptcy/ discharge history is not available past 7 years prior to the loan settlement date, the RBA is willing to accept answers based on 7-year history. In this situation, mark ‘N/A’ if none of the borrowers to the loan have recorded a default or bankruptcy within 7 years prior to the loan settlement. If a 7-year history is not available please refer to the ‘No Data’ policy in the table outlining implementation arrangements.
There will be no further changes to the RMBS data requirements ahead of 30 June 2015. If there are any changes to data requirements after this date, industry will be given a minimum of six months lead time to implement any changes.
From 30 June 2015 onwards, the No Data 1 (ND1 – data not collected at origination), No Data 5 (ND5 – Data not applicable) and No Data 6 (ND6 – Data not collected reason being Pending Sale (RL053)) replies will be the only permitted use of ‘No Data’ replies for any missing data. If, after 30 June 2015, a large number of data fields feature ND1 replies, the Bank reserves the right to make the security ineligible for repo.
The ‘No data’ 1 (ND1) option can be used in such a case since the data are not collected at the loan origination and processing stages. Please refer to the ‘No data’ policy in the table outlining implementation arrangements.
If the data are not collected at loan origination, ‘ND1’ would be an acceptable ‘No Data’ response.
If the data are collected at loan origination but are not stored in any electronic system, ‘ND2’ would be an acceptable ‘No Data’ response.
The scheduled balance of a loan can be estimated as long as it is consistent with the description provided by the RBA in the loan-level template.
Even though certain data fields, such as Maturity Date, have a ‘static’ reporting frequency, related data should be amended when there is updated information available.