Month-end close checklist software for bookkeeping firms

Tracker or close system

Two kinds of product sell as month-end close software. A task tracker stores a recurring list, assigns each item and records when it is marked done. A close system also keeps the evidence: the reconciliation, the statement it was tied to, the reviewer’s approval and a lock on the period. A tracker stops being enough when a client asks who approved the June accrual and nobody can answer from the system.

Decision rule: if the firm must show that a reviewer signed off each reconciliation, buy a close system with sign-off and locked periods. If the firm only needs a status for each client and task, a tracker is enough.

Task assignment and due dates

Each task row needs four fields at minimum: preparer, reviewer, due date and status. The due date should be an offset from the close date, such as “bank reconciliation due business day 3,” so the schedule moves when the close date moves. A tool that only stores a fixed calendar date makes someone edit every row every month for every client.

Test it. Change the preparer and the reviewer on one task, then check that the activity log shows both changes with a name and a timestamp. If reassigning means editing the task title, reject the tool for any firm with more than one preparer.

Dependencies

A dependency means a task cannot be marked complete until the task before it is done. For most small clients the order is: statements uploaded, bank reconciliation, card and loan reconciliations, accruals and adjustments, profit and loss and balance sheet review, owner report, then the period lock. If the owner report can be marked complete while the bank reconciliation is open, the tool records the order without enforcing it.

The failure to test is a reopened predecessor. Take a reconciliation that is already complete and reopen it. A strong tool flags or reopens every downstream task and shows the chain on the dashboard. A weak one leaves the owner report marked complete while the numbers underneath have changed.

Decision rule: if more than one preparer touches a client, require a tool that enforces at least the first dependency, the bank reconciliation before the owner report. If the firm has one preparer and a fixed order, a flag is enough.

Worked example: a client’s May statement arrives three days late and the bank reconciliation is redone. A tool that flags downstream work shows a warning on the review and report tasks. A tracker with no dependencies still shows the report as complete, and the owner gets numbers that will change.

Document attachments

An attachment belongs on the task row, not in an email thread. The minimum is the statement PDF attached to the bank reconciliation task for the same account and the same period, under a file name the firm can search. A pattern such as “2026-05_Operating-4821_statement.pdf” lets a reviewer find the right file in January without opening the email from May.

Check three things. The file stays attached when the task is reassigned. The reviewer can open it without downloading it. The tool records who uploaded it and when. A shared-drive link is not a substitute, because it breaks when a folder moves.

Review sign-off

A sign-off needs three things: a reviewer who is not the preparer, a named approval with a timestamp, and a way to send a task back with a reason. Reject-with-comment is more useful than a plain status change, because the preparer sees what to fix without a phone call. Usual’s review view covers approve, reject and revise on each item, which is the shape to test against.

Run the self-review test: have one person prepare and approve the same task. If the tool allows it, write a rule that says who reviews whose work.

Decision rule: if the owner or a lender relies on the report, require approval by someone other than the preparer before the period locks. If the firm is one person, the log should still show the review step, so the file records that a review happened.

Ledger integration

Most small clients run QuickBooks Online or Xero. The useful integration reads the trial balance and the transaction list for the closed period. Ask the vendor in writing whether the connection is read-only or writes entries back into the ledger. A write-back integration needs its own review, because a bad sync can post entries into the client’s books.

Test it with one client. Pull the trial balance for the last closed month in the tool and run the trial balance report in QuickBooks Online for the same date. The totals should match to the cent. Decision rule: if they differ by any amount, do not roll out the tool to more clients until the cause is found, whether it is a stale sync or a filtered account.

Comparison pages are a starting list. Numeric’s, for example, describes QuickBooks and Xero sync for its own product, and several other vendors on it name QuickBooks but not Xero. Confirm Xero coverage on a client file.

A 100-point scoring rubric

Score each product from 0 to 5 on six criteria, convert each score to points by dividing by 5 and multiplying by the weight, and add the points to 100. Weights: task assignment and due dates 15, dependencies 20, attachments 15, review sign-off 20, ledger integration 20, open-item reporting and activity log 10. A product that scores 1 or lower on dependencies or sign-off is out for any firm that needs those controls, whatever its total.

Anchors for dependencies: 1 means the tool stores an order. 3 means it blocks a dependent task until its predecessor is complete. 5 means it blocks, flags downstream work when a predecessor reopens, and shows the chain on the dashboard.

Anchors for sign-off: 1 means a status field. 3 means a reviewer field with a timestamp. 5 means a reviewer who cannot be the preparer, a reject with a comment, and a period that locks after approval.

Anchors for ledger integration: 1 means a CSV import. 3 means a live read of the trial balance for QuickBooks Online or Xero. 5 means a live read for the firm’s ledger, a tie-out report at a chosen date, and a written statement on write-back.

A worked example

A firm with 60 monthly clients and 12 recurring tasks per client has 720 task rows a month. Pilot three clients for two closes, one of them the messiest, and score from the pilot rather than the demo. The pilot shows the late statement, the reopened reconciliation and the sign-off nobody did.

Illustrative scores: product A scores 4 on dependencies and 2 on ledger integration. Product B scores 2 on dependencies and 4 on ledger integration. Each earns 16 of 20 points on its strong criterion and 8 of 20 on its weak one, so the totals sit close together.

Failure modes and fixes

A statement lands in the wrong period. Fix: put the statement period in the file name and in the task, and reject any file whose period does not match the task.

A task is marked complete with no attachment. Fix: require an attachment before completion if the tool supports it. If it does not, run a weekly report of completed tasks with no file, and review it before the lock.

The owner report goes out before the period locks. Fix: make the lock a task that depends on the reviewer’s approval, so the report cannot be sent while the period is still open.

Staff reassign tasks without a record. Fix: limit reassignment to the manager role.

Where the close meets year-end 1099s

The monthly close is also where the year-end vendor list starts. For payments made in tax year 2026, the IRS instructions for Forms 1099-MISC and 1099-NEC (12/2026 revision) state a $2,000 minimum threshold for tax years beginning after 2025. The same instructions say recipient statements and the IRS filing are due January 31, but because January 31, 2027 falls on a Sunday, the due date for 2026 payments is Monday, February 1, 2027.

The threshold for payments made in tax year 2025 comes from the earlier instructions, so check those before preparing the 2025 returns. A vendor flag on each payment turns the year-end list into a filter instead of a rebuild.