New URLA Forms and Features
Please note that these release notes are for Encompass Banker Edition only. Some forms and features described here may not be available in Encompass Broker Edition.
Encompass 20.2 Major Release
November 2020
(Added on 10/30/2020)
Use the Fannie Mae Additional Data form to record information required when submitting a loan to Fannie Mae. This form replaces the FNMA Streamlined 1003 for loans using the new 2020 URLA forms: the Fannie Mae Additional Data form displays when a loan is using the 2020 URLA forms; the FNMA Streamlined 1003 displays for loans using the 2009 URLA forms.
Much of the information on the form is populated with data entered on the loan application and other loan forms. This form includes an introductory section with information describing the amortization type, the mortgage owner, and the down payment, as well as sections for the following information, as shown below:
-
Fannie Mae Additional Data
-
MORNETPlus Community Lending
-
FHA Loan Data
-
VA Loan Data
-
Value Verify
CBIZ-29465
Encompass LO Connect 20.1 July Service Pack
August 1, 2020
New pages have been added to Encompass LO Connect to enable loan officers to enter information for loans using the new URLA 2020 output forms. The updates include:
-
New pages for entering information for the URLA 2020 version of the 1003 URLA application output form.
-
New pages for entering verification records for URLA 2020 loans.
-
An updated user interface to enable user to switch between the 2009 or 2020 versions of the URLA forms.
For detailed information, refer to the Encompass LO Connect 20.1 July Service Pack release notes.
Encompass 19.3 Major Release
July, 2019
Support for New URLA
(Updated on 4/16/2020)
A new redesigned version of the Uniform Residential Loan Application (URLA), also known as the Fannie Mae 1003 or the Freddie Mac Form 65, is replacing the 2009 version of the URLA effective January 1, 2021. The redesigned URLA makes it easier for lenders to collect information required by the Home Mortgage Disclosure Act (HMDA) and to incorporate additional application information identified under the URLA/ULAD initiative. The redesigned URLA will temporarily use Fannie Mae's ULAD Specification (FNMA MISMO 3.4 AUS Specification) as the exchange format until the ILAD (Industry Loan Application Dataset) becomes widely available for the industry.
Encompass 19.3 (and later) supports the concurrent use of both the current URLA forms and the new URLA forms. Authorized Encompass users can access the new URLA Form Version option in the Forms menu at the top of a loan file to toggle between the current URLA input forms (URLA 2009) and the new URLA input forms (URLA 2020). Administrators can control which users have access to this new option by managing the Change URLA Form Version option in Encompass Settings > Personas.
The new output form has a similar look and feel to the Loan Estimate and Closing Disclosure forms implemented in 2015 and was designed to provide a better experience for borrowers by providing clear instructions in language that is easy to understand, tailored to each borrower’s financial situation. A sample page is shown below.
The new URLA output form is dynamically generated based on the loan scenario and borrower financial situation. The length of the printed or electronically disclosed URLA output form can vary based on the number of borrowers, and the number of individual assets, liabilities, and income sources each borrower declares on their application. Information that does not apply to a borrower’s situation can be excluded from the output form and additional entries for assets and liabilities can be added.
The dynamically generated content on the output form no longer has a one-to-one relationship with the 1003 URLA input forms. For example, with the URLA 2009 version of the form the 1003 Page 1 input form always printed on page 1 of the output form. With the URLA 2020 version of the input forms, the content entered on each of the input forms can spread across multiple pages of the output form depending on how much information has been entered. Some sections on the form are expandable to include as many as 99 distinct records for entries such as assets, liabilities, or employment records. Other sections can be excluded from the output form when the information does not contain relevant information for a borrower or co-borrower through use of section-level “Does Not Apply” indicators. As a result, the number of pages in the output form and the content that displays on each page can vary from loan to loan based on the entries and selections made for the loan.
To accommodate the changes required by the redesigned URLA output form, the following six input forms are available to use beginning with the Encompass 19.3 release. Encompass will continue to support both the URLA 2020 version of the forms and the 2009 URLA versions used in previous Encompass versions.
- Six new URLA input forms for collecting application data:
1003 URLA Part 1 – Captures personal information about the borrower, including the borrower’s name, marital status, dependents, contact information, addresses, military service, and language preference.
1003 URLA Part 2 – Captures all required borrower income, including employment, self-employment, and other income.
1003 URLA Part 3 – Captures different types of assets and liabilities for the borrower, co-borrower, or both.
1003 URLA Part 4 – Captures Loan and Property Information, Declarations, Demographic Information, and Loan Originator Information. Provides access to the Acknowledgements and Agreements.
1003 URLA – Lender – Captures information that is populated to the URLA output form if the lender opts to include the Lender Loan Information section in the borrower package. Most of the information on this form is populated from other input forms, calculations, or templates.
- 1003 URLA Continuation – Captures additional information for the borrower or co-borrower that displays on the Universal Residential Loan – Continuation Sheet output form.
Some content on the continuation form is dynamically generated on the output form, for example, state-specific Language and any explanation text entered for borrower declarations that are marked for printing on the form
- To accommodate the areas that now allow multiple entries, new and existing verification input forms are being used to add records for employment and income, other income, assets, liabilities, real estate owned, existing mortgages, and gifts and grants that are dynamically added when generating the URLA 2020 output forms. As many as 99 entries can now be created and dynamically generated for inclusion on the URLA 2020 output form. A series of pop-up windows enable easy access to the verification records from the URLA 2020 input forms. The way some verification records are categorized has changed with the URLA 2020 version of the forms, and some URLA 2009 entries will be listed under different categories on the URLA 2020 forms.
The existing versions of the input forms continue to display for loans using the current URLA.
The following list provides a high-level summary of features available in Encompass to support the new URLA.
-
New and retired fields– New fields have been added to capture additional information. Fields from the existing input forms that are no longer required do not display on the new input forms. In some cases, these fields (most notably several of the totals fields) have been migrated to the Underwriter Summary tool for the underwriter’s reference.
-
Ability to exclude data from the output form– Sections of the new URLA input forms can be excluded from the output form when information does not apply to a borrower or co-borrower. This is controlled through section-level and borrower-level Does not Apply checkboxes.
-
Borrower information vs additional borrower information– A print option now controls whether details about shared assets and liabilities are included on the output form for both the borrower and co-borrower, or only for the borrower. In both cases, the co-borrower will receive their own copy of the URLA, but the format of the Additional Borrower form will refer to the Borrower Information of the Primary borrower if this format is selected.
-
Loan Identifier Used on Output Form– Lender can configure the URLA output form to use the Loan Number, a Universal Loan Identifier (or a Non-Universal Loan Identifier for loans Partially Exempt from HMDA reporting), or both.
-
Alternate Names– A new pop-up window captures alternate names for each borrower for the vesting documents.
-
Marital Status– A new Marital Status section captures detailed information about each borrower’s marital status. When a borrower is unmarried but in domestic relationships that may involve joint property rights, an Unmarried Addendum is included when the output form is generated.
-
Military Service– Detailed information about military service, including active duty and expiration dates can now be captures for each borrower on all loan applications. This information is no longer limited only to VA loans only.
-
Language Preference– Lenders can now indicate the language in which each borrower prefers to do business. Each borrower can provide their preferred language for doing business, however, this does not represent a guarantee that the lender will be able to honor their preferred language request.
-
Current Employment Income– All borrower employment income is now captured via Verification of Employment entries. checkboxes now enable disclosure of a borrower relationship to parties within the transaction or an ownership share in a business if they are self-employed or a business owner.
-
Military Entitlements– A pop-up window now captures detailed military pay statements for current employment records. Military base pay and other allowances are mapped appropriately to the Base and Other fields in the Verification of Employment record.
-
Loan Imports and Exports– Encompass supports the creation of a new loan file by importing a Fannie Mae (FNMA) formatted MISMO 3.4 XML file. Encompass continues to support the creation of new loans by importing a FNMA 3.2 flat file. Encompass supports the export of loan files into either a FNMA 3.4 XML file or a FNMA 3.2 flat file. Encompass continues to support legacy exports used by partner integrations including MISMO 2.3.1 and 2.6 schemas.
-
Property Address– New fields have been added to capture Street Address, Unit Type, and Unit Number per ULAD data guidelines. for Subject Property, Current, Prior, Mailing, Employer and Loan Originator addresses.
-
Occupancy/Property Use– Encompass continues to identify the property use type as either Primary, Second, or Investment. A new field determines the value to render on the new URLA output form. Support has been added to indicate that the occupancy for a transaction is FHA Secondary Residence.
-
Other Property Information– New fields have been added to record whether the subject property is going to be used as a mixed-use property or if the subject property is a manufactured home.
-
Rental income on Property Being Purchased– New fields have been added to store gross and net rental income the borrower intends to collect upon purchasing the subject property.
-
Declarations– New explanation fields have been added to enable users to enter additional information for any declaration answered in the affirmative. Users can determine which explanations display on the new URLA continuation input form.
-
Demographic Information – Encompass continues to support existing fields that were introduced to support HMDA data collection requirements in January 2018.
-
Continuation Sheet– Encompass leverages a new continuation input form to display state-specific language, program specific language (e.g. balloon loans) or other information the originator may collect for purposes of including in the output form.
-
Title Information– New fields have been added to store the names in which Title either will be held or is currently held. A combination of new and existing fields is used to store Estate Info, Manner in which Title will be held, Trust Information, and Indian Country Land Tenure.
-
Mortgage Loan information– A combination of new and existing fields are used to store Mortgage Loan Information includes the type of mortgage, loan terms, loan features and proposed payments.
-
Qualifying the Borrower– A combination of new and existing fields are used to store the costs and credits to determine cash to/from borrower at close.
-
Homeownership Education and Housing Counseling Information– New fields have been added to store information about homeownership education and housing counseling that the consumer may have received.
For testing purposes, the new URLA input forms are available beginning with this Encompass 19.3 release. Authorized Encompass users can access the new URLA Form Version option in the Forms menu at the top of the loan file to toggle between 2009 and 2020 versions of the forms.
Encompass administrators can configure the personas who have access to the toggle option by selecting or clearing a new Change URLA Form Version checkbox that has been added to the Personas setting. By default, this checkbox will be cleared for all personas except those who have access to all features.
The recommended best practice is to review personas who have access to all features in Encompass and clear the checkbox for any personas who should not have access to the new forms based on your company practices and policies.
To Configure Access to the URLA 2020 Forms:
-
On the menu bar, click Encompass, and then click Settings.
-
On the left panel, click Company/User Setup, and then click Personas.
-
In the Create a persona section, select a persona.
-
Click the Loan tab.
-
In the Other section, select or clear the Change URLA Form Version checkbox to enable or disable access to the forms.
Encompass users can toggle between the 2009 and 2020 versions of the forms within a loan file by opening the loan file and using the Forms menu at the top of the loan file.
To Switch Between the 2009 and 2020 Versions of the URLA Input Forms:
(Updated on 7/11/2019)
-
Open a loan file and click the Forms menu at the top of the loan file.
-
Point to URLA Form Version, and then click URLA 2009 or URLA 2020.
-
When you select the URLA 2020 option, the new URLA 2020 input forms are visible in Encompass.
NOTE: The ability to toggle between URLA 2009 and URLA 2020 forms is disabled after a Disclosure Tracking Tool entry has been created for a loan.
The enumerated values for URLA 2020 vary from URLA 2009. In some cases, values in URLA 2009 are no longer directly supported in URLA 2020. In these cases, the value is converted to the appropriate URLA 2020 structure with a type of Other and an Other Description set to the 2009 enumerated value. Once the loan is converted, a user can either leave the data as is, or modify it to specific supported URLA 2020 types.
2009 Field | 2020 Location |
---|---|
Div / Interest (field IDs 105 and 114) |
Verification of Additional Income input form The values of fields 105 and 114 remain in the loan file but are not included in total income calculations directly in URLA 2020. The value is added to Other income and included in total income and DTI Calculations |
Vested Interest in Retirement Fund (field ID 212) | Verification of Deposit - Bank will reflect "Converted from 2009" |
Net Worth of Business Owned (field ID 213) | Verification of Other Assets - The Description field is populated with Other. The Other Description field is populated with Net Worth of Business Owned. |
Verification of Deposit | Verification of Deposit OR Verification of Other Assets - Where a value in the VOD has an enumeration that is no longer supported in 2020, it is added to the 2020 application as a Verification of Other Assets record, and the prior VOD record is deleted. This avoids double counting of the asset in the application. |
Automobiles Owned | Verification of Other Assets- If these values exist on a 2009 application, they are converted to a Verification of Other Assets entry. |
Other Assets (221, 223, 1052, 1054) | Verification of Other Assets - The Other Description field is populated with the description from 1003 Page 2 fields. |
Life Insurance (field ID 210) | Verification of Deposit - A record is created with the Cash or Market value set to the Market Value of the Life Insurance. There is no equivalent URLA 2020 field for the Face Amount. |
Alimony / Child Support | Verification of Other Liabilities - A Verification of Other Liabilities entry is created with the Description field populated with Other and the Other Description field populated with Alimony/Child Support. URLA 2020 includes detailed enumerations for both Alimony and Child Support. Review the loan file to determine if these values can be separated and documented. |
Job Related Expense | Verification of Other Liabilities |
Other Expense | Verification of Other Liabilities - A Verification of Other Liabilities entry is created with the Description field populated with Other and the Other Description field populated with the Description from the 1003 P2. |
When your company has completed the testing period and is ready to implement the new URLA, Encompass administrators can use a new Policies option in the Encompass Admin Tools to configure when the new URLA input forms will be applied to all new loans. By default, the option is configured to use the URLA 2020 forms on all loans created on or after February 1, 2020, but administrators can adjust the date based on your company’s policies and practices and guidance from your investors.
Encompass administrators can configure the date when the new URLA 2020 input forms are applied by default for new loan files by adjusting the date in the Default to URLA 2020 Policy setting in the Encompass Admin Tools. Encompass users can toggle between URLA versions prior to the mandated implementation date, for example for testing and rollouts to branch offices.
To Select the Date When the URLA 2020 Input Forms Are Used by Default:
- On your Windows task bar, click the Start menu or Start icon, navigate to the Ellie Mae Encompass program folder, and then click Admin Tools.
- Double-click Settings Manager.
-
If you are prompted to log in to the server, type the User ID, Password, and Server that you use to log in to Encompass as the Admin user.
- Select Policies from the Category list.
- Double-click the date in the Value column for the Default to URLA 2020 option.
- Type the date when you want the URLA 2020 forms to be used by default or click the Calendar icon to select a date.
- Click Apply and then click OK.
The setting does not affect loans started prior to the setting date, and a lender can still toggle between URLA versions as needed after the mandated implementation date based on company policies, for example with non-agency products.
When viewing the Pipeline tab, authorized users can click the Print icon provided there to then locate and print the forms of their choice for all loans that are selected in the Pipeline. In Encompass 19.3, the Print window that displays when a user clicks the Print icon from the Pipeline does not list any of the old 1003 forms, nor any of the new 2020 URLA (1003/65) – All Pages, 2020 URLA (1003/65) – All Pages (Legal), etc. (i.e., new URLA) forms. This change will prevent users from attempting to print old and new URLA forms from the Pipeline. This has been implemented to ensure that users do not run into any issues with printing old URLA forms for loans that are using the new URLA forms and vice versa.
NDE-13239
(Added on 7/11/2019)
To help ensure that Encompass users are aware that the new URLA printed output forms are not permitted to be used to originate loans until an optional use date is announced by Fannie Mae and Freddie Mac (or until February 1, 2020 when the new URLA forms are required on all new loans), a new UNDER REVIEW watermark is now applied to all new URLA printed output forms.
(Added on 6/19/2019)
The URLA 2020 introduces new subject property information fields to the application. These new fields have been added to the Lock Request Form to ensure Encompass captures the data needed to complete the new URLA and remain consistent with its new format.
When the URLA 2020 form version is selected, the following fields are displayed.
To select which version of the URLA to use in the loan file, go to Forms > URLA Form Version.
- Address (field ID 2942) – The address of the subject property. This field is a concatenation of the Street Address (field ID 4516), Unit Type (field ID 4517), and Unit # (field ID 4518).
- This field is read-only.
- If the Street Address, Unit Type, or Unit # is updated, this field will also be updated.
- If Address (field ID 11) is updated, this field is populated with the updated data.
- Street Address (field ID 4516) – Enter the street number and street name only. For example, 123 Elm Street.
- If Address (field ID 11) is updated, this field is populated with the updated data.
- Unit Type (field ID 4517) – Select the type of unit. For example, if you have Suite 1500, select “Suite”.
- If Address (field ID 11) is updated, this field is cleared.
- Unit # (field ID 4518) – Enter the number for a suite, apartment, condo etc. For example, if you have Suite 1500, enter “1500”.
- If Address (field ID 11) is updated, this field is cleared.
- FHA Secondary Residence (field ID 4515) – Indicates whether the subject property qualifies as an FHA secondary residence.
- This field is displayed (but disabled) only when Loan Type (field ID 2952) is “FHA”.
- If this field is displayed, and Loan Type is changed to a value other than “FHA”, the field will be cleared and hidden.
- To enable this field, Property Will Be (field ID 2950) must be “Secondary”.
- If this field is displayed and enabled, and Property Will Be is changed to a value other than “Secondary”, the field will be cleared and disabled.
In addition, these new fields have been added to the Reporting Database.
(Added on 6/19/2019)
The new subject property information fields have been added to the Secondary Registration Current Loan Info tab, the Loan Snapshot, the Lock Request Snapshot, as well as the Lock Confirmation to enable Encompass to capture all the subject property information on the Second Registration tabs.
When the URLA 2020 form version is selected, the following fields are displayed on the tabs and Lock Confirmation.
To select which version of the URLA to use in the loan file, go to Forms > URLA Form Version.
- Current Loan Info tab
- Address (field ID 11) – The address of the subject property. This field is a concatenation of the Street Address (field ID URLA.X73), Unit Type (field ID URLA.X74), and Unit # (field ID URLA.X75).
- This field is read-only.
- If the Street Address, Unit Type, or Unit # is updated, this field will also be updated.
- Street Address (field ID URLA.X73) – Enter the street number and street name only. For example, 123 Elm Street.
- Unit Type (field ID URLA.X74) – Select the type of unit. For example, if you have Suite 1500, select “Suite”.
- Unit # (field ID URLA.X75) – Enter the number for a suite, apartment, condo etc. For example, if you have Suite 1500, enter “1500”.
- FHA Secondary Residence (field ID URLA.X76) – Indicates whether the subject property qualifies as an FHA secondary residence.
- This field is displayed (but disabled) only when Loan Type (field ID 2952) is “FHA”.
- If this field is displayed, and Loan Type is changed to a value other than “FHA”, the field will be cleared and hidden.
- To enable this field, Property Will Be (field ID 2950) must be “Secondary”.
- If this field is displayed and enabled, and Property Will Be is changed to a value other than “Secondary”, the field will be cleared and disabled.
- Loan Snapshot
- Address (field ID LOCKRATE.11) – The address of the subject property. This field is a concatenation of the Street Address (field ID LOCKRATE.URLA.X73), Unit Type (field ID LOCKRATE.URLA.X74), and Unit # (field ID LOCKRATE.URLA.X75).
- Street Address (field ID LOCKRATE.URLA.X73) – The street number and street name only. For example, 123 Elm Street.
- Unit Type (field ID LOCKRATE.URLA.X74) – The type of unit. For example, if you have Suite 1500, then “Suite” is displayed.
- Unit # (field ID LOCKRATE.URLA.X75) – The number for a suite, apartment, condo etc. For example, if you have Suite 1500, then “1500” is displayed.
- FHA Secondary Residence (field ID LOCKRATE.URLA.X76) – Indicates whether the subject property qualifies as an FHA secondary residence.
- Lock Request Snapshot
- Address (field ID LOCKRATE.2942) – The address of the subject property. This field is a concatenation of the Street Address (field ID LOCKRATE.4516), Unit Type (field ID LOCKRATE.4517), and Unit # (field ID LOCKRATE.4518).
- Street Address (field ID LOCKRATE.4516) – The street number and street name only. For example, 123 Elm Street.
- Unit Type (field ID LOCKRATE.4517) – The type of unit. For example, if you have Suite 1500, then “Suite” is displayed.
- Unit # (field ID LOCKRATE.4518) – The number for a suite, apartment, condo etc. For example, if you have Suite 1500, then “1500” is displayed.
- FHA Secondary Residence (field ID LOCKRATE.4515) – Indicates whether the subject property qualifies as an FHA secondary residence.
- Lock Confirmation
- Address (field ID LOCKRATE.2942) – The address of the subject property. This field is a concatenation of the Street Address (field ID LOCKRATE.4516), Unit Type (field ID LOCKRATE.4517), and Unit # (field ID LOCKRATE.4518).
- Street Address (field ID LOCKRATE.4516) – The street number and street name only. For example, 123 Elm Street.
- Unit Type (field ID LOCKRATE.4517) – The type of unit. For example, if you have Suite 1500, then “Suite” is displayed.
- Unit # (field ID LOCKRATE.4518) – The number for a suite, apartment, condo etc. For example, if you have Suite 1500, then “1500” is displayed.
- FHA Secondary Residence (field ID LOCKRATE.4515) – Indicates whether the subject property qualifies as an FHA secondary residence.
(Added on 6/19/2019)
The following mappings and behavior have been added when the URLA 2020 is selected to ensure the subject property information between the Loan Origination forms and the Lock Confirmation is correct.
To select which version of the URLA to use in the loan file, go to Forms > URLA Form Version.
- Any changes to the subject property fields in the loan file updates the corresponding fields on the Lock Request Form.
- Street Address (field ID URLA.X73) maps to Street Address (field ID 4516)
- Unit Type (field ID URLA.X74) maps to Unit Type (field ID 4517)
- Unit Number (field ID URLA.X75) maps to Unit Number (field ID 4518)
- FHA Secondary Residence (field ID URLA.X76) maps to FHA Secondary Residence (field ID 4515)
- The property address fields from the loan file are mapped to the Loan Snapshot before a lock is confirmed.
- Street Address (field ID URLA.X73) maps to Street Address (field ID LOCKRATE.URLA.X73)
- Unit Type (field ID URLA.X74) maps to Unit Type (field ID LOCKRATE.URLA.X74)
- Unit Number (field ID URLA.X75) maps to Unit Number (field ID LOCKRATE.URLA.X75)
- The property address fields from the Lock Request Form are mapped to the Lock Request Snapshot when the lock request is submitted.
- Street Address (field ID 4516) maps to Street Address (field ID LOCKRATE.4516)
- Unit Type (field ID 4517) maps to Unit Type (field ID LOCKRATE.4517)
- Unit Number (field ID 4518) maps to Unit Number (field ID LOCKRATE.4518)
- The property address fields from the Lock Request Form are mapped to the Lock Confirmation after the lock is confirmed.
- Street Address (field ID 4516) maps to Street Address (field ID LOCKRATE.4516)
- Unit Type (field ID 4517) maps to Unit Type (field ID LOCKRATE.4517)
- Unit Number (field ID4518) maps to Unit Number (field ID LOCKRATE.4518)
When a Lock Confirmation (manual or auto lock) is submitted, the subject property information field values are compared between the Lock Request Snapshot and the Loan Origination forms.
- If the property address fields are blank in the Lock Request snapshot, no further action is taken.
- If the FHA Secondary Residence checkbox is blank in the Lock Request snapshot, no further action is taken.
- If the property address field values are the same between the Lock Request snapshot and the Loan Origination forms, no further action is taken.
- If the FHA Secondary Residence checkbox is the same between the Lock Request snapshot and the Loan Origination forms, no further action is taken.
- If the property address field values are different between the Lock Request snapshot and the Loan Origination forms:
- The new property address field values are added to the Field Update pop-up window.
- The new property address field values from the Lock Request Snapshot are posted to the Loan Origination forms.
- Address (field ID LOCKRATE.2942) maps to Address (field ID 11)
- Street Address (field ID LOCKRATE.4516) maps to Street Address (field ID URLA.X73)
- Unit Type (field ID LOCKRATE.4517) maps to Unit Type (field ID URLA.X74)
- Unit Number (field ID LOCKRATE.4518) maps to Unit Number (field ID URLA.X75)
- If the FHA Secondary Residence checkbox is different between the Lock Request snapshot and the Loan Origination forms:
- The FHA Secondary Residence field value is added to the Field Update pop-up window.
- The FHA Secondary Residence field value from the Lock Request Snapshot is posted to the Loan Origination forms.
- FHA Secondary Residence (field ID LOCKRATE.4515) maps to the FHA Residence (field ID URLA.X76)
Encompass Software Development Kit (SDK)
To enable Encompass developers and administrators to access and write code to utilize the new URLA features being introduced in Encompass 19.3, the following updates have been made to the Encompass SDK:
- The following APIs have been added to the SDK for use with the new verification input forms and the repeatable fields used on those forms:
LoanURLAAdditionalLoans (for use with the Verification of Additional Loans input form)
LoanURLAGiftsGrants (for use with the Verification of Gifts and Grants input form)
LoanURLAOtherAssets (for use with the Verification of Other Assets input form)
LoanURLAOtherIncome (for use with the Verification of Other Income Source input form)
LoanURLAOtherLiabilities (for use with the Verification of Other Liability input form)
- Each new URLA repeatable record object has the following functions:
int Count { get; }
int Add();
void RemoveAt(int index);
Sample code: int newIndex = loan.LoanURLAAdditionalLoans.Add();
Additional Resources Now Available
(Updated on 7/16/2019)
-
Encompass Guide to URLA - A comprehensive document covering Encompass administrator setup requirements for the new URLA, a review of each part of the new form (1003 URLA Part 1, 1003 URLA Part 2, etc.), sample workflows, and an appendix of field IDs used on the new URLA pages. In addition, a section-by-section analysis from an operations and administrative perspective of high impact areas in each new URLA part. This guide is available here in the Resource Center.
-
URLA Release Notes - Consolidated release notes devoted solely to new URLA features and requirements in Encompass, Encompass Consumer Connect, and other Ellie Mae products.
-
Encompass Administrator Checklist - Checklist of Encompass administrator settings that the administrator can follow as they review their company configurations and adjust the highlighted settings to support the policies and procedures they use when working with the 1003 URLA. Note that this checklist includes settings available in Encompass Banker Edition only.
Refer to the URLA Support page for more information.
Testing the New URLA in Encompass 19.3
Review the information below for use cases and recommended best practices when testing the new URLA forms and features in Encompass 19.3.
Use Test Cases
- Take and Print Application
-
All loan types supported on URLA 2020 Borrower Pages (Parts 1-4)
-
HELOC applications can leverage borrower application
-
1003 URLA - Lender page supports only Mortgage Types for qualifying the borrower
-
New Verification of Additional Loans functionality for subordinate liens
-
USDA 2009-based pages left intact pending availability of GUS
-
Test applications can be taken in Encompass and Encompass Consumer Connect
-
Persona controls, business rules, Dynamic Data Management and Input Form Builder are available to support new URLA
-
Process contacts using URLA 2020 (Velocify, ECRM)
-
- Import/Export
-
Export FNMA AUS formatted MISMO 3.4 xml
-
Import FNMA AUS formatted MISMO 3.4 xml
-
Best Practices
Persona Controls
-
Limit access to test population and review the persona controls to plan for who will have access to the new URLA
-
Start in your test environment
Loan Files / Toggle
-
Toggling from URLA 2020 to URLA 2009 will not populate old data structures
-
Toggling from URLA 2009 to 2020 will overwrite 2020 fields. Multiple changes and toggles can delete data based on interaction between the two formats
-
Use parallel loan files for parallel testing rather than toggle
Encompass Settings Considerations
-
Review your URLA 2009 data templates and loan program templates for the 1003 URLA Part 4, 1003 URLA – Lender, and 1003 URLA Continuation input forms.
- Consider creating a business rule based on URLA form version. Field 1825 indicates your URLA form version (2009 or 2020).
-
Refer to the 1003 to URLA comparison tab in the DU/LPA MISMO 3.4 ULAD Mapping Guide for fields from the current form as a candidate list to review potentially impacted business rules and forms
-
Catalog business rules that leverage fields with impacts
-
Review your Persona Access to Fields business rules for any loan feature fields that might require additional security.
-
Persona Access to Fields business rules will continue to be applied to existing fields that are carried over to the URLA 2020 input forms.
-
Determine whether any of your products use the affordable loan and payment deferred checkboxes and decide whether you need to implement business rules for those fields.
-
Review and understand the impact of the new and changed options in dropdown lists for verifications and other URLA 2020 form fields. Determine how will this affect your company’s business rules and integrations.
-
Contact
- Stay in touch with the latest announcements on the I ♥ URLA mailing list.
For a full list of operational issues to consider when converting loans to use the URLA 2020 version of the forms, refer to the Encompass Guide to the New URLA in the Resource Center.
Proceed to Feature Enhancements