Skip to content

Signatures: what counts and what does not

  • Home
  • Blog
  • Signatures: what counts and what does not
Signatures: what counts and what does not

For electronic signature validity in Nepal, the test is not whether a name appears on a screen but whether you can prove four things: who signed, that they meant to be bound, that the signing method was under their sole control, and that the document has not changed since. Nepal's Electronic Transactions Act, 2063 (2008) recognises this — with carve-outs.

Key Takeaways

Nepal's Electronic Transactions Act, 2063 (2008) treats an electronic signature as valid when it identifies the signer, shows intent, stays under the signer's sole control and detects tampering. Scanned images pass none of those tests reliably; certificate-based digital signatures pass all of them. The gap between the two is evidence, not technology.

  • Validity rests on evidence. A signature holds up when you can prove identity, intent, control and integrity after the fact.
  • A scanned image is not a digital signature. It is a picture anyone can copy, with no cryptographic link to the document.
  • Some documents stay on paper. Wills, powers of attorney, negotiable instruments and property transfers generally still require wet ink.
  • The audit trail beats the signature style. Timestamps, hashes and identity records win disputes more often than the logo on the signing tool.
  • Certificates expire and get revoked. Validity is judged at signing time, so verify the dates, not just the badge.
  • Keep records as long as a claim could live. A signature you cannot re-verify years later protects nobody.
Five tests an electronic signature must pass in NepalOrdered stages from proving the signer's identity to retaining the audit evidence, connected by arrows.Five tests a signature must pass1Identifythe signerID check2Intent tobe boundassent shown3Solecontrolkey is theirs4Integrity(hash check)tamper-evident5Retain theevidencetrail + storeAll five must hold at once. Miss one, and a challenge has a place to land.
The five tests behind electronic signature validity in Nepal, running from proving who signed to keeping the audit evidence retrievable years later.

What counts as a valid electronic signature in Nepal?

Nepal recognises an electronic signature through functional equivalence: the law asks what the signature achieves, not which technology produced it. Under the Electronic Transactions Act, 2063 (2008), a method counts when it identifies the signer, signals assent, remains under that person's sole control and reveals any later alteration. No specific vendor or format is mandated.

In practice that means the law is technology-neutral, but it is not evidence-neutral. A certificate-based digital signature uses a cryptographic key pair and an X.509 certificate issued by a certifying authority licensed under the Act; it satisfies the four tests almost by construction. A typed name in an email might satisfy them, if the surrounding records prove who held the account and who clicked send. The signature itself is only half the artefact — the other half is everything you can show about the moment it was made.

Is a scanned signature or a typed name actually valid?

A scanned signature image or a typed name can be an electronic signature, but it proves little on its own. Anyone can copy a photograph of your signature in seconds, and a typed name carries no cryptographic link to the document. For anything valuable, treat both as weak evidence that needs a supporting trail.

Here is the distinction worth memorising. A digital signature is the document's hash, encrypted with the signer's private key; change one comma and the hash stops matching, which any validator can detect. A scanned signature is a bitmap pasted into a PDF — detachable, reusable and blind to edits. Email acceptance sits in between: courts in many jurisdictions accept a contract concluded over email because identity and intent can be inferred from the thread, and that reasoning applies to low-value Nepali commercial dealings too. We would not push a five-year supply agreement through on a pasted image, though. A common mistake we see is treating the badge on a PDF viewer as proof, when what matters is the certificate and hash underneath.

Which documents still need a wet-ink signature in Nepal?

Several document categories sit outside electronic signing in Nepal. Wills, powers of attorney, negotiable instruments such as cheques, and transfers of immovable property generally still require physical execution, and registries or banks often insist on original signed papers regardless of what the Act allows. Confirm the category before you digitise the workflow.

The practical corollary: even where the law permits an electronic form, a counterparty's process may not. Land revenue offices, notaries and some government portals still run on stamped paper. Plan a hybrid path for those flows rather than forcing everything digital — and note that we are engineers, not lawyers, so for a specific high-stakes transaction, confirm the category with Nepali counsel. If your signature questions extend to invoices and what the tax office accepts, we cover that separately in our guide to electronic billing and invoicing compliance.

How do you make an electronic signature defensible in a dispute?

Defensibility comes from the evidence you capture around the signature, not the signature itself. Match the strength of the method to the value of the contract, verify who the signer is, bind the signature to the exact final document, and keep an audit trail that a third party can later inspect without your help.

  1. Pick the method to match the risk. A purchase order and a distributorship agreement deserve different levels of proof.
  2. Prove identity once, properly. A certificate issued after ID verification, or a verified email plus one-time password for lower stakes.
  3. Sign the final artefact. Freeze the PDF first; a signature on a draft that later changes verifies as invalid.
  4. Capture the trail. Timestamp, signer's verified email, source address, and the document's hash at signing time.
  5. Store tamper-evidently. Keep the signed copy, the certificate and the trail together, on storage nobody can quietly edit.
  6. Re-verify on retrieval. Before you act on any signed document, run the checks in the next section.

