Automatic Receipt Creation and Remittance Execution Report

Receivables◆ Seeded · Receipts

Reports the batch process that creates automatic receipts and remittances, listing generated and remitted receipts plus any validation errors by batch.

Sample build of the Automatic Receipt Creation and Remittance Execution 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

2,100

Receipts created

$16.80M

Remitted

Validation errors

Batch	Receipts Created	Remitted	Amount	Errors
Sample	Sample	Sample	$1,240,500.00	Sample
—	—	—	$842,150.75	—
Sample	Sample	Sample	$96,400.00	Sample
—	—	—	$1,005,233.10	—
Sample	Sample	Sample	$58,720.40	Sample
Sample	Sample	Sample	$1,240,500.00	Sample

AI Analyst · active

reading

The report reports the batch that creates automatic receipts and remittances.

flag

34 receipts errored in validation — those customers' auto-payments didn't process this run.

root cause & next step

Fix the errors — usually a missing bank instruction or expired mandate; a failed auto-receipt is expected cash that didn't arrive.

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_RECEIPT_METHODS	dimension	dimension
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_RECEIPT_METHODS	1	5
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 The validation errors are the value; teams surface them as an actionable queue instead of a process log. Irvine rebuilds these on your data.