Ticket triage: deciding what gets answered first
Triage sorts incoming requests by urgency and owner before anybody starts work. How to set priorities that hold, who should do it, and why first-in-first-out fails.
The month end close is a queue of small tasks with dependencies. Most of the delay is waiting for other people, which means the fix is scheduling rather than accounting.
The month end close is the routine that takes a month's transactions and turns them into figures somebody can rely on: everything recorded, everything reconciled, everything reviewed, and the period locked. In a small company it is usually done by one person, in gaps between other work, and it takes far longer than the work itself justifies.
That gap is worth understanding, because it is not an accounting problem. Almost all of it is waiting — for a supplier invoice that has not arrived, for an expense claim nobody submitted, for an approval, for a bank statement. The close is a dependency chain, and the way to shorten it is to attack the dependencies rather than to work faster at the end.
The balance-sheet review is the step small companies skip and the one that catches real errors. Take each balance in turn and ask what it consists of: this bank balance matches the statement, this receivables figure is these six invoices, this liability is that loan. Anything you cannot explain in a sentence is either a mistake or something you have stopped understanding — and it is much cheaper to find in month three than at year end.
A five-day close is worth having because it means decisions are made on current numbers rather than on six-week-old ones. It is not worth having if it is achieved by skipping the reconciliations and the balance review, which is how closes become fast and wrong at the same time. The order to improve in is: correct first, then explainable, then fast. A company that closes in twelve days with a clean balance-sheet review is in better shape than one that closes in four and discovers problems at year end.
The checklist itself works well on a board in Ettex Board: columns and cards with drag-and-drop for each close task, assignees so every step has an owner, due dates against your target days, checklists inside cards for the per-account reconciliation list, and lists or swimlanes if you close several entities. Every move is logged per card, which gives you the timing data to find the bottleneck. The accounting happens in Ettex Books — chart of accounts, double-entry journals, recurring entries, bank statement import from CSV or OFX with reconciliation, attachments on any entry and P&L, balance sheet and ledger export — while expense claims arrive through Ettex Forms, the reporting pack is written in Ettex Docs and the variance analysis sits in Ettex Sheets.
Plainly: Ettex has no close-management module. There is no close calendar, no task automation, no automatic accrual generation, no flux analysis, no period-lock enforcement workflow and no sign-off trail beyond what you record yourself. The board tracks tasks and Books holds the ledger; the discipline of the checklist is yours. For multi-entity consolidation on a tight timetable, close-management software exists for a reason.
Two things decide whether the close is quick. Lease accounting adds a monthly schedule of right-of-use assets and liabilities that has to be maintained rather than recalculated, and management reporting downstream is only as fast as the slowest reconciliation in the close.
Two things decide how long the close takes. Invoice processing is where the delay usually sits, and lease accounting adds a monthly schedule that has to be maintained rather than recalculated each period.
The routine that finalises a period's accounts: cut-off, completeness of income and costs, reconciliations, payroll, balance-sheet review, variance review, locking the period and issuing the reporting pack.
For a small company, under a week is a reasonable target, but correctness comes first. A fast close achieved by skipping reconciliations is worse than a slower, clean one.
Waiting on other people — late supplier invoices, unsubmitted expense claims, missing approvals. Deadlines and standing accruals remove most of it.
Taking each balance and explaining what it consists of. It is the step most often skipped and the one that catches errors while they are still cheap to fix.
Yes. If transactions can be edited afterwards, reported figures change silently and every downstream number becomes unreliable.
Recurring journals, bank import, categorisation rules and standing accruals. The judgement steps — cut-off, review, explanation — stay human.
The month end close is a dependency chain, not an accounting exercise. Write the checklist, move coding and reconciliation earlier, set a deadline for claims and invoices, review the balance sheet — and lock the period when it is done.
Triage sorts incoming requests by urgency and owner before anybody starts work. How to set priorities that hold, who should do it, and why first-in-first-out fails.
A milestone marks a verifiable completion, not a point in the calendar. How to choose them, how many to have, and why percentage-complete reporting replaced them badly.
The critical path is the sequence that sets the end date. How to find it without software, why most status reports chase the wrong tasks, and what float really means.