
It is the last day of a filing window. The return is ready. The token is in a drawer, the certificate expired eleven days ago, and renewal takes the rest of the afternoon at best.
Every office of any size has had this day. What is striking is that the information needed to prevent it was always available: a certificate carries its expiry date on its face, and the date was knowable months earlier.
The failure is never that nobody knew. It is that nobody was told at a moment when they could act.
What a register has to hold
More than most practices record, and one field in particular is usually missing.
- Whose signature it is. The person, and their role, because a director's and an authorised signatory's are used for different things.
- Their PAN. This is what actually identifies the holder when two people share a name.
- The serial number of the certificate, which is how you tell two tokens for the same person apart.
- Issued on and expires on.
- Who holds it, and where it is kept.
- A note for anything else.
The custody fields are the ones usually left out, and they are the ones that turn a register from a list into something useful on the day. Knowing a certificate is valid does not help if nobody can say which drawer, which branch, or which client's office the token is sitting in.
A register that answers "is it valid" but not "where is it" solves half of a problem that always arrives whole.
Pro tip
Record custody as a free note rather than a dropdown. Real answers are things like "with the client, returned after each filing" and "in the Andheri office safe", and no fixed list of options survives contact with an actual practice.
Thirty days is the number that matters
A warning has to arrive with enough time to act on it, and renewal is not instant: there is an application, a verification step and a delivery.
Thirty days before expiry is the point at which a warning is still useful. A week is not; a week before expiry you are already rearranging a filing calendar around it.
That gives three states a certificate can be in, and they want different treatment:
| State | What it means | What to do |
|---|---|---|
| Lapsed | The date has passed | Nothing can be signed with it. Renew before anything is promised |
| Within thirty days | Still valid, expiring soon | Start the renewal now |
| Further out | Nothing to do today | Should not be in anyone's way |
The third row matters as much as the first. A register that shows every certificate with equal prominence is a register nobody reads, and an unread register fails exactly like no register at all.
The warning belongs where the work is
This is the design point that decides whether a register gets used, and it is easy to get wrong in a way that feels organised.
The tempting shape is a separate place for certificates: its own section, its own list, its own thing to check. It feels tidy and it fails, because it is one more habit to maintain and it competes with the work that is actually pressing.
A lapsing certificate is work that needs doing. It has a deadline, an owner and a client. So it belongs in the same place as the rest of the work with deadlines, grouped and sorted the same way, rather than in a separate list with its own conventions to learn.
The practical test is whether a partner opening their usual view at the start of the week sees the certificate expiring on Thursday alongside the return due on Friday. If seeing it requires going somewhere else on purpose, it will be seen in the week it lapses.
Greenote keeps the register this way: a client's signatures appear on that client's own page, and every client's at once on the firm's home, grouped into lapsed, expiring soon and ahead, using the same grouping as the rest of the firm's work rather than a second arrangement.
One clock, and who may see what
Two smaller points that cause trouble later.
One clock. "How many days until this expires" should be answered in exactly one place across the whole practice. Two pieces of software each working out today's date their own way will eventually disagree by a day across a month boundary or a time zone, and the disagreement will show up as a certificate that is urgent in one view and comfortable in another.
Who may see one. A DSC register is a list of people, their PANs, and physical custody of a credential that can sign on their behalf. That is not an ordinary client record. Access to it should follow the same permission rules as anything else sensitive in the practice, and the register should be no more visible than it needs to be.
The same discipline applies to notices with reply dates, which are the other thing in a practice where a date passing quietly costs real money.
Important
A DSC can sign on behalf of a person. Treat custody of one as you would treat custody of a signed blank cheque, and record every change of hands.
Conclusion
The information needed to prevent a lapsed certificate is never missing. It is on the certificate.
What is missing is a register that records custody as well as expiry, warns far enough ahead to be acted on, and puts the warning where the person will already be looking.
See what the practice workspace covers, or what else a firm should keep in one place.
Turn bank statements into Tally vouchers on your own PC
Greenote reads 100+ Indian banks and posts clean vouchers straight into Tally, from your own PC. The statement is not uploaded, and nothing is typed by hand.
Free trial: 7 days or 5 statements, no card. Works with Tally Prime & ERP 9.


