Your UX is waiting ...interact, engage, explore in Las Vegas at CloudWorld 2023

Learn more
UK Payroll - FPS Errors - How do customers prevent 'bad data' at source? — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

UK Payroll - FPS Errors - How do customers prevent 'bad data' at source?

Received Response



Over many pay periods have found numerous errors/warnings on the FPS file which is often too late and at a crunch point which is not helpful to highlight our data 'is not valid'.

It's a shame a UK instance of payroll doesn't allow a customer to apply 'validation at source' profile setting which polices these types of issue but it looks like each customer needs to add appropriate validation to each of the items below, e.g. autocomplete, mandatory fields etc

Content (required):

Anyone else experienced any of the failures below, be interesting how customers to try prevent these to stop them occurring? Is there any documentations of what the FPS requirements are e.g. what do they define as a valid character, where would it say middle name can't exceed 35 characters for example so we can add these requirements to the UI to prevent issues later in the payroll cycle:

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!