Simplified intersection fields at placement level for wages & rates and allowances
Non-relevant intersection fields for wages & rates and allowances are hidden at placement level, making data entry clearer and preventing synchronisation errors. F102477 | 2026-03
Introduction
When entering wages & rates and allowances at placement level in MSR, various intersection fields were available, such as collective agreement, function, contract phase, age from and pension indicator. These fields were passed during synchronisation to MSF as part of wage & rate and default worktype records.
In practice, however, these intersection fields at placement level turned out not to be functional: the default worktype object in MSF has fewer intersections than the wage & rate object, which could cause overlap errors for records with the same start date.
With this feature, the non-relevant intersection fields are hidden in the input screens at placement level. Only cost centre (and hour type for wages & rates) remain available. At other levels — such as general rates, account and project — there are no changes.
Who is this feature relevant for?
- Recruiters and mid-office staff who enter wages & rates and allowances at placement level
Benefits at a glance
- Clearer input screen: only the relevant fields are visible at placement level
- Reduced risk of synchronisation errors due to conflicting intersections in MSF
- Any historically filled intersection fields are ignored during synchronisation
Feature explanation
Wages & rates at placement level
- The following intersection fields are no longer visible when creating or editing a wage & rate at placement level: collective agreement, function, contract phase, age from and pension indicator.
- The fields cost centre and hour type remain available.
Allowances at placement level
- The function field is no longer visible when creating or editing an allowance at placement level.
- The field cost centre remains available.
Synchronisation to MSF
- If intersection fields at placement level are still populated (for example via a flow or existing records), these values are no longer synchronised to MSF.
Other levels (general rates, account, project)
- At all other levels, the intersection fields remain available unchanged. There are no functional changes outside placement level.
Setup / Implementation time
No additional configuration is required. The validations are active by default once the feature has been rolled out. Validation rules can be disabled if needed.
Other features in this release
🔗 Find all features from this release here