Most finance teams treat the month-end close like a fire drill. Every month, the same chaos: someone is waiting on invoices, another person is chasing approvals, and by the time the numbers are ready, it is already the 20th and half of management has stopped caring.
It does not have to work this way.
After running month-end close processes across companies ranging from CHF 11M startups to CHF 200M retail operations, I can tell you that the difference between a 5-day close and a 3-week close is almost never a question of complexity. It is a question of structure.
This article gives you that structure: a practical, sequenced checklist built for the Swiss context, with notes on where SAP and common local ERP setups tend to create friction.
Why the Close Date Actually Matters
Before the checklist, a quick word on why closing speed matters beyond the obvious.
When your books close on day 10 or later, leadership is making decisions in a vacuum. The CEO is reviewing October numbers in late November. By then, the trends you are seeing are already three to four weeks stale. Any corrective action is delayed by at least a month. Multiply that across a full year and you have a business running perpetually one step behind reality.
The gold standard for high-performing finance teams is 5 to 7 working days. Mid-sized companies typically land between 7 and 10. More than 10 days is a signal that the process has structural problems, not just workload problems.
For the controlling side specifically, the close is not just about getting numbers posted. It is about producing a reliable, explainable picture of what happened and why. That means your accruals need to be accurate, your reconciliations need to be clean, and your variance commentary needs to be ready before leadership gets the report. The accounting team handles the posting side. The controller’s job is to make sure the numbers make sense.
The Architecture of a Fast Close
A well-run close has three distinct phases: pre-close preparation, the active close window, and reporting. Most companies collapse all three into a single chaotic push. Separating them is the first structural improvement you can make.
Phase 1: Pre-close (during the last week of the month)
Much of the groundwork for a fast close can be done before the month even ends. Intercompany balances should be agreed between entities before the last day. Payroll uploads, should be validated as soon as they hit the system. Advance checks and corrections to insurance contracts (such as Swica daily sickness or accident provisions) can be cleared as soon as payroll data is available. This is also the window to verify that KPI inputs, such as FTE counts, square meters, ticket volumes, and passenger numbers, are being gathered by the responsible owners.
If you wait until day 1 of the close to start thinking about intercompany, you have already lost two days.
Phase 2: The active close window (working days 1 to 5)
This is where the bulk of the work happens and where sequencing matters most. Some tasks are hard dependencies: you cannot finalize your cost accruals until payables are closed, and you cannot post inventory losses until stock positions are confirmed. Getting the sequence right prevents bottlenecks.
Phase 3: Reporting and review (days 5 to 7 or 5 to 10 depending on company size)
Once the numbers are posted, the controller’s job shifts to checking integrity, preparing variance commentary, and packaging the management report. This phase is frequently underestimated. Budget-versus-actual analysis done well takes time. Rushing it produces reports that technically have the right numbers but tell leadership nothing useful.
The Checklist: Sequenced by Priority
The following is a working checklist structured around timing and dependency logic. It reflects a closing calendar and has been adapted for broader applicability.
Before Day 2 of the Close (Hard Deadlines)
These items need to clear first because other tasks depend on them.
Integrity check: ERP to source systems. Before anything else, confirm that all transactional data has actually arrived in your ERP. This means verifying that all point-of-sale uploads are complete and that till reconciliations match. Missing sales data from a disconnected terminal, a common issue in high-volume retail or hospitality environments, will corrupt every downstream calculation. Run your integrity check first. This is non-negotiable.
Cash and credit card reconciliation. Reconcile all till and credit card settlements against bank feeds and POS system data. Any variance needs an owner and a corrective action immediately. A register variance account sitting open at month-end is a red flag that will come up in any serious audit.
Concession fees and IFRS 16 accruals. If your company operates under lease agreements, particularly concession-based arrangements, these entries have early posting deadlines because they affect both P&L and the balance sheet. In SAP, this typically means running the relevant FI-CO postings from your lease schedule before other accruals are calculated.
Receivables open amounts. Flag any receivable positions that are aged or unusual. These do not need to be resolved by day 2, but they need to be on someone’s radar.
By Day 5 of the Close
Payables closure and standard accruals. Only after payables are fully closed can you finalize your other expense accruals. Standard operating expense bookings that are not yet invoiced should be accrued based on either budget or the latest forecast, whichever is more defensible. Temporary staff costs, which are often invoiced late, are a common accrual gap.
Inventory reconciliation. This has two components that need to be checked separately. First, reconcile local inventory positions against intercompany stock records to catch any discrepancies between what your system shows and what the counterparty shows. Second, calculate and post any inventory stock losses and obsolescence provisions. At a site with tens of thousands of SKUs, this step requires a structured approach: define your impairment thresholds in advance, run the obsolescence analysis, and post a provision rather than leaving the exposure unrecognized.
Overtime, holiday accruals, and gross-to-net corrections. These are frequently underestimated or skipped entirely. If employees have accrued overtime or unused holiday, that is a liability that needs to be on your balance sheet. The gross-to-net file, which reconciles payroll gross to net amounts, should be reviewed for any corrections before the period is locked.
CAPEX activations. Any capital expenditure that has been completed and put into use during the month needs to be activated and moved from work-in-progress to fixed assets. Leaving items in WIP that should be activated distorts your depreciation charge and your balance sheet.
Accruals review. Before finalizing the period, do one complete pass through all open accrual positions. Are the reversals from last month processed? Are there any positions that should be released because the underlying obligation no longer exists? This review often surfaces CHF amounts that have been sitting on the balance sheet for months longer than they should.
ERP cost center downloads and KPI postings. Run your cost center extraction from your ERP and verify that all allocations have posted correctly. Shared costs that are allocated across business units need to balance to zero at the group level. Any imbalance here creates a discrepancy in your management P&L.
Push line confirmation. In businesses with multiple locations or channels, there is often a reporting cut-off point, sometimes called a push line, which defines what is included in the current period. Confirm that this line has been set correctly in your system before running final reports.
Bank reconciliation. Standard item but worth stating: all bank accounts should be reconciled to statement before the period is closed. Any unreconciled items need documented explanations.
Where Swiss ERPs Create Friction
Swiss companies most commonly use SAP, Abacus, or Bexio. Each creates different types of month-end friction.
SAP is powerful but unforgiving about data quality. The biggest recurring issues are not in the system itself but in what flows into it. Non-automated data entries, such as goods receipts, vendor registrations, and invoice approvals, have no built-in quality filters. A goods receipt posted with the wrong cost center, or an invoice approved by someone who does not understand the cost center structure, creates a posting that is technically valid but analytically wrong. The controller ends up spending day 3 or 4 correcting reclassifications that should never have happened. The fix is upstream: better training on posting rules and, where possible, mandatory field validation on key inputs.
A second SAP-specific issue is the reconciliation between systems. If you are running SAP alongside a separate treasury management system, a separate POS system, or a customs platform like Trinity, reconciling between those environments is manual work. There is no automatic cross-system integrity check. You build that yourself, usually in Excel, which means it is only as reliable as the last person who updated the formula.
Abacus is well-suited for Swiss SMEs and handles OR-compliant accounting cleanly. Its limitation for controlling purposes is reporting flexibility. Getting segmented P&Ls or cost-center level views out of Abacus requires more configuration effort than most SME implementations include. If your Abacus setup was done primarily for accounting and tax purposes, the controlling layer is likely thin or missing entirely.
Bexio is a solid bookkeeping tool for very small companies but it is not a controlling platform. If your business has grown beyond 20 or 30 employees and you are still relying on Bexio for your management reporting, the month-end close is probably a manual Excel exercise that takes longer than it should.
The Single Most Common Reason Closes Run Late
Unclear ownership.
Every item on your close checklist needs exactly one person responsible for completing it and one person responsible for reviewing it. Not a team. Not a department. One person.
When a task has no named owner, it gets done last, done late, or not done at all. When two people think they are both responsible for the same task, it either gets done twice with conflicting results or falls through the gap between them.
A close calendar with named owners and hard deadlines, visible to the entire finance team and relevant department heads, eliminates most of the chasing that makes month-end feel like a crisis every month.
The checklist template at the bottom of this article includes an owner column for exactly this reason.
A Note on the Controller’s Role in the Close
This article is written from the controller’s perspective, which means some items, payroll posting, tax provisions, statutory adjustments, are deliberately outside its scope. Those sit with the accounting or Treuhänder function. The controller’s job during close is to ensure that the management reporting layer is accurate, complete, and ready to explain.
That means: accruals are posted and defensible, variance drivers are identified, KPIs are verified, and the management report is ready with commentary by the time leadership needs it. The accounting close and the controlling close are related but not identical processes. Confusing them is one of the reasons companies end up with technically correct books and analytically useless reports.
Download the Checklist Template
The month-end close checklist below is available as a working Excel template with owner columns, status tracking, and sequencing logic built in. It is structured around the timing framework described in this article and adapted for the Swiss context.
Download the Month-End Close Checklist
If your current close is taking more than 10 working days and you want to understand where the time is actually going, I offer a structured process review as part of my fractional CFO and controlling engagements. The first conversation is free.
Ready to improve your financial reporting? Book a free 30-minute call to discuss your situation.
Alessandro Ratzenberger is a fractional CFO and business controller based in Zurich, with 15 years of operational finance experience at Dufry Group and Bomi (UPS Group).
