Step 01
Checklist auto-generated per entity
Pre-built checklist (bank recon, accruals, intercompany, FX revaluation, GSTR-2B, TDS, fixed asset run, depreciation, period-end provisions) is generated per entity at month-end.
Accounting Software | Period Close Checklist
Close on a checklist. Sign-off captured per task. 5 days, repeatable.
Pre-built checklist of close tasks (bank recon, accruals, FX, intercompany, GSTR-2B match, TDS posting). Owner per task. Evidence attached. Sign-off captured. Period locks when the checklist is green.
How most teams close today
Close week: the same scramble, every month.
Day 1 of the new month. The CFO's question: 'Are we done?' The answer is always 'almost'. The tasks are real, but the orchestration is a WhatsApp group:
- Bank reconciliations chased across three banks and four entities by email.
- Accruals computed in Excel, posted manually, half forgotten by the next month.
- Intercompany positions sent back and forth with the sister entity's controller; mismatches discovered at consolidation.
- GSTR-2B and TDS sign-off chased separately from the books close, often into week 2.
The close finishes on day 8 or 10. The CFO commits to "5 days next month". The pattern repeats.
How it works
From day-1 trigger to period-locked, on a checklist.
Step 02
Tasks assigned to owners
Each task has an owner (controller, AP lead, AR lead, CA reviewer). Reminders fire on Slack and email if a task is past its SLA.
Step 03
Evidence attached per task
Bank statement, intercompany confirmation, FX rate file, supporting workpaper. All attached to the task. Auditor sees the evidence with the task.
Step 04
Sign-off captures the close
Each task is signed off by its owner; the period locks when all tasks are signed. CFO and CA reviewer get a single dashboard view of close progress.
Step 05
Reopen with reason
Where a reopen is needed (a late vendor invoice, a JE correction), authorised users post with reason and approver. The audit trail captures the cycle.
What the system does
Capability, input, output.
| Capability | Input | Output |
|---|---|---|
| Checklist generation | Period-end + entity master | Pre-built checklist with owners |
| Owner assignment | Role mapping per task | Task assigned with SLA |
| Evidence attachment | Workpaper, statement, screenshot | Per-task evidence pack |
| Sign-off capture | Owner action + DSC where required | Hash-verified sign-off per task |
| Cycle-time analytics | Task completion timestamps | Close-cycle dashboard |
| Reopen workflow | Authorised user + reason | Period reopened with audit trail |
-
Checklist generation
- Input
- Period-end + entity master
- Output
- Pre-built checklist with owners
-
Owner assignment
- Input
- Role mapping per task
- Output
- Task assigned with SLA
-
Evidence attachment
- Input
- Workpaper, statement, screenshot
- Output
- Per-task evidence pack
-
Sign-off capture
- Input
- Owner action + DSC where required
- Output
- Hash-verified sign-off per task
-
Cycle-time analytics
- Input
- Task completion timestamps
- Output
- Close-cycle dashboard
-
Reopen workflow
- Input
- Authorised user + reason
- Output
- Period reopened with audit trail
Compliance + integrations
Audit-ready by design.
The close itself is an audit pack. Tasks, owners, evidence and sign-off all hash-verified. The CA reviewer signs off per task; the auditor reads the chain at FY-end.
Regulations we work within
-
Rule 11(g), Companies Act
Edit trail across the close cycle.
-
Section 134(5), Companies Act
Internal financial controls supported with task evidence.
-
SA 230 (audit documentation)
Audit pack export aligned with SA 230 documentation requirement.
Connects to
- Slack Task notifications + reminders
- Microsoft Teams Task cards + reminders
- Email Task notifications
Period Close Checklist FAQ
What buyers ask.
Who owns the checklist?
The Controller owns the checklist by default. Tasks are delegated to AP lead, AR lead, treasury and CA reviewer based on role. The CFO sees the close progress on a single dashboard. Ownership is configurable per organisation.
How does multi-entity close work?
Each entity has its own checklist, with cross-entity tasks (intercompany matching, group consolidation) shared. The group close runs on the same dashboard with a roll-up of entity sign-offs.
Can we customise the checklist?
Yes. Default tasks ship with the product (mapped to standard Indian close practice). Add, remove and customise per entity. Save as a template for the next month.
What if the period needs to be reopened after lock?
Authorised users can reopen with reason and approver. The reopen is captured as a tracked event in the audit trail. Once changes are posted, the period re-locks with a new sign-off.
More in Accounting Software
Related features
Financial Statements
P&L, balance sheet, cash flow generated from the ledger. Schedule III layouts. Drill from line to source.
See Financial StatementsAudit Trail & Evidence
Every change hash-chained, append-only. Auditor-ready evidence pack export. Big-4 accepted.
See Audit Trail & EvidenceMulti-Entity Consolidation
Currency translation, intercompany elimination, minority interest. One-click consolidated view.
See Multi-Entity Consolidation
Bring your last close. We map it to a checklist on screen.
Walk through your last month-end with a finance specialist. The system maps your tasks, owners and evidence to a checklist live. The next close runs on it.