Start with the auditor's return population
Rule 5 of the NFRA Rules, 2018 requires the auditor referred to in rule 3 to file the annual return in Form NFRA-2 by 30 November each year. The 2019 amendment substituted that date and inserted the form. For the annual 2026 preparation, the statutory date is 30 November 2026; distinguish that baseline from any specifically applicable later official relief. Historic extensions for early reporting years are not authority to extend this year's date.
Read the applicable text: NFRA-hosted Gazette: G.S.R. 636(E), rule 5 amendment and notified NFRA-2 NFRA: official NFRA-2 e-form entry point.
Separate coverage from completion of the form
First establish that the auditor and engagements are within the applicable NFRA framework, including any relevant continuing coverage. This guide assumes that scope review has been completed. It concerns assembling the auditor's return, not reperforming every rule 3 threshold or treating NFRA-2 as the company's ordinary ROC annual return. NFRA-1 and NFRA-2 serve different purposes and should not be interchanged merely because the same entity appears in both compliance files.
Use the notified period and report-date fields
Section 2 of the notified form identifies a reporting period beginning 1 April and ending 31 March. Section 4(a) asks for covered entities for which the auditor issued audit reports during that period, followed by entity and report particulars. For a 1 April 2025 to 31 March 2026 working, start from reports issued within those dates. Do not populate it only by selecting financial statements labelled FY 2025–26: an audit report's issue date and the accounts' underlying financial year are different facts.
Reconcile entities and reports separately
Build an entity master with supported identifiers, governance class and registered address. Link each report and its date, engagement partner and relevant quality-review partner particulars. Multiple reports or copied PDFs should not create fictitious additional legal entities. Conversely, merging reports into one entity row in an internal reconciliation must not discard report-level particulars required by the applicable form and instructions. Preserve both levels and resolve the live filing treatment from official instructions.
Bridge the fee ledger to received amounts
The notified domestic-client details ask for total fees and expenses received, categorised across statutory audit services, tax audit and other taxation services, attestation and certification services, non-audit services, and out-of-pocket expenses. The fifth notified category is expenses, not a generic other-services bucket. Reconcile the source ledger to those descriptions rather than using an unexplained total billed or treating every receipt as statutory audit fees. Preserve invoices, bank receipts, allocated advances and any supported classification adjustments. Where tax withholding or another item affects a receipt bridge, establish its treatment from the applicable instructions; this guide does not invent a universal gross-up rule.
Link report answers to the signed evidence
The form asks whether the audit report is modified and includes further professional-reporting information. The preparer should inspect the signed report rather than infer a response from a filename or the client's verbal description. A complete return is not established by matching only fees: identity, report dates, partner records and applicable declarations also matter. Do not invent a clean compliance assertion when an exception remains unresolved.
Preserve submission and correction evidence
Use NFRA's official e-form entry point and current instructions for the actual filing. The references here identify the notified form structure, not an assertion that every live screen is unchanged. Retain the final submitted version and acknowledgement, and reconcile any subsequent official query to that version. Preparing a spreadsheet or starting a draft does not prove filing. Check current official notices before relying on relief; neither a helpdesk request nor an old-year extension should silently replace the statutory calendar entry.
Six worked illustrations
All facts and amounts are fictional. Calculations illustrate the stated assumptions, not a predetermined legal outcome.
Illustrative example 1: Calendar the statutory baseline
For a 30 November 2026 statutory filing date, 7 November is 23 calendar days earlier. A preparation plan using 20 November leaves 10 calendar days to that baseline. These are internal planning intervals, not extra statutory filing periods or confirmation of any extension.
Illustrative example 2: Reports straddling the period end
For a working covering 1 April 2025 to 31 March 2026, a report issued 30 March 2026 falls inside and a report issued 2 April 2026 falls outside that date population. The two issue dates are 3 days apart. Classify by the actual reporting requirement rather than assuming both belong because their underlying accounts share a year label.
Illustrative example 3: Do not confuse report count and entity count
An internal report register has 8 genuine reports for 6 covered entities. The entity count is 6, not 8. Keep the two additional report occurrences linked to their entities so report-level details remain available for the required filing treatment.
Illustrative example 4: Classify received fees
Assume accepted receipt classifications of ₹500,000 statutory audit, ₹150,000 tax/taxation services, ₹80,000 attestation/certification and ₹70,000 non-audit services, with nil out-of-pocket expenses and no other amounts. Total received is ₹800,000. Reporting the entire total under statutory audit would misclassify ₹300,000 on these facts.
Illustrative example 5: Billing and receipts are not identical
A supported source ledger shows ₹1,000,000 billed and ₹750,000 received on the assumed consistent basis, leaving ₹250,000 outstanding. The receipt-based preparation must explain that bridge; it should not copy billed fees into a field asking for received amounts merely to match the revenue ledger.
Illustrative example 6: A missing report-status review remains open
Of 10 report records requiring review, 8 have been checked against signed reports and 2 remain unchecked. Evidence coverage is 80%, with 20% unresolved. Do not represent the whole report-status population as verified until those two records are checked.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Confirm the auditor's obligation | Completed NFRA scope analysis and auditor identity. |
| 2 | Record the calendar basis | Statutory 30 November date and any separately verified applicable relief. |
| 3 | Fix the reporting period | Notified period fields and the selected annual working. |
| 4 | Build the entity master | Legal identifiers, address and covered class. |
| 5 | Index audit reports | Issue dates, signed versions and relevant period selection. |
| 6 | Reconcile partner particulars | Engagement and applicable quality-review records. |
| 7 | Check report-status answers | Signed reports and supported exceptions. |
| 8 | Bridge fees and expenses received | Receipt ledger, invoices, categories and unresolved classification items. |
| 9 | Validate against current official instructions | Final form, declarations and consistent entity/report populations. |
| 10 | Verify actual submission | Acknowledgement, submitted version and follow-up record. |
Sixteen practitioner FAQs
1. Who files the annual NFRA-2 return?
The auditor referred to in the applicable rule 3 framework, under rule 5.
2. Is it the company's usual ROC annual return?
No. Keep the auditor's NFRA return distinct.
3. What is the statutory annual date?
30 November under the amended rule 5.
4. Can an old reporting-year extension be applied to 2026 automatically?
No. Establish specifically applicable current relief.
5. Is a preparation target a statutory extension?
No. Internal planning dates do not change the filing rule.
6. Where are the notified period fields?
Section 2 of the form states the 1 April to 31 March reporting period.
7. Why retain audit-report issue dates?
Section 4(a) identifies reports issued during the reporting period.
8. Can underlying account-year labels replace issue dates?
Not without applying the actual reporting requirement.
9. Are entities and reports necessarily the same count?
No. Preserve both populations and their links.
10. Can duplicate report PDFs create new clients?
No. Identify unique legal entities and genuine reports.
11. Does the notified field ask only for total fees billed?
Its domestic-client details ask for fees and expenses received in the stated categories.
12. Should all service receipts be called audit fees?
No. Reconcile the service categories and the separate out-of-pocket-expenses category to supported receipts.
13. Does this guide prescribe a withholding-tax gross-up?
No. Resolve that treatment from applicable instructions and evidence.
14. Can modified-report answers rely on a verbal assurance?
Check the actual signed report and required particulars.
15. Does a saved draft prove submission?
No. Preserve the final acknowledgement and submitted version.
16. Where should the live filing workflow be checked?
NFRA's official NFRA-2 entry point and current official instructions.
Official sources
NFRA-hosted Gazette: G.S.R. 636(E), rule 5 amendment and notified NFRA-2 NFRA: official NFRA-2 e-form entry point