Ontology
A machine-readable financial ontology that encodes 7 global standards into a single, validatable knowledge graph. Every entity, relationship, and constraint is defined in RDF/OWL and enforced by SHACL shapes.
Seven international standards natively embedded into the Revenu ontology, creating a unified semantic layer for banking operations.
Financial Industry Business Ontology — the EDM Council's canonical model for financial instruments, entities, and processes.
Chart of Accounts for the National Financial System — BACEN's mandatory accounting taxonomy for Brazilian financial institutions.
International Financial Reporting Standards — global accounting standards for transparent and comparable financial statements.
Universal financial messaging standard — structured data model for payments, securities, trade, and FX messaging worldwide.
Brazil's instant payment system — Central Bank regulated real-time payments with QR codes, keys, and 24/7 settlement.
Banking Industry Architecture Network — service landscape framework defining 300+ service domains for banking operations.
Information Security Management — international standard for establishing, implementing, and maintaining information security controls.
An architecture where the domain model IS the ontology. Code conforms to formally defined semantics, not the other way around.
Every transaction, entity, and relationship is validated against SHACL shapes derived from the ontology. Invalid data is rejected before it enters the system.
Regulatory requirements from COSIF, IFRS, and BACEN are encoded as formal constraints. Compliance is checked automatically, not manually.
A single source of truth for all financial concepts. Account, Transaction, Party — every term has one definition, used consistently across all 11 engines.
Traditional banking systems rely on implicit knowledge in code. We made it explicit, verifiable, and future-proof.
Auditors can inspect the ontology directly. Every rule is a SHACL shape, every constraint is testable, every mapping is traceable to a standard.
New standards are absorbed into the ontology, not bolted on. When FIBO releases a new version, we extend the graph — no code rewrite needed.
As regulations evolve and new standards emerge, the ontology grows organically. The system adapts through semantic extension, not structural refactoring.
SHACL (Shapes Constraint Language) shapes define the rules that every piece of data must satisfy. Here's a real example from the Revenu ontology.
ex:AccountShape a sh:NodeShape ;
sh:targetClass fibo:Account ;
sh:property [
sh:path fibo:hasAccountIdentifier ;
sh:minCount 1 ;
sh:datatype xsd:string ;
sh:pattern "^[A-Z]{2}[0-9]{2}[A-Z0-9]{4,}" ;
sh:message "Account must have a valid IBAN" ;
] ;
sh:property [
sh:path fibo:hasCurrency ;
sh:minCount 1 ;
sh:class fibo:Currency ;
sh:message "Account must be linked to a Currency" ;
] .This SHACL shape validates that every Account entity has a valid IBAN identifier and is linked to a Currency. These rules are evaluated at runtime against every account creation and update, ensuring data integrity at the ontology level.