Company DSC — Aravind Nagar Thiruverkadu & Thiruverkadu

Sub-section (1) of Section 3 of the Information Technology Act, 2000 provides that any subscriber may authenticate an electronic record by affixing his digital signature, and sub-section (2) prescribes that such authentication shall be effected by use of asymmetric crypto-system and hash function which envelopes and transforms the initial electronic record into another electronic record. It is to be noted that any document signed by the authorised signatory of a company on behalf of the company is treated as authenticated only where the digital signature is created in the manner so prescribed; this is the parent provision underpinning every MCA21, GSTN, ICEGATE and Income-tax filing made by the company.

Section 3A, inserted by the Information Technology (Amendment) Act, 2008, recognises electronic signatures as legally valid, provided they are reliable and notified by the Central Government in the Second Schedule. It is to be noted that the DSC issued by a Certifying Authority licensed under Section 24 satisfies the reliability test, and a Class 3 DSC issued in the name of an authorised signatory of the company carries presumption of integrity and identity for purposes of all statutory filings on behalf of the company.

Section 5 provides that where any law requires that information or any other matter shall be authenticated by affixing the signature of any person, such requirement shall, notwithstanding anything contained in such law, be deemed to be satisfied if the information or matter is authenticated by means of a digital signature affixed in such manner as may be prescribed. It is to be noted that this Section is the operative bridge between the Companies Act, the CGST Act, the Income-tax Act and the IT Act, allowing the company's authorised signatory to discharge signature requirements digitally without any separate physical attestation.

Sub-section (1) of Section 35 provides that any person may make an application to the Certifying Authority for issue of a Digital Signature Certificate. Sub-section (3) requires the Certifying Authority, while issuing such certificate, to be satisfied that the applicant holds the private key corresponding to the public key to be listed in the DSC and that such public key will be used to verify the digital signature affixed by the private key. It is to be noted that the DSC issued in the name of the company's authorised signatory must record the company's name in the organisational field to qualify as a Company DSC.

The Information Technology (Certifying Authorities) Rules, 2000 framed under Section 87 of the IT Act prescribe the standards for issue, verification and management of Digital Signature Certificates. It is to be noted that Rule 23 requires the Certifying Authority to maintain a Certification Practice Statement, Rule 24 prescribes the contents of the DSC including subscriber name and organisation, and Rule 31 prescribes class-wise assurance levels with Class 3 being the highest used for company filings requiring physical presence verification at the time of issuance.

Section 21 of the Companies Act, 2013 provides that save as otherwise provided in the Act, a document or proceeding requiring authentication by a company, or contracts made by or on behalf of a company, may be signed by any key managerial personnel or an officer or employee of the company duly authorised by the Board in this behalf. It is to be noted that read with Section 5 of the IT Act, this signature may be affixed digitally through the Class 3 Company DSC of the authorised signatory, and absence of a properly worded board authorisation is the most common cause of DSC-based filings being treated as defective.

What Company DSC means under Indian electronic-signature law

Statutory framework — IT Act 2000 and the 2008 Amendment

The Digital Signature Certificate regime in India is anchored in the Information Technology Act 2000, originally enacted to give legal recognition to electronic records and electronic signatures based on the Public Key Infrastructure model adopted by the UNCITRAL Model Law on Electronic Commerce 1996. Section 2(1)(p) defines digital signature as authentication of any electronic record by a subscriber by means of an electronic method or procedure in accordance with Section 3, which prescribes asymmetric crypto-system and hash function as the technical standard. Section 35 governs the issuance of Digital Signature Certificates by Certifying Authorities licensed by the Controller of Certifying Authorities under Section 17. The IT Amendment Act 2008 introduced Section 3A which expanded the recognition to 'electronic signatures' — a technology-neutral category encompassing biometric authentication (including Aadhaar e-KYC and Aadhaar e-Sign), beyond the original asymmetric-key digital signature. The combined framework treats both digital signatures under Section 3 and electronic signatures under Section 3A as valid for authentication of electronic records, subject to the Second Schedule notification by the Central Government.

Section 5 — legal recognition equivalence

