bcgov / bcgov/entity

Receivers: Add Receiver Type to Appoint and Cease Receiver Filings and Outputs

Open
#34,792 0 comments 0 reactions 0 assignees View on GitHub
Colin Egress
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

### Description
Policy confirmed that the receiver type must be captured in both the Appoint Receiver and Cease Receiver filings and must also be displayed in the corresponding filing outputs.
Currently, the receiver type is not captured in the equivalent COLIN filing process. Despite the absence of this information in COLIN, the updated business requirement is to include receiver type in the filing workflow and generated outputs for both filing types.
On the Form 7 Section E, the following are listed as receiver types:
- Receiver appointed by the court
- Receiver appointed under an instrument over all or part of the corporation's undertaking
- Receiver manager appointed by the court
- Receiver manager appointed under an instrument over all or part of the corporation's undertaking

The applicant must select one from the options for receiver type
Form 9 only lists Receiver and Receiver manager as receiver types.
### Business Requirement
- Capture receiver type in the Appoint Receiver filing.
- Capture receiver type in the Cease Receiver filing.
- Include receiver type in the generated output for Appoint Receiver filings.
- Include receiver type in the generated output for Cease Receiver filings.

### Business Rules
- Receiver type is mandatory wherever a receiver is appointed or ceased.
- The same receiver type entered in the filing must be reflected in the corresponding output document.
- The requirement applies to both filing submission and output generation.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the Appoint Receiver and Cease Receiver filing workflows and their generated outputs. Check where filing fields are validated, persisted, and rendered, then compare Form 7 Section E's four receiver-type options with Form 9's Receiver and Receiver manager options. Done means both filing types require receiver type and reproduce the selected value in their outputs.

Written by the indexing model from the issue text.

Assessment

Tech stack
flask, javascript, postgres, python
Domain
backend, databases, frontend, full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.