Skip to main content
The Regulatory Reporting Connector (RRC) provides APIs for managing regulatory reporting across different reports and jurisdictions. It is designed to support report submission, updates, and corrections through structured report-specific flows. Each supported report has its own API structure, data requirements, and processing logic. This allows reporting integrations to be handled in a consistent way while keeping report-specific requirements separated.

​
How It Works

  • Data submission - The client submits data in the required structure for the relevant report.
  • Initial validation - The submitted data is validated before submission to make sure incomplete or incorrectly structured data is identified early.
  • Package generation and submission - If the data passes validation, a submission package is generated and sent to the regulator.
  • Response processing - The regulator response is processed and the result is returned, whether the submission was accepted, rejected, or returned with errors.
  • Corrections - If errors are returned, corrections can be submitted for the affected data.
  • Updates - If previously submitted information changes, updated data can be submitted for the relevant record.

​
What each report section includes

Each report section describes the relevant endpoints, request structure, required data, and report-specific processing logic.

​
Supported regulatory reports

MMR-SASK

Report account holder information to VMI for regulatory compliance

​
Authentication

RRC uses OAuth 2.0 client credentials flow. See the authentication guide for details.
Last modified on April 9, 2026