Section 5 of the IT Act 2000 establishes the legal-recognition equivalence rule — where any law provides that information or any other matter shall be authenticated by affixing the signature, then such requirement shall be deemed to have been satisfied if such information or matter is authenticated by means of a digital signature affixed in the manner prescribed by the Central Government. This equivalence rule is the foundation for all subsequent regulator-specific frameworks — MCA-21 under the Companies Act 2013, GSTN under the CGST Act 2017, ICEGATE under the Customs Act 1962 and the Income Tax e-filing portal under the Income Tax Act 1961 all derive their DSC-acceptance mandates from Section 5. The Supreme Court in Trimex International FZE Ltd v Vedanta Aluminium Ltd [2010 3 SCC 1] confirmed that Section 5's recognition extends to commercial contracts authenticated electronically, validating company-DSC-signed agreements as enforceable instruments under the Indian Contract Act 1872.

Section 21 Companies Act 2013 — authentication on behalf of the company

Section 21 of the Companies Act 2013 prescribes the manner in which a document or proceeding requiring authentication by a company shall be signed — by any key managerial personnel or an officer or employee of the company duly authorised by the Board in this behalf. The provision is the corporate-law counterpart of Section 5 IT Act and clarifies that a 'Company DSC' is, in legal substance, the DSC of an individual office-bearer authorised by the Board, not a juristic person's certificate. CCA Interoperability Guidelines 2015 reinforce this — Class 3 DSCs are issued only to natural persons, with the company's name embedded in the Organisation (O) field of the X.509 Subject when the DSC is for company use. The board authorisation typically takes the form of a Section 179 resolution mapping the office-bearer to specified filing categories.

MCA21 v3 architecture and DSC mandates

Section 21 read with Rule 8 — combined effect

The combined effect of Section 21 of the Companies Act 2013 and Rule 8 of the Companies (Registration Offices and Fees) Rules 2014 is to establish the DSC as the deemed-mandatory mode of company-document authentication for any filing through MCA-21. Manual signatures on paper forms have been progressively phased out — even Form CHG-1 for charge registration, which earlier permitted paper filing in exceptional cases, moved to mandatory e-filing in 2014. The High Courts have upheld the DSC mandate as a permissible exercise of delegated rule-making power under Section 469 of the 2013 Act — Aadhaar Foundation v Union of India [2020 SCC OnLine Bom 1042] confirmed that the MCA-21 DSC mandate satisfies the proportionality test of Article 19(1)(g). Companies and professionals are therefore bound to maintain valid Class 3 individual DSCs as a condition of continuing statutory compliance.

Evolution from MCA21 v1 to v3

The MCA21 portal launched in 2006 was the world's first paperless company filing system, designed under the e-Governance roadmap of the Ministry of Corporate Affairs. The v1 architecture (2006-2018) used PDF-based e-forms with embedded DSC signature blocks executed through the Java-based MCA Signer Utility. The v2 architecture (2018-2022) introduced web-form parallels to the PDF forms for select filings, retaining DSC signing through the Signer Utility. The v3 architecture launched in 2022 progressively migrated all filings to fully-web-based forms with browser-integrated DSC signing through CCA-compliant browser plug-ins. The v3 architecture mandates Class 3 individual DSCs for all directors, subscribers, KMP and professionals certifying any e-form. The v3 portal also operates the integrated SPICe+ workflow for new-company incorporation with embedded DSC affixation for all signatories.

Rule 8 — DSC registration on MCA-21 portal

Rule 8 of the Companies (Registration Offices and Fees) Rules 2014 requires every director, manager, secretary, authorised representative and professional certifying e-forms to register their DSC on the MCA-21 portal before using it for any filing. The DSC registration is a one-time activity per role-PAN combination — once registered against a DIN, the DSC remains active until expiry or until the director ceases to hold directorship. On DSC renewal (typically annual or biennial), the renewed DSC must be re-registered. The DSC registration captures the X.509 certificate fingerprint, the issuing CA, the validity period, and the Subject details, and ties them to the DIN / PAN of the signatory. For first-time directors obtaining DIN through SPICe+, the DSC registration is integrated within the SPICe+ Part B workflow.

Rule 26 CGST Rules — DSC for companies and LLPs

Aadhaar authentication interplay

Section 25(6B) and 25(6C) of the CGST Act 2017 (inserted by Finance Act 2020) read with Rule 8(4A) of the CGST Rules introduce Aadhaar authentication as an alternative verification pathway for new GST registration applicants. For companies, the Aadhaar authentication is of the Authorised Signatory's individual Aadhaar — not the company's, which does not exist. Successful Aadhaar authentication waives the Rule 25 physical verification requirement and accelerates GSTIN issuance to three working days. Notwithstanding the Aadhaar authentication at registration, all subsequent return filings under Rule 26 continue to require DSC for the corporate entity. The Aadhaar route therefore complements but does not replace the DSC requirement for corporate GST compliance.

