Start with how the agent learned the fact
Under section 229 of the Indian Contract Act, 1872, notice received or information obtained by an agent in the course of business transacted for the principal has the same legal consequences between the principal and third parties as notice or information reaching the principal. A delay in forwarding it to head office does not, on its own, put off attribution. Identify the specific principal, business and fact before treating a message as notice.
Read the applicable text: India Code: Indian Contract Act, 1872, sections 226–229 and statutory illustrations.
Build two linked chronologies
The agency file should show the appointment date, mandate, changes and the transactions the agent actually handled. The information file should show the original content, source, recipient and receipt or acquisition date. Link the two using the order, asset, negotiations or contract. Record the time the principal actually learned the information separately. The date an email was forwarded may show internal handling without establishing the first legally relevant date.
Use the title and set-off illustrations as a test
The Act's paired illustrations concern a purchase from an apparent owner who owes money to the principal. When the purchasing agent learns during negotiations that the goods belong to someone else, the principal cannot set off the apparent owner's debt against the price in the statutory example. When the agent acquired that information in earlier employment and the principal did not know, the illustration permits set-off. The difference lies in when and in what capacity the agent learned the fact. Other conditions for set-off remain a separate question in real contracts.
Separate receipt, valid service and authority to act
Receipt of information may matter even if the agent cannot agree a variation, admit liability or settle a claim. For a deadline that runs from contractual service, read the address, method, timing and deemed-receipt terms and then assess statutory attribution. Section 229 does not itself prescribe a notice period or cure defective service. Keep the evidentiary analysis separate from sections 226–228, which address the contractual consequences of acting within or beyond authority.
Preserve uncertainty on mixed mandates
A shared employee, adviser or intermediary may act for different principals or in multiple capacities. Log the project code and authority used at the moment the information arrived. A shared mailbox, a group brand or a copy of a later escalation cannot resolve who was represented. If the same fact is confirmed during the relevant mandate, identify the new source and time and assess that event on its own facts.
Six worked illustrations
All facts and amounts are fictional. Calculations illustrate the stated assumptions, not a predetermined legal outcome.
Illustrative example 1: Title learned during procurement
A buyer's agent learns during negotiations that the machinery belongs to a third party. Assume the first statutory illustration applies, so the buyer cannot set off the apparent seller's ₹3 lakh debt against the ₹12 lakh price. If the buyer pays only ₹9 lakh in reliance on that set-off, ₹3 lakh remains unpaid on those facts.
Illustrative example 2: Knowledge from earlier employment
Assume the second statutory illustration applies: the agent learned of the true owner before appointment, the principal remains unaware and set-off is otherwise available on the facts. A price of ₹9 lakh less the apparent seller's ₹2 lakh debt leaves ₹7 lakh.
Illustrative example 3: Escalation lag
An authorised transaction agent receives relevant information on 5 June and forwards it on 9 June. The forwarding lag is four calendar days; preserve 5 June as the date for the attribution analysis rather than starting with the escalation.
Illustrative example 4: Two principals, two mandates
A service agent receives claims about 14 units for principal A and six units for principal B in separate mandates. Out of 20 units in the combined file, only six relate to B. The remaining 14 are not attributed to B merely because the same agent received both claims.
Illustrative example 5: Independently confirmed fact
An agent first learns of an adverse title claim on 2 July while working elsewhere, then receives a written confirmation in the relevant purchase negotiations on 11 July. Nine days separate the events; assess attribution on the second event independently.
Illustrative example 6: Invoice-level notice
A buyer's agent receives a notice about two identified deliveries worth ₹2.4 lakh and ₹1.6 lakh. A third ₹3 lakh delivery is outside its scope. The affected amount in the notice register is ₹4 lakh of the ₹7 lakh total; that figure does not decide the merits of the claim.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Name the principal for each transaction | Signed mandate or other evidence of appointment |
| 2 | Identify the relevant business | Order, negotiation brief or service contract |
| 3 | Confirm agency dates and scope | Appointment, delegation and change records |
| 4 | Preserve original notice or source | Full message, attachments or meeting record |
| 5 | Verify receipt or acquisition date | Header, delivery log or signed notes |
| 6 | Match the fact to the transaction | Asset identifier, case ID or order reference |
| 7 | Separate unrelated prior knowledge | Dated chronology and capacity at each event |
| 8 | Review any notice formalities | Contract clause or applicable service rule |
| 9 | Separate receipt from authority to agree | Delegation schedule and response text |
| 10 | Record the consequence and uncertainty | Dated position note with evidence and owners |
Sixteen practitioner FAQs
1. Does an agent have to forward the message first?
No. The test is receipt or acquisition in the relevant agency business. Preserve both timestamps.
2. Does this cover facts learned in negotiations?
Yes, when learned in the course of the relevant business for the principal. The Act's first illustration uses negotiations.
3. Can an oral statement matter?
Yes, information is not limited to a written notice. Prove what was conveyed, when and in which capacity.
4. Is every fact the agent already knows imputed?
No. The second illustration distinguishes knowledge acquired in an earlier employment.
5. What if the fact is learned again under the mandate?
Examine the later confirmation as a separate acquisition event.
6. Does a copied email prove attribution?
The copy is evidence to assess. Confirm receipt, content and connection to the mandate.
7. Is the principal's silence an admission?
Section 229 addresses attribution; any effect of silence requires a separate legal or contractual basis.
8. Does a power to receive notice imply power to settle?
No. Check the authority to alter or settle obligations separately.
9. Can the same notice bind two group companies?
Assess agency and receipt in the relevant business for each company independently.
10. How should a shared inbox be handled?
Keep routing, timestamp and transaction assignment records and establish the capacity in which the item was received.
11. Does an old mandate cover notices after its end?
Determine the effective termination and facts of receipt. Do not assume the mandate continued.
12. Does section 229 prescribe how long to respond?
No. Obtain the period and counting method from the applicable contract or law.
13. Can a contractual notice address be ignored?
No. Check formal service and attribution separately before asserting that a deadline ran.
14. What if the file identifies the wrong asset?
Resolve the asset mismatch before treating the notice as applicable to the disputed transaction.
15. Does attribution establish the amount payable?
No. Calculate the consequence under the relevant substantive rules and contract.
16. What belongs in a dispute handover?
The mandate, original information, date evidence, related transaction and a short note explaining the consequence claimed.
Official sources
India Code: Indian Contract Act, 1872, sections 226–229 and statutory illustrations