Skip to content

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

Description

@vikas-gov

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.

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.

Metadata

Metadata

Assignees

Labels

Entities TeamA label to filter on the tickets for the Entities based team that takes care of front end featuresUATThis ticket is to track all UAT feedback from a Story

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions