What we doSmart IT SolutionsBIZENIUS Accord
One platform. Every risk. Your rules.
Banks tell us the quarterly regulatory return takes three to eight weeks, across Finance, Risk, Treasury, Compliance and IT — reconciling extracts, rebuilding last quarter’s workbook, chasing the difference between two versions of the same number. In BIZENIUS Accord it is one governed run measured in seconds: twenty-plus calculation engines chained under one approval, computing the whole Basel framework on your own servers, configured to your regulator, with every figure carrying the lineage that survives a supervisory review.
Where this begins
The quarterly project Accord replaces.
Three to eight weeks. Then it starts again
That is what the quarterly return actually costs: twelve to thirty-two weeks a year of coordinated effort from the people you can least spare — and next quarter starts from the same place, because a workbook retains nothing it learned.
The question your regulator asks has changed
Supervision used to ask for the number. It now asks how the number moved, on what data, under whose approval, and what it becomes under stress. A workbook cannot produce an answer it never recorded.
The chain has weak links
Five departments in sequence: extract, reconcile, rebuild, review, submit. Whichever one is late, the whole return is late — and the method walks out with whoever last maintained it.
What’s inside
Twenty-plus engines. One governed run.
Accord is a working platform, not a programme of work — the whole Basel framework on a single server inside your perimeter, licensed to what you use, and answerable to your examiner from the first run.
The engine room: 20+ engines, one Run All
Credit (SA-CR, F-IRB), market (FRTB-SA, SA-MR, SSA), counterparty (SA-CCR), CVA (BA, SA, AA), operational (SA-OR, BIA, TSA), liquidity (LCR, NSFR), securitisation (SEC-SA, IRBA, ERBA), large exposures and concentration, capital and leverage with the full buffer stack, MDA and the Basel 3.1 output floor, ICAAP, ILAAP, IRRBB and recovery planning — chained automatically, so credit RWAs feed capital ratios under one approval. A hundred thousand exposures are risk-weighted in under a minute.
Basel I through 3.1, side by side
The regime is selectable per run, so your current rules and the target rules compute on the same book at the same time. Profiles are effective-dated: a rule change is configuration your Senior Risk approves, not a rewrite you buy.
A scenario library that arrives populated
39 stress scenarios and 8 recovery scenarios built in — BCBS, EBA and PRA sets, historical replays, climate, geopolitical, macro, market and operational shocks, plus Africa, MENA and IMF regional libraries — each with its own severity band and shock parameters. Your regulator’s prescribed scenarios and your board’s risk-appetite cases are added during implementation. Monte Carlo capital simulation and reverse stress testing are optional modules.
20+ returns, disclosures and the audit report — from one approval
Capital adequacy, liquidity, stress and disclosure outputs produced from the same computation your management numbers use, formatted for the return. And for any run, on demand, an audit report: methodology, BCBS citations, inputs, step-by-step calculations, plausibility appendix, movement attribution and an attestation page — the document that answers the examiner without anyone rebuilding the quarter.
Built to be examined, not just to compute
Built around BCBS 239. Every figure carries its lineage back to the exposure and the BCBS paragraph applied. A SHA-256 fingerprint and a frozen snapshot of inputs on every run; a golden-number regression suite that locks every calculation against unintended change; a pre-calculation data-quality gate; deterministic plausibility rules that annotate rather than silently adjust; maker-checker sign-off across five roles — Administrator, Senior Risk, Risk Analyst, Auditor, Read-only.
Your data never leaves the bank
One server inside your perimeter — on-premises or your private cloud, container-based. Licensing is an offline signed file: no phone-home, no internet dependency. Your core banking, loan, treasury and warehouse systems feed it by CSV or Excel export through the data-quality gate; an automated bridge with API integration is built where you want it. Sovereignty is architectural, not a promise.
How a deployment runs
Six stages. Cutover on your decision.
Define the scope
Agreed scope of work: modules, effort, schedule. The first chargeable stage.
Install
Your server or private cloud, container-based, inside your perimeter.
Configure
Your regulatory profile: risk weights, buffers, limits, national discretions, return formats.
Integrate data
Source systems mapped; the data-quality gate tuned to your extracts.
Validate
The parallel run through a full cycle, with user-acceptance evidence packs.
Go live
Cutover, training through the Capability Arc, handover.
Accord runs in parallel with your existing process through a full reporting cycle — same book, same period, both sets of numbers on the table with the differences explained. You cut over when the parallel run satisfies you, not on a vendor’s timetable.
Proof
Judged by what changes.
20+
calculation engines in one orchestrated run — with 39 stress and 8 recovery scenarios built in, and 100,000 exposures risk-weighted in under a minute
BIZENIUS Accord
Asked before engaging
The four questions you are going to ask — and two more.
“Our regulator is not the Basel Committee.”
Correct — and the platform does not assume otherwise. Pure BCBS profiles are the baseline; your regulator’s risk weights, buffers, limits, national discretions and return formats are configured as your own profile during implementation. Most African prudential regimes are BCBS-derived, so the baseline already produces meaningful ratios on day one, and the profile closes the distance.
“We cannot afford a disruptive implementation.”
Nor should you. Accord runs in parallel with your existing process through a full reporting cycle: same book, same period, both sets of numbers on the table with the differences explained. You cut over when the parallel run satisfies you — not on a vendor’s timetable.
“How do we know the numbers are right?”
You check them, and you keep checking them. Every result carries step-by-step lineage back to the exposure, with the BCBS citation for the rule applied. Calculations are locked against unintended change by a golden-number regression suite, and the model inventory reports honestly which engines have user-acceptance-test evidence behind them and which do not.
“What happens when the rules change?”
Your team changes them — not us. Risk weights, credit-conversion factors, capital buffers, IRB and output floors and loss-given-default values are parameters your own Senior Risk or Administrator maintains. Each change is dated from the day it takes effect, requires four-eyes approval before it goes live, and writes a permanent record of the old value, the new value, who changed it and why. Prior periods keep computing under the rules that applied to them. A circular from your regulator becomes a controlled configuration change — not a vendor release cycle, and not an invoice.
How is Accord licensed?
Two models. A perpetual licence with an Annual Maintenance Contract covering updates, regulatory-change maintenance and support; or an annual all-inclusive subscription. Either way the licence is delivered as a signed offline file to your own server with no cloud dependency, and you license only the engines and report families you use — extended later without reinstallation. Implementation, integration and regulator-profile configuration are scoped per engagement and billed separately on time and materials. The quotation follows the demonstration.
When would you recommend a custom build instead?
When your methodology genuinely departs from the standardised frameworks, or you want machinery designed around a bespoke process and owned as source code. Accord is the fast, proven path for the Basel stack; our custom builds cover what no product should be bent into doing. We will tell you honestly which fits — sometimes the answer is both.
The Capability Arc™
The platform is one point on the arc.
Accord computes the framework; the arc makes sure your institution commands it — the advisory that strengthens the framework, the masterclass that equips the team.
Fix it · Advisory
ICAAP & Capital Planning Advisory
The capital framework Accord computes — reviewed, strengthened and finalised with senior practitioners.
Learn it · Training
Basel III Final Reforms & Capital Planning
The masterclass that gives your risk and finance teams command of what the platform computes.
The ask
See the framework run, end to end.
Not a slide walkthrough — and no data request. We demonstrate on a representative Tier-2 balance sheet we bring, computed on the pure Basel III framework, so your team sees capital adequacy, LCR and NSFR computed; a stress scenario run and its capital impact attributed; one reported ratio traced back to the exposure behind it; a parameter changed under four-eyes approval with the change history shown; and the audit report generated and read, in the room — without releasing a single file.
Your own data comes later, in the parallel run, once the implementation is under way and the usual agreements are in place. A senior engineer responds within two working days.
BIZENIUS Accord
Leave the question with us.
Two lines on the mandate is enough — a senior practitioner replies within one business day.