Financial Software Buyer's Glossary
Plain definitions of the contract, pricing, architecture and compliance terms financial institutions run into when they evaluate software vendors.
- Active-user pricing
- A license model that charges per customer or employee who logs in during a billing period, rather than per registered account. Check exactly how the contract defines 'active' and what happens when you go over your tier.
- Annual minimum commitment
- A floor on yearly fees that applies however little you use the product, which is common in per-check and per-transaction pricing. A low unit price paired with a high minimum can cost more than a higher unit price with no floor.
- API-first architecture
- A design in which every function of a system is exposed through documented APIs, so it can be integrated, extended or partly replaced without vendor customization. It supports gradual modernization but shifts more integration work to the buyer.
- Concentration risk (third-party)
- The risk that comes from depending heavily on one vendor or cloud provider, or that many institutions depend on the same one. Regulations such as the EU's DORA require firms to identify and manage it.
- Customer due diligence (CDD)
- The process of identifying customers, verifying their identity and understanding the purpose and risk of the relationship. Enhanced due diligence (EDD) adds deeper checks for higher-risk customers such as politically exposed persons.
- Data residency
- A requirement that certain data be stored, and sometimes processed, within a specific country or region. Rules differ widely, for example between the EU, India, Saudi Arabia and Indonesia, so confirm a vendor's hosting locations against every market you operate in.
- Exit assistance clause
- A contract term that obliges the vendor to help you move to another provider, including data export in usable formats, continued service during transition and agreed fees. Many supervisors expect exit plans for critical outsourced services.
- False positive rate
- The share of alerts from screening, monitoring or fraud systems that turn out not to be genuine risks after investigation. It drives analyst headcount, so ask vendors to measure it on your own data during a proof of concept.
- ISO/IEC 27001
- An international standard for information security management systems that vendors can be certified against. Certification shows a managed security program exists, but buyers should still check its scope and the statement of applicability.
- Material outsourcing
- Outsourcing of a function important enough that a failure would significantly affect the institution's operations, customers or compliance. It typically triggers regulator notification, stricter due diligence and specific contract terms, and those requirements vary by jurisdiction.
- Parallel run
- A migration phase in which the old and new systems process the same transactions side by side so results can be reconciled before cutover. It lowers go-live risk but adds staff workload and dual running costs for its duration.
- Payments on behalf of (POBO)
- A treasury structure in which one entity, often a central treasury or in-house bank, makes payments for group subsidiaries from its own accounts. Its legal and tax treatment varies by country and needs specialist review.
- Perpetual KYC (pKYC)
- An approach that refreshes customer risk profiles continuously when data changes or events occur, instead of on fixed review cycles. It can reduce periodic review workload but increases screening volumes and per-check costs.
- Right to audit
- A clause that lets the institution, its auditors and its regulators inspect the vendor's controls, premises and records. Financial regulators in the EU, UK, India, Singapore and elsewhere generally expect it in material outsourcing contracts.
- Service level agreement (SLA)
- Contractual commitments on availability, support response and resolution times, with the service credits owed if the vendor misses them. Credits are often capped at a small share of monthly fees, so they rarely cover the business impact of an outage.
- SOC 2 Type II report
- An independent auditor's report on how well a service provider's security and availability controls operated over a period, usually 6 to 12 months. It's stronger evidence than a Type I report, which only covers a single point in time.
- Source code escrow
- An arrangement in which a third party holds a vendor's source code and releases it to the customer if defined events occur, such as insolvency. It matters most for on-premise or heavily customized software.
- Statement of work (SOW)
- The contract document that defines implementation scope, deliverables, milestones, responsibilities and fees. Anything missing from the SOW usually becomes a paid change request later.
- Total cost of ownership (TCO)
- The full cost of a system over its contract life, including licenses, implementation, integration, hosting, internal staff time, upgrades and exit costs. It's the right number to compare across vendors, and the license fee alone usually isn't.
A
C
D
E
F
I
M
P
R
S
T