The previous lesson taught the act of paying; this lesson dissects the channel most payments travel through — the SSP's E-Banking integration. The local SSP guide confirms the architecture in three short, load-bearing statements: the SSP enables "payment of tax in USD or ZiG via credit card or e-banking"; the Payments module's E-Banking page is the "list of banks offering the e-banking service for SSP payments"; and the glossary defines E-Banking as a "bank-led online payment channel integrated into the SSP for tax payments". The official online help was unreachable this run, so every screen-level specific beyond those sentences carries a verification flag — but the channel's legal skeleton is fully confirmed and is the substance of this lesson.

That skeleton is Section 4B of the Finance Act [Chapter 23:04] (inserted by Finance (No. 2) Act 10 of 2022; tightened by Act 7 of 2024). A bank on the E-Banking list is, in statutory language, an "approved financial intermediary" — "any banking or other financial institution registered in terms of the Banking Act [Chapter 24:20]" with which the Commissioner-General holds an account. Through it, a taxpayer "may use that intermediary to make payment of any taxes, duties, fees, levies, charges, penalties, fines or any other moneys due... in terms of any revenue Act" — the section spans everything ZIMRA collects, because "revenue Act" means any Act in the First Schedule to the Revenue Authority Act [Chapter 23:11]. The intermediary must then remit "the full amount" so that the Consolidated Revenue Fund is credited no later than 24 hours from the payment (shortened from 48 hours by Act 7 of 2024, w.e.f. the year of assessment beginning 1 January 2025); delay "without a valid reason as determined by the Zimbabwe Revenue Authority" makes the intermediary liable to the Commissioner-General for interest at 15% on United States dollar amounts or the bank policy rate plus 5% on local amounts.

The instruction leg — what you transmit through the portal, as opposed to the money the bank moves — is governed by the Income Tax Act's electronic-platform provisions in Part VIIIA, walked for this purpose here: Section 80I fixes when an electronic communication is lodged (when it "enters a computer system outside the control of the originator") and received (when it enters ZIMRA's computer), and attributes communications to the registered user who sent them; Section 80J presumes that anything bearing your digital credentials was sent with your authority unless you prove otherwise, and obliges you to report a compromised credential "without delay"; Section 80K provides the downtime fallback — when the system is inoperative, taxpayer and Commissioner "shall communicate with each other in writing in the manner prescribed"; and Section 80L criminalises unauthorised use of another's digital signature and false electronic records at level 12 or ten years' imprisonment — the heaviest sanction in the Act, sitting directly under every shared banking token and SSP password.

The practical doctrine the lesson builds: the taxpayer's leg of an e-banking payment ends when the approved bank is irrevocably paid, within time, with the right reference — and is provable by a dated confirmation. Everything after that — the 24-hour hop to the Consolidated Revenue Fund, the landing in the Single Account, the oldest-first allocation — is the statute's machinery, with the float risk placed on the bank by Section 4B(4). The taxpayer's disciplines are therefore: pay only through banks on the E-Banking list (a non-listed bank is not the statutory channel), never confuse an instruction with a payment, keep the dated proof, and reconcile bank statement against Single Account Transactions monthly.

Before 2022, paying ZIMRA through a bank was a matter of ordinary banking law: the taxpayer instructed a transfer, the bank executed it, and the money arrived at ZIMRA when it arrived. Two recurring failures made that intolerable at fiscal scale. First, float: sums collected from taxpayers could sit in commercial bank accounts — earning the bank value — before reaching the State, and in an inflationary, dual-currency economy every day of float was a real transfer of wealth from the fisc to the intermediary. Second, the orphan-payment problem: money that left the taxpayer but could not be matched to a liability at ZIMRA, leaving the taxpayer in the worst position of all — out of pocket and in default.

Finance (No. 2) Act 10 of 2022 answered the first failure with Finance Act Section 4B, which converts the bank from a mere conduit into a statutory actor with its own duty (remit to the Consolidated Revenue Fund within a fixed time) and its own sanction (interest on what it sits on). TaRMS answered the second with the Single Account and the SSP's integrated e-banking flow, which carries the payment's identity (TIN, reference) with the money so the landing can be traced.

For the student, this lesson completes a triangle begun two lessons ago: Balances taught you to read what you owe; Making a New Payment taught the law of amount, currency and date; this lesson teaches the law of the pipe — the parties it runs between, where each party's duty begins and ends, and what to do when the pipe blocks. It matters practically because deadline-day disputes are almost never about whether money moved; they are about when whose leg completed, and the answers live in Section 4B and Part VIIIA, not in the bank's brochure.

