Financial Software Buyer's Glossary
Plain-English definitions of the contract, pricing, technology and compliance terms financial institutions meet when evaluating software vendors.
- Data processing agreement (DPA)
- A contract that sets out how a vendor processes personal data on the institution's behalf, covering security measures, subprocessors and breach notification, as required by laws such as GDPR.
- Data residency
- A requirement that customer data be stored, and sometimes processed, within a specific country or region. Rules vary widely between jurisdictions such as India, Saudi Arabia, Indonesia and the EU.
- Exit and transition assistance
- Contract terms that oblige the vendor to return data in a usable format and support migration to a replacement system, ideally at pre-agreed rates.
- False positive rate
- The share of screening or monitoring alerts that turn out not to be genuine risk after investigation. It's the main driver of analyst workload in AML, sanctions and fraud tools.
- Interchange++ (IC++)
- A card pricing model that passes through the card-issuer interchange fee and the card-scheme fee at cost and adds a separate processor markup. It's more transparent than a single blended rate.
- Material outsourcing
- A regulatory classification for outsourcing critical functions, such as a core banking system. In many countries it triggers notification to the regulator, due diligence, audit rights and exit-plan requirements.
- Minimum annual commitment
- A guaranteed yearly spend or volume floor the buyer pays even if actual usage comes in lower. It's common in KYC, payments and per-account core banking pricing.
- Model validation
- Independent testing of a scoring, detection or pricing model's design, data and performance. Regulators increasingly expect it for vendor-supplied models as well as in-house ones.
- Multi-tenant SaaS
- A cloud delivery model where many clients run on one shared software instance with their data kept logically separate. Upgrades are usually mandatory and arrive on the vendor's schedule.
- Parallel run
- A migration technique where the old and new systems process the same live transactions side by side so results can be reconciled before cutover.
- Per-account pricing
- A licensing model where fees scale with the number of active customer accounts or loans on the platform, often in tiers that get cheaper per account as volume grows.
- Right to audit
- A contract clause that lets the institution, its auditors and its regulators inspect the vendor's controls and premises. Many supervisors expect it for critical outsourced services.
- Sandbox environment
- A non-production copy of the vendor's platform with test data. Buyers use it to check APIs, configuration and integrations before signing or going live.
- Service level agreement (SLA)
- Contractual commitments on uptime, support response times and incident resolution, usually backed by service credits. Banks should check that SLA targets match their own operational resilience obligations.
- SOC 2 Type II
- An independent audit report on how well a service provider's security and availability controls worked over a period of time, typically six to twelve months. It's a common starting point for vendor due diligence.
- Statement of work (SOW)
- The contract document that sets out exactly what an implementation partner or vendor will deliver, by when and at what price. Anything left out of it usually ends up as a change request.
- Systems integrator (SI)
- A third-party consulting firm that configures, integrates and migrates data onto a vendor's platform. SI fees often equal or exceed the software license cost in the first year.
- Total cost of ownership (TCO)
- The full cost of a system over its expected life, including licenses, implementation, integrations, infrastructure, internal staff and exit costs, not just the subscription fee.
D
E
F
I
M
P
R
S
T