Payment Audit by Voucher Number Report

Payables◆ Seeded · Payments

Lists payments with assigned sequential voucher numbers for audit.

Sample build of the Payment Audit by Voucher Number 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

6,200

Payment vouchers

no gaps

Sequential

Gaps

Voucher No	Payment	Supplier	Amount	Status
1001	Sample	Acme Industrial	$1,240,500.00	Open
1002	—	Northwind Trading	$842,150.75	Posted
1003	Sample	Globex Holdings	$96,400.00	Validated
1004	—	Initech LLC	$1,005,233.10	Open
1005	Sample	Umbrella Corp	$58,720.40	Paid
1001	Sample	Acme Industrial	$1,240,500.00	Open

AI Analyst · active

reading

The report lists payments with their sequential voucher numbers for audit.

flag

Four gaps in the payment voucher sequence — voided or deleted payments that should be documented.

root cause & next step

Confirm each gap is a void with a reason; an unexplained payment-sequence gap is an audit and fraud-control flag.

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_PAYMENTS_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_CHECKS_ALL	44	6
AP_INVOICE_PAYMENTS_ALL	22	2

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 Like the invoice audit, the real need is sequence gap/duplicate detection layered on top. Irvine rebuilds these on your data.