A scale-up with 40 employees can often still get by with one accounting tool, an Excel plan and one person in the finance team. With 150 employees, a second legal entity and a board that expects numbers every month, that no longer works. The processes do not all break at once, but in a fairly typical order. This article shows which finance processes come under pressure first, how you can tell, and which next step is enough in each case.
Key points
- The month-end close is usually the first bottleneck. Planning and reporting depend on it directly.
- For every process, the approach is the same: spot the symptom, take the smallest step that works, and check how long it holds.
- Systems and group structure come after stable processes, not before.
- Controls such as the four-eyes principle must be documented at the latest before a due diligence.
Warning signs: how you can tell your finance processes are not keeping up
The following signs show up often in growing companies. One alone is not yet a problem, but several together are a clear signal.
- The month-end close takes longer than ten working days or is regularly corrected in the following month.
- Several Excel versions of the forecast are in circulation, and nobody is sure which one is current.
- Invoices are approved by email or a quick word, with no defined limits and no record.
- The board reporting is built by hand every month and ties up the head of finance for several days.
- There is a second entity or a foreign subsidiary, but no fixed process for intercompany charges and consolidation.
Process by process: symptom, next step, how far it carries you
The sections follow the order in which the processes typically come under pressure.
Month-end close
Symptom: The close takes a different amount of time every month, documents are missing, and accruals are booked after the fact.
Next step: A close checklist with fixed days, owners and cut-off dates for documents. The month-end close calendar for ten working days shows what such a process looks like. If you already have a backlog, it has to be cleared first, see interim accounting for closing backlogs.
Enough as long as: documents come from a few sources and only one entity is closed. With several entities or many cost centres, you also need system support.
Forecasting and planning
Symptom: The forecast is only updated for a funding round, and actuals cannot be compared cleanly against the plan.
Next step: A planning model with the same account structure as the accounting, and a fixed monthly rhythm for plan-versus-actual reviews. A rolling forecast keeps the plan current without starting over every year.
Enough as long as: one person maintains the model and the departments hand in their budgets through discussion. Once several budget owners are expected to plan directly, a dedicated FP&A tool is worth it.
Reporting for the board and investors
Symptom: Every board pack looks different, metrics are redefined each time, and preparation takes days.
Next step: A fixed reporting format with consistent metrics and definitions. You can find a template in the article PE reporting: sample board pack and Excel template.
Enough as long as: the close delivers on time. A good reporting format does not fix a close problem, it only makes it more visible.
Payables and approvals (purchase-to-pay)
Symptom: Invoices arrive through many channels, approvals happen by email, and payments are triggered by one person alone.
Next step: A central invoice inbox, an approval matrix with amount limits, and payments only after a second approval.
Enough as long as: the number of suppliers and cost centres stays manageable. After that, purchase orders linked to budgets and an approval tool connected to the accounting system help.
Receivables and order-to-cash, including SaaS revenue recognition
Symptom: Invoices are written by hand, open items are rarely chased, and ARR, revenue and cash receipts give three different numbers with no explanation.
Next step: Invoicing straight from the contract or billing system, a fixed dunning run, and a monthly bridge from ARR to booked revenue. For annual contracts, revenue is spread over the contract term and amounts billed in advance are deferred. The article ARR, revenue and cash receipts explains the differences.
Enough as long as: the contract models are simple. With usage-based pricing, discount tiers or multi-year contracts, revenue recognition usually needs a system-based solution.
System landscape: accounting software, ERP and DATEV
Symptom: Data is moved between tools by export and import, and side calculations in Excel stand in for missing functions.
Next step: First connect the tools you already have through interfaces. If your tax advisor works with DATEV, the handover of booking data has to be clarified and stable. An ERP makes sense once several entities, foreign currencies or complex approvals come into play. The article DATEV alternatives for startups compares the options. What can realistically be automated is covered in what can really be automated in the finance function.
Enough as long as: the processes behind it run stably. Putting a new system on top of unresolved processes only moves the problems.
Group and entity structure, consolidation
Symptom: A new entity is founded or acquired, services between the entities are not charged consistently, and group figures are built in Excel.
Next step: One chart of accounts for all entities, contracts for intercompany services, and a monthly reconciliation of the balances between entities. The article Buy-and-build: consolidation and group reporting describes how to set up group reporting.
Enough as long as: the number of entities stays small. Whether consolidated accounts become a legal requirement depends on size and structure and should be clarified with your tax advisor and auditor.
Controls and the four-eyes principle before due diligence
Symptom: Important processes depend on individuals, master data such as bank details can be changed without a second check, and nothing is documented.
Next step: The four-eyes principle for payments and master data changes, separate roles in the systems, and short documentation of the key processes. The article Red flags in startup due diligence shows what investors look for.
Enough as long as: no audit requirement or transaction is coming up. At the latest then, the controls must demonstrably work, not just be described.
In which order you should proceed
The table is a guide, not a fixed rule. Industry, business model and funding shift the priorities.
| Phase (employees) | Priorities |
|---|---|
| 30–80 | Month-end close with a checklist, approval matrix and four-eyes principle for payments, a planning model with plan-versus-actual comparison |
| 80–200 | Fixed board reporting, system-based invoicing and revenue recognition, interfaces between the tools, evaluating an ERP |
| 200–500 | Consolidation of several entities, documented controls for audits and due diligence, FP&A with direct budget planning by the departments |
What comes first right after a funding round is covered in the article Finance setup for the first 90 days after a funding round.
Conclusion
Finance processes in scale-ups rarely fail because of one big mistake, but because of many small routines that were built for a smaller company. If you start with the month-end close, secure approvals early and only put systems on top of stable processes, you stay able to act as the team grows. If your internal team is fully occupied with day-to-day work, a head of finance on a temporary basis or interim accounting and FP&A can take over the rebuild for a fixed period and then hand it back.
Frequently asked questions
Which finance process usually breaks first as a company grows?
In most scale-ups it is the month-end close. It depends on a few people, on documents from many departments and on manual reconciliations. When it slips, the forecast and board reporting automatically arrive late, so it pays to start there.
When does a scale-up need an ERP instead of accounting software?
There is no fixed headcount for this. Typical triggers are several entities, foreign currencies, approval workflows with many cost centres, or revenue recognition that can only be handled with side calculations in Excel. As long as the close runs stably with accounting software and clean interfaces, an ERP is usually not yet needed.
How long should a month-end close take in a scale-up?
As a guide, ten working days for a reliable close including accruals. More important than the number is that the close runs the same way every month, responsibilities are fixed, and the result needs no major corrections in the following month.
What needs to be in place in the finance processes before a due diligence?
Buyers and investors check whether numbers are produced in a traceable and repeatable way. That includes a documented close process, the four-eyes principle for payments and master data changes, reconciled receivables and payables, explainable revenue recognition and a clean bridge from ARR to revenue.
Do all finance processes have to be rebuilt at the same time?
No. A sequence makes sense: first stabilise the close and approvals, then build planning and reporting on top, and only then tackle systems and group structure. Changing everything at once often costs you the comparability of the numbers during the transition.
When does temporary support for rebuilding finance processes make sense?
When the existing team is fully occupied with day-to-day work and the rebuild still has to be done within a fixed period, for example before a funding round or an audit. An interim hire can lead the rebuild and hand it over to the internal team.
