Attribution, Acknowledgment, Dispatch of Electronic Records (Sections 11–13)

When a contract is born from a chain of emails, three questions decide everything that follows: who the law treats as the sender, whether the message was received, and where and when dispatch and receipt are deemed to occur. Chapter IV of the Information Technology Act, 2000 answers all three through Sections 11, 12 and 13, supplying default rules that fill the gaps the parties leave open. These three provisions are the bridge between the old common-law law of offer and acceptance and the realities of machine-to-machine communication, and they have repeatedly decided real disputes over jurisdiction and contract formation. This chapter unpacks each section, traces the case law from Bhagwandas Kedia to Trimex and P.R. Transport Agency, and shows how attribution, acknowledgment and dispatch interlock in practice.

Chapter IV: the default rules of electronic communication

Sections 11 to 13 form Chapter IV of the Information Technology Act, 2000, headed "Attribution, Acknowledgment and Despatch of Electronic Records." They are residual or default provisions: each opens (in substance) with the formula "save as otherwise agreed," meaning the parties are free to contract out of them. Where the parties are silent, however, these sections supply the legal answers to three distinct questions. Section 11 tells us when an electronic record is treated in law as having come from a particular person (attribution). Section 12 tells us how, and with what consequences, the recipient acknowledges that a record was received. Section 13 fixes the time and place at which dispatch and receipt are deemed to occur.

The architecture borrows directly from the UNCITRAL Model Law on Electronic Commerce, 1996, on which the entire Act is modelled. The Model Law's drafters recognised that paper-based concepts of "signature," "dispatch" and "receipt" do not map cleanly onto data messages, and so created functional equivalents. Reading these sections alongside the definitions in Section 2 is essential, because the operative words, originator, addressee, computer resource and electronic record, are all defined terms. For the foundational scheme of the Act, see the introduction chapter and the broader Information Technology Act hub.

The building blocks: originator, addressee and computer resource

Section 11, 12 and 13 cannot be understood without their defined terms. Under Section 2(1)(za), an "originator" is a person who sends, generates, stores or transmits any electronic record, or causes any electronic record to be sent, generated, stored or transmitted to any other person, but does not include an intermediary. The exclusion of intermediaries is deliberate: a person who merely relays or hosts a message, an internet service provider, an email host, is not the originator of the content passing through it.

An "addressee," under Section 2(1)(b), is a person who is intended by the originator to receive the electronic record, but does not include any intermediary. Again, the intermediary is excluded, so the mail server that holds the message in transit is neither originator nor addressee. A "computer resource" under Section 2(1)(k) is broadly defined to mean a computer, computer system, computer network, data, computer database or software. Because dispatch and receipt under Section 13 turn on records entering or leaving a "computer resource," this wide definition ensures the rules apply to email servers, web portals and automated systems alike. The treatment of these foundational terms is developed further in the definitions chapter.

Section 11: attribution of electronic records

Section 11 answers the question, "whose message is this in the eyes of the law?" It provides that an electronic record shall be attributed to the originator in three situations: (a) if it was sent by the originator himself; (b) if it was sent by a person who had the authority to act on behalf of the originator in respect of that electronic record; or (c) if it was sent by an information system programmed by or on behalf of the originator to operate automatically.

Clause (a) covers the ordinary case of a person personally pressing "send." Clause (b) imports principles of agency: a record sent by an authorised agent, an employee, a power-of-attorney holder, a company secretary acting within scope, is attributed to the principal. Clause (c) is the genuinely modern provision: it attributes to the originator records generated by automated systems, electronic agents, auto-responders, automated trading platforms, programmed by or on behalf of that person. Crucially, Section 11 does not say a record is attributed to the originator only in these cases; it is an inclusive, enabling rule, and it does not by itself resolve disputes about spoofed or forged emails. Where authorship is contested, the party relying on the record must still prove that it in fact emanated from the alleged originator, and the admissibility of that proof is governed by the law of electronic evidence rather than by Section 11 alone.

