Software testing in finance: calculations, resilience and DORA
In finance, a defect is counted in money: a badly rounded rate, a transaction posted twice, a limit ignored. And since January 2025, the resilience of information systems has been subject to explicit European obligations.
- Calculation is the first risk: rates, rounding, value dates, fees.
- A transaction must never go through twice: replay, double click, recovery after an error.
- DORA has applied since 17 January 2025: it requires a digital operational resilience testing programme.
- Permissions are tested like a feature: who can approve, who can only view.
Oussama Belakhdar, QA architect and founder of AutomationDataCamp, has worked on testing projects for financial software. Here is what we check first in a banking, payments or asset management application. Our clients remain anonymous.
What do the financial industry figures say?
Figures published by the organisations cited, not results of our own engagements.
Why is financial software hard to test?
- Calculation rules pile up and change: rate tables, interest rates, fees, tax, day count conventions (actual/360, 30/360), rounding rules set by a contract.
- Time is part of the data: value dates, month ends, bank holidays, daylight saving changes, overnight jobs that assume the previous day ended cleanly.
- The core system is often old and connected to dozens of flows: a format change on the payments side breaks a reconciliation on the accounting side.
- Security is not a separate layer: strong authentication, permissions and segregation of duties are business features in their own right.
Which scenarios should be tested first in a financial application?
- Calculations: interest, repayment schedules, fees and currency conversions, with boundary values and an explicit rounding rule.
- Idempotency: a replayed transaction, a double click or a restart after an outage never debits twice.
- Limits and controls: exceeding a limit, splitting a transaction to stay under a threshold, four-eyes approval.
- Strong authentication: enrolment, two factors, failure, expiry, change of device, link to the amount and the payee.
- Period ends: daily, monthly and yearly closing, catching up after an incident.
- Reconciliation: every movement shows up in the books, with no gap and no orphan entry.
PSD2, PCI DSS, DORA: the obligations that can be tested
PSD2 and strong customer authentication. Directive (EU) 2015/2366 on payment services requires strong customer authentication, detailed by Delegated Regulation (EU) 2018/389: at least two independent elements among knowledge (something the user knows), possession (something they have) and inherence (something they are). For a remote payment, the authentication code must be dynamically linked to the amount and the payee. Related test: changing the amount after authentication must invalidate the code.
PCI DSS for card data. The PCI Security Standards Council standard applies to any system that stores, processes or transmits cardholder data. The requirements added in version 4.0 have been mandatory since 31 March 2025. Two points always come up in testing: no real card numbers (PANs) in pre-production environments unless they are inside the protected scope, and masked numbers on screen.
DORA, Regulation (EU) 2022/2554. Applicable since 17 January 2025, it requires financial entities to run a digital operational resilience testing programme (Articles 24 and 25): vulnerability assessments, performance testing, end-to-end testing and penetration testing, among others. Entities designated by the authorities must also run threat-led penetration testing (TLPT) at least every three years (Article 26).
Verification of payee. Regulation (EU) 2024/886 on instant payments has required euro area providers, since 9 October 2025, to check that the payee's name matches the IBAN before a credit transfer. The three possible answers (match, close match, no match) and the message shown to the customer are tested like any other business rule.
An example test case: currencies that do not have two decimals. Many rounding defects come from a hidden assumption that every currency has cents. The ISO 4217 list, published by SIX as the official maintenance agency of the standard, gives each currency its number of minor units: 2 for the euro, 0 for the Japanese yen, 3 for the Kuwaiti and Bahraini dinars. A typical test converts the same amount into EUR, JPY and KWD, applies a percentage fee, then compares four values: the amount stored, the amount shown to the customer, the amount sent in the payment message and the accounting entry. All four must use the currency's own precision and the same rounding rule. A screen that correctly shows 1,250.375 KWD while the ledger stores 1,250.38 is the kind of gap that only reconciliation reveals.
Testing time: value dates, closings and overnight jobs
Many financial defects only appear on a specific date: 29 February, the last business day of the month, the switch to winter time, the first day of a new rate table. Waiting for those dates in acceptance is not an option. We make the clock controllable in test environments, then replay a full calendar: opening, the day's transactions, the overnight job, month-end closing.
Batch jobs are tested along three lines: the result (amounts, entries), recovery (an interrupted batch restarts with no duplicate and no gap) and duration (the batch fits in its window, even at year-end volume). That last point feeds directly into the performance testing DORA expects.
How do we organise testing for financial software?
- Start from the possible losses. Each feature is ranked by the amount at stake and its regulatory exposure; calculations, payments and permissions are covered first.
- Data-driven calculation tests. Rules are checked with example tables (input, expected result, rounding rule) at API level; Playwright covers customer and back-office journeys, k6 covers load, all running in your continuous integration.
- Test accounts and test cards. Test accounts, IBANs and card numbers supplied by providers, never customer data.
- AI, with a review. An assistant helps expand example tables and edge cases. Nothing is kept without a review against our 7-question checklist; our case study: from a PDF specification to Playwright tests shows the approach.
Where should you start?
A useful first step is to check that critical calculations and payment idempotency are covered by tests that run in every release.
A QA audit reviews your application: a written assessment, a test strategy adapted to your industry and a costed action plan, in 5 days, for €1,000 excl. VAT as a fixed fee. Delivered remotely, in English or French, for companies in the US, the UK, Canada, Australia, Europe, the Gulf and the Nordics. The first scoping session is free.
See the QA audit at €1,000 excl. VAT
Frequently asked questions about financial software testing
Does the DORA regulation concern software testing?
Yes. DORA, applicable since 17 January 2025, requires financial entities to run a documented and monitored digital operational resilience testing programme. Functional and performance tests of critical applications are part of it.
What should be automated first in financial software?
Calculations (with boundary values and rounding), transaction idempotency, limits and approvals, and end-of-period processing. These are the tests rerun on every release that protect the most.
Can real bank cards be used to test a payment?
No. PCI DSS excludes real card numbers from pre-production environments unless those environments are inside the protected scope. Payment providers supply test card numbers that simulate approval, decline and strong authentication.
How do you test PSD2 strong customer authentication?
By covering enrolment, each two-factor combination, failures and expiry, change of device and dynamic linking: a code obtained for a given amount and payee must no longer be valid if either of them changes.
How much does a QA audit cost at AutomationDataCamp?
The QA audit and diagnosis costs €1,000 excl. VAT as a fixed fee, over 5 days: a written assessment, a test strategy and a costed action plan. The first scoping session is free.
Other industries: Healthcare · E-invoicing · Blockchain · Logistics · E-commerce · Document management. All industries.
Page signed by Oussama Belakhdar, written with the help of AI. Regulatory references link to the official sources above; they are not legal advice.
Related articles

AI & ML for test automation
What AI concretely changes in test automation.
Read more : AI and ML for test automation
Integrating Automation into CI/CD
Jenkins, GitLab CI, GitHub Actions — practical examples.
Read more : Integrating Automation into CI/CD