ICAI Guidelines for CA Certificates

A Certificate Is Not the Same Thing as a Report

The distinction ICAI draws first is between a report and a certificate. A report carries an opinion, expressed with the qualifications an opinion needs. A certificate is a statement of fact verified against records, and it leaves far less room to hedge. That is why the wording of a certificate is short and why a member is careful about what it does and does not cover.

The Guidance Note on Reports or Certificates for Special Purposes governs this territory. It covers engagements where a member certifies something for a bank, a regulator, a consulate or a court rather than auditing financial statements. It sets what the member must do before signing and what the document must disclose about its own basis.

The Assurance the Member Is Actually Giving

A certificate under this framework is a reasonable assurance engagement. The member is not merely reproducing what the client supplied; they are obtaining evidence sufficient to state the fact certified. Where the evidence supports only part of what is asked, the certificate is limited to that part rather than stretched to cover the rest.

This is the practical reason a member declines work more often than clients expect. A request to certify a figure the records do not carry asks for assurance that cannot be supported. The professional answer is to fix the records first.

UDIN, and Why Every Certificate Carries One

Since 1 February 2019, a Unique Document Identification Number has been mandatory on certificates issued by practising chartered accountants. It is generated on the ICAI portal against the member's registration and printed on the document.

Its purpose is verification by the recipient. A bank or consulate holding a certificate can confirm that the number resolves to the member named on it. That makes a forged certificate harder to pass, and it is the first thing a careful recipient checks, ahead of reading the figures.

Independence: Who a Member May Not Certify

The Code of Ethics bars a member from certifying where their objectivity is compromised. In practice that rules out certifying one's own work, and certifying an entity in which the member or firm holds an interest. It also rules out certifying where a relationship would lead a reasonable reader to doubt independence.

The same logic runs through the Companies Act restrictions on an auditor providing other services to an audit client. The principle is consistent: the person who writes the underlying records should not be the person certifying them.

Wording, Recipient Formats and What Cannot Be Signed

Recipients frequently supply their own proforma, and a member may complete it, but not at the cost of certifying something untrue. Where a supplied format asks for a statement the evidence does not support, the member amends the wording or attaches a note rather than signing as printed.

Certificates also state their own scope: what was examined, the basis of any valuation, and the date the position relates to. A certificate that omits its basis is weaker for the client, because the reader cannot tell what it rests on.

The File Behind the Signature

Standard on Quality Control 1 requires engagement documentation to be retained for no shorter than seven years from the date of the report. For certification work that means the evidence, the representation obtained and the reasoning behind any valuation basis stay on file.

This is what makes a certificate defensible when it is questioned long after issue, which is common in lending and litigation. A member who cannot produce the file is in a materially worse position than one who can, regardless of whether the original figure was right.

Peer Review, and Why It Reaches Certification Work

Peer review examines whether a practice unit's systems actually produce the quality its reports assert, and it looks at documentation rather than at opinions. For certification work the question a reviewer asks is simple and awkward: for this certificate, what evidence was on file, and does it support what was signed.

That is why the discipline described above is not merely good practice. A firm issuing certificates without a traceable file will not fail because a figure was wrong; it will fail because nobody can show how the figure was reached. The certificate and the file behind it are treated as one document.

For a client choosing who signs, this is the practical significance of asking whether a firm is peer reviewed. It says nothing about any single certificate, but it says a good deal about whether the firm keeps the records that make its certificates hold up later.

What Happens When a Certificate Is Challenged

Challenges usually arrive from one of three directions: a lender re-examining a file after a default, an opposing party in litigation, or a regulator reviewing an application. In each case the certificate is read alongside something else, and the question is whether the two agree.

The member's position then rests entirely on what was documented at the time. A valuation basis named on the face of the certificate is defensible even if another valuer would reach a different figure. The reader was told what they were being given. An unnamed basis is not, because there is nothing to compare the challenge against.

This is the concrete reason certificates are written narrowly. A member who certifies exactly what the evidence supports, and says what it rests on, is in a sound position when the document is tested. Wider wording buys the client nothing and costs the member the ability to defend it.