Attribution, agency and automated systems in practice

The practical force of Section 11 is felt most in commercial correspondence conducted by employees and agents. When a procurement manager emails a purchase confirmation from a corporate account, clause (b) attributes that record to the company, provided the manager had authority. This dovetails with the ordinary law of agency under the Indian Contract Act, 1872, and with the line of authority recognising that contracts can be concluded entirely through electronic exchanges. In Trimex International FZE Ltd v Vedanta Aluminium Ltd, (2010) 3 SCC 1, the Supreme Court treated emails exchanged between officers of the two companies as binding the companies themselves; the records sent by each side's representatives were effectively attributed to the corporate principals, and a concluded contract was found to exist once the essential terms had been agreed by that exchange.

Clause (c) becomes important as commerce automates. An order-confirmation generated automatically by an e-commerce engine, or a quote produced by an algorithmic pricing system, is attributed to the business that deployed it, even though no human reviewed the specific message. The originator cannot disown an automated communication merely because a machine produced it; the law looks to who programmed or deployed the system. This principle anticipates modern debates about algorithmic and AI-generated communications, and aligns Indian law with the UNCITRAL position that automated message systems bind the party on whose behalf they operate.

Section 12: acknowledgment of receipt

Section 12 governs how an addressee acknowledges that an electronic record was received and what follows if no acknowledgment comes. It operates only where the originator has either stipulated that an acknowledgment be given, or has not stipulated a particular form. Section 12(1) provides that where the originator has not agreed with the addressee that the acknowledgment of receipt be given in a particular form or by a particular method, an acknowledgment may be given by (a) any communication by the addressee, automated or otherwise; or (b) any conduct of the addressee, sufficient to indicate to the originator that the electronic record has been received.

The breadth of clause (b) is significant: conduct, not merely an express message, can amount to acknowledgment. If the addressee acts on the contents of a record, for instance, by shipping goods described in an emailed order, that conduct may itself signal receipt. This mirrors the common-law principle that acceptance and receipt can be inferred from conduct, and it means an addressee cannot always avoid the consequences of receipt simply by declining to send a formal reply.

Conditional records and the consequence of no acknowledgment

Section 12(2) addresses the case where the originator has made the electronic record conditional on acknowledgment. It provides that where the originator has stipulated that the electronic record shall be binding only on receipt of an acknowledgment of such electronic record by him, then, unless acknowledgment has been so received, the electronic record shall be deemed to have been never sent by the originator. This is a powerful default protection for an originator who wants certainty: by expressly making the record's effect conditional, the originator ensures that an unacknowledged record carries no legal weight, as though it had never left his control.

Section 12(3) deals with the residual situation where the originator has not made the record conditional but has not received an acknowledgment within the time specified or agreed, or, if no time was specified, within a reasonable time. In that case the originator may give notice to the addressee stating that no acknowledgment has been received and specifying a reasonable time by which the acknowledgment must be received; and if no acknowledgment is received within that further time, the originator may, after giving notice to the addressee, treat the electronic record as though it had never been sent. The two-step structure, the record is not automatically void; the originator must give notice and allow a further reasonable time, protects the addressee against an originator unilaterally and silently withdrawing a record.

Section 13(1): the time of dispatch

Section 13 is the most litigated of the three provisions because it fixes both the time and the place of dispatch and receipt, facts that determine when a contract is concluded and which court has jurisdiction. Section 13(1) provides that, save as otherwise agreed to between the originator and the addressee, the dispatch of an electronic record occurs when it enters a computer resource outside the control of the originator.

The test is one of loss of control. The moment the record leaves the originator's own computer resource, his outbox, his own server, and enters a resource he no longer controls, typically the recipient's mail server or an intermediary beyond his reach, dispatch is complete. This is the electronic analogue of posting a letter, but the trigger is technological rather than physical: it is not the click of "send" as such, but the record crossing the boundary of the originator's control. If a message is composed but never leaves the sender's own system, there is no dispatch under Section 13(1).

