Tax Box Allocation Report

Transaction Tax◆ Seeded · Tax box return

Transactions allocated to the tax boxes of a tax return, mapping each taxable and tax amount to the box it reports in, so the return ties to the underlying transactions.

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 Tax Box Allocation 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

Tax boxes

$3.40M

Allocated

$26K

Unallocated

Tax Box	Transaction	Taxable	Tax	Return Period
Sample	Sample	Sample	Sample	APR-26
—	—	—	—	MAR-26
Sample	Sample	Sample	Sample	FEB-26
—	—	—	—	JAN-26
Sample	Sample	Sample	Sample	DEC-25
Sample	Sample	Sample	Sample	APR-26

AI Analyst · active

reading

The report maps each taxable and tax amount to the box it reports in on the return.

flag

$26K of tax maps to no box, so it won't appear on the return — understating either the liability or the reclaim.

root cause & next step

Complete the box-allocation rules; an unallocated transaction is a return line silently missing.

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

ZX_REPORTING_TYPES_B
ZX_LINES
RA_CUSTOMER_TRX_ALL
AP_INVOICES_ALL

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
ZX_LINES	dimension	dimension
RA_CUSTOMER_TRX_ALL	dimension	dimension
AP_INVOICES_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.

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
ZX_REPORTING_TYPES_B	Setup / configuration table — joined for reference, not exposed for analytics
ZX_LINES	Setup / configuration table — joined for reference, not exposed for analytics
RA_CUSTOMER_TRX_ALL	58	16
AP_INVOICES_ALL	63	15

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 Box allocation rules are country-specific; the build encodes them once and validates that every transaction maps to a box. Irvine rebuilds these on your data.