Financial Reporting SOP Drafting: Calendar, Ownership, Review Controls

Financial reporting SOP drafting is the work of turning a close process that depends on one person into a written procedure an auditor can test and an investor can rely on. In India the document has three jobs. It fixes a reporting calendar against the clocks in the Companies Act 2013, it names an owner and a reviewer for every output, and it defines the review controls that leave evidence behind. Since 01/04/2023 it must also account for the non-disableable audit trail required by the proviso to Rule 3(1) of the Companies (Accounts) Rules 2014. This guide shows how to draft each part.

What should a financial reporting SOP contain?

A financial reporting SOP should contain a scope clause, a reporting calendar tied to statutory deadlines, a role-based ownership matrix with a separate preparer, reviewer and approver for each output, a list of review controls with thresholds and evidence, an exceptions route, an audit trail clause under the proviso to Rule 3(1) of the Companies (Accounts) Rules 2014, and version control.

What does a financial reporting SOP cover, and where does it stop?

A financial reporting SOP covers the path from a closed ledger to a signed, filed and communicated set of numbers: management reports, statutory financial statements, filings that depend on the books, and investor reporting. It stops short of daily bookkeeping, spending approvals and the day-by-day close, which sit in separate SOPs that this one references.

The boundary matters because most finance teams hold fragments: a close checklist in a spreadsheet, an approval matrix in an email, an MIS template in the board folder. A financial reporting SOP joins them into one answer to one audit question: for each report, when is it due, who owns it, who reviews it and what proof shows the review happened.

The table shows which document answers which question, so the reporting SOP points to the others instead of copying them.

Which document answers which question

Question	Document	Scope	Treelife guide
Who approves a payment, and what stops one person initiating and releasing it?	Payments and approvals SOP	Approval matrix, segregation of duties	Startup financial controls
How is the month closed in a fixed number of days?	Close SOP	Day-by-day close tasks	Month end close checklist
What goes into the board pack and who signs it?	Board pack procedure	Pack contents, timeline, sign-off	Board reporting pack preparation
Which metrics does management track, and how often?	MIS definition	KPI list and cadence	MIS reporting for founders
When is each report due, who owns it, who reviews it, what proof is kept?	Financial reporting SOP	Calendar, ownership, review controls	This guide

The SOP must also name the accounting framework. Financial statements give a true and fair view and follow Schedule III and the accounting standards notified under Section 133 (Section 129(1), Companies Act 2013). Companies below the Ind AS limits report under the Accounting Standards, while Ind AS applies to unlisted companies with net worth of ₹250 crore or more and to their holding, subsidiary, joint venture and associate companies, and once it applies it cannot be reversed (Rule 4, Companies (Indian Accounting Standards) Rules 2015). The framework changes the disclosure checklist and the review controls, so state it in clause 2. Our guide on Ind AS applicability for private companies covers the test.

Write the scope clause as a list of deliverables, not departments. A usable clause names the monthly MIS pack, statutory reconciliations, annual financial statements, the auditor request list, AOC-4, MGT-7, the tax audit report and return inputs, and investor and lender reports. An output that is not on the list has no owner.

Which statutory clocks should the financial reporting calendar be built around?

Build the financial reporting calendar backwards from the Annual General Meeting, which must be held within six months of the financial year end (Section 96(1), Companies Act 2013). AOC-4 follows within 30 days of the AGM (Section 137(1)) and the annual return within 60 days (Section 92(4)). For a 31/03 year end with an AGM on 30/09, that gives 30/10 and 29/11.

These dates move with the AGM, not with the calendar. A company that held its FY 2025-26 AGM on 30/09/2026 files AOC-4 by 30/10/2026 and the annual return by 29/11/2026. Write the formula, not a typed date.

Annual reporting anchors for a company with a 31/03 year end

