bcgov / bcgov/entity

Policy - Fee review

Open
#27,424 2 comments 0 reactions 1 assignee Claimed by @mbertucci View on GitHub
Assets MHR On Hold PPR
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

# **Decision Ticket: Secured/Client Party Code Change Fee Policy**

## **Decision Requested**
Should the Registrar continue to charge the **$100 Secured Party Code change fee** when the function is moved from a back‑end FTE process to a feature set (self‑serve) in the Personal Property Registry (PPR)?

## **Background**
Currently, the Personal Property Security Regulation (BC Laws — Fee Schedule) specifies a **$100 fee** for changes to a Secured Party Code, including updates to the name or address associated with that code.

This fee is applied **each time** a secured party code change is filed.

As part of upcoming modernization work, this function will **no longer be completed by a back-end FTE** and will instead be implemented as part of a **feature set within the system**.
A decision is required on whether the fee should remain unchanged, be modified, or be removed once the procedural workflow changes.

_Source: BC Laws — Personal Property Security Regulation, Fee Schedule (https://www.bclaws.gov.bc.ca/)_

## **What are the alternatives?**
1. **Maintain the $100 fee**
- Fee continues to apply per change, consistent with regulation.
2. **Adjust the fee**
- Reduce or restructure the amount to reflect reduced manual effort.
3. **Remove the fee**
- Transition Secured Party Code changes to a no‑fee service, subject to regulatory alignment.

## **Due Date**
- yyyy.mm.dd

## **Raised on Date**
- 2026‑01‑27

## **Accountable**
- *Name of accountable decision maker (e.g., Registrar)*

## **Follow‑up Action to be Taken**
- Confirm regulatory constraints and whether a fee change requires a regulatory amendment.

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.