IMPORTANT ANNOUNCEMENT REGARDING RSA ROLLOVER TO INTACT
Effective August 2nd, Intact commenced downloading Ontario and Western Canada converted renewals from RSA and Western Assurance. Intact has taken a phased-approach to the RSA conversion. Atlantic Canada, Group Dynamix and Facility will follow at a later date. Our updated version of Power Broker caters to these changes, which has been available on our Website since Friday July 30th.
Included in this release are also updates to support this for Atlantic Canada and Facility. Intact will continue communicating with you directly as dates are confirmed.
We recommend you update Power Broker before you commence download. Website link: https://power-broker.com/faq/power-broker-4-update-instructions/
Please read this announcement in its’ entirety for full disclosure
Intact has not been able to provide valid test data so Power Broker has made programming changes based on the information provided to us in their email correspondence. Unfortunately, no valid test data means we cannot guarantee these changes will work for all RSA incoming download. We are relying on Intact to actually include the Royal Insurance policy information in the data, that they said they will include in their emails. Intact has also promised to communicate with us in the future, so his bad ‘last second’ situation does not happen again.
If the download comes in according to Intact’s email, when you launch the Merge Policy function Power Broker will pull forward the Assign Policy to New Market screen which will allow the user to indicate the correct Intact Company code before proceeding to <save>. This will then associate the existing RSA policy with the newly downloading Intact policy and populate and transact accordingly.
If the information downloads incorrectly (not as outlined in Intacts email correspondence), it will pull the Intact policy in as a ‘new’ policy leaving the RSA policy ‘as-is’. You will need to monitor and update the RSA policy accordingly and verify the download charges hold the correct Insurer Code. If it does not, you will need to <delete> these entries and enter manually or, you can process with the RSA coding (if you are not concerned about accurate reporting) and do a month-end journal entry to correct the payable and receivable GL Codes balances.
NOTE: If the Customer Code is not included in their download, the process will STOP on each incoming ‘new’ record and ask you to search for the associated customer code. Intact has promised us that they will have the existing customer code in place by August 2nd although it was not present on the test cases that they sent us yesterday.
Warning: If download is processed without updating to the new Power Broker release:
The download will pull in as a ‘new’ policy and will not be associated with the existing RSA policy. The Insurer Code will populate based on your entry for IBM416HAL167 / email@example.com in your CSIO Insurance Company Table. This will include your Policy screen and the download charges Print/Post area. If the Insurer Code is incorrect in the downloaded transaction, you will need to <delete> and post the invoice manually after updating the Policy screen with the correct Insurer Code.
NOTE: If the Customer Code is not included in their download, the process will stop on each incoming ‘new’ record and ask you to search for the associated customer code. Intact has promised us that they will have the existing customer code in place by August 2nd although it was not present on the test cases that they sent us yesterday.
For those Brokerages who do NOT currently have INTACT set up in their Insurer Table or CSIO Insurance Table, please contact our Support Department for assistance.