Guide

Fintech Glossary

The complete dictionary of financial operations, reconciliation, and ledger infrastructure terms.

Terms starting with A

ACH (Automated Clearing House)#

A batch-processing network for US electronic funds transfers that operates on a T+1 or T+2 settlement cycle.

ACH processes two types of transactions: Direct Deposits (credits) for payroll and vendor payments, and Direct Payments (debits) for bill pay and recurring charges
Settlement typically takes 1-2 business days, though Same-Day ACH settles within hours for an additional fee
ACH is governed by NACHA (National Automated Clearing House Association) rules and processes over 30 billion transactions annually
Common reconciliation challenges include batch timing delays, return codes (R01-R85) that require exception handling, and matching individual transactions within batch settlements
ACH competes with faster payment rails like RTP (Real-Time Payments) and FedNow, though ACH remains dominant for recurring and bulk payments due to lower cost

AI Reconciliation #

The use of machine learning models to probabilistically match complex financial transactions and identify anomalies that deterministic rule-based engines miss.

AI reconciliation combines deterministic matching (exact field comparison) with probabilistic matching (fuzzy logic and ML models) to handle complex transaction patterns
Key capabilities include automated exception classification, anomaly detection for potential fraud, and confidence scoring that determines which matches need human review
Unlike rule-based systems, AI reconciliation adapts to new data patterns over time, reducing false positives and improving match rates without manual rule updates
Common techniques include natural language processing for remittance parsing, graph-based matching for N:M transaction relationships, and reinforcement learning for exception routing
AI reconciliation is most impactful at scale — the accuracy advantage over manual processes compounds as transaction volume and data source complexity increase

ARR (Annual Recurring Revenue)#

Annual Recurring Revenue (ARR) is the annualized value of active subscription contracts, representing the predictable revenue a SaaS or subscription business expects to receive over the next 12 months. ARR is calculated by summing all active recurring subscription values, normalized to an annual amount — a customer paying $5,000/month contributes $60,000 to ARR. It excludes one-time fees, professional services, and usage overages. ARR is the primary valuation metric for SaaS businesses and the foundation for calculating growth rates, retention metrics, and sales efficiency ratios.

Formula: ARR = sum of all active annual subscription values; for monthly contracts, multiply MRR by 12
ARR components: beginning ARR + new business ARR + expansion ARR - contraction ARR - churned ARR = ending ARR
Net new ARR (new + expansion - contraction - churn) is the most watched SaaS growth indicator and the basis for revenue forecasting
ARR must reconcile against billing system records — discrepancies between CRM-reported ARR and actual billed amounts indicate data quality issues
Deferred revenue and ARR are related but different: ARR is a forward-looking metric; deferred revenue is an accounting liability on the balance sheet
ARR per employee and ARR growth rate are key efficiency metrics used by investors to benchmark SaaS companies against peers
Reconciliation use case: monthly ARR bridge reconciliation verifies that reported ARR movements (new, expansion, churn) match underlying contract changes

Account Reconciliation #

The process of verifying that a specific financial account's balance in the general ledger matches the corresponding external statement (bank, credit card, or vendor) for a given period.

Account reconciliation compares internal account balances against external statements or counterparty records to ensure accuracy
Common types include bank reconciliation, intercompany reconciliation, credit card reconciliation, and vendor statement reconciliation
The reconciliation process identifies timing differences (transactions recorded in different periods), errors (incorrect amounts or mispostings), and fraudulent or unauthorized transactions
Regulatory requirements such as SOX and SOC 2 mandate regular account reconciliation with documented evidence of review and resolution
Automation reduces reconciliation from days to hours by eliminating manual spreadsheet matching and providing real-time exception visibility

Accounts Payable #

Accounts payable (AP) represents the outstanding amounts a business owes to its vendors and suppliers for goods and services received on credit. AP is a current liability on the balance sheet and a core component of working capital management. The AP process — invoice receipt, coding, approval, payment execution, and reconciliation — is one of the most automation-ready finance workflows, with modern platforms using OCR, AI matching, and workflow automation to eliminate manual data entry and reduce payment cycle times from weeks to days.

The AP lifecycle: receive invoice, validate against PO/receipt (two-way or three-way matching), code to GL accounts, route for approval, execute payment, reconcile
Three-way matching compares the purchase order, goods receipt, and invoice to prevent paying for undelivered or incorrect goods
AP aging reports categorize outstanding payables by due date (current, 30, 60, 90+ days) to manage cash flow and vendor relationships
Early payment discounts (e.g., 2/10 net 30) represent a significant cost savings opportunity — automation enables consistent capture of discount terms
Duplicate invoice detection prevents one of the most common AP errors: paying the same invoice twice due to re-submission or format differences
AP reconciliation verifies that the AP subledger balance matches the GL control account and that all payments clear the bank as expected
Days Payable Outstanding (DPO) measures how long a company takes to pay suppliers — optimizing DPO improves working capital without damaging vendor relationships

Accounts Receivable #

Accounts receivable (AR) represents the outstanding invoices and money owed to a business by its customers for goods or services delivered on credit. In fintech and financial operations, AR management encompasses the full order-to-cash cycle: invoicing, payment collection, cash application, credit management, and collections. Modern AR automation platforms use AI to optimize each stage, reducing DSO and improving cash flow predictability.

AR appears as a current asset on the balance sheet, representing expected future cash inflows
The AR process includes invoice generation, delivery, payment tracking, cash application, and collections
Days Sales Outstanding (DSO) is the primary metric for AR efficiency — lower DSO means faster cash collection
AR aging reports categorize outstanding invoices by how long they have been unpaid (30, 60, 90+ days)
Automated AR platforms handle dunning (payment reminders), credit scoring, and dispute resolution
Cash application — matching incoming payments to invoices — is the most automation-ready AR sub-process
AR factoring and invoice financing allow businesses to convert receivables into immediate working capital

Accrual #

An accounting method that records revenues and expenses when they are earned or incurred, regardless of when cash is actually received or paid.

Accrual accounting provides a more accurate picture of financial performance than cash-basis accounting.
Common accruals include accrued revenue (earned but not yet billed) and accrued expenses (incurred but not yet paid).
Accruals require adjusting journal entries at period-end to recognize transactions in the correct period.
Automating accrual calculations reduces manual effort and ensures consistent application of accounting policies.

Audit Trail #

An audit trail is a chronological record of every action, change, and decision made within a financial system — including who did what, when, and why. In reconciliation and financial operations, audit trails provide the evidence chain that auditors, regulators, and compliance teams require to verify that processes are operating correctly. Modern systems generate audit trails automatically as a byproduct of operations rather than requiring manual documentation.

