Netting Settlement Listing

Payables◆ Seeded · Netting

Lists the transactions netted for a specific netting settlement, in spreadsheet format.

Related The spreadsheet companion to the Netting Settlement Report.

Sample build of the Netting Settlement Listing — 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

420

Transactions

$4.20M

Net settled

Trading partners

Trading Partner	Transaction	Type	Amount	Net Position
Sample	Sample	Standard	$1,240,500.00	Sample
—	—	Corporate	$842,150.75	—
Sample	Sample	Standard	$96,400.00	Sample
—	—	Default	$1,005,233.10	—
Sample	Sample	Standard	$58,720.40	Sample
Sample	Sample	Standard	$1,240,500.00	Sample

AI Analyst · active

reading

The report lists the netted transactions in spreadsheet form for analysis.

flag

One partner's listing shows AR far exceeding AP — netting barely reduces a balance they mostly owe you, so collection still matters.

root cause & next step

Use netting for genuinely two-way partners; a lopsided netting relationship is really a collection problem wearing a netting label.

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
RA_CUSTOMER_TRX_ALL	dimension	dimension
NETTING_TRANSACTIONS	dimension	dimension
Amount	measure	measure
Net Position	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_INVOICES_ALL	63	15
RA_CUSTOMER_TRX_ALL	58	16
NETTING_TRANSACTIONS	Setup / 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.

Customization note Usually combined with the PDF settlement report into one reconciled netting workbook. Irvine rebuilds these on your data.