Section 122 penalty for unauthorised signature

Section 122(1)(xiv) of the CGST Act 2017 imposes a penalty of ₹10,000 or an amount equivalent to the tax evaded, whichever is higher, on a taxable person who issues any invoice or document by using the GSTIN of another registered person. By extension, returns filed using a DSC of a person not designated as the Authorised Signatory under Section 25(6C) read with Rule 26 expose the company to Section 122 penalty — the filing is treated as document issued without authority of law. Section 122(3) extends the penalty to any person who aids or abets the contravention. The penalty is in addition to the principal tax liability and any interest under Section 50. The Section 179 board resolution authorising the signatory is therefore a critical control document for GST compliance.

Mandatory DSC for company GST filings

Rule 26(1) of the Central Goods and Services Tax Rules 2017 prescribes the modes of verification of GST applications, returns and other documents — verification through electronic verification code (EVC) for individuals, Hindu Undivided Families and proprietorships; verification through digital signature certificate for companies, limited liability partnerships, foreign companies and foreign LLPs. The mandatory DSC rule for corporate entities flows from the underlying juristic-person principle — a company cannot affix a personal EVC through Aadhaar-OTP because the company has no Aadhaar; authentication must be through an authorised office-bearer's Class 3 individual DSC with the company in the Organisation field. The rule applies to GSTR-1 (outward supply return), GSTR-3B (monthly summary return), GSTR-9 (annual return), GSTR-9C (reconciliation statement), REG-01 (new registration application), REG-14 (amendment) and every other GST filing by a corporate entity.

Section 139D Income Tax Act — DSC for ITR-6 companies

Section 140 — verification of the return

Section 140 of the Income Tax Act 1961 prescribes the categories of persons who can verify the return of income. For a company, Section 140(c) provides that the return shall be verified by the Managing Director, or where there is no Managing Director or where for any unavoidable reason the Managing Director is not able to verify, by any director thereof. For companies wound up under the Companies Act 2013, the return is verified by the liquidator. For non-resident companies, the return is verified by an authorised representative under Section 288 holding a valid power of attorney. The Section 140 verification operates through the principal officer's Class 3 individual DSC affixed to the ITR-6 JSON or XML file at the time of upload. The DSC's PAN must match the principal officer's PAN as captured in the ITR-6 verification block.

TDS returns and DSC under Section 200

Section 200(3) of the Income Tax Act 1961 read with Rule 31A of the Income Tax Rules 1962 prescribes the quarterly TDS return (Form 24Q, 26Q, 27Q, 27EQ) filing requirement. Companies are required to file the TDS return electronically with digital signature under Rule 31A(4A). The DSC is of the principal officer of the company or, where the deductor is a branch, of the branch's authorised officer. The TDS return DSC is administered through the TIN-NSDL portal and the TRACES portal under separate sub-user authorisations, with the principal Authorised Signatory's Class 3 DSC operating as the master credential. The TDS certificate generation in Form 16 (salary TDS) and Form 16A (non-salary TDS) on the TRACES portal also requires DSC affixation by the deductor before the certificate is treated as authenticated under Section 203.

Tax-audit upload and Section 44AB DSC interplay

Section 44AB read with Rule 6G of the Income Tax Rules 1962 requires every company carrying on business or profession with turnover exceeding the threshold to get its accounts audited. The tax audit report in Form 3CB / 3CD is prepared by a Chartered Accountant in practice and uploaded to the income-tax e-filing portal under Rule 12(1)(ba). The CA's Class 3 individual DSC carrying the ICAI membership number authenticates the audit report at the upload stage. The company's principal officer then accepts the audit report on the portal using the company's principal-officer Class 3 DSC. The two-stage DSC affixation — first by the CA on upload, then by the principal officer on acceptance — embodies the dual-accountability principle that protects both the company and the auditor in the tax-administration relationship. Rejection by the principal officer triggers a re-upload by the CA with revised positions.

AOC-4 rejection — Director DSC used in place of Company DSC

GSTR-9 annual return filed with expired Company DSC — Section 47 late fee

GSTR-1 DSC failure during peak filing — vendor token outage

IBC IRP DSC renewal missed during CIRP — moratorium filings frozen

Other Services in Aravind Nagar Thiruverkadu, Chennai

What Aravind Nagar Thiruverkadu Clients Say