Inside the Tax Return Management module, between Submitted Tax Returns and Old Period Documents, sits a page this course has so far only named: E-Agreement — in the local SSP External Guide's complete description, the page where the user can "manage e-agreements submitted on behalf of the taxpayer; complete and submit new e-agreements". That single sentence is the entire procedural source available for this lesson, and the lesson says so plainly at the outset: the precise inventory of agreement types the page carries, its form fields, and its approval workflow are not documented in the source folder and are flagged for verification against the SSP online help (unreachable this run). What the sources do support — fully, verbatim, and richly — is the law of agreements concluded with ZIMRA electronically: what kinds of agreement exist between a taxpayer (or user) and the Commissioner, what makes an electronic signature and an electronic record binding, when an agreed figure becomes final, and what disciplines follow. That law is the substance of this lesson, because whichever specific instruments the E-Agreement page carries, they are governed by it.

The framework has two layers. The platform layer is Part VIIIA of the Income Tax Act [Chapter 23:06] (Sections 80B–80L, walked verbatim in the Roles & Permissions lesson and re-applied here): Section 80E empowers the Commissioner to prescribe a user agreement between the Zimbabwe Revenue Authority and registered users, which "shall set out" the terms of communication through the Section 80D computer system — including the use of specified equipment, the allocation of a digital signature, the user's duty to ensure the security of that signature, the manner of affixing it, ZIMRA's reasonable access to the user's computer system "for such verification and audit purposes as may be required", and electronic record-keeping; Section 80F(2) makes the completed user agreement an attachment to the application for registration as a registered user. The signature so allocated is unique, under the user's sole control, verifiable and integrity-linked (Section 80G), legally equivalent to a manuscript signature (Section 80I(6) context per the roles lesson), presumed used with the user's consent or authority absent contrary proof (Section 80J(3)), with timing rules for electronic lodgement and receipt (Section 80I) and admissibility of electronic records (Section 80C; PIL 17-HH-213). In short: an agreement completed and submitted through the SSP is signed in the eyes of the Act, and what is concluded under your credential is presumptively your agreement.

The substantive layer is the family of statutory agreements a taxpayer can conclude with the Commissioner, each taught earlier in this course and gathered here because each is a candidate occupant of an electronic-agreement channel: the Section 71(1) instalment arrangement ("instalments of equal or varying amounts", the Commissioner's discretion — Mayor Logistics 14-CC-007 context — lodged through Debt Management before the due date, and never stopping Section 71(2) interest); the Section 45(2) agreed assessment (where a person is "unable from any cause to furnish an accurate return", the agreed taxable income being non-objectionable and the power non-delegable to junior officers — PPC 19-HH-755 — re-openable only where information was withheld); the Section 46(7) agreed additional tax (an additional-tax amount agreed with the taxpayer "shall be final" and not subject to objection); the VAT Section 65 compromise of offence proceedings (agreed fine within the maximum; Prosecutor-General's approval once proceedings are instituted; not a conviction; bars prosecution; never exempts the tax itself); and the payment-plan limb (Part D) of the VDA01 voluntary disclosure, whose missed instalment invalidates the disclosure relief. The common DNA of every one: an agreement with ZIMRA trades flexibility for finality — you gain time, certainty or peace; you give up objection rights, re-litigation or both. The lesson's governing discipline follows: read an e-agreement as a waiver document before signing it as a convenience document, agree only figures and schedules you can honour, and treat the digital execution as carrying everything a wet signature would. Worked examples price an instalment e-agreement against the cost of default, walk a Section 46(7) penalty agreement decision, and apply the Section 80J credential rules to a disputed agreement. Case law on the page itself: none, said honestly; the platform and agreement authorities above carry the lesson.

Everything a taxpayer lodges with ZIMRA falls into one of three families. Declarations state facts and figures one-sidedly — returns, the subject of the last four lessons. Applications request an exercise of discretion — registrations, refunds, clearances. Agreements are the third and rarest family: instruments where both sides commit — the taxpayer to figures, payments or conduct; the Commissioner to acceptance, forbearance or finality. The E-Agreement page is the SSP's home for that third family within the returns module, and its single-sentence treatment in the local guide should not mislead anyone about the family's importance: agreements are where the most consequential signatures in tax practice happen, precisely because they are the signatures that close doors.