Milestone	Rule	Date or formula	SOP design note
Annual General Meeting	Section 96(1), Companies Act 2013	Within six months of year end, so 30/09	Registrar can extend by up to three months for a special reason (proviso to Section 96(1)); an exception, not a plan
Notice of AGM	Section 101(1)	At least 21 clear days before the meeting	Board approval of the statements comes before the notice goes out
Board approval and signing of financial statements	Sections 129 and 134(1)	Before the AGM notice	Signatories fixed by board resolution
Statutory auditor’s report	Section 143	Signed before board approval	Includes the Rule 11(g) audit trail comment
AOC-4	Section 137(1)	AGM date plus 30 days	Computed from the AGM date; FY 2025-26 only: fee-free to 31/12/2026 (General Circular 05/2026)
Auditor appointment filing, ADT-1	Section 139, Rule 4 of the Companies (Audit and Auditors) Rules 2014	AGM date plus 15 days [verify rule]	Not covered by the FY 2025-26 fee relaxation
MGT-7 or MGT-7A	Section 92(4)	AGM date plus 60 days	Computed from the AGM date; FY 2025-26 only: fee-free to 31/01/2027 (General Circular 05/2026)
Consolidated financial statements, where subsidiaries, associates or joint ventures exist	Section 129(3), Companies Act 2013	Prepared with the standalone statements; AOC-4 CFS on the same 30-day clock	Set subsidiary cut-offs earlier than the parent and reconcile intercompany balances before consolidation
Tax audit report	Section 44AB (1961 Act) for FY 2025-26; Section 63 and Form 26 (Income-tax Act 2025, Income-tax Rules 2026) for tax years starting on or after 01/04/2026	One month before the return due date under Section 263(1)	Keep a rule log, because section numbers and forms changed on 01/04/2026
Income tax return, audit cases	Section 139(1) (1961 Act) for FY 2025-26; Section 263(1) (2025 Act) from tax year 2026-27	FY 2025-26: 31/10/2026, extended to 21/11/2026 for companies and other audited assessees without transfer pricing; tax year 2026-27: 31/10, or 30/11 where transfer pricing applies	Form 26 falls due 30/09 or 31/10 respectively; point the SOP to the rule log, not a typed date

The tax rows need care this year. Income earned in FY 2025-26 is still governed by the Income-tax Act 1961, and its tax audit report is filed in Forms 3CA or 3CB with 3CD under Section 44AB. For tax years starting on or after 01/04/2026, the report is filed in Form 26 under Section 63 of the Income-tax Act 2025, due one month before the return due date under Section 263(1) (Income Tax Department, Form 26 FAQs, 2026). For FY 2025-26, CBDT Circular No. 07/2026 dated 28/09/2026 moved the audit report date to 21/10/2026 and the return date to 21/11/2026 for companies and other audited assessees where Section 92E does not apply (Sl. No. 2 of the table in Explanation 2 to Section 139(1)); transfer pricing cases keep 31/10/2026 and 30/11/2026. Dates move by circular, so the SOP should point to a dated rule log and not embed them.

Late filing costs more than a fee. Default on AOC-4 or MGT-7 attracts an additional fee of ₹100 per day, per form, with no cap (first proviso to Section 403, Companies Act 2013, read with Rule 12 of the Companies (Registration Offices and Fees) Rules, 2014). For FY 2025-26 only, MCA General Circular No. 05/2026 dated 24/10/2026 allows AOC-4 and its variants to be filed up to 31/12/2026, and MGT-7 and MGT-7A up to 31/01/2027, without additional fees. It does not extend the AGM deadline, and a filing made after those dates carries additional fees counted from the original due date, not from the extended date. GST, TDS and advance tax dates sit alongside these; reference the Treelife compliance calendar 2026 from the SOP and own only the reporting deliverables.

One legislative change is pending and belongs in the rule log. The Corporate Laws (Amendment) Bill 2026 was introduced in the Lok Sabha on 23/03/2026 and the Joint Committee presented its report on 03/08/2026; as of 25/10/2026 it had not been passed (PRS Legislative Research). It proposes to raise the small company limits to ₹20 crore paid-up capital and ₹200 crore turnover (Section 2(85)), to allow hybrid AGMs, to exempt prescribed small companies from appointing an auditor, and to move books of account defaults to civil penalties. None of it applies until enactment and notification, so write the current rule into the SOP.

