Express-O 17 · Regulatory reporting

Regulatory
Reports

Flagship banking platform

Prepare BSP, CIC, PDIC, and AMLC reporting from shared, dated source data. Validate report-specific requirements, retain generated files, and manage independent approval and filing evidence in one workspace.

Shared facts. Report-specific controls.

Reporting confidence starts
with governed data.

Bring customer, deposit, loan, transaction, and general-ledger data into a dedicated reporting workspace. Reuse common facts across report preparation, apply agency-specific codes and mappings, and keep the generated file connected to its source revisions, approval, and recorded agency outcome.

Confirm your reporting portfolio.

Report coverage depends on the agreed format, source data, mappings, and validation for your institution. Confirm supported report versions and submission requirements with MBP; generation alone does not establish regulator acceptance.

Review your requirements with us →

The reporting journey

A clear path from source data to report output.

A dedicated reporting workflow keeps data preparation and report generation separate from daily transaction processing.

  1. 01

    Source

    Extract a point-in-time view of approved banking datasets.

  2. 02

    Prepare

    Validate data and apply the configured report mappings.

  3. 03

    Generate

    Run report definitions for the selected reporting period.

  4. 04

    Review & export

    Review outputs and retain their execution history.

Report formats, validation rules, and submission requirements are confirmed for each institution.

Module capabilities

One operating flow from
source to output.

Dedicated workflows bring source preparation, mappings, generation, and execution history together for reporting teams.

01

Common source preparation

Preview and import dated customer, deposit, loan, transaction, and GL extracts. Retain source revisions, counts, and hashes for reconciliation.

02

Connected report workspaces

Prepare FRP, COCREE, CIC, PDIC Deposit Account View, and supported AMLC covered transactions using common facts and report-specific extensions.

03

Bank-specific FRP mappings

Maintain GL, snapshot, data-tag, and report-line rules. Apply reasoned FRP adjustments and validate configured XML destinations.

04

Validation and correction

Resolve shared-data issues at source and record reasoned report-only corrections. Changes invalidate prior preparation so the file can be checked again.

05

Approval of the exact file

Retain generated bytes, source manifests, and SHA-256 hashes. Approval of the current file requires a different authenticated operator.

06

Filing and amendment evidence

Record external filing references separately from agency acceptance or rejection. Reopen an eligible file with authorization and a reason while retaining earlier evidence.

Inside the workspace

From common facts
to a controlled filing.

See the current application screens and a short visual walkthrough of source intake, report preparation, and filing controls.

Workspace walkthrough · 24 seconds · silent, with captionsRead the descriptive transcript →
Express-O 17 source import screen with dataset selection, file upload, and preview controls
01

Start with shared source facts

Select the dated dataset, preview the source file, and confirm the import.

View full-size screen ↗
FRP preparation workspace showing reporting date selection and validation controls
02

Prepare the reporting period

Select FRP preparation, validate the date, and manage adjustments before generation.

View full-size screen ↗
Regulatory filing controls showing report and date selection with retained file history
03

Keep approval connected to the file

Select the report and date to review retained files, approvals, and agency outcomes.

View full-size screen ↗

Captured from the local application with no customer records displayed. Screens show preparation and control interfaces; bank configuration and authenticated operator acceptance are part of implementation.

Report preparation, scoped to your institution

BSP · FRP / FRP_S
Configured GL, deposit, and loan mappings with XML validation and reasoned adjustments. Applicable schedules and bank mappings require confirmation.
BSP · COCREE
Customer and installment-loan projections, report-only corrections, and supplementary schedule overlays. Full exposure coverage requires source and semantic validation.
CIC · Credit data
Borrower and loan preparation with retained output and filing evidence for the external SFTP and CE Portal process.
PDIC · Deposit Account View
Shared customer and deposit preparation with Annex C and C-1 deductions packaged in a generated ZIP.
AMLC · Covered transactions
Joined customer, account, loan, and financial-event data with supported transaction codes and classification checks. Full GoTRACS coverage is confirmed during discovery.
  1. Import & reconcile
  2. Prepare & validate
  3. Generate & retain
  4. Independent approval
  5. File externally
  6. Record agency outcome

Files are submitted through the institution’s approved agency channels. The workspace records filing evidence and agency results; it does not transmit directly to regulators.

Modular architecture

Designed to protect
the transaction core.

Reporting runs through a dedicated data path, keeping analytical workloads separate from day-to-day banking transactions.

  1. 01

    Approved source extracts

    Dated customer, deposit, loan, transaction, and GL facts

  2. 02

    Controlled intake

    Preview, strict imports, revisions, and source reconciliation

  3. 03

    Common reporting store

    Shared facts with agency codes and report-only extensions

  4. 04

    Report preparation

    Mappings, corrections, validation, and retained output files

  5. 05

    Approval & filing evidence

    Independent approval, external filing references, and recorded agency outcomes

Operational safeguards

Built for work that must be
explainable and supportable.

01

Dedicated reporting data

Prepare reports against a separate reporting store. Production source adapters, scheduling, and genuine as-of reconciliation are agreed as part of implementation.

02

Protected preparation

Common date locks coordinate imports and filing controls. Source changes invalidate dependent preparation, and filed reports protect their source date until the correction process is followed.

03

Evidence across the lifecycle

Retained source revisions, exact files, independent approval, and control history support review. Hosting authentication, access roles, retention, and backups must be configured for live use.

Part of Express-O 17

A dedicated module.
Part of the flagship.

Move regulatory preparation into a dedicated reporting platform while Express-O 17 remains focused on customer and transaction processing.

Explore the core banking platform →

Let’s plan your next step

Explore how Regulatory Reports can fit your institution.

Share your current environment, reporting or payment scope, and operational priorities with our banking technology team.

Discuss your requirements