Captures transaction creation, modifications, approvals, matching decisions, exception resolutions, and write-offs with timestamps and user IDs
Immutability is essential: audit trail entries must be append-only and tamper-evident, preventing after-the-fact modification of records
SOC 2 Type II and SOX 404 compliance require audit trails demonstrating consistent process execution and proper authorization controls
Retention requirements vary by regulation: SOX mandates 7 years, PCI DSS requires 1 year readily available, and bank regulations may require 5-10 years
Audit trails should capture not just the action but the context — what data the user saw, what options were available, and the rationale for the decision
Automated systems generate richer audit trails than manual processes because every matching decision, confidence score, and rule application is logged
Searchable audit trails enable rapid response to auditor queries, reducing audit preparation time from weeks to hours

Automated Payment Reconciliation #

Automated payment reconciliation uses software to match payment transactions from processors, banks, and internal systems without manual spreadsheet work. Instead of downloading CSVs from Stripe, Adyen, and bank portals and matching them row by row, automated systems ingest data via APIs, apply matching rules and ML models, and surface only genuine exceptions for human review. This transforms payment reconciliation from a multi-day batch process to a continuous, real-time operation that scales with transaction volume.

Data ingestion connects to PSPs, banks, and ERPs via APIs or file feeds, normalizing disparate formats into a common transaction schema
Rule-based matching handles exact matches on reference ID and amount; ML-based matching resolves fuzzy scenarios like split payments and fee deductions
Achieves 90-99% auto-match rates depending on data quality, reducing manual work from hours per day to minutes of exception review
Real-time reconciliation flags settlement failures, missing transactions, and fee discrepancies within minutes instead of days
Fee reconciliation automatically verifies that processor charges match contracted rate cards, catching overcharges that manual processes miss
Scales linearly with transaction volume — a system reconciling 1,000 transactions/day handles 100,000/day without additional headcount
ROI calculation: compare analyst hours eliminated, error reduction, and faster close against software cost and implementation effort

Terms starting with B

Balance Sheet Reconciliation #

Balance sheet reconciliation is the process of verifying that every account on the balance sheet — assets, liabilities, and equity — is supported by underlying documentation and matches source records. It is the primary control ensuring that reported financial position is accurate and complete. Each balance sheet account is reconciled by comparing the GL balance against subledger detail, third-party statements, or supporting schedules, with differences investigated and resolved before financial statements are finalized.

Scope covers all balance sheet accounts: cash, receivables, prepaids, fixed assets, payables, accrued liabilities, debt, and equity accounts
High-risk accounts (cash, receivables, intercompany) are typically reconciled monthly; lower-risk accounts may follow a quarterly rotation
Each reconciliation produces a rec report showing GL balance, supporting detail, identified differences, and sign-off by the preparer and reviewer
Common reconciling items include timing differences, in-transit deposits, outstanding checks, and unposted journal entries
SOX 404 compliance requires documented balance sheet reconciliations with evidence of management review for all material accounts
Automation platforms auto-match GL balances to subledger data and bank statements, surfacing only true exceptions for investigation
Stale or unresolved reconciling items should trigger escalation — they often indicate process breakdowns or errors that compound over time

Bank Reconciliation Automation #

Bank reconciliation automation uses software to match an organization's internal transaction records against bank statement data without manual intervention. Traditional bank reconciliation involves downloading bank statements, importing them into spreadsheets, and manually matching each transaction — a process that can take days for high-volume accounts. Automated bank reconciliation connects directly to bank APIs, applies matching rules and AI, and completes in minutes with 95%+ accuracy.

Connects to banks via APIs, Open Banking feeds, SFTP file imports, or direct Plaid integration
Auto-matches deposits, withdrawals, transfers, fees, and interest against internal records
Handles timing differences where bank posts transactions on different dates than internal records
Multi-bank reconciliation consolidates accounts across multiple banking partners into one view
Exception reporting highlights unmatched items with suggested resolutions and aging status
Supports multiple currencies with automatic FX rate lookup for cross-border transaction matching
Audit trail captures every match decision, manual override, and approval for compliance requirements

Banking-as-a-Service (BaaS)#

APIs that enable non-banks to offer banking products by connecting to licensed financial institutions.

Provides regulatory umbrella and bank charter access
Exposes core banking features via API (accounts, cards, payments)
Examples: Unit, Treasury Prime, Bond

Terms starting with C

Cash Application #

Cash application is the accounts receivable process of matching incoming customer payments to their corresponding open invoices. This critical AR function determines which invoices a payment covers, handles partial payments and overpayments, and updates the ledger accordingly. Automated cash application uses AI and OCR to parse remittance advice, match payments with 95%+ accuracy, and reduce unapplied cash by up to 80%.

Processes payments from multiple channels: ACH, wire transfers, checks, lockbox, credit cards, and digital wallets
AI-powered matching handles complex scenarios like partial payments, combined payments, and payments without remittance data
OCR and NLP parse remittance advice documents in various formats (PDF, EDI, email) to extract invoice references
Reduces Days Sales Outstanding (DSO) by accelerating the invoice-to-cash cycle
Exception queues route unmatched payments to AR analysts with candidate matches and confidence scores
Integrates with ERP systems (NetSuite, SAP, QuickBooks) for automatic posting and ledger updates
Key metrics: match rate, unapplied cash percentage, average time-to-apply, exception resolution rate

Chart of Accounts #

A structured list of all accounts used in the general ledger, organized by category (assets, liabilities, equity, revenue, expenses).

Serves as the foundation for all financial reporting and analysis
Each account has a unique number and name following a hierarchical structure
Standard frameworks include GAAP and IFRS classifications
Proper COA design enables accurate financial consolidation and reporting

Continuous Close #

Continuous close (also called continuous accounting) is the practice of distributing traditional period-end close activities throughout the month rather than batching them into a frantic end-of-period sprint. Instead of reconciling all accounts, posting all adjustments, and reviewing all reports in the last 5-10 days of the period, continuous close performs these tasks daily or in real time. The result: month-end becomes a formality — a final review and sign-off rather than a multi-day operational bottleneck.

Core principle: any close task that can be done on day 5 of the month should not wait until day 30 — front-load what the data supports
Daily reconciliation of high-volume accounts (cash, payments, intercompany) eliminates the largest close bottleneck
Real-time transaction matching and automated journal entries reduce the adjustment backlog that accumulates at period end
Continuous close reduces close cycle from the industry average of 6-10 days to 1-3 days, with leaders achieving virtual day-one close
Prerequisites: automated reconciliation, real-time data feeds from all source systems, and workflow tools that track task completion daily
Management benefit: leadership gets reliable preliminary financials by day 2-3 instead of waiting 10+ days for final numbers
Continuous close does not eliminate the need for period-end cutoff procedures — it reduces the volume of work remaining at cutoff

