The Summary Report is one of the four pages of the SSP's Taxpayer Accounting module, and the guide defines it in one confirmed sentence: "the balance summary report — net balance per tax type for the date range". Where the Balance page answers "what do I owe right now?" and the Tax Type Report answers "what happened, line by line?", the Summary Report answers the accountant's question: "per revenue head, where does ZIMRA's trial balance stand for this period?" The guide then assigns it a job, also confirmed: "Use the Summary Report monthly to reconcile the taxpayer's accounting records to the SSP. Discrepancies almost always indicate either (a) an unallocated payment that needs ZIMRA to allocate, or (b) an assessment the taxpayer hasn't received notice of and may want to object to." That sentence is the thesis of this lesson: the Summary Report is not a statement to glance at — it is the monthly reconciliation instrument, and the two discrepancy species it surfaces each have their own legal remedy with its own clock.

This lesson builds the reconciliation methodology in full: how to construct tax control accounts in your own ledger (one per head, per currency) so there is something to reconcile to; the three-way tie between your control accounts, the Summary Report, and the underlying instruments (returns filed, payments made, assessment notices received); and the routing table for every class of difference — unallocated payments to an E-Messaging allocation query, unnotified assessments to the Section 51(3)/Section 62 objection machinery (the notice itself must announce the 30-day window — Barclays Bank 04-HH-162, established), timing differences to the diary, and interest accruals to the daily clocks (Section 71(2); VAT Fifth Schedule).

The legal frame is established and re-applied rather than new: Section 37B of the Income Tax Act and Section 57 of the VAT Act make six-year, reconciliation-grade record-keeping a statutory duty, and the evidentiary asymmetry doctrine (Section 79 certified extracts conclusive in recovery; Section 78(2) correctness unchallengeable in the recovery action — Trek Petroleum 17-SC-056) means a discrepancy you fail to surface and dispute in time hardens into a number you can no longer argue with. The Summary Report read monthly is therefore the taxpayer's early-warning radar: the cheapest possible audit of what ZIMRA believes, run before ZIMRA acts on its beliefs.

There is, honestly stated, no statute and no case law about the Summary Report itself — it is an administrative rendering of the Single Account. Its law is borrowed: the deemed-assessment architecture that populates it (Section 37A), the allocation engine that shuffles it, the notice provisions that police what may appear in it, and the records duties that demand you keep your own version. The skill it teaches is the most transferable in this course: never let ZIMRA's ledger and yours drift apart for more than a month.

Every prior lesson in the accounting arc has assumed a habit this lesson finally teaches properly. The Single Account lesson prescribed "reconcile monthly"; the Balances lesson built the reading flow; the Searching Transactions lesson built the trace. But reconciliation is not reading, and it is not tracing — it is the disciplined comparison of two independently maintained records of the same facts, with every difference explained, routed, and cleared. The Summary Report exists to be one side of that comparison.

Why a summary rather than detail? Because reconciliation works top-down. You do not begin by comparing ten thousand ledger lines; you begin by comparing one net figure per tax head per currency against your own control account for that head and currency. Heads that agree are closed in seconds. Heads that disagree get the drill-down (Tax Type Report) and the trace (Payment History, Single Account Transactions). The Summary Report is the triage layer that makes monthly reconciliation affordable — which is precisely why the guide assigns the monthly job to it and not to the detail reports.

The stakes are asymmetric, which is what makes the habit professional rather than clerical. If your ledger says you owe less than ZIMRA's and you do nothing, the difference ripens: interest compounds daily, the ITF 263 grid fails at the next clearance run, and if recovery proceedings ever come, Section 78(2) makes the assessment's correctness unchallengeable in that action while Section 79 makes ZIMRA's certified extract conclusive evidence (Trek Petroleum (Pvt) Ltd v ZIMRA 17-SC-056, established). If ZIMRA's ledger says you owe less than yours, you are sitting on an unbooked exposure that will surface at the worst moment — an audit, a due-diligence, a clearance application. Either way, the month you skip reconciliation is the month drift begins.

The confirmed portal layer

The Taxpayer Accounting module's four pages (established in the Single Account and Balances lessons; restated as the report's habitat):

• Assessment Notices — every liability assessment raised for the date period;
• Audit Assessment Notices — post-audit assessments, "typically with a different sequence number and reference";
• Summary Report — "the balance summary report — net balance per tax type for the date range" (confirmed);
• Tax Type Report — "drill-down per tax type showing every assessment, payment and adjustment in the period" (confirmed).

