Cash Management Bank Statement Report

Cash Management◆ Seeded · Bank statements

Bank account balances and transaction information for specific bank statements — opening and closing balance, the statement lines, and their reconciliation status.

Sample build of the Cash Management Bank Statement Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Sample build · illustrative

Filters

Period

FEB-26

Ledger

US Primary

Currency

USD

Statements

$14.20M

Closing balance

Lines unreconciled

Statement Date	Bank Account	Opening	Lines	Closing	Reconciled
2026-04-30	1000-2100-000	Sample	Sample	Sample	Sample
2026-03-31	1000-5400-000	—	—	—	—
2026-02-28	1000-1410-000	Sample	Sample	Sample	Sample
2026-01-31	2000-2100-000	—	—	—	—
2025-12-31	1000-6300-000	Sample	Sample	Sample	Sample
2026-04-30	1000-2100-000	Sample	Sample	Sample	Sample

AI Analyst · active

reading

The report reads the statement lines per statement with opening and closing balances.

flag

42 statement lines remain unreconciled — the bank balance won't tie to the books until they clear.

root cause & next step

Tune the auto-match rules or post the missing system transactions; unmatched statement lines are why a bank rec won't close.

Illustrative data. The live interactive version — drill-through, filters, export, and the AI Analyst — runs on your warehouse. See it live →

This is the report's BI Publisher data model — the SQL data set BI Publisher runs against Oracle tables to produce the output. The same SQL becomes a dbt model in your warehouse, so one definition drives both the formatted report and the analytics layer.

Data sources

CE_STATEMENT_HEADERS_ALL
CE_STATEMENT_LINES
CE_BANK_ACCOUNTS
CE_BANK_ACCT_BALANCES

How it interconnects: this data set reads the physical tables above. Those same tables surface in OTBI as subject areas and in BICC as PVOs — three lenses on one source. Open any table to trace its subject areas and View Objects.

The SQL data set is authored to this report's exact spec during the build and ships as the BI Publisher data model plus a matching dbt model — one definition, both layers.

The data-warehouse model — one fact surrounded by conformed dimensions (what you slice by) and measures (what you aggregate), expressed as dbt so it migrates with you. Grain: one row per source transaction.

●— fact → dimension join

Element	Type	Definition
CE_STATEMENT_LINES	dimension	dimension
CE_BANK_ACCOUNTS	dimension	dimension
CE_BANK_ACCT_BALANCES	dimension	dimension
Amount	measure	measure

Runs on your cloud warehouse — Snowflake, BigQuery, Redshift, or Synapse on AWS, Google Cloud, Azure, or any provider. Reconciled to the source control total — 0% variance by design. You own the code, the model, and the data.

How the data gets here: a BICC bulk extract of the source tables above, on the same pattern for every report. See the extraction pattern & data flow →

See the complete model

How this report's fact and dimensions fit the full picture, via conformed keys.

Cash Management data model →Enterprise model →

Every source object behind this report. Each linked table has its own page with full column descriptions, drawn from the Oracle BICC lineage and articulated for practitioners.

Table	Reporting columns	Subject areas
CE_STATEMENT_HEADERS_ALL	Setup / configuration table — joined for reference, not exposed for analytics
CE_STATEMENT_LINES	23	3
CE_BANK_ACCOUNTS	9	12
CE_BANK_ACCT_BALANCES	Setup / configuration table — joined for reference, not exposed for analytics

Reporting columns = fields the report selects that are exposed as analytics attributes; subject areas = the OTBI subject areas the table appears in. Setup and configuration tables (master data, ledger and book setup, lookups) are referenced by the report's joins but aren't exposed as analytics columns or subject areas — that's expected, not a gap.

Customization note Ships per statement; treasury usually wants a multi-account daily position with prior-day and intraday balances on one screen. Irvine rebuilds these on your data.