Payables Trial Balance Report

Payables◆ Seeded · Period close

Lists and subtotals by supplier and liability account all unpaid and partially paid invoices that Payables transferred to the general ledger.

Related Pairs with the flagship Payables to Ledger Reconciliation Report.

Sample build of the Payables Trial Balance 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

$32.00M

Open AP

Liability accounts

$0 diff

Ties to GL

Supplier	Liability Account	Open Balance	Period	Currency
Acme Industrial	1000-2100-000	$1,240,500.00	APR-26	USD
Northwind Trading	1000-5400-000	$842,150.75	MAR-26	USD
Globex Holdings	1000-1410-000	$96,400.00	FEB-26	USD
Initech LLC	2000-2100-000	$1,005,233.10	JAN-26	USD
Umbrella Corp	1000-6300-000	$58,720.40	DEC-25	USD
Acme Industrial	1000-2100-000	$1,240,500.00	APR-26	USD

AI Analyst · active

reading

The report subtotals all unpaid and partially paid invoices by supplier and liability account, tied to GL.

flag

The AP trial balance ties to GL except one liability account where a manual journal posted directly, bypassing Payables.

root cause & next step

Keep manual journals off the AP liability account; a direct GL post is the classic reason the AP subledger won't tie.

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
AP_INVOICE_DISTRIBUTIONS_ALL	dimension	dimension
POZ_SUPPLIERS	dimension	dimension
Open Balance	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.

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.

Table	Reporting columns	Subject areas
AP_PAYMENT_SCHEDULES_ALL	21	2
AP_INVOICE_DISTRIBUTIONS_ALL	59	11
POZ_SUPPLIERS	145	75

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 seeded AP trial balance rarely ties to GL without effort; the build reconciles it to the liability account with a documented variance. Irvine rebuilds these on your data.