Fully Loaded FTE Cost: Formula, Example, and Common Mistakes

If you are trying to understand product profitability, customer profitability, or make-or-buy decisions, one number matters more than most finance teams admit: the fully loaded FTE cost. Salary alone is not enough. If you only use gross salary in your model, you will systematically understate the true cost of product work, support work, and internal capacity.

This guide shows how to calculate fully loaded FTE cost, what to include, what to exclude, and how to turn the number into a useful cost-allocation input without falling back to time-tracking. For European readers, the key mindset shift is simple: think in total employer cost, not just salary.

What fully loaded FTE cost actually means

Fully loaded FTE cost is the annual cost of one full-time equivalent once you include the costs that make that person employable and productive.

At a minimum, that usually includes:

Base salary
Employer social contributions and statutory on-costs
Benefits, pension, bonuses, and other contractual extras
Equipment and software (licences)
Training, travel, and other enablement costs
A fair share of shared overhead

The purpose is simple: finance wants a cost figure that reflects reality, not just compensation. If an engineer earns EUR 85K but also requires employer social contributions, pension contributions, software licences, a laptop, management support, office cost, and HR/admin support, the true employer cost is materially higher than EUR 85K.

The simple formula

Use this structure:

Fully loaded FTE cost = direct people cost + enablement cost + allocated overhead

Where:

Direct people cost = gross salary + employer social contributions + pension + benefits + variable compensation
Enablement cost = software + equipment + training + travel + workspace
Allocated overhead = HR + finance + legal + leadership + general operating overhead

This does not need to be perfect on day one. It needs to be consistent enough to support better decisions than salary-only guessing.

In many European organisations, this is very close to what finance teams already call employer cost, employment cost, or fully loaded personnel cost. The terminology varies by country; the principle does not.

Worked example

Imagine a product engineer with the following annual costs:

Base salary: EUR 85,000
Employer social contributions and statutory on-costs: EUR 15,500
Pension, bonus accrual, and other benefits: EUR 9,500
Laptop, software, and tooling: EUR 4,000
Training and travel: EUR 2,000
Allocated shared overhead: EUR 14,000

That yields:

Direct people cost: EUR 110,000
Enablement cost: EUR 6,000
Allocated overhead: EUR 14,000

Fully loaded FTE cost: EUR 130,000 per year

That is the number finance should use when allocating cost to products, customers, or internal initiatives. Not EUR 85,000.

In a European context, the exact mix behind this number will differ by country. Germany, France, the Netherlands, the Nordics, and Southern Europe all structure employer charges a bit differently. Some organisations also include items such as holiday pay, a 13th salary, meal vouchers, or employer pension contributions. The important thing is not using one universal percentage. The important thing is applying one consistent method inside your own company.

What to include and what to avoid

The most common problem is not missing math. It is inconsistent scope.

Include

Costs that scale with employing and enabling a person
Country-specific employer social charges and statutory employment costs
Recurring contractual extras such as employer pension, holiday pay, or 13th-month salary where applicable
Shared support functions that make delivery possible
Overhead drivers that can be applied consistently across teams

Avoid

Double-counting management if leadership costs are already part of shared overhead
Mixing one-time restructuring costs into recurring FTE cost
Treating fully loaded cost as if it were the same for every role level
Mixing recoverable VAT into internal personnel cost calculations
Using day-level timesheets to simulate precision you do not actually have

If your finance model includes executive leadership, finance, recruiting, and office cost in an overhead pool, do not add those same items again at the team level.

One practical European note: VAT is usually not part of internal personnel cost unless it is genuinely irrecoverable for your organisation. Otherwise, it belongs in procurement/accounting treatment, not in your FTE base cost.

The real mistake: confusing cost with allocation

Knowing fully loaded FTE cost is only half the job. The second question is where that cost should land.

That is where many teams reach for timesheets. But most of the time, what you really need is not a log of every hour. You need a defensible view of capacity allocation.

For example:

A staff engineer may spend 50% on Product A, 30% on platform work, and 20% on shared architecture
A support lead may spend 70% on enterprise customers and 30% on onboarding
A product operations role may support three business lines in fixed quarterly proportions

Once you know the fully loaded annual cost of the role owner, you can allocate that cost using stable capacity shares instead of chasing weekly timesheets.

If that is the problem you are solving, read How to Calculate Product Costs Without Timesheets. It is the companion piece to this article.

How finance teams can use this number

Fully loaded FTE cost becomes useful when it supports actual decisions, such as:

Product profitability: Which product absorbs the most engineering and support cost?
Customer profitability: Which accounts consume disproportionate delivery capacity?
Make-or-buy decisions: Is an external vendor actually cheaper than internal capacity?
Headcount planning: What is the true budget impact of adding 3 FTE instead of 2?
Reorg scenarios: What happens to cost structure if a shared platform team is split?

The mistake is to calculate the number once and leave it in a finance deck. The better approach is to connect it to a living model of roles, teams, and allocation rules.

Why role-based allocation works better than time-tracking

If people already work across explicit roles or circles, the organization already has a better cost-allocation model than most timesheet systems.

With role-based allocation, finance can answer:

Which roles support Product A?
How much capacity is allocated to that product this quarter?
What is the fully loaded cost of the people holding those roles?
Which shared-service costs should be spread across products or customers?

This turns fully loaded FTE cost into a strategic metric instead of a payroll footnote.

Keyroles is built around exactly that kind of structure: roles, circles, and capacity shares that stay current as the organization changes. For the product-costing side of the workflow, see Profitability Mapping & Cost Allocation.

FAQ

What is the difference between salary and fully loaded FTE cost? Salary is only direct cash compensation. Fully loaded FTE cost includes gross salary plus employer social contributions, pension, benefits, tooling, enablement, and a share of overhead.

Should every employee have the same fully loaded FTE cost? No. Seniority, benefits, bonus plans, tooling costs, geography, and overhead treatment all differ. A company can still use blended averages when speed matters, but it should know that it is simplifying.

Do I need timesheets to calculate fully loaded FTE cost? No. Fully loaded FTE cost is a cost basis, not a time log. Timesheets are only relevant if you also need task-level or client-billing allocation. For product and internal profitability, capacity allocation is often enough.

Should fully loaded FTE cost be monthly or annual? Usually annual first, then converted into monthly or daily views for planning. Annual is easier because taxes, bonuses, and overhead are often budgeted that way.

What tends to differ most across European countries? Usually the biggest differences are employer social contributions, pension rules, statutory leave treatment, and contractual extras such as holiday pay or a 13th salary. That is why copied benchmark percentages are risky. Your own payroll and finance data is the better source.