Bar Council of India Notice

Disclaimer & Confirmation

As per the rules of the Bar Council of India, an advocate is not permitted to solicit work or advertise. By clicking “I Agree” below, you acknowledge and confirm that:

you are seeking information about Advocate Manish Jha of your own accord and for your own information and use; there has been no advertisement, personal communication, solicitation, invitation or inducement of any kind whatsoever from Advocate Manish Jha or the chamber to solicit any work through this website; the information made available here is provided only on your specific request; and no information on this website is to be construed as legal advice, nor does its use create any advocate-client relationship.

⚖  E-397, 4th Floor, Tagore Garden Extension, New Delhi – 110027 Mon–Sat  ·  +91 98738 50301  ·  legal@advocatemanishjha.com
Advocate Manish Jha Criminal · Civil · Family Law — New Delhi ☎  Consult the Chamber
Home › Evidence — Electronic Records
Practice Explainer · 26 September 2026

Proving Electronic Records In Commercial Litigation: Section 63 BSA After Section 65B

Commercial cases are now decided on emails, chats and system data. The Bharatiya Sakshya Adhiniyam, 2023 carries forward the certificate regime for electronic records — with a tightened format that parties ignore at the cost of their best evidence.

Ask what actually proves a modern commercial case — a supply dispute, a recovery suit, an arbitration over project delays — and the answer is rarely a witness’s memory. It is the email fixing the deadline, the WhatsApp message acknowledging the debt, the ERP entry recording delivery. All of these are electronic records, and none of them proves itself. Section 63 of the Bharatiya Sakshya Adhiniyam, 2023, the successor to Section 65B of the Evidence Act, prescribes exactly how such records enter evidence — and the printout without its certificate remains the most common self-inflicted wound in commercial trials.

The architecture: original versus output

The law distinguishes the electronic record itself — the data on the server, phone or drive — from the outputs by which litigants actually use it: printouts, PDF exports, forensic copies. The record in its native environment is primary; the outputs are admissible in its place only through the statutory gateway. Section 63 of the BSA supplies that gateway, deeming the output a document — admissible without production of the original device — where its conditions are satisfied and the certificate accompanies it. The conditions track the familiar Section 65B logic: the device was regularly used for the relevant activity, the information was regularly fed into it in the ordinary course, the device was operating properly (or its malfunction did not affect the record), and the output reproduces information so fed.

What changed with the BSA

Section 65B, Evidence Act

Certificate by a person occupying a responsible official position in relation to the device; no prescribed form; hash values a matter of good practice.

→
Section 63, BSA 2023

Certificate in the form prescribed in the Schedule, contemplating signature by the person in charge of the device or relevant management and an expert, with hash-value authentication of the record built into the format. Semiconductor memories and communication devices expressly covered.

The substance of admissibility has not been relaxed anywhere: the certificate remains a condition of admissibility for secondary outputs of electronic records, not an ornament. Commercial parties should treat every disclosed email chain, chat export and system report as incomplete until its certificate is on the file.

Building a compliant record, transaction by transaction

Identify the source. For each electronic document in the disclosure list, record where it lives: which mailbox, which phone, which server, whose custody. The certificate must describe this, and vagueness here is what cross-examination feeds on.
Extract forensically where stakes justify it. For the documents on which the case turns, export in native format, generate hash values at extraction, and note date, time and operator. For phone chats, a full export with media beats screenshots every time.
Prepare the Schedule-form certificate. Signed by the person in charge of the device or the relevant activity’s management and by an expert, identifying the record, the manner of production and the device particulars, with the hash values stated.
File certificate with the record. In commercial suits, the disclosure regime expects the documentary case up front; the certificates belong with the documents, not with the closing arguments.

The recurring failure modes

Three patterns account for most electronic-evidence casualties in commercial trials. The first is the orphan printout — an email or ledger filed without any certificate, objected to at the evidence stage, with the trial court then asked to decide the suit while its central document hangs in admissibility limbo. The second is the wrong certifier — a certificate signed by counsel’s clerk or a director with no relationship to the system, which collapses on the first question in cross-examination. The third is the eve-of-trial certificate for a system that has since been replaced, where the signatory cannot honestly attest to the device’s operation years earlier. Each failure is avoidable by the same habit: certify at extraction, when the facts are fresh and the system is alive.

This article is for general information only and is not legal advice or a solicitation.

Frequently Asked Questions

What does Section 63 BSA actually require?

Information from a computer or communication device becomes admissible as a “document” through its printout or copy only if the statutory conditions about the device’s regular use and proper operation are met, and the record is accompanied by a certificate in the prescribed form identifying the record, describing how it was produced, and giving the device’s particulars.

Who signs the certificate under the new law?

The Adhiniyam’s Schedule format contemplates the certificate being signed by the person in charge of the computer or communication device or the management of the relevant activities, and by an expert, and it provides for hash-value authentication of the record. This is a tightening of the older single-signatory practice, and certificates should follow the Schedule’s format.

When should the certificate be prepared?

At the time the record is extracted — not on the eve of evidence. Contemporaneous certification, with hash values generated at extraction, forecloses tampering arguments and spares the party the scramble of locating, years later, someone competent to certify a defunct system.

Do these rules apply in arbitration?

Arbitral tribunals are not strictly bound by the Evidence Act or its successor, but tribunals and the courts that scrutinise awards take authenticity seriously, and the Section 63 discipline is the accepted gold standard. Certifying electronic records in arbitration is inexpensive insurance for the award’s enforceability.

Note: This article is general information about the law and is not legal advice. It does not create an advocate-client relationship. The position stated is as at 26 September 2026 and may have changed since. Readers should verify any provision or decision referred to against the official text and seek advice on their own circumstances.