bcgov / bcgov/entity

BUG - Involuntary Dissolution not handling pre-2004 Restored corps correctly

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

Description

The Involuntary Dissolution job was implemented with these criteria governing entry into the Dissolution process for companies that are required to file a **Post Restoration Transition Application** (_just called Transitiion filing in the new system_) and fail to do so:

image.png

Testing in relation to the data migration has shown that this requirement is incorrect and needs to be corrected.

The new requirement should read:

- An active BC company (incorporated or recognised pre-29 March 2004) that has been Restored but has not filed a Transition within 12 months of the Restoration **and does not already have a Transition filing recorded on their ledger.**

- Eligible Transition filings (with COLIN codes) are:
TRANS Transition a Company
TRANP Transition a Restored Company

What we need to exclude here is the scenario where:
- Pre-2004 corp was required to file a Transition filing
- corp did not file a Transition and was dissolved as a result (or Dissolved for other reasons)
- corp was Restored post 2004
- corp filed a Transition filing
- corp was subsequently Dissolved for any reason
- corp is Restored
--> In this this scenario a corp should never be included in the Dissolution process for not filing a Transition, because they already have one.

link to Miro board with full requirements - https://miro.com/app/board/uXjVKM58-XE=/

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file or test is named. Start by locating the Involuntary Dissolution job and the ledger checks for TRANS and TRANP filings, then review the linked Miro requirements and data-migration context; done means an eligible restored pre-2004 company is excluded when either filing is already recorded.

Written by the indexing model from the issue text.

Assessment

Tech stack
flask, postgres, python
Domain
backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.