Skip to Content

Fast Close: How to Finish Your Month-End Close in 5 Working Days

A practical guide for managing directors, finance managers and interim controllers in the German Mittelstand — and for any company whose close still takes three weeks longer than it should.
29 June 2026 by
Mert Ilter

The quarter just ended. Your finance team is chasing invoices, reconciling accounts and waiting on department heads to approve their cost centres. By the time the numbers land on the managing director's desk, they are already three weeks old. And by the time someone acts on them, the next quarter is already underway.

This is the cost of a slow close — not just in working hours, but in the quality of every decision made on stale data.

Fast close is the discipline of completing your month-end or quarter-end reporting within five working days of the period end. Not "as fast as reasonably possible." Five days — as a reliable, repeatable target.

In this guide you will learn what a fast close involves, why most German Mittelstand companies can achieve it with their existing systems, and what the five levers are that actually move the needle.

What "fast close" actually means

Fast close is not a software feature. It is a process standard. The term describes a finance function that has organised itself so well — with clear deadlines, clean processes and predictable data flows — that the monthly or quarterly reporting pack is ready within five working days of month-end.

The target is widely agreed across the profession: day 5. That means if the period ends on 30 June, management has a complete, reliable reporting package by 7 July.

It sounds straightforward. Most companies are nowhere near it. The German average for a Monatsabschluss is typically ten to fifteen working days — sometimes longer. Not because the numbers are complex, but because the process is not engineered for speed.

Fast close is not about cutting corners. It is about removing the waste that has built up around a process nobody redesigned after the company grew.

Why a slow month-end close costs more than time

The hidden cost of a slow close is rarely calculated — but it is real:

  • Decision lag: management is steering by data that is two to three weeks old. In a fast-moving business, that matters.
  • Finance team burnout: a team that sprints every month-end, every quarter, every year-end burns out faster than one with a steady rhythm.
  • Investor and board credibility: if monthly reporting consistently arrives late, it signals process weakness — not just to management but to PE investors, board members and lenders who monitor reporting discipline.
  • Due diligence risk: a buyer or investor conducting due diligence will notice immediately if your team cannot produce a clean month within five days on request. It raises questions about data quality and control.

The five levers of a fast close

After walking into multiple companies to build or repair their close process, I have found the same five root causes of slow closes — and the same five fixes.

1. Clear ownership and a close timetable

The single biggest accelerator is a written close timetable that assigns every task to a named person with a named deadline. Not "Accounting closes payables" — but "Anna in AP closes payables by 14:00 on day 2."

This sounds bureaucratic. It works because it removes ambiguity. People do not wait for each other if they know exactly when their deliverable is due and who is waiting on it. A one-page close calendar, circulated before each period end, is often worth a week of elapsed time on its own.

2. Daily bank reconciliation

Companies that reconcile their bank accounts daily rather than at month-end eliminate one of the most time-consuming close activities: hunting for reconciling items across thirty days of transactions.

A daily reconciliation takes fifteen to twenty minutes. It means that by day one of the close, the bank position is already clean. In DATEV, this is straightforward to set up as a daily workflow — and it removes a task that traditionally eats a full day of close time.

3. Standardised accruals

Accruals and provisions are the most common bottleneck in a German close. Every month, someone has to estimate the outstanding invoices, recurring costs, and period-end adjustments — often by calling department heads who are busy with their own month-end.

The fix: document your standard accruals once, agree the methodology, and roll them forward with minimal variation. Recurring items like rent, insurance, licence fees, and ongoing service contracts should be accrued automatically from a schedule — not re-estimated each month. Reserve ad-hoc judgment for the exceptions.

4. Hard deadlines for data suppliers

Accounting cannot close until it has received data from operations, sales, HR and any other cost-generating function. If those functions hand over data late, the close is late — no matter how efficient the accounting team is.

The solution is to set and enforce upstream deadlines: all departmental data to accounting by day 2, no exceptions. This requires buy-in from management, because accounting alone cannot enforce it. Once the rule is clear and backed by leadership, compliance usually follows quickly.

5. Automated reconciliations

