Apex Hub PulseEnterprise Wealth Tech
Pricing & Licensing

What Regulatory Reporting Software Costs a $20 Billion Bank: A Five-Year Worked Example

A line-by-line, hypothetical five-year cost model for a mid-size bank filing in two jurisdictions, comparing a licensed platform with a managed service so you can test every vendor quote.

By the Apex Hub Pulse editorial team · November 2026 · 8 min read

Why the license line is less than a third of the five-year bill

If you're comparing regulatory reporting software pricing across three or four proposals, the subscription fee is the number everyone negotiates and the one that matters least. In the hypothetical model below, module licenses come to about 29% of five-year spend. The rest goes to implementation, data integration, rule and taxonomy changes, environments and the people who keep the returns accurate.

That ratio is why so many regtech replacements run over budget. The license is fixed in the contract. Everything else is estimated, often by the vendor, and usually on the low side. A credible total cost of ownership means pricing those soft lines yourself and making vendors commit to them.

Advertisement

What follows is a hypothetical worked example. The bank, the figures and the scenarios are illustrative, built from typical 2026 market ranges that vary widely by contract, region and scope. Use it as a template for testing quotes, not as a benchmark, and confirm every number with the vendors you're considering.

The hypothetical bank: $20 billion in assets, two regulators

Say a bank with roughly $20 billion in total assets is headquartered in one jurisdiction and runs a regulated subsidiary in a second. Think of an EU bank with a UK subsidiary, a Gulf bank with a licensed entity in another GCC market, or a Southeast Asian lender with a subsidiary elsewhere in the region. The pattern holds across most pairings: one heavy home-regulator regime and one lighter but separate set of local returns.

The scope:

  • Home jurisdiction: capital adequacy, liquidity (LCR and NSFR or local equivalents), large exposures, leverage, statutory financial statements and statistical returns to the central bank. Assume roughly 40 to 60 returns, some in XBRL or similar structured formats.
  • Second jurisdiction: perhaps 15 to 25 local prudential and statistical returns, plus solo and consolidated variants where the regulator requires them.
  • Consolidation: group figures built from both entities, with intercompany eliminations.

The bank is replacing spreadsheets and an older on-premises tool. It wants the home jurisdiction live within 12 months and the subsidiary within 18. All figures are in thousands of USD.

Five-year cost of a licensed platform, line by line

Option A is a SaaS license from an established multi-jurisdiction vendor, such as Wolters Kluwer OneSumX, Regnology or AxiomSL (Nasdaq). The bank's own team runs it, with a systems integrator helping on implementation.

Line item (USD thousands)Y1Y2Y3Y4Y5Total
Module licenses, both jurisdictions (4% escalator)7507808108458804,065
Implementation services (vendor and integrator)2,2003000002,500
Data integration build, then run1,1002502502502502,100
Taxonomy and rule change work not covered by maintenance1002503502002501,150
Hosting tiers and extra environments150150160160170790
Incremental internal staff (about 4 FTE)6406406606606803,280
Legacy parallel run and decommissioning3000000300
Annual total5,2402,3702,2302,1152,23014,185

Four lines need explaining.

Implementation. For a two-jurisdiction scope, vendor and integrator services plausibly fall between $1.5 million and $3 million. Most of it is configuration, reconciliation and parallel-run support, not installation. The $300,000 in year two pays for the subsidiary go-live.

Data integration. Vendors leave this out of proposals because the bank owns it. Mapping general ledger, loan, deposit, treasury and collateral data into the vendor's input model, then building lineage your auditors will accept, is usually the biggest technical risk in the project. If your source data is clean and already sits in one finance data store, the build can come in under $800,000. If it's scattered across several core systems, $1.5 million is realistic.

Taxonomy and rule changes. Maintenance fees generally cover mandatory updates to existing returns. They often don't cover new returns, new regimes or the bank's own testing and sign-off. The year-three spike stands in for one major prudential reform, such as a Basel III final-reform rollout, landing in one of the two jurisdictions.

Staff. These are incremental heads only: platform administrators, data analysts and a change lead, at an assumed blended, fully loaded $160,000. Existing reporting accountants aren't counted.

Pricing the managed regulatory reporting service alternative

Option B is a managed service. A vendor or outsourcer hosts the platform, applies rule updates and prepares the returns, while the bank supplies data and keeps sign-off. Several platform vendors offer this, as do large consultancies and specialist outsourcers. Inclusions vary a lot, so compare scope documents, not headline fees.

