Wakilii
HomeKnowledge › Electronic contracts and e-signatures in Uganda

Electronic contracts and e-signatures in Uganda

Practice note Contracts Updated 6 July 2026 17 min read AI-assisted · review recorded

In brief

Electronic contracts are valid. Under the Electronic Transactions Act, Cap. 99, information and contracts are not denied legal effect merely because they are in electronic form (s.5(1)), and a contract concluded by data message is made when and where acceptance is received (s.14). Only a short, specific list of documents is excluded — wills and codicils, trusts created by a will or codicil, powers of attorney, documents creating or transferring a property interest that require registration to bind third parties, and negotiable instruments (Schedule 2) — not 'land dealings' generally. Electronic signatures are recognised under the Electronic Signatures Act, Cap. 98, with two distinct routes: an 'advanced' signature backed by a qualified certificate (s.10), and a lower-bar 'secure' signature satisfied by a reliable procedure without needing a licensed certification provider (s.11). Case law testing either Act is genuinely thin.

1. At a glance

What this note covers

Electronic contracts and electronic signatures are both recognised under Ugandan law. This note covers the general legal-effect rule, the real (short and specific) list of excluded documents, the separate question of proving an electronic contract in court, and the practical fork between 'advanced' and 'secure' e-signatures that most platforms and advocates need to navigate.

It is written for a business or advocate structuring electronic contracting or e-signature workflows — sales terms accepted online, contracts signed via a click-to-sign or OTP-verified platform, documents exchanged by email. It does not cover consumer-protection rules for online sales specifically, data-protection obligations around the personal data collected during e-signing, or sector-specific electronic filing regimes (for example tax or company-registry e-filing), which need separate advice.

No 2023 consolidation — these Acts are static

Unusually for this project, there is no 2023 Revised Edition consolidation to flag here — both the Electronic Transactions Act, Cap. 99 and the Electronic Signatures Act, Cap. 98 remain, as far as could be verified, in their original 2011 as-enacted form. That is itself a notable fact: these two statutes have gone unamended for over a decade while surrounding technology and commercial practice have moved a great deal further.

2. The general rule: electronic form does not defeat legal effect

Section 5(1) of the Electronic Transactions Act states the broad principle underlying the whole Act: information shall not be denied legal effect, validity or enforcement solely on the ground that it is wholly or partly in the form of a data message. This is the general rule; s.14 is its specific application to contracts, providing that a contract shall not be denied legal effect merely because it is concluded partly or wholly by means of a data message. Reading the two together matters for drafting an essay or an opinion: s.5(1) establishes the policy, s.14 gives contracting parties the specific rule they actually need.

Section 14(2) adds a genuinely practical rule: a contract concluded by data message is made at the time when, and the place where, acceptance of the offer is received by the person who made the offer. This displaces any argument that an electronic acceptance should be treated differently from a postal or instantaneous-communication acceptance — the statute simply fixes the moment and place of formation at receipt.

3. The real exclusions: Schedule 2, not 'land dealings' generally

The Act does not apply at all to a short, specific list of documents set out in Schedule 2, given effect by s.3(1). This list is considerably narrower and more precise than a generic 'land dealings and wills are excluded' summary suggests, and getting the wording right matters — a client should not be told that electronic form is unavailable for a category of document that is not actually on this list.

  • A will or codicil.
  • A trust created by a will or codicil.
  • A power of attorney.
  • A document that creates or transfers an interest in property and requires registration to be effective against third parties.
  • Negotiable instruments, including negotiable documents of title.

The property exclusion is narrower than it looks

The property exclusion is narrower than 'all land dealings'. It is keyed specifically to a document that creates or transfers a property interest AND requires registration to be effective against third parties — tracking the Land Act/Registration of Titles Act registration regime. On a literal reading, a land document that does not itself need registration to bind third parties would fall outside the exclusion, though in practice most substantive land dealings do require registration and so remain outside electronic form for that reason.

Two exclusions that appear in other UNCITRAL Model Law-style statutes are notably absent from Uganda's list: there is no court-documents exclusion and no dangerous-goods-transport-documents exclusion. Do not assume either exists in Uganda's framework.

Section 3(2) is a savings clause: nothing in the Act limits the operation of any other law that expressly authorises, prohibits or regulates the use of electronic documents. This preserves sector-specific rules — for example a regulator's own electronic-filing regime — independently of the Schedule 2 list. Section 36 gives the Minister power to amend the Schedules by statutory instrument with Cabinet approval; no amending instrument was found to have issued since 2011.

4. Two different questions: is it valid, and can you prove it