How do you set internal deadlines in the financial reporting calendar?

Set internal deadlines by subtracting a fixed buffer from each statutory limit and then stacking the dependencies: books closed, draft statements to the auditor, signed audit report, board approval, AGM notice. A buffer of about 15 days on the AGM, with shorter buffers on each dependency, lets one step slip without moving the AGM. Buffer length is a design choice, not a legal requirement.

The worked example below uses a 31/03/2027 year end and an AGM target of 15/09/2027, which is 15 days inside the 30/09/2027 limit. All internal dates are illustrative design values.

Worked calendar for FY 2026-27, working back from an AGM target of 15/09/2027

Milestone	Target date	Statutory limit	Buffer
Books closed and trial balance frozen	15/05/2027	None, internal	Not applicable
Draft financial statements to auditor	15/06/2027	None, internal	Not applicable
Auditor’s report signed	17/08/2027	Before board approval	Set by the audit plan
Board approves and signs statements	18/08/2027	Before AGM notice	Set by the audit plan
AGM notice dispatched	20/08/2027	24/08/2027 for a 15/09/2027 AGM (Section 101(1))	4 days
AGM held	15/09/2027	30/09/2027 (Section 96(1))	15 days
AOC-4 filed	22/09/2027	15/10/2027 (Section 137(1))	23 days
MGT-7 filed	06/10/2027	14/11/2027 (Section 92(4))	39 days

Mark the critical path before you fix any date. In annual reporting it runs from sub-ledger cut-off to reconciliations, trial balance freeze, draft statements, audit fieldwork, signed report, board approval, AGM notice and AGM. A line on that chain with no slack moves the AGM when it slips, so give it the shortest escalation window.

Two rules make the calendar usable. First, every line has a named owner and backup. Second, a slippage rule: when a milestone slips by more than three working days, the owner tells the finance head the same day, and the finance head decides whether to move dependent dates or add resource.

Each calendar line carries eight fields: the output by name, the owner and reviewer as roles, the date or formula with the statutory limit it protects, the dependency, the evidence location, the rule reference, a definition of done (for example “reviewed pack uploaded, comments cleared, tie-outs attached”) and an escalation route.

Recurring outputs need their own cadence lines beside the annual ones:

• Monthly: MIS pack, and GST, TDS and provident fund tie-outs to the books
• Quarterly: TDS return agreed to the ledger, investor or lender update, sample test of review controls
• Annually: the table above, the disclosure checklist and the auditor request list

The day-by-day mechanics of the monthly close belong in the close SOP, covered in our month end close checklist. The reporting SOP only states the date by which the closed ledger must be available.

Who owns each step of financial reporting in the SOP?

Every reporting output needs one accountable owner, a preparer who is not the reviewer, and an approver who is not the preparer, all named by role and not by person. Role-based naming keeps the SOP valid when someone resigns, and the three-role split shows the auditor that review was independent.

Ownership matrix for financial reporting outputs (roles, not names)

Output	Preparer	Reviewer	Approver	Cover when absent
Monthly MIS pack	Finance executive	Finance manager	Finance head	VCFO or senior accountant
GST, TDS and provident fund tie-outs to books	Finance executive	Finance manager	Finance head	Compliance lead
Draft annual financial statements	Finance manager or VCFO	Finance head	Board of directors	VCFO
Auditor request list and management representation	Finance manager	Finance head	Authorised director	Company secretary
AOC-4 and MGT-7	Company secretary	Finance head	Authorised director	External company secretary
Tax audit report and return inputs	Finance manager	Finance head	Authorised director	External tax adviser
Investor and lender reporting	Finance manager	Finance head	Founder-director	VCFO

Six ownership rules belong in the clause that sits above the matrix:

