AP Vendor Financing Batch Creation Inquiry Report

Payables

An inquiry into vendor-financing (supply-chain finance) batches — which approved invoices were offered for early payment or financing, the discount taken, and the financed amount by supplier and bank.

Sample build of the AP Vendor Financing Batch Creation Inquiry Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Sample build · illustrative

Filters

Business Unit

APAC

Currency

USD

Supplier Name

Globex Holdings

420

Financed invoices

$6.10M

Financed value

$92K

Discount captured

Supplier	Invoice	Original Due	Financed Amount	Discount	Settlement Date
Acme Industrial	Sample	Sample	$1,240,500.00	Sample	2026-04-30
Northwind Trading	—	—	$842,150.75	—	2026-03-31
Globex Holdings	Sample	Sample	$96,400.00	Sample	2026-02-28
Initech LLC	—	—	$1,005,233.10	—	2026-01-31
Umbrella Corp	Sample	Sample	$58,720.40	Sample	2025-12-31
Acme Industrial	Sample	Sample	$1,240,500.00	Sample	2026-04-30

AI Analyst · active

reading

The report reads financed invoices and their settlement against AP payments, by supplier and bank.

flag

A block of invoices was financed at a discount rate higher than the company's cost of capital — the financing cost more than holding the cash would have.

root cause & next step

Set the financing-discount threshold to the cost of capital so the program only finances invoices where early payment actually pays.

Illustrative data. The live interactive version — drill-through, filters, export, and the AI Analyst — runs on your warehouse. See it live →

The SQL behind this report is not published. Its logic is one organisation's own setup, so it would not run anywhere else. The tables it reads are listed below, and the warehouse model shows how the same data lands in your warehouse.

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 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_PAYMENTS_ALL	dimension	dimension
AP_CHECKS_ALL	dimension	dimension
POZ_SUPPLIERS_V	dimension	dimension
POZ_SUPPLIER_SITES_ALL_M	dimension	dimension
Financed Amount	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
AP_INVOICE_PAYMENTS_ALL	22	2
AP_CHECKS_ALL	44	6
POZ_SUPPLIERS_V	2	24
POZ_SUPPLIER_SITES_ALL_M	179	56

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.