Validations for error-free synchronisation to MSF

Introduction

The synchronisation from MSR to MSF is an essential part of the platform, but occasionally failed due to data quality issues that could have been caught at the point of entry. Examples include a phone number containing letters, a missing invoice email address or an end date that falls before the start date.

With this feature, validations are added in MSR. When a user saves data that cannot be synchronised, they immediately receive a clear error message. This resolves the issue at the source — rather than only discovering it when a synchronisation fails.

Who is this feature relevant for?

This feature is relevant for:

Customers who use the MSR to MSF synchronisation and therefore have the Combi package installed.
Recruiters and mid-office staff who enter candidate, account, placement and vehicle data.
Application administrators who want to reduce sync errors and ensure data quality.

Benefits at a glance

Fewer synchronisation errors through direct blocking of invalid input
Clear error messages at the point of saving, so users can take immediate action
Better data quality in both MSR and MSF

Feature explanation

Account

Phone number: may not contain letters. Digits, spaces, + and - are permitted. Validation active when synchronisation to MSF is enabled.
Invoice email: required when the billing method is set to Email and the account status synchronises to MSF. Validation active when synchronisation to MSF is enabled.

Contact (candidate and contact person)

House number: the house number (derived from the Street field) may not be longer than 5 characters. Validation active when synchronisation to MSF is enabled.
Date of birth: may not be in the future. Validation always active.
Employment start date / Employment end date: the end date must be equal to or later than the start date, if the end date is filled in. (validation rule, active by default)

Placement

Dates: the end date must be equal to or later than the start date, if the end date is filled in. (validation rule, active by default)

Price agreement line

Work type and Hour type: both fields may not be filled in simultaneously. Validation always active.

Vehicle

Type: the value may contain a maximum of 30 characters. Validation active when vehicle synchronisation is enabled.
Licence plate: the licence plate must be unique within the organisation. Validation active when vehicle synchronisation is enabled.

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