Sisu Closed Date Handling
Keeping your Transaction Closing Dates updated between apps enables your team to have a more accurate insight into performance, and helps keep workflow aligned for legal and regulatory processes. Realsynch offers Integrations that integrate from CRM to Sisu, and Integrations that integrate from Transaction Management Systems (TMS) to Sisu. In either case, the Integrations update two (2) important fields to Sisu: Forecasted Close Date and Closed (Settlement) Date.
Forecasted Closed Date:
When the result of Integration automation is creating or updating a Sisu Transaction, the Integration's workflow is:
-
If the CRM or TMS transaction status = not Closed,
-
And if the CRM or TMS Closing Date is in the future,
-
Then fill or update the Forecasted Closed Date field on the related Sisu Transaction using the Closing Date in the CRM or TMS.
Note: the Forecasted Close Date does not control the Transaction's status in Sisu.
Closed (Settlement) Date:
When the result of Integration automation is creating or updating a Sisu Transaction, the Integration's workflow is:
-
If the CRM or TMS transaction status = not Closed,
-
And if the CRM or TMS Closing Date is in the future,
-
Then fill or update the Closed (Settlement) Date field on the related Sisu Transaction using the date specified when the Transaction's status was updated to Closed in the CRM or TMS.
Note: if the Closing date on a CRM transaction is empty, then the date the transaction status was set to Closed in the CRM is integrated into the Sisu Settlement (Closing) date field. Additionally, Integrations cannot update Sisu Transactions which are in a Closed Status.
CRM Closed Date Handling in Sisu
TMS Closed Date Handling in Sisu