US 1099 Report

Payables◆ Seeded · Income tax & withholding

Reports total US 1099 miscellaneous payments for a 1099 supplier and generates 1099 forms for each tax reporting entity.

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 US 1099 Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

US 1099 Report

Sample build · illustrative

Filters

Period

FEB-26

Ledger

US Primary

Currency

USD

320

1099 suppliers

$6.40M

Reportable

TIN mismatch

Supplier	1099 Type	Box	Reportable Amount	Tin Status
Acme Industrial	Standard	Sample	$1,240,500.00	Open
Northwind Trading	Corporate	—	$842,150.75	Posted
Globex Holdings	Standard	Sample	$96,400.00	Validated
Initech LLC	Default	—	$1,005,233.10	Open
Umbrella Corp	Standard	Sample	$58,720.40	Paid
Acme Industrial	Standard	Sample	$1,240,500.00	Open

AI Analyst · active

reading

The report totals reportable 1099 payments per supplier and generates the forms per reporting entity.

flag

12 suppliers have a TIN that doesn't match IRS records — 1099s that will reject and may trigger backup withholding.

root cause & next step

Run TIN matching and correct the 12 before filing; a mismatched TIN is the most common 1099 rejection and a penalty risk.

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
POZ_SUPPLIERS	dimension	dimension
AP_INCOME_TAX_TYPES	dimension	dimension
Reportable 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
POZ_SUPPLIERS	145	75
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 Year-end 1099 almost always needs cleanup tooling for missing/incorrect income-tax types before forms are generated. Irvine rebuilds these on your data.