Finance Team Month-End Handbook
The prompt
Write a month-end close handbook.
Business type: {{describe}}
Accounting software: {{quickbooks_xero_netsuite_sage}}
Team size: {{people_handling_accounting}}
Pain points in close: {{what_takes_longest_or_breaks}}
Current close timeline: {{how_many_days}}
Handbook including:
1. Day-by-day close calendar with tasks, owners, dependencies
2. Checklist per team role
3. Journal entries posted every month
4. Reconciliations required and how to perform each
5. Review and approval steps before closing books
6. Common errors and how to catch them
7. What to do if something is wrong on the last day Why this works
The day-by-day close calendar with dependencies is the most valuable section of a close handbook because it makes sequencing explicit — knowing that bank reconciliations must be done before the trial balance review is reviewed prevents the experienced team member from doing things out of order and the new hire from not knowing the order at all. Journal entry templates reduce both time and error compared to creating entries from scratch each month. The error escalation path prevents small issues from becoming large problems through inaction.
Risks & review
Close handbooks go stale quickly when processes or systems change — a handbook that doesn't match the current close process creates more confusion than having no handbook. Establish a quarterly review process to update the handbook for any process changes. Also ensure the handbook is tested with someone who wasn't involved in writing it: documentation that makes sense to the author often has critical gaps that only become visible when a new team member tries to follow it.