• One accountable owner per output: shared ownership means no ownership
• Reviewer is never the preparer: a review by the person who built the number is not a control
• Approver sees the reviewed version: the approved file carries the version stamp the reviewer saw
• Outsourced preparation, internal accountability: if a virtual CFO or CA firm prepares an output, the company’s finance head still reviews or approves it, and the SOP states the turnaround for each outsourced step, for example draft pack by working day 6 and review by working day 8 [illustrative]
• Absence cover: a named backup with system access granted before the absence, not during it
• Sub-certification: payroll, payables, receivables and compliance owners confirm in writing that their inputs are complete and cut off before the finance head approves the pack

Signing is its own step. The board approves the statements, and they are signed for it by the chairperson if authorised, or by two directors, one being the managing director and CEO where appointed, with the CFO and company secretary where appointed (Section 134(1), Companies Act 2013). The SOP records the signatories, where each digital signature token is held and who holds the backup.

With a two-person finance team the reviewer is often a founder-director. Write that down, give the founder a one-page review checklist, and add a compensating control such as a quarterly external review, as set out in our guide to startup financial controls.

Which review controls belong in a financial reporting SOP?

A financial reporting SOP should list each review control by name, state what the reviewer checks, set a numeric threshold for investigation, and name the evidence kept. A control without a threshold and evidence is a statement of intent, and an auditor cannot test intent.

A risk control matrix, or RCM, is the document auditors and diligence teams ask for: it ties each financial reporting risk to the assertion it threatens, the control that answers it, the control type, how often it runs, who owns it and what evidence it leaves. The table below is the reporting slice of that matrix.

Review controls to write into the SOP (thresholds are illustrative design values, set yours from materiality)

Control	Assertion protected	Type and frequency	Investigation threshold	Evidence kept
Bank reconciliation sign-off	Existence and completeness of cash	Detective, monthly	No unreconciled item older than 30 days [illustrative]	Signed reconciliation with statement attached
Sub-ledger tie-out	Completeness and accuracy	Detective, monthly	Zero unexplained difference	Tie-out sheet with reviewer comment
GST tie-out	Accuracy and completeness of revenue and input credit	Detective, monthly	Difference above ₹10,000 a month, explained [illustrative]	Reconciliation file linked to the return period
TDS tie-out	Completeness of liabilities	Detective, monthly and quarterly	Zero difference	Challan and return acknowledgement
Flux review	All assertions, through unusual movements	Detective, monthly	Movement above 10 percent and ₹5 lakh together [illustrative]	Written commentary on every line above threshold
Manual journal review	Occurrence and accuracy	Preventive, per entry	Every entry above ₹1 lakh, sample below that [illustrative]	Journal log with approver and support reference
Cut-off and accrual review	Cut-off and completeness	Detective, monthly	Any item above ₹5 lakh [illustrative]	Accrual schedule with reversal date
Intercompany reconciliation	Existence and completeness of related balances	Detective, monthly	Zero difference before consolidation	Signed counterparty confirmation
Report logic and spreadsheet review	Accuracy and presentation	Preventive, on every change	Any change to a mapping or formula	Change log with reviewer initials and date
User access review	Integrity of records	Detective, quarterly	Any posting right not in the role list	Dated access report signed by the finance head
Disclosure review	Presentation and disclosure	Detective, annually	Complete before audit fieldwork starts	Signed Schedule III and standards checklist, updated for the year’s standard amendments
Audit trail attestation	Integrity of the books	Detective, monthly	No exceptions	Dated attestation by the finance head

The assertion column is what separates a control list from a risk control matrix. Write each risk as a statement about the accounts, for example “revenue is recorded in the wrong month”, and name the assertion it threatens: existence, completeness, accuracy, valuation, rights and obligations, cut-off or presentation.

Evidence decides whether a control survives audit. The standard that holds is a system record: a timestamp, a user ID and a comment on the file or ticket. Write sign-off wording that names the check, such as “reviewed and agreed to bank statement”, never just “reviewed”.

State each threshold as a percentage and a rupee floor together. A flat rupee limit is loose on a small line and meaningless on a large one.