Terms starting with D

Days Sales Outstanding (DSO)#

Days Sales Outstanding (DSO) measures the average number of days it takes a company to collect payment after a sale. Calculated as (Accounts Receivable / Total Credit Sales) x Number of Days, DSO is a key indicator of AR efficiency and cash flow health. Lower DSO means faster cash collection, improved working capital, and reduced credit risk. Fintech companies typically target DSO below 30 days through automated invoicing, payment reminders, and cash application.

Formula: DSO = (Accounts Receivable / Net Credit Sales) x Number of Days in Period
Industry benchmarks vary: SaaS companies average 40-60 days, while B2B manufacturing can exceed 90 days
Reducing DSO by even 5-10 days can significantly improve working capital and reduce borrowing needs
Key drivers of high DSO: manual invoicing, slow cash application, weak collections processes, and dispute handling delays
Automated AR platforms reduce DSO through instant invoice delivery, payment reminders, and AI-powered cash application
Best-in-class DSO improvement: eliminate paper checks, offer multiple payment methods, and automate matching
Track DSO trends monthly — sudden increases may signal customer credit issues or process breakdowns

Deferred Revenue #

Deferred revenue (also called unearned revenue or contract liability) is a balance sheet liability representing cash received from customers for goods or services not yet delivered. Under ASC 606 and IFRS 15, revenue cannot be recognized until the performance obligation is satisfied — so an annual SaaS subscription paid upfront creates 12 months of deferred revenue that converts to recognized revenue monthly. Accurate deferred revenue tracking is critical for SaaS and subscription businesses because it directly impacts reported revenue, cash flow timing, and key metrics like ARR and net retention.

Recorded as a current liability (portion to be recognized within 12 months) or long-term liability on the balance sheet
SaaS recognition: a $120K annual contract paid upfront creates $120K deferred revenue, recognized at $10K/month as service is delivered
Revenue recognition schedules (rev rec waterfalls) track the systematic conversion of deferred revenue to earned revenue over time
Contract modifications — upgrades, downgrades, cancellations, extensions — require re-calculation of the deferred revenue balance and recognition schedule
Deferred revenue reconciliation compares billing system records against GL balances to catch missed or duplicated recognition entries
Auditors scrutinize deferred revenue because premature recognition inflates reported revenue — it is a common area of financial restatements
Key related metrics: current remaining performance obligation (cRPO) and total RPO, which represent committed but unrecognized revenue

Disbursement #

A disbursement is the payment or distribution of funds from a business to external parties such as vendors, employees, or partners. It represents the outflow of cash from company accounts.

Includes vendor payments, payroll, refunds, and partner distributions
Requires proper authorization, documentation, and reconciliation controls
Tracked against accounts payable records to ensure completeness
Subject to timing differences between initiation and bank settlement

Double-Entry Ledger #

A double-entry ledger is a bookkeeping system where every financial transaction is recorded as two equal and opposite entries — a debit and a credit — across different accounts. This fundamental accounting principle ensures the balance equation (Assets = Liabilities + Equity) always holds and that every dollar is accounted for twice. In fintech systems, double-entry ledgers provide the integrity guarantees needed for payment platforms, wallet systems, and financial marketplaces where transaction accuracy is non-negotiable.

Every entry has a matching counterpart: debit one account, credit another for the same amount — the books always balance by construction
The accounting equation (Assets = Liabilities + Equity) is enforced at the database level in well-designed fintech ledgers
Double-entry makes errors self-revealing: if debits do not equal credits for any transaction, the system rejects it immediately
Fintech implementation typically uses account pairs: user wallet (debit) and platform liability (credit) for deposit flows
Compared to single-entry systems, double-entry provides built-in audit trails and makes reconciliation against external records straightforward
Modern implementations use immutable append-only logs with double-entry constraints enforced in the write path, not post-hoc
Multi-currency double-entry ledgers maintain separate debit/credit pairs per currency and record FX conversion as explicit cross-currency journal entries

Terms starting with E

Embedded Finance #

The integration of financial services (lending, payments, insurance) into non-financial applications.

Allows platforms like SaaS or marketplaces to offer financial products.
Requires robust infrastructure for compliance and ledgering.
Examples include a ride-sharing app offering debit cards to drivers.

Embedded Payments #

Embedded payments integrate payment acceptance directly into software platforms, enabling SaaS companies and marketplaces to process transactions without redirecting users to third-party payment pages. Instead of being a separate checkout step, the payment flow is native to the application experience. For the platform, embedded payments create a new revenue stream through payment facilitation fees while increasing user retention. For finance operations, they add complexity — platforms must reconcile their share of each transaction, manage split settlements, and track funds flowing through sub-merchant accounts.

Payment facilitation (PayFac) model allows platforms to onboard sub-merchants and process payments under their own merchant ID
Split settlement divides each transaction between the platform fee and the sub-merchant payout, requiring precise reconciliation of both sides
Platforms must reconcile gross transaction volume, platform fees retained, processor fees deducted, and net payouts to sub-merchants
Regulatory requirements include KYC/KYB for sub-merchants, PCI DSS compliance for card data handling, and money transmission licensing in some jurisdictions
Embedded payment revenue typically ranges from 0.2-0.5% of gross transaction volume for the platform after processor costs
Reconciliation complexity increases with multi-currency support, refund handling, chargeback liability allocation, and reserve holdbacks
Key infrastructure providers: Stripe Connect, Adyen for Platforms, PayPal Commerce Platform, and white-label PayFac solutions

Exception Handling #

Exception handling in financial operations is the workflow for identifying, investigating, and resolving transactions that fail to match during automated reconciliation. Exceptions are the residual items after matching rules and ML models have processed everything they can — they represent genuine discrepancies, data quality issues, or edge cases that require human judgment. Effective exception handling transforms these from an unstructured backlog into a prioritized, context-rich queue that operations teams can resolve efficiently.

Exception categories include: amount mismatches, missing counterparty records, duplicate transactions, timing overages, and format/reference errors
Priority scoring ranks exceptions by financial impact, age, and likelihood of resolution — high-value items surface first
Each exception should include full context from both source and target records, suggested resolution actions, and similar historical resolutions
Aging analysis tracks how long exceptions remain open — SLA targets typically require resolution within 3-5 business days for material items
Root cause tagging on resolved exceptions feeds back into matching rules, systematically reducing future exception volume
Segregation of duties requires different people to investigate exceptions and approve write-offs or adjustments above threshold amounts
Exception rate (unmatched items / total items) is the primary reconciliation quality KPI — best-in-class targets below 2%

