Month-end close
A close that follows the same steps every month, finishes in days and locks the period when done.
The problem
Month-end in most growing companies is a scramble: exports from three tools, a reconciliation spreadsheet, journal entries typed from emails and a set of numbers that changes after it has been sent to the owner. The close takes two weeks and nobody fully trusts it.
How it runs in Sundial
1. Sales, purchases, stock movements and payments are already in the books, because every module posts to the same ledger as the work happens. There is nothing to import.
2. Reconcile each bank account with the bank reconciliation tool, matching the statement to payments and receipts already recorded.
3. Post depreciation for the month from the asset register, and enter accruals, prepayments and adjustments as journal entries, which can repeat on a schedule.
4. Review receivables and payables aging, and stock value against the ledger, to catch anything missed.
5. Read the profit and loss, balance sheet and cash flow statement, by company and cost center.
6. Close the accounting period so nobody can post into it by accident. Changes after that need a deliberate reopening by someone with the authority to do it.
What the team sees
The finance team works from one checklist in one system. The owner sees statements that do not move after they are shared. Auditors see a locked period with every entry traceable to its source document.
Sample for Kestrel Workspace: October closed on 4 November, 3 bank accounts reconciled, 11 adjusting entries, period locked.
With AI (coming to Sundial)
Sundial is designed for an agent to prepare the close: find unreconciled lines, list missing supplier invoices and draft the recurring entries, then wait for the accountant to review and post. This is roadmap; the steps above are how it runs today.