Auditors test these controls because of Section 143(3)(i), which requires the statutory auditor to report on whether adequate internal financial controls over financial reporting exist and operate effectively. A private company is exempt if it is a one person company or a small company, or if its turnover is below ₹50 crore and its borrowings are below ₹25 crore, and only when it has no default under Section 137 or Section 92 (MCA notification G.S.R. 583(E) dated 13/06/2017, corrected by S.O. 2218(E) dated 13/07/2017 to read “and”, and MCA General Circular 8/2017 dated 25/07/2017). Every company’s board report states the adequacy of internal financial controls with reference to the financial statements (Section 134(3)(q) read with Rule 8(5)(viii), Companies (Accounts) Rules 2014), although Rule 8 does not apply to one person companies and small companies [verify current Rule 8 proviso]. From tax year 2026-27 the tax auditor also reports transactions not covered in the TDS and TCS returns after the latest correction statement (Form 26 FAQs, 2026), so run the TDS tie-out against the corrected return.

The ICAI Guidance Note on Audit of Internal Financial Controls Over Financial Reporting rests on five control components [verify component names and current edition on the ICAI portal]. The table shows where each lives in the SOP.

Where the SOP answers each control component

Control component	SOP clause that answers it	What the auditor looks for
Control environment	Scope, ownership matrix, delegation and sign-off authority	Named roles, independence of reviewer, board approval of the SOP
Risk assessment	Assertion column in the control table	Risks written against assertions, not generic headings
Control activities	Step procedures and review controls	Thresholds applied and evidence produced each period
Information and communication	Calendar, escalation route, board and investor reporting	Dated hand-offs, timely escalation, one version of the numbers
Monitoring	Walkthrough tests, deficiency log, retrospective, version history	Deficiencies logged, fixed by a date and re-tested

The audit trail clause deserves its own paragraph because it is the one control the law names directly. Every company using accounting software must use software that records an audit trail of each transaction, creates an edit log of each change with its date, and cannot have the audit trail disabled, for financial years starting on or after 01/04/2023 (proviso to Rule 3(1), Companies (Accounts) Rules 2014, G.S.R. 205(E) dated 24/03/2021, deferred by G.S.R. 235(E) dated 31/03/2022). The statutory auditor reports on it under Rule 11(g) of the Companies (Audit and Auditors) Rules 2014, read with Section 143(3)(j). From FY 2024-25 that report also covers whether the audit trail was preserved as record retention rules require (ICAI Implementation Guide on Reporting under Rule 11(g), revised 2024), so FY 2025-26 is the third reporting year. Books must stay accessible in India, and a daily backup must sit on servers physically located in India (Rule 3(1) and Rule 3(5), as amended by G.S.R. 624(E) dated 05/08/2022). The Income-tax Rules 2026 repeat this in Rule 46, and Form 26 requires the tax auditor to report the server location and the address of the India-located backup server (Form 26 FAQs, 2026).

The SOP clause should therefore say three things:

• Edit log: switched on in every module that posts to the books, with no user able to disable it
• Attestation: the finance head confirms monthly that the log was on and the backup ran
• Location: books and backup sit where Rule 3 of the Companies (Accounts) Rules 2014 and Rule 46 of the Income-tax Rules 2026 require, including where a group ERP is hosted abroad, with the server details ready for Form 26

Financial reporting SOP drafting: what does the document itself look like?

Draft the SOP as numbered clauses a reviewer can audit line by line: purpose and scope, accounting framework, calendar, ownership, step procedures, review controls, exceptions, audit trail, systems, and version history. Keep each procedure to one page and reference, not repeat, the close and payments SOPs. Use this skeleton as a financial reporting SOP template.

1. Purpose and scope: outputs and entities covered, and exclusions
2. Accounting framework: Accounting Standards or Ind AS, Schedule III, group overlay
3. Reporting calendar: statutory anchors as formulas, internal targets, slippage rule
4. Ownership matrix: preparer, reviewer, approver and cover for each output
5. Step procedures: one table per output, in the order the system forces
6. Review controls: the control table with thresholds and evidence
7. Exceptions: late inputs, post-approval adjustments, restatements, and who authorises each
8. Audit trail and records: Rule 3(1) proviso, Rule 3(5) backup, retention
9. Systems and access: accounting software, MIS tool, role access list
10. Document control and version history: SOP ID, owner, approver, classification, effective date, next review date, reason for change, rule log