Why doors close is worth understanding from first principles. A declaration can be amended (within limits the Amendment lesson taught); an application refused can be re-made. An agreement, by design, ends movement: the Section 45(2) agreed assessment is not subject to objection and appeal; the Section 46(7) agreed additional tax is final; the VAT Section 65 compromise bars prosecution for the compromised offence but equally binds the taxpayer to the agreed fine. The State offers certainty and concession; the price is the taxpayer's remedies. That trade is often excellent — an instalment plan that restores an ITF 263, a compromise that avoids a criminal record — but it is a trade, and this lesson's purpose is to make sure the practitioner prices both sides before the digital signature goes on.

A candour note before the framework, in keeping with this course's accuracy rules: the source folder documents the E-Agreement page in one sentence, and no source in the folder enumerates which agreement types the page presently carries, whether the Section 80E user agreement itself is executed there or at user registration, or what the page's screens look like. Everything screen-specific below is therefore flagged. What is not flagged — because it is confirmed verbatim from the Acts — is the law that governs any agreement the page carries, and that law is most of what a professional needs to act safely.

B.1 The platform layer — Part VIIIA makes electronic agreement possible

The Roles & Permissions lesson walked Sections 80B–80L verbatim; here the same provisions are re-read as the contract-formation rules for e-agreements:

• Section 80E — the user agreement itself. The Commissioner "may, for the purpose of regulating communication through a computer system established in terms of section eighty D, prescribe the form of a user agreement to be entered between the Zimbabwe Revenue Authority and registered users". Its mandatory content (Section 80E(2), confirmed verbatim): the terms and conditions of communication, including use of specified computer equipment; allocation to a registered user of a digital signature by the Commissioner; the requirement that users ensure the security of allocated signatures "in the manner specified in the agreement"; the manner of affixing a digital signature to any electronic communication or record; ZIMRA's reasonable access to the registered user's computer system for verification and audit purposes; and the manner and period of keeping electronic records. Two teaching points. First, the user agreement is the constitutional document of the taxpayer–TaRMS relationship: every submission this course has taught happens inside its terms. Second, its audit-access clause means the agreement reaches beyond the portal — into the user's own systems — a term most users have never read and every practitioner should have.
• Section 80F(2) — the application for registration as a registered user "shall … be accompanied by the user agreement completed by the applicant" (plus any prescribed fee and supporting information). The agreement is therefore executed at the threshold; whether the SSP's E-Agreement page is where it is completed, renewed or varied is a screen-level specific not documented in the folder.
• Section 80G — the allocated digital signature must be unique to the user, under the user's sole control, verifiable, and linked to the record so any change is detectable; allocated per nominated employee for corporates (Section 80G(2)).
• Section 80J — the liability triangle: the duty to notify compromise "without delay"; ZIMRA's entitlement to assume authority pre-notification; and the presumption that a signature was used with the user's consent or authority "unless the contrary is proved" (Section 80J(3)). Applied to agreements: an e-agreement concluded under your credential is presumptively your agreement, and the rebuttal evidence is the credential hygiene the Roles lesson prescribed.
• Section 80C and Section 80I — electronic records are admissible and carry due evidential weight (PIL (Pvt) Ltd v ZIMRA 17-HH-213); a communication is lodged when it leaves the originator's control and received on entry into ZIMRA's computer (Section 80I(4)–(5)) — the timing code that dates an e-agreement's conclusion; and the digital signature ranks with the manuscript one. Section 80H lets electronic retention satisfy record-keeping; Section 80K supplies the paper fallback when the system is down — an agreement deadline does not die with the portal.

The composite: Zimbabwean law has, since FA 12 of 2006, supplied everything contract formation needs in electronic form — offer and acceptance through the system, signature, attribution, timing, evidence, retention. An "e-agreement" is not a lesser agreement.

B.2 The substantive layer — what taxpayers and ZIMRA agree about

The statutory agreements this course has met, gathered and compared (each confirmed in its own earlier lesson from the source Acts):

