The four-week close is a scheduling problem

Teams rarely close late because the accounting is hard. They close late because the work waits in queues nobody can see: an inbox waiting for one approver, a warehouse count that reaches finance on day three, a reconciliation that starts only when the bank statement lands.

If you map a four-week close, the pattern repeats. The work itself is measured in hours. The waits are measured in days.

Where the time goes

A typical long close spends its time in four places:

1. Waiting for inputs. Stock counts, shipping logs, and purchase orders arrive on their own schedule, and finance works around them.
2. Serial hand-offs. Preparer to reviewer to approver, each step starting after the previous one fully ends.
3. Rework. A variance found on day eighteen sends the team back to day six.
4. Assembling evidence. Collecting the approval trail takes longer than the approvals did.

None of these are accounting judgments. All of them are scheduling and visibility problems, which is why they respond to tooling rather than to more accountants.

Shorten the waits, not the work

The close compresses when the queues become visible and the hand-offs overlap:

• Move inputs online. A count entered on a tablet at the warehouse arrives the moment it is taken. Finance stops planning around arrival dates.
• Run matching continuously. Bank lines matched daily leave a small queue at month-end instead of a wall.
• Let approvals carry their documents. An approver who sees the invoice, the receipt, and the policy approves in one sitting.
• Generate the evidence as you go. The audit trail is a byproduct of the workflow, not a project at the end.

A realistic target

Teams that do these four things rarely reach a two-day close, and they do not need to. A five-day close with no rework beats a three-day close that gets redone. The number worth watching is not the finish line — it is how early in the month you know where you stand.