An allowance system already structured but highly dispersed
In the State civil service, RIFSEEP combines the IFSE allowance linked to functions, constraints and expertise with an annual allowance linked to professional engagement and performance. The annual component can vary from zero to its ceiling and is not automatically renewed. [1]
What RIFSEEP already allows
The 2014 decree already includes rules excluding certain overlapping bonuses and transitional guarantees. Equality does not require identical bonuses for different functions: differences may be justified by responsibility, constraints or duties. Harmonisation should therefore be methodological rather than uniform. [1][2]
Harmonise rules rather than impose one bonus
Harmonisation should focus on a common taxonomy of function groups, comparable ceilings, publication of disparities, control of derogatory schemes and annual justification of supplements. Genuinely necessary special regimes can remain, but become explicit, capped and documented. [1][2]
Why €450 million requires individual-level data
The €450 million target requires a comprehensive base of allowances paid to covered populations. A cap by function group must be simulated, compared with current amounts, adjusted for transition guarantees and assessed for effects on recruitment and retention. Without that base, the number remains a policy target. [3][4]
Recruitment, responsibility and controlled exceptions
Uniform levelling would weaken the ability to recognise very different responsibilities and could multiply off-system schemes. The safeguard is a simple but sufficiently granular framework jointly overseen by Civil Service and Budget authorities, with published exceptions and costs. [2][3]
What must be demonstrated before retaining the 450 million euros per year target
Harmonising senior bonuses does not mean pretending every responsibility is identical
RIFSEEP structures a large part of allowance-based compensation around functions, constraints, expertise and professional commitment. [1] Harmonisation therefore should not mean paying a central director, prefect, technical specialist and other senior roles exactly the same bonus. The stronger objective is to make criteria, job groups, ceilings, amounts actually paid and exceptions comparable, so that similar differences in pay are supported by similar reasons.
The project should begin with a map of schemes and populations: base salary, IFSE or equivalent, variable components, benefits, individual guarantees and special contracts. DGAFP and INSEE data provide context, but savings require finer information at the upper end of the distribution. [3] [4] The site should therefore require aggregated data by job family, post and bonus band, then simulate alternative harmonisation rules without confusing a lower legal ceiling with a lower executed payment.
Legal control must respect equality principles: different treatment can be justified by objectively different situations or a relevant public-interest reason. [2] The financial model must also interact correctly with measure 1.15. The same reduction in a bonus cannot be counted once as an effect of harmonisation and again as an effect of the six-SMIC cap. The financial ledger should assign every euro to one measure and monitor circumvention through relabelling allowances or switching to contractual compensation.
Comparing bonus schemes requires a common language across administrations
Senior public-sector compensation may contain fixed, functional, variable and exceptional elements under different names across ministries and bodies. A cross-government reform therefore needs a mapping table that classifies each allowance by purpose: responsibility, expertise, mobility, performance, hardship or another clearly defined reason. Equivalent functions can then be compared and unexplained gaps identified. Without that normalisation, reducing one bonus can simply lead to compensation being recreated under a different label elsewhere in the pay package.
The reform target should be stress-tested through several scenarios rather than imposed uniformly. Options include caps by responsibility level, reductions in variable components, harmonisation across administrations or removal of obsolete allowances. Each scenario should show affected headcount, financial mass, cliff effects and recruitment or retention risks. Monitoring over several budget years then reveals whether the saving persists or is offset by other increases. The aggregate transparency infrastructure created under measure 1.14 becomes essential here because it can track the structure of compensation without unnecessarily publishing named individual salaries.
Normalise senior civil-service bonuses without flattening responsibility
Senior civil-service bonus schemes should be compared through functions and constraints that are genuinely alike. Job titles alone are insufficient: service size, budget responsibility, legal exposure, on-call requirements, management and technical complexity can justify differences. Reform should create a common set of factors and publish corresponding ranges, combining a function-related component with a variable component whose criteria are explicit. The objective is to remove opaque or duplicative schemes, not to pay every senior role the same amount.
Variable pay requires particular discipline. Objectives should be measurable, known before the assessment period and sufficiently independent to prevent bonuses becoming automatic. The review should identify threshold effects, legacy supplements and cases where several payments reward the same constraint. Any reduction must be tested for legal and recruitment effects: if it triggers compensating salary increases or greater reliance on more expensive contractors, the claimed saving disappears. Monitoring should therefore compare total remuneration, turnover, hard-to-fill vacancies and net savings after harmonisation.
Common audit method: double-counting controls, transition costs and budget reconciliation are centralised in the versioned budget-methodology register. For measure 1.20, those rules apply only to the flows and risks documented on this page; no saving is booked without executed baseline spending, an identifiable base and transferred costs deducted.
Open the technical appendix: evidence required before validating the costing
| Stage | Expected evidence | Timing | Treatment |
|---|---|---|---|
| Zero baseline | Executed expenditure, headcount, contracts, allowances, property and directly related resources | Before legislation | Publish |
| Avoidable cost base | Lines that genuinely cease, with date and legal basis | Impact assessment | Justify |
| Transition | Mobility, compensation, redistricting, IT, contracts and transfers | Year 1 | Separate from recurring |
| Transferred costs | Expenditure taken over by another administration or tier | Years 1–2 | Deduct |
| Net result | Recurring saving on a like-for-like basis with confidence level | After 12 stable months | Audit |