1. Instalment arrangements — ITA Section 71(1) ("in instalments of equal or varying amounts", within the Commissioner's discretion) and the operational rule from the guide that plans are lodged through Debt Management, ideally before the due date ("ZIMRA is more receptive to instalment plans for tax that is not yet overdue"). The plan reschedules payment, never liability: Section 71(2) interest keeps running, and a plan in good standing preserves the ITF 263 position (engagement lesson). Default consequences are contractual and practical — the balance accelerates into ordinary recovery and the clearance position collapses.
2. Agreed assessments — ITA Section 45(2) (confirmed verbatim this run): where a person "is unable from any cause to furnish an accurate return", the Commissioner "may agree with such person what shall be the amount of his taxable income or assessed loss", and the agreed amount "shall not be subject to any objection and appeal" — with the proviso that withheld information re-opens it (subject to Section 47), and the PPC 19-HH-755 gloss that the power is the Commissioner's, not delegable to junior officers (an "agreement" concluded with an officer lacking authority is no agreement).
3. Agreed additional tax — ITA Section 46(7): an additional-tax amount agreed with the taxpayer is final and conclusive, not objectionable (debt course). The negotiating consequence: in a penalty negotiation, the number you agree is the number you keep.
4. Compromise of offences — VAT Section 65 (engagement lesson, confirmed): proceedings for an offence may be compromised on payment of an agreed fine not exceeding the maximum; once proceedings are instituted the Prosecutor-General's approval is required (Act 5 of 2014 proviso); the compromise is not a conviction and bars prosecution for that offence (Section 65(4)); and it never exempts the tax itself (Section 65(5)).
5. The VDA01's Part D payment plan — the voluntary-disclosure instrument's instalment schedule is a condition subsequent: a missed instalment invalidates the disclosure's relief (engagement lesson). It is the sharpest illustration in the system of an agreement whose breach revives everything it settled.
6. The Section 28(3)/Section 37A(4) extensions — strictly unilateral discretions rather than agreements, but practically negotiated undertakings: the Commissioner extends, the taxpayer commits to the extended date.

The comparative anatomy matters more than the catalogue: each instrument specifies (i) what the taxpayer gives up (objection rights — Section 45(2), Section 46(7); the right to litigate the offence — Section 65; the relief itself on breach — VDA Part D); (ii) what survives regardless (the tax always — Section 65(5) says it expressly; interest almost always — Section 71(2)); and (iii) what re-opens it (withheld information — Section 45(2) proviso; breach — VDA Part D; nothing — Section 46(7)). Reading any e-agreement against those three questions is the lesson's core professional skill.

B.3 Old vs new

The substantive agreement powers are old (Section 45(2) is classical machinery; Section 71(1) likewise); what changed is execution and evidence. Pre-TaRMS, an instalment arrangement was a letter and a stamped copy; proof of its terms depended on filing discipline. Part VIIIA (FA 12/2006) supplied the legal infrastructure, and the SSP now supplies the channel: agreements completed and submitted electronically, time-stamped on receipt (Section 80I(5)), retained electronically (Section 80H), admissible (Section 80C), and attributed to the signing credential (Section 80J(3)). The practical consequence cuts both ways, exactly as it did for amendments: the taxpayer can prove the agreement and its date; ZIMRA can prove the undertaking — and the breach.

C.1 Where the page sits and what "manage" implies

The E-Agreement page lives in Tax Return Management alongside Pending, Submitted, Old Period Documents and Drafts. The guide's verbs — "manage e-agreements submitted on behalf of the taxpayer; complete and submit new e-agreements" — support three inferences, each stated as inference and not as confirmed screen fact: the page is a register (existing agreements are listed and viewable — the audit trail function); it is an execution channel (new agreements are completed and submitted there, presumably moving through a status life like other SSP documents); and it operates per taxpayer ("on behalf of the taxpayer" — so the user-vs-taxpayer discipline applies: shift to the right taxpayer; the agreement binds the taxpayer, executed under the user's credential, which is precisely the Section 80J(3) attribution geometry).

C.2 The pre-signature protocol

Because agreements close doors, the review that precedes submission is different in kind from a return review. The protocol this course recommends, built from the statutory anatomy in B.2:

