Update and Report Income Tax Details

Payables◆ Seeded · Income tax & withholding

Updates or reports income tax type and income tax region on invoice distributions used for US 1099 reporting.

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 Update and Report Income Tax Details — 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

2,100

Distributions

180

Updated

Still missing

Supplier	Invoice	Distribution	Income Tax Type	Region	Action
Acme Industrial	Sample	Sample	Standard	Sample	Sample
Northwind Trading	—	—	Corporate	—	—
Globex Holdings	Sample	Sample	Standard	Sample	Sample
Initech LLC	—	—	Default	—	—
Umbrella Corp	Sample	Sample	Standard	Sample	Sample
Acme Industrial	Sample	Sample	Standard	Sample	Sample

AI Analyst · active

reading

The report updates or reports income tax type and region on the distributions used for 1099 reporting.

flag

After the update, 60 distributions still have no income tax type — they remain outside the 1099 totals.

root cause & next step

Source the income tax type at invoice entry, not at year-end; a bulk fix catches most, but the remainder needs upstream defaulting.

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_INCOME_TAX_TYPES	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_INCOME_TAX_TYPES	2	5

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 The seeded mass-update is blunt; teams add rule-based assignment by supplier/category before running it. Irvine rebuilds these on your data.