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

Payables to Ledger Reconciliation Report

Payables

The Payables to Ledger Reconciliation Report reconciles the accounts-payable subledger to the general ledger liability balance, listing the documents that explain any difference — unaccounted invoices, entries transferred but not posted, and manual journals hitting the liability account. It is the report finance teams fight with most at close.

Used by · AP managers and controllers closing the payables period.Run · At period close, before setting the AP period to Closed.

The question it answers

Does the AP subledger tie to the GL liability account, and if not, which documents explain the gap?

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 Payables to Ledger Reconciliation Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Payables to Ledger Reconciliation Report
Sample build · illustrative
Filters
Business Unit
APAC
Ledger
US Primary
Period
FEB-26
Liability Account
1000-1410-000
$14,902,310
AP Subledger
$14,860,114
GL Liability
$42,196
Variance
9 inv
Unaccounted
DocumentSupplierSubledger 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 stacks the AP subledger balance against the GL liability balance and lists every document that breaks the tie. A clean close shows zero in the Difference column.

flag

Out of balance by $42,196 across 9 invoices — accounted in the subledger but their journals were transferred and not yet posted to GL, the classic close blocker.

root cause & next step

Traced from AP_INVOICE_DISTRIBUTIONS_ALL through XLA_AE_HEADERS to GL_BALANCES: post the open transfer batch and re-run Create Accounting; the variance clears.

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.

AP_INVOICE_DISTRIBUTIONS…dimensionXLA_AE_HEADERSdimensionGL_BALANCESdimensionGL_CODE_COMBINATIONSdimensionAP_INVOICES_ALLfact · one row per source transactionSubledger Amount · Accounted Amount…
●— fact → dimension join
ElementTypeDefinition
AP_INVOICE_DISTRIBUTIONS_ALLdimensiondimension
XLA_AE_HEADERSdimensiondimension
GL_BALANCESdimensiondimension
GL_CODE_COMBINATIONSdimensiondimension
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.
Payables 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
AP_INVOICES_ALL6315
AP_INVOICE_DISTRIBUTIONS_ALL5911
XLA_AE_HEADERS1619
GL_BALANCESSetup / configuration table — joined for reference, not exposed for analytics
GL_CODE_COMBINATIONS761
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.