The Tax Type Report is the deepest reading surface in the SSP — the guide's confirmed definition: a "drill-down per tax type showing every assessment, payment and adjustment in the period". If the Summary Report is the trial balance and the Balance page the dated position, the Tax Type Report is the general ledger: the transaction-level record of one revenue head, in one currency, over a chosen date range. It is where every question the summary surfaces gets answered — which assessment created this liability, where that payment was allocated, what adjustment moved the balance — and it is the document around which disputes, audits and due-diligence files are actually built.

This lesson teaches the report as a forensic instrument. Its three confirmed line species — assessments, payments, adjustments — map one-to-one onto bodies of law this course has confirmed verbatim: assessments onto the instrument catalogue (the Section 37A(10)–(11) deemed assessment that is your return; Commissioner assessments under Sections 45, 46, 47 and 51 and their VAT Section 31 mirror; audit assessments with their own sequence); payments onto the Single Account's allocation engine (oldest-first within head — so the report is where allocation becomes visible); and adjustments onto everything else that lawfully moves a ledger — Section 48 reductions, VAT Section 44 refund set-offs under subsection (6), penalty and interest postings, and migration entries. Reading the report means attaching every line to its governing provision and its instrument; a line that resists attachment is a finding, not a curiosity.

The lesson builds three working methods on top of the established foundations. The line-audit method: walk a head's period chronologically, instrument file open, classifying each line into the three species and ticking it against its source — the transaction-level completion of the Summary Report lesson's three-way tie. The story reconstruction: because allocation is oldest-first and not intention-based, the report is the only place you can see what actually happened to a payment — the misallocation cascade, the phantom credit, the interest line that explains a residue. And the dispute file: when an assessment must be objected to (30 days, Case Management, established) or an allocation queried (E-Messaging), the exported Tax Type Report is the exhibit that frames the issue — remembering always the evidentiary asymmetry (your export is informal; ZIMRA's Section 79 / VAT Section 42 certified extract is conclusive in recovery — Trek Petroleum, established), which is precisely why the report must be worked while the correcting forums are open.

No statute names the report and no case construes it — stated honestly, as with its sibling surfaces. Its law is the law of its lines. The skill is attachment: every line to a section, every section to an instrument, every instrument to a date and a clock.

Every figure this course has handled ultimately decomposes into Tax Type Report lines. The USD 4,930 balance the Balances lesson decomposed into principal, penalty and interest? Three-plus lines here. The misallocated VAT payment that ate a stale PAYE debt in the Single Account lesson? Two lines — a credit landing and an allocation — in two different heads' reports. The unnotified estimate the Summary Report lesson routed to objection? One assessment line, bearing a reference your instrument file lacks. The report is where the system stops summarising and shows its work.

Why give a report its own lesson? Because transaction-level reading is a different skill from position-reading, and it is the skill the high-stakes moments demand. An objection is not lodged against a balance; it is lodged against an assessment — a specific line with a reference, a date and a 30-day clock. An allocation query does not say "my balance looks wrong"; it says "this payment line of this date and reference was applied to that liability line, and here is why it should not have been". An auditor, a buyer's diligence team, or a Section 57(2) inspection does not want your impression of the account; they want the lines tied to instruments. Position-reading manages the account; line-reading defends it.

The report also completes the course's accounting arc in a satisfying way: it is the surface on which the allocation engine — invoked in every lesson since the Single Account — finally becomes observable. Allocation rules are stated in one confirmed sentence ("oldest debt first within tax type, then by tax type priority"); the Tax Type Report is where you watch the sentence operate on your money, line by line.

The confirmed portal layer

Within Taxpayer Accounting (four pages, established): the Tax Type Report is the "drill-down per tax type showing every assessment, payment and adjustment in the period". Its companions: the Summary Report above it (net per head — the triage layer), and the two instrument pages beside it (Assessment Notices — every liability assessment for the period; Audit Assessment Notices — post-audit assessments "typically with a different sequence number and reference", confirmed). The Searching Transactions lesson established its place in the four-hop trace (hop three: where was the credit allocated?) and the export discipline (portal exports filed monthly with bank statements).

The law of the three line species (established verbatim, organised by line)

Assessment lines. Everything that creates a liability line traces to the instrument catalogue confirmed across this course: the deemed assessment — your own return, served on the later of due date and filing (Section 37A(10)–(11), with the IAB/CF/DNS/TL/Nestlé line); estimated assessments on default (Section 45(1); VAT Section 31(3)–(4), the PIL/VSL/Linda Shoes line); agreed assessments (Section 45(2) — non-objectionable, non-delegable, PPC); additional tax (Section 46 — the greater of 100% or the level-7 fine); additional assessments (Section 47 — six years, lifted entirely by fraud/misrepresentation/wilful non-disclosure); audit assessments surfacing with their own sequence; and the policing rule over all of them — Section 51(2)–(3): notice shall be given and the notice itself must announce the 30-day objection window (Nestlé; Barclays). An assessment line whose notice you cannot produce is the Summary Report lesson's species (b), met here at the line level.

Payment lines. Everything that settles traces to the payment law of the last three lessons: the Single Account landing and oldest-first allocation (confirmed guide rule); currency segregation (Section 37AA; VAT Section 38(4)–(4a) — a payment line can only ever appear in its own currency's report); the FA Section 4B channel whose dated bank confirmation is the external evidence each payment line should tie to; and the Section 72(8) successive-application cascade as the provisional-tax ancestor of what the report displays.

Adjustment lines. The residual species — every lawful movement that is neither assessment nor payment: Section 48 reductions (amended assessments on proved overcharge — non-objectionable, established this run); Section 49 loss adjustments; VAT Section 44(6) set-offs (a refund consumed against arrears appears as movement, not money); Section 44(1)(b)/(4) de minimis carry-forwards (credits rolling between periods); penalty impositions and remissions (Section 46(6); VAT Section 39 and the VSL factors); interest postings (Section 71(2); Fifth Schedule); and migration entries from the pre-SSP era — the Old-Period lesson's territory, reconciled early because VAT Section 42 makes ZIMRA's produced record conclusive except on appeal.

The evidentiary frame (established, applied)

Two rules set the report's legal weight. Your export is informal — useful, dateable, attachable, but at the bottom of the instrument hierarchy (below the ITF 263 and Section 52 certified copies, established). ZIMRA's certified extract is conclusive in recovery (Section 79; VAT Section 42; Trek Petroleum), and Section 78(2) bars challenging an assessment's correctness in the recovery action. The consequence is the same drumbeat as the last two lessons, now at line level: the Tax Type Report is worked while the objection window and the allocation query are alive — afterwards it is merely the record of what you should have contested.

The line-audit method

The transaction-level completion of the monthly reconciliation. For a head and currency under examination:

1. Export the Tax Type Report for the period (dated; filed).
2. Sort chronologically and walk every line, classifying it: assessment / payment / adjustment.
3. Attach each line to its source: assessment lines to instruments in Assessment Notices (or Notifications) and to your filed returns; payment lines to bank confirmations and Payment History entries; adjustment lines to their statutory event (the Section 48 instrument, the set-off computation, the interest section and day-count, the migration note).
4. Flag the unattachable. Three failure signatures: an assessment line with no instrument (species (b) — Section 51 testing, objection clock); a payment line you cannot match to a bank debit (either ZIMRA matched someone else's money to you — rare but real — or your records are incomplete); an adjustment line with no statutory story (demand the explanation via E-Messaging before you build on the balance).
5. Recompute the running balance across the walked period. The arithmetic will agree — the system adds correctly — but the recomputation is what forces every line through your hands, which is the audit.

For a clean head this is minutes; for a disputed or migrated head it is the foundation of every later argument, and it is precisely the "dispute file built from searches" the Searching Transactions lesson's Mukonde scenario described — built here, at line level.

Reading allocation: the report as the engine's flight recorder

Because payments pool and the engine allocates oldest-first within the head, the Tax Type Report is the only place the actual application of your money is visible. Three recurring patterns to recognise on sight:

• The absorbed payment: your payment line lands, and the liability it reduces is older than the one you intended — the misallocation cascade's first frame. The report shows the credit applied against the stale item; your intended period remains part-paid and quietly accrues interest. Detection here, within the month, is an E-Messaging allocation query; detection at clearance season is a crisis.
• The split payment: one payment line satisfies the tail of an old liability and the head of the next — two application entries from one credit. Innocent in itself, but it means your "paid in full" period is actually paid across two ZIMRA postings, and your control account tie must follow the split.
• The interest sandwich: liability line → part payment → interest line → residue. The Balances lesson's decomposition doctrine, observed in the wild: the interest line dates the clock, and paying the residue (principal remnant + accrued interest at today's date) is what finally flattens the sequence.

Cross-head movements — the VAT payment that fed PAYE — require two reports: the credit appears in one head's report as unapplied or absent, and in the other's as an application. This is why the four-hop trace reads Tax Type Reports across heads before concluding anything.

The dispute file: from line to forum

When a line must be fought, the report frames the fight:

• Disputed assessment line → identify the instrument (reference, date); test Section 51(2)–(3); lodge the objection via Case Management within 30 days of the notice, attaching the exported report page that situates the assessment in the account (and your return, where the dispute is an estimate your filing should displace — the back-filing lesson's lane E, never blind). Pay-now obligations apply (Section 69; VAT Section 36, established).
• Disputed allocation → an E-Messaging allocation query: the payment line (date, reference, amount), the bank confirmation, the liability you intended, and the request — re-allocate or explain. Not an objection; no statutory clock; but interest accrues while it pends, so escalate stale queries to Case Management rather than re-sending them.
• Unexplained adjustment → a written explanation request via E-Messaging; if the answer reveals an assessment in disguise, the objection clock arguments begin at notice, which is the point to press (Section 51(3); Barclays).
• In every case: request Section 52 certified copies of the instruments you will fight over, and remember the asymmetry — the file you build now is what stands between you and a conclusive Section 79 extract later.

Periodic uses beyond dispute

Three confirmed-workflow applications worth systematising: the year-end pack — December's exports per head per currency, tied to the control accounts, are the tax balances your financial statements assert (and the schedule your auditor will request first); the due-diligence pack — a buyer prices unexplained lines as risk, so a line-audited report file is directly worth money in a disposal (the Balances lesson's Section 52 discipline, plus this lesson's attachments); and the migration reconciliation — for any head with pre-SSP history, the first Tax Type Report read is the Old-Period lesson's six-step routine performed at line level, early, because Section 42 conclusiveness rewards the side that reconciled first.

Individuals: Rudo reads an interest sandwich

Rudo's income tax (USD) report for the first quarter, after her late fourth QPD of last year:

The line-audit attaches each row: the assessment line to her ITF 12B estimate; the January payment to its bank confirmation; the interest line to Section 71(2) and a 20-day count at the SI 212/2022 rate; the March payment to the residue she paid after her reconciliation found it. Four lines, fully attached, head closed. This is what "clean" looks like at line level — and why her fifteen-minute monthly habit suffices.

SMEs: Pamberi traces the absorbed payment

Pamberi's bookkeeper intends USD 8,000 for January VAT; the ledger later shows VAT part-paid. The VAT-USD Tax Type Report tells the story the intention never sees:

One payment line, split application: an old Section 31 estimate residue — never displaced because the back-filed return was filed after the estimate without an objection — absorbed USD 3,000, leaving January VAT short by exactly that. The dispute file writes itself from the export: objection impossible (the estimate'Section 30 days are long dead — the lesson Pamberi will not need twice), so the cure is forward-looking: the four-hop evidence goes to E-Messaging seeking re-allocation if the old period's return was in fact processed, and failing that the residue is paid and the root cause (file-then-verify on every back-filed period) enters the monthly minute. The report did not fix the problem; it made the problem legible in time to stop its sequel — February's payment is preceded by a balance check, per the New Payment lesson's discipline.

Large corporates: Mukonde's audit-assessment file

An audit assessment of USD 240,000 lands on Mukonde's subsidiary (its own sequence, per the confirmed Audit Assessment Notices page). The group's response file, assembled the same week, is Tax Type Report work end to end: the head's report exported for the full look-back, every line attached; the audit assessment line isolated against its instrument and its Section 51(3) notice (window diarised day one); the payments the auditors claim were never made, evidenced as payment lines tied to FA Section 4B bank confirmations; the adjustments the auditors mischaracterised, tied to their statutory events; and a recomputed running balance demonstrating the account's integrity apart from the disputed line. The objection (Case Management, day 22 of 30) attaches the certified copies requested under Section 52, not just the informal exports — because the group's counsel knows exactly which document will be conclusive if the matter ever reaches recovery, and intends to have matched it first.

As with its sibling surfaces, no reported case construes the Tax Type Report — stated honestly. The lesson's authorities are the established annotation-level lines now read transactionally: the Section 37A deemed-assessment line (IAB, CF, DNS, TL, Nestlé — why a return appears as an assessment line at all); the estimation line (PIL, VSL, Linda Shoes — the Section 31/Section 45 lines that absorb careless payments); PPC 19-HH-755 (agreed assessments, non-delegable); the Section 51 notice line (Nestlé; Barclays — the handle on any assessment line without a produced notice); Trek Petroleum 17-SC-056 (Section 79 conclusiveness — the stakes of the export-vs-extract distinction); and the records line (NYS; PIL on Section 37B/Section 57 — the duty the attached, archived report file discharges). Facts are not narrated in the sources; the cases are cited as markers, as throughout this course.

1. Reading balances off the report without walking the lines. The running balance is arithmetic; the lines are the law. Position-reading on a forensic surface wastes the only thing it offers.
2. Leaving lines unattached. An assessment line without an instrument, a payment line without a bank debit, an adjustment without a statutory story — each is a finding with a clock. "It's probably fine" is how species (b) discrepancies age past their objection window.
3. Tracing a cross-head movement in one head's report. The absorbed payment's other half lives in another report. The four-hop trace reads across heads; single-report conclusions about allocation are guesses.
4. Treating the export as evidence ZIMRA must accept. Your PDF is informal; their certified extract is conclusive (Section 79; Section 42). Build the file from instruments and Section 52 certified copies; use exports to frame, not to prove.
5. Working the report after the forums close. A perfectly line-audited account is archaeology once the 30 days lapse and recovery begins (Section 78(2)). The report's value is front-loaded into the month after each posting.
6. Ignoring migrated lines until they matter. Pre-SSP entries reconcile hardest and harden fastest (Section 42). First read of any migrated head = the Old-Period routine, at line level, now.
7. One export, no archive. The report changes as postings land; only your dated, filed exports prove what the account showed when you acted. Monthly exports with the bank statements — six years (Section 37B; Section 57).

Work through the questions one at a time. Choose an answer and it is graded immediately, with an explanation and the provision it comes from. Your progress is saved, so you can stop and resume.

• The Tax Type Report is the general ledger per head, per currency: "every assessment, payment and adjustment in the period" (confirmed) — the forensic surface beneath the Balance and Summary Report.
• Its three line species each carry their own law: assessments (Section 37A deemed; Sections 45/46/47/51; VAT Section 31; audit sequences — policed by Section 51(2)–(3) notice rules), payments (Single Account oldest-first allocation made visible; FA Section 4B confirmations as the external tie; currency segregation fixing which report a line can inhabit), adjustments (Section 48/Section 49; VAT Section 44(6) set-offs and de minimis carry-forwards; interest and penalty postings; migration entries).
• The line-audit method: export dated → walk chronologically → classify → attach every line to instrument + section → flag the unattachable → recompute the running balance as a forcing device. Unattachable lines are findings with clocks.
• Allocation patterns to recognise on sight: the absorbed payment, the split payment, the interest sandwich — and cross-head movements that require reading two reports.
• Dispute files are built here: assessment lines → 30-day objection via Case Management (Section 51(3) tested; Section 52 certified copies obtained); allocation grievances → E-Messaging queries with payment evidence; unexplained adjustments → written explanation requests.
• Evidentiary humility: your export frames, the Section 52 copy proves your side, the Section 79/Section 42 certified extract is conclusive in recovery (Trek Petroleum) — so the report is worked while the forums are open, and exported monthly into the six-year archive (Section 37B; Section 57).
• Honest boundary: no statute or case touches the report itself; its entire force is the law of its lines, attached one by one.

Line species → law → evidence tie

Allocation patterns and responses

The line-audit loop

flowchart TD
 A[Export Tax Type Report - head, currency, period, dated] --> B[Walk lines chronologically]
 B --> C{Classify line}
 C -->|assessment| D[Attach: instrument + notice + your return]
 C -->|payment| E[Attach: bank confirmation + Payment History]
 C -->|adjustment| F[Attach: section + computation or instrument]
 D --> G{Attached?}
 E --> G
 F --> G
 G -->|yes| H[Tick; next line]
 G -->|no| I[FINDING: species + clock]
 I --> J{Assessment w/o notice?}
 J -->|yes| K[Section 51 test - 30-day objection via Case Mgmt + Section 52 copies]
 J -->|no| L[Allocation query / explanation request via E-Messaging]
 H --> M[Recompute running balance]
 M --> N[File export + attachments - 6-yr archive]

Statutes & sections

• Income Tax Act [Chapter 23:06] — Section 37A(10)–(11) (deemed assessment lines, established); Sections 45/46/47 (estimated, additional-tax and additional-assessment lines, established); Section 51(2)–(3) (notice rules policing assessment lines, established verbatim); Section 52 (certified copies, established); Section 48/Section 49 (reduction/loss adjustment lines, confirmed verbatim this course); Section 71(2) (interest lines, SI 212/2022); Section 78(2)/Section 79 (recovery asymmetry, established); Section 37B (six-year archive, established verbatim); Section 37AA (currency segregation of reports, confirmed verbatim).
• Value Added Tax Act [Chapter 23:12] — Section 31 (estimate lines, established); Section 32/Section 36 (objection; pay-now, established); Section 38(4)–(4a) (currency of payment lines, confirmed verbatim); Section 39 (penalty lines, established); Section 42 (conclusive evidence — migrated records, established); Section 44(1)(b)/(4)/(6) (carry-forward and set-off adjustment lines, confirmed verbatim this run); Section 57 (records, established verbatim); Fifth Schedule (interest, SI 25/2025).
• Finance Act [Chapter 23:04] — Section 4B (the channel behind payment lines; confirmation evidence, confirmed verbatim this run).

Case law

• Trek Petroleum (Pvt) Ltd v ZIMRA 17-SC-056 — Section 79 conclusiveness (established).
• Nestlé Zimbabwe 20-SC-290 / 23-HH-312; Barclays Bank 04-HH-162 — Section 51 notice line (established).
• PIL (Pvt) Ltd v ZIMRA 17-HH-213; VSL; Linda Shoes — estimation/penalty lines (established markers).
• PPC 19-HH-755 — agreed assessments (established).
• NYS v ZIMRA 19-HH-617 — records duty (established).
• No authority exists on the Tax Type Report itself — stated honestly.

ZIMRA guidance

• Comprehensive Guide to the ZIMRA Self-Service Portal (local External Guide) — Taxpayer Accounting module §10 (Tax Type Report defined: "every assessment, payment and adjustment"; Assessment and Audit Assessment Notices pages; Summary Report relationship); Single Account allocation rule (§11.1); monthly workflow (§19.1). The official SSP online help was unreachable this run; report columns, filters and export formats flagged.