Close cycle discipline
Reconciliation and month-end close, without the scramble
The close is where every small process problem shows up at once. This page covers bank reconciliation automation, transaction matching, review workflows, and a checklist with names attached.
Where the days go
Why the close takes longer than it should
Ask a controller where the close time goes and the answer is rarely the actual accounting. It is waiting: waiting for a receipt, waiting for an approval, waiting for someone to explain a transaction from three weeks ago. Each wait is short, but they stack.
The fix is not a faster ledger. It is removing the waits. Continuous reconciliation means exceptions surface weekly instead of monthly, so the questions get asked while the answers are still fresh. A close checklist with due dates and owners turns a memory exercise into a schedule, and a schedule can be improved.
Three waits show up on almost every team's list. The first is an unreconciled bank account, where the balance is right but nobody can name the individual items behind it. The second is a missing receipt attached to an expense that cleared the card weeks ago. The third is a vendor invoice that arrived near the end of the month and never got coded before the cutoff. None of these are accounting failures. They are timing failures, and timing is the one thing a checklist can actually control.
Two cadences
Continuous versus batch reconciliation
Batch reconciliation matches once a month
A transaction from the 3rd has had four weeks to become a mystery. The person who made the purchase has moved on, and the receipt is somewhere in an inbox thread nobody wants to reopen.
Weekly reconciliation catches the same item early
The unmatched line surfaces while the context is recent. The question gets answered in a two-line reply instead of a fifteen-minute investigation.
The accounting result is identical
What changes is the cost of resolving exceptions, which falls when the context is fresh. Teams that move to weekly reconciliation often find the close shortens by several days within a quarter, mostly because the exception pile at month-end shrinks.
The switch is a cadence decision, not a tool purchase
You can run weekly reconciliation in the ledger you already own. Software helps at volume, but the first improvement comes from putting the same task on the calendar four times a month instead of once.
What the matching engine can and cannot do
Matching engines compare bank feed lines to ledger entries using amount, date, and reference. Exact matches are straightforward. The hard cases are timing differences, partial payments, and batched deposits where one bank line covers several ledger entries. The engine's job is to propose matches and flag what it cannot resolve. Your job is to review the proposals and investigate the leftovers.
Transaction matching
How the engine earns its keep
Rules handle most of the awkward cases. If a bank line equals the sum of three specific ledger entries, the rule matches them. If a check clears two days after month-end, a timing rule holds it in the right period. If a customer pays part of an invoice, a partial-payment rule ties the deposit to the open balance. What remains is genuinely worth a human look.
- Amount, date, and reference compared together, not one at a time
- Batched deposits split across the entries they cover
- Proposals you accept or reject, with the reason kept on the record
Bank feeds
What to do when a feed breaks
Bank feeds fail. Credentials expire, banks change their authentication, and connections drop. When a feed breaks, transactions stop appearing, and if nobody notices, reconciliation runs on incomplete data. Check the feed at the start of each cycle and compare the last transaction date against the bank statement.
- Some tools alert on stale feeds; if yours does not, add it to the checklist
- Importing a statement file works as a fallback, though it adds manual work
- Log the outage and the fix so the next occurrence takes minutes, not an afternoon
Credit cards, loans, and non-bank accounts
Bank reconciliation is the visible part, but the same logic applies to credit cards, lines of credit, and loan accounts. Card reconciliation is often messier because transactions include tips, foreign currency, and refunds. Loans need interest and principal split, which usually requires a schedule rather than a matching rule. Handling these accounts on the same weekly cadence as the bank account keeps the month-end workload even, and it makes the interest and fee entries easier to verify because you are looking at one period at a time.
Build the schedule
The close checklist
A close checklist lists every task, the owner, and the due date. Review it after each close and remove steps that no longer matter. Checklists grow over time, and a list with forty items where ten are obsolete is a list people stop reading.
Before the period ends
- Confirm every bank and card feed has transactions through the last business day
- Chase open receipts and missing approvals while the request is still fresh
- Review open purchase orders and recurring vendor commitments for accruals
During the close
- Complete each account reconciliation and clear the flagged exceptions
- Post accruals, depreciation, and the standard journal entries
- Handle intercompany items if you have them, before the review opens
Review and sign-off
- Assign each account or schedule to a named reviewer
- Check unusual balances, unexplained variances, and entries without support
- Record the sign-off so the audit trail shows who checked what
After the books close
- Summarize what changed and why for owners and department heads
- Note timing differences separately from real changes in spending
- Prune the checklist and carry the exceptions into next week's cycle
Review workflows
If the review is just a signature, it is not a review.
A structured review workflow assigns each account or schedule to a reviewer, tracks whether it has been checked, and records the sign-off. That matters for audits, but it matters more for catching mistakes before they compound. Give reviewers a specific list of what to check and how much variance is worth investigating.
Cut-off
Accruals and cut-off
Cut-off is the hardest part of the close. An invoice for December services that arrives in January belongs in December, and catching that requires either an accrual process or a vendor who bills promptly.
A practical approach is to review open purchase orders and recurring vendor commitments at period end, then accrue anything that clearly belongs to the closing period. Automation helps by flagging invoices received after period end with a service date inside the period. Without that flag, cut-off depends on someone recognizing the invoice, which is unreliable at volume.
Reporting the close
Say what moved and why
The close produces numbers that people outside finance need. A short summary of what changed and why is more useful than a data dump, especially for owners and department heads who want to understand variances without reading a full trial balance. Include the accounts that moved materially and the reason. If a variance is a timing difference, say so. If it is a real change in spending, that is worth a conversation. Reporting the close well builds trust in the numbers, which makes the next close easier because people respond to questions faster.
Accruing at period end keeps a December invoice in December, even when the paperwork lands in January.
Choosing a stack
Tools that support the close
Close management sits alongside reconciliation in most accounting stacks. The choice depends on how much of the process you want in one system. Whatever you use, the underlying discipline is the same: reconcile continuously, review deliberately, and keep the checklist honest.
Ledger and bank feeds
Xero and QuickBooks Online
Both handle the ledger and the bank feed, with reconciliation built in. They are where most US small and mid-sized businesses already close their books, which makes them the natural starting point before adding another tool to the stack.
Read the accounting integration guideLayered on top
Automation for matching and review
Automation tools layered on top add matching rules, review workflows, and checklist tracking. They are worth a look once exception volume outgrows what a spreadsheet and a weekly calendar can hold.
Larger organizations
NetSuite
Covers the close as part of an ERP, including multi-entity consolidation.
Questions that come up before the first weekly cycle
How often should a small business reconcile the bank account? +
Weekly is the cadence most teams settle on. It is frequent enough that a transaction from the 3rd is still recognizable when it surfaces, and light enough that it does not become its own project. Monthly reconciliation is not wrong, but it concentrates all the exception work into the busiest week of the month.
What belongs on a month-end close checklist? +
Reconciliations, accruals, journal entries, intercompany items if you have them, and the review steps. Each line carries an owner and a due date. The value is not the document itself, it is that nothing depends on someone remembering. Review the list after each close and cut what no longer applies.
Do I need new software to reconcile continuously? +
No. Weekly reconciliation runs in the ledger you already own. Matching rules, stale-feed alerts, and review tracking make it easier at volume, but the first improvement comes from putting the same task on the calendar four times a month instead of once.
What does a reviewer actually check? +
Unusual balances, unexplained variances, and entries that do not match the supporting documentation. Set the threshold in advance so the reviewer knows how much variance is worth investigating and how much is normal noise. A review without a specific list tends to become a signature.
How do I handle an invoice that arrives after month-end? +
If the service date falls inside the closing period, accrue it. Review open purchase orders and recurring vendor commitments at period end so the obvious ones are caught before the books close. Automation that flags late invoices with an in-period service date makes this reliable rather than dependent on memory.
Next step
Bring your close cycle down
Tell us what your close looks like today — how many accounts you reconcile, where the exceptions pile up, and who signs off. We will walk through where a weekly cadence and a named-owner checklist would change the schedule. Reach us at [email protected] or +1-408-555-9539, Monday to Friday, 9:00 AM to 6:00 PM.