And the confirmed operating instruction: monthly reconciliation against the taxpayer's accounting records, with discrepancies "almost always" one of two species — an unallocated payment, or an unnotified assessment. The confirmed monthly workflow (§19.1) places the work "between 25th and end of month": "review Taxpayer Accounting → Summary Report against the company's own ledger; raise any allocation queries via E-Messaging."

The borrowed law (established, applied)

No section of any Act mentions the Summary Report. Its legal force is assembled from provisions this course has already confirmed verbatim, each of which this lesson applies to the reconciliation:

• What populates it: the deemed-assessment architecture — your return is the assessment (Section 37A(10)–(11)); Commissioner assessments under Sections 45–47 and their VAT Section 31 mirror; payments via the Single Account and its oldest-first allocation; interest accruing automatically (Section 71(2); VAT Fifth Schedule per SI 25/2025).
• What polices what may appear in it: Section 51(2) — notice of an assessment shall be given (Nestlé, established); Section 51(3) — the notice itself must announce the 30-day objection window (Barclays Bank 04-HH-162, established). A liability line in the Summary Report for which no notice arrived is exactly discrepancy species (b), and the missing notice is the point to press.
• What obliges you to keep the other side of the comparison: ITA Section 37B(1) — six years of English-language books from the date of last entry, expressly including "bank statements and deposit slips"; Section 37B(2) penalty — the greater of a level-7 fine or 10% of taxable income (established verbatim). VAT Section 57(1)–(4) — supplies records, systems documentation per tax period, print-out rule, six years, alternative-form authorisation excluding ledgers/cash books/journals (established verbatim, PIL annotated). A reconciliation file is not a nicety; it is what these sections look like in practice.
• What makes timeliness existential: the evidentiary asymmetry — Section 79 / VAT Section 42 certified extracts conclusive; Section 78(2) correctness unchallengeable in recovery (Trek Petroleum); the only correcting forums are the 30-day objection and the allocation query, both of which assume you noticed the discrepancy while the clock was alive.
• What the report feeds: the ITF 263 compliance grid runs the same data — every head, returns and payments, 12–24-month look-back (established). A clean monthly reconciliation is a pre-passed clearance check; the Summary Report panel is the cheapest rehearsal for the Compliance Status panel.

Step zero: build something to reconcile against

Reconciliation requires two independent records. ZIMRA maintains theirs; most reconciliation failures begin with the taxpayer not truly maintaining one. The fix is the tax control account: in your general ledger, one liability account per revenue head per currency — PAYE-USD, PAYE-ZWG, VAT-USD, VAT-ZWG, income tax/QPD-USD, the withholding heads as applicable. Operating rules:

