Financial Software Buyer's Glossary
Plain-English definitions of the contract, pricing and compliance terms buyers run into when evaluating financial technology vendors.
- Configuration vs customization
- Configuration changes behavior using settings the vendor supports and upgrades; customization changes code or adds bespoke extensions. Heavy customization raises upgrade costs and is a leading cause of stalled replacements.
- Data residency
- A requirement, set by law, regulator or contract, that certain data be stored or processed inside a specific country or region. Rules vary widely, from strict in-country requirements in some Gulf and Asian markets to transfer-mechanism rules under the GDPR.
- Exit plan
- A documented, tested plan for moving off a vendor, covering data extraction formats, transition support and timelines. Many regulators expect one for critical outsourcing, and it should be negotiated before signing, not at renewal.
- False positive rate
- The share of alerts from a screening, monitoring or fraud system that turn out, after review, not to be suspicious. It drives analyst headcount, so ask vendors how it was measured and on whose data.
- Investment book of record (IBOR)
- A real-time view of positions, cash and exposures used by portfolio managers and traders, as opposed to the end-of-day accounting book of record. Platforms differ sharply in how they build and reconcile it.
- Material outsourcing
- An outsourcing arrangement a regulator considers critical to a firm's operations, which usually triggers notification, due diligence, audit-access and exit-planning obligations. Most cloud core, payments and compliance platforms fall into this category.
- Model validation
- Independent testing that a risk, fraud or credit model works as intended, is conceptually sound and performs on your population. Supervisors increasingly expect it for vendor models as well as in-house ones.
- Per-user (seat) licensing
- A pricing model that charges per named or concurrent user, often with different rates for full, light and read-only seats. Count operations, compliance and support users as well as front-office staff when modeling cost.
- Right to audit
- A contract clause that lets the customer, its auditors and its regulators inspect the vendor's controls, premises or records. Financial regulators commonly require it for outsourced critical services.
- Service level agreement (SLA)
- Contractual commitments on availability, incident response and resolution times, usually backed by service credits. Check how uptime is measured and whether the credits are meaningful against your actual losses from an outage.
- Software escrow
- An arrangement in which a vendor's source code and documentation are held by a third party and released to the customer if the vendor fails or stops supporting the product. It's more common for on-premise and hosted software than for multi-tenant SaaS.
- Statement of work (SOW)
- The contract document that defines what an implementation partner or vendor will deliver, by when, and on what assumptions. Vague assumptions in the SOW are the most common source of change orders and budget overruns.
- Straight-through processing (STP)
- Handling a transaction, application or onboarding case end to end without manual intervention. Vendors quote STP rates as a selling point, but the realistic rate depends on your data quality and risk appetite.
- Total cost of ownership (TCO)
- The full cost of a system over its expected life, typically five to ten years, including licenses, implementation, integrations, hosting, internal staff, upgrades and exit costs. It's the number to compare across vendors; first-year price isn't.
C
D
E
F
I
M
P
R
S
T