1. One transaction, several legal events
A company signs a security agreement, the bank disburses a loan and a filing acknowledgement arrives later. These are different events. The agreement concerns creation of rights, disbursement concerns lending, and the filing concerns a registry process. A bank should not describe them as one completed action merely because they belong to the same proposal. Understanding this separation is the foundation of company-charge administration.
The Companies Act framework for charges is an additional layer over the underlying security transaction. A mortgage, hypothecation or other arrangement must first be examined on its own terms and under the relevant law. Company-charge registration does not create ownership of an asset the company never owned. Nor does a legally sound security instrument make the applicable company-registration obligations disappear.
This chapter develops an event-based approach to creation, registration, modification and satisfaction. It also explains why omissions matter and how evidence should be maintained. The examples are simplified teaching cases, not advice on a live filing. Current forms, fees, extension mechanisms and portal procedures require reconciliation against the applicable rules and the transaction's date before operational use.
2. Identify the company and the charge
Start with the legal entity that owns the asset or creates the relevant interest. A company is distinct from its directors, shareholders and related companies. An asset belonging personally to a director should not be described as company property simply because the director controls the business. Conversely, company assets do not become the shareholder's personal assets through majority ownership.
Consider a manufacturing company borrowing against machinery. Establish whether the machinery is owned, leased, supplied under a title-retention arrangement or already subject to another interest. The charge description must identify the actual rights being created. A generic phrase covering all assets may require careful analysis of its scope and the company's authority; it is not a substitute for identifying the relevant property and obligation.
The charge-holder, borrower and security provider may differ. A group company can provide security for another entity's borrowing, subject to the relevant authority and legal requirements. That arrangement introduces corporate-benefit and approval questions beyond the filing itself. For an examination case, sketch each legal person separately and draw the debt and security arrows. This often exposes an incorrect assumption hidden by the phrase group loan.
3. Creation and corporate authority
Creation concerns the transaction establishing the security interest. Relevant evidence includes the instrument, parties, asset description, secured obligation, execution and corporate authority. The document should be examined for conditions and effective terms. A sanction letter or unsigned draft does not establish execution. A signature does not settle whether the signatory was authorised or whether other required approvals were obtained.
Suppose a branch receives a board resolution authorising one officer to sign a specified agreement, but a different person signs a materially different document. The file needs reconciliation. The existence of a board resolution is not enough if its scope does not match the executed act. Record the authority, signatory and document version so that a later reviewer can trace the basis of acceptance.
Creation date is legally significant and should be established from the actual transaction, not selected to produce a convenient filing deadline. The date on which a scanning team uploads a document is not necessarily the date the charge was created. If the effective event is uncertain, obtain the appropriate legal assessment and preserve the facts. Backdating an instrument is not a legitimate cure for delay.
4. Section 77 and the registration duty
Section 77 provides the central company duty to register relevant charges with the Registrar. The framework includes a primary filing period and conditional further registration routes. Its treatment can depend on when the charge was created and the applicable amendments. A single remembered outer limit should not be presented as the ordinary deadline for every charge in every period.
For teaching purposes, build an event record containing creation date, legal regime, ordinary filing requirement, actual filing, Registrar response and completion evidence. Then apply the current statutory text and rules. A reminder system can identify elapsed days, but eligibility for an extension or further route is a legal question. The calendar cannot decide whether the facts satisfy the conditions for that route.
The company may have the primary duty, but the lender has a strong practical interest in completion. A bank should not rely solely on the borrower's statement that the company secretary is handling it. The security conditions should identify responsibility, evidence and escalation. Shared involvement should improve control rather than allow each party to assume that someone else completed the task.
5. Filing and registration evidence
Distinguish preparation, submission, acknowledgement, correction and registration. A draft form establishes preparation. A receipt can establish submission or payment. A certificate or other relevant Registrar record establishes a different stage. The bank should obtain and verify the evidence appropriate to the action being claimed. An email containing the word done is not a complete audit trail.
Suppose a form is submitted with the wrong company identifier and the filing later requires correction. Treating the first payment receipt as final registration would conceal the error. Reconcile the company, charge-holder, instrument, amount and property description against the executed security. If a certificate is issued, examine its particulars rather than merely storing its filename. A correct-looking title does not guarantee that the underlying data matches the transaction.
Maintain version history where information changes. The original instrument, filed version, correction request and final record should remain distinguishable. This helps resolve whether a discrepancy arose in the agreement or the filing. It also prevents the mistaken belief that editing the bank's local copy updates the Registrar's record. Each system requires its proper authorised correction process.
6. Charge-holder application and acquired property
Section 78 addresses an application by the person in whose favour the charge is created where the company fails to register within the relevant primary period. The statutory conditions, notice and prescribed procedure matter. This is an alternative mechanism to examine, not a reason for the lender to ignore the company's primary duty or assume that unlimited time is available.
Section 79 applies the registration framework to specified situations involving acquisition of property subject to a charge and modification of a registered charge. A company acquiring an asset does not necessarily acquire it free of existing security merely because the asset is new to its own balance sheet. Review the acquired interest, existing charge and applicable registration treatment.
For example, Lumen Manufacturing acquires a business including charged machinery. The acquisition agreement, lender consent, asset records and charge particulars must be reconciled. A new asset code in the accounting system does not discharge the earlier charge. The learning point is continuity of legal rights through a commercial event: accounting recognition and legal freedom from security are different questions.
7. Modification of a charge
A modification can concern terms, amount, property or other relevant particulars of an existing charge. Distinguish it from creation of a separate security arrangement and from a change that does not alter the registered charge. The actual instrument and applicable requirements determine the route. A routine annual credit review should not automatically be treated as either a new charge or no legal event at all.
Suppose a bank increases a facility and adds machinery to the security. The file should identify the revised obligation, newly included property, executed amendment, authority and registration implications. The existing registration certificate cannot simply be assumed to cover the revised arrangement. Conversely, the mere increase in an internal credit limit may not tell the whole story if the security already covers a differently defined obligation.
Use a before-and-after comparison. What exactly did the original instrument secure? What changes under the new instrument? Which particulars in the registry need corresponding treatment? What evidence confirms completion? This method is more reliable than selecting a form from the transaction's commercial label. It also helps prevent duplicate or contradictory records where an existing charge is mistakenly treated as wholly unrelated.
8. Notice, public records and the company register
The statutory scheme addresses notice of registered charges and records maintained by the Registrar and the company. Public records help interested parties investigate existing security. Their value depends on accurate particulars and a proper search. A search result is not a title opinion on every asset or an assurance that the company's business is creditworthy.
Imagine a prospective lender searching an abbreviated company name and finding no charge. If the search did not identify the correct legal entity, the conclusion is unreliable. Even a correct search needs consideration of timing, scope and the underlying documents. A charge may be relevant although its commercial description differs from the lender's preferred terminology. Preserve the search parameters and date so the inquiry can be reproduced.
The company's own register and retained instruments should be reconciled with the Registrar's record. An internal spreadsheet is useful for monitoring but should not be represented as the official registry. Differences should be investigated, assigned and corrected through the proper route. The aim is consistent evidence across the executed transaction, company records, lender records and public registration.
9. Consequences of non-registration
Failure to complete required registration can materially affect the recognition of security against relevant parties in the circumstances specified by law. It should not be simplified into either the loan disappears or nothing happens because the agreement was signed. The underlying repayment obligation and the security's treatment are distinct. Section 77's consequence provisions must be read accurately for the particular context.
For an original case, a company signs a valid borrowing agreement and security instrument but the required charge registration is omitted. A student writes off the debt automatically. Another student treats the security as unquestionably effective against everyone. Both responses are too broad. Identify the enforceable obligation, the relevant competing parties and the statutory consequence of the registration failure before deciding what the lender can claim.
Delay also creates practical risks: uncertainty, competing claims, additional procedure and the need to reconstruct facts. A control system should detect missing evidence early and escalate before the problem becomes a recovery crisis. A late discovery should produce a transparent chronology and professional review. It should not produce a newly invented creation date or an inaccurate statement that an old acknowledgement was final registration.
10. Satisfaction and release
Section 82 addresses the company's reporting of satisfaction of charge, with related statutory mechanisms elsewhere in the chapter. Satisfaction, partial release and modification must be distinguished. Payment of one instalment is not full discharge. Sale of one secured asset may require a release or modification without ending security over every other asset. The documents and remaining obligations determine the appropriate treatment.
Suppose a term loan is repaid while a working-capital facility remains secured by the same arrangement. Before issuing a broad release, establish what the charge actually secures and whether any relevant obligations remain. A bank ledger showing zero under one account is not necessarily evidence that every obligation under the security has ended. A properly authorised review protects both lender and company from an inaccurate release.
When the security genuinely ends, complete the applicable reporting and release process and retain evidence. A stale public charge can obstruct later financing and create unnecessary customer difficulty. Closure should therefore include account reconciliation, authorisation, communication, document release and appropriate registry follow-up. The bank's operational convenience is not a reason to leave an extinguished interest inaccurately represented as continuing.
11. Rectification, receivers and responsibility
The statutory chapter contains provisions concerning Registrar entries, appointment of a receiver or manager, company records, contravention and rectification. Each serves a particular purpose. Rectification should not be described as an automatic route available without conditions for every omission. Likewise, a receiver's appointment is a legally significant event requiring the appropriate evidence and treatment rather than an informal change in the bank's contact list.
If a mistake is found, identify whether it concerns creation, filing particulars, satisfaction, company records or another event. Establish who may seek the remedy, the applicable authority and supporting facts. The proper route may depend on the nature and timing of the defect. A portal's ability to accept an upload does not establish that a particular statutory remedy has been granted.
Responsibility should be explicit. The company, adviser and lender may each perform different tasks, but the file should name the owner for every control and the evidence required for closure. A deadline reminder without an accountable recipient is weak. A recipient without escalation authority can also be ineffective. Good administration connects the legal event to a practical owner, due review and verified outcome.
12. Worked lifecycle and revision case
Orchid Tools grants a charge over identified machinery. Its file contains an executed instrument, a submission receipt and a later request for correction. The branch dashboard shows complete. The immediate issue is the unsupported completion status. Review the correction request and registration outcome, reconcile particulars and record the actual evidence. Do not assume failure is final, but do not treat an unresolved filing as completed registration.
Later, the company adds machinery and increases the secured arrangement. Review the amendment and authority, compare old and new particulars and assess modification requirements. Finally, the company repays one facility while another remains outstanding. Determine whether satisfaction, partial release or continued security is appropriate from the actual documents. The same charge can therefore require different actions at different points in its lifecycle.
For a reminder exercise, assume the instrument's verified creation date is 1 June and the review date is 18 June of the same year. Seventeen calendar days have elapsed. That arithmetic does not calculate a legal last date, establish an extension or resolve the counting convention required by law. The learning lab intentionally reports elapsed days and asks the learner to consult the verified rule, preserving the distinction between time measurement and legal eligibility.
Revise through the sequence entity, asset, authority, creation, registration, modification, monitoring and satisfaction. At each stage, name the evidence proving completion. In a multiple-choice question, eliminate answers that confuse acknowledgement with registration, loan repayment with every security release, or public registration with title ownership. Detailed dates, fees, forms and rectification conditions remain subject to operative-source reconciliation and academic acceptance before publication of this review edition.
13. Reconstruct a defensible event log
A charge event log should separate the event date, evidence date and review date. The instrument may be executed on one date, scanned on another and reviewed later. Recording only the scan date can corrupt deadline monitoring and obscure a delay. Record the source of the creation-date conclusion and flag any uncertainty for legal review instead of selecting the most convenient date.
For a fictional file, the instrument is signed on Monday, sent to the adviser on Wednesday and uploaded to the bank's archive on Friday. The archive timestamp proves when that copy arrived in the archive. It does not by itself prove Friday was the creation date. If a filing is subsequently corrected, preserve both the initial submission and the correction outcome. A final status should describe the evidence actually received.
At periodic review, compare the event log with active facilities and registered particulars. A repaid facility can remain linked to continuing security for other obligations; a modified facility can require an event that the old log missed. The review should therefore ask what changed and what remains, rather than merely whether a certificate is present. This creates a practical bridge between legal requirements, credit administration and accurate customer service at the end of the borrowing relationship.
Apply the chapter
Worked reasoning
Obtain and reconcile the actual registration outcome and particulars. Creation, submission and registration are different events. Preserve versions and close the condition with actual evidence.
Practice: 25 explained questions
Answers can be saved in this browser.
Choose answers, then check.
Sources and review
- PMLA statutory explanation and sections · checked 2026-11-08
- Maintenance of Records Rules · checked 2026-11-08
- Commercial Banks KYC Directions, 2025 · checked 2026-11-08
- FIU-IND institutional role · checked 2026-11-08
- Negotiable Instruments Act, 1881 · checked 2026-11-08
- CAIIB Rules and Syllabus 2026 · checked 2026-11-08
- Miscellaneous forex facilities FAQ · checked 2026-11-08
- Foreign Currency Accounts by Resident Individuals · checked 2026-11-08
- Foreign Exchange Management (Authorised Persons) Regulations, 2026 · checked 2026-11-08
- Payment and Settlement Systems Act, 2007 · checked 2026-11-08
- Payment and Settlement Systems Act FAQ · checked 2026-11-08
- Master Directions on Authorisation to operate a Payment System · checked 2026-11-08
- Transfer of Property Act, 1882 · checked 2026-11-08
- Indian Contract Act, 1872 · checked 2026-11-08
- Companies Act, 2013 · checked 2026-11-08
Original examples; independent academic review and website UAT pending.