Inter-company eliminations, bank-to-ledger reconciliations and balance-sheet account proofs should be automated or templated wherever possible. Every reconciliation that requires someone to manually pull data from two systems and compare them adds time and creates error risk.

In practice, most German SMEs running DATEV or a comparable ERP can automate the majority of these reconciliations with setup work rather than new software. The investment is one-time; the time saving recurs every single month.

Where DATEV fits into a fast close

Most German SMEs and subsidiaries use DATEV as their primary accounting system — often alongside a Steuerberater who handles the statutory filings. DATEV is well-suited to a fast close, but only if it is set up correctly from the start.

Common issues that slow down the close in a DATEV environment:

  • The chart of accounts (Kontenrahmen) is not structured to produce management reporting directly — so someone has to manually remap every month.
  • Posting permissions and approval workflows are not defined, so invoices queue up waiting for manual release.
  • The link between DATEV and any group reporting system (e.g. NetSuite, SAP, or a consolidation tool) is manual — a spreadsheet export that takes half a day.

None of these are unsolvable. But they need to be addressed in the system, not worked around every month. An interim controller who knows both the close process and the DATEV environment can typically close these gaps within a few weeks of starting a mandate.

Management accounts by day 5: the fast close timeline

DayActivityWho
Day 0 (last day of period)Final transactions posted; bank feeds updated; purchase ledger lockedAP / Accounting
Day 1Bank reconciliation completed; departmental data received; payroll postedAccounting + HR
Day 2Standard accruals posted from schedule; balance sheet accounts reconciledController
Day 3Trial balance reviewed; P&L draft produced; variance commentary draftedController
Day 4Management pack reviewed internally; queries resolved; KPI dashboard updatedController + Management
Day 5Final reporting pack issued to management / board / investorController / Finance Manager

This is not a theoretical model. It is the actual schedule I use when setting up a fast close in a new mandate. Most companies can get to this rhythm within one to two close cycles once the process changes are in place.

When an interim controller or finance manager can help

Building a fast close process from scratch — or repairing one that has accumulated years of workarounds — is a project, not a routine task. It requires someone who can see the whole process, identify the bottlenecks, and implement changes without disrupting the team's day-to-day work.

This is a common reason companies bring in an interim financial controller: not to do the month-end close, but to redesign it. The mandate typically runs for two to four close cycles — long enough to build the process, test it, document it, and hand it over to the permanent team.

Once a fast close is running reliably, it tends to stay running. The process improvements are structural, not person-dependent. The interim controller leaves; the five-day close stays.

Conclusion

A slow month-end close is not an accounting problem — it is a process problem. The numbers are usually not the bottleneck; the flow of data, approvals and ownership is. Fix those five levers — timetable, daily bank rec, standardised accruals, upstream deadlines, and automated reconciliations — and most companies can cut their close from three weeks to five days without buying a single new piece of software.

The result is not just faster reporting. It is better decisions, a more credible finance function, and a team that is no longer running flat out every month-end.

Is your month-end close running longer than five days?
Let's identify the bottlenecks in a no-obligation conversation. 
Book a call → or get in touch directly.

Frequently asked questions (FAQ)

What is a fast close in accounting?

Fast close is the discipline of completing month-end or quarter-end financial reporting within five working days of the period end. It is achieved through clean processes, standardised accruals, clear ownership and automated reconciliations — not through new software.

How long should a month-end close take?

The professional benchmark is five working days. Many companies take ten to fifteen days or longer. The gap is almost always a process issue rather than a data-complexity issue.

Can we achieve a fast close using DATEV?

Yes. DATEV supports a fast close well when it is set up correctly: a structured chart of accounts, automated bank feeds, defined posting workflows and a clear link to any group reporting system. Most of the work is in the setup, not in the software itself.

Do we need an interim controller to implement fast close?

Not necessarily — but it helps. Building or repairing a close process while running the existing close is difficult without external support. An interim controller with fast close experience can typically implement the changes within two to four close cycles and hand over a running process.

What is the difference between fast close and hard close?

A hard close means all transactions for the period are finalised — nothing can be posted retroactively. A fast close is about speed. In practice the two go together: a hard close on day 0 is usually a prerequisite for a reliable five-day close.

Book a free 30-minute assessment