VERIFY: BN Messaging

[sienna-oldaccountdontuse]

Q:It always takes longer for amalgamation BNs, ask hometeam why?
A: It takes so long because CRA manually reviews each amalgamation and decides which BN should be used. It is not an entirely automated process.

When we write back to COLIN API, the existing BN jobs should cover this. Messaging will be sent out to CRA to generate a new BN for the Amalgama"TED" (new) entity. It will also close the amalgama"TING" entities' BNs.

• Coordinate with David Roberts and home team BAs (Patty), see what needs to be done
• Home team will do some development, might need tweaks from us in the COLIN API.
• Verify it works

[sienna-oldaccountdontuse]

The entities BA can start these conversations.

[Mihai-QuickSilverDev]

1. Good morning Olga,

I’ve touched base with other IT OPS Team members who handle BN messaging, and have further updates.
• The BN Amalgamation Notification message to CRA will be generated through the hub as long as there is a BN on 1 or more of the amalgamating companies
• Everything after that initial notification to CRA is manually handled, both on the CRA side and our side.
o CRA has agents that handle the amalgamation updates, which can take up to 6 months sometimes to sort out
o The IT OPS team checks the BNI (Business Number Index) after 21 days to see if a BN has been assigned by CRA, and if it has, they manually apply it to the successor
So in the case of stacked amalgamations, as long as one of the predecessors has a BN, a message will be triggered to CRA, but in most cases it is the Business Unit letting the IT OPS team know that amalgamations have been completed, and that BNs are needed, that will trigger any manual work to be completed.
Stacked amalgamations will just lengthen the process of CRA completing the amalgamations on their side, and ultimately assigning the successor a BN.

I’m not sure if there is a way to make this more streamlined in the future, but definitely something to consider.
Please let me know if you have any questions.

Darci Denis

2. Good morning Olga,

I’ve had a quick chat with one of our IT OPS team members, and have some initial information for you. I will get more when one of the team members is back from vacation next week.

In the meantime, this is the preliminary information we have for you regarding BN messaging and stacked amalgamations:
• For a straightforward amalgamation it can take a long time months most of the time for an amalgamation BN message to come back from CRA (after our original notification is sent), that queue can get "jumped" if we email the CRA they may process an amalgamation in a matter of days rather then months.
• As for stacked back-to-back amalgamations they usually sit for a while and the IT OPS Team continues checking back to see if things have resolved every few months on the existing tickets we get in the system (error tickets generate automatically in Jira).
• Sometimes (approximately 1 out of 20 times) for whatever reason the cert ID we have wont match even after the amalgamation finishes so IT OPS will message the CRA and send them all the info and company summary we have asking if the cert ID we have is incorrect and normally they reply back that the BN we have is correct and they have updated the Cert ID on the CRA side. Then IT OPS can go ahead and apply the BN using the Administer a Corporation filing in COLIN.
I will let you know if I get any different or additional information from the other IT OPS Team member next week.
Darci Denis

[Mihai-QuickSilverDev]

@OlgaPotiagalova

• As per the comments above, there is an established process for these amalgamations.
• Given the overall amount of work to complete, my recommendation would be that we keep these processes AS-IS.
• Future work would be required, probably part of MVP phase II, to align the BN processes.