publish.gold_bacen/fct_income_statement

Comece aqui: guia de acesso aos dados

Readiness (label, not a promise): declared (code) · materialized:unknown until a collector run or publisher check · queryable:unknown until publication

Declared (by code, not by catalog YAML)

field	value
table	fct_income_statement
declared_by	ciano_lake/publish/to_postgres.py::GOLD_TABLES
postgres_schema	gold_bacen

This table is part of the declared Postgres publish surface (ciano_lake/publish/to_postgres.py::GOLD_TABLES). It has no catalog entry — materialization and queryable state are publisher facts, filled at publication time.

Explore in Metabase: https://bi.cianoinvestimentos.space (internal, Tailscale-only).

Deep documentation (curated, grounded in the declarations above)

Long-format income-statement facts (report_type Resultado / Demonstração de Resultado): same join and publication path as fct_balance_sheet.

Grain: one row per (institution, quarter, report, column) for income-statement reports

Units: inherited from valores (per-column, report-scoped; see valores entry)

Safe-join guidance:

• Income-statement rows are period flows (cumulative within the year in BACEN's presentation); comparing across quarters requires the report's own period semantics — verified per report_type, not assumed.

Curated, evidence-backed lineage (not Bruin ordering):

from	to	kind	evidence
bacen.instituicoes.ifdata_valores/valores	publish.gold_bacen/fct_income_statement	curated	ciano_lake/gold/instituicoes/fcts.py::_materialize_fct

Evidence references:

• ciano_lake/gold/instituicoes/fcts.py
• ciano_lake/publish/to_postgres.py (GOLD_TABLES, per-table commit)