How do you build the finance function in a growing company?
A finance function does not mature on its own as a company grows. Recording, control, reporting and planning have to be built in the right order; otherwise every new report inherits the errors of the last.
In a small company, finance is usually just accounting: invoices are recorded, tax returns are filed, payments are made. As the company grows, that structure becomes inadequate, but not all at once. Reports slip, numbers get disputed, cash surprises become more frequent.
Building the finance function does not mean finding a separate fix for each symptom. It means building layers that sit on top of each other, in the right order.
A four-layer structure
| Layer | Question | Core output |
|---|---|---|
| 1. Recording | Are transactions recorded completely and correctly? | Reliable accounting data |
| 2. Control | Are errors caught in time? | Reconciled accounts, approval flows |
| 3. Reporting | Does management see the right information on time? | Monthly management report |
| 4. Planning | Is there a quantified expectation for the future? | Cash plan, budget, forecast |
The order matters. A report built on unchecked records misleads, however polished it looks. A budget prepared without a reliable reporting base cannot be compared with actuals.
1. Recording: chart of accounts and document flow
The first task is to shape the chart of accounts around management’s needs. In Turkey the statutory chart of accounts stays in place, but sub-accounts and cost centres should be designed to produce the breakdowns management wants to see (product, branch, project). How quickly documents reach accounting is part of this layer too: a late invoice means a late report.
2. Control: reconciliations and approvals
Regular bank, counterparty and inventory reconciliations, and clearly defined approval limits for payments and purchasing, belong to this layer. The aim is not bureaucracy but catching an error when it happens rather than at month end. To decide where controls are needed, see key control points in financial processes.
3. Reporting: the close and the management report
Tying the monthly close to a fixed calendar is the best single indicator of a mature finance function. It is followed by a management report in which a small number of indicators are reported with the same definitions every month. I suggest a framework for choosing them in Which KPIs belong in a management report?
4. Planning: cash, budget, forecast
Once the first three layers are in place, planning becomes meaningful. In practice the order is usually a short-term cash plan first, then an annual budget, then a regularly updated forecast.
People and roles
Building a finance function is not a software project. It must be clear who records what, who checks what and who signs off the report. In small teams one person may hold several roles; what matters is that the person who records and the person who checks are kept apart as far as possible.
Common mistakes
- Buying software first: software bought before the process is defined automates the existing disorder.
- Reporting everything: a report with fifty indicators highlights none of them.
- Leaving the budget to accounting: a budget is management’s commitment, not a finance exercise; without operational owners it is meaningless.
I describe how the fractional CFO model can be used to build this structure in What is a fractional CFO?