Quarterly Close & Audit Committee Pack

Quarterly Close & Audit Committee Pack | Finin2min CFO Hub: Finin2min practical finance and law reference.

CFO Office Hub

Quarterly Close & Audit Committee Pack

Practical CFO playbook for finance leaders, founders and controllers. Built for operating discipline, decision quality and audit-ready documentation.

What this module solves

It builds the quarterly close and Audit Committee pack around what the Committee actually needs to discharge its statutory oversight role, not a longer version of the same monthly close deck.

Operating framework

Area	What good looks like	Common failure	Finin2min action
Ownership	Named owner, due date and review layer	Shared responsibility with no accountability	Create RACI and maker-checker tracker
Data	Single source of truth reconciled to books/banks	Different numbers in MIS, ERP and board deck	Reconcile every key metric before reporting
Controls	Preventive and detective controls documented	Ad hoc approvals and spreadsheet errors	Use control matrix and exception log
Decision support	Clear recommendation with risk and upside	Only historical reporting	Add CFO commentary and next action

Practical examples

Example 1

An Audit Committee pack that repeats the monthly close deck's operating metrics wastes the Committee's actual oversight time. The pack should instead foreground judgement areas, estimates, provisions, related-party transactions, and any control exceptions from the quarter, which is what the Committee exists to scrutinise.

Example 2

A quarterly close pack missing a clear related-party-transaction schedule forces the Committee to ask for one live in the meeting, exactly the kind of gap that should never surface for the first time in the room.

What the Audit Committee pack should actually contain

Under Section 177 of the Companies Act, 2013 and, for listed companies, SEBI's LODR Regulation 18, the Audit Committee has the power to investigate any matter within its remit, call for information from any employee, and take outside professional advice. A pack built to support that role should include: the quarter's judgement areas (provisions, estimates, impairment triggers) with the reasoning behind each, a complete related-party-transaction schedule showing which items already have Committee approval and under what mechanism, any control exceptions or reconciliation breaks from the quarter, and the status of matters raised at the previous meeting. A pack that omits any of these forces the Committee to discover the gap live in the meeting, which is a worse outcome for everyone than surfacing it in the papers beforehand.

Checklist

Define owner and reviewer.
Document source systems.
Reconcile to ledger/bank/returns where relevant.
Capture exceptions, judgement areas and open risks.
End every report with decision or action required.

Q&A

Question	Finin2min answer
Who should own this?	The CFO office should own the framework; process owners own inputs and finance controls the review.
What is the biggest red flag?	Different versions of the same number across MIS, books, bank, tax filings or board material.
How frequently should it be reviewed?	Monthly for operating items, quarterly for board-level governance, annually for design refresh.

Finin2min crux

Crux: A quarterly close pack should let the Audit Committee do its actual job — question judgement areas and control gaps — rather than re-present the same operating metrics already covered in the monthly close.