A fast close is useful only when the numbers are reconciled, reviewed and connected to operational decisions.
Financial controller
Monthly
Publish a close timetable and data owners.
Bank and gateway statements.
The close should convert transactions into a consistent period view. Bank, payment gateway, customer, vendor, payroll, tax and financing records need cut-off rules so one month is not improved by pushing costs or receipts into another.
Reconciliation is the core. Every bank account, gateway balance, receivable, payable, payroll liability, tax balance and inter-company account should have an owner, source statement and explained difference.
The final output is not merely a profit and loss statement. Founders need cash runway, collections, burn, deferred revenue, working-capital movements, statutory dues, budget variance and decisions required from management.
| Control | What it covers | Operating rule |
|---|---|---|
| Day 0–2 | Collect source statements and lock the transaction period. | Define cut-off and missing-data list. |
| Day 3–5 | Post revenue, payroll, expenses, provisions and taxes. | Use documented accounting policies. |
| Day 5–7 | Reconcile balance-sheet accounts. | Resolve or age every difference. |
| Day 7–10 | Review MIS and board pack. | Separate facts, estimates and decisions. |
Define materiality for the close but do not use it to ignore recurring control failures. A small unreconciled balance repeated every month can reveal a broken process.
Track close quality through completion time, post-close adjustments, unreconciled items and recurring data delays—not through speed alone.
Document the decision, owner, due date and evidence expected. A verbal explanation should be converted into a board note, approved working, contract amendment, portal acknowledgement or reconciliation before the item is treated as closed.
Rules, forms, thresholds and interpretations can change. The operating team should use the latest official source and the actual company facts instead of copying a control from another entity or prior year.
Ask four questions: Is the obligation or accounting treatment applicable? Has the underlying transaction been completely recorded? Does the evidence agree with the books and portal? Has an independent reviewer challenged the exception?
The review should distinguish a timing difference from an error, a judgement from a missing document, and a control failure from a one-time operational delay. Repeated small exceptions deserve root-cause action because they often become material during audit, fundraising, notice or distress.
The operating record should connect the control stages—day 0–2, day 3–5, day 5–7, day 7–10—to the same transaction population. If the source list, accounting ledger, tax return, board record and management dashboard use different populations, the review can appear complete while exceptions remain outside the test.
Management should define an exception threshold, but the threshold must not hide repeated failures. A small error occurring every month can signal weak master data, unclear ownership or a broken interface. The reviewer should record root cause, immediate correction and preventive action separately.
Closure requires evidence. At minimum, the file should show who prepared the work, who reviewed it, which source documents were used, what differences remained and when the next follow-up is due. Screenshots without context or spreadsheets without source references are not a durable control record.
Finance should reconcile the operational schedule to the general ledger and explain every reconciling item by amount, age and owner. Manual journals, overrides and post-close changes deserve heightened review because they can bypass the normal transaction flow.
The board view should separate reported results from estimates and management metrics. When a KPI does not follow the statutory accounting framework, provide a stable definition and a bridge to the closest financial statement line so the measure cannot be changed silently.