Transaction Risk Calculator
The formula
What the transaction risk tells you
The 5×5 matrix the risk industry actually uses, for transaction risk: gross likelihood × impact, discounted by how well your controls actually work.
Calculation: gross = likelihood × impact (1–25); net = gross × (1 − controls). Enter your inputs and every substitution is shown below the result.
Reading the result
Scores rank attention; they do not price losses. Anything 15+ gets a treatment plan with a named owner.
Rules of thumb: Most organisations carry 3–5 reds; more usually means likelihood inflation, not danger.
Limitations and best practice
Control ratings drift optimistic — audit one control’s evidence and re-mark the rest against it.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Why discount by controls?
Do these scores compare across teams?
Source & methodology
ISO 31000-aligned qualitative risk matrices.
Transaction Risk: the number, the method and the caveats
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. Searchers land on a Transaction Risk page for three reasons — to plan, to compare options, and to check that somebody else’s arithmetic is honest. This tool serves all three, and everything after the calculator explains the model instead of hiding it.
The useful way to hold Transaction Risk is as a ratio with a story attached: gross = likelihood × impact (1–25); net = gross × (1 − controls) says how the parts combine, and the 3.7 / 25 figure above is simply that sentence written in numbers. Everything that follows unpacks one clause of the sentence at a time.
In plain terms, Transaction Risk answers the question "Net risk score?". The measurement matters because it converts a situation that feels complicated — several inputs pulling in different directions — into a single number you can act on. Within Finance & Banking, Currency & International is the context where this figure is quoted most often, and professionals treat it as a first-pass screen rather than a verdict.
What makes a calculation page trustworthy is that its copy is derived from its own arithmetic: here net risk score = 3.7 / 25, recomputed every time a field changes, and the sensitivity section ranks the inputs that move the result — Likelihood (1 = rare … 5 = almost certain) first, at ≈10.0 % of the headline for a ten-percent error either way in that input. Work down the page and by the end you could re-derive the result in a spreadsheet from memory.
Inside the Transaction Risk calculation: formula and every input
Here is the complete model this tool runs — gross = likelihood × impact (1–25); net = gross × (1 − controls) — with each input explained below. If a competitor’s page gives you a different answer from the same inputs, this is the text that settles which of you is right.
Likelihood (1 = rare … 5 = almost certain) (example value 2) is a plain measured quantity — the unit shown in the label is the unit the formula expects. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Impact (1 = negligible … 5 = severe) (example value 3) is a plain measured quantity — the unit shown in the label is the unit the formula expects. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Control effectiveness (0–100 %) (example value 39) is a measured number in the unit named by the label; the formula does not convert for you. Rates are the most mis-transcribed input on any page like this; copy it from the document rather than retyping from memory.
A fully worked Transaction Risk example
Rather than describe the calculation, here it is end to end — every substitution in order, starting from the inputs above. Starting figures: Likelihood (1 = rare … 5 = almost certain), Impact (1 = negligible … 5 = severe), Control effectiveness (0–100 %). Run to the end, the net risk score resolves to 3.7 / 25 — Green — acceptable residual on the bands this tool uses.
- Gross = 2 × 3 = 6
- Net = 6 × (1 − 39 %) = 3.7
Gross score — 6 / 25. This is the number experienced users quote when the headline alone would mislead.
Control credit — 2.3 pts. Read next to the headline, this is the figure that shows the shape of the trade-off.
Likelihood × impact band — Low-low. Read next to the headline, this is the figure that shows the shape of the trade-off.
Keep this worked example open while you enter your own figures: matching the shape of the substitution is the fastest way to spot a unit or convention mistake.
How far Transaction Risk can reasonably move
Read this table as the practical error bar on the headline figure. It answers the question people actually have after seeing a single number: how wrong could this be if the main input is off by ten or twenty percent?
| Likelihood (1 = rare … 5 = almost certain) setting | Net risk score |
|---|---|
| 80 % of the example value | 2.9 / 25 |
| 90 % of the example value | 3.3 / 25 |
| example inputs | 3.7 / 25 |
| 110 % of the example value | 4.0 / 25 |
| 120 % of the example value | 4.4 / 25 |
The corridor runs from 2.9 / 25 to 4.4 / 25 across that band — which is the range worth planning inside rather than the single 3.7 / 25 point estimate. Reproduce it in the form above by editing Likelihood (1 = rare … 5 = almost certain) alone; the substitution steps will follow your figures exactly.
What actually moves your Transaction Risk
Nobody should have to guess which input matters. The engine was re-run once per field below — ten percent up, ten percent down, everything else frozen — and the results ranked by how far they moved the net risk score. For Transaction Risk the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.
- Likelihood (1 = rare … 5 = almost certain): ten percent up gives 4.0 / 25, ten percent down gives 3.3 / 25 — ≈10.0 % of the net risk score either way
- Nudge Impact (1 = negligible … 5 = severe) by ±10 % and Transaction Risk lands between 3.3 / 25 and 4.0 / 25 (sensitivity ≈10.0 %)
- Nudge Control effectiveness by ±10 % and Transaction Risk lands between 3.4 / 25 and 3.9 / 25 (sensitivity ≈6.4 %)
Likelihood (1 = rare … 5 = almost certain) is the dominant lever here: ten percent either way moves the result by about 10.0 %, from 3.3 / 25 to 4.0 / 25. That is where a careless figure does the most damage, so check it against a source, and Impact (1 = negligible … 5 = severe) is effectively tied with it (≈10.0 % for the same nudge), so verify the pair together. Everything below that can stay approximate, which is a licence to stop chasing data that would not change the decision.
Is your Transaction Risk good — reading the result bands
The value above only becomes useful the moment you know what it is being measured against. The default case lands in the “Green — acceptable residual” band, and bands are deliberately wide because real situations overlap. Before treating the band as fact, note its width: ten percent either way on Likelihood (1 = rare … 5 = almost certain) already spans 3.3 / 25 to 4.0 / 25. The practical reading rules: compare against your own history before comparing against other people; treat band boundaries as zones, not walls — one point on the wrong side of a threshold rarely changes a real outcome; and when a companion output contradicts the headline, believe the pair.
Related measures answer related questions, and the distinctions matter: Transaction Risk is the quantity, Net risk score is this tool’s reading of it, and the decision that follows belongs to neither of them separately.
Common mistakes with Transaction Risk (and the fix)
Control ratings drift optimistic — audit one control’s evidence and re-mark the rest against it. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Stopping at the first plausible answer. If the result surprises you, the productive question is which input would have to be wrong for the surprise to disappear — then go check that input.
This model has its own particular trap: Likelihood (1 = rare … 5 = almost certain) carries ≈10.0 % of the response per ten percent of error, so effort spent elsewhere is largely decorative.
The subtlest error is answering the wrong question precisely. Confirm that net risk score is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.
Six things to confirm before acting on Transaction Risk
- Verify each input against its original source document, not memory.
- Check whether the formula treats your inputs as nominal or real dollars.
- Check Likelihood (1 = rare … 5 = almost certain) before anything else: it is the measured dominant input, ≈10.0 % of Transaction Risk per ten percent.
- Confirm rate conventions (APR vs effective, day-count) before comparing two offers.
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- Run the ±10 % stress on the top two levers and check that your conclusion survives both.
How to use the Transaction Risk tool properly
Using a calculator well sounds trivial, but the difference between a decision-grade figure and a throwaway one lives entirely in the routine. The routine for Transaction Risk takes a minute to learn and applies to every input above.
Step 1 — start from evidence. The inputs behind Transaction Risk are likelihood (1 = rare … 5 = almost certain), impact (1 = negligible … 5 = severe), control effectiveness (0–100 %). Write them down with their source next to each one; if you cannot name where a figure came from, that is the input most likely to be wrong. Comparisons are cheap: run the identical calculation for the alternative and look at the gap.
Step 2 — enter the conservative case first. Resist the flattering scenario. Type the inputs you would defend in front of a sceptical reader, read the Net risk score (3.7 / 25 for the example values), and note the verdict band. Precision is a promise you make about your data; make sure your inputs can keep it.
Step 3 — isolate your variables. Change one field, observe, revert. The live sensitivity list does the ranking for the default inputs; verify it against your own, because dominance shifts when the starting point shifts. Comparisons are cheap: run the identical calculation for the alternative and look at the gap.
Step 4 — run the scenario trio. Expected, pessimistic, optimistic. The gap between pessimistic and expected is the number to plan against; the optimistic result is useful only as a ceiling. When two sources disagree, it is almost never the arithmetic that differs.
Step 5 — save the story with the figure. A number without its inputs and its date is unusable within a quarter. Record 3.7 / 25, the assumptions behind it, and today’s date; your future self will be auditing a stranger’s arithmetic. The test of a good estimate is not that it feels right but that it changes what you do.
Where Transaction Risk matters in practice
In Currency & International the figure computed here is usually the first one somebody asks to see. Having it — with the formula behind it — changes your position in the conversation from participant to reference. Repeating a calculation with the same numbers proves only that the arithmetic is reliable — which is worth knowing.
Used properly this is a five-minute filter that saves weeks. Compute Transaction Risk, reject what fails, and only then bring in the expensive analysis for the survivors. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
Nothing here is stored or transmitted, so the habit of checking is free: open the page, re-enter current figures, compare with the number you saved last time. If a result feels obviously right, that is the moment to check the inputs hardest.
Transaction Risk — frequently asked questions
What affects Transaction Risk the most?
The short answer: Likelihood (1 = rare … 5 = almost certain). The longer answer is the sensitivity table on this page, where every numeric input was probed by ten percent and the net risk score recalculated — Likelihood (1 = rare … 5 = almost certain) moved it furthest, by roughly 10.0 % (3.3 / 25 to 4.0 / 25).
Do impact (1 = negligible … 5 = severe) and likelihood (1 = rare … 5 = almost certain) matter equally?
On these inputs, yes: the two measured within a rounding error of each other — ≈10.0 % and ≈10.0 % of the net risk score per ten-percent change. Treat them as one pair to verify together rather than ranking them.
What is a typical Transaction Risk?
There is no honest universal average for Transaction Risk, but there is a reference point: the defaults on this page produce 3.7 / 25 (Green — acceptable residual). Replace the inputs with your own and compare — that comparison is the useful meaning of “typical”.
How do I calculate Transaction Risk by hand?
Use the stated model — gross = likelihood × impact (1–25); net = gross × (1 − controls) — and substitute in the order the tool prints (it starts from Gross = 2 × 3 = 6). On the example inputs the hand route lands on 3.7 / 25, exactly what the calculator shows. A spreadsheet reproduces it in two or three cells; doing it once by hand is what makes the automated answer trustworthy.
What happens to Transaction Risk if likelihood (1 = rare … 5 = almost certain) changes by 10 %?
On these inputs a ±10 % change in likelihood (1 = rare … 5 = almost certain) takes Transaction Risk to 4.0 / 25 against the 3.7 / 25 example — around 10.0 % of the headline. The same test on every other field is in the sensitivity section.
Is the Transaction Risk result of 3.7 / 25 good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own Transaction Risk sit against the 3.7 / 25 reference above, how far would a plausible input error move it (≈10.0 % per ten percent on Likelihood (1 = rare … 5 = almost certain)), and what does the alternative option compute to?
Is Transaction Risk the same as what my bank quotes?
Often close but not identical: institutions quote rates on their own day-count and fee assumptions. Recompute with the actual dollar figures from a statement — if the gap is large, the fine print is doing work you should understand before signing.
Is Transaction Risk accurate?
The arithmetic is exact: gross = likelihood × impact (1–25); net = gross × (1 − controls) is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 3.7 / 25 result as the correct answer to the question you typed — and check the assumptions section before acting on it.
Why discount by controls?
A 20-score hazard half-mitigated is a 10, and 10s behave like a different risk class.
Do these scores compare across teams?
Only if the likelihood and impact scales are calibrated to the same definitions — the matrix is shared, the calibration is organisational.
Do I need an account to use this Transaction Risk calculator?
No, and no data leaves the tab. The engine runs in the page itself, which is why the worked example, the bands and the sensitivity ranking all respond instantly to your keystrokes.
The vocabulary of Transaction Risk
- Gross score
- 6 / 25 for the Transaction Risk worked case; it sits next to the main result because it carries context the headline leaves out.
- Control credit
- 2.3 pts on the example inputs — a companion figure printed beside the headline of Transaction Risk so that no result is read in isolation.
- Likelihood × impact band
- Low-low for the Transaction Risk worked case; it sits next to the main result because it carries context the headline leaves out.
- Net risk score
- The primary output of this tool: 3.7 / 25 for the default inputs, computed exactly from gross = likelihood × impact (1–25); net = gross × (1 − controls).
- Worked example
- Every substitution in order, from the example inputs to 3.7 / 25 — the audit trail for the headline figure.
- Verdict band
- A named zone on the range of plausible results; the example inputs land in “Green — acceptable residual”, and your inputs may not.
- Sensitivity (±10 %)
- How far the Transaction Risk moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Method, sources and what this tool cannot tell you
Everything above runs on one stated formula, applied without hidden coefficients: gross = likelihood × impact (1–25); net = gross × (1 − controls). Source of record: ISO 31000-aligned qualitative risk matrices. Where a professional version of this calculation differs, it differs in inputs and jurisdiction-specific coefficients, not in the algebra — which is why re-checking your inputs beats hunting for a second calculator.
This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. What that buys you is reproducibility — two people, two browsers, the same arithmetic, and a printed trail from inputs to result that either of them can audit.
What to do with your Transaction Risk next
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
Whoever you are (people who need one trustworthy number before their next decision), the next step is the same: replace the example inputs with your own, note the date, and re-run whenever a figure moves. In Finance & Banking, a dated figure is a trend, and an undated one is a rumour.