Section 13(2): the time of receipt

Section 13(2) fixes the time of receipt and distinguishes between addressees who have designated a computer resource for receiving records and those who have not. Where the addressee has designated a computer resource for the purpose of receiving electronic records, receipt occurs at the time when the electronic record enters the designated computer resource; but if the electronic record is sent to a computer resource of the addressee that is not the designated computer resource, receipt occurs at the time when the electronic record is retrieved by the addressee. Where the addressee has not designated a computer resource along with specified timings, if any, receipt occurs when the electronic record enters the computer resource of the addressee.

The logic rewards clarity. If you tell the world to send notices to a particular address, you bear the risk of receipt the instant a message enters that designated resource, whether or not you read it. But if a sender uses a different, non-designated address, the law protects the addressee: receipt is postponed until the addressee actually retrieves the message. This is a sensible allocation of risk, the addressee should not be fixed with receipt at an address he never nominated until he in fact pulls the message down.

Section 13(3)-(5): the place of dispatch and receipt

Section 13(3) supplies the rule that has decided jurisdiction disputes. Save as otherwise agreed to between the originator and the addressee, an electronic record is deemed to be dispatched at the place where the originator has his place of business, and is deemed to be received at the place where the addressee has his place of business. Section 13(4) makes clear that subsection (3) applies notwithstanding that the place where the computer resource is located may be different from the place where the electronic record is deemed to have been received. In other words, the physical location of the server is legally irrelevant; what matters is the parties' place of business.

Section 13(5) resolves ambiguity where a party has more than one place of business or none. It provides that if the originator or addressee has more than one place of business, the principal place of business shall be the place of business; and if the originator or addressee does not have a place of business, his usual place of residence shall be deemed to be the place of business. The Explanation to the section clarifies that for a body corporate, "usual place of residence" means the place where it is registered. These rules deem a legal situs for an inherently placeless communication, and they have proved decisive in litigation.

P.R. Transport Agency: Section 13(3) and territorial jurisdiction

The leading Indian application of Section 13 is P.R. Transport Agency v Union of India, AIR 2006 All 23, decided by the Allahabad High Court. Bharat Coking Coal Ltd had accepted P.R. Transport Agency's e-tender for coal, communicating the acceptance by email which the agency received at its place of business in Uttar Pradesh, although the tender process and the respondent were based in Jharkhand. When a dispute arose, the question was whether the Allahabad High Court had territorial jurisdiction under Article 226, given that part of the cause of action had to arise within its territory.

The Court applied Section 13(3): because the acceptance email was deemed to be received at the place where the addressee, the agency, had its place of business, namely Varanasi/Chandauli in U.P., the contract was completed there, and a part of the cause of action arose within the Court's jurisdiction. The decision is a textbook illustration that the deemed place of receipt under Section 13(3), not the location of the server or the originator, fixes where an e-contract is concluded for jurisdictional purposes. It remains the first Indian authority to give judicial content to Section 13 and is routinely cited for the proposition that e-contract jurisdiction follows the addressee's place of business.

From Kedia to Trimex: contract formation by instantaneous communication

Section 13 did not arrive in a vacuum; it sits atop a line of contract-formation cases. The foundational decision is Bhagwandas Goverdhandas Kedia v Girdharilal Parshottamdas & Co, AIR 1966 SC 543, where a contract was concluded by long-distance telephone, the offer spoken at Ahmedabad and the acceptance at Khamgaon. The Supreme Court held that for instantaneous modes of communication, the postal rule does not apply: the contract is complete only when and where the acceptance is heard by the offeror. The place of formation was therefore Ahmedabad, where the acceptance was received. Kedia thus distinguished instantaneous communication (telephone, telex) from the postal rule, and its "receipt" principle is conceptually echoed by Section 13's focus on the place of receipt.