Terms starting with F

Financial Close #

The process of finalizing all financial transactions and records for a specific accounting period, ensuring accuracy and completeness before producing financial statements.

Financial close occurs at the end of each accounting period (monthly, quarterly, annually).
Involves reconciling accounts, reviewing adjusting entries, and ensuring all transactions are recorded.
A faster close cycle improves decision-making by providing timely financial visibility.
Modern fintech operations aim for continuous close capabilities to reduce the traditional close period from weeks to days.

Financial Data Hub #

A centralized platform that ingests, normalizes, and stores financial data from disparate sources (banks, gateways, ERPs) to provide a single source of truth for reporting.

A financial data hub normalizes disparate data formats from banks, payment processors, ERPs, and internal systems into a unified schema
Core functions include real-time data ingestion via webhooks and APIs, historical data backfill, schema versioning, and data quality monitoring
Eliminates the N-to-N integration problem — instead of each system connecting to every other system, all connect to the central hub
Enables downstream analytics, reconciliation, and reporting by providing a single source of truth for financial data across the organization
Data governance features typically include access controls, audit logging, data lineage tracking, and retention policies for regulatory compliance

Financial Events System #

An architecture based on Event Sourcing where the system stores the sequence of immutable events rather than just the current state.

Built on Event Sourcing principles where the immutable event log is the source of truth and current state is derived by replaying events
Financial events include payments initiated, charges settled, refunds processed, disputes opened, and settlements completed
Enables temporal queries — you can reconstruct the exact state of any account at any point in time by replaying events up to that timestamp
CQRS (Command Query Responsibility Segregation) is commonly used alongside event sourcing, separating write operations from read projections for performance
Critical for audit compliance because the event log provides a complete, immutable history of every financial state change

Financial Operations Infrastructure #

Backend systems that handle data ingestion, ledgering, reconciliation, and controls for fintech products.

Sits between banking partners and product logic
Ensures scalability and accuracy of financial data
Reduces manual operations workload

Fintech Infrastructure #

The backend architectural components, including ledgers, payment rails, and compliance tools, that enable the building and scaling of financial applications.

Core layers include Banking-as-a-Service (BaaS), payment processing, ledger systems, reconciliation engines, compliance/KYC, and analytics
Unlike consumer fintech apps, infrastructure companies provide the backend plumbing that other fintechs build on — analogous to AWS for cloud computing
Key infrastructure decisions include build vs buy for each layer, single-vendor vs best-of-breed strategy, and on-premise vs cloud deployment
Modern fintech infrastructure is API-first, enabling programmatic access to banking, payments, and financial operations capabilities
Infrastructure reliability requirements are stringent — downtime directly impacts money movement, making high availability and disaster recovery critical

Fintech Ledger #

A fintech ledger is a purpose-built system of record designed for platforms that hold, move, or manage money at scale. Unlike traditional general ledgers built for monthly reporting, fintech ledgers operate in real time, process high transaction volumes with sub-second latency, and provide the balance accuracy required for payment authorization, wallet management, and regulatory reporting. They combine double-entry accounting principles with software engineering patterns like event sourcing, idempotency, and API-first design.

Designed for real-time balance queries — supports instant available-balance checks needed for payment authorization and fund holds
Event-sourced architecture stores every state change as an immutable event, enabling full transaction replay and point-in-time balance reconstruction
Idempotency keys prevent duplicate entries from network retries, a critical requirement for payment processing at scale
Multi-tenant ledger architectures isolate balances per customer, sub-merchant, or entity while sharing infrastructure
Supports complex money movement patterns: holds, pending settlements, split payments, refunds, and chargebacks as first-class transaction types
Built-in reconciliation hooks compare ledger balances against bank and processor positions, surfacing drift before it becomes a financial control issue
Regulatory compliance features include immutable audit trails, balance attestation endpoints, and configurable retention policies

Terms starting with G

General Ledger #

A general ledger (GL) is the master accounting record that contains all financial transactions of a business, organized by account. It serves as the single source of truth for financial reporting, using double-entry bookkeeping where every transaction has equal debit and credit entries. In fintech infrastructure, operational ledgers extend the GL concept with real-time event processing, immutability, and API-first architectures designed for high-volume transaction environments.

Organizes transactions into accounts following the chart of accounts structure (assets, liabilities, equity, revenue, expenses)
Double-entry bookkeeping ensures the accounting equation (Assets = Liabilities + Equity) always balances
Subledgers (AR, AP, inventory) feed detailed transactions into summary GL accounts
GL reconciliation compares subledger totals against GL balances to catch posting errors
Modern fintech ledgers add real-time balance tracking, event sourcing, and multi-currency support
Journal entries record transactions in the GL with date, accounts, amounts, and descriptions
The GL is the foundation for all financial statements: balance sheet, income statement, and cash flow statement

Terms starting with I

Intercompany Reconciliation #

Intercompany reconciliation is the process of matching and verifying financial transactions between separate legal entities within the same corporate group. These transactions — including management fees, shared service allocations, intercompany loans, and transfer pricing adjustments — must balance perfectly before consolidation. Unresolved intercompany differences directly impact consolidated financial statements and can trigger audit findings. Automation eliminates the manual back-and-forth between entity controllers by providing a shared matching workspace with real-time visibility.

Eliminates intercompany balances through matching and netting before consolidation, preventing double-counting of revenue and expenses
Common intercompany transaction types: management fees, cost allocations, intercompany loans and interest, inventory transfers, and royalty payments
Multi-currency intercompany transactions require consistent FX rate policies and handling of translation gains/losses at elimination
IFRS 10 and ASC 810 require full elimination of intercompany profits, receivables, and payables in consolidated statements
Typical pain point: entity A records the transaction in March, entity B records it in April — period mismatch creates reconciliation exceptions
Intercompany reconciliation is the top bottleneck in month-end close for companies with 5+ entities, often consuming 30-40% of close time
Automated platforms provide counterparty confirmation workflows where both entities validate transactions before close, reducing disputes

Internal Ledger #

A 'shadow' ledger representing the business intent of a transaction, providing immediate feedback separate from the bank's settlement reality.

An internal ledger records what the business intended to happen with each transaction, separate from what external systems like banks and processors report
Acts as the first source of truth for financial operations — discrepancies between internal ledger and external records surface through reconciliation
Typically implemented as a double-entry system where every transaction creates at least one debit and one credit entry
Essential for businesses with embedded finance where transaction volume exceeds what can be tracked through bank statements alone
Internal ledgers enable real-time balance calculations, credit limit enforcement, and instant transaction validation before external settlement

