Financial ontology packs
The BCBS 239 vocabulary comes pre-loaded and the Basel, IFRS, GAAP, and SOX vocabularies are arriving behind it, so your glossary starts from the language your regulators and your finance teams already use. Instead of writing hundreds of definitions from a blank page, you map what you have to concepts an examiner already recognizes.
Framework vocabularies load as versioned packs, structured as ontologies rather than flat term lists, with BCBS 239 first.
You map your house terms and physical columns to regulatory concepts, so an examiner's question lands on your actual data.
Every term carries framework context, so 'default' or 'exposure' carries the definition that applies to the report you are building.
Packs are versioned: updates arrive as proposed changes with a diff, and nothing in your glossary moves until a steward accepts it. Agents propose, and humans decide.
A sealed record shows when each mapping and definition took effect and who approved it.
Load
Pick the packs that match your reporting obligations.
Map
Link your terms and columns to regulatory concepts; each link lands as a claim.
Approve
Stewards accept or reject mappings through the one decision door, with maker-checker where you require it.
Version
Pack updates come as reviewable proposals, never as silent rewrites of your glossary.
“Do we define 'default' the way Basel defines it?”
That is exactly the question the mapping layer answers: framework vocabularies load as packs and your house terms map to them explicitly. Where your definition and the framework definition diverge, the mapping makes that visible instead of leaving it to interpretation.
“Which of our data maps to BCBS 239 critical data elements?”
The BCBS 239 pack ships as a structured ontology, and you map your terms and physical columns to its concepts. Once those mappings are in place, this question resolves to a concrete list of columns and datasets rather than a research exercise.
“When did this definition change, and who signed off?”
Every mapping and definition carries a sealed record of when it took effect and who approved it. Pack updates arrive as reviewable proposals with a diff, so nothing changes without a steward's explicit acceptance.
Start with proof, not a promise.
There are three ways in, and each one earns the next. You approve the exit criteria before we spend any more of your time or budget.
A 60-minute working session
Bring one report that is expensive to prove. We walk the mechanism against it. Nothing is required from your side.
A two-week guided sandbox
Your team works hands-on against a synthetic sample bank. It requires zero access to your systems and zero procurement.
A six-week proof on your systems
We use read-only metadata across five systems and one priority report, scored against criteria both sides sign first. The decision it produces is yours.