Tax Audit Trail Report

Transaction Tax◆ Seeded · Audit

A full audit trail of tax on transactions — taxable and tax amount, rate, recovery, and the accounts — for tax-authority audit and internal review.

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 Audit Trail 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

12,800

Transactions

$3.40M

Tax

Manual overrides

Transaction	Date	Tax Rate	Taxable	Tax	Recovery	Account
Sample	2026-04-30	Sample	Sample	Sample	Sample	1000-2100-000
—	2026-03-31	—	—	—	—	1000-5400-000
Sample	2026-02-28	Sample	Sample	Sample	Sample	1000-1410-000
—	2026-01-31	—	—	—	—	2000-2100-000
Sample	2025-12-31	Sample	Sample	Sample	Sample	1000-6300-000
Sample	2026-04-30	Sample	Sample	Sample	Sample	1000-2100-000

AI Analyst · active

reading

The report lists the full tax trail per transaction — rate, recovery, and accounts — for audit.

flag

A cluster of transactions carries manual tax overrides — tax entered by hand rather than determined by the rules, which auditors scrutinize.

root cause & next step

Investigate why the rules didn't determine tax for those; frequent manual overrides signal a gap in the tax configuration.

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_LINES
ZX_REC_NREC_DIST
AP_INVOICES_ALL
RA_CUSTOMER_TRX_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_REC_NREC_DIST	dimension	dimension
AP_INVOICES_ALL	dimension	dimension
RA_CUSTOMER_TRX_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_LINES	Setup / configuration table — joined for reference, not exposed for analytics
ZX_REC_NREC_DIST	Setup / configuration table — joined for reference, not exposed for analytics
AP_INVOICES_ALL	63	15
RA_CUSTOMER_TRX_ALL	58	16

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 Rebuilt as a searchable transaction-level tax trail with drill from return line to source document. Irvine rebuilds these on your data.