Before financials are tagged in XBRL for filing with the Registrar, the auditor should confirm the company's applicability to XBRL filing under the current MCA rules, verify that every line item, note disclosure and sub-total tagged in the XBRL instance document ties back exactly to the signed financial statements with no rounding or sign reversal, confirm the correct taxonomy and element mapping was used for each item rather than a generic nearest-match element, and validate the instance document against the MCA's validation tool before certification; the exact applicability class and current taxonomy version should be confirmed against the current MCA notification.
Applicability check
Not every company filing financial statements with the Registrar is required to file in XBRL; applicability is driven by criteria such as listing status, paid-up capital, turnover, or being a subsidiary or associate of a company already required to file in XBRL. Confirm the company's applicability status independently each year, since crossing a threshold or a change in group structure can bring a company into scope that was not required to file in XBRL previously.
Tagging accuracy checks
- 01Tie every tagged figure back to the signed financial statements line by lineThe instance document should reproduce the signed balance sheet, profit and loss account, cash flow statement and notes exactly; a single transposed figure or a note total that does not add up in the tagged version is a filing error even if the underlying financials are correct.
- 02Check sign conventions on expense, contra and negative itemsItems that are naturally negative, such as a loss, a deduction, or a contra-asset, need the correct sign convention in the taxonomy; a sign error here silently inverts the figure in any downstream analysis of the filed data.
- 03Confirm the taxonomy element chosen matches the nature of the item, not just its labelWhere no exact taxonomy element exists for a specific disclosure, the company may need to use an extension element rather than forcing the figure into an ill-fitting standard element; review any such mapping decisions specifically.
- 04Check unit and scale consistency across the documentFigures reported in lakhs, crores or absolute rupees in different parts of the statements need consistent scale tagging; a scale mismatch between the balance sheet and a note can misstate a figure by orders of magnitude in the tagged data even though the printed document is correct.
- 05Validate against the MCA's own validation tool before certificationRun the instance document through the prescribed validation tool and resolve every error and warning flagged, rather than certifying based on the printed PDF rendering of the XBRL document looking correct.
The PDF rendering generated from an XBRL instance can look identical to the signed financial statements even when the underlying tags are wrong, because the rendering is driven by presentation linkbase, not by the data values. Checking the rendered PDF alone is not sufficient; the underlying tagged values need to be checked.
Regulatory requirement
The exact applicability criteria, the taxonomy version to be used for the filing year, and the validation requirements are set out in the Companies Act rules on filing of financial statements and the MCA's XBRL filing instructions as currently in force. Confirm all of these against current source material before filing.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- CARO & Companies ActBooks of account compliance under the Companies ActWhat proper books of account require under the Companies Act, the audit-trail-software requirement, and how to test whether it is actually switched on.
- Audit workflow & automationSA 700: forming an opinion, and what "true and fair" actually requires concluding onFinishing every planned procedure isn't the same as forming an opinion. SA 700 is the step that happens after the checklist, not instead of it.
- Audit data & extractsTrial balance mapping for audit softwareMapping a client's idiosyncratic ledgers to a standard chart of accounts is the step that decides whether analytics and disclosures work at all, and the one most firms rush.
- Technology, data & AI in auditThe audit trail rule: what accounting software must doThe feature is usually present in the software and switched off, not missing. How to actually test which one is true before relying on it.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.