Sections 11 to 13 IT Act: Attribution, Acknowledgment and Dispatch of Electronic Records

When a letter is posted, the law of contract has old answers to three questions: whose letter is it, has it reached, and when and where did posting and delivery happen? Sections 11 to 13 of the IT Act give the electronic answers. Section 11 attributes a record to its originator, including one sent by a machine he programmed; Section 12 deals with acknowledgment of receipt; Section 13 fixes the time and place of despatch and receipt, and in doing so quietly decides where an online contract is formed and which court gets jurisdiction. Topics 43 and 45 used these rules in passing; this note studies them section by section.

1. The Post Office Rules of the Electronic World

Think of an email as a registered letter. Section 11 asks whose handwriting is on it, and answers that a letter written by your clerk on your instructions, or franked automatically by your office machine, is still your letter. Section 12 is the acknowledgment due card. Section 13 is the postmark: it stamps the time and, more surprisingly, deems the letter posted at your place of business and delivered at the recipient's place of business, wherever the mail vans (the servers) actually went.

Figure 1: The three questions answered by Sections 11 to 13

2. Section 11: Attribution of Electronic Records

Figure 2: Three routes of attribution under Section 11

• Originator (s.2(1)(za)). The person who sends, generates, stores or transmits an electronic record or causes it to be sent, generated, stored or transmitted to any other person, but not an intermediary.
• Sent by the originator. A record sent from the originator's own account or device is his. Denial calls for proof, such as evidence that the account was hacked; the logs and headers become decisive.
• Sent by an authorised person. Agency principles apply. A record sent by an employee, agent or authorised signatory within his authority binds the principal, as under Sections 182 and 226 of the Contract Act.
• Sent by an automated system. A record generated by a system programmed by or on behalf of the originator, an auto-reply, a standing instruction, an algorithm, a chatbot confirming an order, is attributed to him even though no human saw that particular message.

Attribution in automated transactions

Figure 3: Why automated transactions bind the originator

• Principle. The consent was given at the stage of programming and deployment. Section 11(c) treats the machine as the originator's instrument, not as a contracting party.
• Illustrations. An e-mandate debiting a monthly subscription; an airline system auto-confirming a booking; an algorithmic trade executed within set parameters; each binds the person who deployed the system.
• Limits. Attribution says whose record it is, not that a contract is valid. Fraud, coercion or mistake still vitiate consent, and a hacked or manipulated system can be shown not to have operated as programmed.
• Beyond s.11. For fully autonomous AI systems acting outside their programming, attribution is debated (see Topic 20); s.11(c) presumes a system doing what it was set up to do.

3. Section 12: Acknowledgment of Receipt

Figure 4: How Section 12 operates

• Acknowledgment by the addressee. Unless a form is stipulated, anything that tells the originator the record arrived is enough: an automated delivery receipt, a reply email, or conduct such as acting on the instruction.
• Conditional acknowledgment. Section 12(2) lets the originator make the record itself conditional: 'binding only on acknowledgment'. Until acknowledgment arrives, the record is deemed never sent, so no obligation arises from it.
• Failure to receive acknowledgment. Where there was no such stipulation, Section 12(3) provides the two-notice route: a notice demanding acknowledgment within a reasonable time, and, on continued silence, a further notice treating the record as never sent. This protects a sender who cannot tell whether his message arrived.
• What s.12 is not. It does not make acknowledgment a condition of every communication, and an acknowledgment of receipt is not an acceptance of the contents; it only shows arrival.

4. Section 13: Time and Place of Despatch and Receipt

Figure 5: Time of despatch and receipt

• Time of despatch. The record leaves the originator's control, typically when the mail server accepts it for transmission. Pressing send on a queued draft that remains in the outbox is not despatch.
• Designated computer resource. Where the addressee has named an address or portal for receiving records ('send bids to tenders@company.in'), entry into that resource is receipt, whether or not anyone reads it.
• Non-designated resource. A record sent to some other address of the addressee is received only when he retrieves it; where nothing was designated, entry into any of his resources is receipt.
• Contrary agreement. Every rule in s.13 yields to agreement: parties can fix their own rules of timing and place.
• Source. The scheme follows Article 15 of the UNCITRAL Model Law on Electronic Commerce.

Figure 6: Time rules and place rules compared

• Place of despatch and receipt. Deemed to be the parties' places of business, severing place from server. A record routed through servers abroad is still received in India if the addressee's business is here (s.13(4))
• Place of business. With several offices, the principal place of business; with none, the usual place of residence, and for a body corporate the place of registration (s.13(5))

5. Section 13, E-Contract Formation and Jurisdiction

Figure 7: How Section 13 feeds into jurisdiction

• Contract formation. Acceptance completes the contract, and for instantaneous electronic communication the contract is made where acceptance is received (Bhagwandas Kedia, AIR 1966 SC 543). Section 13 tells us when and where that receipt happens.
• Civil jurisdiction. The place of contract is part of the cause of action under Section 20 CPC, so the deemed place of receipt can found jurisdiction, as in P.R. Transport.
• Consumer and criminal forums. A consumer may sue where he resides or works (CPA 2019); on the criminal side, jurisdiction follows the place of the offence and Section 75 of the IT Act (see Topic 10)
• Drafting lesson. Because every rule is subject to agreement, online terms commonly designate the resource for notices and choose courts, which is why the clauses matter.

6. Quick Revision and Memory Aids

• 'Whose letter, due card, postmark'. Sections 11, 12 and 13.
• 'Himself, his agent, his machine'. The three limbs of s.11.
• 'Bot binds its master'. s.11(c) automated transactions.
• 'Binding only on acknowledgment: never sent till it comes'. s.12(2)
• 'Out of control is despatch; into the inbox is receipt'. s.13(1), (2)
• 'Business place, not server place'. s.13(3) to (5)
• 'P.R. Transport: acceptance lands where you do business'. Jurisdiction.

7. Frequently Asked Questions

When is an electronic record deemed received?

If the addressee designated a computer resource, when the record enters it; if it was sent to a non-designated resource, when the addressee retrieves it; and if nothing was designated, when it enters any computer resource of the addressee (Section 13(2)). These rules apply unless the parties agree otherwise.

Is a record sent by an automated system binding on the person who set it up?

Yes. Under Section 11(c), a record sent by an information system programmed by or on behalf of the originator to operate automatically is attributed to the originator, so automated confirmations and e-mandates are his records.

8. Related Topics

• Topic 45: Section 10A and E-Contracts. How these rules complete online contract formation.
• Topic 10: Extra-Territorial Application. Jurisdiction over cross-border cyber acts.