Section 14 answers whether an electronic contract is legally valid. A separate, distinct question is whether it can be proved in court once a dispute arises — and that question is answered by s.8, which deals with the admissibility and evidential weight of a data message.

Section 8 provides that rules of evidence must not deny admissibility to a record merely because it is a data message, or is not in its original form; it places the burden of proving authenticity on the party adducing the record; it treats the best-evidence rule as satisfied by proof of the authenticity of the records system that generated the message; and it creates rebuttable presumptions of authenticity in specified circumstances. Importantly, s.8(7) states that the section does not modify the common law or any statutory rule on admissibility of records, except the rules relating to authentication and best evidence — a narrow evidentiary carve-out, not a wholesale override of the ordinary rules of evidence.

Validity and admissibility are separate questions

A contract can be perfectly valid under s.14 and still run into real difficulty being admitted and given weight in court under s.8 if the party relying on it cannot establish the authenticity of the data message or the reliability of the system that generated it. Advise clients on both questions separately: draft and contract for validity, but also build a genuine evidentiary trail (system logs, timestamps, retained originals) for proof.

5. Equal treatment of signature technologies

The Electronic Signatures Act opens with a technology-neutral principle at s.3: nothing in the Act is to be applied so as to exclude, restrict or deprive of legal effect any method of creating an electronic signature that satisfies the Act's requirements, or otherwise meets the requirements of any other applicable law. This is deliberately open-ended — the Act does not mandate a single signature technology, and a new signing method is not automatically disqualified simply for being unfamiliar.

Section 4 then sets the baseline test: where the law requires a signature, that requirement is met by an electronic signature that is as reliable as was appropriate for the purpose for which the data message was generated or communicated, in light of all the circumstances, including any relevant agreement between the parties. Section 4(3) unpacks that reliability standard into a four-factor test: the signature creation data must be linked, within the context used, to the signatory and to no other person; the signature creation data must have been under the signatory's sole control at the time of signing; any alteration to the signature made after signing must be detectable; and, where integrity of the underlying information is a purpose of the signature requirement, any alteration to that information after signing must be detectable.

Worked example: arguing reliability beyond the checklist

Section 4(4) makes the four-factor test in s.4(3) expressly non-exhaustive: it does not limit a party's ability to establish reliability by some other means, or to challenge reliability with contrary evidence. Picture an OTP-verified click-to-sign platform used for a UGX 8 million services agreement: even if the platform cannot point to every element of the four-factor list in a textbook-perfect way, a party can still argue reliability 'in light of all the circumstances' — for example, that the OTP was sent only to the signatory's registered phone number, that the platform logged the IP address and timestamp, and that the parties had expressly agreed in their engagement letter to treat that platform's signatures as binding.

6. The practical fork: 'advanced' versus 'secure' signatures

The Act creates two genuinely different routes to a legally effective electronic signature, and the choice between them has real practical consequences for how a commercial e-signature platform should describe its own product.

Advanced electronic signatures (s.10)

An advanced electronic signature is verified with a qualified certificate and is given full legal equivalence to an autographic (handwritten) signature. This route depends on Uganda's licensed certification-service-provider (CSP) and public-key-infrastructure regime under Part IV of the Act — a formal accreditation structure, not a signature technology a business can simply adopt on its own.

Secure electronic signatures (s.11)

A secure electronic signature is a different, lower bar — a fact-based, behavioural test satisfied where a prescribed security procedure, or a commercially reasonable security procedure the parties agreed to, produces a signature executed in a trustworthy manner and reasonably relied on, tested against criteria including uniqueness, identifiability, sole control, and tamper-evidence. Critically, this route does NOT require a licensed certification-service provider or a qualified certificate at all.

Most platforms should be arguing 'secure', not 'advanced'

As far as could be established in this research, no active, publicly known NITA-U-licensed certification-service-provider register was found — flag this as an unverified point either way (this is an absence-of-evidence finding, not a confirmed statement that no such provider exists). On that basis, most Ugandan commercial e-signature platforms — click-to-sign services, OTP-verified signing tools — will realistically be arguing 'secure electronic signature' status under s.11, not 'advanced' status under s.10, because the advanced route depends on infrastructure whose active operation could not be confirmed. Draft platform terms and client advice around the s.11 reliability test rather than assuming s.10-level certification is realistically available.

Section 12 attaches rebuttable presumptions to both categories: in civil proceedings, a secure or advanced electronic record is presumed unaltered since the relevant point in time, and a secure or advanced signature is presumed to be that of the person to whom it correlates, affixed with intent to sign or approve the record. Both presumptions are rebuttable, with the burden of both raising the challenge and persuading the court placed on the party disputing genuineness (s.12(4)) — a meaningful practical advantage for the party relying on a secure or advanced signature in a dispute.

