TABLE OF CONTENTS
- Document Purpose
- How it Works
- LOS Data Template
- LOS Data Field Mapping
- Data Content Definitions
- Where Does the Information Display in Total Expert
- FAQ
Document Purpose
This document provides a map of data fields needed LOS field mapping to have historical data pulled into the Total Expert (TE) platform. The more information provided or mapped for a historical pull, the more you will be able to take advantage of TE's various features. This document also identifies which data fields are visible in TE and which fields are updatable. TE business-standard process does not allow specific data fields to be updated (for example, lead source or change loan assignment to a different loan officer), so the loan data for import or LOS field mapping must be accurate.
How it Works
TE will provide a LOS field mapping document and a loan import template for flat file import.
For a flat-file import, TE will provide a contact loan import template in import-ready format. TE will need the file back with the column headers intact in the .csv file format. If there are any changes to column headers outside of standard column file headers, the data values will not get imported.
Note
Loan Number is a required field; loan records that do not have a loan number or have a 0 value will not qualify to import.
TE will import the file and run through a de-duplication process within the import file and the database.
For the LOS field mapping, TE will provide a LOS field mapping document, and TE will need it back with Field IDs for the loan information from the LOS system that corresponds with fields in the TE system.
LOS Data Template
The following tables outline TE data fields used for flat-file import and LOS mapping.
Visible in UI – This column identifies which information is visible in the TE user interface (UI). The fields marked Contact Level are data fields stored in the contact record in TE, whereas those kept Yes are stored in the loan record.
Editable – This identifies which data fields can accept updated information. The fields marked not editable will not receive updated data. Once the value is in TE, it will not change.
Note
Editable fields do not overwrite to NULL once they have a value.
Total Expert Fields – These are TE standard field names.
Description – This column has brief information on the expected data. See the Data Content Definitions section for additional details.
Data Type – This column is the expected data type.
Loan Fields
Visible in UI | Editable | Total Expert Fields | Description | Data Type |
No | No | LoanOfficer.external_id Required | Unique identifier for the user | type: varchar, length: 128 |
No | Yes | loan.external_id Required for LOS integration | Unique identifier for the loan | type: varchar, length: 255 |
Yes | Yes | loan_number Required if data is being imported | Loan number | type: varchar, length: 255 |
Yes | Yes | pre_approval_issued | Whether a pre-approval was issued for this loan (0 = No, 1 = Yes) | type: tinyint, length: 1 |
Yes | Yes | is_first_time_buyer | Whether the borrower is a first-time borrower (0 = No, 1 = Yes) | type: tinyint, length: 1 |
Yes | Yes | amount | Amount of the loan | type: decimal, length: 10, decimals: 2 |
Yes | Yes | rate | Loan rate | type: decimal, length: 8, decimals: 5 |
Yes | Yes | term | Loan term (months) | type: int, length: 3 |
Yes | Yes | purchase_price | Purchase price for the loan | type: decimal, length: 10, decimals: 2 |
Yes | Yes | loan_to_value_combined | Combined Loan-to-Value | type: decimal, length: 5, decimals: 2 |
Yes | Yes | loan_to_value | Loan-to-Value | type: decimal, length: 5, decimals: 2 |
Yes | Yes | property_type | Type of property (ex: Single Family) | type: varchar, length: 128 |
Yes | Yes | address_1 | Property address 1 | type: varchar, length: 255 |
Yes | Yes | city | City | type: varchar, length: 255 |
Yes | Yes | state | State | type: varchar, length: 100 |
Yes | Yes | zip | ZIP code | type: int, length: 5 |
Yes | Yes | occupancy | Occupancy type of the property (ex: owner) | type: varchar, length: 32 |
No | Yes | estimated_value | Estimated value of the property | type: decimal, length: 10, decimals: 2 |
Yes | Yes | lock_date | Date the loan was locked | type: datetime |
Yes | Yes | lock_expire_date | Date the loan lock expires | type: datetime |
No | Yes | lock_status | Lock status | type: varchar, length: 32 |
Yes | Yes | appraisal_ordered_date | Date when the appraisal was ordered | type: datetime |
No | Yes | appraisal_expected_date | Date when the appraisal is expected | type: datetime |
Yes | Yes | appraisal_received_date | Date when the appraisal was received | type: datetime |
Yes | Yes | appraised_value | Appraisal value | type: decimal, length: 10, decimals: 2 |
No | Yes | escrow_waived | Whether escrow was waived (0 = No, 1 = Yes) | type: tinyint, length: 1 |
Yes | Yes | referral_source | The source of the referral | type: varchar, length: 64 |
Yes | Yes | application_date | Application date | type: datetime |
No | Yes | processing_start_date_estimated | Estimated processing submission date | type: datetime |
No | Yes | processing_start_date | Date processing began for the loan | type: datetime |
No | Yes | underwriting_submission_date_estimated | Estimated underwriting submission date | type: datetime |
No | Yes | underwriting_submission_date | Date underwriting was submitted | type: datetime |
No | Yes | underwriting_approval_date_estimated | Estimated underwriting approval date | type: datetime |
Yes | Yes | underwriting_approval_date | Date underwriting was approved | type: datetime |
No | Yes | approval_date_estimated | Estimated approval date | type: datetime |
No | Yes | approval_date | Date the loan was approved | type: datetime |
No | Yes | documents_signed_date | Date the documents were signed | type: datetime |
Yes | Yes | funded_date | Date the funds were released | type: datetime |
Yes | Yes | first_payment_date | Date of the first payment for the loan | type: datetime |
No | Yes | closing_date_estimated | Estimated closing date | type: datetime |
Yes | Yes | closing_date | Actual closing date | type: datetime |
Yes | Yes | annual_review_date | Date of annual review for the loan | type: datetime |
Yes | Yes | loan_arm_expiration_date | Date the ARM expires for the loan | type: datetime |
Yes | Yes | created_date | Date the loan was created | type: datetime |
No | Yes | external_last_modified_date | Date the loan was last modified | type: datetime |
No | Yes | lien_position | Order of priority for the loan payment in the event of default | type: varchar, length: 50 |
No | Yes | amort_type | Amortization type | type: varchar, length: 50 |
No | Yes | amort_type_arm_desc | Type of ARM amortization | type: varchar, length: 50 |
No | Yes | resubmittal_date | Date the file is returned to underwriting after rejection | type: datetime |
No | Yes | docs_out_date | Date the documents were sent to borrower & co-borrower | type: datetime |
No | Yes | funds_requested_date | Date funds were requested | type: datetime |
No | Yes | funding_date | Anticipated date funds are to be released | type: datetime |
Yes | Yes | purchased_date | Date purchase occurred | type: datetime |
No | Yes | completion_date | Date mortgage is completed and funds are disbursed | type: datetime |
Yes | Yes | credit_report_date | Credit report date | type: datetime |
No | Yes | credit_report_ordered_date | Credit report order date | type: datetime |
No | Yes | ctc_date | Date the loan becomes clear to close | type: datetime |
No | Yes | loan_date | Date of loan | type: datetime |
Yes | Yes | closing_disclosure_out_date | Date the signed closing documents were issued to the buyer | type: datetime |
Yes | Yes | closing_disclosure_signed_date | Date the signed closing documents were received from the buyer | type: datetime |
No | Yes | county | County containing property | type: varchar, length: 50 |
Yes | Yes | debt_to_income | Debt to income ratio (float value) | type: decimal, length: 5, decimals: 4 |
Yes | Yes | investor | Name of the entity that has purchased this loan on the secondary market | type: varchar, length: 255 |
Yes | Yes | monthly_pi_payment | Dollar amount of monthly payment | type: decimal, length: 10, decimals: 2 |
Yes | Yes | Source | Business Channel | type: varchar, length: 255 |
Yes | Yes | pre_approval_issues | Pre-approval issues | type: text, length: 65,535 |
Yes | Yes | pre_approval_issued_date | Date the pre-approval was issued for the loan. Preferred format: ‘YYYY-MM-DD HH:mm:ss’ | type: datetime |
Yes | Yes | pre_approval_expiration_date | Date the pre-approval for the loan expires | type: datetime |
Yes | Yes | epo_date | Early payoff date for the loan | type: datetime |
No | Yes | audits_date | Date the auditor finished preparing the loan for shipping | type: datetime |
No | Yes | post_closed_date | Date mortgage is completed, and funds are disbursed | type: datetime |
Yes | Yes | buydown_points | Mortgage/discount points applied to the loan | type: decimal, length: 6, decimals: 3 |
Yes | Yes | monthly_pi_with_mi_payment | Dollar amount of monthly payment with mortgage insurance | type: decimal, length: 10, decimals: 2 |
Loan Detail
Visible in UI | Editable | Total Expert Fields | Description | Data Type |
Yes | Yes | program | Program for the loan. Many-to-one relationship, so returned as an object. | type: varchar, length: 100 |
Yes | Yes | purpose | Purpose for the loan. Many-to-one relationship, so returned as an object. | type: varchar, length: 255 |
Yes | Yes | status | Status for the loan. Many-to-one relationship, so returned as an object. | type: varchar, length: 100 |
Yes | Yes | type | Type for the loan. Many-to-one relationship, so returned as an object. | type: varchar, length: 100 |
Borrower Fields
Visible in UI | Editable | Total Expert Fields | Description | Data Type |
Yes | Yes | f_name Required | First name | type: varchar, length: 50 |
Yes | Yes | l_name Required | Last name | type: varchar, length: 50 |
Contact Level | Yes | suffix | Borrower’s suffix, e.g., “Jr.”, “II”, “III”, etc. | type: varchar, length: 128 |
Yes | Yes | email Required | Primary email (valid address only) | type: varchar, length: 254 |
Contact Level | Yes | email_work | Work email | type: varchar, length: 254 |
Contact Level | Yes | address Required | Address line 1 | type: varchar, length: 255 |
Contact Level | Yes | city Required | City | type: varchar, length: 50 |
Contact Level | Yes | state Required | State | type: varchar, length: 2 |
Contact Level | Yes | zip Required | ZIP code | type: varchar, length: 10 |
Yes | Yes | employer | Employer’s name | type: varchar, length: 100 |
Yes | Yes | employer_address | Employer's address line 1 | type: varchar, length: 255 |
Contact Level | Yes | employer_city | Employer's city | type: varchar, length: 255 |
Contact Level | Yes | employer_state | Employer's state | type: varchar, length: 100 |
Contact Level | Yes | employer_zip | Employer's ZIP code | type: int, length: 5 |
Yes | Yes | phone_home Required | Home phone number. Preferred format: ‘(555)555-1234’ | type: varchar, length: 25 |
Yes | Yes | phone_cell Required | Cell phone number. Preferred format: ‘(555)555-1234’ | type: varchar, length: 25 |
Yes | Yes | phone_office Required | Work phone number. Preferred format: ‘(555)555-1234’ | type: varchar, length: 25 |
Yes | Yes | birthday | Borrower’s birthday formatted as a date with 1970 as the year. Preferred format: ‘1970-MM-DD’ | type: date |
Contact Level | Yes | credit_score | Credit score (must be one of: Excellent, Good, Fair, Poor, Very Poor) | type: enum |
Contact Level | Yes | credit_score_date | Credit score date | type: date |
Contact Level | Yes | credit_score_expire_date | Date the credit score expires | type: date |
Contact Level | Yes | referred_by | Referred by | type: varchar, length: 64 |
No | Yes | married | Whether the contact is married (0 = No, 1 = Yes) | type: tinyint, length: 1 |
Co-Borrower Fields
Visible in UI | Editable | Total Expert Fields | Description | Data Type |
Yes | Yes | f_name Required | First name | type: varchar, length: 50 |
Yes | Yes | l_name Required | Last name | type: varchar, length: 50 |
Contact Level | Yes | suffix | Co-borrower’s suffix, e.g., “Jr.”, “II”, “III”, etc. | type: varchar, length: 128 |
Yes | Yes | email Required | Primary email (valid address only) | type: varchar, length: 254 |
Contact Level | Yes | email_work | Work email | type: varchar, length: 254 |
Contact Level | Yes | address Required | Address line 1 | type: varchar, length: 255 |
Contact Level | Yes | city Required | City | type: varchar, length: 50 |
Contact Level | Yes | state Required | State | type: varchar, length: 2 |
Contact Level | Yes | zip Required | ZIP code | type: varchar, length: 10 |
Contact Level | Yes | employer | Employer’s name | type: varchar, length: 100 |
Contact Level | Yes | employer_address | Employer's address line 1 | type: varchar, length: 255 |
Contact Level | Yes | employer_city | Employer's city | type: varchar, length: 255 |
Contact Level | Yes | employer_state | Employer's state | type: varchar, length: 100 |
Contact Level | Yes | employer_zip | Employer's ZIP code | type: int, length: 5 |
Contact Level | Yes | phone_home Required | Home phone number. Preferred format: ‘(555)555-1234’ | type: varchar, length: 25 |
Contact Level | Yes | phone_cell Required | Cell phone number. Preferred format: ‘(555)555-1234’ | type: varchar, length: 25 |
Contact Level | Yes | phone_office Required | Work phone number. Preferred format: ‘(555)555-1234’ | type: varchar, length: 25 |
Yes | Yes | birthday | Coborrower birthday, formatted as a date with 1970 as the year. Preferred format: ‘1970-MM-DD’ | type: date |
Contact Level | Yes | credit_score | Credit score (must be one of: Excellent, Good, Fair, Poor, Very Poor) | type: enum |
Contact Level | Yes | credit_score_date | Credit score date | type: date |
Contact Level | Yes | credit_score_expire_date | Date the credit score expires | type: date |
Contact Level | Yes | relationship | Relationship to borrower | type: varchar, length: 32 |
Contact Level | Yes | referred_by | Referred by | type: varchar, length: 64 |
Contact Level | Yes | married | Whether the contact is married (0 = No, 1 = Yes) | type: tinyint, length: 1 |
Buyer’s Agent Fields
Visible in UI | Editable | Total Expert Fields | Description | Data Type |
Yes | Yes | full_name | Full name | type: varchar, length: 50 |
Yes | Yes | Primary email (valid address only) | type: varchar, length: 254 | |
Yes | Yes | phone_cell | Cell phone number. Preferred format: ‘(555)555-1234’ | type: varchar, length: 25 |
Yes | Yes | phone_office | Work phone number. Preferred format: ‘(555)555-1234’ | type: varchar, length: 25 |
Yes | Yes | employer | Employer’s name | type: varchar, length: 100 |
No | Yes | employer_license_number | The company’s license number | type: varchar, length: 64 |
No | Yes | license_number | The buyer’s agent’s license number | type: varchar, length: 64 |
Contact Level | Yes | email_work | Work email | type: varchar, length: 254 |
Contact Level | Yes | employer_address | Employer's address line 1 | type: varchar, length: 255 |
Contact Level | Yes | employer_city | Employer's city | type: varchar, length: 255 |
Contact Level | Yes | employer_state | Employer's state | type: varchar, length: 2 |
Contact Level | Yes | employer_zip | Employer's state | type: varchar, length: 10 |
Seller’s Agent Fields
Visible in UI | Editable | Total Expert Fields | Description | Data Type |
Yes | Yes | full_name | Full name | type: varchar, length: 50 |
Yes | Yes | Primary email (valid address only) | type: varchar, length: 254 | |
Yes | Yes | phone_cell | Cell phone number. Preferred format: ‘(555)555-1234’ | type: varchar, length: 25 |
Yes | Yes | phone_office | Work phone number. Preferred format: ‘(555)555-1234’ | type: varchar, length: 25 |
Yes | Yes | employer | Employer’s name | type: varchar, length: 100 |
No | Yes | employer_license_number | The company’s license number | type: varchar, length: 64 |
No | Yes | license_number | The seller’s agent’s license number | type: varchar, length: 64 |
Contact Level | Yes | email_work | Work email | type: varchar, length: 254 |
Contact Level | Yes | employer_address | Employer's address line 1 | type: varchar, length: 255 |
Contact Level | Yes | employer_city | Employer's city | type: varchar, length: 255 |
Contact Level | Yes | employer_state | Employer's state | type: varchar, length: 2 |
Contact Level | Yes | employer_zip | Employer's state | type: varchar, length: 10 |
Settlement Agent Fields
Visible in UI | Editable | Total Expert Fields | Description | Data Type |
Yes | Yes | full_name | Full name | type: varchar, length: 50 |
Yes | Yes | Primary email (valid address only) | type: varchar, length: 254 | |
Yes | Yes | phone_cell | Cell phone number. Preferred format: ‘(555)555-1234’ | type: varchar, length: 25 |
Yes | Yes | phone_office | Work phone number. Preferred format: ‘(555)555-1234’ | type: varchar, length: 25 |
Yes | Yes | employer | Employer’s name | type: varchar, length: 100 |
No | Yes | employer_license_number | The company’s license number | type: varchar, length: 64 |
No | Yes | license_number | The settlement agent’s license number | type: varchar, length: 64 |
Contact Level | Yes | email_work | Work email | type: varchar, length: 254 |
Contact Level | Yes | employer_address | Employer's address line 1 | type: varchar, length: 255 |
Contact Level | Yes | employer_city | Employer's city | type: varchar, length: 255 |
Contact Level | Yes | employer_state | Employer's state | type: varchar, length: 2 |
Contact Level | Yes | employer_zip | Employer's state | type: varchar, length: 10 |
Attorney Fields
Visible in UI | Editable | Total Expert Fields | Description | Data Type |
Yes | Yes | full_name | Full name | type: varchar, length: 50 |
Yes | Yes | Primary email (valid address only) | type: varchar, length: 254 | |
Yes | Yes | phone_cell | Cell phone number. Preferred format: ‘(555)555-1234’' | type: varchar, length: 25 |
Yes | Yes | phone_office | Work phone number. Preferred format: ‘(555)555-1234’' | type: varchar, length: 25 |
Yes | Yes | employer | Employer’s name | type: varchar, length: 100 |
No | Yes | employer_license_number | The company’s license number | type: varchar, length: 64 |
No | Yes | license_number | The settlement agent’s license number | type: varchar, length: 64 |
Contact Level | Yes | email_work | Work email | type: varchar, length: 254 |
Contact Level | Yes | employer_address | Employer's address line 1 | type: varchar, length: 255 |
Contact Level | Yes | employer_city | Employer's city | type: varchar, length: 255 |
Contact Level | Yes | employer_state | Employer's state | type: varchar, length: 2 |
Contact Level | Yes | employer_zip | Employer's state | type: varchar, length: 10 |
Contact Groups
Visible in UI | Editable | Total Expert Fields | Description | Data Type |
Contact Level | Yes | borrowerContactGroup_name | Contact group | type: varchar, length: 50 |
Contact Level | Yes | coborrowerContactGroup_name | Contact group | type: varchar, length: 50 |
Data Content Definitions
LoanOfficer / external_id – This field is required field—a unique identifier of the loan officer that owns the contact or loan. The import or API will look for this during the process and tie each contact to a Loan Officer's external ID.
Note
Loan Officer external ID is required for all imports. Records without a Loan Officer external ID or where a Loan Officer external ID does not exist within TE will be skipped.
Warning
Cannot change loan assignment to another user instead a new record of loan will get record and assigned to another loan officer.
Loan / external_id – This field recommended—a unique identifier of the loan. This ID should never change during the lifetime of a loan. If an external ID is blank, the loan number should never change over the lifetime of a loan. If an external ID has a value, the loan number will update within TE if it changes, but the external ID does not change.
Loan / loan_number – This field is required— loan records that do not have a loan number or have a 0 value will not qualify to import.
Loan / pre_approval_issued – Indicates if re-approval was issued for this loan (0 = No, 1 = Yes).
Loan / is_first_time_buyer – Indicates if the borrower is a first-time borrower (0 = No, 1 = Yes).
Loan / amount – The dollar amount of the loan.
Loan / rate – The interest rate of the loan.
Loan / term (Months) – The term of the loan.
Loan / purchase_price – The purchase price for the loan.
Loan / loan_to_value_combined – Percentage ratio of loan amount to purchase price, including all loans on the property.
Loan / loan_to_value – Percentage ratio of loan amount to purchase price.
Loan / property_type – Type of property (for example: Condo or Single Family).
Loan / address_1 – Address 1 of the property.
Loan / city – City of the property.
Loan / state – State of the property.
Loan / zip – ZIP code of the property.
Note
Check business rule within Encompass to update the mailing address for the borrower and co-borrower (if applicable) to the subject property address only when the purchased milestone is complete for the primary residency purchase type. Otherwise, if a user wants to send a mailing, it will go to an obsolete address.
Loan / occupancy – Occupancy type of the property (for example: Owner).
Loan / estimated_value – Estimated value of the property.
Loan / lock_date – Date the loan was locked.
Loan / lock_expire_date – Date the loan lock expires.
Loan / lock_status – Lock status for the loan.
Loan / appraisal_ordered_date – Date when an appraisal of the property was ordered.
Loan / appraisal_expected_date – Date when the appraisal is expected.
Loan / appraisal_received_date – Date when the appraisal was received.
Loan / appraised_value – Appraised value of the property.
Loan / escrow_waived – Indicates whether escrow was waived (0 = No, 1 = Yes).
Loan / referral_source – Source the contact originated from
Loan / application_date – Date of the application for the loan.
Loan / processing_start_date_estimated – Estimated date when the loan process will begin.
Loan / processing_start_date – Date processing began for the loan.
Loan / underwriting_submission_date_estimated – Estimated date when underwriting to assess the eligibility of the loan application will be submitted.
Loan / underwriting_submission_date – Date the file was submitted to underwriting department.
Loan / underwriting_approval_date_estimated – Date underwriting is expected for the loan.
Loan / underwriting_approval_date – Date that underwriting approved the file.
Loan / approval_date_estimated – Estimated date of loan approval.
Loan / approval_date – Date when loan was approved.
Loan / documents_signed_date – Date in which the borrower signed the documents
Loan / funded_date – Date the funds were released.
Loan / first_payment_date – Date of the first payment for the loan.
Loan / closing_date_estimated – Date of the closing for the loan.
Loan / closing_date – Actual close date.
Loan / annual_review_date – Date of annual review for the loan.
Loan / loan_arm_expiration_date – Date the ARM expires for the loan.
Loan / created_date – Date the loan application was created.
Loan / external_last_modified_date – Date the loan record was last modified.
Loan / lien_position – Ordered of priority for the loan payment in the event of default.
Loan / amort_type – Type of loan payments by equal periodic amounts (for example: Fixed or AdjustableRate).
Loan / amort_type_arm_desc – Type of ARM amortization (for example: Construction ARM Pri, 1YWCMT - 10/1 ARM 1)
Loan / resubmittal_date – If a loan is rejected during the underwriting stage and requires additional information from the borrower to proceed. This date indicates when it was resubmitted to underwriting.
Loan / docs_out_date – Date in which documents were sent to the borrower.
Loan / funds_requested_date – Date funds were requested.
Loan / funding_date – Anticipated date funds will be released.
Loan / purchased_date – Date the purchase occurred.
Loan / completion_date – Date the mortgage is completed, and funds are disbursed
Loan / credit_report_date – Date when the credit report was retrieved.
Loan / credit_report_ordered_date – Credit report ordered date
Loan / ctc_date – Clear to close date.
Loan / loan_date – Date on which a loan is made to the borrowers by the lender pursuant to this agreement.
Loan / closing_disclosure_out_date – Date the signed closing documents were issued to the buyer.
Loan / closing_disclosure_signed_date – Date the signed closing documents were received from the buyer.
Loan / county – Property’s county that is used to target refinance.
Loan / debt_to_income – DTI ratio. Decimal – example 40% would be represented as 0.40
Loan / investor – Name of the entity that has purchased this loan on the secondary market
Loan / monthly_pi_payment – Dollar amount of monthly payment
Loan / source – Business Channel
Note
In UI, the source field is displayed as Business Channel.
Loan / pre_approval_issues – Open text to provide information if there is an issue with the pre-approval process.
Loan / pre_approval_issued_date – Date the pre-approval was issued for the loan.
Loan / pre_approval_expiration_date – Date the pre-approval for the loan expires.
Note
Displays in dashboard upon logging to TE loans that will reach expiration date in the next 30 days
Loan / epo_date – Early payoff date for the loan.
Loan / audits_date – Date the internal auditor completed their review and prepared the file for shipping.
Loan / post_closed_date – Date the mortgage is completed, and funds are dispersed.
Loan / buydown_points – Mortgage/discount points applied to the loan
Loan / monthly_pi_with_mi_payment – Dollar amount of monthly payment with MI
Loan / program – Program for the loan. This is a many-to-one relationship, so it is returned as an object of the loan program.
Loan / purpose – Purpose for the loan. This is a many-to-one relationship, so it is returned as an object.
Loan / status – Recommended. Status for the loan. This is a many-to-one relationship, so it is returned as an object.
- It has its journey trigger, allowing for customized management/marketing based on the milestone.
- It is part of every in-line condition to use as criteria for customized management/marketing based on milestones.
- It can trigger an action in an auto campaign.
Note
Loan Status in TE is the crucial mechanism for driving in-process loan communication to consumers and other loan participants. Your loan status in Total Expert should reflect those touchpoints you want to communicate with borrower/co-borrower. With Encompass status, it can often be a custom field that combines various milestones within each status. . In relation to Encompass statuses, it can often be a custom field that Encompass various milestones within each status.
Advantages:
• It has its journey trigger, allowing for customized management/marketing based on the milestone.
• It is part of every in-line condition to use as criteria for customized management/marketing based on milestones.
• It can trigger an action in an auto campaign.
Loan / type – Type for the loan. This is a many-to-one relationship, so it is returned as an object.
Borrower / f_name – This field is required. The borrower’s first name. If there are not distinct first and last names available for any of the contacts associated with a loan, they can be replaced with full_name and they will be split into first and last name automatically by the importer or API.
Borrower / l_name – This field is required. The borrower’s last name. If there are not distinct first and last names available for any of the contacts associated with a loan, they can be replaced with full_name and they will be split into first and last name automatically by the importer or API.
Borrower / suffix – Personal suffix to use in correspondence with the borrower (e.g., “Jr.”, “II”, “III”, etc.).
Borrower / email – This field is required. Borrower’s email address.
Borrower / email_work – Borrower’s work email address.
Borrower / address – This field is required. First line of the borrower’s address.
Borrower / city – This field is required. Borrower’s city.
Borrower / state – This field is required. Borrower’s state.
Borrower / zip – This field is required. Borrower’s ZIP code.
Warning
TE requires a complete physical address. If any part of the address is missing from a record, such as the Zip code, the loan record will not import.
Note
Check business rule within Encompass to update the mailing address for the borrower and co-borrower (if applicable) to the subject property address only when the purchased milestone is complete for the primary residency purchase type. Otherwise, if a user wants to send a mailing, it will go to an obsolete address.
Borrower / employer – Borrower’s employer.
Borrower / employer_address – First line of the borrower’s employer’s address.
Borrower / employer_city – Borrower’s employer’s city.
Borrower / employer_state – Borrower’s employer’s state.
Borrower / employer_zip – Borrower’s employer’s ZIP code.
Borrower / phone_home – This field is required. Borrower’s home phone number. Preferred format: ‘(555)555-1234’
Borrower / phone_cell – This field is required. Borrower’s cell phone number. Preferred format: ‘(555)555-1234’
Borrower / phone_office – This field is required. Borrower’s work phone number. Preferred format: ‘(555)555-1234’
Borrower / birthday – Borrower’s birthday, formatted as a date with 1970 as the year. Preferred format: ‘1970-MM-DD hh:mm:ss’.
Note
Date and time preferred in the format "YYYY-MM-DD hh:mm:ss."
Borrower / credit_score – Borrower’s credit score (must be one of: Excellent, Good, Fair, Poor, Very Poor).
Note
This field requires a custom field. Due to Infosec polices established by Total Expert, we cannot bring in numeric credit scores. However, we have a set up a field that will bring in credit information, but the only option is the categories (Excellent, Good, Fair, Poor, Very Poor).
Borrower / credit_score_date – Date when the credit score was retrieved for the borrower.
Borrower / credit_score_expire_date – Date when the credit score will expire.
Borrower / referred_by – Individual that referred the borrower.
Borrower / married– Whether the borrower is married (0 = No, 1 = Yes).
Co-Borrower / f_name – This field is required. Co-borrower’s first name. If there are not distinct first and last names available for any of the contacts associated with a loan, they can be replaced with full_name and they will be split into first and last name automatically by the importer or API.
Co-Borrower / l_name – This field is required. Co-borrower’s last name. If there are not distinct first and last names available for any of the contacts associated with a loan, they can be replaced with full_name and they will be split into first and last name automatically by the importer or API.
Note
If records only have first and last names without other required fields will be skipped entirely.
Co-Borrower / suffix – Personal suffix to use in correspondence with the co-borrower (e.g., “Jr.”, “II”, “III”, etc.)
Co-Borrower / email – This field is required. Co-borrower’s email address.
Co-Borrower / email_work – Co-borrower’s work email address.
Co-Borrower / address – This field is required. First line of the co-borrower’s address.
Co-Borrower / city – This field is required. Coborrower’s city.
Co-Borrower / state – This field is required. Coborrower’s state.
Co-Borrower / zip – This field is required. Coborrower’s ZIP code.
Note
Check business rule within Encompass to update the mailing address for the borrower and co-borrower (if applicable) to the subject property address only when the purchased milestone finished for primary residency loan. The default address fields in Encompass for borrower and co-borrower do not auto-update to property address.
Co-Borrower / employer – Co-borrower’s employer.
Co-Borrower / employer_address – First line of the co-borrower’s employer’s address.
Co-Borrower / employer_city – Coborrower’s employer’s city.
Co-Borrower / employer_state – Coborrower’s employer’s state.
Co-Borrower / employer_zip – Coborrower’s employer’s ZIP code.
Co-Borrower / phone_home – This field is required. Coborrower’s home phone number. Preferred format: ‘(555)555-1234’
Co-Borrower / phone_cell – This field is required. Coborrower’s cell phone number. Preferred format: ‘(555)555-1234’
Co-Borrower / phone_office – This field is required. Coborrower’s work phone number. Preferred format: ‘(555)555-1234’
Co-Borrower / birthday – Co-borrower’s birthday, formatted as a date with 1970 as the year. Preferred format: ‘1970-MM-DD hh:mm:ss’’.
Note
Date and time preferred in the format "YYYY-MM-DD hh:mm:ss."
Co-Borrower / credit_score – Coborrower’s credit score (must be one of: Excellent, Good, Fair, Poor, Very Poor).
Note
This field requires a custom field. Due to Infosec polices established by Total Expert, we cannot bring in numeric credit scores. However, we have a set up a field that will bring in credit information, but the only option is the categories (Excellent, Good, Fair, Poor, Very Poor).
Co-Borrower / credit_score_date –Date when the credit score was retrieved for the co-borrower.
Co-Borrower / credit_score_expire_date – Date when the credit score will expire.
Co-Borrower / relationship – Co-borrower’s relation to the borrower.
Co-Borrower / referred_by – Individual that referred the borrower.
Co-Borrower / married – Whether the co-borrower is married (0 = No, 1 = Yes).
BuyersAgent /full_name – First & last name of the buyer’s agent. The full_name will split into first and last name automatically by the importer or API.
BuyersAgent / email –Buyer’s agent’s email address.
BuyersAgent / phone_cell – Buyer’s agent’s cell phone number. Preferred format: ‘(555)555-1234’
BuyersAgent / phone_office – Buyer’s agent’s work phone number. Preferred format: ‘(555)555-1234’
BuyersAgent / employer – Buyer’s agent’s employer
BuyersAgent / employer_license_number – Buyer’s agent’s company license number.
BuyersAgent / license_number – Buyer’s agent’s license number.
BuyersAgent / email_work – Buyer agent’s work email address
BuyersAgent / employer_address – First line of buyer agent’s employer’s address.
BuyersAgent / employer_city – Buyer agent’s employer’s city.
BuyersAgent / employer_state – Buyer agent’s employer’s state.
BuyersAgent / employer_zip – Buyer agent’s employer’s zip code.
SellersAgent / full_name – First and last name of seller agent, and full_name can be split into first and last name automatically by the importer or API.
SellersAgent / email – Seller agent’s email address.
Sellers Agent / phone_cell – Seller agent’s cell phone number. Preferred format: ‘(555)555-1234’
SellersAgent / phone_office – Seller agent’s work phone number. Preferred format: ‘(555)555-1234’
SellersAgent / employer – Seller agent’s employer
SellersAgent / employer_license_number – Seller agent’s company license number.
SellersAgent / license_number – Seller agent’s license number.
SellersAgent / email_work – Seller agent’s work email address
SellersAgent / employer_address – First line of seller agent’s employer’s address.
SellersAgent / employer_city – Seller agent’s employer’s city.
SellersAgent / employer_state – Seller agent’s employer’s state.
SellersAgent / employer_zip – Seller agent’s employer’s zip code.
SettlementAgent / full_name – First and last name of settlement agent or Escrow Company, and full_name can be split into first and last name automatically by the importer or API.
SettlementAgent / email – Settlement agent’s email address.
SettlementAgent / phone_cell – Settlement agent’s cell phone number. Preferred format: ‘(555)555-1234’
SettlementAgent / phone_office – Settlement agent’s work phone number. Preferred format: ‘(555)555-1234’
SettlementAgent / employer – Settlement agent’s employer
SettlementAgent / employer_license_number – Settlement agent’s company license number.
SettlementAgent / license_number – Settlement agent’s license number.
SettlementAgent / email_work – Settlement agent’s work email address
SettlementAgent / employer_address – First line of settlement agent’s employer’s address.
SettlementAgent / employer_city – Settlement agent’s employer’s city.
SettlementAgent / employer_state – Settlement agent’s employer’s state.
SettlementAgent / employer_zip – Settlement agent’s employer’s zip code.
Attorney / full_name – First and last name of attorney, and full_name can be split into first and last name automatically by the importer or API.
Attorney / email – Attorney’s email address.
Attorney / phone_cell – Attorney’s cell phone number. Preferred format: ‘(555)555-1234’
Attorney / phone_office – Attorney’s work phone number. Preferred format: ‘(555)555-1234’
Attorney / employer – Attorney’s employer
Attorney / employer_license_number – Attorney’s company license number.
Attorney / license_number – Attorney’s license number.
Attorney / email_work – Attorney’s work email address
Attorney / employer_address – First line of Attorney’s employer’s address.
Attorney / employer_city – Attorney’s employer’s city.
Attorney / employer_state – Attorney’s agent’s employer’s state.
Attorney / employer_zip – Attorney’s employer’s zip code.
ContactGroups – Choose to add or change contact group names if the business does not want to utilize the defaults. The contact group names, by default, are static. By default, TE bundles ContactGroup as follows:
- Client (Borrower & Coborrower)
- Buyer’s Agents
- Seller’s Agents
- Settlement Agents
- Attorney
Note
Additional loan participants such as Processor, LOA, 2nd Buyer’s agent, etc. can be added
Where Does the Information Display in Total Expert
The more data information imported into TE, the more options loan officers will have to market to their customers. For example, auto-campaigns use loan data (such as loan EPO Date, loan lock date, loan underwriting approval date, or loan status).
When viewing a loan details page in TE, all the loan participants (such as borrower, co-borrower, buyer’s agent, seller’s agent, settlement agent, and attorney) will display on the left side. Information for the loan itself (such as loan date, loan term, loan status, and loan amount) appears on the right side.
Loan status / progress |
In the loan view, some information for the buyer’s agent, seller’s agent, settlement agent, and an attorney will be displayed. The contact’s detail view will display additional information for each. |
In the loan view, it displays details of the loan amount, rate, term, purchase price, etc., and loan-related dates (e.g., application date, closing date, funded date, etc.) |
The loan view displays details of the loan property address, appraisal value, etc. Note: External ID is the loan GUID from LOS. |
Loan details (continued). |
Additional information is displayed on the contact’s detail page.
How contacts that opt-out of email appear in UI.
Warning
Users do not have the ability to change the opt-out status manually or provide a contact import file with different status. TE will accept a forwarded message from a loan officer (or another person on behalf of our customer) and re-subscribe to the email address. There must be an email trail showing the contact asked to be re-subscribed. TE will not take a note stating the contact called in asking to be put back on to email lists, nor will TE accept a bulk list to re-subscribe contacts unless appropriate arrangements have been made.
FAQ
Q: How often does TE pull loan data from Encompass?
A: Our default setting is every hour. We can pull loan data every 30 or 15 minutes, but the Product team would like a use case provided when requesting to change the default instance.
Q: When hourly pull runs, how far back does TE pull data from?
A: Periodic pulls always look for "LastModified" DateTime on loans in the last three intervals. If a customer has hourly periodic pulls, each pull looks for any loan modified in the previous 3 hours to have redundancy. For example, suppose the systematic data pull at 1215 UTC would be looking for loans modified after 0915 UTC the same day.
Q: What field does Total Expert look at to identify which loans we pull every hour?
A: We look at the "LastModified" DateTime on loan.
Q: How many loans does TE fetch in each API call?
A: Integer, 1-25000 (EllieMae’s max). Defaults to 1000. Governs how many loans we fetch in each API call.
Q: Can TE schedule a historical pull for a specific date/time?
A: Yes, we can schedule historical pull ahead of time.
Q: Can customers add specific fields such as contact birthday as part of the required fields for contact dedupe?
A: Our standard importer required fields to add a contact listed below. These are part of our de-dupe logic across all customers. We cannot add a specific data field as part of the required fields for one particular customer.
- Contact Must Have:
- First Name & Last Name
- At least one of the following:
- Address (address, city, state, and zip)
- Email address
- Phone Cell
- Phone Home
- Phone Office
Q: If a loan in a synced folder is updated and then moved to a non-sync folder, does it still send the update to TE?
A: No, if a loan gets moved to a folder that we don't have access to, we can't access that loan anymore. If a loan was in "Started" status and it got moved to a folder that we do not have access to the loan status to "Completed," it will still reflect in TE as "Started."
Q: Does changing folders count as an update to the loan/contact and send it to TE?
A: We pull loan data on the "LastModified" DateTime field. For example, we will pull if a modified DateTime stamp gets updated when moving a new loan folder.