Withholding Tax Report

Transaction Tax◆ Seeded · Withholding

Tax withheld from supplier payments by withholding type and supplier — the basis for withholding remittance and certificates.

Run note · Data latency Several tax reports read the Tax Reporting Ledger extract rather than live transaction tables — run the extract first or the report returns stale or empty results.

Sample build of the Withholding Tax 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

180

Suppliers

$210K

Withheld

Missing tax ID

Supplier	Withholding Type	Taxable	Rate	Withheld
Acme Industrial	Standard	Sample	Sample	Sample
Northwind Trading	Corporate	—	—	—
Globex Holdings	Standard	Sample	Sample	Sample
Initech LLC	Default	—	—	—
Umbrella Corp	Standard	Sample	Sample	Sample
Acme Industrial	Standard	Sample	Sample	Sample

AI Analyst · active

reading

The report summarizes tax withheld from supplier payments by withholding type and supplier.

flag

Seven suppliers were withheld without a tax ID on file — the remittance and certificates can't be filed correctly for them.

root cause & next step

Capture the tax IDs; withholding without an ID often forces a higher rate and blocks the certificate.

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_AWT_TEMP_DISTRIBUTIONS_ALL
AP_INVOICES_ALL
POZ_SUPPLIERS_V
ZX_RATES_B

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_V	dimension	dimension
ZX_RATES_B	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.

Transaction Tax 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_AWT_TEMP_DISTRIBUTIONS_ALL	Setup / configuration table — joined for reference, not exposed for analytics
AP_INVOICES_ALL	63	15
POZ_SUPPLIERS_V	2	24
ZX_RATES_B	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 Localization adds the jurisdiction's certificate format and the tax-authority remittance tie-out. Irvine rebuilds these on your data.