The step table is where most SOPs go vague. The sample shows the standard: one action per line, a role, the system, a due day and the control that fires.

Sample step table for the monthly MIS pack (working day numbers are illustrative)

Step	Role	System and output	Due	Control
Lock the period after close sign-off	Finance manager	Accounting software, period lock	Working day 5	Close sign-off
Extract trial balance and map to MIS format	Finance executive	Trial balance export, mapping sheet	Working day 6	Sub-ledger tie-out
Prepare MIS pack and flux commentary	Finance executive	Draft pack with commentary	Working day 7	Flux review
Review commentary and tie to GST and TDS	Finance manager	Reviewed pack, comments logged	Working day 8	GST and TDS tie-outs
Approve and release	Finance head	Approved pack, release log	Working day 9	Approval log

Write each procedure by watching the work happen, not by recalling it: sit with the preparer for one full cycle, note every hand-off, then correct the process before documenting it. SOPs that fight the software are ignored within a month.

The exceptions clause carries weight. When a number changes after board approval, for example a late audit adjustment, the same approver re-approves it, a note records what moved, and every pack that carried the old figure is re-issued.

Version control keeps the document auditable. Each version carries a number, an effective date, the approver, the reason for change and a short rule log of statutory triggers, such as the start of the Income-tax Act 2025 on 01/04/2026. An auditor can then see which version applied to the period under review.

How do you test and maintain a financial reporting SOP?

Test the SOP by walking one real reporting cycle through it before the audit, logging every step that was skipped, improvised or undocumented, and fixing the SOP or the practice. Then review it once a year before 01/04 and after any trigger event.

The walkthrough runs in seven steps:

1. Pick a closed cycle: the last completed month and, if available, the last annual close
2. Trace the evidence: for each output, find the evidence the SOP says should exist, and note what is missing
3. Log deficiencies: step, gap, owner and a fix date set by severity, shorter for gaps touching statutory filings or the audit trail
4. Fix the cheaper side: change the SOP if the practice is sound, the practice if the SOP is sound
5. Brief the auditor: share the SOP and evidence trail before fieldwork and ask which controls they plan to test
6. Run a live cycle: operate the next cycle under the SOP and keep the evidence as you go
7. Hold a retrospective: within five working days of the cycle, review the metrics below and record what changes in the next version

Rollout hygiene matters as much as drafting, so tie each item to a reporting output:

• Single SOP owner: the finance head, with approvals in the version history
• Central repository: one folder with version history, linked from the calendar
• Training record: each preparer and reviewer walks through their step table once, and the date is logged
• Multi-entity consistency: one SOP with an entity schedule, not one per subsidiary
• Records retention: books of account are preserved for at least eight financial years (Section 128(5), Companies Act 2013), so the clause names the period and location

Track four metrics each cycle, so improvement is measured and not assumed:

• Close to pack time: working days from period end to the approved MIS pack
• Post-close adjustments: number and value of entries booked after the ledger was locked
• Evidence completeness: share of controls with evidence on file for the period If the books are far behind, fix that first, because an SOP written over unreliable records documents the wrong process; our guide on books reconstruction before statutory audit covers that route.

Maintenance triggers go into clause 10 so the review is not left to memory:

• Software or funding change: a new accounting system, ERP or MIS tool, or new information rights in a shareholders’ agreement
• Statute or circular: any change that moves a date or a section reference, including enactment of the Corporate Laws (Amendment) Bill 2026
• Accounting standard amendments: the Companies (Accounting Standards) Amendment Rules 2026 (G.S.R. 169(E), AS 22 and Pillar Two taxes) and the Companies (Indian Accounting Standards) Amendment Rules 2026 (G.S.R. 725(E) dated 12/08/2026, effective from 01/04/2026) feed the FY 2026-27 disclosure checklist
• Audit findings: deficiencies in the auditor’s report or management letter, read alongside the CARO 2020 reporting framework

