bcgov / bcgov/entity

SBC Connect - Officers Filing

Open
#28,026 0 comments 0 reactions 0 assignees View on GitHub
Entities Team P
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

> _This issue was auto-created as part of the Zenhub sub-issues migration. The original entity was opened on 2025-02-25. For more details see [this post](https://changelog.zenhub.com/migration-of-epics-projects-to-sub-issues-313645?zenhub_entity_id=Z2lkOi8vcmFwdG9yL1plbmh1YkVwaWMvMjI2Mzk0)._

### Background:
When Benefit companies were implemented in the new system a decision was made not to collect Officer related information as this was only ever Optional information (corps are under no obligation to provide) and was only possible to do via the Annual Report.
This has now changed based on the needs of Registry partners. The new decision is to implement the collection of Officer information on a similar optional basis, but without being tied to the Annual Report filing.

### Scope:
• Applies to BC corps, CCCs, ULCs and BENs plus their Continued In equivalents.
• Information to be collected will remain the same.

- Illustration from COLIN:
image.png

Existing Officer information will be migrated over from COLIN and be available in this new functionality to be built.

### Design Considerations:

- Preference for locating this feature in similar fashion to the Current Directors feature on the Corporate Dashboard (UX/UI team to refine this).
- No filing to be recorded for entering/updating this information (this is optional information not mandated by legislation).
- - Based on Thor's input the best way to implement this may be to implement as a filing that does not show on the Dashboard. This might allow cloning of the code for the Current Directors feature and associated Change of Director filing as a starting point.
- Information to be collected (Officer types) is to be the same as COLIN, but functionality should be built with reuse of code for other Registry applications in mind with minimal changes.
- Design should also allow for changes to list of Officer types in the future.

### Business Rules:
- Allow users to enter or update Officer information at any time with no restrictions.
- Capturing dates of appointment or cessation for Officers is not required, system to record only date of information entry as per COLIN functionality (information captured/displayed is considered 'Snapshot' data not authorative historical record).
- No need for Correction or Amendment functionality, users will be able to update information at any time as needed.
- No record of a "Filing" to appear on corporate ledger.
- o This applies also to partners using APIs to support their own applications.
- Business Summary to show Officer information when present in same manner as in COLIN today.
- No outputs are required for this 'not-a-filing' when making changes.
- No fees are to be charged

### Officer Related Rules:
Officer roles to be supported are:

- CEO
- CFO
- Chair
- Other Office(s)
- Treasurer
- Vice President
- President
- Secretary
- Assistant Secretary

### Rules related to entering or updating Officer information:

- A person may hold more than 1 offices in a company
- The roles that a person holds may change over time
- o E.g. a person who is recorded as "CEO" and "Chair" may be updated to record "CEO" and "President"
- The roles a person holds should be recorded against a single "person record" in the system.
- Companies are not required to record any Officer information and may enter as many persons and offices held as they chose to.
- o Companies that had previously entered Officers may remove them all resulting in no Officers being recorded when there were previously Officers recorded.
- There are no restrictions on how many people a particular role can be recorded against
- o E.g. several people can be recorded as "President"
- Previously entered person names can be changed
- Previously entered persons can be deleted as Officers
- Addresses previously entered can be changed
- Delivery and Mailing addresses are to be captured for each person recorded as an officer (as per Directors functionality)
- o There are no requirements for Officers to have addresses in B.C.

### Dependencies:
Existing COLIN data will be imported into the new system as is and will be displayed in the new Officers functionality and Business Summary exactly the same as data entered in the new system.

Liquidation Report also collects Officer information in the same way as the Annual Report does in COLIN. This filing is planned to be implemented as a backend filing only with data entry performed by Jupyter Notebook or Google Document AI. This filing will be implemented as it exists in COLIN as these requirements represent no fundamental changes to the capture and storage of Officer related information.

Figma details:
https://www.figma.com/design/tYtkdpIMJvPWvrhs06Klil/Change-of-Officer?node-id=11772-88261&p=f&t=eDR3VOGFvdTXFNWW-0

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.