Terms starting with J

Journal Entry #

A record of a financial transaction in an accounting system, documenting debits and credits to specific accounts in the general ledger.

Journal entries are the fundamental building blocks of double-entry bookkeeping, ensuring every transaction balances.
Each entry includes a date, account references, amounts (debit and credit), and a description or memo.
Manual journal entries require review and approval workflows to prevent errors and fraud.
Automated journal entry posting eliminates manual data entry and reduces month-end close time significantly.

Terms starting with K

KYC/KYB #

Know Your Customer (KYC) and Know Your Business (KYB) are regulatory compliance processes for verifying the identity of individuals and businesses before establishing financial relationships.

KYC applies to individual customers and includes identity verification, address verification, and risk assessment
KYB extends these requirements to business entities, verifying ownership structure, beneficial owners, and business legitimacy
Required by anti-money laundering (AML) regulations across most jurisdictions
Modern fintech platforms automate KYC/KYB through API integrations with identity verification providers

KYC/KYB #

Know Your Customer / Know Your Business. Regulatory processes to verify the identity of clients to prevent financial crime.

Mandatory for most fintech applications.
KYC verifies individuals; KYB verifies business entities.
Often integrated via third-party identity providers.

Terms starting with L

Ledger-as-a-Service (LaaS)#

Infrastructure-as-Code for accounting that provides pre-built, immutable double-entry accounting primitives via API.

LaaS provides pre-built, immutable double-entry ledger infrastructure via API, eliminating the need to build financial record-keeping from scratch
Core capabilities include multi-currency support, multi-entity management, programmable accounting rules, and real-time balance queries
Analogous to Database-as-a-Service — abstracts away the complexity of building and maintaining financial data infrastructure
Particularly valuable for fintechs that need ledger capabilities but where the ledger itself is not their core product differentiation
Compliance features typically include SOC 2 certification, immutable audit trails, and configurable retention policies

Ledgering #

Ledgering is the practice of recording, tracking, and maintaining financial transactions in a structured system of record — a ledger. In fintech infrastructure, ledgering extends beyond traditional accounting to encompass real-time balance management, event-sourced transaction histories, and multi-currency position tracking for platforms that move money. A well-designed ledger is the single source of truth for every balance, hold, and movement in the system, enabling accurate reconciliation, instant reporting, and regulatory compliance.

Modern fintech ledgers use double-entry principles: every transaction creates equal and opposite debit and credit entries across accounts
Event-sourced ledgers store immutable transaction events and derive balances on demand, providing a complete audit trail by design
Real-time balance tracking prevents overdrafts and ensures available-balance accuracy for payment authorization decisions
Multi-currency ledgering maintains separate balances per currency with explicit FX conversion entries when funds cross currency boundaries
Ledger design must handle holds (authorized but unsettled funds), pending transactions, and reversals without corrupting running balances
High-scale platforms process millions of ledger entries per day, requiring append-only writes, idempotency keys, and eventual consistency patterns
Reconciliation between the operational ledger and external bank/processor records is the primary control for detecting balance drift

Terms starting with M

MRR (Monthly Recurring Revenue)#

Monthly Recurring Revenue (MRR) is the normalized monthly value of all active subscription revenue, providing a real-time view of a SaaS business's revenue run rate. MRR standardizes subscriptions of varying lengths and billing frequencies into a consistent monthly figure — annual contracts are divided by 12, quarterly by 3. MRR is the operational heartbeat of subscription businesses, used for monthly performance tracking, churn detection, and short-term forecasting where ARR is too coarse a measure.

Formula: MRR = sum of monthly-normalized values of all active subscriptions; annual contracts contribute (annual value / 12) per month
MRR movement categories: new MRR (new customers), expansion MRR (upgrades/add-ons), contraction MRR (downgrades), and churned MRR (cancellations)
Net MRR growth rate = (new + expansion - contraction - churn) / beginning MRR — the single metric that shows business momentum
MRR differs from recognized revenue: MRR is a management metric; recognized revenue follows ASC 606 rules with potential timing differences
Quick ratio = (new MRR + expansion MRR) / (contraction MRR + churned MRR) — measures growth efficiency; >4 indicates healthy SaaS
MRR reconciliation compares CRM/billing system MRR calculations against actual invoiced amounts to catch pricing errors and missed cancellations
Cohort-based MRR analysis tracks revenue retention by customer signup month, revealing long-term retention trends invisible in aggregate numbers

Month-End Close #

Month-end close is the accounting process of finalizing all financial transactions, reconciling accounts, and preparing financial statements at the end of each month. This critical finance operations cycle typically involves closing subledgers, reconciling bank and intercompany accounts, posting adjusting journal entries, and generating trial balance and financial reports. Modern continuous close practices use automation to reduce the close from 10-15 days to 1-3 days.

Standard close checklist: close AP/AR, reconcile bank accounts, post accruals, reconcile intercompany, generate financials
The average mid-market company takes 6-10 business days to close; best-in-class achieves 1-3 days
Bottlenecks include manual reconciliation, late vendor invoices, intercompany eliminations, and review cycles
Continuous close practices distribute close tasks throughout the month instead of batching at period end
Automation targets: bank reconciliation, intercompany matching, accrual calculations, and variance analysis
Close management software tracks task completion, dependencies, and reviewer sign-offs
Faster close improves decision-making by providing timely financial data to leadership

Multi-Currency Ledger #

A ledger system that handles FX revaluation, maintaining both the native transaction currency and a normalized base reporting currency.

Records transactions in both the original (native) currency and a functional (reporting) currency, maintaining the exchange rate applied at the time of recording
FX revaluation recalculates foreign currency balances at current exchange rates, creating unrealized gain/loss entries in the ledger
Multi-currency reconciliation must account for rate differences between the time a transaction is initiated, processed, and settled
Common challenges include handling currency pairs with high volatility, rounding differences across systems, and regulatory requirements for FX rate documentation
Enterprise systems typically support both spot rates for individual transactions and period-end rates for balance revaluation

Multi-Entity Ledger #

A database architecture designed to support organizations with multiple legal entities, allowing for strict data segregation and consolidated reporting.

Supports complex organizational hierarchies
Enables inter-company transfers and settlement
Critical for marketplaces and platforms

Terms starting with O

Operational Ledger #

The high-volume transactional source of truth that powers product logic, distinct from the general ledger used for accounting.

Real-time balance updates for users
Handles granular metadata needed for product features
Feeds aggregated data to the General Ledger (ERP)

Terms starting with P

Payment Gateway #