• Credit the control account when the liability arises (the P2 accrual at payroll close; the VAT 7 net position at period close; the QPD when the estimate fixes it) — dated the statutory event, not the filing;
• Debit it when payment leaves (dated the bank debit — the e-banking lesson's irrevocable-debit doctrine supplies the date);
• post interest and penalties only from instruments or computed accruals you can tie to a section — never as balancing figures;
• and never, ever, post a "plug" to force agreement. An unexplained difference is information; a plug is the destruction of information.

Done this way, each control account's closing balance is your version of the Summary Report's net-per-head figure, and the monthly comparison becomes mechanical.

The three-way tie

A professional reconciliation ties three things, not two:

1. Your control account (per head, per currency) — what your books say;
2. The Summary Report (same head, same currency, same date range) — what ZIMRA's ledger says;
3. The instrument file — the returns filed (Submitted Tax Returns exports), payments made (bank confirmations + Payment History), and assessment notices received (Notifications/Taxpayer Accounting) for the period.

The third leg is what converts "the numbers differ" into "here is why they differ". Every reconciling item must be attached to an instrument or to the absence of one — and "the absence of one" is itself the finding (a payment with no landing; a liability with no notice).

The difference taxonomy and its routing table

The guide names the two big species; practice adds three more. Every reconciling item falls into one of five classes, each with its route and its clock:

1. Unallocated or misallocated payment (your debit, no SSP credit — or a credit allocated somewhere unexpected). Route: the four-hop trace (Payment History → Single Account Transactions → Tax Type Report), then an E-Messaging allocation query with the bank confirmation and exports attached. Clock: none statutory, but interest accrues on whatever the payment failed to settle — move within days.
2. Unnotified assessment (an SSP liability line your books have never seen). Route: pull the instrument from Assessment Notices / Audit Assessment Notices; test it against Section 51(2)–(3) (was notice given? did it announce the objection window?); then either book it (it is right) or object via Case Management within 30 days (it is wrong). Clock: the harshest in the system — 30 days from the notice, and Barclays gives you the argument where the notice never announced the window.
3. Timing difference (you accrued at the statutory event; the SSP posts at processing — or your payment of the 30th lands on the 1st). Route: list, date, and let it clear next month. Clock: none — but a "timing difference" that survives two reconciliations is a misallocation wearing a disguise; reclassify and trace it.
4. Interest/penalty accrual gap (ZIMRA's figure includes daily interest your books accrue monthly, or a penalty instrument you have not booked). Route: recompute from the Section (Section 71(2); Fifth Schedule rates), book the accrual, and if the penalty is disputable, remember it has its own contest (the VSL remission line, established) on its own instrument.
5. Your error (mis-posted control entry, wrong currency column, missed accrual). Route: correct your books. The reconciliation that never finds your own errors is not being done honestly.

The monthly routine, end to end

Slotting into the confirmed monthly workflow (after the 25th, before month-end):

1. Export the Summary Report per currency for the month (and file it — it is your dated snapshot of ZIMRA's position; the Balances lesson's "a balance is only meaningful with its date" applies to reports too).
2. Compare each head/currency net against the matching control account. Agreeing heads: close, initial, done.
3. Drill each disagreeing head into the Tax Type Report; build the difference list; classify each item into the five classes.
4. Route each item per the table — allocation queries fired, objections diarised and lodged, accruals booked, own errors corrected.
5. Minute the reconciliation: one page per month, per taxpayer — differences found, classes, routes, clearance status of last month's items. This minute is Section 37B-grade evidence: it proves vigilance (relevant to "just cause" and remission arguments, established) and it is the working paper an auditor, a buyer's due-diligence team, or your own successor will ask for.
6. Escalate the stale: any item surviving two cycles gets a named owner and, if it is a dispute, the formal channel (objection/Case Management) rather than another month of E-Messaging patience.

The whole routine, for a compliant SME, is an hour a month. Its absence is how a USD 3,000 phantom debt sits unnoticed for a year, eats a VAT payment via oldest-first allocation, fails a clearance run in renewal season, and surfaces as a 30%-withholding crisis — the cascade worked in the Single Account lesson, which begins, always, with a reconciliation nobody did.

What the Summary Report cannot do

Honest boundaries, each met before: it is not a formal statement of account for third parties (the instrument hierarchy: ITF 263 for standing; Section 52 certified copies for assessment content; SSP exports informal — established,); it is not conclusive evidence either way (that is Section 79's word, and it belongs to ZIMRA's certified extracts, not your PDF export); and it does not decompose the story behind a net figure — a head can net to zero while concealing an unpaid USD assessment offset by a misallocated credit that belongs to another head. Net-zero is where reconciliation starts, not where it stops: tie the components, not just the total, whenever the period saw any dispute, misallocation, or audit activity.

Individuals: Rudo's fifteen-minute version

A consultant with one head in play (income tax/QPDs, USD) does not need a general ledger to reconcile like a professional. Rudo keeps a one-page schedule: four QPD lines (date, amount, bank reference) plus the annual ITF 12C settlement. Monthly — in practice, the week after each QPD — she exports the Summary Report (USD), checks the income tax head's net against her schedule, and drills only if they differ. In March they differ by USD 412: the Tax Type Report shows an interest line dated to the prior year's late fourth QPD. Class 4: she recomputes (Section 71(2) from 21 December to her January payment date — the rate per SI 212/2022), books it, pays the residue, and minutes it. Total cost: fifteen minutes and the interest she always owed; counterfactual cost: the USD 412 silently eating the front of her next QPD and a confusing shortfall at year-end.

SMEs: Pamberi's first real reconciliation

Pamberi's accountant builds the control accounts (PAYE, VAT, QPD × two currencies) and runs the first three-way tie. The opening exercise finds the classic spread — and note how each lands in a different class with a different route:

Item	Class	Finding	Route
VAT-USD: SSP shows USD 1,150 more than books	2 — unnotified assessment	Section 31 estimate from a period Pamberi later back-filed; the return-displacement never processed	Pull instrument; object/raise via Case Management with the filed return as evidence (established: never back-file blind over an estimate)
PAYE-ZWG: books show ZWG 14,000 paid, SSP shows nothing	1 — unallocated payment	manual transfer, malformed reference, pre-e-banking habit	Four-hop trace; E-Messaging allocation query, bank proof attached
VAT-ZWG: ZWG 3,900 difference	4 — accrual gap	Fifth Schedule interest on the old-25th-deadline misses of early 2025	Recompute, book, pay residue
QPD-USD: USD 800	3 — timing	March QPD paid 24th, processed 26th	List; clears next month
PAYE-USD: USD 92	5 — own error	February accrual posted to VAT-USD control	Reclassify in own ledger

The minute records all five; next month's reconciliation inherits the open items 1 and 2 with owners and dates. Within a quarter, Pamberi's Summary Report and books agree to the dollar, every month — which is also, not coincidentally, the state in which its October ITF 263 renewal sails through the automated check.

Large corporates: Mukonde's reconciliation as a control environment

At group scale the same methodology becomes formal internal control. Mukonde's tax function runs: control accounts per entity × head × currency, mapped to TINs; a month-end close step in which the Summary Report export is reconciled within five working days, with the reconciliation reviewed and signed by a second person (maker-checker, again); a standing exceptions register feeding the "instruments in objection window" dashboard from the Balances lesson; and an internal-audit test, twice yearly, that re-performs one month's reconciliation per entity from raw instruments. The payoffs compound: external auditors take the tax balances with minimal substantive work (the auditor-pack scenario, established); due-diligence on any disposal starts from agreed numbers; Section 37B/Section 57 inspections are answered from the file in hours; and when an audit assessment lands, the group knows the same day — because Audit Assessment Notices is on the monthly path — with twenty-nine days of objection window still alive instead of none.

Stated honestly: no reported case construes the Summary Report or the Taxpayer Accounting module — administrative renderings of a ledger do not generate jurisprudence. The authorities that give the reconciliation its teeth are the established ones, re-applied: Trek Petroleum (Pvt) Ltd v ZIMRA 17-SC-056 (Section 79 certified extract conclusive in recovery; with Section 78(2), the reason discrepancies must be fought before recovery, in the objection window); Barclays Bank of Zimbabwe Ltd v ZIMRA 04-HH-162 and the Nestlé Zimbabwe line (Section 51(2)–(3): notice must be given and must itself announce the 30-day window — the legal handle on discrepancy species (b)); NYS v ZIMRA 19-HH-617 and PIL (Pvt) Ltd v ZIMRA 17-HH-213 (the records-duty annotations behind Section 37B and Section 57 — the duty the reconciliation file discharges). All are annotation-level markers in the source Acts, met and labelled in earlier lessons; none narrates facts about reports or reconciliations, and the lesson claims nothing more for them.

1. Reading instead of reconciling. Opening the Summary Report, nodding at familiar-looking numbers, and closing it is not reconciliation. Without a control account on your side, you are checking ZIMRA's ledger against your memory — and memory always agrees.
2. Reconciling the net, missing the components. A head can net to zero across an unpaid assessment and a stray credit. Tie components whenever the period saw disputes, misallocations, or audit activity.
3. Plugging differences. A balancing entry to force agreement destroys the only thing reconciliation produces: the difference list. Every item gets a class and a route or it stays on the list.
4. Treating species (b) as a bookkeeping item. An unnotified assessment is not "book it and move on" — it is a 30-day clock that started at a notice you may never have received. Pull the instrument, test it against Section 51(3), and lodge the objection before booking arguments.
5. Letting "timing differences" become permanent residents. Anything surviving two cycles is reclassified and traced. The phrase "timing difference" is where misallocations go to hide.
6. One currency column. USD and ZWG reconcile separately — one control account and one Summary Report read per currency. A combined column is a guaranteed false agreement.
7. No minute. An unrecorded reconciliation cannot prove vigilance (remission/just-cause arguments), cannot be inherited by your successor, and cannot answer a Section 37B/Section 57 inspection. The minute is the deliverable; the agreement of the numbers is merely its best paragraph.

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 Summary Report is the monthly reconciliation instrument: "net balance per tax type for the date range", read per currency, exported and dated — the triage layer above the Tax Type Report's drill-down.
• The guide's confirmed diagnosis: discrepancies are "almost always" an unallocated payment (→ four-hop trace + E-Messaging allocation query) or an unnotified assessment (→ Section 51(2)–(3) testing + 30-day objection via Case Management). Two species, two remedies, two clocks.
• Reconciliation needs your own side: tax control accounts per head per currency, event-dated, plug-free — that is what ITA Section 37B and VAT Section 57 look like in working form, and the monthly minute is the evidence of vigilance.
• The three-way tie (control account ↔ Summary Report ↔ instrument file) converts differences into findings; the five-class taxonomy (unallocated, unnotified, timing, accrual, own error) routes every finding; nothing survives two cycles unowned.
• The stakes are set by the evidentiary asymmetry: Section 79 extracts conclusive, Section 78(2) correctness unchallengeable in recovery (Trek Petroleum) — the reconciliation is how discrepancies get fought while the correcting forums are still open.
• Net figures can lie: tie components, not totals, in any period with disputes or misallocations. And the same data feeds the ITF 263 grid — a clean monthly reconciliation is a clearance application rehearsed twelve times a year.
• Honest boundary: no statute or case addresses the report itself; its law is borrowed, its power is procedural, and its cost — an hour a month — is the cheapest insurance in this course.

The five-class difference taxonomy

Class	Signature	Route	Clock
1 Unallocated/misallocated payment	your debit, no/odd SSP credit	four-hop trace → E-Messaging allocation query + proofs	none, but interest accrues — days
2 Unnotified assessment	SSP liability, no instrument in your file	Section 51(2)/(3) test → object via Case Mgmt	30 days from notice
3 Timing	both records right, dates differ	list and roll; reclassify if it survives 2 cycles	next cycle
4 Interest/penalty accrual	ZIMRA's daily clocks vs your monthly books	recompute from section; book; contest penalty separately	per instrument
5 Own error	control account mispost	correct own ledger	immediate

Reading surfaces and their jobs (consolidated)

Surface	Question answered	Cadence
Balance	what is owed now (dated, per currency)	before any payment
Summary Report	net per head for the period — does ZIMRA agree with my books?	monthly, after the 25th
Tax Type Report	every assessment, payment, adjustment — why don't they agree?	on any difference
Assessment / Audit Assessment Notices	the instruments behind liability lines	monthly + on species (2)

The monthly reconciliation loop

flowchart TD
 A[Export Summary Report per currency - dated] --> B{Head agrees with control account?}
 B -->|Yes| C[Close head - initial the minute]
 B -->|No| D[Drill: Tax Type Report for that head]
 D --> E[Classify each difference: 1-5]
 E --> F1[1: trace + allocation query]
 E --> F2[2: Section 51 test + 30-day objection]
 E --> F3[3: list as timing - roll once]
 E --> F4[4: recompute + book accrual]
 E --> F5[5: correct own books]
 F1 --> G[Minute the reconciliation]
 F2 --> G
 F3 --> G
 F4 --> G
 F5 --> G
 G --> H{Items surviving 2 cycles?}
 H -->|Yes| I[Named owner + formal channel]
 H -->|No| J[File minute + exports - 6-yr archive]

Statutes & sections

• Income Tax Act [Chapter 23:06] — Section 37A(10)–(11) (return = deemed assessment populating the ledger, established); Section 51(2)–(3) (notice shall be given; notice must announce objection window, established verbatim in the Balances lesson); Section 52 (certified copies of own notices, established); Section 62/Section 69 (objection; pay-now, established); Section 71(2) (automatic interest, SI 212/2022); Section 78(2)/Section 79 (recovery: correctness unchallengeable; certified extract conclusive, established); Section 37B(1)–(2) (six-year reconciliation-grade records; penalty greater of level 7 / 10% of taxable income, established verbatim).
• Value Added Tax Act [Chapter 23:12] — Section 31 (Commissioner assessments, established); Section 32 (objections, established); Section 42 (conclusive-evidence twin, established); Section 57(1)–(4) (records incl systems documentation; six years; print-out rule, established verbatim); Fifth Schedule (interest per SI 25/2025, established).

Case law

• Trek Petroleum (Pvt) Ltd v ZIMRA 17-SC-056 — Section 79 certified extract conclusive (established; the stakes of late discovery).
• Barclays Bank of Zimbabwe Ltd v ZIMRA 04-HH-162; Nestlé Zimbabwe 20-SC-290 / 23-HH-312 — Section 51 notice line (established; the handle on unnotified assessments).
• NYS v ZIMRA 19-HH-617; PIL (Pvt) Ltd v ZIMRA 17-HH-213 — records-duty annotations (established).
• No authority exists on the Summary Report or Taxpayer Accounting module itself — stated honestly.

ZIMRA guidance

• Comprehensive Guide to the ZIMRA Self-Service Portal (local External Guide) — Taxpayer Accounting module §10 (four pages; Summary Report defined; the confirmed monthly-reconciliation instruction and two-species diagnosis); monthly workflow §19.1 (Summary Report review between the 25th and month-end; allocation queries via E-Messaging). The official SSP online help was unreachable this run; report columns, currency presentation and export formats flagged.