Termination must be traced beyond the main agent
Section 210 of the Indian Contract Act, 1872 states that termination of an agent's authority causes termination of the authority of all sub-agents appointed by him, subject to the Act's rules regarding termination of an agent's authority. The qualification matters: do not assume that a central termination letter makes every downstream transaction ineffective at the moment the letter is signed.
Read the applicable text: Indian Contract Act: sections 202, 204, 208 and 210.
Establish who is actually a sub-agent
Map the appointment chain, mandate and transaction function. A person appointed by an agent is not necessarily a sub-agent for every legal purpose; the distinction between sub-agents and persons properly named to act directly for the principal must be examined under the relevant agency provisions. Do not cancel an independently granted direct mandate merely because the same person also worked with the outgoing agent.
Preserve knowledge and effective-event evidence
Section 208 distinguishes when termination becomes known to the agent and when it becomes known to third persons. Read that rule with section 210's express qualification, and keep notices, receipt evidence and actual conduct. A dispatch date is not automatically proof that every downstream participant knew of termination then.
Protect existing commitments without inventing new authority
Section 204 addresses obligations arising from authority already partly exercised; section 202 protects the stated interest-related case. Review such qualifications before treating a proposed revocation as effective for every purpose. Separate completed binding commitments, performance of existing obligations and proposed new transactions. This article does not determine validity solely by whether a transaction is entered before or after an internal system flag.
Close operational access and legal authority separately
Revoke or amend credentials, purchasing limits and forwarding permissions as appropriate, but record these as operational controls. Disabling an account does not itself resolve all third-party rights; a still-active password does not prove continuing legal authority. Notify relevant participants and preserve evidence of the actual handoff.
Reconcile property and transaction exposure
Prepare registers for pending orders, funds, documents and goods at each appointment level. Avoid treating all pending value as established loss. Deduplicate the principal's and agent's copies of the same commitment and retain unresolved knowledge questions for transaction-specific review.
Six worked illustrations
All facts and amounts are fictional. Calculations illustrate the stated assumptions, not a predetermined legal outcome.
Illustrative example 1: Map downstream recipients
An outgoing agent appointed four genuine sub-agents. Receipt evidence presently exists for three downstream notices, leaving one knowledge record unresolved. Three out of four is 75% evidenced notice coverage, not proof that 25% of contracts are invalid.
Illustrative example 2: Dispatch and receipt differ
A notice is dispatched on 2 November and acknowledged on 5 November, a three-day elapsed interval. Transactions in that interval need their own knowledge and authority analysis. Do not use the dispatch date alone as proof of receipt.
Illustrative example 3: Remove duplicated commitments
The main-agent register lists pending orders ₹6 lakh and the sub-agent register lists ₹4 lakh, including ₹3 lakh of the same orders. Distinct pending value is ₹7 lakh. It is not automatically a ₹7 lakh loss or an admission of liability.
Illustrative example 4: Separate direct authority
Five service providers appear on an exit list. Evidence identifies three sub-agents and two independently appointed direct agents of the principal. The section 210 chain review concerns the three; analyse the two direct mandates separately rather than treating all five as one appointment chain.
Illustrative example 5: Reconcile custody
A sub-agent holds 120 units of the principal's stock. Ninety are returned with evidence, leaving thirty to reconcile. The outstanding quantity is a custody issue; it does not by itself establish a right to make new sales.
Illustrative example 6: Split access and notification controls
Six downstream accounts are disabled, while acknowledgements cover four of the six relevant holders. The operational access count is six and the evidenced acknowledgement gap is two. Neither register can replace the other.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Map the principal and agent | Original authority and termination basis. |
| 2 | Identify genuine sub-agents | Appointment chain and scope. |
| 3 | Separate direct mandates | Independent appointment evidence. |
| 4 | Review termination qualifications | Sections 202, 204 and relevant facts. |
| 5 | Record dispatch and knowledge dates | Notices and acknowledgements. |
| 6 | Review affected third persons | Knowledge evidence by transaction. |
| 7 | Separate existing commitments | Orders and performance obligations. |
| 8 | Control operational access | Credentials and delegated limits. |
| 9 | Reconcile funds and property | Custody and return records. |
| 10 | Close unresolved cases individually | Authority analysis and handoff sign-off. |
Sixteen practitioner FAQs
1. What does section 210 address?
Termination of the authority of sub-agents appointed by the agent.
2. Is its rule unconditional?
No. It expressly preserves the Act's termination rules.
3. Does dispatch prove downstream knowledge?
Not by itself.
4. Why is section 208 relevant?
It distinguishes knowledge of the agent and third persons.
5. Are all outsourced providers sub-agents?
Examine appointment, function and legal relationship.
6. What about a direct agent of the principal?
Analyse the independent mandate separately.
7. Does a password prove authority?
It is operational evidence, not a complete legal conclusion.
8. Does disabling access settle third-party rights?
No; examine the legal and factual position.
9. Can existing obligations survive a proposed revocation?
Review the applicable qualifications and prior exercise of authority.
10. Why review section 202?
The interest-related protection may affect termination analysis.
11. Why review section 204?
Prior exercise of authority can affect obligations already arising.
12. Is pending order value necessarily loss?
No. Distinguish exposure, performance and established damage.
13. Can duplicate order registers inflate exposure?
Yes. Reconcile common transaction IDs.
14. Does returning stock authorise fresh sales?
Custody reconciliation and transaction authority are separate.
15. Should every downstream file use one assumed knowledge date?
Use the actual supported evidence for each relevant participant.
16. What completes the exit file?
Authority, knowledge, commitments, access and property records reconcile.