Accelerate your BCBS 239 program. Prove the origin of every indicator in your reports.
Your deadline is approaching. Vokse analyzes your source code as it exists and identifies every gap, all the way to the regulatory report. First results in 4 weeks.
Is your BCBS 239 program ready for the next review?
8 questions, 3 minutes, instant result, no email.
Since 2013, the supervisor has been asking four questions
During the crisis, many banks could not quickly state their exposure to a client or a country, or whether the figures presented to the executive committee were right. Since then, BCBS 239 has required reliable, traceable and usable Risk data.
-
1 Do you know exactly where your data comes from and how it is transformed?
Data lineage
-
2 Can you demonstrate that it is complete, accurate and consistent?
Data quality
-
3 Can you aggregate it quickly?
Risk aggregation
-
4 Can management make its decisions based on reliable, traceable information?
Governance and controls
You have documented. You still have to demonstrate.
- Hundreds of sources, thousands of indicators. And decentralized controls, run separately in each data source, with no end-to-end view.
- A data catalog filled in by hand, after the fact. Out of date before it is finished, and business teams never open it.
- A lineage drawn for the last review. It is wrong by the next one.
- One parser per technology. Each one breaks at the first syntax change, and every adaptation is billed again.
- AI alone. Thousands of proposed links, just as many to validate by hand.
- Governance split across Risk, Finance and IT. Subsidiaries each move at their own pace and remediations don't hold.
- One question from the auditor, a team mobilized for weeks.
And the same questions come back from one review to the next.
Vokse accelerates your BCBS 239 program
Technology, methodology and support adapt to the scope and progress of your program.
-
1
Today's lineage is purely technical
It describes the flows without explaining the uses, controls and impacts.
-
2
It is disconnected from operational reality
Business teams, processes and responsibilities stay outside the diagram.
- Application Salesforce, SAP
- Database DB2, relational databases
- Table customer, fx_rate
- Column country_code, SOURCE_CCY
3
Vokse is an accelerator
The platform, the methodology and the support connect the technical side to the decisions and expected evidence.
- Regulatory reports COREP, FINREP, ICAAP
- Regulatory indicators BCBS 239 indicators
- Business process Credit risk aggregation
- Business rules Currency conversion
- Controls Accuracy, completeness
- Owners Risk, Finance, IT
- Processing Cobol LOANENR and FXCONV
- Data and systems DB2, relational databases
The question is no longer “do you know how it works?” but “is it under control today?”
The traditional approach inventories, documents and audits from time to time. Vokse monitors critical flows, controls and BCBS 239 indicators continuously. Your teams spend their time solving problems, no longer searching for them.
An anomaly, with all its context
- The data concerned
- The systems affected
- The business rules affected
- The processes exposed
- The regulatory reports at stake
- The teams responsible
A change, its impact in advance
Change a program, a table or a business rule: Vokse shows the processing, indicators and reports affected before the change goes into production.
An action plan run together
Every alert comes with its context and an owner. Actions are prioritized and tracked through to resolution, in the same tool for business teams, IT and data.
From the DB2 table to the COREP report, a column-by-column use case
Cobol, JCL, Copybooks, DB2, relational databases, Salesforce. Reverse-engineering algorithms, the result of 25 years of R&D, rebuild the flows; AI sorts and links. Applications, tables, columns, transformations, business rules and processes are linked without any link being declared by hand.
From customer repositories to account management, every table and every column is linked. Links found in the code are distinguished from declared links, and the business view translates each column into business data.
A link opens the actual transformation. Here, the currency conversion of the outstanding balance: the rule applied, and the Cobol programs that implement it, lines 112 to 122.
The business process for credit risk aggregation and regulatory reporting is modeled in the tool. Each step carries its data and opens its lineage in one click.
Accuracy and completeness controls run continuously. An anomaly appears on the affected column and follows the path of the data to the report it affects.
COREP, ICAAP, BCBS 239 indicators: completeness, accuracy, uniqueness and consistency measured against a threshold and tracked over time. Auditors consult the traceability through dedicated access.
-
1 Vokse analyzes your code as it is
Cobol, JCL, Copybooks, DB2, relational databases, Salesforce. Reverse-engineering algorithms, the result of 25 years of R&D, rebuild the flows; AI sorts and links. Applications, tables, columns, transformations, business rules and processes are linked without any link being declared by hand.
-
2 Lineage, column by column
From customer repositories to account management, every table and every column is linked. Links found in the code are distinguished from declared links, and the business view translates each column into business data.
-
3 Every transformation, down to the line of code
A link opens the actual transformation. Here, the currency conversion of the outstanding balance: the rule applied, and the Cobol programs that implement it, lines 112 to 122.
-
4 Linked to the business process
The business process for credit risk aggregation and regulatory reporting is modeled in the tool. Each step carries its data and opens its lineage in one click.
-
5 Anomalies, along the path of the data
Accuracy and completeness controls run continuously. An anomaly appears on the affected column and follows the path of the data to the report it affects.
-
6 Quality tracked report by report
COREP, ICAAP, BCBS 239 indicators: completeness, accuracy, uniqueness and consistency measured against a threshold and tracked over time. Auditors consult the traceability through dedicated access.
What each team gains
An end-to-end view, readable by IT and Risk alike, and available to Audit and the regulator.
- Risk
- Every indicator in a report can be justified, from the cell down to the line of code.
- Finance
- COREP and FINREP produced faster, with less rework before submission.
- IT
- No more lineage to redraw, and changes delivered without bad surprises in the reports.
- Data Office
- Quality measured continuously and every remediation followed through to the end.
- Compliance and Audit
- Audits and inspections prepared in far less time, with traceability consulted without mobilizing the teams.
From code to piloting, in 7 steps
-
1 Reverse engineering
Code and databases are read, flows rebuilt.
-
2 Modeling
Business processes are drawn up and linked to the data.
-
3 Repository
A glossary and business objects give every column a name.
-
4 Quality requirements
Each indicator gets its quality requirements and thresholds.
-
5 Controls
Controls run on the data, continuously.
-
6 Activation
Alerts, owners and action plans are set in motion.
-
7 Real-time piloting
Business and technology are aligned on operational impacts.
What you've tried, what Vokse changes
| Data catalog | Technical lineage (parsing tools) | Consulting engagement with AI | 
|
|
|---|---|---|---|---|
| Program acceleration | Manual entry | Tedious integration and maintenance | One-off engagement | Instant deployment |
| Real-time piloting | Manual updates | Technical view | Point-in-time snapshot | Yes, continuously |
| Alignment between business and technology | By data entry | Technical only | In workshops | Shared operational impacts |
| Based on the actual code | Links declared by hand | One technology at a time | Assumed links | Yes, all technologies |
| Alerts | No | Technical alerts | Ad hoc | Yes, with context and owner |
| Linked to business processes | By data entry | No | Ad hoc | Yes |
| Keeps up with IT changes | Manual updates | Adaptation for every change | No | Yes, continuously |
| Quality checked continuously | Separate module | No | Ad hoc | Yes, threshold per report |
| Anomaly tied to the affected report | No | No | By hand | Yes, with an owner |
| Impact analysis | Depends on data entry | Technical only | One-off study | Technical and business, immediate |
| Direct auditor access | Team mobilized | Team mobilized | Team mobilized | Dedicated access |
| Group and subsidiary piloting | Each subsidiary at its own pace | Each subsidiary at its own pace | Each subsidiary at its own pace | Consistent controls |
| Cost | Licenses per module and per user | Adaptations billed | Consulting days | All-inclusive subscription |
| Getting started | Several months | Several months | Several months | 4-week pilot |
“BCBS 239 goes beyond compliance. It is a matter of control and trust in risk data. Vokse contributes to this requirement by strengthening visibility into its quality, its traceability and the associated responsibilities.”
Frequently asked questions
Does Vokse store your data?
No. Vokse reads your metadata, your data and your code, in read-only mode.
Which technologies are covered?
All modern and legacy technologies: Cobol, JCL, relational and NoSQL databases, business applications such as Salesforce, SAP and Microsoft Dynamics, data applications, data warehouses, data lakes, as well as structured, semi-structured and unstructured files.
Which regulatory reports are covered?
Vokse covers all regulatory reports, for example COREP, FINREP, ICAAP, stress tests and your BCBS 239 indicators. Each data item is linked to the report that uses it.
We already have a catalog or a lineage tool.
Vokse connects to it, as it does to your quality, ETL and BI tools, and links technical lineage to business processes. Nothing is replaced.
Not all of our subsidiaries have mapped their sources.
Vokse automates source mapping by connecting to a department's sources, applications and files. It also tracks how they change over time.
Can Vokse be installed on our premises?
Yes, as an option. Vokse can also be deployed in your environment.
Does Vokse perform risk aggregation?
No. Vokse covers traceability, data quality and report reliability. Aggregation remains with your analysts.
What does a 4-week pilot cover?
A first end-to-end scope: from a data source to the report.
How long does it take to get started?
The platform deploys instantly, then connects to your sources in a few clicks. A first end-to-end scope is completed in 4 weeks.
How can Vokse support our teams?
Vokse is a software vendor and can train your teams in implementation, then let them move forward on their own. In coaching mode, Vokse provides scoping, methodology and supervision while your teams qualify the lineage, link it to processes and extend it to all your BCBS 239 indicators, until they are autonomous. In operational mode, Vokse leads the project with your teams.
How is the price structured?
An annual subscription, all features and all users included. The first year adds setup and training. The amount depends on the scope and is set during an initial conversation.
