Reliably Complete the Month-End Close in 5 Days

Shortly after the month turns, the same procedure begins in many companies: controllers chase missing time entries, HR staff search for outstanding absence reports, and project managers wait for hour totals that are not yet available for reliable billing. The month-end close drags on for ten days, sometimes longer. The figures arrive late, and decisions are based on an outdated foundation.

This is not a failure of individuals but a structural problem. It arises when a clear process, a binding deadline, and a system that makes gaps visible before they are frozen are all missing. The good news: this bottleneck can be eliminated.

Key points at a glance:

• A month-end close is not legally required under commercial law, but it is the foundation of every functioning controlling operation
• At project level, missing or delayed closes generate direct costs: incorrectly billed hours, uncontrollably growing overtime accounts, delayed client invoices
• Four in five insolvencies among German SMEs are attributable to missing or inadequate controlling, according to an analysis by Euler Hermes and the University of Mannheim
• A structured close by the fifth working day of the following month is achievable with the right processes and system support

Where the Month-End Close Becomes a Problem in Everyday Project Operations

The month is over, but the data is not. In project-oriented companies — IT service providers, agencies, consultancies, and engineering firms — time entries typically arrive with a delay. Those working across multiple projects in parallel often only catch up at the weekend or in the first week of the following month. Absences are not reported in the system in time. Travel expense reports arrive weeks later.

The result is a data foundation that is already outdated at the time of evaluation. For controllers and executives, this means: the monthly management meeting takes place with figures that do not reflect the actual position. Projects continue on the basis of incorrect actual costs, resources are allocated incorrectly, and client invoices diverge from the services actually delivered.

The Four Most Common Weaknesses Before the Close

1. Time recording gaps at employee level. Project hours are sporadically entered retrospectively, sometimes over several weeks. As long as no system-level deadline takes effect, this effort keeps being pushed further back.
2. Absence management without system integration. Vacation and sick leave notifications are handled by email, paper slip, or verbally. Gaps arise in the monthly overview that have to be researched manually.
3. Overtime accounts without ongoing monitoring. According to the IAB Working Time Calculation 2025, employees in Germany worked an average of 15.6 unpaid overtime hours per person per year. In project-oriented industries, this figure is significantly higher. Without a monthly reconciliation against target working hours, the overtime account grows unchecked until the statutory compensation period can no longer be met.
4. No binding close moment. Anyone who sets no deadline at which data is locked invites retrospective corrections. This undermines data integrity and renders the month-end close effectively worthless for controlling.

What a Month-End Close Under HGB Means and What It Achieves

Under commercial law, the month-end close is not a standalone mandatory component. The statutory obligation relates to the annual financial statements: all companies required to keep accounts must, under Section 242 HGB, prepare a balance sheet and a profit and loss account at the end of the financial year. For corporations, additional deadlines and disclosure obligations to the company register apply under Sections 264 et seq. HGB.

The month-end close under HGB is, within this framework, a recommended rather than mandatory practice: it maps all business transactions of the previous month on a period-accurate basis and thereby creates the foundation for meaningful in-year reporting. In practice, it is understood as a “mini annual close” that is repeated monthly and prepares the annual close in terms of content.

What the Month-End Close Must Contain

A complete month-end close encompasses, from an accounting and HR management perspective, at least the following components:

• Complete posting of all incoming and outgoing invoices for the previous month
• Reconciliation of debtors and creditors including open items
• Period-accurate recording of accruals and deferrals
• Reconciliation of target and actual working hours for all employees
• Review and approval of overtime balances and vacation accounts
• Locking the period against further changes

Only when all these steps are completed are the figures robust enough for monthly reporting to management, tax advisors, and investors.

An important point that is frequently underestimated in project-oriented companies: accruals and deferrals for outstanding supplier invoices or services not yet invoiced must be included in the month-end close. If they are omitted, the monthly profit and loss account is significantly distorted. Project costs appear too low, contribution margins too high. The management decisions made on this basis are then systematically miscalibrated.

Month-End Close Example: What Happens Without a Process

A management consultancy with 60 employees carries out the month-end close without fixed deadlines and without a system-level lock. Project managers enter hours up to three weeks after month-end because there is no binding booking deadline. HR receives absence notifications in parallel by email and phone. By the time of the monthly executive meeting — which regularly takes place on the 15th of the following month — the figures are still incomplete. Decisions on project staffing and resource planning are made on the basis of estimated values. Client invoices deviate from actual services in several cases and must be cancelled and corrected.

{{blog-cta}}

Creating the Month-End Close: Step-by-Step Implementation

A structured month-end close follows a fixed rhythm with clear responsibilities. The difference between a company that takes ten days and one that manages five rarely lies in the volume of data. It lies in whether the process begins before or after month-end.

Month-End Close Preparation: What Determines the Outcome Before the Deadline

A month-end close that only begins on the first of the following month is already too late. Preparation takes place during the current month. This includes specifically:

• Clear booking deadlines for all employees. Anyone who wants to be done by the fifth of the following month needs an internal booking deadline of the last day of the previous month. This deadline applies to employees on heavily utilized projects as well.
• Automatic reminders instead of manual follow-up. When the system directly notifies employees of missing entries and simultaneously alerts their line managers, the manual follow-up effort for HR and controllers is eliminated.
• Absence requests in the system, not by email. Vacation requests, sick leave notifications, and other absences submitted outside the system never reliably find their way into the month-end close. Anyone who approves absences by email or verbally creates a data source that does not correspond to system reality.

Month-End Close Controlling: Focus on Evaluations

Once the month is closed, the actual controlling work begins. Which projects have exceeded their budget? Which employees have overtime accounts that need to be compensated in the coming weeks? Which departments show conspicuous absence rates?