Keep internal and statutory audit roles separate; see internal audit versus statutory audit for the split.

Common mistakes that cost founders time and money

Five drafting mistakes account for most SOPs that fail an audit walkthrough, and each is cheap to avoid at drafting stage.

Mistake 1: writing from the rule book instead of the practice

A copied template describes steps nobody performs, and a procedure that is not followed is direct evidence that controls do not operate (Section 143(3)(i)). Observe one full cycle, then write what happens.

Mistake 2: hard-coding statutory dates

Teams type 30/10 for AOC-4 and 29/11 for MGT-7 because that was last year’s date, but both move with the actual AGM (Sections 137(1) and 92(4)). A wrong date risks the ₹100 per day additional fee and the loss of the internal financial controls exemption. Write the formula and add a buffer.

Mistake 3: naming people instead of roles

The SOP says “Anita reviews the bank reconciliation”, and Anita resigns. Name roles and a backup, and grant access before the absence.

Mistake 4: review controls with no threshold and no evidence

“Finance head reviews MIS” cannot be tested. State what is checked, the threshold that triggers investigation and the record that proves it happened.

Mistake 5: leaving the audit trail out of the SOP

Teams assume the accounting vendor handles the edit log, but the company is the party bound by the proviso to Rule 3(1), and the auditor reports on it under Rule 11(g). Add a monthly attestation and a backup location check, including where the ERP is hosted outside India.

FAQs on Financial Reporting SOP Drafting

Q: Is a financial reporting SOP mandatory under the Companies Act 2013?
A: No statute requires a document called an SOP. The obligations that make one necessary are indirect: the proviso to Rule 3(1) of the Companies (Accounts) Rules 2014 on audit trail, the auditor’s report on internal financial controls under Section 143(3)(i) where it applies, and, for listed companies, the board’s controls statement under Section 134(5)(e). A written SOP is the cheapest way to show what the controls are meant to be.

Q: What is a risk control matrix, and does the SOP need one?
A: A risk control matrix ties each financial reporting risk to the assertion it threatens, the control, its type and frequency, the owner and the evidence. The review control table is the reporting slice of it. A full matrix is expected where Section 143(3)(i) reporting applies, and investors ask for one anyway.

Q: Which tax filings belong in the reporting calendar?
A: Include the tax audit report, the income tax return and the TDS returns, each with its governing section. For FY 2025-26 the tax audit report falls under Section 44AB of the Income-tax Act 1961; from tax year 2026-27 it is filed in Form 26 under Section 63 of the Income-tax Act 2025, due one month before the Section 263(1) return date (Income Tax Department, Form 26 FAQs, 2026). Keep a dated rule log, because circulars move dates, as CBDT Circular 07/2026 did, and add the server and backup details Form 26 asks the tax auditor to report.

Q: How much does financial reporting SOP drafting cost?
A: There is no standard fee, because cost follows scope: the number of entities, reporting outputs and systems, and whether a test cycle with the statutory auditor is included. [Confirm Treelife fee approach before publishing.]

Q: How long does it take to draft and test the SOP?
A: Plan for four to six weeks to draft for a single entity, plus one full reporting cycle to test [Treelife estimate, confirm with the VCFO team]. The test cycle takes longest because it runs on your actual calendar, and if the books are behind, fix the backlog first.

Q: What documents do we need before drafting starts?
A: Collect the last audited financial statements with the auditor’s report and annexures, the chart of accounts, the close checklist, the approval matrix, the MIS and board pack formats, the shareholders’ agreement information rights and the systems list with user access. The CARO annexure and any management letter point to controls the auditor already considers weak.