A payment gateway is the technology layer that securely transmits payment data between a merchant's application and the payment processor or acquiring bank. It handles the real-time authorization request — encrypting card data, routing it through card networks (Visa, Mastercard), and returning an approval or decline response in milliseconds. Beyond basic authorization, modern payment gateways offer tokenization, fraud screening, multi-currency support, and alternative payment method integration, serving as the critical entry point for all payment transactions in an e-commerce or platform stack.

Authorization flow: gateway encrypts card data, sends to processor, processor routes to card network, issuing bank approves/declines, response returned in <2 seconds
Tokenization replaces sensitive card numbers with non-reversible tokens, reducing PCI DSS scope for merchants storing payment credentials
Gateway fees typically include per-transaction charges ($0.10-0.30) plus percentage fees (2.4-2.9%) that vary by card type, region, and volume
Hosted payment pages vs. embedded forms vs. direct API integration — each approach has different PCI compliance implications and UX tradeoffs
Multi-currency gateways handle dynamic currency conversion, local acquiring, and cross-border fee optimization for international merchants
Gateway settlement reports are the primary data source for payment reconciliation, containing transaction IDs, amounts, fees, and settlement dates
Redundancy strategy: integrating multiple gateways provides failover capability and leverage for fee negotiation through competitive routing

Payment Lifecycle Automation #

The use of Finite State Machines (FSM) to strictly enforce valid transitions for a payment from initiation to settlement and reconciliation.

Uses Finite State Machines (FSM) to enforce valid payment state transitions — e.g., a payment can move from authorized to captured but not from refunded to authorized
Automates the complete payment lifecycle: initiation, authorization, capture, settlement, reconciliation, and exception handling
Reduces manual intervention by automatically handling retries for failed transactions, routing to fallback processors, and escalating exceptions
State machine approach prevents impossible states and ensures every payment has a deterministic, auditable path from initiation to resolution
Integration with reconciliation ensures each lifecycle stage is matched against external records in real-time

Payment Operations #

The operational workflows required to move money, including authorization, capture, settlement, and exception handling.

Involves managing relationships with payment processors and banks.
Includes handling returns, chargebacks, and failed payments.
Modern payment ops relies on API-driven infrastructure.

Payment Orchestration #

Payment orchestration is the technology layer that routes payment transactions across multiple processors, acquirers, and payment methods through a single integration point. Instead of building separate integrations for Stripe, Adyen, PayPal, and local payment methods, an orchestration layer abstracts the complexity and dynamically selects the optimal route based on cost, approval rates, and availability. For finance operations, orchestration simplifies reconciliation by normalizing transaction data across all processors into a unified format.

Smart routing selects the processor most likely to approve each transaction based on card type, geography, amount, and historical success rates
Failover logic automatically retries declined transactions on alternate processors, recovering 2-5% of otherwise lost revenue
Unified reporting normalizes settlement data, fee structures, and transaction statuses across all connected PSPs for simplified reconciliation
Vault-based tokenization stores card credentials once and routes tokens to any connected processor, reducing PCI scope
Cost optimization routes transactions to the processor with the lowest interchange + processor fee for each card type and region
Cascading payment flows handle 3DS authentication, local payment methods (iDEAL, Boleto, UPI), and alternative payment types through a single API
Reconciliation benefit: one data format across all processors eliminates the need for per-PSP normalization scripts and reduces matching exceptions

Payment Rail #

The underlying network infrastructure (ACH, Wire, RTP, FedNow) facilitating funds movement, each with distinct speed, cost, and risk profiles.

Major US payment rails include ACH (batch, 1-2 day settlement), Wire (real-time, irrevocable), RTP (real-time, 24/7), and FedNow (instant, Federal Reserve operated)
Each rail has different cost structures, speed guarantees, reversibility rules, and transaction limits that affect payment routing decisions
Card networks (Visa, Mastercard) are payment rails for card-based transactions, with their own settlement cycles and interchange fee structures
Cross-border payments involve multiple rails and correspondent banks, creating reconciliation complexity from FX conversion and intermediary fees
Payment orchestration layers abstract away rail-specific complexity, routing transactions to the optimal rail based on cost, speed, and availability

Payment Reconciliation #

Payment reconciliation is the process of verifying that payment transactions recorded in internal systems match the corresponding records from payment processors, banks, and acquirers. For fintechs processing thousands of daily transactions through Stripe, Adyen, PayPal, and other PSPs, payment reconciliation ensures every charge, refund, chargeback, and fee is accurately accounted for. Automated payment reconciliation eliminates manual CSV matching and catches discrepancies in real time.

Matches payment processor settlement reports against internal order/transaction records
Handles complex payment scenarios: partial refunds, chargebacks, currency conversion, and processor fees
Multi-PSP reconciliation normalizes data formats across Stripe, Adyen, Braintree, PayPal, and others
Fee reconciliation verifies processor charges match contracted rates and flags overcharges
Settlement timing differences (T+1, T+2, T+3) require date-aware matching logic
Real-time reconciliation alerts operations teams to settlement failures or missing transactions immediately
Integration with accounting systems ensures reconciled data flows directly to GL and financial reports

Payout Reconciliation #

Payout reconciliation is the process of verifying that funds disbursed to merchants, sellers, service providers, or partners match the expected amounts based on transaction records, fee schedules, and contractual terms. For marketplaces and platforms that facilitate payments between buyers and sellers, payout reconciliation ensures that every dollar collected is correctly split, fees are accurately deducted, and the right amount reaches each recipient. Errors in payout reconciliation directly impact partner trust and can create financial exposure if overpayments go undetected.

Matches gross transaction amounts against fee deductions, reserves, adjustments, and net payout amounts for each recipient
Marketplace complexity: each transaction may split across platform commission, seller payout, tax withholding, and payment processor fees
Timing reconciliation tracks the lag between transaction capture and actual payout delivery, which varies by payout schedule (daily, weekly, threshold-based)
Multi-currency payouts require reconciling FX conversion rates applied at settlement against expected rates, flagging adverse rate deviations
Refund and chargeback impact: payouts must be adjusted when transactions are reversed — reconciliation verifies these clawbacks are correctly applied
Reserve reconciliation tracks holdback amounts, release schedules, and ensures reserves are returned to sellers per contractual terms
Key KPIs: payout accuracy rate, average time-to-payout, dispute rate, and variance between expected and actual payout amounts

Terms starting with R

Real-Time Reconciliation #

An event-driven reconciliation model that processes webhooks and instant payment notifications immediately rather than waiting for end-of-day batch files.

