Your Close Got Faster. Your Controls Didn't.

A controller I work with at a $16M services company moved her close from a monthly batch to a continuous model last quarter. Reconciliations ran every night through an automated platform. The books were effectively closed by the 3rd instead of the 18th. Faster, cleaner, less heroics at month-end. Everyone was happy.

Then a duplicate vendor payment of $41K sat in the ledger for six weeks before anyone noticed. It reconciled cleanly every single night. Both entries matched a real invoice and a real bank debit, so the daily process waved them through. What used to catch a thing like that was a person reviewing the whole month in one sitting and thinking "wait, didn't we already pay this." That sitting no longer happened.

The monthly close was also a control

Nobody designed it that way, but the month-end batch did double duty. It closed the books, and it forced one human moment where someone looked at the full period at once and saw the shape of it. Round numbers that didn't belong. A vendor that got paid twice. A revenue spike with no customer behind it. The batch was slow, and the slowness was where judgment lived.

Continuous close removes the batch. Reconciliation happens incrementally, daily, and each day's entries get matched and cleared before the next day starts. The error gets folded into a clean running state and stops looking like an error. There's no point where anyone steps back, because stepping back was a function of the books being open.

This isn't a fringe setup anymore. Continuous auditing jumped from 18% of organizations in 2024 to 42% in 2026, and close cycles are compressing from ten-to-fifteen days down to three-to-five. The tooling that makes a daily close possible is now sold to mid-market teams, not just the Fortune 500.

The control has to move with the close

If reconciliation runs every night and your review still runs once a month, you've automated the speed of mistakes and kept the catch rate on dial-up.

The fix isn't to slow the close back down. It's to make the control continuous too, which means writing down the checks that used to live in a person's head and running them on the same cadence as the reconciliation.

Duplicate-payment detection has to run daily, on vendor plus amount plus a fuzzy date window, not at year-end when the auditor asks. Set dollar thresholds that route anything above a line to a human before it clears, so the daily process can't quietly absorb a $41K mistake. And keep one scheduled review where a person reads the full trailing month, even when the books are already closed, because a clean ledger and a correct ledger aren't the same thing.

A faster close is worth having. Just don't mistake the speed for safety. The batch was carrying a control you forgot you were paying for, and the bill comes due the first time something clean turns out to be wrong.