SSSmartnode Suite
Guides › Pricing & Licensing

Signing a Core Banking Contract? Eight Clauses Banks Regret Accepting

Core banking deals often run a decade or more, and most of the pain traces to eight clauses that looked harmless at signing. Here's what each one costs you and what to negotiate in its place.

Smartnode Suite editorial team · November 2026 · 10 min read

Why the contract outlasts the demo

You've picked the platform, the board has approved the business case, and now procurement and legal face a 200-page master agreement the vendor wants signed this quarter. In core banking contract negotiation, this is where buyers give away the most. The team is tired, the deadline is the vendor's, and the clauses that will hurt in year six read like boilerplate.

A core contract commonly runs 7 to 12 years once renewals are counted, and replacing the system can take another two to four. Over that span the license fee matters less than how prices escalate, how the vendor measures volume and service, and what happens when you leave. Regulators care about the same clauses. The EBA Guidelines on outsourcing arrangements and the EU's Digital Operational Resilience Act (DORA), the Reserve Bank of India's IT outsourcing directions, the Monetary Authority of Singapore's outsourcing guidelines and APRA's CPS 230 all set out what a contract for a critical service should contain.

Advertisement

The eight red flags below are grouped by theme, each with what to ask for instead. Treat this as a negotiating framework, not legal advice, and have outsourcing and technology counsel in your own jurisdiction review the final drafting.

Uncapped price escalators and volume-tier traps

Red flag 1: CPI-plus escalators with no ceiling

The usual wording is "fees increase annually by the greater of 5% or CPI plus 3%." That looks manageable when inflation is low. It gets expensive fast when inflation runs high, and in some markets it does so often.

Hypothetical worked example: a mid-sized bank pays $2.0 million a year for a hosted core. Say inflation averages 6%. Under CPI plus 3%, fees rise 9% a year and the bank pays roughly $12 million over five years. With a 4% annual cap, the total is roughly $10.8 million. That's a gap of more than $1 million from one sentence. For context, typical 2026 market ranges run from several hundred thousand dollars to $1.5 million a year for smaller banks and credit unions, and from about $1 million to $5 million or more for mid-tier institutions. These vary widely by contract and region, so confirm with vendors.

Negotiate instead: a fixed price for the first two or three years, then a single published index (name the specific national index) with a hard cap, typically 3% to 5%. Exclude escalation from any year in which the vendor missed its SLA.

Red flag 2: volume tiers that only move one way

Per-account or per-transaction pricing is standard. The trap is in the definitions. If "account" covers dormant, closed-but-retained and zero-balance accounts, you can climb a tier without gaining a single customer. A one-way ratchet means you keep paying the higher tier after you sell a portfolio.

Negotiate instead: define billable units as active accounts, with an activity test such as a transaction in the last 12 months. Make unit prices fall at higher tiers. Allow step-downs after divestments, and run true-ups once a year with a 30-day dispute window, not quarterly.

A core banking SLA that measures the wrong thing

Red flag 3: headline availability with gaps you could drive a batch run through

A 99.5% monthly availability target still allows roughly 3.6 hours of downtime a month. Weak SLAs add their own gaps. Availability is measured at the vendor's data center, not at your channels or APIs. "Scheduled maintenance" is excluded with no limit. Service credits are capped at a small share of monthly fees and are your only remedy. Under those terms, a failed end-of-day run that stalls card authorizations can be fully compliant.

A good core banking SLA sets targets per service, not one aggregate number. Real-time payments and digital-channel APIs need tighter targets than back-office reporting.

TermWeak versionWhat to ask for
Availability99.5% monthly, platform-wide99.95% for customer-facing and payment services, measured at the API endpoint
MaintenanceExcluded, unlimitedCapped hours per month, in agreed low-traffic windows, with advance notice
RecoveryNot specifiedContractual RTO and RPO per service, tested at least once a year
CreditsSmall cap, sole remedyEscalating credits with a meaningfully higher ceiling, not the sole remedy
Chronic failureNoneTermination right after repeated breaches, e.g. three in any six months
Incident notice"Without undue delay"Notice within a set number of hours, so you can meet your own regulatory reporting deadlines

The last row matters most. Under DORA and similar regimes elsewhere, a bank has hours, not days, to make its first report on a major incident. A vendor that tells you on day two leaves you in breach.

Missing regulator audit rights and unchecked subcontracting

Red flag 4: audit rights the regulator would reject

Vendors often offer one audit a year, on long notice, at your cost, limited to a SOC 2 or ISAE 3402 report. That may work for a low-risk SaaS tool. For core banking it falls short of most supervisors' expectations.

  • EU: the EBA outsourcing guidelines and DORA's contractual requirements for ICT services supporting critical or important functions expect access, inspection and audit rights for the institution and its competent authority.
  • India: the RBI's IT outsourcing directions expect the RBI, or anyone it appoints, to be able to inspect the service provider.
  • Singapore: MAS guidelines expect the contract to give MAS access to the provider's information and premises as they relate to the outsourced service.
  • Australia: CPS 230 expects agreements with material service providers to allow APRA access to relevant documents and information.

Negotiate instead: audit and access rights for you, your external auditors and any regulator with jurisdiction over you. Don't let the vendor limit how often a regulator can come. Pooled audits and certifications can supplement your rights but shouldn't replace them, and the vendor should support regulator requests at no extra charge.

Red flag 5: subcontracting and data location the vendor can change on its own

Many contracts let the vendor change cloud provider, hosting region or offshore support team with nothing more than a portal notice. That's a problem wherever data must stay in-country, as with India's payment-data storage rules and residency expectations in parts of the Gulf, Southeast Asia and Africa.

