Two halves. Recording: entering and coding bills, invoices, receipts and bank transactions, largely assisted by bank feeds, bank rules and repeating transactions. Proving: agreeing bank and card balances to statements, reconciling supplier statements, applying receipts correctly, posting accruals, prepayments and depreciation, tying subledgers to the general ledger, reviewing the balance sheet, and locking the period. Xero automates most of the recording. The proving is human work, and it's the half most commonly skipped.

It depends far more on how the work is distributed than on business size. A business handling transactions weekly and closing in the first week of the following month spends less total time than one attempting everything at month end, because deferred work requires reconstructing context that was free at the time. As a rough shape, a small business with clean processes might spend a few hours a week plus half a day closing; the same business working only at month end often spends two full days and produces a less reliable result.

Bookkeeping is recording and proving transactions — coding, reconciliation, keeping subledgers accurate. Month-end close is what turns a recorded month into a reportable one: posting accruals and prepayments so costs land in the right period, depreciation, tying subledgers to control accounts, reviewing variances against prior month and budget, and locking the period. In small businesses the same person often does both, which is why the terms blur, but they're distinct activities and close is the one more often skipped.

A lock date prevents changes to transactions dated before it. You should use one. Without it, a closed month remains editable indefinitely, so a report you ran and shared in January can silently differ from the same report run today — usually because someone tidied an old transaction while working on a later period. Once a month is reviewed and reported, lock it. If a correction is genuinely needed afterwards, unlock deliberately, make it with a note, and re-lock. The aim is to make changes visible and intentional rather than to prevent them.

Useful, but not to be trusted indefinitely. Bank rules automatically code transactions matching conditions you set, which works well for genuinely predictable items like a fixed monthly subscription. The risk is that a broadly written rule keeps firing after circumstances change, coding transactions consistently and consistently wrong — and because the automation worked, nothing flags it. Write rules narrowly, and review what they've been capturing periodically rather than assuming they're still correct.

At minimum: clear the reconcile queue for every account; agree each bank balance to its statement; reconcile credit cards to the statement period; enter all bills received whether or not they're due; reconcile supplier statements; apply all customer receipts to the correct invoices; review aged payables and receivables; post accruals, prepayments and depreciation; clear the suspense account to zero; tie subledgers to the general ledger; review the balance sheet line by line; compare the profit and loss to prior month and budget; and set the lock date. Inventory, multi-currency revaluation and payroll reconciliation apply where relevant.

Usually because costs are being recorded when paid rather than when incurred. An annual insurance premium paid in March hits March entirely, making that month look bad and every other month look better than it was. The fix is accruals and prepayments: spread costs across the periods they relate to, and accrue for work received but not yet billed. Miscoded transfers between your own accounts and inventory recorded without matching cost of goods sold to revenue produce the same effect.

Xero reduces the mechanical work substantially — feeds, rules and connected apps handle much of the recording. What it doesn't do is judgment: whether a transaction is correctly classified, whether an accrual is needed, whether a balance sheet figure is explainable, whether the period should be locked. Plenty of small businesses run their own books in Xero successfully, and if you have the discipline for a monthly routine you may not need help. The businesses that struggle are usually not short of software but short of the recurring hour that nobody's job description contains.

Test it against questions rather than appearance. Can you produce last month's profit and loss within a week of month end? Does every bank and card account agree to a statement, and do you know when each was last agreed? Can you explain every balance sheet balance? Is the suspense account zero? Do aged payables and receivables tie to their control accounts? Are prior periods locked, and do reports run today match what they showed when the period closed? A tidy-looking file that fails these is common — the recording is happening and the proving isn't.

Establishing a monthly rhythm on top of an unreliable opening position mostly documents the problem more regularly. The sequence is to catch up and clean up first — find the last date your records genuinely agreed to external sources, work forward from there, resolve what's resolvable and write off the rest with documented reasoning — and only then start the monthly cycle. Businesses are commonly further behind than they think, since a file that looks maintained can still have diverged from the bank a year earlier.