The “Audit Log” page displays a comprehensive history of the actions taken on the current loan by the borrower, co-borrower, and loan officer.
Table of Contents
Audit Log - Overview
The “Audit Log” allows the user to review the history of the active loan. This history appears as a comprehensive list of actions taken by the borrower, co-borrower, and loan officer throughout the application process.
The “Audit Log” page contains the following sections:
- Title - name of the action performed
- Date Added - date and time the action was performed
- Status - description of the action and the person who performed it
Audit Log Action Index - Added in 6.0.1000
The following table serves as a catalog of the possible actions that may appear on the “Audit Log” page, the conditions that trigger those actions, and their corresponding status messages.
Title |
Trigger(s) |
Status (Message) |
Borrower Converted to NBS |
Selecting the Convert Co-Borrower to NBS checkbox during the Remove Borrower Process |
{Borrower Name} was changed from a Borrower to a Non-Borrowing Spouse by: {Logged in user} |
Loan Status Updated |
Changing the loan status
OR When Old LOS Status is available: Update LOS Data API (api/Loans/LOSData/{loanId}) is called by Vendor (ENVOY or FAM) and MISMO payload resulted in a change in POS: from {oldCVLoanStatus} to {newCVLoanStatus} ; change in LOS from: {oldLOSLoanStatus} to {newLOSLoanStatus}
When Old LOS Status is unavailable: Update LOS Data API (api/Loans/LOSData/{loanId}) is called by Vendor (ENVOY or FAM) and MISMO payload resulted in a change in POS: from {oldCVLoanStatus} to {newCVLoanStatus} ; set in LOS: {newLOSLoanStatus}
OR
Frontend/UI Change: For Purchase loans, when PreApproval/PreQualification letter is generated AND SAVED and current milestone status is different than "PreApproved" status This is a Frontend change [AMAYtoDO: Front End?] |
The Loan Status field has been updated to "{newLoanStatus}", by {submittedByName}
OR
When Old LOS Status is available: "The Loan Status field has been updated in POS: from {oldCVLoanStatus} to {newCVLoanStatus} & updated in LOS from: {oldLOSLoanStatus} to {newLOSLoanStatus}, by {submittedByName}"
When Old LOS Status is unavailable: "The Loan Status field has been updated in POS: from {oldCVLoanStatus} to {newCVLoanStatus} & set in LOS to: {newLOSLoanStatus}, by {submittedByName}"
OR
The Loan Status field has been updated to PreApproved, by {loFullName} |
Fee Modified |
Modifying a fee in the iME and clicking Save |
{Fee Name} has been modified from {previous total fee amount} to {new total fee amount}: Modified by {User First & Last Name} |
Fee Added |
Adding a fee in the iME and clicking Save |
{Fee Name} has been added: Added by {User First & Last Name} |
Fee Deleted |
Deleting a fee in the iME and clicking Save
|
{Fee Name} has been deleted: Deleted by {User First & Last Name} |
Lock Requested |
Clicking the Submit Lock Request button in oPOS (on the “Locking and Adjustments” page) |
{NULL/Post Line of Demarcation}{Forward/Standard} Lock Requested for {finalLoanOfficerRate} % at {finalLoanOfficerPrice} on {productTypeName} ({productCode}) with {lockPeriod} period, by {requestingUser} |
Lock Fulfilled |
Automatic approval of Lock Request
OR
Successful receipt of lock request via postpage |
Lock Fullfilled for {finalLoanOfficerRate} % at {finalLoanOfficerPrice} on {productTypeName} ({productCode}) with {lockPeriod} period, by {requestingUser} |
Submission Process |
Sending a successful submission request to the lender’s LOS, causing the status type to update to ‘Submitted’ |
Submission Status has been changed to: Submitted by {User First and Last Name} |
Submission Process |
Sending a submission request to the lender’s LOS and the request is rejected |
Submission Status has been changed to: Rejected by the lender |
Initial Disclosures Request Process |
Clicking Lender Disclosures or Broker and Lender Disclosures and successfully completing disclosure validation |
{DisclosureType} Request Status has been changed to: Requested by {User First and Last Name} |
Initial Disclosures Request Process |
ACK200 is received from the LOS and ‘DisclosureTracking RequestStatus’ is updated to ‘Received’
|
{DisclosureType} Request Status has been changed to: Received by the System |
Initial Disclosures Request Process |
ACK400 is received from the LOS and ‘DisclosureTracking RequestStatus’ is updated to ‘Error’ |
{DisclosureType} Request Status has been changed to: Error by the System due to an error in the request |
Initial Disclosures Request Process |
ACK500 is received from the LOS and ‘DisclosureTracking RequestStatus’ is updated to ‘Failed’ |
{DisclosureType} Request Status has been changed to: Failed by the System due to a failure in the request |
Initial CD Request Process |
Clicking the Request ICD button (on the “Request ICD” page) |
Initial CD Request Status has been changed to: Requested by {User First and Last Name} |
Initial CD Request Process |
ACK200 is received from the LOS and ‘DisclosureTracking RequestStatus’ is updated to ‘Received’ |
Initial CD Request Status has been changed to: Received by the System |
Initial CD Request Process |
ACK400 is received from the LOS and ‘DisclosureTracking RequestStatus’ is updated to ‘Error’ |
Initial CD Request Status has been changed to: Error by the System due to an error in the request |
Initial CD Request Process |
ACK500 is received from the LOS and ‘DisclosureTracking RequestStatus’ is updated to ‘Failed’ |
Initial CD Request Status has been changed to: Failed by the System due to a failure in the request |
Closing Docs Request Process |
Clicking the Request Closing Documents button (on the “Closing Documents” page) |
Closing Docs Request Status has been changed to: Requested by {User First and Last Name} |
Closing Docs Request Process |
ACK200 is received from the LOS and ‘DisclosureTracking RequestStatus’ is updated to ‘Received’ |
Closing Docs Request Status has been changed to: Received by the System |
Closing Docs Request Process |
ACK400 is received from the LOS and ‘DisclosureTracking RequestStatus’ is updated to ‘Error’
|
Closing Docs Request Status has been changed to: Error by the System due to an error in the request |
Closing Docs Request Process |
ACK500 is received from the LOS and ‘DisclosureTracking RequestStatus’ is updated to ‘Failed’ |
Closing Docs Request Status has been changed to: Failed by the System due to a failure in the request |
Export to LOS Successful |
Successfully importing the loan to the lender’s LOS |
An Export to LOS for Loan # {loanNumber} (Internal Loan # {internalLoanNumber}) with Action: {actionType Description} (Code:{actionType Enum}) has been completed successfully, by System
|
Export to LOS Unsuccessful |
Unsuccessful attempt to export the loan to the lender’s LOS |
If loan number does not exist: LOS export was unsuccessful, for Action: {actionType Description} (Code:{ActionType Enum}) by {userFullName}. (code {errorCode}: {message})
Otherwise: LOS export of loan #{loanNumber}, Internal Loan Number: {internalLoanNumber}, was unsuccessful, for Action: {actionType Description} (Code:{ActionType Enum}) by {userFullName}. (code {errorCode}: {message}) |
Export to LOS Unsuccessful |
Unsuccessful push of MISMO and/or the "CV Proprietary JSON" while exporting a loan to the lender’s LOS |
If loan number does not exist: LOS export was unsuccessful, for Action: {actionType Description} (Code:{actionType Enum}) by {userFullName}. (code {errorCode}: {message})
Otherwise: LOS export of loan #{loanNumber}, Internal Loan Number: {internalLoanNumber}, was unsuccessful, for Action: {actionType Description} (Code:{actionType Enum})by {userFullName}. (code {errorCode}: {message}) |
Get Loan Number Unsuccessful |
Failure to get loan number while exporting a loan to the lender’s LOS |
An Export to LOS for Loan Number was unsuccessful for Action: {actionType Description} (Code:{actionType Enum}) |
Line of Demarcation Set |
Lender’s LOS takes over from Cloudvirga’s iMP as the system of record for the current loan in response to an action taken by a user |
Line of Demarcation has been met with this Action Type Enum {Action Type Enum name and number value} |
Line of Demarcation Rollback |
Reversing the system of record from the lender’s LOS to Cloudvirga’s iMP |
Line of Demarcation has been rolled back. |
LOS Data Sync |
Lender’s LOS performs a sync back of data with Cloudvirga’s iMP |
Sync Back of Loan data from the LOS has been {Successful/Unsuccesful} |
Lock Status Updated |
|
|
Created Loan |
1. Creating a loan in oPOS by clicking New Quote
2. Creating a loan in oPOS by clicking the Purchase or Refinance links located in the +New menu
3. Creating a loan in cPOS (after clicking the first Next button in the loan application) |
|
Created Loan |
Importing a loan via FNM 3.2 file or MISMO |
Created Loan for {Borrower} |
Created Loan |
Creating a new loan by duplicating an existing loan |
Created Loan copied from Loan # {Loan Number} (Internal Loan # {Internal Loan Number}) Borrower {Borrower Name} - Created {Created DateTime}. |
Duplicate Loan Alert Acknowledged |
Opening the loan while related configuration for duplicate loan tracking is enabled
|
Duplicate Loan Alert acknowledged by {loFullName} |
Borrower Login |
Borrower logs into cPOS |
{Borrower/Co-Borrower Name} has successfully logged into the Consumer Portal |
Updated URLA Version Completed |
Converting a loan from URLA Version 2009 to URLA Version 2020 |
Updated URLA Version {conversionStatus} : The loan {updateStatus} from URLA Version 2009 to URLA Version 2020, by {userAccount.FullName} |
Credit Authorization Accepted |
Borrower accepted credit authorization in cPOS
OR
oPOS user accepted credit authorization in oPOS on behalf of the borrower |
Credit Authorization from {Borrower/Co-Borrower Name} received electronically from IP Address {IP Address}. |
Credit Report Retrieved |
Credit Report retrieved from credit vendor |
Credit Report retrieved for {Borrower, Co-Borrower Name}. |
Decision Score Override |
Changing the value of the borrower’s FICO score on the “Shop for Rates” page (oPOS privilege setting) |
Credit decision score updated to {ficoScoreValue} by {loanOfficerName}. |
Homeowner Ins. Updated |
Updating Homeowner’s Insurance amount from any value to $0.00 |
Homeowner Ins. changed from {From Value} to $0.00 by {Username}. |
Property Tax Updated |
Updating Property Tax amount from any value to $0.00
|
Property Tax changed from {From Value} to $0.00 by {Username}. |
Loan Application Date Set |
Cloudvirga’s iMP collects six pieces of RESPA information and Mega Save is performed |
All 6 Pieces of information have been collected for all 1003 Loan Applications and the Loan Application Date has been set. |
1003 Application Completed |
Cloudvirga’s iMP collects six pieces of RESPA information and Mega Save is performed
|
1003 Completed for {Borrower, Co-Borrower} |
Secure Link Sent |
Secure link is sent from oPOS |
{secureLinkType} sent to {recipientNames} by {currentUserName} |
Borrower Re-Added/Borrower Removed |
Selecting the Is your registered spouse or partner going to be on the loan? switch (on the “Personal” page) |
{borrowerFullName} was removed from the loan by: {loanOfficerFullName} OR {borrowerFullName} was re-added to the loan by: {loanOfficerFullName} |
Asset eVerified |
Borrower electronically verifies assets in cPOS |
{borrowerName} electronically verified {financialInstitution} Account ****{accountNumber} |
VOA Report Created |
Verification of Assets report received
|
A Verification of Assets Report for {includeDays} days has been created, by {borrowerName} |
Legal Disclaimer Confirmed |
Borrower confirms legal disclaimer in cPOS |
Legal Disclaimer was confirmed by {Borrower/Co-Borrower Name} from {IP Address} |
Additional Properties Owned |
oPOS user dismisses alert message on Credit tab if the borrower has indicated that they own additional properties |
{userAccount.Party.FullName} dismissed the "additional properties owned" alert message on the credit tab for {borrowerNames}. |
eVOI/eVOE Authorization Accepted |
Running employment verification (eVOI/eVOE) |
eVOI/eVOE Authorization from {borrower.FirstName} {borrower.LastName} received electronically from IP Address {IPAddress}. |
Accepted eConsent |
Borrower or Co-Borrower accepts eConsent in cPOS |
{Borrower/Co-Borrower Name} accepted eConsent from IP Address {IP Address} (received from {LoggedInUser Email Address}) |
Declined eConsent |
Borrower or Co-Borrower declines eConsent in cPOS |
{Borrower/Co-Borrower Name} declined eConsent from IP Address {IP Address} (received from {LoggedInUser Email Address}) |
Appraisal Uploaded |
Appraisal document received from appraisal vendor |
Appraisal Document - {Document Type} uploaded. |
Price Concession Deleted |
Deleting Rate/Price concession in oPOS |
{adjustmentType} Concession for {concessionValue} has been deleted by {LastModifiedBy} for {concessionReason} - {Note} |
Price Concession Requested |
Adding/requesting a price concession adjustment on the “Locking & Adjustments” page |
Price Concession for {concessionValue} has been requested by {LastModifiedBy} for {concessionReason} - {Note} |
Rate Concession Requested |
Adding/requesting a rate concession adjustment on the “Locking & Adjustments” page
|
Rate Concession for {concessionValue} has been requested by {LastModifiedBy} for {concessionReason} - {Note} |
Price Concession Approved |
Approving a price concession adjustment in oPOS |
Price Concession for {concessionValue} has been Approved by {LastModifiedBy} for {Note} |
Rate Concession Approved |
Approving a rate concession adjustment in oPOS
|
Rate Concession for {concessionValue} has been Approved by {LastModifiedBy} for {Note} |
Price Concession Denied |
Denying a price concession adjustment in oPOS
|
Price Concession for {concessionValue} has been Declined by {LastModifiedBy} for {Note} |
Rate Concession Denied |
Denying a rate concession adjustment in oPOS
|
Rate Concession for {concessionValue} has been Declined by {LastModifiedBy} for {Note} |
Rate/Price Concession Deleted |
Deleting a rate or price concession in oPOS |
{adjustmentType} Concession for {concessionValue} has been deleted by {LastModifiedBy} for {concessionReason} - {Note} |
Intent to Proceed Received |
Signing ‘Intent to Proceed’ in cPOS |
Intent to Proceed received from {Borrower/Co-Borrower Name} |
Disclosures Created |
Successful response is received for initial disclosures (Lender Broker, Lender Broker Locked, Initial Locked and In Person as well) |
Loan Estimate and Initial Disclosure Created for {Borrower, Co-Borrower Name} by Vendor |
Assumed Receipt |
1. On post processing logic for ScannedAtfFulFillment pushback (success case)
2. When document status is changed to ‘Sent’ (for example: tracking disclosures triggers, on pushback received when borrowers have e-consent, manual update of the document via mailroom) |
Assumed receipt of Initial Disclosures Package for {Borrower, Co-Borrower Name} is {Expected Date}. |
Initial Disclosures Sent |
1. On post-processing logic for ScannedAtFulFillment pushback (success case)
2. When document status is changed to ‘Sent’ (for example: tracking disclosures triggers, on pushback received when borrowers have e-consent, manual update of the document in mailroom) |
1. Tracking number available: "Loan Estimate and Initial Disclosures sent to {borrowersName} by {response.SendBy}", otherwise:Loan Estimate and Initial Disclosures sent to {borrowersName} by {response.SendBy} package {response.TrackingNumber }";
2. If loan is not opened in mailroom and the status is changed, then message will be: "Loan Estimate and Initial Disclosures sent to {fullNameOfBorrower} {auditLogSentBy}"
If it is opened in mailroom and we have SentByName (if we have record in DisclosureDetails then it's SentBy column (value from Lookup table for that value and keyword ‘sendingmethods’) otherwise DocumentShippingInformation table and BorrowerSentByName column(value from Lookup table for that value and keyword ‘sendingmethods’)) and trackingNumber (if we have record in DisclosureDetails then it's TrackingNumber otherwise DocumentShippingInformation table and TrackingNumber column), then the message will be: "Loan Estimate and Initial Lock Disclosures sent to {fullNameOfBorrower} {auditMessageDetails}"
Otherwise: - Message: "Loan Estimate and Initial Lock Disclosures sent to {fullNameOfBorrower}" |
Tracking Disclosures |
When LOS Setting from System Admin “Disclosure Tracking” is True AND (borrower eConsented/Declined (ONLINE) OR offline) AND one of the following takes place:
1. If disclosure package is in Status "Sent" or "Rejected" AND Save is executed
2. When Sign Initial Disclosures Secure link is sent (ONLINE)
3. When Disclosure Package is uploaded to DocVault AND status of document is set to "Approved" AND Save is executed
4. When Initial Disclosure is Previewed (opened for signing) on cPOS (ONLINE) – update disclosures |
Created tracking record for disclosures in {Lender’s LOS} |
Initial Disclosures Package Signed |
Signing initial disclosure package in cPOS |
Initial Disclosures Package was signed by {borrowerName} electronically |
Initial Disclosures Package Previewed |
Opening initial disclosure package in cPOS |
Initial Disclosures Package was previewed by {borrowerName} electronically |
Assumed Receipt |
#1: On post processing logic for ScannedAtFulFillment pushback (success case)
#2: When document status is changed to Sent (for example: tracking disclosures triggers, on pushback received when borrowers have e-consent, manual update of the document via mailroom) |
Assumed receipt of Initial Disclosures Package for {Borrower, Co-Borrower Name} is {Expected Date}. |
Compliance Check Received |
Compliance check is received |
Compliance Check {ComplianceCheckStatus} |
Compliance Check Requested |
Requesting a compliance check by
|
Compliance Check Requested |
Disclosures Process |
Document status updates to ‘Sent’ |
Document {documentName} for {borrowerName} has been marked as sent by {currentUserFullName} |
Initial Disclosures Sent |
On post-processing logic for Scanned at FulFillment pushback - success case |
If Tracking Number exists: Loan Estimate and Initial Disclosures sent to {borrowersName} by {SendBy} package {TrackingNumber },
Otherwise: Loan Estimate and Initial Disclosures sent to {borrowersName} by {SendBy}. |
Disclosures Detailed Process |
|
1. Disclosure status has been changed to: {disclosureStatus}
2. Document delivery type has been set to {newDocDeliveryType}
3. The LO Signature has been sent in the Disclosure request to the Vendor |
Disclosures Detailed Process |
Resending initial disclosure request to vendor after a failed request |
Disclosure Request has been rerouted to Lender |
Appraisal Requested |
Requesting an appraisal in cPOS
OR
Requesting an appraisal in oPOS |
Appraisal Order requested by {Borrower}
OR
Appraisal Order successfully submitted by {Loan Officer} |
Appraisal Report Package Viewed |
Opening or viewing the appraisal report in cPOS |
Appraisal Report Package was viewed by {BorrowerName} electronically |
Title Express Pass Decision |
Clicking Check Title (on the Property tab or the “Loan Details” page) |
Success response: Express Pass Decision "{clearanceTime}" received for Loan # {loanNumber}, Expiration Date {expirationDate}.
Unsuccessful response: Express Pass Decision | {errorMessage} |
Check Title |
One of the following responses is received from title decisioning:
|
Success response:
<Vendor> - <Product> time to clear: "<DaysToClear> received for Loan #<lender loan number>. Expiration Date <Title Decision Expiration Date>
Unsuccessful response:
<Vendor> - <Product> <error response> |
Loan Number Not Requested |
Running credit in cPOS while required fields are not completed |
Loan Number not requested from LOS as required fields were not completed. |
Disclose in LOS |
Exit workflow rules are met
OR
LO manually clicks Disclose in LOS in oPOS |
Loan has been sent to be Disclosed in LOS by: {userFullName} |
{Lender’s LOS} Template Applied |
Lender’s LOS applies loan template during export process |
{Lender’s LOS} Template {loanTemplateName} has been applied in {Lender’s LOS} successfully, by System |
{Lender’s LOS} Template Not Applied |
Lender’s LOS does not apply loan template during export process |
{Lender’s LOS} Template match not found, Template could not be applied in {Lender’s LOS}, by System |
Export to LOS Not Performed |
LOS wins rules are satisfied during export process |
Data in the LOS was verified as part of export process, and any further changes to this loan application must be made in the LOS |
No Address Export – No License Match |
Exporting loan to lender’s LOS and the loan officer is not licensed in subject property state. |
Export of Loan {loanNumber}, Internal Loan Number: {internalLoanNumber}, Borrower {borrowerFullName} to LOS without Subject Property Address; State License not found in {Lender’s LOS} for assigned Loan Officer {losUserId} |
No Address Export – No State |
Subject property state not provided when exporting to lender’s LOS |
Export of Loan {loanNumber}, Internal Loan Number: {internalLoanNumber}, Borrower {borrowerFullName} to LOS without Subject Property Address; State not available |
No Address Export – User Authorized |
Subject property state not provided when exporting to lender’s LOS, but authorized by the loan officer during the export process. |
Export of Loan {loanNumber}, Internal Loan Number: {internalLoanNumber}, Borrower {borrowerFullName} to LOS without Subject Property Address authorized by user: {username} |
Loan Number Updated (by LOS) |
Loan number is changed during data sync between lender’s LOS and Cloudvirga’s iMP. |
Loan Number has been updated from {Old Loan Number} to {New Loan Number} due to a Loan Number change in the LOS. Internal Loan Number: {Internal Loan Number} |
Loan Officer Reassigned (by LOS) |
Loan officer is changed during data sync between lender’s LOS and Cloudvirga’s iMP.
|
Loan Officer has been reassigned from {Old LO Name} ({Old <Lender‘s LOS> User ID}) to {New LO Name} ({New <Lender’s LOS> User ID}) due to a Loan Officer reassignment in the LOS |
Appraisal Receipt |
Appraisal receipt by the borrower |
{Borrower/Co-Borrower Name} has confirmed receipt of the appraisal. |
External Loan Number Created |
eVOI/eVOE is requested AND external loan ID does not already exist |
Created External Loan Number {externalLoanId} for eVOI/eVOE Service. Internal Loan Number: {InternalLoanNumber} |
PreDisclosures Created |
Response received with document |
PreDisclosures Package was created for {borrower name} <and {coborrower name}> by {logged in user name}. |
PreDisclosures Signed |
Borrower signs predisclosures |
PreDisclosures Package was signed by {borrower name}. |
PreDisclosures Mailed |
Creation of predisclosures package for mail delivery |
PreDisclosures Package was Mailed {pushback date}. |
Summary
The “Audit Log” page displays the entire history of the active loan. From here, the oPOS user can review the actions that have been taken on the loan, the dates and times those actions were performed, and the parties who performed them.
Comments
0 comments
Please sign in to leave a comment.