Q: Does the SOP need to cover FEMA reporting and foreign parent group reporting?
A: Yes, where the company has foreign investment or a foreign parent, because group and Indian statutory deadlines run on different clocks. The annual FLA return under the Foreign Exchange Management Act 1999 is filed on the RBI’s FLAIR portal by 15 July, provisionally if the audit is pending and revised on audited figures by 30 September (RBI FAQs updated 01/07/2026); RBI has extended the date in some years, so check the portal notice. If the group ERP sits outside India, books must stay accessible in India with a daily backup on servers in India (Rule 3(1) and Rule 3(5), Companies (Accounts) Rules 2014).

Q: Who signs the financial statements when there are several founder-directors?
A: The board approves the statements and authorises signatories by resolution, so the SOP names signing roles, not individuals. Section 134(1) requires signature by the chairperson if authorised, or by two directors including the managing director and CEO where appointed, with the CFO and company secretary where appointed. Record the authorised pair, the backup pair and who holds each digital signature token.

Q: Do DPIIT-recognised startups get any reporting relief?
A: DPIIT recognition does not change the Companies Act reporting calendar. It adds evidence: where a tax benefit such as Section 80-IAC of the Income-tax Act 1961 is claimed, the SOP keeps the eligibility file with the tax inputs [map to the Income-tax Act 2025 equivalent]. Check the current DPIIT notification before relying on any exemption.

Q: What happens if an investor’s diligence finds the SOP is not followed?
A: A written SOP that is not followed is worse than none, because it documents the gap. Expect diligence requests for specific evidence, such as the last three bank reconciliations and their sign-offs, and a remediation covenant or closing condition where evidence is missing. Test the SOP on a closed cycle before the data room opens.

Q: How does the SOP handle ESOP accounting and directors outside India?
A: Treat both as named steps. The ESOP expense is booked from the grant and vesting schedule under the applicable standard, and the SOP shows who recalculates it each quarter and who reviews it; see our guide on ESOP expense under Ind AS 102. For directors abroad, record digital signature token custody and the process for remote board approval.

Q: Can a virtual CFO prepare the SOP while the company stays accountable?
A: Yes, and the SOP should say so. Treelife’s virtual CFO service can prepare the draft, the reconciliations or the reporting pack, and our note on what a virtual CFO does week to week shows where that fits. The reviewer and approver roles stay with the finance head and board, because responsibility for approving and signing the statements rests with the board under Section 134(1).

Where to start this month

Start financial reporting SOP drafting with the calendar, because it forces the ownership and control questions in the right order. This week, write the statutory anchors as formulas, add a target date and an owner to every line, and list the evidence each review leaves behind. Then draft the step tables, test them on the last closed cycle and version the result.

---

Regulatory references

• Companies Act 2013: Sections 2(85), 92(4), 96(1), 101(1), 128(5), 129(1), 129(3), 133, 134(1), 134(3)(q), 134(5)(e), 137(1), 143(3)(i), 143(3)(j), 403, and Schedule III
• Companies (Accounts) Rules 2014: Rule 3(1) and its proviso (G.S.R. 205(E) dated 24/03/2021; deferred by G.S.R. 235(E) dated 31/03/2022), Rule 3(5) (G.S.R. 624(E) dated 05/08/2022), Rule 8(5)(viii)
• Companies (Audit and Auditors) Rules 2014: Rule 11(g) (G.S.R. 206(E) dated 24/03/2021)
• Companies (Indian Accounting Standards) Rules 2015: Rule 4
• MCA notification G.S.R. 583(E) dated 13/06/2017, corrected by S.O. 2218(E) dated 13/07/2017, and MCA General Circular 8/2017 dated 25/07/2017 (internal financial controls reporting exemption for certain private companies)
• Companies (Registration Offices and Fees) Rules 2014: Rule 12; first proviso to Section 403 (additional fee)
• MCA General Circular No. 05/2026 dated 24/10/2026 (fee relaxation for FY 2025-26 AOC-4 and MGT-7 filings)
• Companies (Accounting Standards) Amendment Rules 2026 (G.S.R. 169(E)); Companies (Indian Accounting Standards) Amendment Rules 2026 (G.S.R. 725(E) dated 12/08/2026)