Report
Discussion
A report communicates structured information about a subject, event, condition, activity, obligation, result, or state of affairs. In business and regulatory contexts, a report does more than present information to a human reader. A report also provides facts that another person, organization, system, regulator, auditor, or process can interpret, validate, compare, analyze, or act upon.
The Standard Business Report Model (SBRM) treats a report as a structured information artifact. A report contains facts. Dimensions distinguish one fact from another. A report model explains what is in the report and its organization.
This treatment separates the report from a presentation format. A report may appear as a form, a spreadsheet, a PDF, an XBRL filing, a JSON document, an RDF graph, a database extract, a dashboard, or a message set. The report remains the information artifact. The format provides one realization of that artifact.
In DIDO Solutions' work, a report should have traceable semantics, structure, facts, dimensions, rules, constraints, and validation logic when the report supports governance, regulatory interpretation, audit, conformance, or automated processing.
Definition
structured information artifact that contains reported facts distinguished by dimensions within a defined reporting context
Source
OMG Standard Business Report Model (SBRM), Version 1.0 Beta 1; specialized for use in the FX Demo Reference Architecture.
Note
A report is not equivalent to its presentation format. A PDF, spreadsheet, web page, XBRL instance, JSON document, or RDF graph may realize a report, but the report consists of the reported information, its organization, its facts, its dimensions, and its governing report model.
Example
An FX regulatory report may include details of a confirmed FX trade, such as counterparties, currency pair, notional amount, trade date, settlement date, jurisdiction, validation status, and reporting timestamp. Dimensions distinguish facts by reporting entity, period, jurisdiction, currency, and lifecycle state.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.