Overview
Shared costs are a fact of every organisation above a certain size. Central IT infrastructure serves every department. Facilities costs are consumed by every team in the building. Shared services — HR, legal, finance, procurement — provide value across business units that do not directly bear their costs. Management overhead allocates to the entities that benefit from it. Without a systematic, documented allocation process, these shared costs either sit undistributed in central cost centres — obscuring the true cost of each business unit or department — or are distributed through manual calculations that are inconsistent, difficult to audit, and time-consuming to maintain as the organisation changes.
Cost allocation software automates the distribution of shared costs according to defined allocation bases and rules — applying the logic consistently across every allocation period, producing the allocated cost view that management reporting and profitability analysis depend on, and maintaining the documentation that internal audit and regulatory compliance may require. The finance team defines the allocation methodology. The system applies it.
We build custom cost allocation software for controlling functions, group finance teams, and management accounting operations that need allocation logic specific to their organisation's cost structure, entity hierarchy, and reporting requirements — rather than the allocation functionality embedded in a general ERP or planning tool that cannot represent the complexity of how shared costs actually flow through the organisation.
What Cost Allocation Covers
Direct and indirect cost separation. The starting point of any allocation model is understanding which costs are directly attributable to a cost object — a department, a product, a project, a customer — and which are indirect, requiring allocation. Cost allocation software maintains the separation between direct and indirect costs explicitly, ensuring that the allocation process adds indirect costs to the cost objects that consume them without displacing the direct costs that are already attributed.
Allocation bases. The basis on which a shared cost is allocated determines how accurately the allocation reflects actual consumption. IT infrastructure costs allocated by number of users. Facilities costs allocated by floor space. Shared HR costs allocated by headcount. Finance function costs allocated by revenue or transaction volume. Each allocation base reflects a different theory of cost causation — the cost allocation system supports multiple bases applied to different cost pools, with the basis for each allocation documented and auditable.
Allocation bases are configured per cost pool and per period — updated when headcount changes, when floor space changes, when the organisational structure changes — with the history of base values preserved so that prior period allocations can be recalculated or validated against the bases that were in effect at the time.
Step-down and reciprocal allocation. Simple allocation models distribute shared costs from service departments directly to the business units that consume them. More accurate models recognise that service departments also consume each other's services — the HR department uses IT infrastructure, the IT department uses facilities. Step-down allocation processes service departments in a defined sequence, allowing each department's costs to be allocated including the shared service costs they have already received. Reciprocal allocation solves the simultaneous equations that result from mutual service consumption between departments, producing the most theoretically accurate allocation of shared costs.
We implement the allocation methodology — direct, step-down, or reciprocal — appropriate to the organisation's requirements and the level of accuracy that management reporting demands.
Multi-level allocation. In complex organisations, costs flow through multiple allocation levels before reaching the final cost objects. Group overhead allocates to business units. Business unit overhead allocates to departments. Department overhead allocates to projects or products. Each level of allocation adds the costs from above to the cost base of the receiving entity before that entity's costs are allocated further. Multi-level allocation models are difficult to manage in spreadsheets — the interdependencies between allocation levels mean that a change at one level ripples through all downstream levels. Built into a dedicated allocation system, multi-level allocation is calculated correctly and consistently.
Intercompany allocation and transfer pricing. In group structures, shared costs are not just allocated between departments but between legal entities — management fees charged by the holding company to subsidiaries, shared service charges between group entities, IT infrastructure costs recharged from the entity that operates the infrastructure to the entities that use it. Intercompany allocations need to reflect the group's transfer pricing policy, produce the accounting entries in both the charging and receiving entities, and be eliminated in the group consolidation.
Project and activity-based costing. Organisations that manage costs by project or activity need allocation logic that assigns shared costs to projects based on the resources each project consumes — hours worked, materials used, shared infrastructure consumed. Activity-based costing models that allocate to projects or products based on activity drivers rather than simple volumetric bases produce more accurate cost information for pricing, profitability analysis, and project evaluation.
The Allocation Process
Period processing. Cost allocation runs on the reporting period schedule — monthly for management reporting, quarterly for certain regulatory purposes, annually for statutory reporting. Each period run extracts the cost pool balances from the source system, applies the allocation bases for the period, calculates the allocated amounts, and produces the allocation output — the journal entries that post allocated costs to the receiving cost objects, and the allocation report that shows the calculation.
Base data collection. Allocation bases need to be current for the period being allocated. Headcount figures for the current month, floor space figures reflecting the current office configuration, revenue figures for the current period. Some bases are stable and rarely change. Others change frequently. The allocation system manages the collection and version control of base data, with workflow for submission and approval where base data is collected from across the organisation.
Calculation and validation. The allocation calculation applies each allocation rule to the cost pools in the configured sequence, distributing costs to receiving cost objects according to the basis weights. Calculation validation confirms that total allocated costs equal total source costs — that the allocation is complete and no costs are lost or duplicated in the process. Validation failures surface before the allocation output is posted rather than after.
Journal generation. The output of the allocation process is the set of journal entries that post allocated costs to the receiving cost objects in the financial system. Journal generation produces entries in the format the financial system requires — account codes, cost centre codes, entity identifiers, amounts, and the allocation reference that links the journal to the allocation run that produced it. Journals are reviewed and approved before posting rather than posted automatically, with the allocation report providing the supporting documentation.
Retrospective adjustment. When base data is corrected after an allocation has been run — a headcount figure that was submitted incorrectly, a floor space measurement that changed — the allocation needs to be recalculated and the adjustment posted. Retrospective adjustment capability allows prior period allocations to be recalculated with corrected bases and the adjustment journals produced without rebuilding the allocation from scratch.
Reporting and Transparency
Allocation reports. Every allocation run produces a report showing the full calculation — the source cost pool, the allocation basis, the basis weights for each receiving cost object, the allocated amount, and the receiving account and cost centre. Allocation reports are the documentation that internal audit, external audit, and transfer pricing review require — showing that the allocation was calculated as the policy specifies and applied consistently.
Cost centre P&L including allocations. The management P&L for each cost centre, department, or business unit showing direct costs alongside allocated shared costs — giving budget owners the full cost picture including the overhead that the organisation's allocation policy assigns to them.
Allocation basis history. The history of basis values used in each period's allocation — headcount at each allocation date, floor space at each allocation date, revenue figures at each allocation date. Basis history provides the evidence for retrospective queries and the data for trend analysis of how allocation bases are changing over time.
Sensitivity analysis. What would the allocation have been if a different basis had been applied? What is the cost impact on each business unit of a proposed change to the allocation methodology? Sensitivity analysis tools allow the finance team to model allocation methodology changes before implementing them and to quantify the cost impact on each recipient.
Integration Points
Exact Online. Cost pool balances extracted from the Exact Online general ledger by account and cost centre. Allocation journal entries generated in the format Exact Online requires and uploaded via the API. Allocation reference data stored in Exact Online dimensions for cost allocation reporting within Exact Online's reporting layer.
AFAS. Cost centre actuals from AFAS used as cost pool inputs. HR data from AFAS — headcount, FTE — used as allocation bases for HR-driven allocations. Journal entries posted to AFAS via the REST API.
Twinfield. General ledger balances from Twinfield as cost pool sources. Allocation journals posted to Twinfield in the dimension structure that Twinfield's reporting uses.
SAP. Controlling module cost centre balances as allocation inputs. Internal order and profit centre allocations integrated with SAP's assessment and distribution cycle logic. Allocation journals posted via SAP's RFC or API interfaces.
HR systems. Headcount and FTE data from HR systems used as allocation bases — updated automatically when headcount changes rather than requiring manual base data entry.
Facilities management. Floor space and occupancy data from facilities management systems used as allocation bases for space-based cost pools.
Technologies Used
- Rust / Axum — high-performance allocation calculation engine, large cost pool processing, journal generation
- C# / ASP.NET Core — financial system integration, complex allocation logic, Excel import and export, journal formatting
- React / Next.js — allocation management interface, basis data input, allocation reports, cost centre P&L views
- TypeScript — type-safe frontend and API code throughout
- SQL (PostgreSQL, MySQL) — allocation model storage, basis history, allocation run history, journal archive
- Redis — allocation job queuing, period processing coordination
- Exact Online / AFAS / Twinfield / SAP — cost pool extraction and journal posting integration
- OpenXML / EPPlus — Excel-based allocation reports and basis data import
- REST / Webhooks — financial system integration for cost data extraction and journal delivery
Allocation Accuracy and Its Business Consequence
Cost allocation accuracy matters because management decisions are made on the cost information that allocation produces. A business unit whose costs include a disproportionate share of shared overhead appears less profitable than it is. A product whose fully loaded cost is calculated from an allocation model that does not reflect actual resource consumption is priced on incorrect information. A transfer price that does not reflect the cost of the services being provided creates tax and regulatory risk.
These are not abstract concerns. They are the practical consequences of allocation models that are inaccurate, inconsistently applied, or not maintained as the organisation's cost structure changes. Custom allocation software that implements the allocation methodology correctly, applies it consistently, and maintains the documentation of how it was applied addresses these risks directly.
Allocation That the Organisation Can Stand Behind
Cost allocation is one of the areas of management accounting where the methodology is most visible to scrutiny — from internal audit, from tax authorities in transfer pricing reviews, from business unit managers who question why their allocated overhead has changed. Allocation software that produces documented, auditable, consistently applied allocations gives the finance team the confidence to present allocation results and the evidence to defend them.