What a Finance Operating System Looks Like
A finance operating system is not a single piece of software. It is a connected set of tools, each handling a specific function, that together give the CFO real-time visibility of financial position, support efficient transaction processing, and enable fast, reliable reporting. The core components and the typical software choices at growth stage are as follows:
- Accounting and ERP: The system of record for all financial transactions. At seed to Series A: Xero (best-in-class for UK SMEs, strong bank feed integration, good VAT handling). At Series B and above: NetSuite (the de facto standard for pre-IPO scale-ups requiring multi-entity consolidation, advanced revenue recognition, and audit-grade controls) or Sage Intacct (a strong NetSuite alternative, particularly for professional services and multi-entity structures).
- FP&A: The financial planning and analysis layer, used for budgeting, forecasting, and management reporting. At Series A: Pigment or Mosaic are both strong cloud-native FP&A tools built for growth-stage companies, with direct Xero and Salesforce integrations. Workday Adaptive Planning is the enterprise standard at Series C and beyond. A well-maintained Excel model with Power Query is still a legitimate choice at Series A if the finance team has the skills to maintain it, but the scalability ceiling is real.
- Expense management: Pleo, Soldo or Airbase for card-based and out-of-pocket expense management. These tools replace the paper receipt and spreadsheet process, apply spend controls at the point of purchase, and integrate with Xero or NetSuite to automate posting. The ROI on implementing one of these tools is typically 2 to 4 hours of finance team time saved per week per 10 card users.
- Payroll: Rippling (increasingly popular for UK companies with US or multi-country operations), Deel (strong for contractor and global employee payroll), or ADP (the established enterprise option). For a purely UK business with fewer than 100 employees, Xero Payroll or BrightPay are simpler and lower-cost options.
- Treasury: For most growth-stage companies, treasury management is handled within the ERP or via a dedicated cash management module. Dedicated treasury management systems (Kyriba, TreasuryXpress) become relevant at £50m+ revenue with complex multi-currency cash positions.
- Reporting and BI: Looker (now Google Looker Studio Pro) or Microsoft Power BI for the operational dashboard layer. These tools connect to the data warehouse and provide the self-serve analytics that department heads and the board need, without requiring every ad hoc request to go through the finance team.
How to Choose and Sequence the Build
The most important principle is to implement the right tool for the current stage, not the tool you expect to need in three years. The cost of implementing NetSuite at seed is disproportionate: it requires a minimum 3 to 6 month implementation, a dedicated administrator, and ongoing licensing costs of £20,000 to £40,000 per annum. The cost of migrating from Xero to NetSuite at Series B is real but manageable with adequate planning, and it is the right sequencing decision.
The trigger for moving from Xero to NetSuite is typically one or more of: more than 2 legal entities requiring consolidation, revenue recognition complexity (multi-element arrangements, ASC 606/IFRS 15), audit readiness requirements from a Big 4 auditor, or investor reporting requirements that exceed what Xero's reporting can handle. This typically occurs at Series B or upon a significant commercial contract win that introduces revenue recognition complexity.
Integration Architecture: Getting Data to Flow
The most common failure mode in growth-stage finance systems is not choosing the wrong tools. It is failing to connect them properly, resulting in a situation where the accounting system, the FP&A model, the CRM, and the HR system all have different numbers for the same metric, and reconciling them consumes hours of finance team time each month.
The correct integration architecture for a growth-stage company is API-first, with a central data warehouse as the integration layer. The data warehouse (typically Snowflake or Google BigQuery at growth stage) receives data from all operational systems, transforms it into a consistent format, and serves as the single source of truth for all downstream reporting and analytics.
The alternative, point-to-point integrations (connecting Xero directly to Salesforce, Salesforce directly to the FP&A tool, the FP&A tool directly to the HR system), creates a web of bilateral dependencies that is expensive to maintain and fragile when any single tool is upgraded or changed. It also means that each bilateral integration has its own latency and error rate, making it difficult to know which number is correct when systems disagree.
"The question is not whether to invest in finance systems. It is whether to invest now, on your terms, or in twelve months in a panic because your auditors have raised a material weakness on data integrity and your Series C data room is a mess. The cost of an ERP upgrade is the same either way; the timing makes all the difference."
Common Data Governance Pitfalls
Technology is the easy part of building a finance operating system. The hard part is data governance: the policies, processes, and controls that ensure data quality, consistency, and integrity across the stack.
The most common data governance failures at growth stage are:
- Inconsistent chart of accounts: Different entities or periods use different account codes for the same type of expenditure. This makes consolidation unreliable and management accounts inconsistent. Establish a chart of accounts policy at Series A and enforce it across all entities and in every ERP implementation.
- Master data management failures: Customer names, product codes, and cost centre definitions used inconsistently across the CRM, ERP, and FP&A tool. A customer called "Acme Ltd" in Salesforce and "ACME Limited" in Xero and "Acme" in the FP&A model is three different records until a human resolves the discrepancy. Standardise master data definitions and governance before connecting systems.
- Period-end cut-off inconsistencies: Different systems close at different times, resulting in the same transaction appearing in different periods in different systems. The ERP closes at midnight on the last day of the month; the CRM may not be closed off until the sales team submits their pipeline update two days later. Define and enforce a consistent cut-off policy across all systems.
- Uncontrolled manual adjustments: Adjustments made directly in the FP&A tool or the BI dashboard that are not reflected in the ERP create a permanent discrepancy between the system of record and the reporting layer. All adjustments must flow through the ERP.
The Business Case for Finance Systems Investment
Finance systems investment is frequently deprioritised in favour of product development, sales, and marketing. The CFO's job is to make a credible, quantified business case for the investment. The case typically rests on three pillars: time saved (and its cost equivalent), error and risk reduction, and audit and investor readiness improvement.
A typical Series B company migrating from Xero to NetSuite and implementing a data warehouse can expect: a reduction in month-end close time from 8 to 12 business days to 4 to 5 business days (saving 15 to 20 finance team days per month, worth approximately £30,000 to £60,000 per annum at a blended team cost); elimination of the management accounts reconciliation process between Xero and Excel (typically 2 to 3 days per month); and a significant improvement in audit readiness that reduces external audit fees by approximately 15 to 25 per cent (a saving of £10,000 to £25,000 per annum for a typical Series B audit).
Key Takeaways
- A finance operating system is a connected set of tools: accounting/ERP (the system of record), FP&A (planning and forecasting), expense management, payroll, treasury, and BI/reporting. Each layer has different tool requirements at different stages.
- Xero is the right ERP at seed and Series A. NetSuite or Sage Intacct is the right choice at Series B when multi-entity consolidation, IFRS 15 revenue recognition, or audit-grade controls are required. Do not implement NetSuite early; do not stay on Xero too long.
- The data warehouse is the integration layer that makes the stack coherent. API-first, warehouse-centric architecture avoids the fragility and maintenance cost of point-to-point integrations.
- Data governance is harder than technology selection. Chart of accounts consistency, master data management, and period-end cut-off policies must be defined before systems are connected, not after.
- The business case for finance systems investment rests on time saved (2 to 4 hours per week per 10 card users on expense management alone), error reduction, and audit fee savings of 15 to 25 per cent for a properly controlled ERP environment.
- Implement expense management tools (Pleo, Soldo, Airbase) at Series A or earlier. The ROI is immediate and the cost is low. There is no justification for a Series A company still processing expenses on paper receipts and spreadsheets.
- FP&A tooling at Series A can be Excel-based if well-structured. The case for a dedicated FP&A tool (Pigment, Mosaic) becomes compelling when the finance team is spending more than 2 days per month maintaining the forecast model rather than using it.
