Payables Withholding Tax by Tax Authority Report

Payables◆ Seeded · Income tax & withholding

Lists withholding for tax codes assigned to a tax authority.

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.

Run note · Year-end Year-end 1099 and withholding output depends on clean income-tax-type and supplier data. Run the exception reports and correct first, or forms generate with gaps.

Sample build of the Payables Withholding Tax by Tax Authority Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Payables Withholding Tax by Tax Authority Report

Sample build · illustrative

Filters

Period

FEB-26

Ledger

US Primary

Currency

USD

Tax authorities

$210K

Withheld

$38K

Unremitted

Tax Authority	Tax Code	Suppliers	Taxable	Withheld
Sample	Sample	Acme Industrial	Sample	Sample
—	—	Northwind Trading	—	—
Sample	Sample	Globex Holdings	Sample	Sample
—	—	Initech LLC	—	—
Sample	Sample	Umbrella Corp	Sample	Sample
Sample	Sample	Acme Industrial	Sample	Sample

AI Analyst · active

reading

The report lists withholding for the tax codes assigned to each tax authority.

flag

$38K was withheld but not yet remitted to one authority — a withholding liability past its remittance date.

root cause & next step

Remit on schedule; withheld tax held past its due date is a penalty exposure, not working capital.

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_AWT_BUCKETS_ALL	dimension	dimension
ZX_LINES_V	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
AP_AWT_BUCKETS_ALL	Setup / configuration table — joined for reference, not exposed for analytics
ZX_LINES_V	12	1

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 Often re-cut to match the exact remittance file each authority requires. Irvine rebuilds these on your data.