Line item (USD thousands)Y1Y2Y3Y4Y5Total
Onboarding and transition1,10000001,100
Managed service fee (license, hosting, operations, standard updates)1,5001,5601,6201,6851,7558,120
Data integration build, then run (still the bank's job)1,0002502502502502,000
Retained oversight team (about 2 FTE)3203303403503601,700
Out-of-scope change requests50150250100150700
Legacy parallel run and decommissioning3000000300
Annual total4,2702,2902,4602,3852,51513,920

Over five years the two options land within about 2% of each other. That's the useful finding. The managed route is cheaper in year one, but its fee climbs every year while the licensed platform's run cost levels off. From year three the managed service costs more annually, and if the trend holds, extending the model to seven years puts the licensed platform ahead.

So cost alone rarely settles it. For a bank this size, a managed service is the better fit when you can't hire or keep regulatory technology staff in your market, or when the second jurisdiction is too small to justify building in-house expertise. Licensing wins when reporting data feeds other uses, such as ALM, stress testing or management reporting, and you want direct control of the platform.

Neither model moves accountability. Regulators in the EU, UK, US, India, the Gulf and Asia-Pacific generally hold the board and senior management responsible for the accuracy of returns, however the work is sourced. Outsourcing rules in many jurisdictions also require notification, exit plans and audit rights. Have your compliance and legal advisers confirm what applies before you sign.

Cost drivers that move the total by millions

Stress-test the model and four variables do most of the damage.

  1. Where your staff sit. A fully loaded reporting technologist costs far more in London, New York or Zurich than in Mumbai, Kuala Lumpur or São Paulo, often by a factor of two or more. On four incremental heads, that gap can swing the licensed option by well over $1 million across five years. It's also the main reason managed services look cheaper to banks in high-cost centers.
  2. Source data quality. Each extra core banking or loan system feeding the platform adds mapping, reconciliation and lineage work. The hypothetical bank assumes three main source systems. As a rough planning assumption, doubling that could add 40% to 70% to the data integration line.
  3. Regulatory change volume. Some regulators revise taxonomies several times a year and others rarely. A jurisdiction in the middle of a major prudential or structured-data overhaul can double the change line for two or three years.
  4. Return count and entity structure. Vendors price by module, jurisdiction, legal entity or return bundle. Adding solo returns for the subsidiary, or a third jurisdiction later, can raise license fees by a fifth or more.

Before comparing quotes, run your own model with each driver set to a pessimistic case. If the ranking between vendors flips, you've found where to negotiate.

Red flags to strike from a vendor quote before signing

Check every proposal for these issues and get written answers before commercial talks begin.

  • Uncapped escalators. Annual increases tied to inflation with no ceiling. Push for a fixed cap; mid-single-digit percentages are a common negotiating target, though terms vary.
  • A vague definition of "regulatory updates included." Ask whether new returns, new regimes and changes to submission formats are covered, or only amendments to existing templates.
  • Uncapped time-and-materials implementation. Ask for a fixed price, or at least a not-to-exceed figure tied to named milestones.
  • Environments charged separately. UAT, pre-production and disaster recovery environments sometimes surface only on the first invoice.
  • Managed-service SLAs that stop short of the deadline. If the vendor's obligation ends at "data processed" rather than "return ready for sign-off by day X," deadline risk stays with you.
  • Exit terms you can't price. Find out what it costs to export your data, mappings and historical returns in a usable format, and how long the vendor supports a handover.

Next step: send each shortlisted vendor the seven line items from the licensed-platform table and ask them to fill in all five years, including lines they consider the bank's responsibility. If a vendor's figures for data integration or change work come in 25% or more below your own estimate, require a written justification before they reach the final round.

Questions buyers ask

What is a typical regulatory reporting implementation cost for a mid-size bank?

For a bank of roughly $10 billion to $50 billion in assets filing in two jurisdictions, vendor and integrator services plausibly run $1.5 million to $3 million in 2026 market terms. Internal data integration can add another $0.8 million to $1.5 million. Actual figures depend heavily on source system complexity and scope, so confirm them with vendors.

Does a managed regulatory reporting service transfer compliance responsibility to the provider?

No. Regulators generally hold the bank's board and senior management accountable for the accuracy and timeliness of returns, whoever prepares them. Many jurisdictions also have outsourcing rules requiring notification, audit rights and exit plans, so get qualified legal and compliance advice before you contract.

Are taxonomy and rule updates included in the annual license fee?

Usually only partly. Maintenance typically covers mandatory changes to returns already in scope, while new returns, new regimes or major format changes may be quoted separately. Your own testing and sign-off effort is rarely included, so budget a separate annual change line.

Written by the Apex Hub Pulse editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.