Processes reconciliation continuously via event streams and webhooks rather than in scheduled batch runs
Detects discrepancies within seconds of a transaction occurring, compared to days or weeks with traditional batch reconciliation
Requires event-driven architecture — the reconciliation engine subscribes to transaction events from all data sources
Enables real-time cash position visibility, immediate exception alerting, and continuous close workflows
Most impactful for high-volume businesses where batch reconciliation backlogs would accumulate faster than they can be processed

Reconciliation #

Reconciliation is the process of comparing two or more sets of financial records to ensure they are consistent and accurate. In fintech and financial operations, reconciliation typically involves matching internal transaction records against external statements from banks, payment processors, or counterparties. Automated reconciliation uses AI and rule-based matching to process thousands of transactions per second, flagging discrepancies as exceptions for human review.

Compares internal ledger entries against external bank statements, PSP reports, or ERP data to identify mismatches
Modern reconciliation engines use machine learning to handle fuzzy matching, partial payments, and timing differences
Key reconciliation types include bank reconciliation, payment reconciliation, intercompany reconciliation, and balance sheet reconciliation
Automated reconciliation reduces month-end close from days to hours by eliminating manual spreadsheet matching
Exception handling workflows route unmatched transactions to operations teams with full context and suggested resolutions
Compliance requirements (SOC 2, SOX) mandate regular reconciliation with documented audit trails
Real-time reconciliation enables continuous close practices instead of periodic batch processing

Reconciliation Automation #

The process of automatically matching transactions across multiple systems (banks, processors, internal records) to identify discrepancies.

Uses rules and algorithms to match high volumes
Reduces manual spreadsheet work
Improves financial accuracy and audit readiness

Reconciliation Engine #

A backend state machine that compares financial datasets and manages the lifecycle of a transaction's verification state from ingestion to matching.

Core components include data ingestion, normalization, matching algorithms, confidence scoring, and exception management
Matching algorithms range from deterministic (exact field comparison) to probabilistic (fuzzy matching, ML-based scoring) for complex transaction patterns
Handles match types including 1:1 (single transaction to single record), 1:N (one payment to many transactions), and N:M (many-to-many relationships)
Exception routing uses confidence thresholds — high-confidence matches are auto-approved, low-confidence items route to human review with suggested resolutions
Performance at scale is critical — enterprise reconciliation engines process millions of transactions daily with sub-second matching latency

Reconciliation Exceptions #

Reconciliation exceptions are discrepancies identified during the reconciliation process that require investigation and resolution. They occur when matched records have differences in amounts, dates, or other attributes, or when transactions cannot be matched at all.

Exceptions are categorized by type: amount variances, timing differences, missing transactions, and duplicate entries
Exception management workflows route items to appropriate reviewers based on type, amount, and priority
Resolution involves investigation, adjustment entries, write-offs, or escalation depending on root cause
Exception metrics including volume, aging, and resolution time are key indicators of reconciliation health

Remittance Advice #

Remittance advice is a document sent by a payer to a payee that identifies which invoices are being paid with an accompanying payment. It enables accurate cash application by providing invoice-level detail.

Typically includes invoice numbers, amounts, and any adjustments or deductions
May arrive via email, EDI, or alongside wire/ACH payment details
OCR and AI technologies automate extraction of remittance data
Critical for accurate cash application when payments cover multiple invoices

Revenue Recognition #

Revenue recognition determines when and how revenue is recorded in financial statements, governed by accounting standards ASC 606 (US GAAP) and IFRS 15. For SaaS and subscription businesses, revenue recognition is complex because payment timing often differs from when the service is delivered. The five-step ASC 606 framework requires identifying performance obligations, determining transaction price, and recognizing revenue as obligations are satisfied — not simply when cash is collected.

ASC 606 five-step model: identify contract, identify obligations, determine price, allocate price, recognize revenue
SaaS revenue is typically recognized ratably over the subscription period (e.g., $12,000/year = $1,000/month)
Deferred revenue (contract liability) represents payments received before the performance obligation is fulfilled
Multi-element arrangements require allocating total contract value across separate performance obligations
Usage-based and consumption pricing models recognize revenue as the customer consumes the service
Contract modifications (upgrades, downgrades, cancellations) trigger re-evaluation of revenue recognition
Automated revenue recognition systems handle complex scenarios and maintain audit-ready compliance documentation

Terms starting with S

SOC 2 Compliance #

An auditing procedure ensuring a service provider securely manages data to protect the interests of the organization and the privacy of its clients, critical for fintech vendors.

SOC 2 evaluates five Trust Service Criteria: security, availability, processing integrity, confidentiality, and privacy
Type I assesses control design at a point in time; Type II tests control effectiveness over a minimum 6-month observation period
Enterprise customers and financial partners increasingly require SOC 2 Type II as a prerequisite for vendor selection
Key controls for fintech include access management, encryption at rest and in transit, change management, incident response, and audit logging
Automated compliance platforms (Vanta, Drata) can reduce readiness time from months to weeks by continuously monitoring control evidence

Settlement #

Settlement is the process by which funds are transferred from a payer's bank to a payee's bank after a payment transaction is authorized and captured. In payment processing, settlement converts an authorized transaction into actual money movement — the point where the merchant's bank account balance increases. Settlement timing, netting behavior, and fee deduction methods vary by processor and region, making settlement reconciliation one of the most operationally complex reconciliation types for fintechs processing across multiple PSPs.

Settlement cycles vary by processor: T+1 (Stripe standard), T+2 (traditional card networks), T+0 (instant settlement offerings), or weekly batches
Gross settlement deposits the full transaction amount and deducts fees separately; net settlement deducts fees before depositing — reconciliation logic differs for each
Batch settlement groups multiple transactions into a single bank deposit, requiring one-to-many matching during reconciliation
Rolling reserves hold a percentage of settlements for high-risk merchants, creating timing differences between expected and actual deposits
Cross-border settlement involves intermediary banks, currency conversion, and correspondent banking fees that must be reconciled separately
Settlement failure — where expected funds do not arrive — requires immediate investigation as it may indicate processor issues or fraud
Reconciliation matches individual authorized transactions to settlement batches, accounting for fees, refunds, chargebacks, and adjustments

Subledger #

A subsidiary ledger that contains detailed transaction records for a specific account category, which are summarized and posted to the general ledger.

Common subledgers include accounts receivable (AR), accounts payable (AP), inventory, and fixed assets.
Subledgers provide granular detail while keeping the general ledger clean and manageable.
The total of all transactions in a subledger must equal the corresponding control account balance in the GL.
Subledger reconciliation is critical for ensuring the accuracy of consolidated financial statements.

Terms starting with T

Three-Way Matching #

