Invoices Posted to Suspense Report

Receivables◆ Seeded · Accounting

Lists transactions whose revenue posted to a suspense account during AutoInvoice import, showing transaction class, customer, transaction date, and amount by business unit.

Sample build of the Invoices Posted to Suspense 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

Suspense transactions

$310K

In suspense

Unresolved

Transaction	Class	Customer	Suspense Account	Amount	Reason
Sample	Standard	Acme Industrial	1000-2100-000	$1,240,500.00	Standard
—	Corporate	Northwind Trading	1000-5400-000	$842,150.75	Corporate
Sample	Standard	Globex Holdings	1000-1410-000	$96,400.00	Standard
—	Default	Initech LLC	2000-2100-000	$1,005,233.10	Default
Sample	Standard	Umbrella Corp	1000-6300-000	$58,720.40	Standard
Sample	Standard	Acme Industrial	1000-2100-000	$1,240,500.00	Standard

AI Analyst · active

reading

The report lists transactions whose revenue landed in a suspense account during AutoInvoice import.

flag

$310K of revenue sits in suspense with 18 items unresolved — revenue not yet recognized to its proper account.

root cause & next step

Fix the AutoAccounting or revenue rules that couldn't derive an account; suspense revenue is recognized revenue parked in the wrong place.

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
RA_CUSTOMER_TRX_LINES_ALL	dimension	dimension
AR_DISTRIBUTIONS_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
RA_CUSTOMER_TRX_ALL	58	16
RA_CUSTOMER_TRX_LINES_ALL	56	7
AR_DISTRIBUTIONS_ALL	12	6

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 Suspense postings signal a revenue-account-derivation gap; the build usually adds a root-cause view that pinpoints the missing AutoAccounting rule. Irvine rebuilds these on your data.