The short answer: A continuous close moves reconciliation and coding into the month, so only 18 of roughly 90 close hours remain after month-end in the worked example below. That shift takes a single-accountant close from about 15 business days to 5.
- Transactions are coded daily, bank and card accounts reconcile weekly, and a controller reviews exceptions every week.
- Total effort barely changes: 88 hours in a batch close versus 90 hours spread across the month.
- Month-end still exists. It shrinks to cutoff, accrual true-ups, review, and the packet.
- QuickBooks Online, Xero, or NetSuite can all carry the method; cadence and ownership matter more than the ledger.
Last updated October 2026.
A continuous close is the practice of doing close work as transactions happen instead of after the month ends. Coding happens daily, reconciliations weekly, and review in small weekly batches. By the last business day, most of the ledger is already tied out.
This guide defines the method, explains why a batch close runs past two weeks, and maps each task to a cadence. It then works through the hours for one illustrative company. The figures describe a hypothetical $22M B2B services firm as of October 2026.
What is a continuous close?
A continuous close spreads the month-end workload across the month on fixed cadences. The goal is a ledger that is substantially reconciled before the period ends, so the formal close becomes a short confirmation step.
Debit & Co. runs this approach as the Continuous Close Method™. Its three rhythms are simple to state:
- Daily: bank and card lines are coded, and vendor bills are entered the day they arrive.
- Weekly: bank, card, and clearing accounts reconcile, and a controller clears the exception list.
- Monthly, during the month: recurring journal entries, prepaid amortization, and payroll accruals are drafted before the period ends.
The method overview describes how those rhythms fit into an engagement. This article focuses on the mechanics any finance team can copy.
Why does a manual month-end close take two-plus weeks?
A batch close starts every task on the same day, after the month ends, and most of those tasks depend on each other. One accountant then works through the whole queue in sequence.
Take the illustrative company. It posts 1,240 bank and card lines a month across 5 accounts, plus 85 vendor bills and 140 customer invoices. One staff accountant has about 6 productive hours a day for close work.
In a batch close, all 88 hours of close work begin on business day 1. Dividing 88 hours by 6 hours a day gives 14.7 business days, or roughly three calendar weeks. Reviews then add another round of questions, because nobody looked at the ledger during the month.
The delay comes from queueing, not from slow staff. Coding 1,240 lines cold also takes longer, since each unfamiliar charge needs research weeks after it posted.
How does a continuous close differ from a traditional batch close?
The difference is timing. Both approaches perform the same tasks; a continuous close runs most of them before month-end instead of after.
| Close task | Batch: hours after month-end | Continuous: hours during month | Continuous: hours after month-end |
|---|---|---|---|
| Code 1,240 bank and card lines | 41 | 39 | 2 |
| Reconcile 5 bank and card accounts | 15 | 12 | 3 |
| Tie out AP and AR subledgers | 12 | 9 | 3 |
| Accruals, prepaids, deferred revenue | 10 | 6 | 4 |
| Review, flux analysis, close packet | 10 | 6 | 6 |
| Total | 88 | 72 | 18 |
The worked arithmetic shows the trade. The continuous version totals 72 plus 18, or 90 hours, against 88 for the batch. Two extra hours pay for weekly reviews. After month-end, though, the remaining work falls from 88 hours to 18, and 18 divided by 6 is 3.0 business days.
What does that look like on the close calendar?
With 3.0 days of tie-out left, the books close on business day 5. Day 4 goes to controller review, and day 5 to the packet.
The daily load during the month stays modest. Coding 39 hours across 21 business days works out to about 1.9 hours a day, or roughly 59 lines. That fits inside a normal week without overtime.
For the sequence of gates inside those five days, the 5-day close calendar lays out each day. To see where a given company sits today, compare it against the close benchmarks by company size.
Which close tasks move to daily and weekly cadences?
Move any task whose inputs arrive during the month. Keep at month-end only the tasks that need the final balance or the cutoff date.
- Daily: transaction coding, bill entry into Bill.com or the ledger, and deposit matching against open invoices.
- Weekly: bank and card reconciliations, clearing-account sweeps, AR aging review, and the controller’s exception list.
- Mid-month: drafting recurring entries, rolling prepaid and fixed-asset schedules, and updating deferred revenue under ASC 606.
- Month-end only: cutoff, final accruals, intercompany and payroll true-ups, flux review, and sign-off.
Weekly reconciliation is the anchor. It caps any unexplained item at seven days old, which keeps research short. The trade-offs of each cadence are covered in how often to reconcile accounts.
Does closing faster sacrifice accuracy?
No, provided review moves forward with the work. Accuracy depends on who checks the ledger and how often, while speed depends on when the work starts.
Public-company rules show that speed and rigor are separate settings. The SEC’s Form 10-Q instructions set two quarterly filing windows. The largest filers have “40 days after the end of the fiscal quarter for large accelerated filers and accelerated filers.” Every other registrant has “45 days after the end of the fiscal quarter for all other registrants.” Those windows cover auditor review and disclosure drafting, which a private monthly close does not need.
A continuous close adds checkpoints instead of removing them. In the example, four weekly reviews catch miscoded lines while the context is fresh. Aaron Ressel reviews every close packet before it ships, so the final sign-off is unchanged.
What tooling does a continuous close require?
It requires a cloud ledger with bank feeds, a bill-pay tool, and written schedules. It does not require an enterprise system.
- A general ledger with live bank feeds: QuickBooks Online, Xero, or NetSuite.
- A payables tool such as Bill.com, so bills enter the ledger on arrival.
- Prepaid, accrual, and deferred revenue schedules kept current each month.
- A shared close checklist with an owner and a due cadence on every line.
Software improves the data; a team still runs the close. Puzzle, a platform Debit & Co. partners with, delivers categorized transactions quickly, and a controller turns that feed into reviewed books. Bank-feed setup across ledgers is covered in automating bank reconciliation.
Can you run a continuous close in QuickBooks Online?
Yes. Most single-entity companies can run the full method in QuickBooks Online with Bill.com alongside it.
The ledger matters less than the cadence. A file with connected feeds, a clean chart of accounts, and documented coding rules supports daily work. Companies with several entities usually consolidate outside the ledger, which adds a day to the close calendar.
What has to be true before a continuous close works?
The books must be clean, the work must have an owner, and the procedures must be written down. Without those three, daily coding just moves the backlog forward.
- A reconciled starting point. Prior periods must tie to bank and card statements.
- Named owners. Each daily and weekly task needs one responsible person and one reviewer.
- Documented rules. Coding conventions, accrual logic, and cutoff policy belong in a written Custom Playbook™.
- Timely inputs. Receipts, approvals, and contract changes must reach accounting within days, not at quarter-end.
A company that is months behind should finish a cleanup first. Starting a daily cadence on unreconciled history usually stalls within one cycle.
Frequently asked questions
What is a continuous close?
A continuous close performs coding daily, reconciliations weekly, and review in weekly batches, so most of the ledger is tied out before month-end. In the worked example, only 18 of about 90 close hours remain after the period ends.
Does a continuous close eliminate month-end entirely?
No. Cutoff, final accruals, payroll and intercompany true-ups, flux review, and sign-off still happen after the period ends. They take about 3 business days instead of 15, and the packet ships on day 5.
Can you do a continuous close in QuickBooks Online?
Yes. A single-entity company with connected bank feeds, Bill.com for payables, a clean chart of accounts, and written coding rules can run the method in QuickBooks Online. Multi-entity groups usually consolidate outside the ledger.
Does closing faster sacrifice accuracy?
No, provided review moves forward with the work. Weekly controller reviews catch miscoded lines while context is fresh, and a final sign-off still happens before the close packet ships.
What has to be true operationally before continuous close works?
The books need a reconciled starting point, and every recurring task needs a named owner and reviewer. Coding and accrual rules must be written down, and source documents must reach accounting within days.
Sources: U.S. Securities and Exchange Commission, Form 10-Q General Instructions. Worked example is illustrative.