Three-way matching is an accounts payable control that compares three documents — the purchase order (PO), the goods receipt (or receiving report), and the vendor invoice — before authorizing payment. Each document must agree on item descriptions, quantities, and pricing within configured tolerance thresholds. Discrepancies trigger exception workflows for investigation. Three-way matching prevents overpayment, payment for undelivered goods, and invoice fraud, making it a foundational AP internal control required by most audit frameworks.

The three documents: PO (what was ordered and at what price), goods receipt (what was actually received), invoice (what the vendor is charging)
Match criteria typically include: line-item descriptions, quantities (ordered vs. received vs. invoiced), unit prices, and total amounts
Tolerance thresholds allow small variances to pass without exception — e.g., quantity within 5% or amount within $10 of PO value
Two-way matching (PO to invoice only) is used for services where there is no physical goods receipt to match against
Automated three-way matching eliminates manual document comparison, reducing invoice processing time from 10+ days to under 48 hours
Exception handling routes mismatches to buyers or receiving departments with side-by-side document comparison for quick resolution
Audit requirement: SOX and internal audit frameworks consider three-way matching a key control for preventing unauthorized payments and AP fraud

Timing Difference #

A timing difference is a temporary discrepancy between two sets of financial records caused by transactions being recorded in different periods across systems. In reconciliation, timing differences arise when a payment is initiated in one system but not yet reflected in another — for example, a wire sent on Friday that settles on Monday. Unlike true errors, timing differences are expected and self-resolving, but they must be tracked to prevent false exception flags and to maintain accurate real-time balances.

Common causes include bank processing delays (T+1 to T+3 settlement), batch posting schedules, and cut-off time mismatches between systems
Timing differences account for 40-60% of unmatched items in typical reconciliation runs, making them the largest category of exceptions
Automated reconciliation engines use configurable date tolerance windows (e.g., +/- 3 business days) to match across timing gaps
Persistent timing differences that exceed expected settlement windows should trigger alerts — they may indicate failed transactions or system errors
Multi-currency timing differences compound with FX rate fluctuations, requiring date-specific rate lookups for accurate matching
Tracking timing differences separately from true exceptions improves match rates and reduces false positives for operations teams
Best practice: maintain a timing difference register that ages items and auto-escalates when expected clearing dates are missed

Transaction Ledger #

An immutable, append-only log of every financial event (debits and credits) that serves as the bedrock of financial integrity.

Implemented as append-only (immutable) — entries can never be modified or deleted, only corrected with new compensating entries
Each entry contains timestamp, amount, currency, debit account, credit account, transaction reference, and metadata
Supports both synchronous writes (consistency-first) and asynchronous event-sourced writes (throughput-first) depending on requirements
Query patterns include balance lookups (sum of all entries for an account), transaction history, and point-in-time balance reconstruction
Critical for regulatory compliance — provides the complete, tamper-evident record of every financial event in the system

Transaction Matching #

Transaction matching is the automated process of comparing individual transactions across two or more data sources to identify corresponding entries. In reconciliation, matching engines compare records from banks, payment processors, ERPs, and internal ledgers using configurable rules, fuzzy logic, and machine learning. Modern matching engines achieve 95-99% automatic match rates, leaving only true exceptions for human review.

Match types: one-to-one (single transaction pairs), one-to-many (one payment covers multiple invoices), many-to-many (batch settlements)
Rule-based matching uses exact or tolerance-based comparisons on amount, date, reference, and counterparty fields
AI/ML matching handles fuzzy scenarios: slightly different amounts, date offsets, partial references, and name variations
Confidence scoring ranks match candidates so operators can quickly confirm or reject suggested matches
Tolerance windows allow matching within configurable thresholds (e.g., amounts within $0.01, dates within 3 days)
Unmatched transactions route to exception queues with full context from both source and target records
Match rate is the primary KPI — measured as percentage of transactions automatically matched without human intervention

Two-Way Matching #

Two-way matching is a verification process that compares purchase orders to vendor invoices to confirm that the billed amount matches what was ordered. Unlike three-way matching, it does not require goods receipt verification.

Compares PO line items, quantities, and prices against the corresponding invoice
Commonly used for services, subscriptions, and items that do not require physical receipt
Faster and simpler than three-way matching while still providing financial controls
Ideal for recurring expenses where delivery confirmation is implicit or unnecessary

Terms starting with U

Unmatched Transactions #

Unmatched transactions are records that fail to pair with corresponding entries during the reconciliation matching process. They represent discrepancies that require investigation to determine whether the cause is timing, data quality, or a genuine financial exception.

Common causes include timing differences between systems, data format inconsistencies, and missing records
Aging analysis tracks how long transactions remain unmatched to prioritize investigation
Automated classification categorizes unmatched items by likely cause to streamline resolution
Persistent unmatched items may indicate process failures, fraud, or system integration issues

Terms starting with V

Variance Analysis #

The practice of comparing actual financial results against budgets, forecasts, or prior periods to identify and explain differences (variances).

Helps identify unexpected trends, operational issues, or opportunities for improvement.
Common variance types include revenue variance, cost variance, and volume variance.
Effective variance analysis requires timely, accurate data from reconciled financial records.
In fintech, variance analysis often focuses on transaction volumes, fee income, and operational costs.

Virtual Account (vIBAN)#

A routing pointer or 'pass-through' address that maps to a master physical account, primarily used to automate payment attribution.

A virtual account is a routing layer — it has a unique identifier (like an IBAN) but no actual bank account underneath
All virtual accounts map to one or more master physical accounts, enabling transaction-level segregation without the cost of individual bank accounts
Common uses include marketplace escrow (each seller gets a virtual account), client money segregation, and multi-entity cash management
Reconciliation is simplified because each virtual account receives only its designated transactions, eliminating the need to parse a shared account statement
Provided by Banking-as-a-Service platforms like Railsr, ClearBank, and Modulr, typically via API for programmatic account creation

Terms starting with W

Wallet Ledger #

A composite data structure for marketplaces that segregates the high-performance view layer (cache) from the immutable source of truth (SQL).

A wallet ledger tracks stored value, available balance, pending transactions, and holds for each user or entity in a marketplace
Segregates the hot path (real-time balance checks, transaction authorization) from the cold path (reconciliation, reporting, audit) for performance
In marketplace contexts, manages creator/seller balances, platform fees, escrow holds, and withdrawal eligibility simultaneously
Must handle concurrent operations safely — race conditions in balance updates can lead to negative balances or double-spend scenarios
Typically backed by pooled funds in a master bank account, with the wallet ledger tracking each participant proportional entitlement

Get technical insights weekly

Join 4,000+ fintech engineers receiving our best operational patterns.