These questions can only be answered if the data foundation of the close is complete and unchanged. This is why the close exists as a process step: it creates a temporally delimited snapshot on which analyses and reports can be based. Without this snapshot, controlling permanently works with data that may still change, and thus produces evaluations that may already be outdated by the time they are read.

Step 2: Check Completeness Before the Deadline

Two to three days before the planned close, a completeness check should take place. Which employees still have open days? Which absences have not been recorded? Which overtime balances deviate conspicuously?

This check is the last moment at which corrections are still possible without jeopardizing the close. It should therefore always take place before the deadline. If this check only occurs after the close, retrospective changes become inevitable, extending the entire process and jeopardizing data integrity.

It is worth examining the causes of completeness problems: in project-oriented companies, the most common reason for missing entries is the division of labor between time recording and project work. Employees under pressure in projects prioritize the task, not the documentation. Without system reminders or automatic escalation to the line manager, there is no sufficient incentive to keep entries current.

Step 3: Enforce the Deadline at System Level

Binding commitments arise through a mechanism that technically prevents changes after the deadline. Hints and friendly reminders are not sufficient for this. A month that can still be changed after the close is not, from an accounting perspective, a closed month. It is an open file with an unknown final state. Only a system-level lock creates the foundation for audit-proof evaluations.

Step 4: Generate and Distribute Evaluations

On the basis of the locked data, the reports for controlling are produced: working time overview, absence overview by category, overtime balances per employee, project time evaluations. These reports are then audit-proof and directly reusable.

Month-End Close Checklist: Tasks, Responsibility, Deadlines

Who must complete what by when in the month-end close?

The Month-End Close in ZEP: Check, Lock, Evaluate

ZEP maps the entire month-end close process in a single platform. Administrators can carry out the close for all employees in one step. The system automatically calculates the balance of overtime, absences, and vacation entitlements on the basis of stored standard working hours and the hours actually booked.

Working Time Overview: See Gaps Before They Are Frozen

Before the month is closed, the working time overview in ZEP shows at a glance whether all employees have fully booked their hours. Fields highlighted in red signal days on which the entry falls below the defined minimum percentage of standard working time. Grey fields mark days off, weekends, and public holidays. Yellow fields indicate break regulations that have not been observed.

This color-coded overview makes catch-up requirements visible before they become a problem. Clicking on a day opens a detail window with all project entries for the employee. Corrections can be made directly from there.

Month-End Close and Lock: What This Means in Concrete Terms

Once the month is closed in ZEP, no project hours, absences, or receipts can be changed. This lock applies at system level for all users. For retrospective corrections that may be required in exceptional cases, the close can be selectively lifted for an individual employee without opening the entire month for everyone. The administrator unlocks the relevant employee, makes the correction, re-locks them, and closes the month again.

Month-End Evaluation and Annual Overview

The month-end evaluation in ZEP gives each employee insight into their current status: hours worked per day, overtime balance, absences by category, residual vacation entitlement. This transparency significantly reduces queries to HR and creates a shared data foundation between employees, team managers, and the HR department.

For companies managing contractually offset overtime, ZEP automatically calculates the monthly amount to be offset on the basis of the stored standard working time. This means: anyone who has agreed in their employment contract that up to ten overtime hours per month are included in the salary will have this deduction automatically taken into account in the overtime balance. Corrections can be stored individually per employee.

The annual absence overview provides a comprehensive view per employee across the current financial year, broken down by reason for absence. Controllers and HR managers use this evaluation for absence analyses, capacity planning, and the preparation of annual reviews. Illness clusters or seasonal absence patterns become visible at a glance.

Through the connection with project controlling in ZEP, closed monthly data flows directly into project evaluations: hour statements, budget comparisons, and cost reports are reliable on the basis of locked, immutable data and can be passed directly to clients or the tax advisor.

What a Lack of Systematic Approach Costs in the Medium and Long Term

The direct costs of an unstructured month-end close are rarely visible as a single line in the budget. They are distributed across several areas simultaneously.

Retrospective corrections to client invoices generate additional administrative effort and undermine confidence in one’s own quality. Accruals in the annual financial statements for overtime or absences that were not properly accrued could have been avoided with a clean monthly close. During audits, auditors regularly check whether working hours have been fully and period-accurately recorded. If reliable monthly closes are absent, considerable proof-of-evidence effort results.

Why Excel-Based Closes Reach Their Limits

Many companies carry out their month-end close via spreadsheets. This works until multiple people are entering data simultaneously, formulas are changed, or previous versions can no longer be found. A central data foundation with a system-enforced lock cannot in principle be replicated in Excel. Anyone who “completes” a month’s close in a spreadsheet can reopen and change that spreadsheet the next day without anyone noticing the change.

This is precisely the problem that leads to considerable additional effort during audits and when preparing annual financial statements: there is no reliable version of the truth for the closed month.

Companies that close their month-end by the fifth working day have 20 days in the month to steer on the basis of current figures. Companies that wait until the 20th have five. These 15 days of difference determine whether project controlling is proactive or reactive.

Conclusion: Three Measures for Immediate Impact

The month-end close is not an accounting ritual. It is the moment at which a company decides whether it manages with data or with estimates.

1. Introduce and communicate a booking deadline. Establish by which date all time entries must be fully recorded. This deadline applies as non-negotiable for all employees.

2. Define responsibilities in writing. Who checks which area by when? Missing responsibilities are in practice the most common reason for delayed closes.

3. Establish a system-level lock as standard. A month that can still be changed after the close is not a close. Only a system-enforced lock creates the data integrity on which reliable controlling can be built.