A month-end tick-and-tie checklist (and why the order matters)

"What order do you do this in?" is the right question — the people asking it have already figured out the thing most checklists skip: sequence isn't a preference, it's load-bearing. Reconcile a derived account on top of an unverified one and you don't fix the error, you just move it somewhere harder to find. Here's the order that works, why each step has to come before the next, and a checklist you can print and tick off.

What does "tick and tie" actually mean?

Two small jobs, done to every figure. Tick means mark an item once you've checked it — the literal ✓ next to a line you've proven. Tie means trace that figure to the document that proves it: the bank statement, the aging report, the payout file. A close is just tick-and-tie repeated across every account until nothing is left unproven. That's the same thing as reconciliation, said the way accountants actually say it. The output isn't "the books balance" — it's a trail where every number points at the thing behind it.

Why does the order matter so much?

Because each step assumes the step before it is true. One operator put it exactly right — "I think sequence matters more than almost anything else" — and the most-upvoted reply was a single tactic ("tie out retained earnings first"), not the whole order. That's the gap: people get one good tip and no sequence to hang it on.

The rule underneath all of it: work from your most trustworthy anchor outward. The prior period's close and the bank statement are facts you didn't produce, so they're where certainty starts. Retained earnings and your subledgers are derived from everything below them, so they can only be right once everything below them is. Verify a derived account while its inputs are still unproven and a clean-looking result tells you nothing — you've confirmed an account against numbers you haven't confirmed yet.

The tick-and-tie sequence, in order

Top to bottom. Don't start a step until the one above it ties.

1. Confirm the opening balance. The prior period is closed and reconciled; this period's beginning balances equal last period's ending balances. Set the period cutoff so you know exactly which dates you are closing.
2. Reconcile cash and bank first. Match every bank and credit-card account to its statement until the ending balance ties. Cash errors are the loudest and easiest to spot, so clearing them first removes the most noise.
3. Clear the clearing accounts. Undeposited funds, payments-in-transit, and payout/settlement clearing accounts should net to roughly zero. A leftover balance is an unfinished match, not a rounding quirk.
4. Tie subledgers to the GL. AR aging total equals the AR control account; AP aging equals AP; inventory valuation equals the inventory asset account; payroll liabilities tie to the provider.
5. Reconcile the remaining balance-sheet accounts. Prepaids, accruals, fixed assets and depreciation, loans, and taxes each tie to a schedule or statement.
6. Post adjusting entries last. Accruals and deferrals go in only after the core accounts are stable. An adjustment refines the close; it does not paper over an account you never reconciled.
7. Tie out the financials. Confirm the trial balance has debits equal to credits, that retained earnings rolls forward correctly, and review the P&L for any month-over-month swing you cannot explain.
8. Keep the evidence. Save each reconciliation with its supporting document attached, and give every open item an owner and an expected clear date.

Where does each item tie to?

Reconciling means nothing without naming the second source. Every account ties to something independent — here are the usual pairs and the trap that hides in each.

The receivables and payables rows are where a primary ID earns its keep: an invoice number that drifts between systems is exactly how a duplicate payment slips through, and catching missing or doubled rows is the same set-difference check you'd run on any two lists.

A worked example: the payments-versus-invoices trap

Here's the mistake that sends people to the order-of-operations question in the first place. A self-taught operator described "marking all of my payments as sales" and then realizing the payments didn't tie to the invoices. They shouldn't — a payment settles an invoice, it isn't a second sale. Book it that way and revenue is doubled and AR never clears.

The clean pattern, which is step 2 and 3 of the sequence doing their job: record the invoice, receive the payment against it into a clearing account (undeposited funds), then record the actual deposit out of that clearing account, net of any processor fee booked as an expense. The clearing account is what lets a bundled bank deposit reconcile against several individual invoices — and it's why Shopify or processor payouts are their own reconciliation, keyed on the payout, not the order.

When the checklist stops scaling

A printed checklist is the right tool for a monthly close you do by hand — it's the manual reconciliation method with an order stamped on it. It starts to strain when the same tie-outs run every week, when subledgers like inventory and the GL drift across hundreds of SKUs, or when someone else has to trust the result without redoing it. At that point the sequence still holds — you just want it preserved as a repeatable process rather than re-walked from memory each month. If you reach for help there, keep the AI on the setup and explanation and the arithmetic in code, so the order stays enforced and the numbers stay defensible.

← All writing