Your finance team is spending three days a month assembling management accounts from six spreadsheets that don't agree with each other.

Off-the-shelf FP&A platforms are built for the general case. They work well when your planning structure, chart of accounts, and reporting hierarchy fit their data model. When your business has a complex management reporting structure that does not map cleanly to the standard dimensions, entity hierarchies that don't match how the platform models organisations, or calculation logic that requires workarounds the platform was not designed for, the implementation cost and ongoing maintenance burden of a SaaS platform can exceed the cost of building something that fits exactly. The other case for custom is integration depth. Anaplan and Adaptive integrate with common ERP systems, but the mapping work between your general ledger codes and your management reporting structure requires significant configuration in any platform. Custom financial software encodes those mapping rules directly into the data model, so there is no translation layer to maintain. That said, we do not recommend custom by default. If your requirements are standard and the SaaS platform fits, buy the SaaS platform. We tell you which one fits before you commit to building anything.

Integration complexity depends on your ERP and what data you need. NetSuite, Xero, and QuickBooks have well-documented REST APIs and the integration work is straightforward, typically 2-4 weeks including data mapping and testing. Microsoft Dynamics 365 Finance and Oracle ERP Cloud have more complex APIs and require more mapping work, 4-8 weeks. SAP S/4HANA and SAP ECC integrations range from straightforward via RFC function modules to complex depending on which modules you use and whether your system is heavily customised, 4-12 weeks. The mapping work is where most time goes: translating your general ledger account codes and cost centres into your management reporting structure requires documented logic, and that logic usually lives in someone's head or in a spreadsheet. We extract and document that logic as part of the integration design phase so it is auditable and maintainable, not embedded in a formula chain.

Multi-entity consolidation requires eliminating intercompany transactions (sales between entities within the group), translating subsidiary financials from local currency to presentation currency using the correct rate (closing rate for balance sheet, average rate for income statement, historical rate for equity), and calculating minority interest where you do not own 100% of a subsidiary. In practice, most consolidations at $10M--$200M businesses run in a spreadsheet that someone updates at month end, pulling trial balances from multiple ERP instances, applying elimination journals manually, and reconciling the result. The process takes 2-3 days and requires the same person every month because no one else knows how the spreadsheet works. We replace that process with software that pulls trial balances from each ERP instance, applies your defined elimination rules and currency translations automatically, flags intercompany mismatches for review, and produces the consolidated accounts in your configured template. The finance team reviews the output and approves exceptions, they do not build it. We support IFRS and US GAAP consolidation rules.

A focused FP&A system covering budget entry, driver-based forecasting, and budget-vs-actuals reporting for a single entity typically runs $40,000--$65,000. Management accounts automation for a single entity with one ERP integration runs $35,000--$55,000. Multi-entity consolidation with two to five ERP sources and currency translation runs $60,000--$95,000. Treasury and cash management with bank connectivity and FX exposure tracking runs $45,000--$80,000. A full finance software suite covering FP&A, management reporting, consolidation, and treasury integration for a mid-size multi-entity business runs $90,000--$120,000. These ranges widen with the number of entities, the complexity of ERP integrations, and the extent of AI features. We assess your current process, data sources, and reporting requirements before pricing. Every project is fixed cost.

Three AI applications have clear ROI in financial software. Variance commentary generation: rather than a finance analyst writing 'revenue was $200K below budget due to lower volume in the enterprise segment,' an AI layer reads the variance in the data, identifies the contributing factors, and drafts the commentary in your preferred format. The analyst reviews and edits rather than starting from a blank page. Anomaly detection in financial data: an AI model trained on your historical financial patterns flags transactions, journal entries, or balance movements that fall outside expected ranges, catching errors and fraud signals earlier than a monthly review. Forecast model improvement: AI identifies which drivers in your historical data have the strongest correlation with outcomes, improving the accuracy of driver-based forecasts in the FP&A system. We scope AI features separately and add them to the base system once the underlying data layer is sound. AI on bad data produces wrong answers confidently, so we get the data foundation right first.

Financial software sits on sensitive data and needs controls from the start, not retrofitted later. Role-based access control: finance directors see consolidated group P&L; business unit heads see only their entity; AP clerks see invoice queues, not balance sheet data. Every permission set is defined in the design phase and enforced at the API layer, not just the UI. Audit trail: every data change, journal entry, approval action, and exception override is logged with timestamp, user identity, and the previous value. This is not optional for financial software. It is the record that answers an auditor's question about why a number changed. Data residency: if your business operates in the UK or EU, financial data stays in the configured region. We design the infrastructure for the residency requirements your auditors and regulators expect. Encryption at rest and in transit on all financial data as a baseline. We walk through the control framework with your finance and IT teams during the design phase so the software passes internal audit review.

A focused single-scope project, management accounts automation for a single entity, or an FP&A system for one business unit, typically runs 10-14 weeks from project start to go-live. Multi-entity consolidation or a full finance suite runs 14-20 weeks depending on the number of ERP integrations and the complexity of the reporting structure. The timeline breaks into three phases: design and data mapping (3-4 weeks), where we document the reporting requirements, map the general ledger to management structure, and design the data model; build and integration (5-10 weeks), where we build the system, connect the integrations, and load historical data; and testing and parallel run (2-4 weeks), where the finance team runs the new system alongside the existing process to validate the numbers before switching. We do not skip the parallel run. The point at which finance trusts the system is when they have seen it produce the same numbers as their manual process three months in a row.