Reversal Status Report

Receivables◆ Seeded · Receipts

Reports the status of automatic receipt reversals in a settlement batch, with receipt date, number, amount, reversal reason, and a note on any reversals that failed.

Sample build of the Reversal Status 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

Reversals

$420K

Reversed value

Failed reversal

Receipt	Date	Amount	Reversal Reason	Status
Sample	2026-04-30	$1,240,500.00	Standard	Open
—	2026-03-31	$842,150.75	Corporate	Posted
Sample	2026-02-28	$96,400.00	Standard	Validated
—	2026-01-31	$1,005,233.10	Default	Open
Sample	2025-12-31	$58,720.40	Standard	Paid
Sample	2026-04-30	$1,240,500.00	Standard	Open

AI Analyst · active

reading

The report reports the status of automatic receipt reversals in a settlement batch.

flag

Six reversals failed — the receipt is in a half-reversed state, neither applied nor cleanly backed out.

root cause & next step

Resolve the failed reversals manually; a stuck reversal misstates both cash and the customer balance.

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

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
AR_RECEIVABLE_APPLICATIONS_ALL	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.

Receivables 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
AR_CASH_RECEIPTS_ALL	25	9
AR_RECEIVABLE_APPLICATIONS_ALL	35	2

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 Failed reversals need follow-up; the build adds reason-coded exception routing rather than a passive status page. Irvine rebuilds these on your data.