Payables Matched and Modified Receipts Report

Payables◆ Seeded · Invoices

Identifies receipts that were modified after invoice matching.

Sample build of the Payables Matched and Modified Receipts 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

140

Modified receipts

$320K

Value impact

$90K

Understated liability

Receipt	Invoice	Original Qty	Modified Qty	Difference	Supplier
Sample	Sample	120	120	Sample	Acme Industrial
—	—	45	45	—	Northwind Trading
Sample	Sample	860	860	Sample	Globex Holdings
—	—	12	12	—	Initech LLC
Sample	Sample	305	305	Sample	Umbrella Corp
Sample	Sample	120	120	Sample	Acme Industrial

AI Analyst · active

reading

The report identifies receipts modified after they were matched to an invoice.

flag

$90K of receipts were reduced after matching — the invoice may have matched to a quantity that no longer exists.

root cause & next step

Review post-match receipt changes; a receipt modified after matching can leave the liability over- or under-stated.

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
RCV_TRANSACTIONS	dimension	dimension
AP_INVOICES_ALL	dimension	dimension
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_INVOICE_DISTRIBUTIONS_ALL	59	11
RCV_TRANSACTIONS	25	31
AP_INVOICES_ALL	63	15

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 Frequently extended with the quantity/price variance and the receiving correction trail. Irvine rebuilds these on your data.