65B Certificate Rejected: 7 Common Mistakes and How to Avoid Them

Introduction: Why Courts Reject These Certificates

When electronic evidence is produced in an Indian court, the law expects a statutory certificate to accompany it — historically under Section 65B of the Indian Evidence Act, 1872, and now under Section 63 of the Bharatiya Sakshya Adhiniyam (BSA), 2023. In practice, the most common reason a party ends up with its 65B certificate rejected is not some exotic legal point — it is an avoidable defect in the document itself: the wrong person signs it, the device is described too loosely, a required statement is missing, or it is filed long after the fact. This article walks through seven recurring mistakes and how to avoid each. It is general information, not legal advice; whether any certificate is accepted is ultimately for the court to decide on the facts of the matter. For the underlying form, see our Section 65B certificate format with example and the Section 63 BSA 2023 electronic evidence certificate guide.

Mistake 1: Missing or Wrong Signatory

The certificate must be signed by a person occupying a responsible official position in relation to the operation of the relevant device or the management of the relevant activities — in plain terms, the person in charge of the computer or system from which the record was produced. A frequent error is having a convenient but unconnected person sign it: an advocate, a clerk, or a relative who never operated the device. How to avoid it: identify, before you draft anything, who actually controlled the device or activity, and have that person depose. If responsibility was shared, say so honestly rather than overstating one person's role.

Mistake 2: Vague Device Identification

"Taken from a mobile phone" is not enough. A certificate that cannot pin down which device produced the record invites doubt about whether the file in court is the file that was collected. How to avoid it: record concrete identifiers — make and model, IMEI or serial number, operating system, the application used, account or phone number where relevant, and the date and method of acquisition. Specificity is cheap to add at the time and very hard to reconstruct later.

Mistake 3: No Statement That the Computer Was Working Properly

The statutory scheme expects an assurance that, over the relevant period, the device was operating properly (or that any malfunction did not affect the accuracy of the record) and was regularly used to store or process information of that kind. Certificates often omit this entirely. How to avoid it: include an explicit statement addressing the device's proper functioning and its regular use, phrased to match what actually happened rather than copied verbatim from a template.

Mistake 4: Filed Too Late / Not Contemporaneous

Producing the certificate as an afterthought — drafted months later, near a hearing — weakens its weight and can attract objection. How to avoid it: prepare the certificate as close as possible to the time of collection, ideally when the data is acquired, and preserve the original media. Contemporaneous documentation is far more persuasive than a certificate assembled from memory after the dispute has crystallised.

Mistake 5: No Integrity Hash Linking the Certificate to the Exact File

Even a well-worded certificate can be undermined if there is nothing tying it to the exact bytes of the file produced. Without an integrity value, an opponent can ask how you know the file in court is the one the certificate describes. How to avoid it: compute a cryptographic hash (such as SHA-256) of the file at the time of certification and print it on the certificate, so the document and the file are verifiably bound. A tool such as e-Dex records multiple hashes per file, and anyone can re-check them on the certificate verifier later.

Mistake 6: Generic Boilerplate Not Matching the Facts

A certificate copied wholesale from a sample — describing a "server" when the source was a phone, or reciting activities that never occurred — reads as a form, not a sworn account, and is easily picked apart in cross-examination. How to avoid it: treat any template as a checklist of what to address, not text to reproduce. Every clause should reflect your actual device, your actual process, and your actual dates. A short, accurate certificate beats a long, generic one.

Mistake 7: Confusing an Affidavit with the 65B / 63 Certificate

An affidavit is a sworn statement of facts; the Section 65B / Section 63 certificate is a specific statutory document about the electronic record and the device. Filing one in place of the other, or assuming a general affidavit covers the statutory requirement, is a recurring confusion. How to avoid it: treat the certificate as its own distinct document with its own required contents. An affidavit may accompany it, but it does not replace it. Whether a given document satisfies the statute is, again, for the court to decide.

Frequently Asked Questions

Why do courts in India reject a Section 65B certificate?
Common reasons include the certificate being signed by someone who was not the person in charge of the device or relevant activity, vague identification of the source device, the omission of a statement that the computer was operating properly, the certificate being filed too late, generic boilerplate that does not match the facts, and no integrity value tying the certificate to the exact file produced. The list here is general information, not legal advice; whether any certificate is accepted is for the court to decide on the facts of the matter.

Who is the right person to sign a Section 65B or Section 63 certificate?
Broadly, the certificate should be signed by a person occupying a responsible official position in relation to the operation of the relevant device or the management of the relevant activities — typically the person in charge of the computer or system from which the electronic record was produced. A signatory with no real connection to the device is a frequent reason a certificate is questioned. Identifying the correct deponent in your specific matter is a legal question; this article is general information, not legal advice.

Does a Section 65B certificate need a hash value of the file?
The statute does not prescribe a hash, but recording a cryptographic hash such as SHA-256 alongside the certificate is good practice because it ties the certificate to the exact bytes of the file produced. Without an integrity value, it can be hard to show later that the file in court is the same file the certificate described. A tool such as e-Dex can compute and print these hashes so the certificate and the file are verifiably linked, and a verifier page lets anyone re-check them.

Is an affidavit the same as a Section 65B / Section 63 certificate?
No. An affidavit is a sworn statement of facts; the Section 65B / Section 63 certificate is a specific statutory document about the electronic record and the device that produced it. Filing an affidavit in place of the prescribed certificate, or assuming one covers the other, is a common confusion. Whether a particular document satisfies the statutory requirement is for the court to decide; this is general information, not legal advice.

Can e-Dex guarantee my electronic-evidence certificate will be admitted?
No. e-Dex helps you produce a well-structured certificate that records device details, the required statements and integrity hashes, and it runs offline on your own Windows machine. But no software can guarantee admissibility. Admissibility depends on the facts of the matter, how the evidence is tendered, and the current text of the law, and it is for the court to decide. e-Dex is a tool, not a substitute for legal counsel.

Conclusion

Most of the reasons a 65B certificate is rejected come down to avoidable defects: the wrong signatory, a loosely described device, a missing "working properly" statement, late filing, no integrity hash, generic boilerplate, or confusion with an affidavit. Getting these right is a matter of discipline at the time of collection, not legal wizardry — and the integrity hash, at least, can be handled for you. Download e-Dex free to compute and print per-file hashes and produce a structured, integrity-backed certificate offline on your own Windows machine. Remember: this article is general information, not legal advice, and admissibility is always for the court to decide.