The confirmed procedural layer

The local SSP External Guide confirms, in full, the following about the integration — and nothing more:

• Among the SSP's core functions: "Payment of tax in USD or ZiG via credit card or e-banking."
• Payments module, New Payment page: "pay tax liabilities online by credit card or via E-Banking. The portal lists banks offering e-banking."
• Payments module, E-Banking page: "list of banks offering the e-banking service for SSP payments."
• Glossary: E-Banking is the "bank-led online payment channel integrated into the SSP for tax payments."

Finance Act Section 4B — the money leg, walked clause by clause

Section 4B(1) — the cast. Four definitions set the scene. A "financial intermediary" is "any banking or other financial institution registered in terms of the Banking Act [Chapter 24:20]" — so the channel is open to building societies and other registered institutions, not only commercial banks, provided the next condition is met. "Revenue" is "an amount paid by a taxpayer through an approved financial intermediary in terms of subsection (2)". A "revenue Act" is "any of the Acts specified in the First Schedule to the Revenue Authority Act [Chapter 23:11]" — which is why one channel serves income tax, VAT, capital gains tax and the rest of ZIMRA's portfolio. The "bank policy rate" (inserted by Act 7 of 2024, w.e.f. the year of assessment beginning 1 January 2025) is "the rate set by the Monetary Policy Committee established in terms of Section 29B of the Reserve Bank of Zimbabwe Act [Chapter 22:15]".

Section 4B(2) — approval and entitlement. "If the Commissioner-General has an account with a financial intermediary ('approved financial intermediary'), a taxpayer may use that intermediary to make payment of any taxes, duties, fees, levies, charges, penalties, fines or any other moneys due from the taxpayer in terms of any revenue Act." Three observations. Approval is structural, not ceremonial: what makes a bank "approved" is the existence of a Commissioner-General account with it — the E-Banking page is, in effect, the published register of such banks. The taxpayer's right is permissive ("may"): the channel is an entitlement, not an obligation — the Section 71(1) proviso's right to pay through the post survives, and card payment inside the SSP is an alternative. The scope is total: "any... moneys due... in terms of any revenue Act" covers penalties and fines as well as tax.

Section 4B(3) — the 24-hour rule. "An approved financial intermediary must remit the full amount of revenue paid by a taxpayer so that no later than 24 hours from the time of such payment the Consolidated Revenue Fund is credited with that amount." The Consolidated Revenue Fund is the State's central fund established under the Constitution — the statute is explicit that the destination is the State's fund, not a ZIMRA suspense account, and that the remittance is of the full amount: the intermediary cannot net off charges against the tax. The deadline was 48 hours as enacted in 2022; Act 7 of 2024 shortened it to 24 hours, w.e.f. the year of assessment beginning 1 January 2025 — Treasury squeezing the float window in half.

Section 4B(4) — the sanction, on the bank. An intermediary "that delays to comply with subsection (3) without a valid reason as determined by the Zimbabwe Revenue Authority becomes liable to the Commissioner-General to pay interest of 15% (in the case of United States dollar amounts) or the bank policy rate plus 5% (in the case of Zimbabwe dollar amounts) on any amount it has failed to remit timeously". Act 7 of 2024 amended the local-currency rate and repealed the former proviso to the subsection. Read the architecture carefully: the liability runs from the bank to the Commissioner-General — it is regulatory discipline on the intermediary, not a remedy the taxpayer sues on. The taxpayer's protection is indirect but complete: having paid the approved intermediary within time, the taxpayer has used the channel the statute offers, and the dated confirmation evidences it.

Part VIIIA of the Income Tax Act — the instruction leg

Money is moved by the bank; communications — the payment instruction you transmit through the portal, the acknowledgment that comes back — are electronic communications on ZIMRA's Section 80D computer system, governed by Part VIIIA (the platform law walked in the Roles and E-Agreements lessons; re-read here for the payment context):

