How to Set Up nCino Milestones for Encompass

Description:

Milestones between nCino and Encompass are considered a custom feature. It's good to take note that the milestones between nCino and Encompass may not always read the exact same between the two systems as your company has most likely set up the milestones in nCino to be more Borrower friendly and easier to digest. 

The following steps will show you how to set up the milestones in both Encompass, as well as in nCino, and give a brief explanation of how they will function once set up. 

Setting up loan milestones will need to be a collaborative effort between your Company Admins, and CSM/Support as the settings to add remote names, switch milestone positioning, or update the description/client messages. 

Steps to resolve:

Encompass: 

1. During Implementation, your Implementation specialist should run through the milestone triggers that you would like to set up. 
   • We will briefly run over how this is set up as a refresher in case you need to update the milestone triggers that push to nCino
2. In Encompass go to Settings > Business Rules > Field Triggers > and then find the SimpleNexus/nCino Milestone Triggers. (NOTE - the naming convention may differ depending on your companies general workflow on business rules, but it should be pretty self identifying)
3. Upon opening the business rule, you will be presented with all of the field events that are moving milestones from within the nCino Platform
4. The general workflow of how milestones work is that once an action in Encompass takes place (one of your organizations choosing), this will then push an advanced code over to nCino, and complete the corresponding milestone in the nCino Portal that relates to the completed milestone in Encompass. Here is an example of what the the rule should look like
   • The Activation type is what actually triggers the business rule to activate. This can be through Milestone Completed, a Field Value being modified, or rate lock actions. Most commonly we see either Field Value, or Milestone completed being the main triggers to move the milestone
   • The Trigger milestone is the milestone in Encompass that will then push the advanced code over to nCino. For example if "Approval" is completed inside of Encompass this will then push the advanced code to nCino and complete the milestone with the corresponding "Remote Name"
   • The action type for these business rules will always be "Run advanced code"
   • The advanced code that is used to push the milestone update over to nCino is as follows and will be the same for each milestone trigger - 
     IgnoreValidationErrors
     [CX.SIMPLENEXUS.SEND.PROGRESS] = "RemoteName"
   • The "RemoteName" portion is an identifying factor that is used to push the update over to the corresponding milestone in nCino. Whatever your company would like to use can be entered in between the quotations, however it is best to keep this as close to the milestone that is being completed as possible for easier tracking
   • The RemoteName that you set in the quotes on the business rule MUST match the "Remote name" that we have entered in the nCino Portal. If the remote names do not match, the milestone trigger event will not be completed in nCino and the milestone will not appear to move in the portal

nCino:

Loan Milestones is only accessible by a Company Admin. It is recommended that you review your milestones in Encompass frequently to ensure that they are still behaving as you would like

1. From the "Company Settings" page, either search or find the "Loan Milestones" tile
2. Once you click into it, you will see a list of Milestones showing what Step they are (in sequential order), The name of the milestone in nCino, the Remote Name that is used to trigger the milestone from Encompass, and the Description that is used for the Milestone/Client Messaging
3. The main portion of milestones here is the Remote Name
   • As previously mentioned, the Remote Name is what connects the nCino milestones and Encompass milestones together. The remote name in the business rule will need to reflect the remote name to the milestone you want that to match with inside of nCino
   • For example, the previously shown "Approval" milestone in Encompass has a remote name of "Approval Review Done"
     
     This means that when the "Approval" milestone in Encompass is completed, it will then complete the "Approval" milestone in nCino
4. Once the milestone has been completed in the LOS, as long as everything matches up, the milestone in nCino should then also complete
   • This is shown by filling in a box on the milestone that has been completed on the loan file
   • At this point, the corresponding notifications would be sent to the team members, and borrowers on the loan file

If you end up wanting to make any changes to the way that the milestones trigger from within nCino, the best format is to reach out to the support team with the following information in a table format: 

It would also be extremely helpful to receive a screenshot of what each of your triggers currently looks like to confirm that everything should be triggering as expected: 

Solution:

After understanding how milestones work in nCino Mortgage, you should recognize that milestone updates depend on properly configured field triggers in Encompass, active folder locations, and saved loan files. nCino Mortgage displays milestones based on information sent by the Encompass Plugin, which only communicates when loans are saved in active folders that are configured to send updates.

Additional Things to Note:

It is again important to remember that these Milestones are custom and do not represent a 1:1 between nCino and Encompass. They will function exactly as you set them up on both sides. 

• Milestones in nCino only complete after a "Save" action has been completed on a file that is in a tracked folder through the plugin. If the file has not been saved in Encompass, is in an untracked folder, or has stopped syncing with us for any reason, the milestone will not progress forward. 
• If milestones appear to not be triggering as you'd expect, review the trigger milestone, activation type, and the remote name of the milestones in both Encompass and nCino. Generally the remote name is the culprit so ensure that they both match, and ensure that all of the above step is set up to sync correctly with nCino
• When a milestone is completed in nCino, that Milestone will complete in the loan overview page of the loan file and be represented as a filled in color
  1. The most recent completed milestone on this file was the "Approval" milestone, showing that the loan file is now currently in the "Closing Docs" milestone
  2. From the borrower view this will show that the "Approval" milestone has been completed, and the "Current Step" is "Closing Docs" meaning that the "closing Docs" milestone is the one that is currently being worked on
• Always save loans in Encompass after making changes that should trigger milestone updates.
• Understand your organization's milestone triggers - ask your manager or administrator which fields control milestone changes.
• Check loan folder location before assuming a milestone update should have occurred - loans saved in folder to make the file inactive in nCino Mortgage will not receive milestone updates on those files. Only files that are in a tracked folder and are active in nCino Mortgage will receive milestone updates.
• Document the timeline - note when changes were made and when the loan was saved for troubleshooting purposes.
• nCino Mortgage milestones are controlled by field triggers in Encompass, not by Encompass milestones directly.
• The Encompass Plugin must send updates to nCino Mortgage; nCino Mortgage cannot "pull" milestone information on its own.

Solution:

After understanding how milestones work in nCino Mortgage, you should recognize that milestone updates depend on properly configured field triggers in Encompass, active folder locations, and saved loan files. 

nCino Mortgage displays milestones based on information sent by the Encompass Plugin, which only communicates when loans are saved in active folders that are configured to send updates.

If a milestone appears incorrect, verify that: 

1. The loan was saved after the trigger event occurred,
2. The loan is in an active folder connected to nCino Mortgage,
3. The correct field trigger was activated, 
4. The milestone configuration matches between systems

The vast majority of milestone issues are caused by loans being in inactive folders, not being saved after trigger events, or misunderstanding which field triggers control milestone changes. By following the verification steps outlined in this article and gathering the appropriate documentation, you can quickly identify whether a milestone issue is due to expected system behavior or requires technical support investigation.

Published: 05/04/2026                                            Last Update: 05/04/2026