A two-week close is not a staffing problem. It is what happens when every check waits until the month is over, so every exception is discovered at the worst moment to fix it.
Continuous agents raise missing accruals, outliers, probable duplicates, stale receivables and unrecognised revenue while the month is still open and the person who knows the answer is still available.
Recognition, amortisation and depreciation are idempotent, so they can run during the month and again at close without double-posting. Day one is review, not execution.
Subledger totals are derived from the same journal the control accounts read, so they agree by construction rather than after a reconciliation exercise.
Recognition is keyed by obligation and period; amortisation and depreciation by item and period. Running the close mid-month, then again at month end, posts each amount once. Without that property continuous close is just double-counting with a nicer name.
A checklist of tickable boxes cannot run early — a person has to be looking. A checklist of functions can run continuously, and tell you the state at any moment.
Subledgers freeze while accruals, recognition, FX and adjustments still post, so review does not have to fight new transactions arriving underneath it.
Once the period is signed off the journal itself refuses entries dated inside it. Continuous only works if closed genuinely means closed; otherwise the number moves after everyone stopped watching.
June is open in the console right now, with two blockers and three exceptions waiting.