Blogs / Company and LLP Compliance

Company and LLP Compliance

AOC-4 and Financials: Reconcile the Filing Data before Upload

A practical guide to aoc-4 and financials, with a worked example, evidence checklist, common mistakes and steps to prepare a defensible working.

By Team assureOffice
Published 2026-10-11
AI SummaryQuick overview

AI Summary

A practical guide to aoc-4 and financials, with a worked example, evidence checklist, common mistakes and steps to prepare a defensible working. • AOC-4 preparation should reconcile the approved financial statements, board and auditor information, and the selected filing variant. • Copying lakhs into rupee fields: check the evidence before finalising. • Keep the applicable period and source records clear.

Financial statements and the filing working use different units and note totals. The useful result is a working that explains the facts, the calculation or classification, and the evidence behind the conclusion. This guide shows how to prepare that working and where a reviewer should investigate before accepting the result.

Scope and applicable period

Indian company or LLP compliance, as identified in the article, with FY 2025–26 illustrative records. Use the current notified rules and relevant form for the actual reporting period.

Verification date: 11 October 2026. Figures and rates identified as assumptions are teaching examples; apply the stated conditions and the actual facts to a real assignment.

The key principle

AOC-4 preparation should reconcile the approved financial statements, board and auditor information, and the selected filing variant. The form is not a substitute for signed accounts. Determine whether ordinary AOC-4, an XBRL route or another applicable variant is required before entering figures. Check units, standalone versus consolidated reporting and attachments against the current instruction kit.

Worked example

ItemValue or factWhat it means
Signed revenue₹1,25,00,000Source financial statements
Form unitRupeesConfirm current field requirement
Mistyped entry₹1,25,000100-fold understatement
Correct reconciliation₹1,25,00,000Matches signed source

A units error can survive a technically valid upload. Use a cross-reference sheet mapping each form amount to the signed statement or note, including previous-year figures where required. Review the dates of approval, signing and adoption, and verify the legal filing time limit or any official extension separately. The final evidence pack should contain the submitted form, attachments and acknowledgement. Correcting a portal field must not silently change the underlying signed financial statements.

A practical sequence

Select the applicable filing variant and reporting basis before data entry. Map each financial amount to the approved statements, with units and rounding recorded.

Verify attachments, dates, auditor details and required approvals against current instructions. Review the generated form before submission and preserve the exact submitted version.

Reconcile any resubmission to the earlier filing; a technical rejection does not authorise unexplained changes to signed accounts.

Build one evidence file with separate legal conclusions

Corporate compliance often uses the same source records as the accounts, but each filing, approval and auditor-reporting requirement has its own purpose. Establish the entity type and applicable rules before selecting a form or threshold. Reconcile submitted figures to approved source records and retain the actual acknowledgement. Keep accounting recognition, statutory approval and filing status separate in the working. A completed form does not establish that the underlying transaction was properly authorised or correctly accounted for. Review changed ownership, contracts and business facts instead of carrying forward last year’s conclusion without support.

Evidence checklist

Keep the following records linked to the same entity, period and working version. Identify missing items explicitly; a checked box should mean the document was examined and supports the stated conclusion.

  • Approved and signed statements
  • Board and adoption records
  • Auditor report and particulars
  • Field-to-note mapping
  • Submission acknowledgement

Common mistakes and how to avoid them

  • Copying lakhs into rupee fields. Compare the conclusion with the approved and signed statements and resolve any conflicting facts.
  • Uploading unsigned working accounts. Trace the affected item to the auditor report and particulars before finalising the working.
  • Mixing standalone and consolidated figures. Use the submission acknowledgement to make the final position and remaining exceptions clear.

Before you finalise

Recheck the example’s assumptions against the actual assignment, resolve the identified exceptions and make the final figure or conclusion traceable to its source. Preserve the reviewed version and the reason for material changes. For this task, the submission acknowledgement should agree with the conclusion presented to the client, reviewer or authority.

Frequently asked question

Does successful upload certify financial accuracy? No. Portal validation and substantive reconciliation are separate controls.

Sources and further reading

Related guide: Notes to accounts preparation financials builder.