MRAS integration

[sienna-oldaccountdontuse]

Background

MRAS is a system that helps facilitate sharing of info across different Canadian provincial registries. We need to integrate with MRAS for our June release. MRAS has a few pieces:

• Gives users links to other jurisdictions right after they incorporate so they know where to register elsewhere
• Updates select basic information in other systems if the entity changes that info in our systems, keeping all systems that they have registered in up to date
• Check out this PPT provided by MRAS team for lots of business and technical information

Story

• As a benefit company incorporator,
• I want to register my benefit company in an MRAS jurisdiction (Manitoba, Alberta, Quebec, Saskatchewan)
• and I can easily operate in multiple jurisdictions

Acceptance Criteria

Scenario 1: Notify about option to register in partner jurisdiction

• GIVEN I am incorporating a benefit company in BC
• WHEN I have finished incorporating,
• AND received my outputs
• THEN I will see links to register in a partner jurisdiction in my outputs

---

NOT MVP ? :

Scenario 2: Pull info from MRAS hub

• GIVEN I have an existing Benefit Company in BC
• WHEN I go to register my business in a different jurisdiction
• AND provide my BC Incorporation number
• THEN I see my BC benefit Company information, to reduce errors/fraud/complexity in registration.

Requirements Documentation

https://sites.google.com/freshworks.io/bcros/business-registry/all-entities/mras

Design

@xxx - please link the Design here

---

Link to DoR for a US/ Feature https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoR%20-%20Entity.md

Link to the DoD for a US/ Feature https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoD%20-%20Entity.md

[sienna-oldaccountdontuse]

Research: https://docs.google.com/document/d/1ZttZlY96tQGhSpWaXneJ9iCQ7tSgFyWw6O8rB9xDBeo/edit?usp=sharing

[lmcclung]

Discussing with Carol Apr 24 - to confirm whether sending links with partner jurisdiction in the incorporation notification email along with outputs will suffice for Scenario 2.

Can confirm Scenario 1 works without our intervention once we have entities back into CDEV/CTEST databases.