1. Identify the instrument and its statute. Which agreement is this — instalment (Section 71(1))? agreed figure (Section 45(2)/Section 46(7))? compromise (VAT Section 65)? disclosure schedule (VDA Part D)? The statute determines what you are giving up.
2. Run the three questions: what rights does this waive; what survives it (tax, interest); what re-opens or invalidates it (withheld information, breach).
3. Stress-test every schedule. An instalment calendar must survive the business's worst realistic month, not its average one — Part D's invalidation rule and the acceleration consequences make an optimistic schedule worse than no agreement.
4. Verify authority on both sides. Internally: the signer holds a role scoped for agreements (the Roles lesson's payment-authoriser/submitter design; an agreement is closer to a payment than to a return). Externally: for Section 45(2)-type agreements, the PPC point — is the agreement genuinely the Commissioner's act through an authorised channel?
5. Paper the file. Export the concluded agreement to PDF; minute the negotiation; diarise every payment date and review date. The Section 37B/Section 80H retention rules apply; the diary is what keeps a condition-subsequent agreement alive.

C.3 Living with an agreement

An e-agreement is an operating document, not a filing event. The disciplines: performance tracking (each instalment paid in the right currency on the right date — Single Account never-net rules apply to agreed payments as to any others); early renegotiation (if a scheduled payment will be missed, approach ZIMRA before the date — the same pre-due-date receptivity logic the guide states for plans applies to variations; silence converts a cash problem into a breach); status monitoring (the agreement register reviewed in the quarterly sweep alongside grants and profiles); and closure (on final performance, confirm the account reflects it — Summary Report reconciliation — and retain the concluded file for the six-year horizon).

C.4 When the system is down or the agreement is disputed

Two edge doctrines complete the picture. Downtime: Section 80K's paper fallback governs — an agreement deadline (an instalment date, an execution date) is met by written communication when the portal fails; downtime excuses nothing. Dispute: where a taxpayer disowns an e-agreement ("we never signed that"), Section 80J(3) presumes the credentialled signature was authorised; the rebuttal is the Roles lesson's hygiene evidence — per-person credentials, the compromise notice given "without delay", the contemporaneous incident record. Conversely, where ZIMRA's side of an agreement is performed by an officer without authority, PPC shows the agreement may not bind — the taxpayer's protection is to conclude significant agreements through the formal channel, in writing, with the authorising office identified.

D.1 The SME instalment e-agreement, priced

Tariro Distributors (from the Back-Filing lesson) emerges from its campaign owing USD 11,200 after immediate payments. Option A — no agreement: the arrear sits on the Single Account, oldest-first allocation eats every incoming payment, the ITF 263 stays dead (30% Section 80 bleed on roughly USD 7,500/month of registered-payer receipts ≈ USD 2,250/month withheld), and recovery measures loom. Option B — a six-month instalment e-agreement at ≈ USD 1,867/month: Section 71(2) interest continues on the reducing balance (at 10% p.a. on a USD average balance ≈ USD 280 over the half-year), but the plan in good standing restores the clearance position, switching the 2,250/month bleed off. The arithmetic is not close: the agreement's carrying cost (≈ 280) buys back ≈ 13,500 of withheld working capital over the period. The discipline it demands: six dates diarised, each payment in USD, and renegotiation initiated before any date that will be missed — because default resurrects everything Option A threatened, now with a breach on the record.

D.2 The penalty negotiation: agreeing under Section 46(7)

Mukonde Retail's disclosed under-declaration (Amendment lesson) ends with ZIMRA proposing additional tax at 40% of the shortfall in place of the statutory 100%. Agreeing under Section 46(7) makes that figure final — no objection, no appeal, no second bite if a court later softens the law; refusing keeps remedies alive but keeps the 100% exposure alive with them. The decision frame the lesson teaches: agree when the proposed figure is at or below the realistic litigated outcome discounted for costs and time; refuse when a genuine Section 46(6) no-intent case has not yet been properly put. What the agreement does not touch: the principal (always payable) and Section 71 interest. The signature, executed electronically, carries the full Section 80I/80J weight — dated on receipt into ZIMRA's system, attributed to the credential that signed.

D.3 The corporate's user-agreement audit

Khanyisa Group's tax-risk review asks a question most boards never do: what did we sign when our users registered? The Section 80E user agreement's clauses — equipment classes, signature security "in the manner specified in the agreement", ZIMRA's reasonable access to the user's computer systems for verification and audit, electronic record-keeping — are corporate undertakings, performed in practice by IT and payroll people who have never read them. The audit actions: obtain the executed agreements for every registered user; map the security clause onto the company's actual credential practice (the Roles lesson's grid); brief IT that ZIMRA system-access requests trace to a contractual clause, with scope limits to be managed, not improvised; and align record-retention settings with the agreement's terms and Section 80H. The point generalises: the first e-agreement any taxpayer ever concluded is the one governing everything else it does in TaRMS.

