The Month-End That Takes Two Weeks

The month closes on the 31st. The numbers arrive on the 14th.

By then the month they describe is half over, the decisions they would have informed have already been made, and everyone reads them as history rather than as information.

A number that arrives too late to change anything is a record, not a report.

Where the two weeks actually go

Rarely in the accounting. Almost always in the gathering.

Chasing what was never captured. Cash variances with no note, comps with no record, a night where the till was reset and nobody wrote down why. Each one is a phone call, and the calls are what take the time.

Reconciling things that should have matched. Card settlements against till totals, delivery notes against invoices. The work is not the reconciliation; it is finding the one that does not match and working out why, three weeks later, from memory.

Waiting for documents. Supplier invoices that arrive on the 8th, a statement that comes quarterly, an expense claim someone forgot.

One person doing all of it. Frequently the manager, in gaps between shifts.

The reframe that helps

Stop trying to make month-end faster. Move the work to the night it happens.

Almost everything above is easy on the night and hard three weeks later, because on the night the person who knows the answer is standing there.

a cash variance explained on the night → one line
the same variance in three weeks       → a phone call, a guess, or an unexplained figure

The cost of capture is roughly constant. The cost of recovery grows every day.

What to move to the night

Four things, none of which takes more than a minute:

The variance note. Whoever cashes up writes what they think caused it. Even "no idea" is useful — it distinguishes an unexplained variance from an unexamined one.

Comps, as they are given. Rung as comps rather than remembered.

Anything unusual, in one line. A till reset, a refund, a supplier paid in cash, a machine that went down. The line takes seconds and saves the phone call.

The deliveries that arrived. Signed against what was ordered, not against what the invoice says three weeks later.

What genuinely cannot be moved

Some of it is real waiting and no process will fix it.

Supplier invoices that arrive when they arrive. Quarterly statements. Anything that depends on a third party's calendar.

⚠️ For these the answer is not to speed them up. It is to produce a report that does not wait for them — a fast operational close with the known figures, and a slower financial close for the record.

Most venue decisions need the first and are held hostage by the second.

The two-close idea

Operational close, on the 1st or 2nd. Revenue, labour, comps, obvious cost of goods. Accurate to a few percent, available while the next month can still be changed. This is the one that gets used.

Financial close, when everything is in. Complete and reconciled. This is the one that matters for tax, for the accountant, and for anything requiring precision.

⚠️ Trying to make one report do both jobs is why the useful numbers arrive too late to be useful.

The test for whether it is working

Not how long the close takes.

"When we make a staffing or pricing decision, are we looking at last month or the month before?"

If the answer is "the month before", the close is too slow regardless of what the calendar says, and the operational figures are the ones to pull forward.

Two weeks of what, exactly

Calculating  a small part
Collecting  most of it
Chasing what is missing  the rest

⚠️ It is not an arithmetic problem, and buying something that calculates faster changes almost nothing.

---

The month end is decided during the month

Recorded as it happens  the close is assembly
Recorded at month end  the close is investigation

⚠️ Nothing done in the final week can compress a month of missing entries, which is why the effort always feels misplaced.

---

Find the three slowest items

Not  "it all takes ages"
But  which three things are you always still waiting for

⚠️ The list is short and everyone knows it, and it is almost never written down because each item is somebody's exception.

---

Most of them are one missing field

A payment with no purpose recorded
A cash entry with no date
An invoice with no matching order

⚠️ Each takes seconds at the time and twenty minutes a month later, because a month later the person who knows has to be found and asked.

---

Close weekly, in twenty minutes

Monthly  ninety minutes of reconstruction
Weekly  twenty minutes of memory

⚠️ The weekly version is both faster in total and more accurate, which is unusual enough to be worth acting on. 　 ⇒ And a week's gap is answerable; a month's gap is a guess.

---

Measure the days, not the effort

"It is getting better"  unverifiable
Days from month end to a figure you would act on  a number

⚠️ Write it for three months. 　 ⇒ Two weeks means every decision is made on figures that describe a 　 　 month you can no longer influence, which is the actual cost and the 　 　 only reason to shorten it.

---

---

Three to hold

Days from month end to usable operational numbers. The number that determines whether reporting affects decisions at all.

Share of cash variances with a same-night note. The single biggest driver of chase time.

Number of items still open at close. If it is the same items every month, they are structural, not accidental.

Where the record has to sit

If the till is one system, the rota another, comps nowhere, and the notes on paper behind the bar, the gathering is the work — and gathering is what takes two weeks.

tasteck keeps sales, shifts, and comps on the same nights, so the operational close is a report rather than a fortnight of assembly.

The month did not take two weeks to close. It took two weeks to find.

---

Read next

• Nightclub KPI Dashboard: What Belongs On It and What Is Just Noise
• Two Venues, One Owner, and No Comparable Numbers
• The Report You Should Read Every Monday
• Your Coat Check Is a Queue Problem
• The Till That's Always Short
• The ID Scanner You Stopped Using