
Choose the event before calculating the certificate deadline
Section 56(4) of the Companies Act, 2013 uses four different triggers: incorporation for subscribers, allotment for later shares or debentures, and receipt by the company for transfer or transmission. The periods are two months, two months, six months and one month respectively. A Board approval date cannot automatically replace the statutory event. Where securities are dealt with in a depository, the proviso instead requires immediate intimation of allotment details to the depository; the physical-certificate timetable is not a reason to postpone that intimation.
This guide, checked as at 23 October 2026, concerns the event calendar and proof of completion under Companies Act section 56. First establish whether the transaction may lawfully use physical certificates under the applicable dematerialisation regime and other securities requirements. The examples assume physical delivery is permissible, the transaction is valid, and no law or competent authority’s order prohibits delivery. They do not create an exemption from dematerialisation or replace a listed company’s separate compliance obligations.
| Event | Section 56(4) period | Starting evidence |
|---|---|---|
| Memorandum subscribers | Two months from incorporation | Certificate of incorporation and subscriber record |
| Subsequent share allotment | Two months from allotment | Valid allotment resolution and allotment record |
| Transfer or transmission | One month from company’s receipt of instrument or intimation | Receipt register and actual submission |
| Debenture allotment | Six months from allotment | Debenture allotment record |
Keep instrument delivery and certificate delivery on separate lines
Section 56(1) concerns delivery of the executed transfer instrument to the company within sixty days of execution, with the required supporting security certificate or allotment letter, subject to the statutory conditions and proviso. Section 56(4)(c) is a different obligation: delivery of the transferred security certificate within one month of the company’s receipt. A single spreadsheet column called “transfer due date” loses one of these controls. Record execution, actual receipt, registration decision and delivery separately.
Transmission operates by law and is addressed in section 56(2); it should not simply be processed as a contractual transfer requiring the same execution history. Keep the claimant’s intimation, supporting entitlement evidence and any reasoned request for missing material. A disputed or incomplete claim needs a legal conclusion on its facts. An internal preference to start the clock only after the next Board meeting is not evidence that the statute uses that event.
Use months as months and preserve the original trigger
The General Clauses Act, 1897, section 3(35) defines a month by the British calendar. A month-based period should not be replaced by a fixed sixty-, thirty- or 180-day formula. The illustrations use ordinary corresponding calendar dates and avoid month-end dates. They show the unextended calendar boundary even where it falls on a non-working day; assess any applicable legal extension separately and plan delivery earlier. Plan completion before the boundary. Do not assume a non-working day, late signature, courier delay, printing problem or return filing automatically extends the statutory period. Where a special order or legal prohibition exists, retain it and analyse its exact scope instead of hiding the item from the tracker.
For subscribers, the incorporation date is not reset by the day the company opens a bank account or the day stationery arrives. For a later share allotment, use the valid allotment event rather than the date on which the accounting team books the entry. For debentures, distinguish allotment from an offer, application receipt or proposed issue date. Corrections to the tracker must retain an audit trail linking back to the true event.
Completion requires evidence beyond printing
Treat the workflow as a chain: legal eligibility, correct certificate particulars and prescribed execution formalities, register reconciliation, dispatch or handover, and delivery evidence. Printing a certificate does not demonstrate that it was delivered. Retain the certificate record, dispatch details, acknowledgement and exception follow-up together. If delivery is disputed, preserve the facts and obtain a conclusion on the actual mode and evidence; do not assert that a courier booking alone conclusively satisfies the law.
Common failure points for the secretarial review
The subscriber timetable can be missed when the team tracks only later allotments. Transfers can be missed when the registered office receives documents but the secretarial tracker is updated weeks later. Debentures can be misclassified as shares and given the wrong period. Depository intimation can be delayed because the team mistakenly follows a certificate-printing calendar. A competent review checks each securities population and its underlying event rather than sampling a single generic deadline field. Section 56 also addresses partly paid transfers and other conditions; these are transaction-validity checks, not automatic extensions of delivery periods.
Worked illustrations
These illustrations use fictional facts and expressly stated assumptions. Amounts are Indian rupees unless a different currency or unit is specified. They are independent examples, not findings about any actual client.
Illustrative example 1: Subscriber certificates start at incorporation
Assume a company is incorporated on 10 April 2026 and the subscriber certificates may lawfully be physical. The two-month corresponding-date deadline is 10 June 2026. That span is sixty-one elapsed days. A generic sixty-day formula would show 9 June, which demonstrates that “two months” and “sixty days” are not interchangeable.
Illustrative example 2: A later share allotment has its own clock
A valid share allotment occurs on 12 May 2026. Two calendar months lead to 12 July 2026, sixty-one elapsed days later. The tracker should retain the May allotment event even if the accounting entry is posted on 20 May; using that posting date would incorrectly show 20 July, eight days later.
Illustrative example 3: Receipt, not the later Board date, controls this transfer illustration
The company receives a valid physical transfer instrument on 8 June 2026. The one-month certificate deadline is 8 July. Assume the Board registers the transfer on 25 June. Starting one month from that Board date would show 25 July, seventeen days beyond the correct corresponding-date deadline.
Illustrative example 4: Transmission is measured from the stipulated intimation
Assume a legally sufficient transmission intimation is received on 15 July 2026 and the right and documentation are undisputed. One calendar month leads to 15 August, thirty-one elapsed days later. This example does not assume that every initial email from a claimant necessarily constitutes the legally relevant sufficient intimation.
Illustrative example 5: Debenture allotment uses six months
A valid debenture allotment occurs on 20 January 2026. Six calendar months lead to 20 July 2026, an elapsed 181 days. A fixed 180-day calculation would show 19 July. Keep the debenture allotment population distinct from the two-month share-allotment population.
Illustrative example 6: One transfer produces two separate dates
A valid instrument is executed on 5 April 2026 and received by the company on 25 April. The elapsed delivery time is twenty days, within the section 56(1) sixty-day period; the sixtieth-day date is 4 June. The company’s separate one-month certificate-delivery date is 25 May. Waiting until 4 June to complete the certificate task confuses the two obligations and is ten days beyond 25 May.
Illustrative example 7: Printing on time does not establish delivery on time
For a share allotment on 10 April 2026, the corresponding two-month deadline is 10 June. Assume the certificate is printed on 8 June but the accepted delivery evidence establishes delivery only on 14 June. That is four elapsed days after the deadline. The printing date does not demonstrate timely completion; retain the actual facts for remediation and legal assessment.
Ten-step verification table
| Step | Verification | Evidence to retain |
|---|---|---|
| 1 | Identify the security and company compliance population | Share/debenture register and listing/company status |
| 2 | Determine whether physical delivery is legally permissible | Applicable dematerialisation and securities-law assessment |
| 3 | Classify subscriber, allotment, transfer or transmission event | Transaction documents and legal classification |
| 4 | Capture the original statutory trigger date | Incorporation/allotment record or receipt evidence |
| 5 | Track transfer-instrument execution and submission separately | Executed instrument and company receipt log |
| 6 | Calculate calendar-month and day periods correctly | Independent date working and exception flags |
| 7 | Check legal prohibitions, orders and disputed entitlement | Actual order or reasoned legal assessment |
| 8 | Complete prescribed certificate execution and register checks | Certificate record and authorised execution evidence |
| 9 | Prove delivery or complete immediate depository intimation as applicable | Acknowledgement, delivery trail or depository submission |
| 10 | Review overdue items and retain corrective-action history | Exception report with responsible owner and dated actions |
Sixteen practitioner FAQs
1. Do subscribers receive a fresh two-month period from a later Board meeting?
The statutory subscriber trigger is incorporation. An internal meeting calendar does not replace it.
2. Is the allotment clock tied to the accounting posting date?
No. Establish the valid allotment event and preserve its date.
3. Are two months always sixty days?
No. Use calendar-month arithmetic and assess special boundary facts separately.
4. Does the company’s receipt date matter for a transfer?
Yes. Maintain evidence of actual receipt instead of relying only on the date the secretarial team entered it in a tracker.
5. Can registration approval automatically reset the transfer clock?
Section 56(4)(c) refers to receipt of the instrument or intimation. Do not substitute a later internal approval date without a legal basis.
6. Does transmission always require an executed transfer instrument?
Transmission by operation of law is distinct. Analyse the entitlement and supporting intimation under the applicable framework.
7. What if the claimant’s documents are disputed?
Record the gaps, communications and legal assessment. The clean transmission example assumes sufficient, undisputed documentation.
8. Are debentures subject to the two-month share-allotment period?
Section 56(4)(d) provides a six-month period from debenture allotment.
9. Can the physical-certificate period delay depository intimation?
No. The proviso calls for immediate intimation of allotment details where the securities are dealt with in a depository.
10. Does this guide exempt a private company from dematerialisation?
No. Determine the applicable regime before choosing the delivery process.
11. Is timely printing enough?
Retain evidence addressing delivery. Printing proves preparation, not necessarily delivery.
12. Does a dispatch receipt conclusively prove every delivery issue?
Its evidential value depends on the actual mode and facts. Preserve acknowledgement and follow up exceptions.
13. Can a holiday extension be assumed?
Do not build an automatic extension into the tracker without assessing the applicable legal rule and circumstances.
14. What is the difference between sixty days and one month on a transfer?
The sixty-day instrument-submission obligation and the company’s one-month certificate obligation have different triggers and actors.
15. What if an authority prohibits delivery?
Retain the actual prohibition or order and analyse its terms. Do not treat an ordinary administrative delay as such a prohibition.
16. What should a monthly secretarial exception report show?
Security type, original event, receipt where relevant, computed deadline, completion evidence, unresolved legal issue and dated corrective action.
Conclusion
Build the calendar around the security’s actual legal event, retain separate submission and delivery dates, and close each task with evidence. Establish the applicable physical or depository route before applying the timetable.