Keeping your Transaction Closing Dates in synch between apps enables your team to a more accurate insight into performance and helps keep workflow aligned for legal and regulatory processes. Real Synch offers Bots that synch from CRM to Sisu and Bots that synch from Transaction Management Systems (TMS) to Sisu. In either case, the Bots synch two (2) important fields to Sisu: Forecasted Close Date and Closed (Settlement) Date.


Forecasted Closed Date:

When the result of Bot automation is creating or updating a Sisu Transaction, the Bot's workflow is:

  • If CRM or TMS transaction status = not Closed,
  • And if the CRM to 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 Bot automation is creating or updating a Sisu Transaction, the Bot's workflow is:

  • If CRM or TMS transaction status = not Closed,
  • And if the CRM to 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 CRM is synched to the Sisu Settlement (Closing) date field. Additionally, Bots cannot synch to Sisu Transactions which are in a Closed Status.


CRM Closed Date Handling in Sisu

TMS Closed Date Handling in Sisu


Did this answer your question?