Payables Negative Supplier Balance Report

Payables◆ Seeded · Invoices

Lists suppliers with negative balances along with the invoices and credit or debit memo transactions that make up the balance.

Sample build of the Payables Negative Supplier 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

Neg-balance suppliers

-$680K

Net credit held

Aged > 180d

Supplier	Balance	Driving Memo	Invoices	Status
Acme Industrial	$1,240,500.00	Sample	Sample	Open
Northwind Trading	$842,150.75	—	—	Posted
Globex Holdings	$96,400.00	Sample	Sample	Validated
Initech LLC	$1,005,233.10	—	—	Open
Umbrella Corp	$58,720.40	Sample	Sample	Paid
Acme Industrial	$1,240,500.00	Sample	Sample	Open

AI Analyst · active

reading

The report lists suppliers with negative balances and the memos and invoices behind them.

flag

-$680K of supplier credits sit unused, 14 aged past 180 days — money owed back that isn't being recovered.

root cause & next step

Request refunds or apply the credits to new invoices; aged supplier credits are recoverable cash left on the table.

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

AP_SUPPLIER_BALANCES
AP_INVOICES_ALL
POZ_SUPPLIERS

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_INVOICES_ALL	dimension	dimension
POZ_SUPPLIERS	dimension	dimension
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_SUPPLIER_BALANCES	Setup / configuration table — joined for reference, not exposed for analytics
AP_INVOICES_ALL	63	15
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 Negative balances signal unapplied credits; the build adds an actionable recovery list with aging. Irvine rebuilds these on your data.