Negotiate instead: list material subcontractors and data locations in a schedule. Require advance notice (90 days is a common ask) before any change, with a right to object and to terminate without penalty. Your audit and security obligations should flow down to every subcontractor that touches customer data.

Weak exit assistance and an escrow nobody can use

Red flag 6: "reasonable assistance at then-current rates"

Banks regret this clause most. A core migration commonly takes 18 to 36 months. A vendor you're leaving has little reason to hurry, and "then-current rates" lets it name its price. EBA guidelines, DORA, MAS and APRA all expect documented exit strategies, and your plan is only as credible as your contract.

A usable exit assistance clause should include:

  • An assistance period of 12 to 24 months that applies however the contract ends, including your termination for convenience and the vendor's breach
  • Continued service during that period at existing fees and SLA
  • A fixed rate card for transition services, agreed now
  • Full data extracts in a documented, non-proprietary format with a data dictionary, plus at least two trial extracts before cutover
  • Support for parallel runs and knowledge transfer to the incoming vendor

Red flag 7: a software escrow agreement with narrow triggers and no verification

Many escrow deposits are never tested, and the code is released only if the vendor goes formally insolvent. For a SaaS core, source code alone is close to useless. You'd also need deployment scripts, configuration and access to the hosting environment.

Negotiate instead: broader release triggers covering insolvency, end of support for your version, failure to fix a material breach, and a change of control that discontinues the product. Require build verification at least once a year. For hosted cores, consider a SaaS continuity escrow that keeps the cloud environment running for a set period. Typical 2026 market ranges are in the low thousands to tens of thousands of dollars a year for escrow, with verification often costing more per test depending on scope. Confirm current pricing with providers.

Liability caps that treat a data breach like a late invoice

Red flag 8: one cap, set at 12 months' fees, for everything

A general cap of 12 months' fees is common and often acceptable for ordinary breaches. The problem is what gets pushed under that cap or excluded altogether. Data loss, regulatory penalties and customer redress are often labeled "indirect or consequential," so the vendor isn't liable for them at all. Yet a breach at the vendor's data center can trigger notification costs, remediation and regulatory action under the GDPR, the UK GDPR, India's DPDP Act, Singapore's PDPA or Brazil's LGPD.

Negotiate instead:

  • A separate, higher cap for breaches of data protection, security and confidentiality, often a multiple of annual fees (two to five times is a common ask)
  • Unlimited liability for fraud, wilful misconduct and IP infringement indemnities
  • Express wording that data restoration, regulatory investigation costs and customer compensation count as direct losses
  • Cyber insurance from the vendor, verifiable and matched to the higher cap

Whether fines can be recovered or insured differs by jurisdiction, and some legal systems don't allow regulatory penalties to be passed to someone else. Your counsel should confirm what is enforceable where you operate.

A negotiation sequence that protects your leverage

Your leverage peaks before you name a preferred vendor, so table these eight clauses at the RFP stage. Put your required positions in the RFP itself and score each bidder's deviations. Vendors price a concession differently when a competitor has already agreed to it.

  1. Map each clause to the regulatory requirements in every country where you hold a license, and record where the strictest applies.
  2. Classify each ask as must-have or tradeable. Regulator audit rights and exit assistance are must-haves. Escalator caps and credit percentages can be traded.
  3. Trade term length for price protection. A seven-year commitment is worth a longer fixed-price period and a lower cap.
  4. Run a mock exit. Ask the vendor to produce a full data extract from a test environment before you sign.
  5. Put the agreed exit plan and subcontractor schedule into the contract as annexes, not side letters.

Here's the decision rule: if a vendor won't accept regulator audit access or a funded exit period of at least 12 months, stop negotiating on price. That gap will surface in your next supervisory review, and no discount makes up for it.

Quick answers

Which core banking contract clauses do regulators actually check?

Supervisors usually look at audit and access rights, subcontracting and data location, incident notification, business continuity and exit strategies. The EBA guidelines and DORA in Europe, the RBI's IT outsourcing directions, MAS outsourcing guidelines and APRA's CPS 230 all address these areas for critical services. Check the current rules in each country where you're licensed.

What is a reasonable price escalator in a core banking contract?

Many buyers aim for two or three fixed-price years, followed by increases tied to a named national inflation index and capped at about 3% to 5% a year. Avoid "greater of" formulas and CPI-plus wording with no ceiling. Actual outcomes depend on deal size, term length and how competitive the bid was.

Is a SOC 2 or ISAE 3402 report enough to satisfy audit rights?

For core banking, usually not. These reports are useful supplements, but most banking supervisors expect the contract to give the institution and the regulator their own rights of access, inspection and audit. Accept pooled audits and certifications as a way to cut costs, not as a substitute for those rights.

Do we still need a software escrow agreement if the core is SaaS?

Yes, but the structure needs to change. Source code alone won't help much if the vendor fails, because you'd also need deployment scripts, configuration and access to the hosting environment. A SaaS continuity escrow that keeps the environment running for a set period is often more useful.

How long should the exit assistance period be?

Twelve to 24 months is a common target, because full core migrations often take 18 months or more. The period should apply however the contract ends, with service continuing at existing fees and transition work priced from a fixed rate card. Size it to your own migration plan, not to the vendor's standard offer.

Should the liability cap differ for data breaches?

Most banks seek a separate, higher cap for data protection and security breaches, often a multiple of annual fees, plus unlimited liability for fraud and wilful misconduct. Make sure remediation and customer redress costs count as direct losses. Whether regulatory fines can be recovered varies by jurisdiction, so have local counsel confirm.

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