Definitions
800 banking software testing terms, explained from A to Z
This glossary explains software testing terms for banks and financial institutions, from core banking, payments and cards to open banking, AI testing and regulation. Every entry opens with a short definition, then covers how the practice works and how teams test it.
Search for a term or browse the A–Z index below.
A
Account information service testing
Account information service testing checks that an authorised open banking service retrieves and presents permitted account data accurately and securely. It also verifies consent changes, API failures and the dependencies between the provider, bank and customer-facing application.
Read definitionAccount takeover prevention testing
Account takeover prevention testing checks that security controls prevent unauthorised access to existing accounts across sign-in, recovery and post-login journeys. It also verifies enforcement, audit records, fraud alerts and legitimate-user outcomes.
Read definitionACH payment testing
ACH payment testing checks that US Automated Clearing House instructions are validated, processed and reflected correctly across connected systems. It should cover asynchronous outcomes, returns, duplicate handling and reconciliation with approved test data.
Read definitionAgentic banking workflow testing
Agentic banking workflow testing verifies that AI agents complete banking tasks through authorised tools and preserve business controls across each step. It combines workflow assertions with checks for permissions, recovery behaviour, transaction state and audit evidence.
Read definitionAgentic test automation in banking
Agentic test automation uses AI agents to select and perform test actions in response to observed application state. In banking, bounded permissions, controlled test data and independent assertions are needed to make its results safe to assess.
Read definitionAgricultural bank loan grace period testing
Agricultural bank loan grace period testing checks that servicing follows contract-specific deferral dates and interest rules. The entry covers boundary cases, independent calculation checks and downstream consistency.
Read definitionAgricultural bank seasonal repayment schedule testing
Agricultural bank seasonal repayment schedule testing checks schedule dates, amounts and subsequent payment behaviour against approved product rules. Reliable tests use controlled loan data, independent expected calculations and checks across connected banking systems.
Read definitionAI AML model integration testing
AI AML model integration testing verifies that AML data reaches an AI model correctly and that its response is handled properly by connected services. It complements model validation by testing deployed interfaces, data transformations and operational outcomes.
Read definitionAI bank statement extraction accuracy testing
AI bank statement extraction accuracy testing compares structured output with verified statement data at both field and transaction level. Reliable results depend on clear reference values, representative documents, documented comparison rules and acceptance criteria matched to downstream risk.
Read definitionAI banking acceptance criteria generation
AI can draft acceptance criteria from approved banking requirements, but owners must verify every rule, assumption and expected outcome. The entry explains a review workflow and shows how to turn an AI assistant requirement into testable criteria.
Read definitionAI banking boundary test generation
AI can propose tests around banking thresholds, but testers must validate rule interpretation, expected outcomes and test data. The entry shows a transfer-limit example and explains how to verify both responses and transaction effects.
Read definitionAI banking business impact estimation
AI banking business impact estimation compares a defined operational baseline with expected or observed outcomes, while accounting for lifecycle costs and residual risk. Testing representative workflows helps confirm whether the forecast benefits occur without compromising banking controls or customer outcomes.
Read definitionAI banking business rule extraction
AI can identify candidate banking rules in policies and specifications, with source references for human review. The entry explains how to resolve ambiguity and conflicts, then verify approved rules through traceable tests.
Read definitionAI banking cross-application test execution
AI banking cross-application test execution uses AI to coordinate or support tests spanning banking applications, with explicit assertions checking business outcomes across system boundaries. Reliable runs depend on controlled test data, safe environments, recorded evidence and clear handling of uncertain states.
Read definitionAI banking decision table generation
AI can draft banking decision tables from requirements, but reviewers must confirm rule meaning, precedence and completeness against approved sources. The validated table can then provide traceable test cases with controlled inputs and explicit expected outcomes.
Read definitionAI banking defect clustering
AI banking defect clustering groups similar defect reports and test failures using text and execution data. QA teams must validate each group because similarity does not establish a shared cause.
Read definitionAI banking desktop test automation
AI can assist desktop banking tests by recognising interface elements, interpreting screen content and supporting test creation. Reliable results require controlled test data, explicit assertions, protected evidence and independent checks of transaction outcomes.
Read definitionAI banking duplicate test detection
AI banking duplicate test detection uses semantic and structured test information to flag cases that may cover the same behaviour. Reviewers must confirm equivalence against banking rules, assertions, data and risk before consolidating or retiring tests.
Read definitionAI banking edge case discovery
AI can propose boundary, rule-interaction and failure scenarios from banking requirements and test assets. QA teams must validate each candidate, define an approved expected result and verify the outcome with suitable test data and evidence.
Read definitionAI banking end-to-end scenario generation
AI can propose banking journeys from approved requirements and interface contracts, including cross-system success and failure paths. Teams must verify the rules, test data and expected outcomes before execution.
Read definitionAI banking expected result generation
AI can draft expected results from approved banking requirements and controlled data, while reviewers verify each assertion against its source. The entry explains how to handle deterministic financial outcomes, variable AI responses and a loan document extraction test.
Read definitionAI banking failure scenario identification
AI banking failure scenario identification maps plausible failures in models, data, controls and connected services into prioritised, testable conditions. The entry explains how to validate scenarios and verify expected banking outcomes.
Read definitionAI banking flaky test detection
AI flaky test detection in banking uses execution history and contextual signals to rank tests with inconsistent outcomes. Teams must validate each classification against banking behaviour, test data and environment evidence before changing test or release status.
Read definitionAI banking mainframe test automation
AI can assist with drafting, recognising and maintaining mainframe banking tests, while deterministic automation and explicit financial assertions verify outcomes. Safe use depends on controlled test data, stable environments and human review of AI-generated changes.
Read definitionAI banking model fallback testing
AI banking model fallback testing checks that a banking service detects an unusable primary model result and routes work to a controlled alternative. It also verifies recovery, audit records and transaction integrity across the switch.
Read definitionAI banking negative test generation
AI can draft negative banking tests from approved requirements and interface rules, including invalid inputs, prohibited account states and unauthorised actions. Testers must verify the expected outcomes, data setup and persisted effects before running cases in a controlled environment.
Read definitionAI banking regression suite optimisation
AI can help prioritise, group and select banking regression tests using change data, coverage links and execution history. Keep mandatory risk gates under human control and validate recommendations against full-suite results.
Read definitionAI banking release readiness analysis
AI banking release readiness analysis combines model evaluation with end-to-end banking workflow, control and operational checks. The entry explains how to set evidence-based gates and apply them to an AI payment fraud triage release.
Read definitionAI banking requirements ambiguity detection
AI can identify ambiguous wording and missing conditions in banking requirements, but domain owners must decide the intended behaviour. Traceable findings and approved clarifications provide a sound basis for acceptance criteria and boundary tests.
Read definitionAI banking requirements change impact analysis
AI banking requirements change impact analysis combines traceability, system knowledge and human review to identify affected banking behaviour and assurance evidence. The article explains how to assess impacts and verify a change to a fraud-scoring threshold.
Read definitionAI banking requirements completeness checks
AI can help identify omissions in banking requirements when it has a defined scope and authoritative source material. Human owners must confirm each finding, resolve policy gaps and link accepted changes to test coverage.
Read definitionAI banking requirements conflict detection
AI can identify candidate contradictions across banking requirements by comparing meaning, scope and expected outcomes. QA teams should verify every finding against traceable source text, resolve it with an accountable owner and test the approved behaviour.
Read definitionAI banking requirements traceability
AI banking requirements traceability connects requirements for an AI system to risks, controls, components, tests and versioned evidence. It supports coverage checks and change-impact analysis, while human review remains necessary for the validity of requirements and conclusions.
Read definitionAI banking risk scoring
AI banking risk scoring uses model outputs to estimate or rank risk for customers, applications, transactions or exposures. Testing should cover input data, model behaviour, decision policies, integrations and changes over time.
Read definitionAI banking risk-based regression planning
AI can help map banking changes to risks and regression tests, while QA teams validate selections against traceability, mandatory controls and system dependencies. The entry explains how to account for AI-specific risks and verify regression results in context.
Read definitionAI banking risk-based test selection
AI can rank banking tests by connecting release changes to risks, workflows and test history. Teams need reliable traceability, human review and checks for missed risks before relying on recommendations to reduce execution scope.
Read definitionAI banking screenshot analysis
AI banking screenshot analysis inspects captured banking screens for visual changes and expected content. Reliable results depend on controlled capture conditions, careful comparison rules and separate checks of underlying banking behaviour.
Read definitionAI banking specification analysis
AI can organise banking requirements and suggest ambiguities, conflicts and test conditions for review. The article explains how to control source documents, protect data, verify findings and preserve traceability.
Read definitionAI banking specification to test mapping
AI can extract banking rules and propose linked test cases, while testers verify assumptions, expected results and coverage. The entry shows a daily transfer limit example and explains how to preserve traceability through review and execution.
Read definitionAI banking state transition test generation
AI can draft banking workflow tests from a defined state model, including transition paths, guards and expected side effects. QA engineers must verify the model and generated assertions, then run tests with controlled data and inspect system outcomes.
Read definitionAI banking test case generation
AI can draft banking test cases from requirements and API contracts, including payment boundaries and failure paths. Review every case against approved rules, trace its source and prepare test data and assertions before execution.
Read definitionAI banking test coverage gap analysis
AI banking test coverage gap analysis compares requirements, risks, controls or workflows with tests and execution evidence to identify likely omissions. Its findings need review against source material and actual test assertions before teams treat a gap as confirmed.
Read definitionAI banking test data generation
AI can draft synthetic banking records and scenarios from approved schemas and business rules. Validate the output in the target application, protect sensitive inputs, and preserve accepted datasets for repeatable tests.
Read definitionAI banking test data privacy controls
AI banking test data privacy controls protect customer and account information throughout dataset preparation, test execution and AI processing. Effective controls combine suitable data treatments with access, retention and verification checks across prompts, outputs and logs.
Read definitionAI banking test evidence generation
AI can organise and summarise banking test records, but the original execution artefacts remain the basis for test conclusions. A controlled workflow links evidence to assertions, protects sensitive data and requires human review.
Read definitionAI banking test failure classification
AI banking test failure classification assigns failed tests to evidence-based categories while keeping root cause, severity and business impact distinct. A practical workflow helps teams investigate AI behaviour, banking rules, data, integrations, test automation and environment faults safely.
Read definitionAI banking test failure root cause analysis
AI banking test failure root cause analysis separates application and AI defects from automation, data and environment problems. The entry sets out an evidence-led investigation and shows how to verify a suspected duplicate-payment cause.
Read definitionAI banking test result summarisation
AI can organise structured banking test results into a concise report, provided each claim remains linked to execution evidence. Validate counts and explanations, protect sensitive data, and keep release decisions under established human review.
Read definitionAI banking test step generation
AI can draft banking test steps from approved requirements, workflows and rules. Reviewers must verify assumptions, expected results, test data and traceability before execution or automation.
Read definitionAI banking test suite maintenance
AI can help analyse changes and classify test failures, while banking teams retain control of assertions, data and approvals. Trace tests to business rules, diagnose failures before changing cases, and verify updates through relevant regression runs.
Read definitionAI banking UI element recognition
AI banking UI element recognition uses computer vision and text recognition to locate interface controls from rendered screens. Banking teams should handle ambiguous matches safely and verify transaction outcomes with explicit application or backend assertions.
Read definitionAI banking workflow extraction
AI banking workflow extraction uses AI to derive candidate process steps, decisions and hand-offs from banking documents or system evidence. QA teams must validate the model against approved rules and observed behaviour before using it to design tests.
Read definitionAI credit decision explanation testing
AI credit decision explanation testing validates the reasons provided alongside automated credit decisions against inputs, outputs and approved policy. It helps find explanation defects and supports fairness investigations, while requiring separate tests to assess fairness.
Read definitionAI credit decision override testing
AI credit decision override testing verifies that human review and changes to AI-generated credit outcomes follow defined permissions and workflow rules. It also checks that final decisions, audit records and downstream systems remain consistent.
Read definitionAI credit decision system testing
AI credit decision system testing must cover the model and the full decision path, including data preparation, policy rules, explanations and integrations. The entry outlines validation checks and a worked threshold test.
Read definitionAI credit model integration testing
AI credit model integration testing verifies that model inputs and outputs are transferred and acted on correctly within connected lending systems. It complements model validation, which assesses the model’s suitability and performance.
Read definitionAI credit scoring input validation testing
AI credit scoring input validation testing verifies that features meet defined data contracts before scoring and that exceptions follow the intended workflow. The entry covers test design across APIs, transformations and model interfaces, with a worked income example.
Read definitionAI document confidence threshold testing
AI document confidence threshold testing verifies how document-processing systems act on confidence scores, including acceptance, review and rejection decisions. It also checks extracted values against labelled documents and detects changes caused by model, configuration or environment updates.
Read definitionAI document extraction testing for banks
AI document extraction testing for banks evaluates document classification, OCR, field accuracy, confidence-based routing and downstream data handling. A risk-focused approach uses controlled examples, explicit expected results and regression checks across model and configuration changes.
Read definitionAI document human review routing testing
AI document human review routing testing verifies that defined policy conditions produce the correct route and that the review workflow completes safely. Tests should cover boundary cases, failure handling, queue state and route quality separately from extraction accuracy.
Read definitionAI financial advice suitability control testing
AI financial advice suitability control testing verifies that client and product information drives policy-compliant recommendations and that uncertainty or control failures trigger defined action. The entry outlines scenario design, integration checks and evidence to retain.
Read definitionAI financial document classification testing
AI financial document classification testing evaluates whether a model assigns the correct class to financial documents and whether the application handles uncertain or incorrect predictions safely. It covers labelled test data, class-level metrics, dependencies such as OCR, and downstream workflow behaviour.
Read definitionAI fraud alert investigation workflow testing
AI fraud alert investigation workflow testing verifies that model outputs become correctly routed, actionable and auditable cases. Tests should cover model-to-case integration, analyst permissions, boundary conditions, duplicate alerts and recovery from service failures.
Read definitionAI fraud detection drift monitoring tests
AI fraud detection drift monitoring tests check whether monitoring detects configured changes in transaction data or model outputs and reports them correctly. They also test data quality, delayed outcomes, alert handling and failures in the monitoring pipeline.
Read definitionAI fraud detection threshold testing
AI fraud detection threshold testing verifies how model scores map to actions at and around configured cut-offs. It also checks the impact of those decisions using representative data, defined acceptance criteria and reproducible evidence.
Read definitionAI identity document extraction testing
AI identity document extraction testing compares model output with trusted field-level values across supported documents and image conditions. It also verifies confidence handling, failure paths and the effect of extracted data on connected workflows.
Read definitionAI identity verification bias testing
AI identity verification bias testing compares decision errors and workflow outcomes across relevant groups under controlled and realistic conditions. Reliable results depend on suitable data, stage-level evidence, uncertainty reporting and retesting after changes.
Read definitionAI investment recommendation guardrail testing
AI investment recommendation guardrail testing verifies that configured controls constrain recommendations and route unsafe or incomplete cases correctly. It covers rule boundaries, model output, connected services, failure handling and evidence.
Read definitionAI loan document completeness testing
AI loan document completeness testing checks whether an application has the documents required for its product, applicant and workflow stage. Effective tests cover case-specific rules, AI classification, uncertain files, downstream status and human review.
Read definitionAI loan underwriting workflow testing
AI loan underwriting workflow testing verifies that application data, models, policy rules and human review work together to produce traceable lending outcomes. The entry explains how to test normal journeys, edge cases, dependencies and model-related behaviour.
Read definitionAI payslip extraction testing for mortgage applications
AI payslip extraction testing checks field accuracy, validation and error handling against labelled documents. It also verifies that uncertain results are routed safely and that accepted data reaches the correct mortgage workflow.
Read definitionAI risk assessment for banking software
AI risk assessment for banking software examines potential harm across the model, data, integrations and operating processes. The entry explains how to identify and prioritise scenarios, verify controls through testing and document residual risk.
Read definitionAI sanctions screening model testing
AI sanctions screening model testing evaluates how well a model identifies potential matches against sanctions lists and how its outputs behave in the screening workflow. Reliable results depend on labelled data, versioned lists and configuration, and tests of both model performance and downstream routing.
Read definitionAI signature verification integration testing
AI signature verification integration testing checks that signature data, service responses and application workflows work together as specified. It also tests error handling and review routing, while keeping integration checks distinct from model accuracy evaluation.
Read definitionAI test automation adoption in banks
Banks can adopt AI test automation by starting with bounded, verifiable tasks and governing data, access and generated assets. Validate outputs against known requirements, preserve deterministic checks and retain evidence before expanding use.
Read definitionAI test automation auditability in banking
AI test automation auditability links AI configuration and inputs to test execution, human decisions and results. Banking teams need to preserve useful evidence while protecting sensitive data and accounting for non-deterministic outputs.
Read definitionAI test automation evaluation for banks
Evaluate AI test automation for banks against a defined use case, existing process and measurable acceptance criteria. Verify banking outcomes, repeatability, data controls and reviewable evidence before adoption.
Read definitionAI test automation for banks
AI test automation tools can assist with test design, execution, maintenance and failure analysis across banking applications. Banks should validate generated tests, protect data and retain reproducible evidence for business-critical workflows.
Read definitionAI test automation for central banks
AI can assist central bank test design, maintenance and analysis when generated outputs are checked against approved requirements. Safe use depends on controlled data, traceability, repeatable execution and human approval.
Read definitionAI test automation for challenger banks
AI test automation can assist with test generation, interface recognition and failure analysis across a challenger bank's mobile and service workflows. Financial assertions, test data controls and release evidence still require explicit rules and human oversight.
Read definitionAI test automation for commercial banks
AI can assist with scenario design, interface interaction and failure analysis across commercial banking workflows. Reliable use depends on controlled data, explicit business assertions, human review and reproducible evidence.
Read definitionAI test automation for community banks
AI can assist community banks with test creation, maintenance and failure analysis across digital channels and vendor platforms. Reliable use depends on controlled test data, explicit financial assertions, human review and reproducible evidence.
Read definitionAI test automation for cooperative banks
AI test automation tools can assist with test creation, interface automation, maintenance and failure analysis in cooperative banking. Banks should validate generated outputs against approved rules, controlled test data and independently checked financial results.
Read definitionAI test automation for corporate banks
AI can help corporate banking teams generate and maintain test scenarios, support interface automation and analyse failures. Reliable outcomes require controlled environments, reviewed test assets and deterministic checks of payment state, permissions and audit records.
Read definitionAI test automation for correspondent banks
AI can assist with drafting correspondent banking test scenarios, maintaining automation and analysing failures across payment systems. Reliable results depend on reviewed acceptance rules, controlled data and repeatable evidence.
Read definitionAI test automation for credit unions
AI test automation can assist credit union teams with test creation, interface maintenance and failure analysis. Reliable release evidence still depends on explicit business assertions, controlled test data and human review.
Read definitionAI test automation for custodian banks
AI can assist with test design, automation maintenance and failure analysis across custody workflows. Custodian banks still need controlled test data, explicit financial assertions and traceable evidence.
Read definitionAI test automation for development banks
AI test automation tools can assist with test creation, maintenance and failure analysis across development bank workflows. Their outputs need review against business rules, data controls and traceable release evidence.
Read definitionAI test automation for investment banks
AI can assist with scenario design, interface maintenance and failure analysis across investment bank workflows. Teams need authoritative expected results, controlled data and reviewable evidence to verify outcomes.
Read definitionAI test automation for mortgage banks
AI can assist mortgage QA teams with scenario generation, regression selection and failure analysis when the work is grounded in approved rules. The entry explains a controlled workflow and a worked affordability-rule test, including data and evidence controls.
Read definitionAI test automation for neobanks
AI can assist neobank teams with test design, interface automation and failure analysis across mobile journeys and connected banking services. The entry explains how to use it while keeping financial assertions deterministic and test data controlled.
Read definitionAI test automation for private banks
AI can assist with test design, maintenance and failure analysis across private-banking workflows. Teams should retain explicit assertions for financial and access-control outcomes, use controlled data, and review AI-generated changes before relying on their results.
Read definitionAI test automation for retail banks
AI can assist retail bank test teams with scenario generation, regression selection, interface maintenance and failure analysis. Reliable results depend on reviewable banking rules, controlled test data and explicit assertions for transaction outcomes.
Read definitionAI test automation for traditional banks
AI can assist traditional bank test teams with test design, interface maintenance and failure analysis across legacy and digital systems. Apply it to bounded workflows, keep financial assertions deterministic, and retain human review and traceable evidence.
Read definitionAI test automation for universal banks
AI can assist with test design, maintenance and failure analysis across a universal bank’s connected systems. Reliable use depends on controlled data, independent business assertions, human review and traceable test evidence.
Read definitionAI test automation for wholesale banks
AI can assist wholesale banking teams with scenario design, regression selection and failure analysis across complex workflows. Reliable use depends on controlled data, independently defined assertions, review and traceable evidence.
Read definitionAI test automation governance in banking
AI test automation governance sets boundaries and accountable review for AI-assisted test design, execution and analysis in banking. It connects risk-based approvals, controlled data and access, output validation, traceable evidence and release decisions.
Read definitionAI test automation limitations in banking
AI can assist with banking test creation and maintenance, but variable outputs, sensitive data and incomplete assertions can undermine test reliability. Independent checks, traceable evidence and human review are needed for high-risk workflows.
Read definitionAI test automation reliability in banking
Assess AI-assisted banking tests by separating execution consistency, assertion accuracy and failure classification. Verify outcomes against transaction and ledger records, then use traceable evidence to set risk-based release controls.
Read definitionAI test automation ROI for banks
Measure AI test automation ROI for banks by comparing a defined pilot with a documented baseline and including implementation, operating and governance costs. Count released capacity only when the bank can evidence its value, and report quality measures alongside financial return.
Read definitionAI test orchestration in banking
AI test orchestration coordinates test selection, execution and result analysis across banking systems, using AI to support decisions such as risk-based prioritisation. Teams need reliable dependencies, controlled data, traceable evidence and checks that confirm selected tests cover the change.
Read definitionAI-assisted banking requirements analysis
AI-assisted banking requirements analysis uses AI to extract, organise and clarify candidate requirements from banking source material. Teams must validate outputs against authoritative sources and confirm that accepted requirements are traceable and testable.
Read definitionAI-assisted banking risk workshops
AI-assisted banking risk workshops use AI to analyse project information and suggest risks and test scenarios for human review. Their outputs are useful when teams validate suggestions against authoritative sources and connect agreed risks to planned tests.
Read definitionAI-assisted exploratory testing in banking
AI-assisted exploratory testing uses AI to suggest and organise investigations while a tester controls execution and evaluates evidence. In banking, reliable findings depend on approved rules, protected test data and traceable session records.
Read definitionAI-assisted review of banking test scenarios
AI-assisted review checks banking test scenarios against supplied requirements, rules and risk information to flag possible design issues. Testers validate findings against authoritative sources and retain responsibility for approved scenarios and execution evidence.
Read definitionAI-generated banking summary accuracy testing
AI-generated banking summary accuracy testing compares model claims with authorised banking records and business rules. Effective tests check exact financial facts, material omissions, unsupported claims, variability and customer impact.
Read definitionAI-powered testing in banking
AI-powered testing uses AI to assist software testing, while testing AI-enabled banking features requires checks suited to variable model outputs. Banking teams need reviewed test suggestions, controlled data and reproducible evidence.
Read definitionAML alert generation testing
AML alert generation testing verifies that configured monitoring rules raise accurate alerts for matching activity and avoid alerts for non-matching activity. It relies on controlled, traceable test data and checks alert content as well as rule outcomes.
Read definitionAML case management workflow testing
AML case management workflow testing verifies case transitions, role controls, data hand-offs and failure behaviour from alert creation through disposition. Effective tests use controlled data, explicit expected outcomes and evidence from both the workflow and its integrations.
Read definitionAML transaction monitoring rule testing
AML transaction monitoring rule testing verifies that configured rules assess transaction data as specified and produce the expected alert outcomes. Good tests cover boundaries, time windows, customer data, integrations and rule versions.
Read definitionATM cash deposit testing
ATM cash deposit testing validates the ATM's handling of cash and the related transaction across connected banking systems. Coverage includes posting rules, exception handling, recovery from interruptions and reconciliation.
Read definitionATM cash withdrawal testing
ATM cash withdrawal testing validates the complete path from customer authentication and authorisation to cash delivery and account records. It also checks that timeouts, dispenser faults and declines produce a consistent financial outcome.
Read definitionATM network integration testing
ATM network integration testing verifies that ATM transaction data and outcomes remain correct across connected banking and payment systems. It covers interface behaviour, error handling, recovery and reconciliation.
Read definitionATM partial dispense reversal testing
ATM partial dispense reversal testing verifies that a withdrawal is financially corrected according to the confirmed physical cash outcome and the bank's transaction rules. The entry covers controlled test setup, cross-system assertions, retry handling and evidence for diagnosing mismatches.
Read definitionAutonomous testing for banking applications
Autonomous testing can make bounded decisions about banking test design, selection, execution and analysis. Its results need traceable evidence, controlled test data and review proportionate to transaction and customer risk.
Read definitionAvailable balance vs ledger balance testing
Available balance vs ledger balance testing validates posted account funds alongside funds usable under configured banking rules. Tests follow holds, authorisations, posting and reversals, checking for correct amounts and consistent results across systems.
Read definitionAvaloq banking application testing
Avaloq banking application testing verifies that a bank's configured Avaloq workflows meet business and control requirements. Testing should trace transactions through application behaviour, data, accounting effects and relevant integrations.
Read definition
B
Bacs payment testing
Bacs payment testing verifies payment instructions across file creation, submission, processing and reconciliation. The entry explains safe test data, cycle-date checks, exception scenarios and an end-to-end supplier payment example.
Read definitionBank account closure testing
Bank account closure testing verifies the rules and system changes involved in moving an account to a closed state. It checks financial outcomes and consistency across customer channels and connected banking services.
Read definitionBank account overdraft testing
Bank account overdraft testing validates how account and transaction rules behave when balances fall below zero or approach an overdraft limit. It relies on controlled account data and explicit expected outcomes for accepted, declined and reversed transactions.
Read definitionBank account reactivation testing
Bank account reactivation testing verifies that eligible accounts return to the correct operational state and that blocked requests preserve the required controls. It also checks data integrity, audit evidence and status consistency across relevant systems.
Read definitionBank account statement testing
Bank account statement testing checks that generated statements faithfully reflect account records and banking rules. It combines data and balance assertions with document presentation and delivery checks.
Read definitionBank account switching testing
Bank account switching testing checks that an account transfer and its related payments, data and customer communications complete according to the applicable process. It combines end-to-end workflow checks with data and payment reconciliation.
Read definitionBank fee calculation testing
Bank fee calculation testing checks that configured tariffs produce the expected charge from account and transaction data. It also distinguishes amount verification from checks that fees post correctly to accounts and downstream records.
Read definitionBank fee waiver testing
Bank fee waiver testing validates the conditions and timing that determine whether a bank fee is waived, reduced or credited. It also checks that the financial and customer-facing records reflect the expected result.
Read definitionBank guarantee lifecycle testing
Bank guarantee lifecycle testing checks that each workflow stage follows the guarantee’s terms and leaves connected systems consistent. The entry explains stage-specific checks, integration failures and a practical claim scenario.
Read definitionBank merger system integration testing
Bank merger system integration testing checks that connected banking applications, data and controls behave correctly across both banks' processes. The entry explains how to scope scenarios, verify transaction flows and reconcile results before migration or cutover.
Read definitionBanking acceptance criteria
Banking acceptance criteria define verifiable conditions for deciding whether a banking feature meets agreed business needs. The entry explains how to write them, account for dependencies and verify outcomes with a transfer example.
Read definitionBanking account hold testing
Banking account hold testing verifies that funds or account activity are restricted and released according to product rules. It checks hold state, balance effects, transaction outcomes and consistency across connected banking systems.
Read definitionBanking AI agent approval gate testing
Banking AI agent approval gate testing checks that consequential actions remain blocked until an authorised person approves the exact action. It also tests rejection, expiry, changed requests, retries, bypass attempts and evidence of execution.
Read definitionBanking AI agent audit trail testing
Banking AI agent audit trail testing verifies that each consequential agent action can be traced from request to banking-system outcome. It checks record completeness, integrity, access controls, privacy and behaviour during failures and retries.
Read definitionBanking AI agent cost control testing
Banking AI agent cost control testing verifies that spend limits cover the full workflow and are enforced safely. Tests should capture attributable usage, exercise boundary and failure paths, and preserve banking permissions and audit evidence.
Read definitionBanking AI agent cross-system consistency testing
Banking AI agent cross-system consistency testing verifies that agent actions produce valid, traceable states across banking services. Tests should define authoritative data, allow for asynchronous updates and check retries, failures and customer-facing status against business rules.
Read definitionBanking AI agent duplicate action prevention testing
Banking AI agent duplicate action prevention testing verifies that retries, replays and concurrent calls do not create unintended financial effects. It also checks that valid repeated instructions remain possible and that evidence comes from authoritative transaction records.
Read definitionBanking AI agent escalation testing
Banking AI agent escalation testing verifies that policy-defined cases reach the right human workflow and that the agent handles tools, customer messaging and failures safely. The article gives a practical test setup and a worked scenario for a suspected unauthorised transfer.
Read definitionBanking AI agent external content injection testing
Banking AI agent external content injection testing verifies that instructions hidden in retrieved or processed content cannot override the agent's authorised task, permissions or approval controls. A sound test checks tool calls and banking application state as well as the response.
Read definitionBanking AI agent human override testing
Banking AI agent human override testing checks whether authorised staff can control agent-led workflows and whether those decisions remain effective across connected banking systems. It covers permissions, timing, transaction outcomes, recovery and evidence.
Read definitionBanking AI agent interruption recovery testing
Banking AI agent interruption recovery testing checks that an agent resumes, retries or escalates safely after a disruption. It verifies workflow controls and banking records as well as the agent's reported outcome.
Read definitionBanking AI agent latency evaluation
Banking AI agent latency evaluation measures response and task-completion time across the agent and its banking dependencies. The entry explains how to build repeatable tests and interpret timing alongside verified workflow outcomes.
Read definitionBanking AI agent memory isolation testing
Banking AI agent memory isolation testing probes whether agent memory, caches and retrieval paths respect customer, session and tenant boundaries. The entry sets out test preparation, cross-boundary scenarios and evidence to collect when investigating leakage.
Read definitionBanking AI agent non-deterministic behaviour testing
Testing non-deterministic banking AI agents focuses on permitted behaviour and verified system outcomes across varied runs, rather than identical text. The entry explains how to control test conditions, check consequential actions and investigate variation.
Read definitionBanking AI agent permission boundary testing
Banking AI agent permission boundary testing verifies that agent actions and information access stay within the user's entitlements across connected tools and services. The entry explains how to define scenarios, test denied operations and validate backend effects and audit evidence.
Read definitionBanking AI agent planning reliability testing
Banking AI agent planning reliability testing verifies that an agent's action sequence, tool calls and resulting state comply with banking rules. Use controlled scenarios, explicit safety invariants and repeatable evidence to identify unsafe plans and dependency failures.
Read definitionBanking AI agent policy adherence testing
Banking AI agent policy adherence testing evaluates whether an agent respects bank-defined rules throughout a task, including tool use and escalation. Reliable tests specify the policy version, controlled test conditions and observable evidence for each expected decision.
Read definitionBanking AI agent retry safety testing
Banking AI agent retry safety testing verifies that retries recover from uncertain failures without duplicating or altering a banking action. Tests should inject failures around transaction commitment and confirm the final state across agent traces, payment records and ledger entries.
Read definitionBanking AI agent rollback testing
Banking AI agent rollback testing checks whether an agent stops safely and restores reversible state after failures or control decisions. Tests must account for external payments that may need reconciliation or a compensating reversal instead of an erased transaction.
Read definitionBanking AI agent sandbox testing
Banking AI agent sandbox testing checks agent decisions and tool actions against banking controls in an isolated environment. The entry explains how to test permissions, transaction handling, failure paths and environment limits.
Read definitionBanking AI agent task completion evaluation
Banking AI agent task completion evaluation checks whether an agent achieves a specified banking outcome under its authority and policy constraints. Reliable evaluation uses explicit acceptance conditions and observable system state, with safety failures reported separately from completion rates.
Read definitionBanking AI agent testing
Banking AI agent testing evaluates both an agent's decisions and the banking actions it initiates. It uses controlled scenarios, explicit boundaries and traceable outcome checks to assess correctness and risk.
Read definitionBanking AI agent tool argument validation
Banking AI agent tool argument validation checks proposed tool inputs against structural, business and access rules before execution. QA should verify rejection paths, permission boundaries and the absence of side effects, then test transaction outcomes separately.
Read definitionBanking AI agent tool selection testing
Banking AI agent tool selection testing verifies that an agent chooses an authorised tool suited to the request and workflow state. The entry explains scenario design, safe execution, failure classification and a scheduled-transfer example.
Read definitionBanking AI agent transaction limit testing
Banking AI agent transaction limit testing verifies both agent behaviour and authoritative banking-service enforcement. Tests should cover numeric boundaries, cumulative usage, approvals, retries and the absence of payment side effects when a request is declined.
Read definitionBanking API authorisation testing
Banking API authorisation testing verifies that identities can perform only permitted actions on permitted financial resources. Effective tests cover denied access, business approval rules and the absence of unauthorised state changes.
Read definitionBanking API contract testing
Banking API contract testing verifies that banking services meet the request and response expectations of their consumers. It detects interface incompatibilities, while functional and broader integration tests remain necessary for business outcomes and cross-service workflows.
Read definitionBanking API error handling testing
Banking API error handling testing verifies documented failure responses and checks that errors do not cause unsafe financial side effects. It also tests retry behaviour, sensitive data exposure and failures in dependent services.
Read definitionBanking API rate limit testing
Banking API rate limit testing checks that agreed thresholds apply to the intended identity and endpoint, including at concurrency boundaries. Validate documented responses, recovery behaviour and the absence of unintended banking side effects.
Read definitionBanking API version compatibility testing
Banking API version compatibility testing verifies that supported consumers continue to work when API providers or clients change. It combines contract checks with integration and business-behaviour tests across the versions the bank supports.
Read definitionBanking application accessibility testing
Banking application accessibility testing combines automated checks with manual keyboard and assistive technology testing across complete customer journeys. The entry covers authentication, payment flows, test data and a practical transfer scenario.
Read definitionBanking application soak testing
Banking application soak testing runs a representative workload over an extended period to expose resource degradation and time-dependent faults. It verifies performance alongside transaction outcomes, postings and reconciliation.
Read definitionBanking application testing
Banking application testing verifies that banking software follows business rules and handles transactions, integrations and security controls correctly. A transfer retry example shows why teams must check recorded financial outcomes as well as customer-facing status.
Read definitionBanking audit trail testing
Banking audit trail testing verifies that significant banking actions produce accurate, accessible and appropriately protected records. Tests compare events with transaction state and check permissions, sequencing, failures and retention controls.
Read definitionBanking authentication exemption rule testing
Banking authentication exemption rule testing verifies eligibility logic and the payment flow that follows an exemption request or refusal. Reliable coverage includes configured boundaries, missing data, provider responses, fallback authentication and traceable evidence.
Read definitionBanking automated test evidence capture
Banking automated test evidence capture connects test outcomes to the records that support them, while controlling sensitive data and artifact access. A reliable process checks that evidence is traceable, readable and retained according to policy.
Read definitionBanking backdated transaction testing
Banking backdated transaction testing verifies that past-effective transactions follow product date rules across balances, accruals, accounting and audit records. The entry gives a practical test design for date boundaries, downstream systems, duplicate submissions and controlled test evidence.
Read definitionBanking batch processing testing
Banking batch processing testing validates the records, rules, outputs and controls of banking jobs that process transactions in groups. It also checks reconciliation, scheduling dependencies and safe recovery from partial or failed runs.
Read definitionBanking batch restart and recovery testing
Banking batch restart and recovery testing checks that interrupted scheduled processing resumes from a valid state without missing or duplicating financial activity. It verifies batch control, ledger results, reconciliation and downstream outputs after recovery.
Read definitionBanking beneficiary management testing
Banking beneficiary management testing validates how saved payment recipients are created, changed, approved, used and removed. It also checks data consistency, authorisation and configured fraud or verification controls.
Read definitionBanking biometric authentication testing
Banking biometric authentication testing verifies biometric login and approval flows across banking apps, device services and server-side controls. It also checks failures, fallback routes, action binding and the handling of sensitive authentication data.
Read definitionBanking business continuity testing
Banking business continuity testing exercises a bank's ability to maintain or restore critical services during disruption. It verifies recovery objectives, operational procedures, dependencies and transaction integrity across the service.
Read definitionBanking chatbot accessibility testing
Banking chatbot accessibility testing combines automated checks with assistive technology and keyboard testing across the full conversation lifecycle. Use controlled banking test data and verify that messages, errors, authentication and handover remain accessible.
Read definitionBanking chatbot account information accuracy testing
Banking chatbot account information accuracy testing compares chatbot responses with authorised banking records and checks that values remain correct through retrieval and presentation. The entry explains test data, access checks, freshness rules, failure cases and a worked balance example.
Read definitionBanking chatbot audit logging testing
Banking chatbot audit logging testing verifies that relevant actions and outcomes are recorded accurately, linked across services and protected from inappropriate access. Tests should cover successful, rejected and interrupted journeys, as well as privacy controls and logging failures.
Read definitionBanking chatbot authentication testing
Banking chatbot authentication testing verifies that protected data and actions depend on trusted identity and access controls. The entry covers test design, session security, failure handling and backend evidence.
Read definitionBanking chatbot complaint routing testing
Banking chatbot complaint routing testing verifies that complaint conversations follow documented bank policy and reach the correct operational queue. It covers classification, context retention, fallback behaviour, secure data transfer and evidence for regression testing.
Read definitionBanking chatbot context retention testing
Banking chatbot context retention testing verifies that conversation details persist only for the right customer and duration, and remain separate from authentication and banking authority. The entry gives a practical test case for context continuity, expiry, stale data and cross-customer leakage.
Read definitionBanking chatbot conversation isolation testing
Banking chatbot conversation isolation testing verifies that customer data and dialogue context remain scoped to the authorised chat. It uses synthetic accounts, concurrent sessions and session-change tests to expose cross-conversation leakage.
Read definitionBanking chatbot dialogue flow testing
Banking chatbot dialogue flow testing verifies conversation states, branches and controls throughout banking tasks. The entry explains how to prepare scenarios, check backend effects and diagnose failures safely.
Read definitionBanking chatbot entity extraction testing
Banking chatbot entity extraction testing validates how messages become structured banking values and how the chatbot handles uncertainty. Test field-level accuracy, normalisation, context, safe clarification and downstream transaction behaviour.
Read definitionBanking chatbot fallback response testing
Banking chatbot fallback response testing verifies that a chatbot recognises when it cannot safely answer, responds accurately and offers a working next step. Test trigger conditions, service failures, privacy controls, recovery and handover behaviour.
Read definitionBanking chatbot hallucination testing
Banking chatbot hallucination testing checks whether responses contain invented, incorrect or unsupported financial claims. The entry explains how to build evidence-based tests, assess refusals and retain reproducible results.
Read definitionBanking chatbot human handover testing
Banking chatbot human handover testing verifies that escalation reaches the right support channel with appropriate conversation context and access controls. It should also cover failed transfers, customer updates and traceable evidence.
Read definitionBanking chatbot intent recognition testing
Banking chatbot intent recognition testing verifies that customer messages map to the right intent and conversation route across varied and ambiguous phrasing. The entry covers test data, per-intent measurement, downstream assertions and safe handling of sensitive banking journeys.
Read definitionBanking chatbot jailbreak testing
Banking chatbot jailbreak testing probes whether adversarial prompts can defeat a chatbot’s instructions or banking controls. It verifies responses, tool calls and downstream effects using controlled data and environments.
Read definitionBanking chatbot latency testing
Banking chatbot latency testing measures customer-visible response times across the chat channel, AI components and banking services. Reliable tests pair percentile timings with checks for answer accuracy, safe fallback and reproducible environment conditions.
Read definitionBanking chatbot multilingual testing
Banking chatbot multilingual testing evaluates whether the bot understands supported languages and locales while preserving banking rules, customer context and safe transaction behaviour. The entry outlines test data, practical assertions, failure paths and regression coverage.
Read definitionBanking chatbot prompt injection testing
Banking chatbot prompt injection testing checks whether hostile user or retrieved content can trigger data disclosure, rule bypass or unauthorised tool use. A sound test verifies responses alongside permissions, tool traces and backend state in an isolated environment.
Read definitionBanking chatbot refusal behaviour testing
Banking chatbot refusal behaviour testing checks that a bot declines requests outside its permissions or safe scope without disclosing data or triggering unauthorised actions. Effective tests also catch refusals of legitimate customer requests.
Read definitionBanking chatbot regression testing
Banking chatbot regression testing checks that existing conversations, integrations and safety controls continue to meet requirements after a change. Effective tests use controlled data and environments, assert banking actions as well as responses, and account for acceptable language variation.
Read definitionBanking chatbot sensitive data disclosure testing
Banking chatbot sensitive data disclosure testing checks whether customer information crosses user, session or system access boundaries. Use synthetic records and verify chatbot responses alongside retrieval, API, transcript, logging and handover paths.
Read definitionBanking chatbot testing
Banking chatbot testing checks conversational accuracy alongside the security and correctness of connected banking services. A useful test strategy covers authentication, privacy, failure handling and end-to-end verification of account actions.
Read definitionBanking chatbot tool integration testing
Banking chatbot tool integration testing verifies that conversational requests reach banking services with valid arguments and correct permissions. It also checks confirmations, error handling and the resulting account or transaction state.
Read definitionBanking chatbot transaction confirmation testing
Banking chatbot transaction confirmation testing checks customer approval and verifies that chatbot messages match the authoritative transaction status. Tests should cover pending and failed outcomes, retries, changed details and evidence across connected services.
Read definitionBanking CI/CD test automation
Banking CI/CD test automation places staged, risk-based checks inside delivery pipelines and uses explicit gates to control promotion. Reliable results depend on repeatable test data, representative environments, clear failure handling and evidence linked to each change.
Read definitionBanking concurrent transaction testing
Banking concurrent transaction testing deliberately overlaps financial operations to reveal race conditions and inconsistent transaction outcomes. Verification should cover customer-facing responses and committed account and ledger state.
Read definitionBanking continuous testing
Banking continuous testing runs relevant checks throughout delivery and uses their results to inform release decisions. Its reliability depends on representative environments, controlled test data and assertions that cover business outcomes across connected systems.
Read definitionBanking conversational AI testing
Banking conversational AI testing evaluates an assistant’s language handling, responses, security controls and connections to banking services. It verifies both what the assistant says and whether any resulting banking action follows the expected rules.
Read definitionBanking critical business service testing
Banking critical business service testing evaluates an end-to-end service under disruption, including its technology, people, processes and suppliers. Results should show whether customer outcomes and data integrity meet defined criteria and any applicable impact tolerance.
Read definitionBanking CRM integration testing
Banking CRM integration testing verifies data exchange and business outcomes between a bank's CRM and connected services. It covers interface behaviour, data ownership, access controls and recovery from integration failures.
Read definitionBanking cross-browser testing
Banking cross-browser testing verifies that a bank's supported browsers handle customer-facing workflows consistently. Reliable checks record the browser configuration and validate transaction state as well as displayed results.
Read definitionBanking cross-device testing
Banking cross-device testing verifies that banking features, security controls and transaction state behave as expected across supported devices and channels. It combines compatibility checks with tests of workflows that move between devices.
Read definitionBanking customer data deletion workflow testing
Banking customer data deletion workflow testing verifies that requests are authorised, correctly scoped and processed across connected systems according to policy. It also checks retention exceptions, failures, recovery and evidence without exposing personal data.
Read definitionBanking customer offboarding testing
Banking customer offboarding testing verifies that closure requests follow approved rules and leave customer, account and downstream records in consistent states. Effective tests cover product dependencies, pending activity, access changes, retries and evidence.
Read definitionBanking customer onboarding testing
Banking customer onboarding testing verifies the application journey, KYC outcomes, workflow state changes and account setup across channels and connected systems. It also checks exception handling, duplicate prevention and consistency of records.
Read definitionBanking day-count convention testing
Banking day-count convention testing verifies that financial systems calculate accrual periods and interest according to the configured contractual rule. It uses controlled dates and inputs to expose errors in denominators, date inclusion, variants and rounding.
Read definitionBanking daylight saving time testing
Banking daylight saving time testing verifies that local clock changes do not cause incorrect payment schedules, dates, postings or batch outcomes. The entry explains transition scenarios, test-clock control and cross-system verification.
Read definitionBanking deep link testing
Banking deep link testing verifies that external links reach the correct banking workflow without bypassing authentication, authorisation or transaction controls. It includes app and operating-system routing, invalid-link handling and confirmation that no transaction occurs without the required customer action.
Read definitionBanking defect severity classification
Banking defect severity classification rates defects by their evidenced consequences for transactions, customers, controls and services. Consistent criteria, documented scope and end-to-end verification help teams make defensible triage and release decisions.
Read definitionBanking desktop application testing
Banking desktop application testing verifies staff-facing banking clients, their security controls and the banking outcomes produced by user actions. It accounts for desktop and virtual desktop dependencies, integrations and the records created by each workflow.
Read definitionBanking disaster recovery testing
Banking disaster recovery testing exercises the recovery of banking systems and data after disruption. It verifies recovery targets alongside transaction integrity, service dependencies and operational procedures.
Read definitionBanking email notification testing
Banking email notification testing verifies that banking events generate accurate, secure emails for the right recipients. The entry explains controlled test setup, event and content checks, delivery verification and a transfer example.
Read definitionBanking end-of-day processing testing
Banking end-of-day processing testing verifies that daily banking batches apply transactions and accounting rules correctly across connected systems. It also checks reconciliations, processing-date boundaries and safe recovery from incomplete or repeated runs.
Read definitionBanking end-of-month processing testing
Banking end-of-month processing testing checks that month-close jobs apply approved rules and leave account, ledger and downstream data consistent. It also verifies failure handling, reruns, reconciliation and evidence.
Read definitionBanking end-of-year processing testing
Banking end-of-year processing testing verifies annual batch calculations, account updates, ledger postings and downstream outputs. It also checks reconciliation, exception handling and safe recovery when jobs fail or require a rerun.
Read definitionBanking event ordering testing
Banking event ordering testing verifies that event delivery and processing preserve required transaction outcomes across banking services. It uses controlled delivery scenarios and state assertions to expose ordering defects, retries and duplicate handling problems.
Read definitionBanking failover testing
Banking failover testing exercises the transfer of services from a failed primary component to a standby component. It verifies recovery behaviour alongside transaction integrity, dependencies and agreed recovery targets.
Read definitionBanking false positive handling testing
False positive handling in banking testing relies on evidence from the requirement, test setup, environment and authoritative transaction records. The entry gives a payment example and explains how to correct tests and manage quarantines without hiding genuine defects.
Read definitionBanking file upload validation testing
Banking file upload validation testing verifies file structure, data and banking rules before processing, then checks rejection handling and downstream outcomes. The entry gives a practical test approach and bulk payment example.
Read definitionBanking four-eyes approval testing
Banking four-eyes approval testing verifies that a distinct, authorised user approves controlled transactions or changes before they proceed. It covers policy enforcement, workflow state, access paths and audit evidence.
Read definitionBanking general ledger testing
Banking general ledger testing verifies that financial events create complete, accurate and traceable accounting entries under the bank's posting rules. It combines transaction-level assertions with reconciliation and control-total checks.
Read definitionBanking green screen test automation
Banking green screen test automation drives terminal-based banking workflows and checks both screen behaviour and resulting system state. Reliable tests depend on controlled environments, suitable test data, state-aware synchronisation and traceable evidence.
Read definitionBanking impact tolerance testing
Banking impact tolerance testing assesses whether an important service stays within agreed disruption limits during severe but plausible scenarios. It considers end-to-end customer outcomes, dependencies and recovery evidence.
Read definitionBanking infrastructure provider failover testing
Banking infrastructure provider failover testing verifies that a bank can switch to an alternative provider or route while preserving transaction integrity and meeting agreed service objectives. It must cover uncertain in-flight transactions, reconciliation, operational response and failback.
Read definitionBanking interrupted customer journey testing
Banking interrupted customer journey testing verifies how a banking task recovers after disruptions and whether customer-visible status matches transaction and account state. The entry explains test setup, a lost-response transfer example, session expiry and cross-channel checks.
Read definitionBanking keyboard navigation testing
Banking keyboard navigation testing verifies that customers can complete banking tasks without a pointer while retaining clear focus and control over transaction actions. The entry gives a practical test approach for forms, dialogs, automation and safe transfer scenarios.
Read definitionBanking leap year processing testing
Banking leap year processing tests validate calendar rules and the product-specific handling of dates around 29 February. The entry covers boundary cases, integrated verification and a scheduled-payment example.
Read definitionBanking LLM adversarial testing
Banking LLM adversarial testing challenges AI banking applications with hostile inputs to check data protection, policy compliance and tool permissions. It evaluates the complete application, including retrieval and connected services, in a controlled environment.
Read definitionBanking LLM benchmark design
A banking LLM benchmark should test the intended application against controlled, risk-relevant cases, with explicit scoring criteria and recorded configuration. Report results by task and risk category so aggregate scores do not conceal high-impact failures.
Read definitionBanking LLM bias evaluation
Banking LLM bias evaluation tests whether a model produces materially different banking responses for equivalent cases across customer groups. The entry explains how to scope testing, create matched cases, assess outcomes and preserve evidence through model and prompt changes.
Read definitionBanking LLM calculation tool testing
Banking LLM calculation tool testing verifies tool selection, argument construction, calculation results and the model's final response against explicit banking rules. It also checks failure handling, calculation assumptions and separation from transaction-changing actions.
Read definitionBanking LLM evaluation datasets
Banking LLM evaluation datasets pair representative inputs with expected outcomes or scoring rules to test model behaviour. Public finance benchmarks help with early evaluation, while bank-specific tasks require controlled data, relevant labels and repeatable runs.
Read definitionBanking LLM factual accuracy testing
Banking LLM factual accuracy testing compares model claims with versioned, authoritative evidence and checks how the system handles uncertainty. The entry explains test-set design, scoring, end-to-end verification and a synthetic product-rate example.
Read definitionBanking LLM groundedness testing
Banking LLM groundedness testing checks whether responses are supported by the evidence provided to the model and whether the model handles gaps appropriately. The entry explains how to design controlled cases, verify retrieval and citations, and investigate unsupported claims.
Read definitionBanking LLM model upgrade regression testing
Banking LLM model upgrade regression testing compares a candidate model and its surrounding application with a controlled baseline across risk-ranked banking scenarios. Tests should assess answers, data access, tool behaviour, downstream state and release evidence.
Read definitionBanking LLM numerical reasoning testing
Banking LLM numerical reasoning tests should check rule interpretation, calculation, precision and response behaviour as separate failure points. Versioned test cases, controlled inputs and independently verified expected results make evaluations repeatable across model and tool changes.
Read definitionBanking LLM output schema validation
Banking LLM output schema validation checks response structure and declared field constraints before an application consumes model output. Reliable testing also covers business rules, invalid-output handling, schema changes and protection of test evidence.
Read definitionBanking LLM personal data leakage testing
Banking LLM personal data leakage testing checks whether users or connected services can access customer information without permission. The entry explains how to create safe test fixtures, probe system data paths and verify failures with supporting evidence.
Read definitionBanking LLM prompt version testing
Banking LLM prompt version testing compares a candidate prompt with an approved baseline while controlling model, data, retrieval and tool dependencies. The entry explains how to design regression cases, assess failures and record evidence for release decisions.
Read definitionBanking LLM response consistency testing
Banking LLM response consistency testing checks that repeated or equivalent questions produce stable banking facts and safe behaviour under controlled conditions. The entry explains how to isolate dependencies, write assertions and investigate inconsistent answers.
Read definitionBanking load testing
Banking load testing assesses whether banking systems can process an expected workload within agreed performance targets while preserving transaction correctness. The entry explains workload design, dependencies, failure modes and a payment-service example.
Read definitionBanking localisation testing
Banking localisation testing checks that banking interfaces and workflows behave correctly for their intended locales. It verifies local presentation and input handling while confirming that financial data and transaction outcomes remain accurate.
Read definitionBanking mainframe testing
Banking mainframe testing checks the behaviour of banking workloads on mainframe platforms, including transaction processing, batch jobs and connected systems. Reliable results depend on controlled data, representative environments and verification of outputs across system boundaries.
Read definitionBanking maker-checker workflow testing
Banking maker-checker workflow testing checks whether financial operations follow configured preparation, approval and execution controls. The entry explains positive and negative tests, audit verification and a corporate payment example.
Read definitionBanking manual review queue testing
Banking manual review queue testing checks that review items follow configured routing, access, decision and closure rules. It also verifies audit evidence and the resulting state of connected banking transactions or records.
Read definitionBanking manual to automated testing transition
A banking manual to automated testing transition works best in stages, beginning with repeatable, high-risk workflows and reliable test data. Keep human-led testing for judgement-based work, and treat automation failures as signals to investigate rather than results to suppress.
Read definitionBanking migration cutover testing
Banking migration cutover testing verifies the data, transaction state and operational steps involved in switching to a replacement banking platform. Rehearsals, reconciliation rules and explicit go/no-go and rollback criteria help teams control the transition.
Read definitionBanking migration rollback testing
Banking migration rollback testing proves that a bank can recover service and data after a migration failure without losing or duplicating transactions. The entry covers prerequisites, cutover scenarios, reconciliation and evidence of recovery.
Read definitionBanking mobile browser testing
Banking mobile browser testing verifies that browser-based banking journeys work across supported mobile devices and browsers. It also checks browser-specific behaviour that can affect authentication, sensitive data and transaction outcomes.
Read definitionBanking multi-agent workflow testing
Banking multi-agent workflow testing checks that software agents coordinate safely across a banking process and preserve correct state, permissions and financial outcomes. Effective tests cover hand-offs, failure recovery, control gates and evidence across connected systems.
Read definitionBanking multi-currency ledger testing
Banking multi-currency ledger testing verifies transaction and functional-currency amounts, exchange-rate handling, configured journal postings and reconciliation. Tests need controlled rates and currency-specific assertions to expose conversion, rounding and posting errors.
Read definitionBanking multi-factor authentication testing
Banking multi-factor authentication testing verifies that required factors are correctly challenged and enforced across customer journeys and server-side operations. It also checks recovery, retries, challenge binding, service failures and the protection of authentication data.
Read definitionBanking multilingual interface testing
Banking multilingual interface testing checks that translated banking journeys remain usable and present financial information accurately across supported languages and locales. It covers text, regional formats, layout, right-to-left behaviour and the boundary between display changes and transaction data.
Read definitionBanking operational resilience scenario testing
Banking operational resilience scenario testing evaluates a bank's ability to maintain or recover an important service during a severe but plausible disruption. Effective exercises test service outcomes, dependencies, recovery actions and transaction integrity, with evidence tied to defined criteria.
Read definitionBanking parallel run testing
Banking parallel run testing processes equivalent transactions in existing and target systems and reconciles their outputs. Reliable results depend on aligned data, configuration and processing conditions, with material variances investigated and documented.
Read definitionBanking password reset workflow testing
Banking password reset workflow testing verifies that customers can securely restore access and that invalid, expired or misused reset attempts cannot change credentials. The entry covers test setup, functional and security checks, service failures and a practical example.
Read definitionBanking payment latency testing
Banking payment latency testing measures payment response and completion times across defined transaction stages. Reliable results combine latency percentiles with workload, dependency and payment-correctness checks.
Read definitionBanking payment processing testing
Banking payment processing testing verifies payment instructions from entry through processing, ledger updates and settlement or rejection. It checks expected financial outcomes across connected systems, including retries, returns and reconciliation.
Read definitionBanking peak transaction volume testing
Banking peak transaction volume testing checks whether a banking system can sustain its defined maximum transaction rate while meeting performance and correctness criteria. Reliable results depend on a representative workload, suitable environment and checks across the full transaction path.
Read definitionBanking performance testing
Banking performance testing assesses the speed, capacity and reliability of banking services under defined workloads. It combines performance metrics with checks that transactions produce correct outcomes.
Read definitionBanking posting rule testing
Banking posting rule testing confirms that transaction events generate the accounting entries required by approved rules. It checks rule selection, account mapping, amounts, balance effects and downstream ledger consistency.
Read definitionBanking privileged access workflow testing
Banking privileged access workflow testing checks that elevated permissions follow approved rules throughout their lifecycle. Effective tests verify both workflow decisions and the resulting access state in target systems, with auditable evidence.
Read definitionBanking production verification testing
Banking production verification testing checks that a banking release behaves as expected in the live environment. Its scope and safeguards must account for customer impact, financial records and downstream processing.
Read definitionBanking production-like test environments
Banking production-like test environments reproduce selected production configurations, dependencies and operating conditions in a controlled setting. Their test results are useful when teams understand data and integration limits, isolate transactions and track environment drift.
Read definitionBanking push notification testing
Banking push notification testing verifies the full path from a banking event to device presentation and authenticated navigation. It also checks privacy, customer preferences, retries and failure handling.
Read definitionBanking quality assurance
Banking quality assurance combines lifecycle activities, risk assessment and testing to check that banking software meets business, customer, security and operational requirements. Its evidence supports release decisions and compliance assessment, while wider governance remains necessary.
Read definitionBanking race condition testing
Banking race condition testing coordinates overlapping transactions and checks that account rules remain true across responses, stored transaction state and ledger postings. The entry gives a controlled concurrent debit example and explains how to test retries and asynchronous results.
Read definitionBanking RAG access permission testing
Banking RAG access permission testing verifies that retrieval and every user-visible output respect the current user's entitlements. Test both permitted access and leakage paths, including stale permissions, citations and cached responses.
Read definitionBanking RAG citation accuracy testing
Banking RAG citation accuracy testing verifies that references resolve to the right, authorised source and support the claims they accompany. A reliable test set records expected evidence and checks citations at claim level across source and system changes.
Read definitionBanking RAG conflicting source handling testing
Banking RAG conflict tests check whether a system selects evidence using approved authority, scope and effective dates. They also verify citations, safe handling of unresolved disagreements and reproducible results across changes.
Read definitionBanking RAG cross-customer data isolation testing
Banking RAG cross-customer isolation tests verify that retrieval and generated outputs remain within the active user's authorised customer scope. The entry covers test data, negative and positive checks, stateful paths, assertions and failure diagnosis.
Read definitionBanking RAG document ingestion testing
Banking RAG document ingestion testing verifies that documents are accurately processed and indexed with correct metadata, versions and permissions. The entry gives a practical test approach for pipeline failures and a revised lending-policy example.
Read definitionBanking RAG document relevance evaluation
Banking RAG document relevance evaluation checks whether retrieval returns authoritative evidence for the right product, jurisdiction and effective date. The entry explains evaluation data, ranking metrics, access-control checks and a mortgage tariff example.
Read definitionBanking RAG knowledge freshness testing
Banking RAG knowledge freshness testing verifies that approved, applicable source content reaches retrieval and generated answers within a defined period. The entry explains how to test updates, effective dates, removals, permissions and stale-cache failures.
Read definitionBanking RAG retrieval accuracy testing
Banking RAG retrieval accuracy testing checks whether the correct, current and authorised banking passages appear in the results supplied to the language model. A repeatable evaluation set, top-k metrics and risk-based regression checks expose retrieval defects separately from answer-generation errors.
Read definitionBanking RAG unanswerable question testing
Banking RAG unanswerable question testing checks whether a system abstains or escalates when permitted source material cannot support a response. Effective tests distinguish missing knowledge from retrieval, access-control and generation failures.
Read definitionBanking recovery point objective validation
Banking recovery point objective validation measures the age of the latest complete data state recovered after a disruption and compares it with the approved RPO. It also checks transaction integrity across the ledger and dependent systems.
Read definitionBanking recovery time objective validation
Banking recovery time objective validation tests whether a defined banking service is restored within its agreed time and meets operational recovery criteria. The entry explains how to scope scenarios, measure recovery and verify transaction integrity.
Read definitionBanking regulatory reporting software testing
Banking regulatory reporting software testing verifies data lineage, reporting rules, calculations, validations, controls and generated outputs against approved requirements. Repeatable test data, reconciliation and traceable evidence help teams assess report accuracy and release readiness.
Read definitionBanking release approval evidence
Banking release approval evidence connects a specific release candidate to its scope, risk assessment, test results, defects, deployment readiness and authorised decision. Its coverage should reflect the change and the bank’s internal controls and applicable obligations.
Read definitionBanking release readiness assessment
A banking release readiness assessment combines test evidence and operational checks to determine whether a release can proceed at an accepted level of risk. It should produce a traceable decision, with clear conditions, owners and actions for unresolved risks.
Read definitionBanking release risk assessment
A banking release risk assessment links a proposed software change to credible failure scenarios, their business impact and proportionate test evidence. It gives release decision-makers a clear view of verified risks, evidence gaps and residual uncertainty.
Read definitionBanking remote desktop test automation
Banking remote desktop test automation drives banking workflows inside a hosted desktop while accounting for session, display and application dependencies. Reliable tests combine stable UI interactions, controlled test data and independent checks of business outcomes.
Read definitionBanking requirements ambiguity analysis
Banking requirements ambiguity analysis identifies wording that permits different interpretations of banking rules or workflows. The entry gives a review method and an available-balance example showing how to turn assumptions into testable criteria.
Read definitionBanking requirements risk scoring
Banking requirements risk scoring rates the potential impact and likelihood of requirement failure to guide analysis and test priority. Consistent criteria, recorded evidence and regular reassessment help teams use scores without treating them as precise predictions.
Read definitionBanking requirements testability
Banking requirements are testable when their conditions, rules and observable outcomes let teams verify behaviour consistently. The entry explains how to assess testability and gives a transfer-limit example.
Read definitionBanking requirements traceability
Banking requirements traceability connects requirement sources and versions to controls, tests and execution evidence. Its value depends on clear requirements, maintained links and evidence that verifies the intended behaviour.
Read definitionBanking risk and control matrix testing
Banking risk and control matrix testing checks whether mapped controls address identified risks and operate as specified in banking systems and workflows. It connects risk statements to test procedures, evidence, defects and retests.
Read definitionBanking risk assessment matrix
A banking risk assessment matrix ranks software failure scenarios by likelihood and impact so teams can prioritise test coverage and evidence. Its ratings depend on agreed criteria and should be revisited when requirements, dependencies or environments change.
Read definitionBanking risk-based coverage analysis
Banking risk-based coverage analysis connects potential failures to appropriate tests, controls and execution evidence. Its value depends on a current risk inventory, valid test conditions and clear reporting of unresolved gaps.
Read definitionBanking risk-based release decisions
Banking risk-based release decisions combine impact and likelihood assessments with test evidence, operational readiness and accountable risk acceptance. The entry explains practical release gates and applies them to a payment retry change.
Read definitionBanking risk-based test selection
Banking risk-based test selection chooses test cases according to assessed failure likelihood and impact, with traceability from risks to expected results and evidence. It supports focused testing while keeping required controls and critical regression checks in scope.
Read definitionBanking role-based access control testing
Banking role-based access control testing checks that users can perform authorised actions only within their permitted data and workflow scope. Effective coverage combines positive and negative cases across interfaces, APIs, role changes and audit records.
Read definitionBanking rounding and precision testing
Banking rounding and precision testing checks that calculations preserve the required decimal precision and apply the specified rounding rule at the correct stage. Tests should cover tie cases, boundaries, data conversions and consistency between calculated, posted and displayed amounts.
Read definitionBanking scheduled transfer testing
Banking scheduled transfer testing verifies that future-dated instructions follow product rules and execute once at the correct time. It also checks calendar handling, payment controls, status updates, recovery and ledger reconciliation.
Read definitionBanking screen reader testing
Banking screen reader testing verifies that customers can complete financial tasks using assistive technology. The entry explains how to prepare a test setup and check forms, errors, confirmation steps and dynamic updates.
Read definitionBanking segregation of duties testing
Banking segregation of duties testing verifies that users cannot perform conflicting financial actions, or that violations are detected and recorded as designed. Effective tests cover combined access, transaction workflows and audit evidence.
Read definitionBanking sensitive data masking testing
Sensitive data masking testing checks that banking data transformations meet policy across systems and user access paths. It also verifies that masked datasets retain the structure needed for testing without exposing original values.
Read definitionBanking service virtualisation
Banking service virtualisation provides controllable simulations of banking APIs and external dependencies. It helps teams test workflow behaviour when live services are unavailable, while requiring checks for model fidelity and clear evidence of what was simulated.
Read definitionBanking session timeout testing
Banking session timeout testing checks that idle and absolute expiry rules are enforced by the server across banking clients and APIs. It also verifies that expired sessions cannot expose data or submit unauthorised actions, and that transaction outcomes remain clear.
Read definitionBanking shift-left testing
Banking shift-left testing brings requirement review and suitable automated checks earlier in development, including tests for financial rules and service boundaries. It supports earlier feedback and traceability while leaving integration, end-to-end and other risk-based validation in place.
Read definitionBanking shift-right testing
Banking shift-right testing checks deployed banking services through controlled production or production-like tests and operational monitoring. Effective checks require defined expected results, reliable observability and safeguards for customer data and financial actions.
Read definitionBanking SMS notification testing
Banking SMS notification testing verifies that banking events generate accurate, appropriate messages and that delivery is traceable across provider integrations. The entry explains practical test cases, failure handling and safeguards for test data.
Read definitionBanking software failure mode analysis
Banking software failure mode analysis maps potential failures to their causes, effects and controls so teams can prioritise risk-based tests. The payment retry example shows how to verify transaction and ledger outcomes after a timeout.
Read definitionBanking software risk assessment
A banking software risk assessment evaluates plausible software failure scenarios by their likelihood and impact. Its findings guide controls, targeted testing and decisions about residual risk.
Read definitionBanking software stress testing
Banking software stress testing pushes a controlled workload beyond expected demand to expose system limits and failure behaviour. Results should include transaction-integrity checks and evidence of recovery, alongside performance measures.
Read definitionBanking software testing
Banking software testing checks that financial applications process transactions accurately, protect data and meet applicable operational and regulatory requirements. Effective testing verifies business rules, integrations, failure handling and the evidence behind each result.
Read definitionBanking subledger testing
Banking subledger testing validates detailed account records, balance calculations and the accounting entries sent to the general ledger. Strong tests use controlled transaction data and verify outcomes across the subledger and downstream accounting systems.
Read definitionBanking suspense account testing
Banking suspense account testing checks exception posting, resolution, reconciliation and control evidence across a transaction's lifecycle. Test expected journals and bank-specific rules with traceable data and configured acceptance criteria.
Read definitionBanking terminal emulator testing
Banking terminal emulator testing validates user interactions with text-based banking applications and checks that host processing produces the expected results. Reliable tests need controlled data, stable emulator settings and evidence that distinguishes application defects from environment or automation failures.
Read definitionBanking test account provisioning
Banking test account provisioning prepares account and customer records in a controlled environment for repeatable banking tests. Reliable provisioning checks relationships, state and downstream visibility, while preventing test data from reaching live services.
Read definitionBanking test automation
Banking test automation runs repeatable checks across banking interfaces, services and workflows. Reliable results depend on controlled data, suitable environments and assertions tied to banking rules.
Read definitionBanking test automation across Citrix and web applications
Automating a banking workflow across Citrix and web applications requires separate interaction methods for each interface and explicit checks at every hand-off. The entry explains environment and data preconditions, business-state assertions, and safe handling of failures that may have changed transaction state.
Read definitionBanking test automation infrastructure
Banking test automation infrastructure connects automated tests to controlled environments, services, test data and execution processes. Its reliability depends on managing dependencies, security, environment configuration and failure evidence.
Read definitionBanking test automation maintenance cost
Estimate maintenance from the work required to diagnose, repair and support automated tests, then apply your organisation's loaded rates and add relevant direct costs. Use banking workflow dependencies, historical failure data and planned system changes to make the forecast specific and reviewable.
Read definitionBanking test automation ownership
Banking test automation ownership assigns accountability for test design, maintenance, failure investigation and release use across technical and business teams. Clear ownership makes it easier to distinguish product defects from automation, data and environment failures.
Read definitionBanking test automation proof of concept
A banking automation PoC tests whether a specific workflow can be automated and verified safely in a controlled environment. Define measurable acceptance criteria, use representative data and document dependencies and limitations.
Read definitionBanking test automation scalability
Banking test automation scalability depends on risk-focused coverage, independent tests, and execution capacity that respects shared banking dependencies. Repeatable data, controlled environments and useful failure evidence help teams scale without losing confidence in results.
Read definitionBanking test automation stability
Banking test automation stability depends on repeatable test state, controlled dependencies and assertions against authoritative transaction outcomes. Diagnose failures before adding retries, and retain evidence that lets teams reproduce them.
Read definitionBanking test automation tool evaluation
Evaluate banking test automation tools against real application workflows, security controls, data and environment constraints, and maintainability. Use a controlled proof of concept with explicit acceptance criteria before selecting a tool.
Read definitionBanking test automation vendor selection
Banking test automation vendor selection should begin with required systems, workflows and operating controls. A focused proof of concept can verify vendor claims against the bank’s actual environment and test needs.
Read definitionBanking test automation without APIs
Banking test automation without APIs exercises banking workflows through user interfaces when direct service access is unavailable or the interface itself is in scope. Reliable coverage depends on controlled test data, safe transaction handling and evidence that verifies the business outcome.
Read definitionBanking test automation without DOM access
Banking tests can interact through accessibility information, keyboard input or screen recognition when DOM inspection is unavailable. Verify financial outcomes through approved independent evidence, and control test data, retries and captured information.
Read definitionBanking test automation without source code access
Banking test automation without source code access relies on authorised external interfaces and observable business outcomes. The entry explains interface choices, test controls and a transfer example.
Read definitionBanking test cases from software specifications
Derive banking test cases by converting specification rules into traceable checks with controlled data, explicit preconditions and observable outcomes. The transfer example shows how to test a daily limit boundary and verify that a rejected request creates no postings.
Read definitionBanking test cases from user stories using AI
AI can draft banking test cases from stories and acceptance criteria, but its output needs review against approved business rules. This guide covers preparation, prompting, validation and traceability.
Read definitionBanking test coverage
Banking test coverage describes how thoroughly tests address defined requirements, workflows, controls and risks. Its measures are meaningful only when the scope, denominator and execution evidence are clear.
Read definitionBanking test data anonymisation
Banking test data anonymisation transforms or removes identifying information in banking datasets prepared for testing. Its controls must address indirect identifiers and preserve only the data relationships and behaviours required by test scenarios.
Read definitionBanking test data management
Banking test data management prepares and governs data for banking tests while protecting customer information and preserving the linked records and business states workflows require. Effective controls cover data sourcing, privacy transformations, validation, access and retirement.
Read definitionBanking test data referential integrity
Banking test data referential integrity ensures that related records point to valid parent records and remain consistent across systems. The entry explains database constraints, validation queries, fixture design and common causes of broken links.
Read definitionBanking test environment management
Banking test environment management keeps banking test systems and their data controlled, secure and suitable for repeatable testing. It helps teams identify whether failures come from the application or from environment state.
Read definitionBanking test environment refresh
A banking test environment refresh restores selected data and services to a defined testing baseline. The process needs controlled data handling, dependency-aware execution and verification before testers resume work.
Read definitionBanking test evidence traceability
Banking test evidence traceability connects requirements and controls to tests, execution results and supporting artifacts. Reliable links include enough run, build and environment context for teams to check coverage and investigate outcomes.
Read definitionBanking test execution observability
Banking test execution observability connects a test outcome to evidence from the applications, services and environment involved in a banking workflow. Correlated evidence helps teams investigate failures while preserving the need for correct assertions and controlled test data.
Read definitionBanking test execution orchestration
Banking test execution orchestration coordinates test steps, data, environments and service dependencies across banking workflows. Clear gates, safe retry rules and traceable evidence help teams separate product failures from execution problems.
Read definitionBanking test planning
Banking test planning converts a defined change, its risks and applicable obligations into an executable testing approach with clear dependencies and completion criteria. It also gives teams a way to trace requirements to results and assess gaps before release.
Read definitionBanking test result reproducibility
Banking test result reproducibility depends on recording the inputs, versions, environment and state that shape an outcome. The entry gives a practical method for replaying a transfer test and diagnosing differences safely.
Read definitionBanking test scenario design
Banking test scenarios connect customer actions and banking rules to verifiable outcomes across channels and dependent systems. The entry explains how to define conditions, cover failure paths and validate transaction records.
Read definitionBanking test strategy
A banking test strategy aligns software testing with customer, financial, operational and compliance risks. It guides test scope, methods, data, environments and the evidence used in release decisions.
Read definitionBanking test suite runtime optimisation
Banking test suite runtime optimisation reduces feedback time through measured test selection, safe parallelism and efficient data setup. Verify that speed gains preserve risk coverage, reproducibility and release evidence.
Read definitionBanking third-party service outage testing
Banking third-party service outage testing exercises dependency failures under controlled conditions and checks their effect on customer journeys, transaction integrity and operational handling. The entry covers safe failure injection, workflow assertions, recovery and reconciliation.
Read definitionBanking third-party service simulation
Banking third-party service simulation lets teams exercise integrations through a controlled substitute for an external provider. Its value depends on realistic behaviour models, safe routing and separate checks against the live provider where compatibility matters.
Read definitionBanking transaction atomicity testing
Banking transaction atomicity testing verifies that required posting changes commit together or leave no partial effects. The entry covers test setup, failure injection, ledger assertions and distributed payment workflows.
Read definitionBanking transaction consistency testing
Banking transaction consistency testing verifies that financial state changes follow defined rules across ledgers, account views and downstream services. Tests should cover retries, concurrent activity, failures and any asynchronous updates.
Read definitionBanking transaction durability testing
Banking transaction durability testing confirms that committed financial transactions remain correctly recorded after defined failures and recovery. It checks authoritative ledger state, related balances and retry behaviour against explicit system guarantees.
Read definitionBanking transaction isolation testing
Banking transaction isolation testing verifies that concurrent database transactions preserve banking business rules and produce consistent committed records. It combines controlled concurrency with checks of configured isolation behaviour and application-level safeguards.
Read definitionBanking transaction reversal testing
Banking transaction reversal testing verifies that reversals follow rules for the transaction's lifecycle state and leave consistent balances, ledger entries and downstream records. The expected behaviour varies by transaction type and may involve cancellation, voiding or compensating entries.
Read definitionBanking transaction rollback testing
Banking transaction rollback testing verifies that a failed operation leaves financial records in the state defined by the transaction rules. The entry explains test setup, failure injection, authoritative assertions and the limits of database rollback across systems.
Read definitionBanking value date testing
Banking value date testing verifies that transactions receive the effective date required by configured banking rules. It also checks that calendar, cut-off and timezone handling produce consistent downstream processing.
Read definitionBanking virtual assistant testing
Banking virtual assistant testing verifies dialogue behaviour alongside the banking services and controls behind each response or action. The entry explains how to scope scenarios, test failure paths and confirm outcomes against system state.
Read definitionBanking virtual desktop testing
Banking virtual desktop testing validates banking applications and workflows in hosted desktop sessions, including the access and configuration dependencies that can affect results. It combines functional checks with verification of session behaviour, permissions and downstream banking outcomes.
Read definitionBanking web portal testing
Banking web portal testing evaluates customer-facing banking workflows alongside the services that support them. It combines interface, security, integration and transaction checks, with test evidence suited to each outcome.
Read definitionBanking webhook delivery testing
Banking webhook delivery testing checks event delivery and receiver behaviour under valid, invalid and failure conditions. Verify acknowledgements alongside payment and ledger state so transport success is not mistaken for completed banking processing.
Read definitionBanking-as-a-service account provisioning testing
Banking-as-a-service account provisioning testing verifies that account requests produce the correct records, states and downstream effects across partner and banking systems. The entry covers test preparation, lifecycle and retry cases, and a practical API example.
Read definitionBanking-as-a-service integration testing
Banking-as-a-service integration testing verifies that applications and connected banking services exchange data and maintain correct business state. It covers API behaviour, asynchronous events, retries, reconciliation and failures across provider boundaries.
Read definitionBanking-as-a-service ledger reconciliation testing
Banking-as-a-service ledger reconciliation testing verifies that transaction events and ledger postings agree across provider, partner and programme systems. The entry explains how to prepare controlled data, test matching and exception handling, and verify balance results.
Read definitionBanking-as-a-service partner offboarding testing
Banking-as-a-service partner offboarding testing checks that access, processing, customer servicing and data handling follow the approved exit plan. It also verifies that financial records reconcile and that failures leave the transition in a controlled state.
Read definitionBanking-as-a-service partner onboarding testing
Banking-as-a-service partner onboarding testing verifies partner approval, configuration and access across provider systems and external dependencies. It also checks failure handling, activation gates and safe retries before live services are enabled.
Read definitionBanking-as-a-service tenant isolation testing
Banking-as-a-service tenant isolation testing verifies that each partner and its authorised users can access only their own data and operations. The entry explains test setup, cross-tenant attack cases, asynchronous paths and evidence checks.
Read definitionBCBS 239 data aggregation testing
BCBS 239 data aggregation testing verifies the controls and processing that turn source risk data into aggregated reports. It combines reconciliation, lineage, calculation and failure-path checks, while recognising that software test results alone do not prove regulatory compliance.
Read definitionBoundary value testing in banking
Boundary value testing checks values around banking rule limits, including the expected behaviour at the limit itself. The entry explains how to select test data and verify transaction results, rejections and related account effects.
Read definitionBuilding society member account integration testing
Building society member account integration testing verifies that account, membership and transaction data stay consistent as they pass between systems. Effective tests cover business rules, duplicate delivery, dependency failures and reconciliation.
Read definitionBuilding society savings to mortgage journey testing
Building society savings to mortgage journey testing checks that customer identity, savings access, deposit evidence, transfers and mortgage status remain correct across connected systems. The entry explains how to prepare data, test successful and failed hand-offs, and verify persisted records.
Read definitionBulk payment testing
Bulk payment testing checks that a submitted group of payment instructions is validated, processed and reported correctly at both batch and item level. It also verifies how partial failures, retries and downstream outcomes affect payment records and reconciliation.
Read definitionBusiness bank account opening testing
Business bank account opening testing checks the full application lifecycle, its decision rules and the connected services that verify a business and provision an account. Effective coverage includes failure recovery, duplicate prevention, data protection and evidence tied to requirements.
Read definitionBusiness customer KYB testing
Business customer KYB testing verifies that banking systems apply configured business identity and onboarding controls correctly. It covers entity and ownership data, screening, integrations, workflow decisions and failure handling.
Read definitionBusiness impact analysis for banking software
A business impact analysis assesses the consequences of banking service disruption over time and identifies recovery priorities and requirements. Its findings help teams design tests that verify business service recovery, data integrity and transaction handling.
Read definitionBusiness process testing in banking
Business process testing in banking validates complete workflows against business rules, controls and expected outcomes across connected systems. The entry explains how to prepare a transfer scenario and verify its processing, financial records and failure handling.
Read definition
C
Camt.053 statement testing
camt.053 statement testing combines version-specific XML validation with checks of account data, entries, dates and balances. End-to-end tests should also verify ingestion, reconciliation, error handling and duplicate prevention.
Read definitionCamt.054 notification testing
camt.054 notification testing checks message structure, profile-specific rules and transaction data, then verifies that receiving systems process delivery and retries correctly. Use version-matched schemas and end-to-end assertions to catch both XML and business integration defects.
Read definitionCard activation testing
Card activation testing verifies the lifecycle transition that enables an issued payment card and checks that connected systems reflect the result correctly. It should cover valid activation, rejected requests, retries and status consistency, while keeping activation distinct from transaction authorisation.
Read definitionCard authorisation reversal testing
Card authorisation reversal testing verifies that a cancellation is linked to the right approved payment and handled consistently across the processing flow. It also checks retries, asynchronous outcomes and the boundary between an authorisation reversal and a refund.
Read definitionCard authorisation testing
Card authorisation testing checks that payment requests receive and handle the expected issuer or processor decisions. It also verifies payment state, retry behaviour and downstream effects using controlled test data.
Read definitionCard chargeback workflow testing
Card chargeback workflow testing verifies that disputes progress through permitted states and produce the correct evidence, audit and financial outcomes. The article covers test setup, valid and negative paths, duplicate events and cross-system verification.
Read definitionCard clearing and settlement testing
Card clearing and settlement testing checks that captured card transactions produce correct clearing records, settlement obligations and accounting outcomes. It also verifies reconciliation and safe handling of duplicates, exceptions and retries.
Read definitionCard freeze and unfreeze testing
Card freeze and unfreeze testing verifies state changes, permissions and payment behaviour across channels and processor integrations. Tests should cover valid transitions, repeated requests, timing, pending transactions and recovery from failures.
Read definitionCard issuance workflow testing
Card issuance workflow testing checks that card requests pass through the required rules, systems and status changes to the expected outcome. It also verifies failure handling, retry safety and consistency between integrated services.
Read definitionCard payment stand-in processing testing
Card payment stand-in processing testing verifies how eligible card authorisations are handled when the issuer cannot respond. It checks configured fallback decisions and controls, response handling and transaction records during recovery.
Read definitionCard refund processing testing
Card refund tests should verify the request, processor outcome, transaction state and financial records together. Include partial refunds, duplicate submissions, delayed responses and reconciliation checks.
Read definitionCard replacement testing
Card replacement testing verifies the transition from an existing payment card to its replacement across issuer systems, processors and linked services. Expected behaviour depends on the issuer’s rules for card status, activation, credentials and transactions already in progress.
Read definitionCard spending limit testing
Card spending limit testing checks that card authorisations follow configured transaction and cumulative limits through the transaction lifecycle. Reliable tests use controlled card states, boundary values and assertions across authorisation responses and recorded usage.
Read definitionCard tokenisation testing
Card tokenisation testing checks that payment systems substitute and manage card tokens correctly throughout their lifecycle. It also verifies payment outcomes, failure handling and protection against card data exposure.
Read definitionCash pooling workflow testing
Cash pooling workflow testing checks that configured pool rules and connected systems produce accurate positions and safe account movements. It also verifies failure recovery and reconciliation across the workflow.
Read definitionCentral bank collateral eligibility rule testing
Central bank collateral eligibility rule testing verifies that systems apply the correct policy criteria to asset data for the relevant facility and assessment date. It also checks boundary cases, unresolved data and decision evidence.
Read definitionCentral bank participant access control testing
Central bank participant access control testing checks that authorised users can perform permitted actions within their own participant scope and that prohibited requests have no effect. Effective tests cover identity dependencies, direct API requests, revocation, resulting system state and audit evidence.
Read definitionCentral bank payment gridlock resolution testing
Central bank payment gridlock resolution testing verifies that a settlement system identifies and resolves compatible groups of queued payments according to its rules. It checks participant balances, instruction statuses, audit records and recovery behaviour.
Read definitionCentral bank RTGS application testing
Central bank RTGS application testing checks payment processing, account updates, liquidity and queue rules, participant interfaces, security and recovery against documented operating requirements. The entry includes a practical retry scenario for verifying duplicate-payment handling.
Read definitionCentral bank settlement queue management testing
Central bank settlement queue management testing checks how queued instructions progress under configured priority, liquidity and timing rules. It verifies queue states against settlement records, participant balances and recovery behaviour.
Read definitionChallenger bank core platform migration testing
Challenger bank core platform migration testing checks that data, balances and banking workflows transfer correctly to a replacement core. It also verifies integrations, cutover controls, reconciliation and recovery using agreed rules and traceable evidence.
Read definitionCHAPS payment testing
CHAPS payment testing verifies the full lifecycle of a high-value sterling payment, from initiation through settlement and reconciliation. Reliable tests distinguish technical acceptance from settlement and cover rejection, timeout and duplicate-handling behaviour.
Read definitionChecking account transaction testing
Checking account transaction testing checks that account activity follows configured rules and produces correct, traceable state changes. The entry explains balance verification, failure paths, retries and controlled test data.
Read definitionCitrix banking application testing
Citrix banking application testing must cover both banking workflow outcomes and the remote session conditions that shape user interaction. Reliable checks combine controlled test data, session-aware automation and independent transaction evidence.
Read definitionCognitive AI testing in banking
Cognitive AI testing evaluates AI-supported banking functions alongside the controls and workflows that consume their outputs. Test results depend on representative data, defined acceptance criteria and checks that reflect the consequences of failure.
Read definitionCognitive AI vs generative AI for banking testing
Cognitive AI commonly supports pattern recognition, classification and prediction, while generative AI creates test content and other outputs. Banking teams should validate both against approved requirements, controlled data and risk-based checks.
Read definitionCollateral management system testing
Collateral management system testing verifies collateral eligibility, valuation, margin workflows and movement records against configured agreement terms. It also checks that data and settlement statuses remain consistent across connected systems.
Read definitionCommercial bank AI underwriting human review testing
Commercial bank AI underwriting human review testing checks that cases are routed correctly, reviewers see reliable evidence and permitted decisions persist across lending systems. It also separates workflow verification from evaluation of the model’s recommendations.
Read definitionCommercial bank collateral valuation integration testing
Commercial bank collateral valuation integration testing verifies that valuation data moves accurately between collateral, valuation and lending systems. It checks mapping, processing outcomes, downstream credit effects and failures such as invalid or delayed valuations.
Read definitionCommercial bank credit facility renewal testing
Commercial bank credit facility renewal testing checks that a facility’s renewal follows approved decisions and leaves consistent terms and records across connected banking systems. Testing covers successful renewals, exceptions, approvals and recovery from integration failures.
Read definitionCommercial bank loan covenant workflow testing
Commercial bank loan covenant workflow testing checks that configured facility terms, borrower data, calculations and approval paths produce correct, traceable servicing outcomes. Coverage should include thresholds, exceptions, permissions, integrations and recovery from failed processing.
Read definitionCommercial bank relationship manager portal testing
Commercial bank relationship manager portal testing checks that staff can access the right customer records and complete permitted workflows reliably. The entry explains how to test permissions, integrations, security controls, test data and evidence.
Read definitionCommercial bank SME onboarding testing
Commercial bank SME onboarding testing validates the full business-customer journey, from application data and KYB checks through review decisions and account creation. Effective tests verify both workflow states and the resulting records across connected systems.
Read definitionCommercial lending workflow testing
Commercial lending workflow testing checks that business lending cases progress correctly through decision-making, approval and facility setup across people and systems. It combines role, rules, data and integration checks, including failure handling.
Read definitionCommunity bank AI chatbot information accuracy testing
Community bank AI chatbot information accuracy testing compares chatbot claims with approved bank sources and connected-system results. It covers unanswerable questions, source freshness, numerical assertions, variability and defect evidence.
Read definitionCommunity bank branch teller to ledger testing
Community bank teller-to-ledger testing traces branch transactions from teller capture through customer account and accounting updates. It verifies posting rules, failure handling, traceability and reconciliation across synchronous and delayed interfaces.
Read definitionCommunity bank digital onboarding integration testing
Community bank digital onboarding integration testing verifies data and business outcomes across onboarding, identity, screening and core banking systems. The entry explains environment preparation, failure-path checks and a practical approval scenario.
Read definitionCommunity bank outsourced core banking testing
Community bank outsourced core banking testing combines vendor release evidence with bank-led checks of configured workflows, financial outcomes, integrations and controls. Clear ownership, traceable results and risk-based acceptance criteria help the bank make a defensible release decision.
Read definitionCommunity bank remote deposit capture testing
Community bank remote deposit capture testing checks the complete journey from customer eligibility and cheque-image capture to deposit processing, account posting and notification. It should cover bank-specific rules, vendor and core integrations, mobile failures, duplicate submissions and reconciliation.
Read definitionCommunity bank vendor upgrade regression testing
Community bank vendor upgrade regression testing checks that an upgraded third-party system preserves existing banking workflows, data and integrations. The entry explains how to scope tests, verify a teller deposit end to end and assess failures against release criteria.
Read definitionCompound interest calculation testing
Compound interest calculation testing verifies that rates, periods, dates and rounding rules produce the specified balance and interest. Independent expected results and controlled test data help identify defects in calculations and downstream postings.
Read definitionComputer vision test automation for banking
Computer vision automation can interact with banking screens that lack accessible selectors or APIs. Reliable coverage combines visual checks with independent validation of transaction data and careful control of test environments and evidence.
Read definitionConfirmation of Payee testing
Confirmation of Payee testing verifies that payee details are checked correctly and that each service response produces the intended customer and payment outcome. It covers API integration, test data, response handling and failure scenarios.
Read definitionConsumer lending application testing
Consumer lending application testing verifies the software and workflows that handle applications, decisions, funding and servicing for individual borrowers. Tests should trace to approved product rules and cover calculations, integrations, application states and compliance evidence.
Read definitionContactless payment testing
Contactless payment testing checks the tap and the payment flow that follows it, including terminal behaviour, authorisation and transaction records. Tests need controlled credentials and an environment configured for the payment route in scope.
Read definitionCooperative bank branch system integration testing
Cooperative bank branch system integration testing verifies that teller workflows and connected banking systems exchange consistent data and produce the expected financial outcomes. The entry explains how to prepare test conditions, trace a transaction across interfaces and assess failures.
Read definitionCooperative bank dividend distribution testing
Cooperative bank dividend distribution testing verifies that member eligibility, calculations, approvals, accounting and payments follow the bank's documented rules. It also checks retries, exceptions and member-level reconciliation.
Read definitionCooperative bank member onboarding testing
Cooperative bank member onboarding testing checks the applicant journey, membership rules and downstream account records across connected systems. Effective coverage includes valid and failed checks, duplicate prevention, recovery, audit evidence and state consistency.
Read definitionCooperative bank member share allocation testing
Cooperative bank member share allocation testing checks that configured rules produce correct member share records and consistent accounting outcomes. Effective tests cover eligibility, precision, batch controls, retries and audit evidence.
Read definitionCooperative bank risk-scored test case generation
Risk-scored test case generation links cooperative banking requirements to plausible failure conditions, then ranks derived tests using agreed impact and likelihood criteria. The entry explains a practical workflow and shows how to validate a dividend eligibility change across member and ledger records.
Read definitionCooperative bank shared platform upgrade testing
Cooperative bank shared platform upgrade testing verifies the common platform and each participating bank's configuration, data and integrations after a release. The entry covers scope, test execution, a practical scenario and release evidence.
Read definitionCore banking configuration testing
Core banking configuration testing checks that configured product parameters and business rules produce the expected account, transaction and ledger outcomes. It also verifies relevant boundaries, effective dates and regression risks after a change.
Read definitionCore banking data migration testing
Core banking data migration testing verifies that converted banking records are complete, correctly mapped and financially consistent in the target platform. It combines reconciliation with record-level checks and tests of migrated data in target workflows.
Read definitionCore banking integration testing
Core banking integration testing checks whether connected banking systems exchange requests and data correctly and produce consistent transaction and ledger outcomes. The entry explains scope, prerequisites, a transfer test example and common failure modes.
Read definitionCore banking regression testing
Core banking regression testing reruns relevant checks after system changes to detect unintended effects on established banking workflows and financial records. Its value depends on sound impact analysis, controlled test conditions and assertions that verify downstream outcomes.
Read definitionCore banking replacement testing
Core banking replacement testing checks that migrated records, financial processing and connected systems work correctly on a new core platform. It also provides evidence for cutover readiness and migration risk decisions.
Read definitionCore banking system testing
Core banking system testing verifies account and transaction processing, including ledger updates, integrations and operational jobs. A sound test checks resulting financial records as well as service responses, including after retries and failures.
Read definitionCore banking upgrade testing
Core banking upgrade testing verifies the effects of a software or configuration change on existing banking services and related systems. Its scope should follow the changes, dependencies and risks in the target release.
Read definitionCOREP reporting system testing
COREP reporting system testing verifies that prudential reporting data remains accurate and traceable from source systems through calculation, validation and submission. A sound approach combines rule-based tests, reconciliations, integration checks and controlled evidence.
Read definitionCorporate action processing testing
Corporate action processing testing verifies that securities events produce the correct cash or securities outcomes for eligible accounts. It also checks event changes, retries and consistency across connected systems.
Read definitionCorporate bank account entitlement testing
Corporate bank account entitlement testing verifies that account and transaction permissions match each user's role, entity access and mandate. It tests allowed actions, denials and resulting system state across relevant banking channels.
Read definitionCorporate bank AI document processing validation
Validation should cover document classification and extraction as well as the banking workflow that consumes the results. Risk-focused test data, confidence handling, approval controls and regression checks help expose errors with financial or operational impact.
Read definitionCorporate bank bulk payment partial rejection testing
Corporate bank bulk payment partial rejection testing checks whether valid items proceed and invalid items are rejected with correct statuses and financial effects. Test expectations must reflect the batch policy, payment rail and rejection stage.
Read definitionCorporate bank cash pool interest allocation testing
Cash pool interest allocation testing checks that interest is distributed according to documented pool rules and traceable source data. It also verifies participant postings, reconciliation totals, rounding and handling of invalid or incomplete inputs.
Read definitionCorporate bank delegated payment approval testing
Corporate bank delegated payment approval testing checks that delegated users can approve only eligible payments under the configured grant and approval policy. It also verifies denied actions, workflow state changes and traceable audit records.
Read definitionCorporate bank liquidity dashboard consistency testing
Corporate bank liquidity dashboard consistency testing compares dashboard measures with independently calculated expectations for matching scopes and cut-offs. The entry describes test data, reconciliation steps, a worked example and common causes of discrepancies.
Read definitionCorporate bank mandate expiry testing
Corporate bank mandate expiry testing verifies when payment authority ends and how that change affects signatories, approvals and transactions across banking channels. The entry covers boundary cases, dependencies, test data and outcome checks.
Read definitionCorporate bank multi-entity account testing
Corporate bank multi-entity account testing verifies that account access and banking workflows follow each legal entity's ownership and configured entitlements. The entry covers test data, access checks, payment boundaries and evidence to capture.
Read definitionCorporate bank risk-scored test case generation
Risk-scored test case generation converts corporate banking failure scenarios into traceable cases and a reasoned execution priority. The entry explains scoring inputs, payment workflow examples, review checks and limits of using scores to select tests.
Read definitionCorporate bank trade finance document testing
Trade finance document testing verifies document capture, configured business rules and discrepancy handling for corporate banking transactions. It also checks that document decisions produce the expected workflow and downstream system outcomes.
Read definitionCorporate bank treasury API integration testing
Corporate bank treasury API integration testing verifies that bank and treasury systems exchange accurate data and complete agreed workflows safely. The entry explains how to prepare test environments, assert payment outcomes and handle uncertain results, retries and reconciliation.
Read definitionCorporate banking portal testing
Corporate banking portal testing validates business-user access, payment workflows, account information and connected services against defined rules. It combines role-based checks with transaction-level evidence from downstream systems.
Read definitionCorporate cash management platform testing
Corporate cash management platform testing checks cash, payment, access-control and reporting workflows alongside the integrations that connect the platform to banks and other systems. It verifies outcomes using transaction states, interface evidence, audit records and reconciliation.
Read definitionCorporate liquidity sweep testing
Corporate liquidity sweep testing checks that configured rules generate the correct transfers between corporate accounts and that connected systems report consistent outcomes. It also exercises rejection, timeout, retry and reconciliation behaviour.
Read definitionCorporate multi-bank connectivity testing
Corporate multi-bank connectivity testing checks communication between corporate banking systems and multiple banks, including channel setup, authentication, message exchange and response handling. It confirms connectivity behaviour while broader integration tests verify downstream payment processing and reconciliation.
Read definitionCorporate payment approval matrix testing
Corporate payment approval matrix testing checks that payment rules route approvals correctly and prevent unauthorised approval or release. It covers rule boundaries, roles, workflow transitions, audit records and downstream controls.
Read definitionCorporate payment file duplicate detection testing
Corporate payment file duplicate detection testing verifies matching rules for repeated files and instructions, along with the resulting statuses and payment effects. Tests should cover retries, concurrent submissions and legitimate similar payments to check both duplicate suppression and false positives.
Read definitionCorporate payment signing mandate testing
Corporate payment signing mandate testing checks that signatory authority and approval combinations match the applicable account mandate throughout the payment workflow. Effective tests cover valid and invalid combinations, boundary amounts, mandate changes, release eligibility and audit records.
Read definitionCorporate treasury portal testing
Corporate treasury portal testing verifies financial workflows, permissions and connected-system outcomes using controlled users, test data and environments. The entry explains how to test payment approvals, reconciliation, security and recovery from integration failures.
Read definitionCorrespondent bank beneficiary data integrity testing
Correspondent bank beneficiary data integrity testing traces beneficiary fields across a cross-border payment chain and checks that each change follows an agreed rule. It helps identify data loss, incorrect mapping and unintended alterations between connected systems.
Read definitionCorrespondent bank fee deduction reconciliation testing
Correspondent bank fee deduction reconciliation testing checks whether intermediary fees and resulting settlement amounts agree with payment instructions and bank records. It also verifies that mismatches, missing advice and duplicate records are handled safely.
Read definitionCorrespondent bank nested payment chain testing
Nested correspondent banking payment chain testing verifies the route, payment data, controls and accounting across banks where one respondent uses another bank’s correspondent access. A sound test follows the payment across each participant and checks both successful processing and controlled failure.
Read definitionCorrespondent bank nostro funding alert testing
Correspondent bank nostro funding alert testing validates configured balance and forecast triggers, their inputs, and the resulting alert lifecycle. Use controlled data to check boundaries, delayed feeds, recovery and evidence without initiating live funding movements.
Read definitionCorrespondent bank payment investigation workflow testing
Test the full investigation lifecycle, including payment matching, case transitions, correspondent responses and audit controls. Use controlled data and simulated responses to verify retries, exceptions and cross-system consistency.
Read definitionCorrespondent bank payment repair workflow testing
Test the full repair path from exception creation to downstream payment hand-off, checking permissions, revalidation, data invariants and audit history. Verify retries and timeouts cannot create duplicate instructions or release unresolved payments.
Read definitionCorrespondent bank risk-scored test case generation
Correspondent bank risk-scored test case generation ranks payment workflow risks and converts them into test conditions with traceable, verifiable expected results. Scores guide test priority and should be calibrated to local requirements and controls.
Read definitionCorrespondent bank sanctions hold release testing
Correspondent bank sanctions hold release testing checks that only an authorised, evidenced decision can resume a held payment. It also verifies payment state changes, audit records, downstream processing and safe handling of retries.
Read definitionCorrespondent banking integration testing
Correspondent banking integration testing verifies payment and account data as it moves between banks, intermediaries and internal systems. It covers message handling, routing, failure responses, accounting and reconciliation.
Read definitionCredit bureau integration testing
Credit bureau integration testing checks that an application sends valid enquiries, processes bureau responses correctly and handles errors according to its interface and workflow requirements. The entry explains test data, dependencies, failure scenarios and a practical loan application example.
Read definitionCredit card lifecycle testing
Credit card lifecycle testing checks card and account state changes across issuance, use, servicing and closure, including their effects on transactions and financial records. It relies on consistent results across customer channels and connected issuer services.
Read definitionCredit limit management testing
Credit limit management testing verifies that systems apply approved limits consistently when processing transactions and limit changes. It checks decisions, exposure updates, boundary conditions and interactions with connected services.
Read definitionCredit union AI loan document extraction testing
Credit union AI loan document extraction testing compares extracted fields with reviewed source documents and verifies validation, review routing and downstream updates. Effective tests cover varied document quality, sensitive data handling and failures across the loan workflow.
Read definitionCredit union core conversion reconciliation testing
Credit union core conversion reconciliation testing compares migrated records and financial controls with an agreed source baseline. Reliable results depend on consistent snapshots, documented transformation rules, account-level investigation and explicit release criteria.
Read definitionCredit union member loan refinancing testing
Credit union member loan refinancing testing checks that the existing loan is correctly settled and the replacement loan follows approved product rules. It also verifies connected servicing, payment and accounting records through failure and regression scenarios.
Read definitionCredit union member portal testing
Credit union member portal testing validates member-facing journeys and the accuracy, security and accessibility of portal behaviour. The entry covers test preparation, transaction checks, authentication controls, evidence and common causes of failure.
Read definitionCredit union membership eligibility rule testing
Credit union membership eligibility rule testing checks that configured decisions match the institution’s approved membership criteria and handle incomplete or boundary data as specified. The entry explains how to design decision-table cases and verify results across application workflows.
Read definitionCredit union payroll deduction loan repayment testing
Credit union payroll deduction loan repayment testing checks that authorised amounts move accurately from employer payroll into the correct loan account. It covers posting rules, duplicate handling, exceptions and reconciliation across connected systems.
Read definitionCredit union share account testing
Credit union share account testing checks account rules and member-facing behaviour against configured product requirements, while tracing financial activity through core and ledger systems. The entry explains test scope, lifecycle and balance checks, data controls and a worked minimum-balance example.
Read definitionCritical banking workflow testing
Critical banking workflow testing validates selected high-impact banking journeys across their dependent applications and services. It checks business outcomes, financial records, control behaviour and recovery paths using controlled test data and traceable evidence.
Read definitionCross-application banking test automation
Cross-application banking test automation verifies workflows and state across connected banking applications and services. Effective tests use controlled data, correlate transactions across systems and check outcomes where each state is recorded.
Read definitionCross-border payment currency conversion testing
Cross-border payment currency conversion testing validates the rate, conversion calculation and resulting amounts across the payment journey. It also checks rounding, fees, timing, failure handling and consistency between customer channels, payment messages and ledger records.
Read definitionCross-border payment reconciliation testing
Cross-border payment reconciliation testing verifies that internal payment and accounting records match external statements or partner records according to defined rules. It also checks how the system identifies and reports incomplete, duplicated or inconsistent records.
Read definitionCross-border payment status tracking testing
Cross-border payment status tracking testing checks that status information remains consistent from initiation through the available outcome. It focuses on asynchronous updates, identifier correlation, status mapping and recovery from incomplete or out-of-order events.
Read definitionCross-border payment testing
Cross-border payment testing verifies international payment processing across currencies, countries and connected services. It covers conversion, charges, routing, failure handling and consistent transaction records.
Read definitionCross-channel banking consistency testing
Cross-channel banking consistency testing verifies that customer and transaction state is accurate across banking channels within defined business rules and propagation times. Effective tests compare channel behaviour with authoritative records and account for asynchronous updates.
Read definitionCross-system testing in banking
Cross-system testing checks that banking workflows preserve correct data and business outcomes as they move between applications, ledgers and external services. The entry explains how to set up and verify these tests, including retries, asynchronous processing and failure paths.
Read definitionCurrent account opening testing
Current account opening testing validates the applicant journey and the connected services that assess eligibility and establish an account. It checks expected decisions, system state, error handling and duplicate prevention.
Read definitionCustodian bank asset servicing testing
Custodian bank asset servicing testing checks the processing of securities events and related client services across custody systems. It validates event data, eligibility, instructions, entitlements and downstream records against defined business and market rules.
Read definitionCustodian bank corporate action election testing
Custodian bank corporate action election testing validates the handling of client choices for eligible securities events, from instruction capture and submission to final allocation. It checks event rules, deadlines, acknowledgements, position changes and cash outcomes.
Read definitionCustodian bank securities transfer reconciliation testing
Custodian bank securities transfer reconciliation testing verifies that expected securities movements agree with settlement confirmations and custody records. It checks matching rules, partials, duplicates, linked cash where relevant, and the visibility of unresolved breaks.
Read definitionCustodian bank settlement instruction change testing
Custodian bank settlement instruction change testing checks that approved instruction data reaches the right systems and is selected for the right trades. The entry covers test data, effective-date scenarios, failure paths and evidence.
Read definitionCustodian bank tax reclaim workflow testing
Custodian bank tax reclaim workflow testing verifies the rules, data and system hand-offs that carry a reclaim from income event through submission and reconciliation. The entry covers lifecycle states, integration failures, duplicate handling and an illustrative end-to-end test.
Read definitionCustody platform testing
Custody platform testing verifies that asset movements and servicing events are processed accurately across custody records and connected systems. It also checks reconciliation, access controls, exception handling and the evidence needed to investigate failures.
Read definitionCustomer due diligence workflow testing
Customer due diligence workflow testing verifies that customer checks, risk decisions and reviews follow configured process rules across connected systems. It also checks case controls, test data and evidence needed to investigate results.
Read definitionCustomer risk rating rule testing
Customer risk rating rule testing checks that defined business conditions produce the expected rating, including boundary and overlapping cases. It also verifies that the result is stored and propagated consistently when rules or customer data change.
Read definition
D
Debit card lifecycle testing
Debit card lifecycle testing verifies card state transitions and related transaction behaviour across issuer, processor and account systems. It uses defined state rules and cross-system evidence to find inconsistent statuses, declines and posting errors.
Read definitionDecision table testing for banking rules
Decision tables make combinations of banking rule conditions and outcomes explicit, helping teams derive focused tests and review rule completeness. The example shows how to test card authorisation decisions, including conditions treated as irrelevant and spending-limit boundaries.
Read definitionDeposit insurance eligibility data testing
Deposit insurance eligibility data testing validates the records and processing used to determine deposit eligibility and coverage under an approved jurisdiction-specific ruleset. Effective tests trace fields end to end, check relationships and boundary cases, and preserve reproducible evidence.
Read definitionDeposit rollover testing
Deposit rollover testing checks that a maturing term deposit follows its configured renewal or payout instruction and produces correct account and accounting records. It also verifies dependency-sensitive rules and safe recovery from interrupted processing.
Read definitionDerivatives processing system testing
Derivatives processing system testing validates trade terms, calculations, lifecycle events and downstream processing across derivatives applications. Reliable results depend on controlled market data, product rules and independent checks.
Read definitionDevelopment bank grant and loan reporting integration testing
Development bank grant and loan reporting integration testing verifies that financial and project data transfers correctly into reporting systems and follows approved definitions. The entry explains test preparation, scenario coverage, reconciliation and a worked loan example.
Read definitionDevelopment bank milestone approval testing
Development bank milestone approval testing verifies that project evidence and programme rules lead to authorised, traceable funding decisions. It also checks workflow exceptions and the accuracy of any downstream disbursement.
Read definitionDevelopment bank multi-currency funding workflow testing
Development bank multi-currency funding workflow testing verifies funding decisions, currency calculations and downstream accounting and payment outcomes across connected systems. The entry explains test setup, workflow assertions, failure cases and a worked FX example.
Read definitionDevelopment bank project loan disbursement testing
Development bank project loan disbursement testing checks that each tranche meets facility-specific conditions and is correctly approved, paid, recorded and reconciled. It also verifies failure handling, duplicate protection and cross-system evidence.
Read definitionDigital identity verification testing
Digital identity verification testing checks whether an identity proofing workflow reaches the correct decision and preserves that decision across connected systems. It covers evidence handling, biometric paths, provider failures, security, privacy and downstream account states.
Read definitionDigital operational resilience testing in banking
Digital operational resilience testing evaluates whether banking services can withstand disruption and recover within defined impact limits. It covers technology alongside operational response, dependencies and customer outcomes.
Read definitionDigital wallet card provisioning testing
Digital wallet card provisioning testing validates the workflow that adds and manages a payment card in a digital wallet. It checks customer verification, service integrations, credential status, failure handling and safe use of test data.
Read definitionDigital-only bank chatbot to human handover testing
Digital-only bank chatbot to human handover testing verifies that customers reach the right support queue with appropriate conversation context and security controls. It also checks customer messaging, agent responses and recovery when the transfer path fails.
Read definitionDividend payment processing testing
Dividend payment processing testing verifies dividend eligibility and amounts, then checks deductions, payment outcomes and accounting records. Testing should cover integrations, exceptions, retries and reconciliation using controlled data and explicit business rules.
Read definitionDocumentary collection workflow testing
Documentary collection workflow testing validates that a trade finance system follows collection instructions from lodgement through presentation and settlement. It also checks controls, connected systems and exception paths such as refusal, short payment or failed messages.
Read definitionDomestic bank transfer testing
Domestic bank transfer testing verifies that in-country payment instructions follow the bank's applicable rules from submission through recording and reconciliation. Coverage depends on the payment route, account rules and domestic scheme behaviour.
Read definitionDORA end-to-end testing
DORA end-to-end testing follows a business service across its dependent systems and providers to assess expected outcomes and, where designed, behaviour under disruption. It contributes evidence to a financial entity's resilience testing programme, but does not by itself demonstrate DORA compliance.
Read definitionDORA risk-based testing programme
A DORA risk-based testing programme organises resilience testing around the ICT risks that could affect financial services. It connects risk assessments to test selection, evidence and remediation, including scenarios involving third-party dependencies.
Read definitionDORA scenario-based testing
DORA scenario-based testing uses plausible ICT disruption scenarios to assess a financial entity's ability to maintain or recover important services. It supports the wider resilience testing programme, with results assessed against defined objectives and documented alongside limitations and follow-up actions.
Read definitionDORA testing evidence management
DORA testing evidence management organises records that demonstrate how an entity tests digital operational resilience and responds to findings. Traceable evidence links risks and test conditions to results, remediation and retesting.
Read definitionDORA testing for banks
DORA testing for banks is a proportionate programme covering the ICT systems and dependencies that support critical or important functions. Banks need to test recovery against defined outcomes, document findings and retest remediation.
Read definitionDormant bank account testing
Dormant bank account testing checks that configured inactivity rules drive the correct account state and customer behaviour. Reliable tests use controlled dates and data, exercise boundaries and transitions, and reconcile outcomes across channels and connected systems.
Read definitionDouble-entry posting validation in banking
Double-entry posting validation checks that a banking transaction creates balanced debit and credit entries and follows its posting rules. Tests should also verify account mapping, currency, transaction state and the absence of partial or duplicate postings.
Read definitionDuplicate payment prevention testing
Duplicate payment prevention testing verifies how payment systems handle retries, repeated messages and concurrent submissions. It checks persisted payment and ledger evidence to confirm that one logical payment produces no more than one financial effect.
Read definition
E
Electronic KYC workflow testing
Electronic KYC workflow testing validates digital identity checks, decision rules and case transitions across customer-facing systems and verification providers. It also checks exception handling, audit evidence, data protection and controlled test conditions.
Read definitionEmbedded banking customer journey testing
Embedded banking customer journey testing follows a customer task across the host product and the banking services it depends on. It verifies customer-visible outcomes, service behaviour and financial records, including recovery from failures and delayed updates.
Read definitionEmbedded banking payment status synchronisation testing
Embedded banking payment status synchronisation testing verifies that asynchronous provider updates map correctly to internal records and customer-facing states. It should cover event ordering, duplicate delivery, delays, returns and related accounting effects.
Read definitionEnd-to-end testing in banking
End-to-end testing in banking checks whether a full business workflow produces the expected customer outcome and financial records across connected systems. A transfer example shows how to validate status, postings, notifications and reconciliation.
Read definitionEnhanced due diligence workflow testing
Enhanced due diligence workflow testing verifies policy-based routing, evidence handling, authorised decisions and consistent outcomes across connected banking systems. It combines controlled test data with end-to-end assertions and regression coverage for workflow changes.
Read definitionExplainable AI for banking test prioritisation
Explainable AI ranks banking tests using change, defect, workflow and execution data, then gives reasons for its recommendations. Teams must verify those reasons, protect mandatory coverage and retain human control of release decisions.
Read definitionExploratory testing in banking
Exploratory testing in banking combines learning, test design and execution to investigate uncertain behaviour in financial workflows. Defined charters, controlled data and clear evidence help teams find issues while managing transaction risk.
Read definitionExport-import bank buyer credit servicing testing
Export-import bank buyer credit servicing testing validates that a buyer credit follows its approved terms across servicing calculations, payment processing and accounting. It combines lifecycle, exception and integration checks with reconciliation of facility balances and transaction records.
Read definitionExport-import bank credit guarantee workflow testing
Export-import bank credit guarantee workflow testing validates configured rules and the full guarantee lifecycle across users and connected systems. The entry explains scenario design, integration failure handling, controlled test data and evidence checks.
Read definition
F
Failed trade handling testing
Failed trade handling testing checks how trading systems detect and manage exceptions from booking through settlement. It verifies recovery actions, cross-system consistency and traceable outcomes.
Read definitionFailure likelihood assessment for banking software
Failure likelihood assessment estimates the chance of a defined banking software failure under stated conditions, using evidence and explicit assumptions. Its value comes from directing tests towards plausible scenarios and recording the uncertainty that remains.
Read definitionFaster Payments testing
Faster Payments testing checks that a bank or provider handles UK FPS transactions correctly across its connected systems. It includes normal processing, rejection, timeout recovery, duplicate prevention and reconciliation.
Read definitionFedNow payment workflow testing
FedNow payment workflow testing follows an instant credit payment across bank channels, payment interfaces, ledger posting and reconciliation. Effective coverage checks message and business rules alongside rejection, timeout and duplicate-handling behaviour.
Read definitionFedwire payment workflow testing
Fedwire payment workflow testing checks the complete payment path, with explicit assertions for settlement, accounting and uncertain outcomes. Use isolated test data and environments to exercise normal processing, rejection, duplicate prevention and timeout recovery.
Read definitionFinacle core banking testing
Finacle core banking testing verifies configured banking workflows, financial records and connected systems in a bank’s Finacle implementation. Reliable results depend on controlled configuration, representative test data and verification beyond the user interface.
Read definitionFINREP reporting system testing
FINREP reporting system testing verifies that financial data is accurately transformed into the reports required for supervisory submission. It covers mappings, calculations, validations, reconciliation and traceability across the reporting flow.
Read definitionFIS banking platform testing
FIS banking platform testing verifies the bank’s specific product configuration, business workflows and system integrations. The entry explains how to prepare scenarios and data, check financial outcomes and use evidence to assess failures and release readiness.
Read definitionFiserv banking platform testing
Fiserv banking platform testing must reflect the bank’s specific product, configuration, interfaces and deployment environment. This guide explains how to test workflows and financial outcomes, prepare repeatable data, and assess failures and release evidence.
Read definitionFixed deposit early withdrawal testing
Fixed deposit early withdrawal testing verifies eligibility, contractual recalculation and the complete financial effect of an early closure. Reliable tests use explicit product rules and reconcile the customer outcome with persisted payment and ledger records.
Read definitionForeign exchange trading workflow testing
Foreign exchange trading workflow testing checks trade states, business rules and data consistency across connected systems. It covers successful trades as well as rejection, timeout, retry and settlement outcomes.
Read definitionFraud detection system integration testing
Fraud detection system integration testing verifies that connected services exchange valid data and apply fraud decisions correctly. Tests should cover interface contracts, downstream actions, dependency failures and controlled test data.
Read definitionFront-to-back trade lifecycle testing
Front-to-back trade lifecycle testing follows a defined trade through relevant front-, middle- and back-office systems. It verifies lifecycle states, data continuity, exception handling and final positions or postings against expected outcomes.
Read definitionFunctional testing in banking
Functional testing in banking checks that software carries out defined banking operations and applies business rules correctly. The entry explains test design, environmental dependencies and a worked internal transfer example.
Read definitionFX settlement testing
FX settlement testing verifies the processing and recording of both payment obligations created by an FX trade. Its scenarios should reflect the settlement route and include failures, retries and reconciliation checks.
Read definition
G
General ledger and subledger reconciliation testing
General ledger and subledger reconciliation testing confirms that detailed subledger activity agrees with its corresponding general ledger control accounts. It also tests posting paths, reconciliation exceptions and evidence needed to trace mismatches.
Read definitionGenerative AI in banking software testing
Generative AI can draft banking test scenarios, code and synthetic data from requirements and prompts. Its outputs need review, independent expected-result checks and controls for sensitive information.
Read definition
H
High-risk banking transaction testing
High-risk banking transaction testing targets flows where failure could affect funds, customers or critical services. It verifies business controls, financial records, failure handling and consistent outcomes across connected systems.
Read definitionHost-to-host banking integration testing
Host-to-host banking integration testing verifies the complete exchange of files and processing outcomes between a bank and a connected organisation. It covers transport, data validation, acknowledgements, payment status, security controls and recovery behaviour.
Read definitionHuman validation of AI banking risk assessments
Human validation checks whether an AI-generated banking risk assessment is supported by relevant evidence and handled under defined procedures. Testing covers reviewer access, challenge and escalation, downstream actions and decision records.
Read definitionHuman-in-the-loop banking test automation
Human-in-the-loop banking test automation combines automated execution with human review at defined decision points. Clear criteria, controlled test data and recorded decisions help prevent review from masking defects.
Read definition
I
IFRS 9 calculation system testing
IFRS 9 calculation system testing checks that implemented ECL calculations, staging, data handling and downstream outputs follow approved methods. It uses controlled test cases, independent expected results and reconciliations to expose defects and assess changes.
Read definitionInstant payment testing
Instant payment testing checks that real-time transfers follow scheme rules and produce consistent outcomes across connected systems. It also verifies timing, status handling, duplicate prevention and recovery from errors.
Read definitionIntegration testing in banking
Integration testing in banking checks that connected services exchange and process transaction data according to interface contracts and business rules. The entry explains test conditions and illustrates assertions for an outbound payment, including retry and failure handling.
Read definitionIntermediary bank routing testing
Intermediary bank routing testing checks that a payment follows its configured path through intermediary or correspondent banks. It verifies route selection, message data integrity and the handling of acknowledgements, failures and reconciliation.
Read definitionInternational payment fee calculation testing
International payment fee calculation testing checks configured charges, currency conversion and rounding against an independent expected result. Tests should control rate inputs and trace the fee through payment processing and account posting.
Read definitionInvestment bank collateral call reconciliation testing
Investment bank collateral call reconciliation testing verifies that internal and counterparty call records agree with agreement terms and the underlying exposure and collateral data. It also checks how discrepancies are detected, investigated and reflected in settlement workflows.
Read definitionInvestment bank market data outage testing
Investment bank market data outage testing verifies how trading and risk systems detect feed failures, enforce approved controls and recover consistent data. The entry covers scenario design, safe fault injection, evidence and a delayed-price example.
Read definitionInvestment bank risk-scored test case generation
Risk-scored test case generation applies an agreed risk assessment to test design and prioritisation for investment banking workflows. Its results depend on current evidence, clear scoring criteria and human review of generated cases.
Read definitionInvestment bank trade amendment downstream testing
Investment bank trade amendment downstream testing checks that an authorised trade change reaches affected consumers with correct recalculations, unchanged fields and traceable audit history. The entry covers test data, asynchronous interfaces, duplicate delivery, rejection handling and reconciliation.
Read definitionInvestment bank trade booking integration testing
Investment bank trade booking integration testing verifies that trade data and lifecycle events move correctly between connected systems. It also checks errors, retries, duplicate messages and downstream state.
Read definitionInvestment bank trade confirmation mismatch testing
Investment bank trade confirmation mismatch testing verifies that differences between booked trades and counterparty confirmations are detected, classified and handled according to defined rules. The entry covers test data, lifecycle cases, workflow assertions and evidence for investigating failures.
Read definitionInvestment bank trading limit breach workflow testing
Investment bank trading limit breach workflow testing checks both the configured exposure decision and the workflow that follows it. Tests should cover threshold boundaries, permissions, failure handling, downstream consistency and evidence against approved policy.
Read definitionInvestment fee calculation testing
Investment fee calculation testing checks that approved rates are applied to the correct assets and billing periods, with the expected tiering, proration and rounding. Reliable tests use controlled data, an independently calculated oracle and verification of the resulting charge and postings.
Read definitionInvestment suitability workflow testing
Investment suitability workflow testing checks that client information and product rules lead to the expected recommendation, restriction or review outcome. It also verifies system integrations, workflow controls and records supporting that outcome.
Read definitionInvoice finance workflow testing
Invoice finance workflow testing validates business rules and system hand-offs from invoice submission to funding and settlement. It also checks financial records, permissions, retries and exception recovery.
Read definitionISO 20022 business rule testing
ISO 20022 business rule testing verifies that message data and combinations meet the rules governing a payment or other financial process. Effective tests use the applicable message version and guideline, then assert both the decision and its processing effects.
Read definitionISO 20022 message schema validation
ISO 20022 message schema validation checks an XML message against the XSD for its intended message version. It confirms structural conformance, while business rules and network-specific requirements need separate validation.
Read definitionISO 20022 message testing
ISO 20022 message testing verifies a message against its selected schema, transaction meaning and applicable market or participant rules. Effective tests use the right version and profile, then check the receiving system's processing outcome.
Read definition
L
Legacy banking system testing
Legacy banking system testing checks that changes to older banking applications preserve business rules, data integrity and operational behaviour. It requires careful validation of batch processing, interfaces, test data and downstream financial results.
Read definitionLetter of credit lifecycle testing
Letter of credit lifecycle testing verifies that LC states, rules, documents and connected banking systems behave correctly from issuance through closure. It includes negative paths such as discrepancies, retries, expiry and failed downstream processing.
Read definitionLLM application testing for banks
LLM application testing for banks evaluates model behaviour alongside data access, integrations and banking controls. A risk-led approach uses versioned test data, adversarial cases and evidence from the full application path.
Read definitionLLM evaluation in banking
LLM evaluation in banking assesses a model and its surrounding application against use-case requirements, approved sources and risk-based acceptance criteria. It provides evidence for release and change decisions, but cannot establish safe behaviour for every possible input.
Read definitionLoan amortisation schedule testing
Loan amortisation schedule testing verifies payment, interest and balance calculations against the loan’s contractual rules. Reliable tests use independent expected results and check row-level arithmetic, totals, boundary inputs and schedule changes.
Read definitionLoan arrears management testing
Loan arrears management testing verifies that overdue repayments trigger the correct account calculations, collection workflows and records under configured loan rules. It also checks payment updates and integrations that can change arrears status.
Read definitionLoan early repayment testing
Loan early repayment testing verifies that partial repayments and full payoffs follow the loan's configured terms. It checks calculations, allocation, account state and related records after the payment is processed.
Read definitionLoan interest calculation testing
Loan interest calculation testing compares accrued interest and resulting loan balances with independently derived expected results. Reliable tests use explicit product rules for dates, rates, day-count conventions and rounding.
Read definitionLoan management system testing
Loan management system testing checks that loan rules, financial records and connected services behave consistently throughout servicing. The entry explains how to plan lifecycle tests, verify repayment processing and investigate common failures.
Read definitionLoan origination system testing
Loan origination system testing verifies that applications move through configured assessment and decision workflows with accurate data and outcomes. The entry covers integration checks, test data controls, failure scenarios and evidence for an end-to-end application journey.
Read definitionLoan payment holiday testing
Loan payment holiday testing verifies that approved repayment pauses follow product rules across interest, balances, schedules and connected systems. The entry explains scenario design, calculation checks, integration coverage and failure testing.
Read definitionLoan repayment allocation testing
Loan repayment allocation testing checks whether servicing software applies received funds according to configured product rules. It verifies component balances, schedules and transaction records, including boundary cases and retries.
Read definitionLoan restructuring workflow testing
Loan restructuring workflow testing verifies the process and financial changes applied to an existing loan, including approvals, revised schedules and relevant downstream updates. Its scenarios should reflect documented product rules, integration behaviour and failure handling.
Read definitionLoan servicing platform testing
Loan servicing platform testing verifies loan lifecycle rules, calculations and connected system behaviour against product terms. A partial repayment example shows how to check allocation and duplicate handling.
Read definition
M
Machine learning for banking test automation
Machine learning can rank banking tests, classify failures and detect unusual execution patterns using historical test and change data. Safe use depends on sound labels, controlled data, reviewable recommendations and deterministic checks for release-critical workflows.
Read definitionMambu integration testing
Mambu integration testing verifies that configured interfaces exchange correct data and preserve expected business outcomes across Mambu and connected services. Effective tests cover contracts, test data, asynchronous processing, duplicates and recovery behaviour.
Read definitionMargin call workflow testing
Margin call workflow testing validates the full collateral call process, from calculation and notification to settlement and reconciliation. It also checks exception handling, data consistency and control points across connected systems.
Read definitionMerchant acquiring platform testing
Merchant acquiring platform testing verifies transaction and merchant workflows across the systems involved in card acceptance, clearing and payout. It checks financial outcomes, data consistency, exception handling and reconciliation.
Read definitionMicrofinance bank group lending workflow testing
Microfinance bank group lending workflow testing validates group and member rules across the loan lifecycle, including financial outcomes and system integrations. Tests should reflect the bank's configured liability model and verify recovery from failures as well as successful journeys.
Read definitionMicrofinance bank mobile agent cash reconciliation testing
Mobile agent cash reconciliation testing checks whether an agent's physical cash position agrees with recorded cash movements and configured banking rules. It also verifies transaction status, synchronisation, variance handling and relevant downstream postings.
Read definitionMicrofinance bank offline collection synchronisation testing
Microfinance bank offline collection synchronisation testing verifies that agent-recorded repayments survive disconnection and reach the bank once, with the correct status and financial effect. The entry covers test data, retry and conflict scenarios, ledger validation and useful evidence.
Read definitionMicrofinance bank small instalment rounding testing
Microfinance loan instalment rounding testing verifies that schedule calculations and posted repayments follow documented precision and rounding rules. Tests should check small values, residuals, payment allocation and consistency between customer-facing amounts and ledger records.
Read definitionMobile banking app update regression testing
Mobile banking app update regression testing checks that an updated build preserves critical customer journeys and handles existing installations correctly. The entry explains how to select coverage, verify outcomes across app and backend layers, and assess failures.
Read definitionMobile banking application testing
Mobile banking application testing checks customer workflows across the app, devices and connected banking services. It combines interface, API, security and transaction verification to confirm that customer actions produce correct outcomes.
Read definitionMobile banking operating system compatibility testing
Mobile banking operating system compatibility testing verifies app behaviour across supported operating systems, versions and platform services. Its scope includes banking journeys, security-sensitive features and interruption handling.
Read definitionModel-based testing in banking
Model-based testing in banking uses formal workflow or rule models to derive tests for banking applications and connected services. Its value depends on accurate models, risk-based path selection and assertions against real transaction outcomes.
Read definitionMortgage affordability calculation testing
Mortgage affordability calculation testing verifies repayment and affordability rules against approved requirements, including thresholds, rounding and input handling. The entry gives a worked example and explains how to check data mapping and results across system layers.
Read definitionMortgage application workflow testing
Mortgage application workflow testing validates that an application progresses through the lender's configured stages and that decisions, data and hand-offs remain consistent. Effective scenarios cover normal journeys, exceptions and dependencies across connected systems.
Read definitionMortgage bank affordability rule change testing
Mortgage affordability rule change testing checks revised lending logic, effective dates and connected workflows against an approved policy. It combines decision coverage, boundary tests, integration checks and regression evidence.
Read definitionMortgage bank collateral release testing
Mortgage bank collateral release testing verifies that property security is released only through the bank's defined rules and approvals. It also checks consistent status, records and exception handling across connected systems.
Read definitionMortgage bank fixed-rate expiry workflow testing
Mortgage bank fixed-rate expiry workflow testing checks that contract rules, dates and customer instructions produce the correct loan state and payment schedule. It also verifies communications, downstream consistency, retry safety and evidence.
Read definitionMortgage bank partial redemption testing
Mortgage bank partial redemption testing checks whether a lender applies early partial repayments according to product rules and customer instructions. The entry covers test setup, workflow scenarios, calculation checks and cross-system reconciliation.
Read definitionMortgage drawdown testing
Mortgage drawdown testing verifies the rules and system hand-offs involved in releasing approved mortgage funds. It checks payment outcomes, loan and ledger records, status changes, retries and failure recovery.
Read definitionMortgage offer generation testing
Mortgage offer generation testing verifies the content, calculations, workflow status and presentation of mortgage offers against approved source data and rules. It covers both successful document creation and cases where missing or changed information should prevent or alter an offer.
Read definitionMortgage refinancing workflow testing
Mortgage refinancing workflow testing checks that a refinance case progresses correctly across business stages and connected systems. It verifies data integrity, financial reconciliation, settlement controls and recovery from failed or delayed steps.
Read definitionMulti-currency account testing
Multi-currency account testing verifies balances and transactions for each currency, including conversion calculations and their effects on account records and ledgers. Reliable tests use controlled rate data and check failures, retries and rounding against defined product rules.
Read definition
N
Natural language test automation for banks
Natural language test automation converts written banking scenarios into executable actions and assertions through defined mappings and application access. Reliable results depend on precise expected outcomes, controlled test data, review of generated steps and traceable evidence.
Read definitionNegative interest rate processing testing
Negative interest rate processing testing checks that configured rules produce the expected accrual and downstream posting for rates below zero. Test cases should cover rate floors, eligibility boundaries, calculation conventions, rounding and recovery behaviour.
Read definitionNegative testing in banking
Negative testing in banking verifies that prohibited or invalid requests receive the specified outcome without causing unintended transaction effects. Reliable tests control their preconditions and check both responses and resulting system state.
Read definitionNeobank account closure refund testing
Neobank account closure refund testing checks refund handling against documented account-state and payment-provider rules. It validates ledger effects, customer access, duplicate-event safety and reconciliation across connected systems.
Read definitionNeobank card processor integration testing
Neobank card processor integration testing checks that processor requests and events produce correct card, account and transaction outcomes. The entry explains setup, lifecycle coverage, retry and webhook risks, and a purchase-reversal example.
Read definitionNeobank cloud failover testing
Neobank cloud failover testing verifies service continuity, data integrity and transaction safety when cloud infrastructure or a dependency fails. A useful exercise covers controlled fault injection, customer outcomes, recovery objectives, reconciliation and failback.
Read definitionNeobank core banking provider outage testing
Neobank core banking provider outage testing checks how customer journeys and transactions behave when a core provider fails or slows down. It verifies controlled degradation, safe handling of uncertain requests, recovery and reconciliation.
Read definitionNeobank identity verification failure testing
Neobank identity verification failure testing checks that rejected, inconclusive and unavailable checks lead to the correct onboarding state and customer action. The entry explains how to design failure cases, verify recovery and audit evidence, and test an expired-document scenario.
Read definitionNeobank instant payment failure testing
Neobank instant payment failure testing verifies that failed or uncertain transfers produce accurate statuses and consistent account records. It also checks that retries, customer messages and reconciliation processes handle the outcome safely.
Read definitionNeobank mobile app release regression testing
Neobank mobile regression testing checks that a release preserves existing app journeys and the banking services behind them. The entry explains risk-based selection, environment and test data preparation, end-to-end payment verification, and how to assess failures for release readiness.
Read definitionNeobank multi-currency account testing
Neobank multi-currency account testing verifies currency-specific balances and the complete conversion lifecycle, from rate selection through ledger posting and recovery. The entry gives a repeatable example and checks for fees, rounding, retries and cross-system consistency.
Read definitionNeobank onboarding testing
Neobank onboarding testing verifies the customer journey and connected services from application submission through decision and account setup. It checks state transitions, identity and screening results, recovery from failures, and consistency between the app and bank systems.
Read definitionNeobank open banking consent testing
Neobank open banking consent testing verifies that customer permissions are represented accurately and enforced by the app and connected APIs. It covers consent grant, use, review, expiry, revocation and failures across provider boundaries.
Read definitionNeobank partner bank reconciliation testing
Neobank partner bank reconciliation testing verifies that records exchanged between a neobank and its partner bank match under agreed identifiers, timing and tolerance rules. It also checks that missing, duplicated or inconsistent data produces traceable exceptions.
Read definitionNeobank payment retry safety testing
Neobank payment retry safety testing verifies that retries recover payment outcomes without repeating financial effects. It covers idempotency, uncertain responses, downstream instructions and ledger consistency.
Read definitionNeobank push notification delivery testing
Neobank push notification delivery testing follows a banking event through notification services, platform providers and the mobile device. Reliable checks distinguish provider acceptance from display and app navigation, while covering privacy, token ownership, retries and environment conditions.
Read definitionNeobank real-time balance consistency testing
Neobank real-time balance consistency testing compares account balances across authoritative ledgers and downstream views against transaction rules and timing requirements. It should cover event delays, retries, concurrency and recovery, while distinguishing ledger balance from available balance.
Read definitionNeobank risk-scored test case generation
Neobank risk-scored test case generation uses assessed failure likelihood and impact to create and prioritise test scenarios. The entry explains the inputs, review requirements and how to verify a payment retry case across systems.
Read definitionNeobank subscription plan change testing
Neobank subscription plan change testing checks the customer journey and downstream billing and entitlement effects of moving between plans. Tests should derive expected behaviour from approved plan rules, then verify both successful changes and failure recovery.
Read definitionNeobank transaction feed ordering testing
Neobank transaction feed ordering testing verifies the ordering contract across API responses, pagination and customer-facing screens. Reliable checks use controlled timestamps, explicit tie-breakers and assertions for updates, retries and page boundaries.
Read definitionNeobank virtual card limit testing
Neobank virtual card limit testing checks that spending rules hold across authorisation, clearing and reversal flows. It combines boundary value analysis with API and cross-system verification of limit usage and transaction outcomes.
Read definitionNet asset value data integration testing
Net asset value data integration testing verifies that valuation inputs move accurately and completely between financial systems. It also checks data timing, transformations, exception handling and reconciliation evidence.
Read definitionNew beneficiary fraud control testing
New beneficiary fraud control testing checks whether configured controls make the expected decision when a customer adds a payee and initiates a payment. Effective tests trace that decision through authentication, review, payment processing and audit evidence.
Read definitionNo-code test automation for banks
No-code test automation lets teams build automated banking tests through visual interfaces, though it still depends on sound test design and technical controls. Tool evaluation should cover application support, evidence, data security, failure diagnosis and safe reruns.
Read definitionNostro account reconciliation testing
Nostro account reconciliation testing verifies agreement between a bank's internal records and data from its correspondent-held account. It tests matching, balance calculation, exception handling and the effects of operational conditions such as duplicate or delayed inputs.
Read definitionNotional cash pooling calculation testing
Notional cash pooling calculation testing verifies that a system applies the pool agreement correctly to account balances and calculates interest and allocations accurately. The entry covers test inputs, independent expected results, boundary scenarios and common defects.
Read definition
O
Omnichannel banking testing
Omnichannel banking testing checks that customer journeys and transaction state remain consistent as customers move between channels. It also verifies the connected services, permissions and recovery behaviour behind those journeys.
Read definitionOnline banking testing
Online banking testing verifies customer-facing journeys and the systems behind them, including payment processing, access controls and data handling. Reliable results depend on controlled test data, representative dependencies and checks that compare customer-visible status with back-end records.
Read definitionOpen banking API testing
Open banking API testing checks that data-sharing and payment journeys work under the relevant API rules, with access limited to valid customer consent. It combines functional, security and integration checks across the bank and third-party provider.
Read definitionOpen banking consent lifecycle testing
Open banking consent lifecycle testing verifies that consent state, scope and access behave consistently across customer journeys and APIs. The entry outlines transition, security and propagation checks, with a worked revocation example.
Read definitionOpen banking consent revocation testing
Open banking consent revocation testing checks that withdrawal changes consent state and blocks subsequent access through the relevant APIs and credentials. The entry explains environment setup, lifecycle cases, a practical test sequence and evidence to retain.
Read definitionOpen finance integration testing
Open finance integration testing verifies that financial services exchange and process data or instructions correctly across external provider boundaries. It covers API contracts, consent, data mapping and failure handling, with expected behaviour defined by the relevant integration arrangement.
Read definitionOracle FLEXCUBE testing
Oracle FLEXCUBE testing checks that a bank's configured core banking implementation behaves correctly across transactions, accounting and connected systems. Scope and expected results depend on the implementation, configuration and requirements.
Read definitionOrder management system testing in banking
Order management system testing in banking checks order lifecycle behaviour, controls and data consistency across connected systems. The entry outlines test setup, integration and failure scenarios, with a practical limit-order example.
Read definitionOverdraft interest calculation testing
Overdraft interest calculation testing checks that calculated and posted interest follows the account's approved product rules. It covers balance and date inputs, rates, day-count conventions, rounding and downstream records.
Read definition
P
Pacs.008 message testing
pacs.008 message testing validates both the ISO 20022 message and the payment processing rules for its target interface. Effective tests verify rejection behaviour and trace accepted instructions through routing, posting and reconciliation.
Read definitionPacs.009 message testing
pacs.009 message testing needs separate checks for XML structure, route-specific business rules and downstream settlement behaviour. A cover-transfer test should verify message acceptance, routing, reconciliation and rejection handling.
Read definitionPain.001 message testing
pain.001 message testing checks XML structure, the correct ISO 20022 schema and the receiving bank's implementation rules. It also verifies that accepted and rejected instructions produce the expected processing outcomes.
Read definitionPain.002 message testing
pain.002 message testing checks XML structure and profile rules, then verifies that each reported status is correctly correlated with the original payment. Effective tests also confirm how the receiving application handles pending, partial and rejected outcomes.
Read definitionPayment cut-off time testing
Payment cut-off time testing verifies how payments submitted around a deadline are dated and routed for processing. Reliable tests define the governing timestamp, boundary rule, time zone and calendar, then check the resulting payment records and downstream handling.
Read definitionPayment holiday calendar testing
Payment holiday calendar testing checks that payment systems select the correct calendar and calculate processing dates according to configured closure, cut-off and time-zone rules. It should cover boundary dates, calendar updates and downstream payment outcomes.
Read definitionPayment idempotency testing
Payment idempotency testing verifies that retries identified by the same key do not create duplicate payment effects. It also checks the API contract, key lifecycle and consistency across downstream systems.
Read definitionPayment initiation service testing
Payment initiation service testing verifies the customer journey and system interactions that submit a bank payment instruction and report its status. It checks data integrity, authentication hand-offs, errors, retries and asynchronous updates across connected services.
Read definitionPayment message data truncation testing
Payment message data truncation testing checks that field values remain intact across payment message creation, mapping, transport and processing. The entry explains how to select boundary cases, verify outcomes at system interfaces and distinguish silent data loss from expected validation.
Read definitionPayment purpose code validation testing
Payment purpose code validation testing verifies that a payment's purpose code meets the applicable rules and remains correct as the payment moves through systems. Tests should cover rule conditions, rejection behaviour, reference-data versions and outbound message mapping.
Read definitionPayment recall workflow testing
Payment recall workflow testing checks the handling of requests to stop or recover payments after initiation. It verifies outcomes across systems while accounting for the fact that recovery depends on payment status and the receiving institution.
Read definitionPayment retry testing
Payment retry testing verifies that payment operations follow their configured retry policy and reach a correct final state after failures. It also checks ambiguous outcomes, where a processor may have completed a payment without returning confirmation.
Read definitionPayment return and rejection testing
Payment return and rejection testing verifies how a payment system handles instructions refused during processing and payments returned after dispatch. Tests should confirm status, accounting, notifications and reconciliation behaviour against the relevant rail and bank rules.
Read definitionPayment timeout handling testing
Payment timeout testing checks that a delayed or missing response does not cause duplicate payments or incorrect status. It verifies idempotent retries, eventual state resolution and consistency between payment records and ledger entries.
Read definitionPayroll payment testing
Payroll payment testing verifies the transfer of approved pay amounts from payroll systems to payment providers and checks the resulting statuses and reconciliation. It covers issues such as incorrect payee details, rejected or duplicated instructions, partial batch failures and test-data safety.
Read definitionPega banking workflow testing
Pega banking workflow testing verifies that configured banking cases follow the required decisions, assignments and outcomes. Effective tests check case behaviour alongside downstream records and integration results.
Read definitionPeriodic KYC review testing
Periodic KYC review testing verifies that configured review schedules create the right cases and that evidence, decisions, approvals and audit records flow correctly. It also checks exception handling and dependencies without treating a successful software test as proof of regulatory compliance.
Read definitionPersonal loan approval testing
Personal loan approval testing verifies that loan application data and decision rules produce the expected outcome and that the result is recorded consistently. It also checks dependencies, boundary conditions and failure paths.
Read definitionPhysical cash concentration testing
Physical cash concentration testing validates software workflows and records for consolidating physical cash from dispersed locations. It checks movement data, interfaces, accounting treatment and reconciliation outcomes against configured business rules.
Read definitionPoint-of-sale payment integration testing
Point-of-sale payment integration testing verifies transaction data and outcomes as they pass between POS software, payment terminals and connected processor services. It also checks failure handling, status consistency and safe recovery from uncertain responses.
Read definitionPolitically exposed person screening testing
Politically exposed person screening testing validates configured identity matching and the processes that handle potential PEP alerts. It should cover near matches, missed matches, workflow outcomes, integration failures and traceable test evidence.
Read definitionPortfolio rebalancing workflow testing
Portfolio rebalancing workflow testing validates policy calculations and the complete path from portfolio data to approved orders and reconciled positions. The entry explains test data controls, API and state checks, failure handling and a worked allocation example.
Read definitionPrepaid card testing
Prepaid card testing validates card funding and transaction behaviour against programme rules, including available balance changes and lifecycle restrictions. It also checks that processor, payment and ledger records stay consistent through declines, reversals and settlement.
Read definitionPrivate bank advisor assistant access testing
Private bank advisor assistant access testing checks that each assistant's client data access and permitted actions match the bank's role and delegation rules. It covers positive and negative paths across interfaces, APIs and connected systems.
Read definitionPrivate bank AI-generated portfolio summary testing
Private bank AI-generated portfolio summary testing checks that generated text is accurate, supported by approved data and appropriate to its intended use. The entry sets out test inputs, assertions, failure cases and a practical example.
Read definitionPrivate bank client reporting accuracy testing
Private bank client reporting accuracy testing verifies report fields and calculations against source data and documented rules for the reporting date. Effective tests reconcile data across systems, exercise calculation boundaries and preserve evidence that supports repeatable investigation.
Read definitionPrivate bank client suitability update testing
Private bank client suitability update testing verifies that profile changes are validated, assessed and propagated according to approved policy. It also checks workflow controls, failure recovery, audit evidence and regression risks across connected systems.
Read definitionPrivate bank investment mandate restriction testing
Private bank investment mandate restriction testing checks that client-specific investment constraints are configured and enforced as intended. Testing covers rule interpretation, trade decisions, exceptions and resulting portfolio records.
Read definitionPrivate bank multi-currency portfolio valuation testing
Multi-currency portfolio valuation testing validates the prices, FX inputs, calculation rules and reporting outputs used to value a private bank portfolio. The entry gives a worked conversion example and practical checks for stale data, rate conventions, rounding and cross-system consistency.
Read definitionPrivate bank portfolio fee tier testing
Private bank portfolio fee tier testing checks that configured pricing rules use the correct eligible assets, schedule and valuation date. It combines boundary tests with independent fee calculations and verification of downstream client and accounting outputs.
Read definitionPrivate banking portal testing
Private banking portal testing validates client journeys, financial data, integrations and permissions across the web experience. It also checks security, accessibility and failure handling using controlled test data.
Read definition
R
RAG testing in banking
RAG testing in banking should evaluate ingestion, retrieval, generation and access controls as connected parts of one system. Test with controlled banking data, verify evidence and citations, and rerun regression cases when sources or model components change.
Read definitionReal-time account balance testing
Real-time account balance testing verifies that balance values reflect transactions within a defined freshness limit. Tests should account for balance type, asynchronous updates and consistency across interfaces.
Read definitionReal-time payment fraud control testing
Real-time payment fraud control testing verifies risk decisions, response times, fallback behaviour and the payment actions that follow. It uses controlled scenarios to check both fraud outcomes and end-to-end enforcement.
Read definitionReceivables finance platform testing
Receivables finance platform testing checks invoice processing, funding rules, workflow controls, financial data and connected systems. It verifies that statuses, balances and audit evidence remain consistent through funding and settlement.
Read definitionRecurring deposit testing
Recurring deposit testing verifies the account’s scheduled contributions and lifecycle against product rules, including interest and maturity. It also checks that balances and accounting records remain consistent when processing succeeds, fails or is retried.
Read definitionRecurring payment testing
Recurring payment testing checks scheduled charges and the related billing lifecycle across payment and connected systems. It verifies amounts, timing, state changes, failure handling and protection against duplicate charges.
Read definitionRegression testing in banking
Regression testing in banking checks that changes have not disrupted existing banking behaviour across products, channels and dependent systems. Its scope should reflect change impact, with repeatable test data and assertions that verify business outcomes.
Read definitionRequirements-based risk assessment in banking
Requirements-based risk assessment evaluates the potential impact and likelihood of failure for banking software requirements. Teams use the results to prioritise tests, trace risks to evidence and revisit coverage when requirements or dependencies change.
Read definitionResidual software risk in banking
Residual software risk is the software-related exposure that remains after a bank applies controls and testing. Its assessment should be based on release-specific evidence, explicit assumptions and an authorised decision.
Read definitionRetail bank account package migration testing
Retail bank account package migration testing verifies that accounts move to the intended package while retaining required data and applying new rules from the correct date. It also checks exceptions, connected systems and financial reconciliation.
Read definitionRetail bank AI assistant account access testing
Retail bank AI assistant account access testing checks that identity and entitlement controls apply to every request, including retrieval, tool calls and conversation state. Tests should verify denied access at both the service boundary and in the assistant's final response.
Read definitionRetail bank customer lifecycle testing
Retail bank customer lifecycle testing verifies that customer journeys and controls work consistently across banking states, channels and connected applications. It covers normal transitions, exceptions, data consistency and recovery across the customer relationship.
Read definitionRetail bank deceased customer workflow testing
Retail bank deceased customer workflow testing verifies the journey from notification through review, account actions and resolution against the bank’s approved rules. The entry covers test data, permissions, integration failures, duplicate handling and outcome checks.
Read definitionRetail bank minor account permission testing
Minor account permission testing checks that account access and actions match documented age, relationship and role rules across channels and services. Effective tests verify allowed and denied requests, boundary conditions, permission changes and resulting account state.
Read definitionRetail bank overdraft limit change testing
Retail bank overdraft limit change testing checks that authorised changes take effect at the right time and drive consistent transaction decisions. The entry covers boundary scenarios, existing debit balances, connected systems and a worked example.
Read definitionRetail bank power of attorney workflow testing
Retail bank power of attorney workflow testing verifies that recorded authority, account access and permitted actions remain aligned throughout review, activation and later changes. Effective coverage includes negative authorisation checks, audit evidence and updates across dependent systems.
Read definitionRetail bank recurring payment amendment testing
Retail bank recurring payment amendment testing verifies that authorised changes affect the correct future payments and stay consistent across channels and payment systems. Coverage should reflect the payment type, processing state and product-specific timing rules.
Read definitionRetail bank risk-scored test case generation
Risk-scored test case generation ranks banking tests using documented assessments of impact, failure likelihood and control exposure. The entry explains how to generate traceable cases and validate a payment-limit example.
Read definitionRetail bank savings rate change testing
Retail bank savings rate change testing checks that product rules, effective dates and interest calculations produce the right customer and ledger outcomes. It also verifies downstream displays, communications and regression behaviour.
Read definitionRevolving credit facility testing
Revolving credit facility testing validates facility rules across borrowing, repayment and lifecycle events. It checks calculated availability, financial postings and consistent outcomes across connected systems.
Read definitionRisk coverage vs test coverage in banking
Risk coverage shows whether tests address identified banking risks, while test coverage shows which parts of a defined scope have been exercised. The entry explains how to measure both and interpret their gaps using payment retry testing.
Read definitionRisk scoring for banking test cases
Risk scoring ranks banking test cases by the likelihood and impact of their target failures. A clear scoring rubric, traceable rationale and separate coverage review help teams use scores for prioritisation without treating them as release evidence.
Read definitionRisk-based regression testing in banking
Risk-based regression testing in banking prioritises tests according to failure likelihood, business impact and change dependencies. A defensible approach links changes to risks and tests, uses controlled data, and records residual risk for release decisions.
Read definitionRisk-based test case design for banks
Risk-based test case design for banks prioritises test depth according to failure likelihood and impact while retaining required coverage for applicable controls and obligations. The entry explains assessment, case design, evidence and a duplicate-payment example.
Read definitionRisk-based test prioritisation for banks
Risk-based test prioritisation orders banking tests according to potential harm, likelihood, exposure and the effectiveness of existing controls. A documented mapping from failure scenarios to test evidence helps teams adjust priorities as changes and results emerge.
Read definitionRisk-based testing exit criteria for banks
Risk-based testing exit criteria turn a bank's change-specific risks into evidence-based release gates. They should address critical scenarios, financial integrity, defects, controls, operational readiness and authorised risk acceptance.
Read definitionRisk-based testing for agricultural banks
Risk-based testing helps agricultural banks direct test effort towards software failures with the greatest customer, financial or operational impact. The entry explains how to assess risks, select seasonal lending tests and verify results across connected systems.
Read definitionRisk-based testing for building societies
Risk-based testing for building societies prioritises test effort according to the likelihood and impact of software failures across member services, financial processing and operational controls. A documented assessment links failure scenarios to test coverage, evidence and any residual risk accepted at release.
Read definitionRisk-based testing for central banks
Risk-based testing for central banks directs test effort towards failures with the greatest potential impact on monetary operations, settlement and public confidence. The entry explains how to assess risk, select tests and document release decisions using an RTGS change example.
Read definitionRisk-based testing for challenger banks
Risk-based testing for challenger banks directs testing depth and effort towards software failures with the greatest potential customer, financial, operational or compliance impact. The entry explains how to assess risks across digital services and partners, and shows how to test a payment retry change.
Read definitionRisk-based testing for commercial banks
Risk-based testing for commercial banks directs test effort towards failures with the greatest potential impact while retaining required control coverage. Effective plans connect assessed risks to test evidence and record dependencies, limitations and residual exposure.
Read definitionRisk-based testing for community banks
Risk-based testing helps community banks focus testing on failure scenarios with the greatest potential effect on customers, funds, controls and service continuity. The entry explains how to assess risks, select tests, handle vendor dependencies and document evidence for release decisions.
Read definitionRisk-based testing for cooperative banks
Risk-based testing for cooperative banks directs test effort towards failures with the greatest likelihood and impact on services, records and members. The entry explains how to assess risks, translate them into test scope and maintain auditable evidence.
Read definitionRisk-based testing for corporate banks
Risk-based testing helps corporate bank teams direct test effort towards failures with the greatest potential impact on clients, transactions and controls. Its value depends on sound risk assessment, representative test conditions and clear records of coverage and residual risk.
Read definitionRisk-based testing for correspondent banks
Risk-based testing for correspondent banks directs test effort towards payment flows and controls where failure could have the greatest consequences. The entry explains how to scope risks, test control outcomes and verify dependencies across correspondent relationships.
Read definitionRisk-based testing for credit unions
Risk-based testing helps credit union teams direct effort towards failures that could harm members, financial records, services or compliance obligations. A documented assessment links those risks to test scenarios, evidence and release decisions.
Read definitionRisk-based testing for custodian banks
Risk-based testing for custodian banks prioritises software tests by the possible impact and likelihood of failures across custody services. The entry explains how to assess risk, select scenarios and use evidence to support release decisions.
Read definitionRisk-based testing for development banks
Risk-based testing for development banks ranks software risks by their likelihood and potential effects on financing operations and development outcomes. The entry explains how to map risks to tests, prioritise connected workflows and record residual exposure.
Read definitionRisk-based testing for digital-only banks
Risk-based testing focuses effort on digital banking failures with the greatest potential customer, financial, security or operational impact. A repeatable assessment links those risks to targeted tests, controls and release evidence.
Read definitionRisk-based testing for export-import banks
Risk-based testing directs limited test effort towards export-import bank software failures with the greatest likelihood and business impact. It connects risk assessment to test selection, evidence and release decisions.
Read definitionRisk-based testing for investment banks
Risk-based testing for investment banks uses assessed failure likelihood and consequence to focus test depth and execution order on high-impact changes. Teams still need to meet mandatory control and compliance coverage and record residual risks.
Read definitionRisk-based testing for microfinance banks
Risk-based testing helps microfinance banks focus test effort on failures that could affect borrowers, collections, financial records or compliance. The entry explains how to score and trace risks, select workflow tests and assess evidence before release.
Read definitionRisk-based testing for mortgage banks
Risk-based testing helps mortgage banks focus test effort on failures that could affect lending decisions, customer outcomes, servicing or controls. The entry explains how to assess risks, design targeted tests and preserve release evidence.
Read definitionRisk-based testing for neobanks
Risk-based testing helps neobank teams allocate test effort according to the likelihood and impact of failures across customer journeys and system dependencies. The entry explains how to assess risks, select tests and review release evidence.
Read definitionRisk-based testing for private banks
Risk-based testing helps private banks focus test effort on failure scenarios with the greatest potential impact on clients, finances, operations or compliance. The entry explains how to assess risks, design a payment example and retain evidence that supports control claims.
Read definitionRisk-based testing for retail banks
Risk-based testing helps retail banks direct test effort towards changes with the greatest potential customer, financial or control impact. The entry explains how to assess risk, map it to test scope and verify outcomes using a transfer-limit change.
Read definitionRisk-based testing for savings banks
Risk-based testing for savings banks aligns test effort with the likelihood and impact of software failure. The entry explains how to assess risks, select coverage and verify a tiered interest change through ledger and customer outputs.
Read definitionRisk-based testing for traditional banks
Risk-based testing directs effort towards bank changes and failure modes with the greatest potential customer, financial, operational or regulatory impact. Teams should connect documented risk assessments to test objectives, evidence and decisions about residual risk.
Read definitionRisk-based testing for transaction banks
Risk-based testing directs effort towards transaction failures with the greatest potential impact and likelihood. The entry explains how to assess risks, select tests, manage execution dependencies and document remaining exposure.
Read definitionRisk-based testing for universal banks
Risk-based testing directs test effort towards changes and workflows with the greatest assessed failure impact and likelihood. Universal banks need to include shared services, cross-division dependencies, mandatory controls and residual risk in that assessment.
Read definitionRisk-based testing for wholesale banks
Risk-based testing for wholesale banks prioritises scenarios by failure likelihood and business impact across connected trading, treasury, payment and control workflows. The entry explains how to assess risk, select tests, capture evidence and review residual exposure.
Read definitionRisk-based testing in banking
Risk-based testing directs banking test effort towards failures with the greatest likelihood and impact. The entry explains how to assess risks, prioritise payment scenarios and verify coverage while retaining regulatory obligations.
Read definitionRisk-scored test case generation for banks
Risk-scored test case generation links bank requirements and failure risks to specific, verifiable test scenarios. Agreed scoring criteria help teams prioritise execution while retaining mandatory coverage and traceability.
Read definitionRTP network payment testing
RTP network payment testing verifies that bank systems correctly initiate, receive and process payments through the US RTP network. It checks network interactions alongside posting, status, recovery and customer-facing outcomes.
Read definition
S
Sanctions screening integration testing
Sanctions screening integration testing verifies that applications send screening data correctly, handle service responses as configured and update downstream workflows safely. Reliable tests control service responses, test data and configuration, then check both interface behaviour and resulting application state.
Read definitionSAP GUI testing in banking
SAP GUI testing in banking verifies staff workflows through the desktop client and checks that the resulting business records are correct. Reliable coverage depends on controlled environments, role-based scenarios and independent outcome verification.
Read definitionSavings account lifecycle testing
Savings account lifecycle testing validates account state changes and financial behaviour from opening to closure. It follows transactions and data across channels and banking systems, using product rules as the basis for expected results.
Read definitionSavings bank deposit renewal testing
Savings bank deposit renewal testing checks that maturity instructions, product rules and interest calculations produce the intended renewed deposit. It also verifies postings, account state, downstream consistency and safe recovery from processing failures.
Read definitionSavings bank tax certificate generation testing
Savings bank tax certificate generation testing checks that approved tax rules and banking data produce accurate, correctly assigned certificates. It also validates document output, error handling and evidence across connected systems.
Read definitionSavings bank tiered interest regression testing
Savings bank tiered interest regression tests verify calculations against approved product rules, controlled account data and independent expected results. They should cover tier boundaries, dates, rounding and downstream posting.
Read definitionScriptless test automation for banking
Scriptless test automation lets teams build banking tests through visual workflows or configuration while an execution engine carries them out. Reliable results depend on meaningful business assertions, controlled test data and environments, and evidence that covers downstream processing.
Read definitionSecurities position reconciliation testing
Securities position reconciliation testing checks whether systems agree on the quantity of each security held in an account at a specified date. It validates matching, discrepancy detection and the handling of unsettled activity and other position changes.
Read definitionSecurities settlement workflow testing
Securities settlement workflow testing checks that trade instructions progress through settlement systems and produce the expected cash and securities outcomes. It also verifies failure handling, cross-system consistency and reconciliation against the applicable market rules.
Read definitionSelf-healing test automation for banking
Self-healing test automation can recover from some locator changes in banking interfaces, provided the intended control can be identified reliably. It must preserve strict business assertions, safe failure behaviour and reviewable evidence.
Read definitionSEPA credit transfer testing
SEPA credit transfer testing validates payment instructions and their processing across bank channels, interfaces and ledger services. Reliable tests follow the payment through its status lifecycle and verify data consistency, duplicate handling and account entries.
Read definitionSEPA direct debit testing
SEPA direct debit testing validates mandate and collection processing across payment systems and bank interfaces. It also checks asynchronous outcomes, duplicate prevention, returns, reconciliation and scheme-specific behaviour.
Read definitionSEPA instant credit transfer testing
SEPA instant credit transfer testing verifies the payment journey against applicable SCT Inst rules, including its timing window and 24/7 processing. It must also establish that failures, retries and uncertain outcomes do not cause incorrect statuses or duplicate postings.
Read definitionSME lending application testing
SME lending application testing verifies that business loan applications, credit decisions and related integrations follow documented rules and controls. It checks workflow outcomes and supporting records across the systems involved.
Read definitionSmoke testing for banking applications
Smoke testing checks whether a banking build and its essential services are usable for further testing. The entry explains safe scope, environment and data preconditions, a transfer example, and how to interpret failures.
Read definitionSpecialist bank risk-scored test case generation
Risk-scored test case generation connects specialist-bank failure scenarios to specific, traceable tests and helps teams prioritise their design and execution. Scores need agreed criteria, evidence-based ratings and review when product rules, controls or dependencies change.
Read definitionStanding order testing
Standing order testing checks the instruction lifecycle and whether scheduled payments produce the correct processing, account and customer-facing outcomes. Reliable tests use controlled data and the bank's configured rules for dates, failed payments and changes.
Read definitionState transition testing for banking workflows
State transition testing checks that banking workflows accept valid events, block invalid ones and produce the expected state and financial side effects. A reviewed model helps testers cover both individual transitions and risky event sequences.
Read definitionStrong customer authentication testing
Strong customer authentication testing validates the required independent authentication elements and the payment flow that follows. It checks challenge and exemption decisions, failure handling, transaction state and evidence across connected services.
Read definitionStructured payment address validation testing
Structured payment address validation testing checks address fields against the applicable interface contract and verifies that accepted data survives payment processing intact. The entry covers test data, boundary cases, API assertions and downstream failure handling.
Read definitionSupply chain finance platform testing
Supply chain finance platform testing covers the end-to-end handling of invoices, financing elections, payments and settlement across participating organisations and connected systems. Tests should verify product-specific calculations, workflow controls, duplicate prevention, auditability and reconciliation.
Read definitionSuspicious activity report workflow testing
Suspicious activity report workflow testing validates that configured investigation, decision, approval and reporting steps work correctly across connected systems. Use synthetic data and controlled reporting endpoints to verify access controls, audit evidence and failure handling.
Read definitionSWIFT CBPR+ testing
SWIFT CBPR+ testing verifies that cross-border payment messages follow the applicable ISO 20022 usage guidelines and that connected systems handle them as expected. Effective coverage includes valid and invalid messages, payment flow outcomes and evidence from the systems involved.
Read definitionSWIFT MT to MX translation testing
SWIFT MT to MX translation testing verifies that converted payment messages preserve business meaning and satisfy the relevant ISO 20022 and market-practice rules. Reliable tests use fixed message profiles, independent expected results and explicit checks for data loss and error handling.
Read definitionSWIFT payment testing
SWIFT payment testing validates payment messages and the processing steps around them, including routing, responses and downstream records. A sound test verifies business outcomes across connected systems as well as message-level correctness.
Read definitionSWIFT UETR validation testing
SWIFT UETR validation testing verifies UUID version 4 format and checks that the reference remains correctly associated with a payment across relevant messages and systems. Tests should cover malformed input, field mapping, processing outcomes and controlled test data.
Read definitionSyndicated loan processing testing
Syndicated loan processing testing verifies that facility terms and loan events are applied consistently across the agent, lender and connected systems. It combines functional, integration and end-to-end checks with reconciliation of allocations and downstream records.
Read definitionSynthetic test data for banking
Synthetic test data for banking provides artificial customer, account and transaction records for testing banking systems without depending on identifiable customer records. Its value rests on realistic relationships, defined business rules and checks for privacy, integrity and safe routing.
Read definitionSystem testing in banking
System testing checks an assembled banking application or configured system against its requirements using realistic scenarios and controlled dependencies. The entry explains scope, evidence and a transfer example that includes retry handling.
Read definition
T
Temenos Infinity testing
Temenos Infinity testing validates a bank's configured digital banking journeys and their connected services. The entry explains how to test business rules, integrations, cross-channel consistency, regression and transfer outcomes.
Read definitionTemenos Transact testing
Temenos Transact testing validates a bank’s configured core banking workflows, accounting outcomes and system integrations. Effective checks use controlled data and verify transaction results across balances, postings and connected systems.
Read definitionTerm deposit maturity testing
Term deposit maturity testing verifies that a deposit matures on the correct date and follows its configured financial and operational rules. It also checks downstream records and safe recovery from failed or repeated processing.
Read definitionThought Machine Vault integration testing
Thought Machine Vault integration testing verifies interface contracts and banking outcomes across Vault and connected systems. The entry explains environment setup, transaction assertions, retry behaviour and failure diagnosis.
Read definitionThreat-led penetration testing for banks
Threat-led penetration testing for banks simulates relevant attacks against critical functions using threat intelligence and agreed safety controls. Its value depends on realistic scope, reliable evidence and clear handling of limitations and remediation.
Read definitionTIBER-EU testing
TIBER-EU testing is a threat-intelligence-led red team exercise that tests an entity's ability to protect critical functions and detect and respond to realistic cyber attacks. It uses agreed scope, controls and a structured review to turn exercise findings into remediation.
Read definitionTiered savings interest testing
Tiered savings interest testing checks that balance portions receive the correct rates under the account's accrual and posting rules. Reliable tests use boundary balances and an independent expected-value calculation.
Read definitionTrade allocation testing
Trade allocation testing verifies how executed trades are assigned to accounts or portfolios and whether those allocations reconcile with fills. It also checks account rules, exception handling, audit records and downstream consistency.
Read definitionTrade cancellation and amendment testing
Trade cancellation and amendment testing checks that permitted changes produce the correct trade state, audit history and downstream effects. It also covers rejected requests, retries, asynchronous processing and version conflicts.
Read definitionTrade confirmation testing
Trade confirmation testing verifies confirmation data and lifecycle handling across trading systems. It checks accurate matching, exception states and safe downstream updates.
Read definitionTrade execution workflow testing
Trade execution workflow testing checks that orders pass through configured controls and connected systems correctly, including execution reports and trade capture. Its tests need controlled data and explicit assertions for state changes, quantities, duplicates and failure paths.
Read definitionTrade finance document discrepancy testing
Trade finance document discrepancy testing verifies document-to-transaction comparisons and the workflow that follows a finding. It covers extraction, configured rules, audit records and cases where a valid presentation must pass without a false discrepancy.
Read definitionTrade finance limit utilisation testing
Trade finance limit utilisation testing verifies exposure calculations and limit decisions throughout a transaction's lifecycle. It also checks that amendments, cancellations, retries and concurrent requests leave utilisation and available capacity in the expected state.
Read definitionTrade finance sanctions screening integration testing
Trade finance sanctions screening integration testing checks that transaction and party data reach the screening service and that responses drive the intended workflow. It should cover matching outcomes, failure handling, retries, duplicate events and traceability.
Read definitionTrade finance system testing
Trade finance system testing checks product workflows and the correctness of transaction data across connected banking services. Effective verification includes business states, documents, facility exposure, settlement, accounting and recovery behaviour.
Read definitionTrading collateral substitution testing
Trading collateral substitution testing verifies that a replacement asset meets configured collateral rules and that the substitution updates margin, settlement and related records correctly. It also checks failure paths, including rejection, insufficient value and settlement errors.
Read definitionTrading platform testing
Trading platform testing verifies order lifecycles, market data, positions, security and connected services under expected and adverse conditions. The entry explains test environments, common failure modes and an example limit-order workflow.
Read definitionTraditional bank account switching regression testing
Traditional bank account switching regression testing checks that system changes preserve the bank's documented switching process across channels and connected services. Effective coverage verifies account and payment state, duplicate handling, reconciliation and customer communications.
Read definitionTraditional bank branch teller application testing
Traditional bank branch teller application testing checks branch transactions from the teller screen through core banking and downstream records. It combines functional, transaction and integration testing with access-control and cash-control checks.
Read definitionTraditional bank branch to mobile journey testing
Traditional bank branch to mobile journey testing verifies that customer tasks, data and workflow status remain correct when work moves from branch systems to a mobile banking app. It combines cross-channel checks with end-to-end validation of the underlying business process.
Read definitionTraditional bank business-critical workflow mapping
Business-critical workflow mapping gives bank teams a testable view of process steps, system dependencies, controls and exception paths. The entry explains how to scope a workflow and derive evidence-based scenarios, including a corporate payment example.
Read definitionTraditional bank CRM replacement testing
Traditional bank CRM replacement testing verifies that customer information, staff workflows, integrations and access controls behave as intended during migration. The entry explains how to prepare data, test connected journeys and verify cutover and recovery.
Read definitionTraditional bank cross-channel fraud control testing
Traditional bank cross-channel fraud control testing verifies that fraud policies process related activity across channels and that decisions are enforced in the relevant systems. It depends on representative test data, reliable event context and evidence linking each decision to its outcome.
Read definitionTraditional bank customer data consolidation testing
Traditional bank customer data consolidation testing checks that records from separate systems are matched, transformed and combined according to approved rules. It also verifies relationships, reconciliation, exception handling and downstream access.
Read definitionTraditional bank digital identity integration testing
Traditional bank digital identity integration testing verifies that identity-provider data and decisions produce the correct bank-side workflow state. It covers interface contracts, asynchronous responses, security controls, error handling and downstream effects.
Read definitionTraditional bank end-of-day regression testing
Traditional bank end-of-day regression testing reruns selected business-date batch scenarios after a change to detect unintended effects on existing banking processes. Reliable results depend on controlled data, environment and configuration, plus checks of both job execution and financial outputs.
Read definitionTraditional bank legacy modernisation testing
Traditional bank legacy modernisation testing verifies changed platforms, migrated data and dependent banking workflows across source and target environments. It uses traceable test evidence, reconciliation and controlled regression to inform release and cutover decisions.
Read definitionTraditional bank mainframe to API integration testing
Mainframe to API integration testing checks that API calls produce the correct mainframe outcomes and that responses accurately represent processing state. The entry explains test setup, transaction and failure scenarios, and how to verify results across synchronous and asynchronous flows.
Read definitionTraditional bank merger migration testing
Traditional bank merger migration testing checks that data moved between banks remains accurate, linked and usable in the target systems. It combines mapping validation, financial reconciliation, workflow checks and cutover verification.
Read definitionTraditional bank mortgage to core banking testing
Mortgage to core banking testing verifies that mortgage events produce accurate, traceable account and financial records in a bank's core system. Effective tests cover mappings, lifecycle events, reconciliation, retries and rejected or duplicate messages.
Read definitionTraditional bank payment hub testing
Traditional bank payment hub testing verifies payment processing rules and the connections that carry instructions through a bank's systems and external networks. It also checks recovery behaviour and reconciles outcomes across the hub, channels and accounting services.
Read definitionTraditional bank release risk prioritisation
Traditional bank release risk prioritisation links each change to affected workflows, potential harm, likelihood and available controls. The resulting assessment guides test scope and release gates while keeping residual-risk decisions with accountable owners.
Read definitionTraditional bank risk-scored test case generation
Risk-scored test case generation uses assessed failure risks to shape banking test scenarios and cases. Its value depends on traceable scoring, relevant evidence and assertions that verify outcomes across affected systems.
Read definitionTraditional bank test environment dependency management
Traditional bank test environment dependency management tracks the systems, data, configuration and operational conditions required for reliable tests. A dependency map, controlled baselines and readiness checks help teams reproduce results and diagnose environmental failures.
Read definitionTransaction bank client reporting testing
Transaction banking client reporting testing validates report content against authoritative banking data and checks that timing, presentation, permissions and delivery follow agreed rules. Effective tests trace fields to their sources and reconcile both individual records and aggregate totals.
Read definitionTransaction bank high-volume reconciliation testing
High-volume bank transaction reconciliation testing verifies that large transaction populations reconcile accurately across banking systems within agreed processing windows. It checks record-level outcomes and financial control totals alongside throughput, backlog and recovery behaviour.
Read definitionTransaction bank intraday liquidity alert testing
Intraday liquidity alert testing checks that configured rules act on accurate, timely balance and cash-flow data and produce the expected alert lifecycle. The entry covers test data, boundary cases, stale feeds, delivery failures and a worked threshold example.
Read definitionTransaction bank payment routing failover testing
Bank payment routing failover testing verifies that payments use an approved alternative route when the primary route fails. It also checks ambiguous outcomes, duplicate prevention and downstream consistency.
Read definitionTreasury management system testing
Treasury management system testing checks that configured treasury workflows, calculations, controls and integrations produce accurate and traceable outcomes. It follows transactions across the TMS and connected bank, ERP and ledger services.
Read definition
U
Ultimate beneficial owner verification testing
Ultimate beneficial owner verification testing validates how software identifies natural persons who ultimately own or control a business and processes their verification. Tests should cover configured rules, evidence handling, exceptions, integrations and auditable outcomes.
Read definitionUniversal bank corporate and retail payment integration testing
Bank payment integration testing checks that retail and corporate payment instructions move accurately across connected banking systems and produce the expected statuses and account effects. It includes channel-specific rules, shared processing, error handling and reconciliation.
Read definitionUniversal bank cross-division integration testing
Universal bank cross-division integration testing verifies that systems in separate banking divisions exchange data and complete shared workflows correctly. It relies on coordinated environments, representative test data and assertions across every affected system.
Read definitionUniversal bank retail and wealth data consistency testing
Universal bank retail and wealth data consistency testing verifies that linked customer, account and financial records follow agreed ownership, mapping and timing rules across systems. Tests should include normal journeys, asynchronous updates, duplicate events and recovery outcomes.
Read definitionUniversal bank shared service outage testing
Shared service outage testing checks whether bank workflows remain safe and recover correctly when a dependency fails. The entry explains how to prepare controlled scenarios, validate transaction handling and verify recovery across divisions.
Read definitionUser acceptance testing in banking
User acceptance testing in banking checks whether a release supports agreed business workflows and acceptance criteria in realistic conditions. Reliable UAT depends on representative scenarios, prepared users and data, a controlled environment, and evidence reviewed by the authorised business owner.
Read definition
V
Variable-rate loan repricing testing
Variable-rate loan repricing testing verifies that servicing systems apply rate-reset rules and calculate resulting interest and repayments correctly. Reliable tests use controlled rate inputs, representative loan terms and independent expected calculations.
Read definitionVerification of Payee testing
Verification of Payee testing verifies the name-to-account check and the payment application's handling of its response. It should cover customer choices, service failures and whether the checked details are the ones used in the resulting payment.
Read definitionVirtual bank account testing
Virtual bank account testing verifies that identifiers route and match payments as intended, with consistent records across processing, ledger and reconciliation systems. Useful coverage includes lifecycle changes, duplicate payments and invalid or unmatched transactions.
Read definitionVirtual card testing
Virtual card testing checks card creation, controls and transaction processing in a test environment. Reliable coverage depends on suitable test data, clear simulator boundaries and assertions across application and transaction records.
Read definitionVisual test automation for banking applications
Visual test automation compares captured banking application screens with approved baselines to detect presentation changes in important journeys. Reliable checks depend on controlled test conditions, careful handling of sensitive data and separate assertions for business outcomes.
Read definitionVostro account processing testing
Vostro account processing testing checks payment lifecycle behaviour and accounting outcomes for a correspondent bank's account held by another bank. The entry covers transaction scenarios, balance and statement validation, reconciliation and duplicate handling.
Read definition
W
Wealth management platform testing
Wealth management platform testing validates investment workflows and the accuracy, security and consistency of client and portfolio data. The entry outlines risk-led planning, integration checks and a worked order example.
Read definitionWholesale bank collateral movement testing
Wholesale bank collateral movement testing verifies that cash or securities transfers follow business rules and complete consistently across connected systems. It covers lifecycle states, controls, settlement outcomes, exceptions and reconciliation.
Read definitionWholesale bank counterparty limit utilisation testing
Wholesale bank counterparty limit utilisation testing checks that exposure is calculated and aggregated according to approved rules, and that limit warnings and breaches trigger the correct controls. It also verifies data flows, recalculation and evidence across connected systems.
Read definitionWholesale bank cross-border cash flow testing
Wholesale bank cross-border cash flow testing checks how international payments and treasury activity affect cash positions across currencies, accounts and settlement dates. It combines transaction-path checks with balance, liquidity and reconciliation verification.
Read definitionWholesale bank intraday liquidity dashboard testing
Wholesale bank intraday liquidity dashboard testing verifies that balances, flows, forecasts and alerts agree with defined source data and calculation rules. It also checks update behaviour, degraded states, usability and performance under representative conditions.
Read definitionWholesale bank money market deal testing
Wholesale bank money market deal testing verifies that short-term funding and investment transactions follow their agreed terms throughout processing. It checks calculations, lifecycle controls and consistency across connected systems.
Read definitionWholesale bank treasury settlement integration testing
Wholesale bank treasury settlement integration testing verifies the flow of settlement instructions and outcomes across treasury, payment, account and ledger systems. It also checks exception handling, retries, status mapping and reconciliation using controlled test data.
Read definitionWithholding tax calculation testing
Withholding tax calculation testing validates both the tax rule selected for a payment and the resulting amounts and records. Test cases should reflect approved jurisdiction-specific rules, effective dates, rounding policies and exception handling.
Read definition