The Checklist Nobody Genuinely Follows (Until They Have To)

Most accounting checklists I see are either three pages long or one paragraph. Neither works. The real ones are usually ugly, incomplete, and tied directly to your actual workflow. That matters more than anything else here. I spent about a year trying to enforce a structured monthly close checklist at a mid-size firm before I realized the problem wasn't the format. It was that nobody trusted it anymore. We'd written it once and never touched it again, then wondered why people were closing books from memory and missing things. I ended up abandoning the document and building something else. Not a better one. Just one that actually lived in the workflow. A simple Google Sheet with owner names, dates, status columns, and a hard rule: if a line item didn't have a completion date, the close wasn't closed. No exceptions. That single rule changed everything. People started caring because they could see when they were holding up the next step. It sounds almost stupid how much difference that made. Monthly Close Checklist - Core Sections You need recurring items first. These are the things that show up every single month regardless of what happens. Revenue reconciliation. Accounts receivable aging review. Accounts payable matching. Payroll verification. Accruals entry. Fixed asset depreciation. Bank and credit card reconciliations. Prepaid amortization. Intercompany eliminations if you have them. Tax withholding verification. Generally anything that touches cash should appear here. Cash is where mistakes hide most often. Then you need variable items. These are the things that trigger sporadically and usually get skipped until someone remembers too late. Revenue recognition adjustments for new contracts. Deferred revenue amortization updates. Impairment testing if assets look questionable. Lease accounting updates. Bonus accruals near year end. Inventory write-downs. Customer credit adjustments. Bad debt provisions. These items need their own separate section because people treat them as optional even when they aren't. A missed impairment test in November becomes a restatement in March. I learned that the hard way after we skipped quarterly inventory checks for two cycles during a busy period. Found four SKUs that had been obsolete since summer. Cost us roughly eighteen thousand dollars we should have written off months earlier. Accounting Checklist Best Practices For Setup The best version of this isn't a master document you maintain forever. It's a living template you refresh quarterly. Here's how to actually build it without ending up with something nobody uses. Start by pulling your last twelve months of closing entries. Every adjustment that ever got made during a close belongs in the checklist. If it happened once, it will happen again. The people filing those entries already know the work. Ask them what took extra time or felt unclear. Their answers will point to the gaps in your current process. I keep mine in a shared drive with version control. Each month gets its own folder with the checklist exported as a PDF and the live spreadsheet linked inside. When something breaks during close, I can look back at the previous month's version and see what changed. Last quarter, our AP team stopped matching invoices to POs on custom orders and just started hitting approve. This showed up in the variance report because our checklist had a line item specifically for custom PO matching that nobody had updated. We added a note the same day explaining which transaction types bypass that rule and why. A checklist without annotations is just a list. It doesn't tell you what changed or when. Common Structural Mistakes Number one: making everything equal priority. When every line item is marked urgent, nothing is. I separate my checklists into three tiers. Tier one items block the close entirely. Tier two items need completion but don't stop the close if they're missing by Friday. Tier three items are recommended but purely advisory. This prevents the panic that happens when three different tasks scream for attention simultaneously. Number two: forgetting the documentation requirement. The checklist shouldn't just say "reconcile bank accounts." It should say "reconcile bank accounts and attach the reconciliation PDF to the shared drive folder." The difference matters. Two people on my team would complete reconciliations monthly but never file them. Auditors showed up asking for March statements and both of them couldn't find anything. We lost half a day hunting for documents that existed but weren't filed. The fix was simple. The checklist now requires the attachment link in the same row as the task completion. Nothing counts as done without it. What This Approach Doesn't Handle Well It doesn't help with process errors that originate before the checklist is even used. If the general ledger setup is wrong, no amount of checklist discipline will catch it until it's too late. It also breaks down in small teams where one person wears multiple hats. You can't have healthy internal controls when the same person initiating expenses also approves them and reconciles the accounts. That's a structural issue, not a checklist issue. Sometimes the right answer is hiring help or reassigning responsibilities, not making a more detailed list. For companies with more complexity, especially multi-entity or multi-currency operations, the checklist needs to branch significantly. A single unified document becomes impossible to manage. I'd recommend splitting it by entity or function rather than trying to force everything into one file. The overhead of maintaining a fifty-item checklist for a twenty-person finance team outweighs any benefit. Break it into monthly, quarterly, and annual sections. Each gets its own lifecycle and review schedule. Where to Actually Keep This Thing Spreadsheets are fine for small operations. Sheets, Excel, whatever your team already uses. For anything beyond five people working closely together, you want a project management tool with actual task dependencies. Monday.com, Asana, even Trello work. The tool doesn't matter as much as the requirement that someone owns each line item. An unowned task is a ghost. It exists in the document but never gets completed. I once had a checklist with twelve overdue recurring items across three months because nobody had claimed ownership on any of them. Someone assumed the controller was doing them. The controller assumed someone else was. Everyone was wrong. There's no universal template you can download that will fix your process. What works for a fifteen-person SaaS company doesn't transfer to a manufacturing firm with inventory complications. The closest thing to a downloadable resource is the structure I outlined above. Take the tier system, the ownership requirement, the attachment rule, and the quarterly refresh cycle. Build from there. Fill in the line items from your own closing history. The checklist that saves you the most time is the one you actually wrote yourself based on what you've broken before.