Audit Packet: The Evidence Export That Defends the Study
The audit packet in Quartyl: the exportable evidence file for a proceeding — the ledger, the trail, the captures and the snapshots in one deliverable, with retention.
Definition
The audit packet is Quartyl’s exportable evidence file for a
proceeding — the study’s defence deliverable: the [evidence ledger]
(/docs/glossary/evidence-ledger) (the immutable, append-only record of
every evidence event — the captures, the snippets, the snapshots, the
source), the [audit trail]
(/docs/product/audit-trails/audit-trails-overview) (the study’s chronology
— the state changes, the reviews, the sign-offs, the overrides, the
access), and the context (the study’s parameters, the
[accept-reject matrix]
(/docs/glossary/accept-reject-matrix), the benchmark’s range) — packaged
in one export (the ZIP, the evidence file) for the proceeding (the
TPO examination, the scrutiny, the [appeal]
(/docs/glossary/itat), the MAP submission). The packet is the delivery of
the [evidence ledger]
(/docs/glossary/evidence-ledger)’s record — the ledger is the record
(append-only, the events in sequence), the packet is the delivery (the
export, the file the authority / the counsel / the appeal reads). The
content is the [defending the accept-reject matrix]
(/docs/benchmarking/defending-accept-reject) guide’s standing list: the
per-company evidence (the captures, the source passages), the decision
record (the accept/reject/flag, the rationale), the override record (the
[ground-truth registry]
(/docs/glossary/ground-truth-registry) linkage, the ai_reason_id), the
activity record (the chronology, the sign-offs), and the benchmark (the
range, the comparables, the adjustments). The retention (the packet’s
storage, the study’s evidence life — the [evidence repository]
(/docs/product/evidence/evidence-repository) retention management) is the
packet’s governance (the retention period, the purge, the
[contemporaneous documentation]
(/docs/glossary/contemporaneous-documentation-30day) duty the packet’s
shelf life serves).
The audit packet, in one export:
1. The evidence ledger (the immutable record — the captures, the snippets, the snapshots, the source, in sequence)
2. The audit trail (the study’s chronology — the state changes, the reviews, the sign-offs, the overrides, the access)
3. The context (the study’s parameters, the accept-reject matrix, the benchmark’s range)
4. The export (the ZIP, the evidence file — for the proceeding: the TPO, the appeal, the MAP)
| The element | The content |
|---|---|
| The evidence ledger | The immutable, append-only record — the captures (the screenshots, the snippets, the source extracts), the snapshots (the point-in-time data state), the source (the URL, the filing, the database record) — in sequence, with the identity and the time |
| The audit trail | The study’s chronology — the state changes, the reviews, the sign-offs, the overrides (the rationale, the ground-truth registry linkage), the access log — the activity record |
| The context | The study’s parameters, the accept-reject matrix (the per-company decisions, the reasons, the sources), the benchmark (the range, the comparables, the adjustments) |
| The export | The ZIP, the evidence file — for the proceeding (the TPO examination, the appeal, the MAP submission) — the retention the governance |
The working read (the defending the
accept-reject guide and the
audit defense): the audit packet is
the defence deliverable — the file the TPO, the counsel, and the appeal
read as the work as it happened (the ledger’s immutability — the
append-only, the sequence — the forensic property, the work not
reconstructed at audit time). The [evidence ledger]
(/docs/glossary/evidence-ledger) is the packet’s core (the evidence
record — the captures, the snapshots, the source); the [audit trail]
(/docs/product/audit-trails/audit-trails-overview) is the packet’s
activity (the chronology — the state changes, the reviews, the
sign-offs, the overrides); the context (the parameters, the matrix, the
benchmark) is the packet’s frame (the study the evidence is for).
The [ground-truth registry]
(/docs/glossary/ground-truth-registry) linkage (the ai_reason_id — the
AI reason, the override, the cross-reference) is the packet’s AI
control evidence (the [AI controls guide]
(/docs/tp-software/ai-in-transfer-pricing)’s Layer 4 — the record control,
the audit trail — the AI’s runs, the per-company evidence, the human
decisions, the overrides, in sequence). The retention (the evidence
repository retention
management — the retention period, the purge) is the packet’s governance
(the [contemporaneous documentation]
(/docs/glossary/contemporaneous-documentation-30day) duty the shelf life
serves — the evidence available for the proceeding, the retention the
duty the packet’s life).
Example
The study (the benchmarking, the screening) is examined (the TPO, the scrutiny — the proceeding). The audit packet (the ZIP, the export) carries:
| The section | The content |
|---|---|
| The evidence ledger | The immutable record (the captures — the comparable’s business description, the website snippet, the URL, the date; the snapshots — the comparable’s financials, the profile, the ratios, the data state at the screening; the source — the URL, the filing, the database record) — in sequence, with the identity and the time (the actor, the timestamp, the source) |
| The decisions | The accept/reject/flag (the per-company decision, the AI-assisted screening outcome, the human override, the rationale) — the accept-reject matrix the decision record |
| The overrides | The override (where the reviewer overrode the AI’s recommendation, the new event — the override, the rationale, the identity, the time) — the ground-truth registry linkage (the ai_reason_id) |
| The audit trail | The chronology (the state changes, the reviews, the sign-offs, the access log) — the activity record (the audit trails module) |
| The context | The study’s parameters (the method, the PLI, the years, the tested party), the benchmark (the range, the comparables, the adjustments) — the frame the evidence is for |
The proceeding (the TPO) reads the packet (the evidence the ledger, the activity the trail, the frame the context) — the work as it happened (the append-only, the sequence, the source) — the defending the accept-reject record, the audit defense the proceeding’s file. The retention (the [evidence repository] (/docs/product/evidence/evidence-repository) retention management — the period, the purge) governs the packet’s shelf life (the contemporaneous documentation duty, the proceeding’s availability).
See also
- Evidence Ledger
- Defending Your Accept-Reject Matrix
- Ground-Truth Registry
- AI in Transfer Pricing — Use Cases, Controls and Governance
FAQ
What is the difference between the audit packet and the evidence ledger? The evidence ledger is the record (the immutable, append-only record of every evidence event — the captures, the snapshots, the source, in sequence); the audit packet is the delivery (the export — the ZIP, the evidence file — that carries the ledger, plus the [audit trail] (/docs/product/audit-trails/audit-trails-overview) (the chronology) and the context (the parameters, the matrix, the benchmark), for the proceeding). The ledger is the what (the evidence, the record); the packet is the for whom (the proceeding, the delivery) — the ledger the packet’s core, the packet the ledger’s export. The [evidence ledger term] (/docs/glossary/evidence-ledger) carries the record’s immutability (the append-only, the sequence, the source); this term carries the export (the ZIP, the content, the retention).
What is in the audit packet — the content list? The packet carries three layers: the evidence (the [evidence ledger] (/docs/glossary/evidence-ledger) — the captures, the snippets, the snapshots, the source, in sequence, with the identity and the time); the activity (the [audit trail] (/docs/product/audit-trails/audit-trails-overview) — the state changes, the reviews, the sign-offs, the overrides (the rationale, the ground-truth registry linkage), the access log); and the context (the study’s parameters, the [accept-reject matrix] (/docs/glossary/accept-reject-matrix) — the per-company decisions, the reasons, the sources; the benchmark — the range, the comparables, the adjustments). The proceeding (the TPO, the appeal, the MAP) reads the three layers (the evidence, the activity, the context) — the work as it happened, the defence the packet’s delivery. The defending the accept-reject guide’s standing list is the packet’s content (the per-company evidence, the decision record, the override record, the benchmark).
What is the retention, and why does the audit packet have a shelf life? The retention is the [evidence repository] (/docs/product/evidence/evidence-repository)’s retention management — the retention period (the study’s evidence life — the period the evidence is retained, the purge the expiry), the packet’s governance. The shelf life serves the [contemporaneous documentation] (/docs/glossary/contemporaneous-documentation-30day) duty (the evidence available for the proceeding — the TPO, the appeal, the MAP — the retention the duty the packet’s availability). The retention is the packet’s governance (the period, the purge, the evidence repository management) — the evidence retained for the proceeding, the purged on the expiry, the retention the duty the packet’s life.
Run the screens as a study, not a spreadsheet
Quartyl applies the method, PLI and screening steps above as a pipeline — and keeps a documented reason for every exclusion.
Related docs
Evidence Ledger: The Immutable Record of the Study’s Evidence
The evidence ledger in Quartyl: the immutable, append-only record of every evidence event — the captures, the snippets, the snapshots and the source, per study.
Read docDefending Your Accept-Reject Matrix Before the TPO (and IRS)
What the TPO and IRS actually scrutinize in the Accept-Reject matrix: the evidence file structure, the override rationale, the consistency tests, and the questions to rehearse.
Read doc