That list costs hours to set up and almost nothing per document afterwards. Skipping it costs a lawsuit.

How do you verify a signature on a PDF you have been sent?

Verification checks three things: that the document's hash still matches the value signed at signing time, that the certificate chains back to a certifying authority you trust, and that the certificate was valid on the signing date, not merely today. Adobe Acrobat's signature panel reports exactly these; OpenSSL reports the certificate facts directly.

# Inspect who issued the certificate and whether it is still current
openssl x509 -in signer-cert.pem -noout -subject -issuer -dates

# Check the chain up to a root you already trust
openssl verify -CAfile trusted-chain.pem signer-cert.pem

In Acrobat, open the signature panel and look for "signed and all signatures are valid". A warning that the document has been altered, or that the certificate has expired, means stop and ask questions before you ship the goods. Expiry judged at signing time is the detail people miss: a certificate that expired last month does not poison a signature applied while it was live.

Why do electronic signatures fail in a dispute?

Most failed electronic signatures lose on identity or intent, not technology. The document was altered after signing, the certificate had already expired, the email account was shared, or the signature landed on a draft that later changed. Each defect is detectable in advance with the checks above, which is why disputes reward preparation.

  • Shared identity. Signatures made from a company inbox used by three people prove nothing about who assented.
  • Broken integrity. The file was edited after signing; the hash no longer matches and every validator flags it.
  • Wrong timing. The certificate was expired or revoked when the signature was applied.
  • Excluded category. The document — a property deed, a cheque — never qualified for electronic form at all.
  • No authority. The person signing could not bind the company; a company seal is not the same as an authorised signatory.
  • No intent evidence. A bare click with no trail invites the defence that nobody read, let alone agreed to, the terms.

What does signature compliance cost to keep running?

The ongoing cost of signature compliance is operational, not just financial. Certificates expire and need renewal, private keys need custody arrangements, audit records grow every year, and somebody has to own the verification step before payments or shipments move. Budget engineer or administrator time for this; a method nobody maintains quietly rots.

The big cost driver is key custody. Individual signing keys can live on a smart card or a hardware security module, or the certifying authority can hold the key on your behalf — each option trades convenience against control, and you should weigh who on your team will actually operate it. Add certificate renewal to a calendar, decide how long you retain signed records, and confirm current certificate fees directly with the issuing authority rather than trusting second-hand figures.

Where the security risks sit

  • Key theft means someone can sign as you — use hardware custody and never share the key.
  • Skipping revocation checks means trusting a certificate the authority has already cancelled.
  • Phishing for signing credentials is now routine; treat signing access like bank access.
  • Company certificates used without a log let an insider sign untraceably.
A signature you cannot re-verify in five years is a rumour, not a record.

What does this look like in practice?

A Kathmandu distributor signs annual purchase agreements with an Indian supplier. One year the supplier disputes an amendment, claiming its manager never signed. The distributor's copy carries a certificate-based signature with a timestamp and audit trail; the supplier's counter-copy carries a pasted image of a signature. The case turns on which side can prove its record is intact.

The distributor runs a verification check, the hash matches the signed value, the chain resolves, the dates line up. The supplier cannot demonstrate anything except that a picture of a signature exists. Document-heavy businesses live or die by this — we have built web systems for a legal practice, Moksha Legal Group, and the lesson there is the same: the record is the product, not the paperwork.

Life of a signed agreement, from signature to challengeA horizontal timeline marking signing, tamper-evident storage, verification, certificate renewal and a dispute.Life of a signed agreementSignedtimestamp + trailStoredtamper-evident copyVerifiedchain + dates checkedRenewedbefore expiryChallengedtrail proves itEvery step after the signature is evidence-gathering for a day you hope never comes.
A timeline showing what happens after signing: storage, verification, certificate renewal and the moment an audit trail has to answer for the agreement.

Which signing method should your business use?

Choose by contract value and dispute probability, not by convenience. Typed consents with a good trail cover low-value, high-volume flows; certificate-based signatures earn their setup cost on high-value or cross-border agreements; scanned images should be reserved for internal records where no dispute is plausible. Anything touching land, courts or negotiable instruments stays on paper.

