Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MHR - PPR Lien information not updated for Transport Permits and Transfers of Ownership #10936

Closed
PatrickAHeath opened this issue Feb 1, 2022 · 1 comment
Labels

Comments

@PatrickAHeath
Copy link
Contributor

Staff have indicated that they see PPR Lien info against Manufactured Homes when they do Transport Permits or Transfers of Ownership. (using the green screens) With PPR on the new platform and no link between the applications, this information will be out of date and inaccurate.

Here’s what I gathered from a discussion with staff on the matter:
• If there is a Land Tax Deferment lien against the manufactured home, transfers of ownership are prevented from proceeding.
• SBC staff (as well as qualified suppliers) do Transport Permits from the BC Online MHR application. (Do they see the PPR Lien information as well?)
• When a Transfer of Ownership is done, a notice is sent to the secured party of the lien to inform them that the Manufactured Home has been transferred. (Notice is generated by the system, printed at BC Registries and mailed out by staff)
• Staff will have to perform a Manufactured Home Number search in the new PPR for each Transfer or Transport permit being done in MHR to confirm whether there is a lien against the home. (Instructions for SBC and Qualified suppliers will have to be updated so they first check PPR)

@mstanton1
Copy link
Collaborator

#17440 is a story created to provide warnings and information in the MHR registrations table and in the MHR open screen. This should sufficiently meet the needs for all users who need to be aware if a lien is in place. Note, we prevent non staff from proceeding with changes in cases where a lien is in place. Staff may still proceed.

@PatrickAHeath do you feel a need to keep this ticket open as well or could we close it given it's covered off?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants