Skip to content
Independent research & intelligence
OPEN VARIABLE

Evidence-First Signal Intelligence

Menu

Analysis / Capital & Markets / Policy & Regulation

A bank disclosure is only useful if it can be compared

Machine-readable reporting could make bank risk easier to examine. Comparable fields, definitions and reporting periods will determine how useful it becomes.

Cite this work

OPEN VARIABLE. A bank disclosure is only useful if it can be compared. 2026-10-04. https://www.openvariable.com/research/machine-readable-bank-disclosures

A reporting format can shape the analysis

Publishing a document and making its information usable are different achievements. A reader comparing banks needs to identify the same measure across institutions, periods and reporting boundaries. A PDF can carry that information while leaving the comparison laborious and vulnerable to extraction errors.

In its 1 October statement, the Basel Committee said it had approved a final standard for machine-readable Pillar 3 disclosures, with publication expected around the end of the year. The statement identifies PDF-only reporting as an obstacle to aggregating and comparing bank data. Approval and publication are separate milestones. BIS / Basel Committee on Banking Supervision ↗

Easier extraction is the beginning

A structured field removes one source of friction: the analyst no longer has to recover a number from a page layout. It does not by itself settle what that number covers. A useful comparison also needs the reporting period, unit, consolidation boundary and definition, together with a way to recognise restatements.

Consider two disclosures labelled operational loss. If their periods, categories or coverage differ, placing them in adjacent cells may create a misleading comparison. A reliable workflow retains the source and definition with each value. Machine readability should make that chain easier to preserve, not encourage the reader to discard it.

AI risk adds a classification question

The same meeting statement discusses AI-related financing links and operational vulnerabilities, including cyber attacks and shared dependencies. The committee also agreed to review whether operational-loss event categories adequately capture cyber risk and AI developments. That is a programme of further work, not a finding that every bank’s AI exposure is already reported consistently.

These developments raise two distinct questions for a reader. Can reported information be collected consistently? And do the categories capture the exposure being investigated? A more convenient reporting channel helps with the first. The second depends on the definitions and observations that eventually accompany it.

Follow the standard into practice

The next evidence is the published standard: its scope, fields, definitions and timing. National implementation and actual bank disclosures would then show what changed in practice. The committee’s international standard-setting role should not be confused with a rule already operating in every jurisdiction.

Our interpretation is that disclosure usability belongs in any serious assessment of financial transparency. The strongest test is a reproducible comparison whose numbers can be traced back to the published records. This article does not assess a named bank, establish compliance or offer an investment recommendation.

Sources

  1. Basel Committee meeting: supervisory initiatives and banking-system risks

    BIS / Basel Committee on Banking Supervision · 1 Oct 2026

    Official meeting statement. Approval of a forthcoming standard; not evidence of publication, national implementation or bank compliance.

Report a correction