Which signing method fits which documentRows mapping each signature type to the documents it suits and the risk it carries.What holds up — and for whatTypedLow-value, high-volume consent with a verified email trailScannedInternal records and informal notes — never a disputePlatformCommercial contracts where the audit trail must survive scrutinyCertificateHigh-value and cross-border agreements; regulated filingsMatch the method to the document's value and the likelihood anyone ever challenges it.
How the common signing methods map to document type, value and dispute risk, from typed consents to certificate-based digital signatures in Nepal.
MethodWhat it provesReasonable forMain weakness
Wet ink + courierOriginal, physical executionExcluded categories, notarised papersSlow; originals get lost
Scanned image in a PDFAlmost nothing by itselfInternal records, filing copiesCopied freely; no tamper detection
Typed name / click-to-acceptAssent, if the trail is keptTerms acceptance, routine ordersIdentity is inferable, not proven
International e-sign platformIdentity steps plus an audit trailCross-border commercial contractsConfirm enforceability and data residency for Nepali parties
Certificate-based digital signatureIdentity, intent, control, integrityHigh-value and regulated documentsKey custody and renewal must be owned

In short

In short: an electronic signature is valid in Nepal when the evidence around it proves identity, intent, control and integrity. Scanned images and bare typed names rarely carry that proof; certificate-based digital signatures with audit trails do. Match method to contract value, verify before you rely, and keep the records for as long as a claim could live.

People also search for

Signature validity questions sit next to invoicing, account ownership and software contracts, so readers usually arrive from — or leave for — those topics. Each query below links to a guide we have published; if the exact question is not there, the blog index is the next stop for doing business online from Nepal.

If your contracts, approvals or invoices depend on signatures that would not survive a challenge, our team can help you put a defensible workflow in place — the signing method, the audit trail and where the records live. Tell us what you are signing today, or see our custom software development work for document-heavy systems.

Frequently asked questions

  • Yes. The Electronic Transactions Act 2063 (2008) gives electronic records and signatures the same legal effect as their paper equivalents, so a document cannot be dismissed solely for being electronic. What matters in practice is proof: the stronger the link between the signature and the signer, the better it survives a challenge in court.

  • Electronic signature is the umbrella term: a typed name, a click-to-accept checkbox, a scanned image or a cryptographic mark can all qualify. A digital signature is one specific type, built on public-key cryptography and a certificate from a certifying authority that binds a key pair to a verified identity. Digital signatures carry far more evidentiary weight.

  • The Act excludes certain instruments from electronic form, following the pattern of most e-transaction laws: negotiable instruments such as cheques, powers of attorney, wills, trusts and contracts for the transfer of immovable property. Land transactions still run through the Land Revenue Office with wet-ink signatures. Check the Act's schedule for the current list before planning any paperless workflow.

  • Only a certifying service provider licensed by the Controller of Certification, who regulates certifying authorities under the Electronic Transactions Act. The provider verifies your identity, issues the certificate and charges an issuance fee plus annual renewal. Licensed providers and their fee schedules change, so confirm the current list with the Controller's office before you commit.

  • It is evidence, but weak evidence. A scan proves a document existed with a mark on it; it cannot show who applied the mark or that the page has not been altered since. Nepali courts weigh the surrounding record, including the email trail, delivery confirmations and metadata. Treat scans as a stopgap and keep every supporting artefact.

  • The Act does not require a Nepali-issued certificate for an electronic signature to have effect, so a foreign-platform signature can still serve as evidence. Its strength depends on whether it meets the Act's secure-signature criteria and on the platform's audit trail. For high-value local agreements, pair it with a locally issued digital signature where available.

  • The Act's secure-signature test asks whether the signature-creation data is unique to the signer and under their sole control, and whether any change to the signature or the document after signing is detectable. A certificate-based digital signature satisfies this by design. A typed name or an image of a signature does not, on its own.

  • The Act recognises offers and acceptances expressed through electronic records, so a contract formed by email or messaging can be binding. The practical risk is attribution: proving which account sent the message and that an authorised person sent it. Keep complete exports with headers and timestamps, and confirm significant agreements through a formally signed document.

  • Open it in Adobe Acrobat or Reader and check the signature panel: it reports whether the document matches the bytes covered by the signature, whether the certificate chains to a trusted authority and whether the certificate is still valid. Any change after signing breaks the check, and the panel shows the document as modified.

  • The evidentiary burden falls on you. Without an audit trail of timestamps, IP addresses, OTP or login checks and the counterparty's acceptance emails, a typed name or drawn mark is difficult to prove. Prevention is cheaper than litigation: use a platform that records every step, and reserve simple signatures for low-value, low-risk documents.

0 comments

Be the first to share your thoughts.

Leave a comment

Chat on WhatsApp