No separate exclusions schedule exists in the Electronic Signatures Act — its only schedule concerns the currency-point definition. The Schedule 2 excluded-documents list discussed above is an Electronic Transactions Act concept only. That does not create a gap: those categories (wills, powers of attorney, registration-dependent property documents) are already outside the Transactions Act's scope for contract-formation purposes, and to the extent any of them requires a specific signature form under other law (for example a will's attestation requirements), that other law's formality rules simply are not displaced by the equal-treatment principle in s.3.

7. How the courts have treated electronic contracts and signatures

This is the most honest section a practitioner can be given on this topic: no verified Ugandan case squarely deciding electronic contract formation or e-signature validity in a commercial dispute could be found in this research, despite a dedicated search. That thinness is independently corroborated by academic commentary — Paul Mukiibi's 2023 article on the admissibility of electronic signatures under the Electronic Signatures Act (African Journal of Legal Issues in Technology and Innovation, Vol. 1 No. 1) frames its own contribution around the observation that, more than a decade after enactment, Ugandan case law and institutional practice under the Act remains thin. That article's own live concern is affidavits and statutory declarations, not commercial contracting — but its central finding, that this area is genuinely undertested in the courts, corroborates the same conclusion reached independently in this note's own research.

Be honest about the thin case law

State this plainly to a client rather than manufacturing false confidence: Uganda's electronic-transactions framework is comprehensive and modelled on the UNCITRAL Model Law, but remains substantially untested by Ugandan courts in a commercial contract-formation or signature-validity dispute. That is itself a useful, honest fact for a practitioner and their client to know before relying heavily on either Act in a high-value transaction.

This note also actively checked, and rejects, one specific citation that circulates in secondary sources. A law firm client alert cites Sematimba Peter Simon v Sekigozi Stephen as authority on electronic signatures and notarisation. The actual judgment — Sematimba Peter v Sekigozi, [2017] UGCA 28, Court of Appeal — was independently checked and is an election-petition appeal concerning the authentication of a decades-old foreign academic certificate via consular and diplomatic signature and seal. It contains no mention of electronic signatures, data messages, or either Act. See grey areas below.

8. Consequences of getting it wrong

Treating a genuinely binding electronic exchange as non-binding — for example telling a client an emailed acceptance 'doesn't count' — can cost a business a valid contract it should have been enforcing, or expose it to a claim it wrongly believed did not exist.

The opposite mistake is equally costly: relying on electronic form for a document that Schedule 2 actually excludes — a power of attorney, or a property document requiring registration to bind third parties — produces a document with no legal effect under this Act at all, however carefully the electronic signing process was executed.

A third, subtler risk sits at the validity/proof boundary: a business can build an electronically valid contract under s.14 and still lose a dispute because it cannot satisfy s.8's authenticity and best-evidence requirements — for example, if it cannot show the reliability of the records system that generated and stored the data message. Winning the validity argument and losing the proof argument produces the same practical outcome as never having a contract at all.

9. Practical guidance and drafting tips

Check Schedule 2 before building the workflow

Before building or relying on any e-signature workflow, check the document type against Schedule 2 first. If it is a will, a trust created by a will, a power of attorney, a registration-dependent property document, or a negotiable instrument, electronic form under this Act is simply unavailable — route it through traditional execution instead.

Contract expressly for the s.11 security procedure

For a commercial e-signature platform or a client relying on one, draft the engagement or platform terms to expressly agree a 'commercially reasonable security procedure' under s.11 — naming the specific verification steps used (OTP to a registered number, IP/timestamp logging, document-hash sealing). This gives a direct, contractual hook into the s.11 reliability test rather than leaving reliability to be argued from scratch after a dispute arises.

Keep the full audit trail, not just the final file

Retain the underlying data messages, signing logs, and system records — not just the final signed document. Section 8's authenticity and best-evidence rules turn on being able to show the reliability of the records system, which is far easier to do with the full audit trail than with the signed PDF alone.

10. Common pitfalls

  • Assuming electronic contracts and signatures are broadly untested law-in-name-only — s.5(1) and s.14 give them real legal effect; the honest caveat is about case law testing edge cases, not about basic validity.
  • Assuming 'land dealings' are excluded wholesale — the actual exclusion is narrower, keyed to registration-required-for-third-party-effect (Schedule 2(d)).
  • Claiming 'advanced electronic signature' status for a platform that has no qualified certificate or licensed certification-service-provider backing it — that claim should realistically be pitched at 'secure' status instead (ss.10-11).
  • Conflating a contract's validity (s.14) with its provability in court (s.8) as if they were the same question.
  • Citing Sematimba v Sekigozi, or any of the secondary-sourced-only electronic-evidence cases, as authority on electronic signatures without independent verification.

