A banking CRM is customer relationship software built for banks and credit unions. It models households, financial accounts and relationship roles, pulls balances and transactions from the core, and limits who sees which records. For a US community bank, regional bank or credit union, the choice turns on core integration, exam-ready access controls and five-year cost.
This guide covers what to require, how CRMs connect to Fiserv, Jack Henry and FIS cores, which rules shape the build, and what the main platforms cost. We checked every vendor fact and price on official pages on 12 November 2026.
What is a banking CRM?
A banking CRM is where bankers, branch staff, contact center agents and marketers work with each customer or member. They track opportunities and service cases there, and run onboarding and outreach. The core stays the system of record for balances and transactions.
The data model is what sets it apart. A general CRM tracks accounts, contacts and deals. A banking CRM also needs households, deposit and loan accounts, and roles such as joint owner or guarantor.
The market is consolidating. The FDIC based its Q2 2026 results on 4,238 insured banks and savings institutions, per its 25 August 2026 release. The NCUA counted 4,214 federally insured credit unions with 146.1 million members at 30 June 2026, down from 4,370 a year earlier, in its Q2 2026 data summary. Each merger joins two customer bases and often forces a CRM decision.
What should a banking CRM do that a general CRM does not?
Score every vendor against these six needs. Ask for a live demo of each one with your own sample data.
| Requirement | Why it matters | What to ask the vendor |
|---|---|---|
| Household and relationship view | Bankers price and cross-sell on the whole relationship, not one account | Show a family with joint accounts and a business owner with personal and business accounts |
| Core data without manual exports | A banker should never pitch a product the customer already holds | Which core APIs do you call, and how fresh is the data? |
| Commercial relationship management | Relationship managers run loan pipelines, treasury sales and portfolio reviews | Show a commercial loan from referral to booked |
| One service history across channels | Branch, phone, chat and digital banking requests land in one case record | How are cases routed, and how are service levels tracked? |
| Referrals between lines of business | Teller-to-banker and retail-to-wealth referrals get lost without tracking | How is a referral tracked to a booked account? |
| Need-to-know access and audit trail | Wealth, commercial and retail teams often must not see each other's records | Show who can see a record, why, and the log an examiner would get |
In Financial Services Cloud, a household is a business account paired with a Household-type party relationship group. Each family member is a person account, and Account Contact Relations record each person's role, as Salesforce Help describes. Ask other vendors to show the equivalent objects.
Comparing CRMs for a fintech or nonbank lender instead? Our guide to Salesforce CRM for fintech companies covers those needs.
How does a banking CRM connect to Fiserv, Jack Henry and FIS cores?
Plan core integration first, because it depends on your core provider's licensing, connectivity rules and test windows. The CRM reads customer, account and transaction data from the core through the core provider's APIs. An integration layer handles mapping, security, retries and monitoring.
| Core provider | Common cores | Integration route | What to check |
|---|---|---|---|
| Jack Henry | SilverLake (banks), Symitar (credit unions) | jXchange for SilverLake; SymXchange for Symitar | Vendor program access and the 2028 security changes below |
| Fiserv | DNA, Premier, Signature | Open APIs; DNA lists 400+ pre-integrated apps on AppMarket | Which APIs your contract licenses, and real-time vs batch |
| FIS | Modern Banking Platform, IBS, Horizon | Over 1,000 APIs through Code Connect | Which APIs exist for your specific core and hosting model |
Two Jack Henry dates matter for anything you build now. Username and password access to jXchange will be deprecated on 30 April 2028, and Jack Henry recommends OAuth 2.0. SymXchange connections will require mTLS or VPN/IPSec by 1 November 2028, per its connectivity guide. Build on the new methods from day one.
Fiserv calls DNA "an open API solution." FIS describes its Modern Banking Platform as API-first.
On Salesforce, the MuleSoft Accelerator for Financial Services includes three core banking use cases: any core, Jack Henry SilverLake and Thought Machine Vault. It also ships BIAN-compliant API specs. It has no FIS or Fiserv use case, so those cores start from the generic pattern. Our MuleSoft integration team builds and runs these connections.
Our view: sync balances, products and recent activity to the CRM, not full transaction history. Keep the core as the system of record for money, and give every sync a named owner and an alert.
Which regulations shape a banking CRM project?
No US regulation names a CRM. These rules still decide how you contract for one and configure it.
| Rule | What it requires | What it means for the CRM |
|---|---|---|
| SR 23-4 third-party guidance (June 2023) | Federal Reserve, FDIC and OCC guidance on risk management across all stages of a third-party relationship | Your CRM vendor and implementation partner both go through vendor risk review. Ask for SOC 2 reports, subprocessors, data location and exit terms. |
| Incident notification rule (2022) | Banks notify their regulator within 36 hours of determining a notification incident. Bank service providers notify banks after 4 or more hours of disruption. | The CRM contract should commit the vendor to notify you fast enough to meet that clock. |
| NCUA cyber incident rule (September 2023) | Federally insured credit unions report a reportable cyber incident within 72 hours | Same contract point, on a 72-hour clock |
| Interagency information security guidelines (GLBA 501(b)) | A written security program, including due diligence, contracts and monitoring for service providers | Encrypt sensitive fields, mask account numbers, restrict exports and document the controls |
| CFPB Personal Financial Data Rights | Final rule issued October 2024; reconsideration opened August 2025 | Wait for the outcome before you design data-sharing features around it |
Access control needs the most design work. Salesforce's Compliant Data Sharing uses participant roles to grant read-only or read/write access to specific records. It can also enforce an ethical wall between divisions, and it lets compliance staff audit who has access and why, as Trailhead explains.
Techila Global Services works under SOC 2 controls. That shortens the review when your vendor management team assesses the implementation partner as well as the platform.
How do Financial Services Cloud, Creatio, Dynamics 365 and banking-only CRMs compare?
The four options differ on banking depth, how much you build yourself and how they price. We read each list price on the vendor's site on 12 November 2026.
| Factor | Salesforce Financial Services Cloud | Creatio Bank.AI | Microsoft Dynamics 365 Sales | Banking-only CRMs |
|---|---|---|---|---|
| What it is | Industry edition built on Sales Cloud or Service Cloud | Low-code platform with a banking package | General CRM; banking features come from configuration or partner apps | CRMs built for financial institutions, such as Total Expert |
| Banking data model | Households, person accounts, financial accounts and relationship groups | Customer 360, portfolio management, KYC and AML apps | Standard data model, configured | Built in; confirm depth for commercial banking |
| Core integration | MuleSoft accelerator with any-core and SilverLake use cases | Ask for a connector to your core; none is named on its banking site | Power Platform and Azure tools, or partner connectors | Often prebuilt for common cores; confirm yours |
| Security and audit | Compliant Data Sharing; Advanced adds Backup & Recovery, Data Detect and Security Center | Check on the platform plan you buy | Role-based security and auditing | Varies by vendor |
| AI agents | Flex Credits for Agentforce in every edition; Max adds the full Agentforce for Industries suite | Customer Onboarding, Account Servicing and Dispute Resolution agents | Copilot; Premium includes 1,000 Copilot Credits per user per month | Varies by vendor |
| List price per user per month | $325 Core, $500 Advanced, $700 Max, billed annually | $40 Growth or $75 Enterprise platform, plus $15 per product; $10,000 yearly minimum | $65 Professional, $105 Enterprise, $150 Premium, paid yearly | Quoted; no public price lists |
| Best fit | Banks and larger credit unions running sales, service and onboarding on one record | Institutions that want a lower license cost and will configure heavily | Institutions standardized on Microsoft 365 and Azure | Smaller institutions that want a narrow, fast rollout |
Read the price row with care. Financial Services Cloud includes the industry data model in every edition. Creatio adds each product (Sales, Marketing, Service) on top of the platform fee, with a five-user minimum and a standard three-year term. Its banking package is Bank.AI. Dynamics 365 Sales is priced as a general CRM, and Dynamics 365 Customer Service is licensed separately. Total Expert publishes no prices. For rivals outside banking, see our comparison of Salesforce competitors and alternatives.
What does a banking CRM cost for 50 users?
Licenses are the only cost with public prices. Here is list-price arithmetic for 50 users for one year:
| Option | Per user per month | 50 users, 12 months |
|---|---|---|
| Financial Services Cloud Sales Core | $325 | $195,000 |
| Creatio Enterprise plus Sales and Service | $75 + $15 + $15 = $105 | $63,000 |
| Dynamics 365 Sales Enterprise | $105 | $63,000, before Customer Service licenses |
Discounts, user mix and add-ons change these numbers. The other costs depend on scope:
- Implementation. Data model, workflows, security model, reports and training. Cost grows with each line of business in the first release.
- Core integration. Core provider API fees, the integration platform, and building and testing each flow. Real-time sync costs more than a nightly batch.
- Data migration. Cleaning and matching customer records from the core and legacy CRMs, which is harder after a merger.
- Run costs. An admin team or managed service, release testing and integration monitoring.
The cheapest license is not always the cheapest project. If your team must build the household model and core integration itself, a $63,000 license can cost more over five years than a $195,000 one. Compare five-year totals.
How should a bank or credit union choose a CRM?
- Pick three to five use cases. For example: commercial relationship management, branch referrals and consumer loan onboarding. Write down the users, data and target outcome for each.
- Map your systems. List the core, digital banking, loan origination and card systems, and the data each use case needs.
- Test core integration first. Ask each vendor for a live connection to your core, not a slide. Confirm API licensing with your core provider.
- Start vendor risk review early. Send SOC 2 reports, incident notification terms and data location answers to vendor management before the final round.
- Score the shortlist. Use the requirements table above. Weight the household view, core data and access controls highest.
- Model five-year cost. Include licenses, implementation, integration, migration and run costs.
- Pilot one team. Launch one line of business, measure adoption and data quality, then expand.
How does Techila help banks and credit unions with CRM?
Techila Global Services is a Salesforce Summit Partner, founded in 2012 by Chitiz Agarwal and headquartered in Frisco, Texas. Our 350+ Salesforce professionals hold 500+ Salesforce certifications and have delivered 700+ projects, including 15+ Agentforce programs.
We deliver Financial Services Cloud implementation for banks and credit unions, from the household model and Compliant Data Sharing to MuleSoft core integration. See our wider Salesforce work for financial services.
Frequently asked questions
What CRM do banks use?
US banks and credit unions choose from three groups. The first is general CRM platforms with a financial services edition, such as Salesforce Financial Services Cloud and Microsoft Dynamics 365. The second is low-code platforms with a banking package, such as Creatio's Bank.AI. The third is CRMs built only for financial institutions, such as Total Expert.
Is Salesforce good for banks?
Salesforce fits banks and credit unions that want sales, service, onboarding and marketing on one platform. Financial Services Cloud adds households, person accounts and financial accounts, plus Compliant Data Sharing for need-to-know access. At $325 to $700 per user per month list price, it costs more than most alternatives, so it pays off when several teams share the client record.
How does a CRM connect to the core banking system?
A CRM connects through the core provider's APIs, usually with an integration layer in between. Jack Henry offers jXchange for SilverLake banks and SymXchange for Symitar credit unions. FIS offers APIs through Code Connect, and Fiserv offers open APIs for cores such as DNA. MuleSoft or a similar tool calls those APIs, maps the data and keeps records in sync.
What does a banking CRM cost?
Banking CRM licenses run from about $40 to $700 per user per month at list price. Salesforce Financial Services Cloud is $325 to $700. Microsoft Dynamics 365 Sales is $65 to $150. Creatio charges $40 or $75 plus $15 per product, with a $10,000 yearly minimum. Banking-only CRMs are usually quoted. Implementation, core integration and data migration are extra.
Do credit unions need a different CRM?
Credit unions need a different setup, not a different product. They serve members, often run Symitar or another credit union core, and report cyber incidents to the NCUA within 72 hours. Financial Services Cloud and Creatio both package their CRM for credit unions. Before you buy, check member terminology, the connector for your core and the vendor's incident notification terms.
How long does a banking CRM implementation take?
Timeline depends on scope more than on the platform. A first release for one team on one core, such as commercial relationship managers, is the fastest path. Each extra line of business, a real-time core integration, migration from a legacy CRM and your vendor risk review all add time. Phase the rollout by team and keep the core as the system of record.
Next steps
Choosing a banking CRM, or reviewing one you already run? Talk to our financial services team or call +1 617-777-9873. We will review your core, top use cases and timeline, then send a written scope and estimate.