• Section 80I(1) — attribution. An electronic communication is attributed to the originator if sent by the originator, by "a person who had the authority to act on behalf of the originator", or by "a computer system programmed by or on behalf of the originator to operate automatically". A payment instruction fired by your assignee, or by your accounting system's integration, is your instruction.
• Section 80I(2)–(3) — acknowledgments. Unless a particular form is agreed, ZIMRA may acknowledge receipt by any communication or by conduct sufficient to indicate receipt; and where the parties have agreed that a communication binds only on acknowledgment, an unacknowledged communication "shall be deemed not to have been sent" within the agreed time. (Check what your user agreement says before assuming a fired instruction stands.)
• Section 80I(4)–(5) — lodgment and receipt. Lodgment "occurs when it enters a computer system outside the control of the originator"; the time of receipt is when the communication "enters the computer at any office of the Zimbabwe Revenue Authority... and such office shall be the place of receipt". These are the timing rules for the paperwork of payment — an instruction stuck in your own gateway at midnight was never lodged.
• Section 80J — credential presumptions. A registered user whose digital signature is compromised must inform the Commissioner "in writing of that fact without delay" (Section 80J(1)); ZIMRA bears no liability for the user's security failures and may assume data authenticated by your credentials came from you, at least until notification (Section 80J(2)); and in any proceedings it is presumed, absent contrary proof, that your signature was used with your consent and authority (Section 80J(3)). A "payment" initiated by a rogue holder of your credentials is presumptively yours to own and unwind.
• Section 80K — the downtime fallback. "Whenever a computer system established in terms of section eighty D or any other computer system of a registered user is inoperative, the registered user and the Commissioner shall communicate with each other in writing in the manner prescribed in this Act"; and the Commissioner may at any time require original documents (Section 80K(2)). Note that the fallback triggers on either side's outage — including yours.
• Section 80L — the criminal floor. Using another's digital signature without authority, making or falsifying an electronic record, or dishonestly affixing or transmitting signatures or records: fine up to level 12 or imprisonment up to ten years or both — the heaviest sanction in the Act, and it sits directly beneath the habit of sharing banking tokens and SSP logins on deadline day.

A precision worth stating: Part VIIIA governs communications and records, not the movement of funds. The money leg completes under Section 4B when the bank is paid and remits; the instruction leg lodges under Section 80I when it leaves your control. Deadline analysis usually needs both.

The neighbouring law (established, cross-referenced)

The due-date catalogue, automatic interest (ITA Section 71(2)–(3); VAT Fifth Schedule), currency rules (VAT Section 38(4)–(4a), Section 38A; ITA Section 37AA) and the Single Account's oldest-first allocation were walked in the previous lesson and the Single Account lesson; they apply to every e-banking payment and are not repeated here.

Anatomy of an e-banking payment: four parties, three hops

Name the parties precisely, because each owns a different failure:

1. The registered user (a human with SSP credentials, possibly an assignee) — transmits the instruction. Owner of: credential security (Section 80J), authority hygiene (Roles lesson), timing of initiation.
2. The taxpayer (the TIN whose Single Account will receive the credit) — owner of: the underlying debt, the currency determination, the evidence archive.
3. The approved financial intermediary (a bank on the E-Banking page) — owner of: executing the debit and the 24-hour remittance to the Consolidated Revenue Fund (Section 4B(3)), on pain of Section 4B(4) interest.
4. ZIMRA/TaRMS — owner of: crediting the Single Account, allocating (oldest-first within head, then head priority), and issuing the acknowledgments and records the taxpayer will later rely on.

