Banking
Calculation remediation under regulatory attention
A credit-card interest error across customer balances, under active regulatory attention.
Illustrative · anonymised and reconstructed from real work
The scenario
Where the decision had to hold under scrutiny
A credit-card interest calculation was producing errors across customer balances, creating financial and regulatory risk. An issue of this kind draws regulatory attention and requires changes to the underlying approach. Illustrative work covers calculation accuracy, control design, and output validation, including assurance tooling and close work with compliance and legal teams. This leaves an evidenced record behind the calculation and supports remediation under scrutiny.
What the scenario turns up
The issues
Finding 01
A credit-card interest calculation was producing errors across customer balances, and an issue of this kind draws regulatory attention that demands changes to the underlying approach.
Finding 02
Under scrutiny, the correction itself had to be defensible — compliance and legal needed a record they could stand behind.
What the work does about each one
The response
Response 01
Corrects the calculation approach, designs controls around it, and builds assurance tooling to validate outputs, so accuracy is shown rather than asserted.
Response 02
Works with compliance and legal to confirm the corrected logic and lock an evidenced record of the fix, so the remediation can withstand challenge.
How the work is done
The same five steps, applied to this decision
Every piece of work runs the same path. For this one, the weight falls on Design, Build, Deploy & test — the steps where a decision of this kind is most often challenged.
Discovery
Map where the decision is made, who could challenge it, and the regime that binds it — before any logic is written.
Design
Set the logic out in the open so it can be read and questioned: the same inputs always give the same decision, and nothing is a black box.
Build
Build it with the checks in: coverage and oversight are confirmed before anything ships, and nothing unassessed is waved through as safe.
Deploy & test
Run it against real cases behind a human checkpoint, and keep a dated record of exactly what was decided and on what basis — one that cannot be edited afterwards.
Assure & hand over
Hand over the decision log and a plain-language write-up, so your team owns the record the moment someone says prove it.
What carries across
No automation covers this case yet
58 automations are running today, each built for a rule it names. None of them covers this case, and that is all that is claimed here. What carries across is the method: every one of them refuses to write a sentence its evidence will not support, which is the discipline this kind of work once ran by hand. Any of them can be shown to you running.
Related cases
The same standard, holding elsewhere
Discuss your situation
A decision like this can be made correctly, and shown to be correct, on the record
A short discussion is usually enough to locate where the risk sits — in the logic, the controls, the evidence, or a combination — and where it is made to hold.