Analytics Catalog/Oracle Fusion ERP/Receivables/Receivables to General Ledger Reconciliation Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Receivables

Receivables to General Ledger Reconciliation Report

Receivables

The Receivables to General Ledger Reconciliation Report compares AR transactional and accounted balances to the GL receivables control account, flagging transactions that are unaccounted, fall outside the account range, or were posted to GL from outside Receivables. It requires the Prepare Receivables to General Ledger Reconciliation process to run first.

Used by · AR managers and controllers at period close.Run · After Create Receivables Accounting, before closing the AR period.

The question it answers

Does AR tie to the GL receivables account, and which transactions explain any difference?

Run note · BIP run  High-volume GL extracts can exceed BI Publisher's online output limit and time out. Run it as a scheduled process (ESS) with output bursted to file or email rather than online preview, and bound it by ledger and period.

Run note · Performance  The subledger (XLA) join — especially Projects-to-XLA — is a known BI Publisher performance trap on large ledgers. Pre-join it in the warehouse, or apply tight ledger, period, and source filters before running online.

Sample build of the Receivables to General Ledger Reconciliation Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Receivables to General Ledger Reconciliation Report
Sample build · illustrative
Filters
Business Unit
APAC
Ledger
US Primary
Period
FEB-26
Receivables Account
1000-1410-000
$22,415,880
AR Subledger
$22,415,880
GL Receivables
$0
Variance
4 trx
Outside Range
TransactionCustomerSubledger AmountAccounted AmountGl AmountDifference
SampleAcme Industrial$1,240,500.00$1,240,500.00$1,240,500.00Sample
Northwind Trading$842,150.75$842,150.75$842,150.75
SampleGlobex Holdings$96,400.00$96,400.00$96,400.00Sample
Initech LLC$1,005,233.10$1,005,233.10$1,005,233.10
SampleUmbrella Corp$58,720.40$58,720.40$58,720.40Sample
SampleAcme Industrial$1,240,500.00$1,240,500.00$1,240,500.00Sample
AI Analyst · active
reading

The report aligns AR, Subledger Accounting, and GL into one view so each agrees. The Difference column should be zero once the prepare process has run for the period.

flag

Subledger and GL tie to the penny, but 4 transactions post to an account outside the report's range — they will distort the next period's opening balance if left.

root cause & next step

Traced via XLA_AE_HEADERS: the four sit on a misderived distribution account. Correct the AutoAccounting rule or reclass, then re-run the prepare process.

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.

AR_PAYMENT_SCHEDULES_ALLdimensionXLA_AE_HEADERSdimensionGL_BALANCESdimensionRA_CUSTOMER_TRX_ALLfact · one row per source transactionSubledger Amount · Accounted Amount…
●— fact → dimension join
ElementTypeDefinition
AR_PAYMENT_SCHEDULES_ALLdimensiondimension
XLA_AE_HEADERSdimensiondimension
GL_BALANCESdimensiondimension
Subledger Amountmeasuremeasure
Accounted Amountmeasuremeasure
Gl Amountmeasuremeasure
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.

TableReporting columnsSubject areas
RA_CUSTOMER_TRX_ALL5816
AR_PAYMENT_SCHEDULES_ALL326
XLA_AE_HEADERS1619
GL_BALANCESSetup / 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.