And the three hops: instruction (user → bank, via the SSP integration — lodged when it leaves your control, Section 80I(4)); settlement (taxpayer's account → bank — the taxpayer's leg completes here, evidenced by the dated confirmation); remittance (bank → Consolidated Revenue Fund within 24 hours — the bank's leg, Section 4B(3)) followed by the ledger landing in the Single Account.

The E-Banking page as a legal register

The E-Banking page is not a convenience list; it is the practical register of approved intermediaries — banks where the Commissioner-General holds the account that Section 4B(2) requires. Two disciplines follow. Check the list before paying, not once a year: a bank's appearance on (or disappearance from) the list determines whether your payment travels the statutory channel with its 24-hour duty, or is just an ordinary transfer hoping to be matched. A non-listed bank is not the Section 4B channel: a transfer routed through a bank not on the list may still reach ZIMRA eventually, but no statutory remittance clock disciplines it and the reference-matching that the integration provides is absent — this is the unallocated-credit factory.

Instruction ≠ payment: the doctrine that decides deadline disputes

The single most important conceptual line in this lesson: transmitting an instruction is not paying. An instruction can fail — insufficient funds, expired token, bank-side rejection, a typo in the amount — and Section 80I will happily prove you sent something while your account proves nothing left it. The taxpayer's leg completes when the bank irrevocably debits the taxpayer's account against the correct reference. From that moment:

• if the bank then sits on the money beyond 24 hours, Section 4B(4) makes the bank liable to the Commissioner-General for interest — 15% per annum on USD amounts, bank policy rate +5% on local;
• the taxpayer's evidence that the leg completed in time is the dated, referenced bank confirmation — which is why the previous lesson's archive discipline (confirmation filed with the SSP exports, six years, Section 37B/VAT Section 57) is non-negotiable.

Quantify the bank's exposure to see what the statute is doing. Suppose a bank delays remitting a USD 5,600 VAT payment by four days without valid reason:

USD 9.21 disciplines nobody on one payment — but Section 4B operates on the aggregate float of every taxpayer in the country; on USD 50 million of daily collections, the same four days cost an intermediary over USD 82,000. The point for the taxpayer is different: the section tells you whose problem the float is (the bank's), and what your protection looks like (the dated proof that you paid within time).

Failure modes and their law

Work through the ways the pipe blocks, each with its governing rule and cure:

1. Instruction transmitted, never debited. Not a payment; the debt stands, interest runs (Section 71(2)). Cure: monitor to debit, not to "sent"; on deadline day, re-initiate or pay by the card channel; document the failure (it is "just cause" material for penalty remission, never a defence to interest).
2. Debited in time, remitted late. Taxpayer protected (leg complete, dated proof); the bank owes Section 4B(4) interest to the Commissioner-General. Cure: produce the confirmation if the ledger shows a late landing; raise an E-Messaging allocation query attaching it.
3. Debited, landed, wrongly allocated or unmatched. The Single Account lesson's territory: oldest-first allocation ate it, or a malformed reference orphaned it. Cure: the four-hop trace (Payment History → Single Account Transactions → Tax Type Report → E-Messaging/Case Management).
4. Portal inoperative. Section 80K: communicate in writing as prescribed — and the money leg does not depend on the portal: pay at the approved bank directly, referenced to the TIN, keep the proof, and regularise the paperwork when the system returns. (The E-Agreements lesson's confirmed principle: deadlines do not die with the portal.)
5. Bank-side outage. Section 80K's words cover "any other computer system of a registered user", and the practical answer is redundancy: hold mandates at two listed banks per currency so that no single outage stands between you and a statutory date.
6. Rogue instruction on your credentials. Section 80J(3) presumes authority; Section 80J(1) demands you report compromise "without delay". Cure is the incident routine from the Changing Bank Details lesson: freeze withdrawals, reset credentials, review assignees, notify ZIMRA in writing — and remember Section 80L makes the rogue's conduct a ten-year offence.

Choosing and operating the bank relationship

A deliberate e-banking setup, distilled from the confirmed architecture: hold accounts in both currencies at a listed bank (the Single Account's segregation means USD and ZiG legs travel separately); know the bank's cut-off time for same-day value and set internal deadlines behind it; mandate two authorised operators per the maker-checker discipline (instruction-preparer ≠ releaser — the Roles lesson); and never let the person who can change bank details on the taxpayer profile also release payments (the fraud-surface doctrine, established).

Individuals: Rudo selects her channel

Rudo (our consultant) banks with a mid-sized institution. Before her first e-banking payment she opens Payments → E-Banking and finds her bank is not on the list. Her options, correctly analysed: pay by card in New Payment; open an account at a listed bank; or transfer manually and accept the orphan-risk. She opens a USD account at a listed bank — her income is USD (Section 37AA), so a single-currency relationship suffices — and her payment routine becomes: initiate two banking days early, confirm the debit (not the instruction), file the dated confirmation with the month's SSP exports. Cost of the discipline: minutes. Cost of its absence: her December QPD once spent six days as an untraceable transfer under the old habits, accruing Section 71(2) interest while support tickets crawled.

SMEs: Pamberi's deadline-day anatomy

Pamberi (our retailer) owes its USD 5,600 VAT leg on Friday the 15th. The instruction is released at 15:40; the bank's same-day cut-off was 15:00. The debit posts Monday the 18th. Walk the law: the taxpayer's leg completed on the 18th — three days late; Section 4B is no shield, because the 24-hour clock disciplines the bank's leg and never started until the bank was paid. Fifth Schedule interest runs from the 16th, and the part-payment/penalty machinery looms if the lapse repeats. Compare the counterfactual: released at 14:00, debited the 15th, remitted the 17th — taxpayer compliant on its dated proof; the bank owes Section 4B(4) interest on the delay. Same forty minutes, opposite legal worlds. Pamberi's fix is procedural: internal payment deadline the 12th, instruction prepared by the bookkeeper, released by a director (maker-checker), debit confirmed same day, confirmation filed.

Large corporates: Mukonde's treasury architecture

Mukonde Holdings runs the channel as infrastructure: mandates at two listed banks per currency (outage redundancy); a treasury calendar that front-runs every statutory date by three working days; automated reconciliation each week between bank statements and Single Account Transactions, with a standing "unmatched items" report — at group volumes a mis-referenced payment a quarter is normal, and the four-hop trace starts within days, not at year-end. Governance: SSP payment-initiation rights and bank release tokens are held by different officers; both are reviewed quarterly with the assignee audit; and the group's Section 80J(1) incident procedure (report compromise in writing without delay) is documented, because the Section 80J(3) presumption means a compromised credential is presumptively the group speaking. When ZIMRA's ledger once showed a USD 240,000 instalment landing a day after its due date, the dispute died in one email: the dated confirmation showed the debit at 11:02 on the due date — the late landing was the bank's Section 4B problem, not Mukonde's.

Stated honestly: no reported Zimbabwean case construes Finance Act Section 4B or the SSP's e-banking integration — the section dates from December 2022 and its interest mechanism targets banks, who comply rather than litigate. The annotated authorities that frame this lesson's law are those already met: Mayor Logistics (Pvt) Ltd v ZIMRA 14-CC-007 on the Section 71(1) payment master clause; Man Ltd v ZIMRA 20-HH-078 and MR Bank Ltd v ZIMRA 19-HH-779 on Section 71(2) interest and its proviso; and on the electronic-platform side, PIL (Pvt) Ltd v ZIMRA 17-HH-213 (annotated to the records/admissibility provisions met in earlier lessons) is the closest the law reports come to the evidentiary status of electronic tax records. The facts of these decisions are not reproduced in the source documents; they are cited at annotation level. The credential-presumption and downtime rules (Sections 80J–80K) are likewise unlitigated in the sources — the lesson's guidance there is statutory text plus compliance logic, and is labelled as such.

1. Treating "instruction sent" as "tax paid". The taxpayer's leg completes at the irrevocable debit. An instruction that dies at the bank leaves the debt alive and interest running. Always confirm the debit, same day.
2. Paying through a bank that is not on the E-Banking list. No Section 4B clock, no integrated reference — the unallocated-credit factory. Check the list each cycle, not annually.
3. Testing the bank's cut-off against the statutory date. Forty minutes past cut-off converts a compliant payment into a three-day default (weekends are the multiplier). Internal deadlines sit 2–3 banking days early.
4. Discarding the bank confirmation once the portal shows the credit. The dated confirmation is the only evidence that your leg beat the deadline when the ledger landing is late; it belongs in the six-year archive with the SSP exports (Section 37B; VAT Section 57).
5. Sharing tokens and credentials to make the deadline. Section 80J(3) presumes everything done on your credentials was authorised by you; Section 80L makes the unauthorised user's conduct punishable by up to ten years. Two mandated operators per bank, distinct SSP assignees — never a shared login.
6. Assuming portal downtime suspends payment. Section 80K switches communications to writing; the money can still travel to the approved bank against the TIN. Pay, document, regularise after.
7. One bank, one currency, one signatory. A single point of failure on every statutory date. Redundancy (two listed banks, both currencies where relevant) is cheap; a missed QPD is not.

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.

• E-Banking = the statutory channel: a bank on the E-Banking page is an approved financial intermediary under Finance Act Section 4B(2) (a Banking Act institution holding a Commissioner-General account), through which a taxpayer may pay any revenue-Act moneys.
• The 24-hour rule (Section 4B(3)): the intermediary must credit the Consolidated Revenue Fund within 24 hours of being paid (48→24 by Act 7/2024, w.e.f. YoA 1 Jan 2025), remitting the full amount; delay without valid reason costs the bank interest to the Commissioner-General — 15% USD / bank policy rate +5% local (Section 4B(4)).
• The taxpayer's leg ends at the irrevocable debit, in time, with the right reference — provable by the dated bank confirmation, which belongs in the six-year archive. Instruction ≠ payment; cut-off times decide deadline days.
• Part VIIIA governs the instruction leg: lodgment when the communication leaves your control and receipt on entering ZIMRA's computer (Section 80I(4)–(5)); attribution of assignee- and system-fired instructions (Section 80I(1)); the Section 80J(3) presumption that your credentials = your authority, answered by the Section 80J(1) duty to report compromise without delay; Section 80K written-communication fallback when either side's system is down; Section 80L level 12 / ten years for unauthorised signatures and false e-records.
• Operating doctrine: pay only through listed banks (re-check the list); two banks per currency for redundancy; maker-checker between instruction and release, and between profile-amendment and payment rights; reconcile bank statement against Single Account Transactions monthly; downtime changes the form of compliance, never the date.
• Honesty note: the guide yields four confirmed sentences on this module and no case construes Section 4B; everything screen-level beyond them is flagged, and the lesson's weight rests on the confirmed statutes.

Party–duty–sanction matrix

Channel timeline — whose clock is running?

E-banking payment flow

flowchart TD
 A[Check E-Banking page: is the bank listed?] -->|No| B[Card channel / open account at listed bank]
 A -->|Yes| C[Initiate in New Payment before bank cut-off]
 C --> D{Debit confirmed same day?}
 D -->|No| E[Re-initiate or pay by card; document failure]
 D -->|Yes| F[Taxpayer leg COMPLETE - file dated confirmation]
 F --> G[Bank must credit CRF within 24 hrs - FA Section 4B3]
 G -->|late| H[Bank owes Section 4B4 interest to CG - taxpayer protected by proof]
 G -->|on time| I[Credit lands in Single Account ledger]
 H --> I
 I --> J[Oldest-first allocation]
 J --> K{Verify: Payment History / Transactions / Tax Type Report}
 K -->|mismatch| L[Four-hop trace; E-Messaging / Case Mgmt]
 K -->|clean| M[Archive exports + confirmation, 6 yrs]

Statutes & sections

• Finance Act [Chapter 23:04] — Section 4B (ins Finance (No. 2) Act 10/2022): Section 4B(1) definitions (financial intermediary per Banking Act [Chapter 24:20]; revenue Act per Revenue Authority Act [Chapter 23:11] First Schedule; bank policy rate, ins Act 7/2024); Section 4B(2) approved-intermediary channel for any revenue-Act moneys; Section 4B(3) full-amount remittance, Consolidated Revenue Fund credited ≤ 24 hours (Act 7/2024); Section 4B(4) intermediary interest 15% USD / bank policy rate +5% local (proviso repealed Act 7/2024).
• Income Tax Act [Chapter 23:06] — Section 80I (attribution; acknowledgments; lodgment on leaving originator's control; receipt on entering ZIMRA's computer; e-signature effect; internet submissions); Section 80J (compromise notification without delay; ZIMRA's entitlement to assume authority; presumption of consent absent contrary proof); Section 80K (written communication when either system inoperative; originals on demand); Section 80L (unauthorised signature / false e-records: level 12 or 10 years); Section 71(1)–(2) (payment master clause; automatic interest — established); Section 37B (6-year records).
• Value Added Tax Act [Chapter 23:12] — Section 38(1) (payment in full within allowed time); Section 57 (records) — established; Fifth Schedule interest (SI 25/2025, established).

Case law

• Mayor Logistics (Pvt) Ltd v ZIMRA 14-CC-007 — ITA Section 71(1) annotation (established).
• Man Ltd v ZIMRA 20-HH-078; MR Bank Ltd v ZIMRA 19-HH-779 — Section 71(2) interest and proviso annotations (established).
• PIL (Pvt) Ltd v ZIMRA 17-HH-213 — electronic records/admissibility context (annotation level).
• No authority on Finance Act Section 4B or the e-banking integration exists in the sources — stated honestly.

ZIMRA guidance

• Comprehensive Guide to the ZIMRA Self-Service Portal (local External Guide) — "Payment of tax in USD or ZiG via credit card or e-banking" (§2.1); New Payment and E-Banking pages (§11); glossary: "bank-led online payment channel integrated into the SSP". The official SSP online help was unreachable this run; bank list, initiation flow, references, cut-offs and currency support flagged.