search

bcgov / entity

ServiceBC Registry Team working on Legal Entities
Apache License 2.0
23 stars 57 forks source link

Data Sync - BCROS to COLIN - Annual Report #21014

Open NaveenHebbale opened 1 week ago

NaveenHebbale commented 1 week ago
  1. Scenario 1 I found BC1270938, which incorporated as a BC Benefit company in 2020, and then filed their 2021 annual report in COLIN, which of course does not show on their BCROS dashboard, so in BCROS, their ledger shows outstanding AR reports for 2021, 2022 and 2023. Colin State image.png

BCROS State

image.png
  1. Scenario 2

When looking into the Benefit companies being pulled into the involuntary dissolution run, I did a search for Benefit companies and was looking at the last_ar_filed_dt in CPRD. The first one I came across is for BC0894302. This particular entity was a BC limited company that altered to become a benefit company on September 2, 2021. That is the last entry showing on the ledger in COLIN, and the last annual report showing there is the one filed as a limited company was the 2020 AR filed on January 19, 2021. When I look at that entity in BCROS, they have filed their 2021, 2022, and 2023 annual reports, and filed an address change, none of which are showing on the ledger in COLIN, or in the event table in CPRD. That also means that the address change they filed on July 19, 2023 would not have been sent to CRA via BN messaging. See screen shots of the two different views below COLIN state

image.png

BCROS State

image.png
thorwolpert commented 1 week ago

Scenario 1 - is not s sync issue. Business that are in the new Business Registry should be in a locked stated in CPRD, so they should not be able to file an AR. That flow from CPROD -> new Business Registry for COOPS and BENS is not supported, by choice.

Scenario 2 - Involuntary Dissolution runs in CPRD should not affect any locked business, so no COOP or BEN, or any other company moved over to the new Business Registry should be affected.

Both of these scenarios seem to be an issue with data in CPRD and not from an sync issues, unless the decision to manage those in CPRD has changed, and that has a lot of other impacts that would need to be reviewed.