XBRL filing is where accounting meets taxonomy — every number in your financials mapped to the MCA's tagging dictionary, validated, and filed. Done by people who understand both the accounts and the tags, it's routine. Done as a data-entry job, it generates exactly the MCA queries you don't want.
Certain companies must file their financial statements with the MCA in XBRL (eXtensible Business Reporting Language) format — a machine-readable tagging of every number, note, and disclosure to the MCA's taxonomy. It's not a PDF upload; it's a structured data file where each tag must match the taxonomy's definition precisely.
The work is detail-dense: mapping the trial balance and notes to taxonomy elements, creating extensions where the taxonomy doesn't cover a company-specific disclosure, validating against business rules, and filing. Errors don't just bounce — they raise questions about the underlying accounts.
Companies meeting the MCA's XBRL thresholds — listed companies, companies with turnover or paid-up capital above prescribed limits, and their subsidiaries. If you're unsure whether you fall in, you probably need to check rather than assume.
Companies whose auditors flag XBRL as a scope item every year — the tagging has to reconcile to the audited financials exactly, and last-minute tagging against a filing deadline is where errors breed. And groups where multiple entities need XBRL, multiplying the coordination load.
Every line of the financials — balance sheet, P&L, cash flow, notes — mapped to the current MCA taxonomy. Done by accountants who understand what each number means, so the tags reflect the economics, not just the labels.
Where your disclosures don't fit standard taxonomy elements, properly structured extension tags — documented and defensible, not creative workarounds that invite queries.
Full validation against MCA business rules before filing, then the filing itself with acknowledgement tracking. We validate until it passes clean — resubmissions are a failure we don't accept.
Tagged figures reconciled to the audited financials, rupee for rupee. The reconciliation is the evidence that the XBRL says what the accounts say.
Fixed fee per entity per year, quoted on complexity — a straightforward standalone is quick; consolidated financials with extensive notes take longer. Standard turnaround is 48 hours from final audited financials.
The critical path is always the audit finalisation. We engage early in the audit cycle so tagging starts the moment the numbers freeze, not after.
Mapping "other expenses" to the first taxonomy element with a similar name, without checking the definition. Taxonomy elements have precise meanings; label-matching produces filings that validate but misrepresent. Diligence and regulators read tags, not labels.
Creating extensions for things the standard taxonomy already covers, or using extensions to avoid understanding the taxonomy. Extensions should be rare, documented, and justified.
Starting XBRL after the audit is signed and the deadline looms. Rushed tagging is wrong tagging; the filing deserves its own slot in the calendar.
Applicability confirmed, prior-year filings reviewed, data requirements listed.
Financials mapped to taxonomy, extensions designed where genuinely needed.
Business-rule validation, reconciliation to audited accounts, corrections.
MCA filing with acknowledgement. Done, evidenced, archived.
Listed companies, companies above prescribed turnover/capital thresholds, and their subsidiaries must. We confirm applicability — don't assume either way.
Some do, as an add-on. Dedicated tagging by people who do it daily is faster and cleaner — and your auditor should be reviewing, not producing.
Extension tags, properly structured and documented. Genuine extensions are normal; lazy ones invite questions.
48 hours from final audited financials for standard cases. Consolidated or complex notes take longer.
Final audited financials with full notes, trial balance, and prior-year XBRL if any. We handle the rest.
It's structured data about your company, filed with the regulator and readable by anyone. Treat it with the seriousness it deserves.
We use the prior-year file as the base — consistency across years matters to ROC validation. Starting fresh each year creates mapping drift.
Yes, through revised filings — but the original stays on record. Get it right the first time; revisions invite questions.
Yes — standalone and consolidated are separate filings with their own tagging. The consolidation adjustments need careful mapping.
Copy-pasting prior-year tags onto changed numbers, and tagging notes without reading the taxonomy. Validation passes; accuracy fails.
Talk to a partner about your situation — no pitch, no obligation. If we're not the right firm for it, we'll tell you that too.
Request a consultation