Stated honestly: no reported Zimbabwean case addresses the SSP's E-Agreement page or construes a TaRMS e-agreement, and the Part VIIIA agreement provisions themselves are essentially unlitigated. The supporting authorities are those already met: PIL (Pvt) Ltd v ZIMRA 17-HH-213 (electronic records admissible with due weight — Section 80C, the evidential floor under every e-agreement); PPC v ZIMRA 19-HH-755 (the Section 45(2) agreement power is non-delegable — authority matters on ZIMRA's side of an agreement); Mayor Logistics (Pvt) Ltd v ZIMRA 14-CC-007 (constitutional context of the payment machinery within which instalment arrangements operate); and the remission/compromise lines from the debt course (PL Mines, GC, GFZ, MR Bank on Section 46(6); the VSL/E.J line on VAT Section 39(5)) which set the negotiating backdrop against which agreed penalties are priced. General contract principles (offer, acceptance, authority, breach) apply to these statutory agreements through the ordinary law; no tax-specific authority in the sources displaces them. Where this lesson describes the page's behaviour, the source is the local guide's single sentence plus flagged inference — not authority.

1. Signing the user agreement blind. It is the constitutional document of the relationship — equipment, signature security, audit access to your systems, record-keeping. Read it once, properly, and brief the people who perform it.
2. Treating an e-agreement as softer than paper. Ss 80C, 80G, 80I and 80J make the electronic execution fully binding, dated, and attributed to the credential. There is no "it was only on the portal" defence.
3. Agreeing figures to end the conversation. S 45(2) and Section 46(7) figures are non-objectionable and final. Agree only numbers you have independently verified and can live with permanently; an agreed wrong number is a wrong number forever.
4. Optimistic instalment schedules. A plan must survive the worst month. Default accelerates, collapses the ITF 263 position, and — in the VDA Part D case — invalidates the disclosure relief entirely.
5. Missing the survival clauses. No agreement waives the tax (VAT Section 65(5) says it expressly) and Section 71(2) interest runs through almost everything. Price the agreement on what survives it, not on what it settles.
6. Breaching by silence. A payment that will be missed is renegotiated before its date. Approaching ZIMRA early is the difference between a varied agreement and a breached one.
7. Wrong signer, wrong scope. Agreements belong with payment-authoriser-grade roles, not with whoever happens to hold a submitter login; and an unexplained agreement on the register is an incident (Section 80J(1) notice, credential rotation, record) — the Roles lesson's drill applies.
8. No diary. Condition-subsequent agreements die of forgotten dates. Every instalment, review and expiry date goes into the compliance calendar the day the agreement is concluded.

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-Agreement is the SSP's home for the third family of instruments — mutual commitments, not declarations or applications — documented in the sources by one sentence ("manage … complete and submit"), with the page's inventory and workflow flagged .
• The platform layer makes e-agreements fully binding: Section 80E user agreements (the relationship's constitutional document, with the audit-access clause most never read), Section 80F(2) execution at registration, Section 80G sole-control signatures, Section 80I timing, Section 80C admissibility (PIL), Section 80J(3) attribution, Section 80K downtime fallback.
• The substantive layer is a family with shared DNA: Section 71(1) instalments (interest survives; clearance preserved), Section 45(2) agreed assessments (non-objectionable; PPC authority point; withheld-information re-opening), Section 46(7) agreed additional tax (final, full stop), VAT Section 65 compromise (bars prosecution; never the tax — Section 65(5)), VDA Part D (relief held on condition; breach invalidates).
• Read every agreement through three questions: what rights does it waive; what survives it; what re-opens or invalidates it. Then stress-test the schedule against the worst month, not the average one.
• Agreements often pay for themselves through the compliance grid: the interest an instalment plan costs is routinely dwarfed by the Section 80/ITF 263 working capital it protects.
• Authority and hygiene decide disputes: the Section 80J(3) presumption binds the credential's principal; role scoping, grant reviews, prompt notices and incident records are the rebuttal evidence — or, absent them, the reason the agreement stands.
• Honest record: no case law on the page or on TaRMS e-agreements; PIL, PPC and the debt-course negotiation lines carry the law. Procedural specifics await verification against the SSP help (unreachable this run).

The statutory agreements compared

Deciding whether to sign

flowchart TD
 A[Proposed e-agreement] --> B[Identify instrument + governing section]
 B --> C{What rights are waived?}
 C --> D{What survives: tax? interest? duties?}
 D --> E{What re-opens or invalidates it?}
 E --> F{Schedule survives the WORST month?}
 F -->|No| G[Renegotiate schedule before signing]
 F -->|Yes| H{Signer authorised - both sides?}
 H -->|No| I[Fix authority: role scope / proper ZIMRA channel]
 H -->|Yes| J[Execute; export PDF; minute; diarise every date]
 J --> K[Perform; renegotiate EARLY if a date is at risk]
 K --> L[On completion: Summary Report recon; retain 6 years]

Statutes & sections

• Income Tax Act [Chapter 23:06], Part VIIIA — Section 80C (admissibility of electronic records); Section 80D (computer systems); Section 80E (user agreements: prescribed form; equipment, signature allocation and security, manner of affixing, ZIMRA access to user systems, e-records); Section 80F(2) (completed user agreement accompanies registration application; Section 80F(4)–(5) suspension/cancellation with hearing); Section 80G (digital signatures: unique, sole control, per nominated employee); Section 80H (electronic retention); Section 80I (lodgement/receipt timing; signature equivalence); Section 80J (compromise notice; assumption; (3) presumption of authority); Section 80K (paper fallback).
• Income Tax Act [Chapter 23:06] — Section 45(2) (agreed assessments: non-objectionable; withheld-information proviso); Section 46(6)–(7) (remission; agreed additional tax final); Section 71(1)–(2) (instalments; interest); Section 37B (records).
• VAT Act [Chapter 23:12] — Section 65 (compromise of offences: agreed fine; PG approval post-institution; no conviction; bars prosecution; never exempts the tax (Section 65(5))); Section 66 (evasion additional tax context).

Case law

• PIL (Pvt) Ltd v ZIMRA 17-HH-213 — electronic records admissible with due weight (Section 80C).
• PPC v ZIMRA 19-HH-755 — the Section 45(2) agreement power is the Commissioner's and non-delegable; authority on ZIMRA's side matters.
• Mayor Logistics (Pvt) Ltd v ZIMRA 14-CC-007 — constitutional setting of the payment/recovery machinery within which instalment arrangements sit.
• Negotiation backdrop: PL Mines 15-HH-466; GC 15-HH-759; GFZ 19-HH-843; MR Bank 19-HH-779 (Section 46(6)); VSL 19-HH-023 and the E.J/V/R/G line (VAT Section 39(5)).
• No authority exists on the SSP E-Agreement page or TaRMS e-agreements — stated honestly.

ZIMRA guidance

• Comprehensive Guide to the ZIMRA Self-Service Portal — Tax Return Management (the E-Agreement page's one-sentence description: "manage e-agreements submitted on behalf of the taxpayer; complete and submit new e-agreements"); Debt Management (instalment plans lodged before due date).
• VDA01 Voluntary Disclosure guide (Part D plan as condition subsequent).
• Official SSP online help (https://mytaxselfservice.zimra.co.zw/help/ssp/en/default.htm) — unreachable this run; the page's agreement inventory, fields and workflow are flagged .