Controlled data intake
Preview and load source snapshots for deposits, loans, general ledger, customers, and related reporting datasets.
Express-O 17 · Planned reporting module
Scheduled launch · Early 2027
The planned regulatory reporting module for Express-O 17, scheduled to launch in early 2027, will support BSP and other Philippine regulatory reports through controlled data preparation, generation, and review.
From source data to governed reporting
Express-O 17 will include a regulatory reporting module designed for BSP and other Philippine reporting requirements. A dedicated reporting workspace will bring data preparation, mappings, validation, generation, and review together, with report coverage agreed for each institution.
Report availability 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 dedicated reporting workflow keeps data preparation and report generation separate from daily transaction processing.
Extract a point-in-time view of approved banking datasets.
Validate data and apply the configured report mappings.
Run report definitions for the selected reporting period.
Review outputs and retain their execution history.
Report formats, validation rules, and submission requirements are confirmed for each institution.
Planned module capabilities
Dedicated workflows bring source preparation, mappings, generation, and execution history together for reporting teams.
Preview and load source snapshots for deposits, loans, general ledger, customers, and related reporting datasets.
Surface readiness issues and data exceptions before a report moves into review or export.
Maintain general-ledger, subsidiary-ledger, report-line, and data-tag mappings in a visible operating workflow.
Organize report definitions around BSP, AMLC, CIC, and PDIC portfolios as requirements are configured.
Retain reporting period, operator, status, and execution history so outputs can be traced back to their run.
Render analytical reports and generate configured submission files through PostgreSQL aggregation and JasperReports.
Modular architecture
Reporting runs through a dedicated data path, keeping analytical workloads separate from day-to-day banking transactions.
Deposits, loans, customers, transactions, and general ledger
Point-in-time extraction, preview, validation, and controlled load
Purpose-built PostgreSQL datasets isolated from daily transaction processing
Mappings, SQL aggregation, report definitions, and JasperReports
Operational review, execution history, exports, and configured submission files
Operational safeguards
Reporting activity runs against a dedicated reporting store so heavy report generation does not compete with customer transactions.
A point-in-time dataset gives each report run a stable and reconcilable source.
Import, mapping, and execution workflows provide visible control points instead of opaque offline preparation.
Part of Express-O 17
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
Share your current environment, reporting or payment scope, and operational priorities with our banking technology team.
Discuss your requirements