SBC Connect - Delay of Dissolution

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

**Background:**

New policy has been adopted which governs how the new Delay of Dissolution filing will work. It was determined that existing functionality was not in alignment with legislation. Specifically affected by the new policy are that CRA users and anyone not directly associated with the company can no longer perform a Delay of Dissolution filing. Currently in COLIN Delay of Dissolution can be filed by unauthenticated anonymous users who don't have any association with the company.

CRA requests for a Delay of Dissolution will be served by email requests to the business unit who will then apply a Delay of Dissolution in such a way that no filing is recorded for the company. This will entail directly modifying the applicable trigger date for the next step in the process (D1->D2, or D2-> Historical).

All old/previous requirements put together for Delay of Dissolution should be regarded as no longer valid.

**Requirements:**

Nature of Filing - 1) corp user, 2) staff user and 3) staff user for CRA (different rules apply to each)

No Future Effective Dated option

Court Order and Plan of Arrangement may apply

No Ledger Comment needed (Business decision - change from COLIN functionality)

**Entry conditions:**
- Corp must not be frozen
- Corp is currently in the Dissolution process (in D1 or D2)
- All types of corporation are valid. XPROs will be added in future

**Rules:**

_*2 filings for public users - this relates to the number of times a user associated with a corp can perform Delay of Dissolution filings within a single instance of the corp being involved in the Dissolution process. If a company is in Dissolution and files for a Delay twice, if they subsequently return to good standing and exit the Dissolution process, then if they subsequently enter the Dissolution process any previous Delay filings related to the prior Dissolution process do not count to that limit of 2 filings.
_

Current filing in COLIN includes adding a ledger comment. Business has confirmed this is not required in new filing.

**Applying Delays:**

The Delay applied by this filing should apply to the current phase of the process that the corp is in (D1 or D2), i.e. it extends the trigger date for the next stage (to D2 or to HIS).

Delay (e.g. 6 months) should be added to date interval for next trigger date. If next trigger date for next stage is 10 days in the future, apply the delay will mean trigger date is now 6 months + 10 days in the future.
- See Miro board for examples

**Useability:**

When allowing user to select length of duration (for staff) or confirming length of delay of 6 months (for public users), Screen should display to user: [Janis/Jacqueline to review & confirm if these should be displayed to corp users]
- Date of entry into Dissolution process
- Current phase of process (D1 or D2)
- Current date for move to next phase (trigger date for D2 or HIS as applicable)
-- if in D1, also display current projected date for move from D2->HIS

Once user has selected an option for the Delay to be added, display:
- New date for move to next phase (trigger date for D2 or HIS as applicable)
-- if in D1, also display new projected date for move from D2->HIS

**Staff Filing on Behalf of CRA:**

- No filing is to be recorded for CRA requested Delays
- Direct DB update
LEAR Fields are BATCH_PROCESSING.TRIGGER_DATE when STEP = WARNING_LEVEL_1 or WARNING_LEVEL_2
- No outputs
- No notifications
- No record on ledger

More info on Miro board -https://miro.com/app/board/uXjVK34YjMo=/