That common-law foundation was carried into the digital era by Trimex International FZE Ltd v Vedanta Aluminium Ltd, (2010) 3 SCC 1. There the Supreme Court held that a contract for the supply of bauxite was concluded through an exchange of emails once the parties had agreed on all essential terms, even though no formal contract was later signed. The Court treated the emailed acceptance as effective and binding, reinforcing that electronic records can form contracts and that the moment of conclusion is tied to communication of acceptance, an approach that harmonises with Section 13's machinery for timing dispatch and receipt.

Electronic records as 'writing': SIL Import and Shakti Bhog

The attribution and dispatch rules presuppose that electronic and tele-communications count as legally effective writings. Two Supreme Court decisions support that premise. In SIL Import USA v Exim Aides Silk Exporters, (1999) 4 SCC 567, decided before the IT Act came into force, the Court held that a notice required to be "in writing" under Section 138 of the Negotiable Instruments Act, 1881 could validly be sent by fax. The Court reasoned that the legislature must be presumed to keep pace with technology, so a faxed notice satisfied the writing requirement, an early judicial embrace of electronic communication.

That openness was extended in Shakti Bhog Foods Ltd v Kola Shipping Ltd, (2009) 2 SCC 134, where the Supreme Court held that an arbitration agreement under Section 7 of the Arbitration and Conciliation Act, 1996 need not be a single signed document; it could be gathered from an exchange of letters, telex, telegrams or other means of telecommunication, including faxes and emails, that provide a record of the agreement. Read together, SIL Import and Shakti Bhog confirm that electronic records carry full legal effect, the necessary backdrop against which Sections 11 to 13 allocate authorship, acknowledgment and timing. The statutory recognition of electronic form is examined in the electronic governance chapter.

Attribution disputes and the burden of proof

Section 11 tells us when a record is attributed to an originator, but it does not establish, in a contested case, that the record in fact came from that person. Where authorship is denied, the dispute shifts to the law of evidence. The governing authority is Anvar P.V. v P.K. Basheer, (2014) 10 SCC 473, in which the Supreme Court held that the contents of an electronic record may be proved only in accordance with Section 65B of the Indian Evidence Act, 1872, and that a certificate under Section 65B(4) is a mandatory condition precedent to the admissibility of secondary electronic evidence. The Court overruled the contrary view in State (NCT of Delhi) v Navjot Sandhu on this point.

The practical lesson for attribution is that a party seeking to fix another with an electronic record, an email purportedly sent by him, must be able to prove the record's authenticity and source through admissible electronic evidence. Section 11's attribution presumptions operate within that evidentiary frame: they identify the legal consequence once authorship is established, but they do not dispense with proof where authorship is genuinely in issue. This interaction is sharpened by the provisions on secure electronic records and signatures, which attach stronger presumptions to records secured by a recognised security procedure.

Drafting lessons and exam takeaways

Because Sections 11 to 13 are default rules, well-drafted electronic dealings often displace them. Parties commonly designate a specific email address for notices (engaging Section 13(2)), stipulate that an offer is binding only on express acknowledgment (engaging Section 12(2)), or fix the place and law of the contract by an express clause (displacing Section 13(3)). Examiners reward candidates who notice the "save as otherwise agreed" formula and explain that the statutory defaults yield to party autonomy.

For revision, hold the three questions in mind. Attribution (Section 11): a record is attributed to the originator if sent by him, by an authorised agent, or by a system he programmed. Acknowledgment (Section 12): acknowledgment may be by communication or conduct; a conditional record is deemed never sent without acknowledgment (12(2)); and an unacknowledged ordinary record may be treated as never sent only after notice and a further reasonable time (12(3)). Dispatch and receipt (Section 13): dispatch when the record leaves the originator's control (13(1)); receipt when it enters the designated resource or is retrieved (13(2)); and the deemed place is the relevant party's place of business (13(3)-(5)), as applied in P.R. Transport Agency. Anchor the discussion in Kedia, Trimex and Anvar P.V., and cross-reference the framework of digital and electronic signatures for completeness.