Skip to content

Integration · Insurance & Lending

Core banking systems integration

Finastra, Jack Henry, FIS and others Salesforce

Short answer

A core banking integration connects the bank or credit union core (such as Finastra Phoenix, Jack Henry or FIS) with Salesforce Financial Services Cloud, giving relationship managers a single view of customers, deposits and loans.

How the Core banking systems integration works

The core remains the system of record for accounts and transactions; Salesforce becomes the system of engagement for relationships, referrals, onboarding and service. A typical design uses MuleSoft or another integration layer for nightly batch loads plus events for key changes, without making the CRM depend on a data warehouse. Vantage Point has designed core-to-FSC architectures for community banks.

What syncs

  • Customers and relationships
  • Deposit and loan accounts with balances
  • Key events such as new accounts or maturities

See the architecture diagram ↓

Integration options

  • MuleSoft API-led integration
  • Nightly batch plus event-driven updates
  • Vendor connectors where available

What to plan for

  • Core vendor API access and fees
  • Customer matching across products
  • Sensitive data (SSN, TIN) handling

Frequently asked questions

Does the core stay the system of record?

Yes. Salesforce shows and acts on core data; the core keeps the official records.

Do we need a data warehouse first?

Not necessarily. Many designs connect the core to Salesforce directly through an integration layer.

Last reviewed October 2, 2026 by the Vantage Point team. Product names and capabilities belong to their respective vendors; access to some data requires the vendor's approval. Browse all integrations →

Architecture

How data flows: Core banking systems integration

CRM Middleware / connector layer Connected system
What syncs between systems
FromToWhatDirectionTimingHow
Core bankingSalesforce FSCvia MuleSoft APIs Customers, deposit & loan accountsNightly batch. → one-way scheduledmiddleware
Core bankingSalesforce FSCvia MuleSoft APIs New accounts & maturities → one-way event-drivenmiddleware

A typical pattern, simplified. Your design depends on licenses, data ownership and volumes, which we settle in discovery.