bcgov / bcgov/entity

Continuation Out: Trigger manager approval based on the actual continuation date, not the processing date

Open
#34,667 1 comment 0 reactions 1 assignee Claimed by @forgeuxGH5 View on GitHub
Entities Team UAT
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

**Problem / Need**: What this requirement solves

The current behaviour appears to show an expired-consent warning based on the date staff process the Continuation Out filing. This can require manager approval even when the company continued into the other jurisdiction within the valid consent period but submitted its proof to B.C. after the consent expired.

Business participants clarified that manager approval is intended for cases where the actual continuation date falls outside the authorized consent period, not for records that are merely received or processed late. Applying the warning to late paperwork could create frequent unnecessary approvals and reduce the significance of the manager-approval control.

**Scope**: What’s included, what’s explicitly excluded

**Included**

- Compare the entered actual continuation date against the consent start and expiry dates.
- Require manager approval only where the actual continuation date is outside the consent period.
- Allow staff to process late-submitted proof without manager approval where the company continued out within the valid period.
- Preserve the existing ability to process exceptional cases with the appropriate override.

image.png

**Explicitly excluded**

- Changing the duration of Consent to Continue Out.
- Removing the approval requirement when the actual continuation occurred outside the authorized period.
- Defining the offline management or policy approval procedure.

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.