11. Grey areas and points to confirm

Sematimba Peter Simon v Sekigozi Stephen (Election Appeal No. 8 of 2016; the actual decision is [2017] UGCA 28) circulates in at least one law-firm client alert as authority on electronic signatures and notarisation under 's.11 Electronic Transactions Act'. This is wrong: the judgment is an election-petition appeal about authenticating a decades-old foreign academic certificate through consular and diplomatic signature and seal, and contains no mention of electronic signatures, data messages, or either Act. Treat this citation as debunked if it appears in any other source, and do not repeat it.

A handful of other electronic-evidence-admissibility cases are sometimes cited alongside electronic-signature discussions — including Coil Ltd v Attorney General, Amongin Jane Francis Okili v Lucy Akello and the Electoral Commission, Uganda v Sserunkuma and 8 Others, and Twaha Sebbi Olegga v Alidriga Adinan. These were sourced only via a secondary law-firm summary in this research, could not be independently fetched, and concern general Evidence Act admissibility (mostly election petitions and one criminal case) rather than contract formation or signature validity specifically. They are not cited in this note's substantive analysis and should not be relied on without independent primary verification.

Whether an active, publicly known NITA-U-licensed certification-service-provider register exists — which would make the 'advanced electronic signature' route under s.10 practically available — could not be confirmed either way in this research. This is an absence-of-evidence finding, not a statement that no such provider exists; confirm the current position with the relevant regulator before advising a client that the advanced route is (or is not) realistically available.

The genuine thinness of Ugandan case law testing either Act — corroborated by Mukiibi's 2023 academic article — means every proposition in this note about how a court would actually apply s.4's reliability test, or resolve an s.8 authenticity dispute, is drawn from the statutory text itself rather than from a body of decided cases. Advise clients accordingly, particularly for a high-value transaction where an untested legal question could matter a great deal if it is ever litigated.

12. Practitioner checklist

  1. Confirm the document is not on the Schedule 2 exclusions list (will/codicil, trust created by a will, power of attorney, registration-dependent property document, negotiable instrument) before using electronic form.
  2. Confirm the electronic exchange shows a clear offer and acceptance, and note the time and place acceptance was received (s.14).
  3. Choose and document the signature route deliberately: 'advanced' (qualified certificate, full handwritten-signature equivalence) or, more realistically, 'secure' (a documented, commercially reasonable security procedure) (ss.10-11).
  4. Build the s.4(3) reliability factors into the signing process design — link the signature to the signatory alone, keep it under their sole control, and make post-signing alteration detectable.
  5. Retain the full audit trail (logs, timestamps, system records), not just the signed document, to meet s.8's authenticity and best-evidence requirements if the contract is ever challenged.
  6. Treat validity (s.14) and admissibility/proof (s.8) as two separate checks, not one.
  7. Do not cite Sematimba v Sekigozi or the other secondary-sourced-only cases as electronic-signature authority.

13. Sources and further verification

Every statutory reference in this note is to the Electronic Transactions Act, Cap. 99 (2011 Act 8) and the Electronic Signatures Act, Cap. 98 (2011 Act 7), both in their as-enacted 2011 form — no later consolidation was found for either. Given the thin case law, treat every proposition in this note as a reading of the statutory text, and re-verify against the current ULII text before filing or advising on a live, high-value matter.

  • Electronic Transactions Act, Cap. 99 — ss.3, 5(1), 8, 14, 36, Schedule 2.
  • Electronic Signatures Act, Cap. 98 — ss.3, 4, 10, 11, 12.
  • Statutory text verified against the Electronic Transactions Act, Cap. 99 and the Electronic Signatures Act, Cap. 98, as enacted in 2011 — no 2023 Revised Edition consolidation of either Act could be located. Sourced from the Uganda Legal Information Institute (ulii.org).
Was this practice note helpful? Your feedback helps us improve.
Last updated: 6 July 2026.
Next currentness review: 17 August 2027.
This note is a practitioner orientation, not legal advice, and does not create an advocate–client relationship. Ugandan law changes and chapter and section numbers were revised in the 2023 Laws of Uganda. Verify every statute, rule and authority against the current primary source — and the specific facts of your matter — before filing or relying on it.