Using this guide
There are a large number of potential error messages within the numerous Paycircle integration events. We recommend using the search function while this article is open (Ctrl + F) to search for the error you're looking for more easily.
Where the error contains unique data (e.g., dates, pay element names) we recommend that you search for the portion of the error that comes after the unique data. This will improve your chances of finding the guidance you're looking for.
Address requires a minimum of two lines and the postcode so address has not been saved
Ensure that at least two lines of address have been entered against the employee record.
Post Code is invalid
Ensure that the Post Code assigned to the employee is a UK Post Code and does not contain any white spaces.
Email contained invalid characters which have been removed
Ensure that the email assigned to the employee is valid (e.g., [email protected]).
Email is invalid
Ensure that the email assigned to the employee is valid (e.g., [email protected]).
Title was blank or invalid so has been assumed based on gender
Ensure that a title is assigned to the employee, and that the title is one accepted in Paycircle.
Title cannot be replaced with a blank or invalid value
Ensure that a title is assigned to the employee, and that the title is one accepted in Paycircle.
Title is required
Ensure that a title is assigned to the employee, and that the title is one accepted in Paycircle.
Title is invalid
Ensure that a title is assigned to the employee, and that the title is one accepted in Paycircle.
Gender has been assumed based on the title
Ensure that a gender has been assigned to the employee, and that the gender is one that is acceptable in Paycircle.
Valid genders*:
Male
Female
*these are the genders currently recognised and accepted by HMRC.
Gender cannot be replaced with a blank or invalid value
Ensure that a gender has been assigned to the employee, and that the gender is one that is acceptable in Paycircle.
Valid genders*:
Male
Female
*these are the genders currently recognised and accepted by HMRC.
Gender is required
Ensure that a gender has been assigned to the employee, and that the gender is one that is acceptable in Paycircle.
Valid genders*:
Male
Female
*these are the genders currently recognised and accepted by HMRC.
{PropertyName} is required
Ensure that {PropertyName} has been assigned to the employee.
Note: {PropertyName} can be "First name", "Last name" or "Other names".
{PropertyName} cannot be replaced with a blank value
Ensure that {PropertyName} has been assigned to the employee.
Note: {PropertyName} can be "First name", "Last name" or "Other names".
{PropertyName} is invalid
Ensure that {PropertyName} has been assigned to the employee.
Note: {PropertyName} can be "First name", "Last name" or "Other names".
{PropertyName} cannot be replaced with an invalid value
Ensure that {PropertyName} has been assigned to the employee.
Note: {PropertyName} can be "First name", "Last name" or "Other names".
{PropertyName} contained invalid characters which have been removed
Ensure that {PropertyName} has been assigned to the employee.
Note: {PropertyName} can be "First name", "Last name" or "Other names".
Date of birth is required
Ensure a date of birth has been entered against the employee.
Date of birth cannot be replaced with a blank value
Ensure that a date of birth remains present on the employee record.
Date of birth cannot be in the future
Ensure that the date of birth has been entered correctly against the employee, and does not indicate a future date.
Employee cannot be over 130 years old
Ensure that the date of birth is not less than or equal to 130 years prior to todays date.
NI Number is invalid
Ensure the NI Number assigned to the employee is valid as per HMRC guidance.
NI Number contained invalid characters which have been removed
Ensure the NI Number assigned to the employee is valid as per HMRC guidance.
NI Number is already in use
Ensure the NI Number is not in use on a different employee record.
Department not found
Resolve in Paycircle by creating the department assigned to the employee in PeopleHR and then retrying the event.
A team member already exists with this Employee ID
No resolution required.
Subsequent integration events for the impacted employee record will still process because the records are linked via the Employee ID, which is unique.
New starters must be added into PeopleHR first and sent via integration, rather than being created in Paycircle manually, in order to avoid this error.
Additional context:
This can happen when an employee is created outside of the expected integration flow, for example creating the employee manually in Paycircle first, rather than sending them through from PeopleHR.
This will cause the Paycircle integration handler to fail for this message because the employee already exists and can't be created again.
There is no team member matching this Employee ID
Manually create the team member record in Paycircle and contact the Paycircle support team so that they can trigger the reprocess of the other integration events for that particular employee.
If this error appears, but the team member record appears correctly in PeopleHR and Paycircle, the Support team will contact the Engineering team for further investigation.
Employee ID does not match the existing team member
Manually update the information in Paycircle so that the records match in the 2 systems.
Example
Employee Abby Clarke has the Employee ID PW22 in PeopleHR and the Payroll ID PW21 in Paycircle (it was manually updated in Paycircle).
If in PeopleHR you'd change the Employee ID from PW22 to EMP22, this error message would appear on Paycircle side, because it can't find the employee record.
Payroll company cannot be changed via integration
The process of moving an employee from one company to another is not supported by the integration and should be actioned manually.
If the payroll company was changed in error in PeopleHR, this can be switched back to the initial payroll company. You would still get this error message initially, but the subsequent integration will work process correctly.
Missing value: Account number
Ensure the account number has been entered for the employee.
Account number should consist of 8 digits
Ensure the account number against the employee is exactly 8 numbers.
Account number contained invalid characters which have been removed
Ensure the bank account did not contain non-numeric characters.
Missing value: Sort code
Ensure the sort code has been entered for the employee.
Sort code should consist of 6 numbers
Ensure the sort code entered against the employee is exactly 6 numbers.
Sort code contained invalid characters which have been removed
Ensure the sort code entered against the employee does not contain non-numeric characters.
Team member not found
Manually create the team member record in Paycircle and contact the Paycircle support team so that they can trigger the reprocess of the other integration events for that particular employee.
If this error appears, but the team member record appears correctly in PeopleHR and Paycircle, the Support team will contact the Engineering team for further investigation.
Team member bank details not found
Raise a support ticket for further investigation. The support team will reach out to the development team to review.
Address requires a minimum of two lines and the postcode so address has not been saved
Ensure that at least two lines of address and the post code have been entered against the employee record.
Address requires a minimum of two lines and the postcode
Ensure that at least two lines of address and the post code have been entered against the employee record.
Postcode is invalid
Ensure that the Post Code assigned to the employee is a UK Post Code and does not contain any white spaces.
Leave date added in the past. You may wish to review the Year to date figures for the current tax year and update them as required.
Advisory only. You may wish to check that the leave date assigned to the employee is correct.
Leave date cannot be before start date
Ensure that the leave date is not before the start date of the employee
Leave date can be up to 3 months after the pay date for your current pay period
The leave date has been assigned to the employee more than 3 months in advance, which is not accepted by Paycircle validation but is not restricted in PeopleHR.
The following options are available:
Enter the leavers with their leave date up to 3 months after the current period pay
Edit the date that they entered in leaver wizard so that it fits 3 months rule from Paycircle
FinalEmploymentDate date is invalid
This validation is put in place just to make sure that Paycircle only accepts valid dates (e.g., reject dates like 30/02).
Although PeopleHR has its own validation rules, Paycircle side validation has been included as a safety net.
If the format is correct, but this error message is received, raise a support ticket for further investigation. The support team will reach out to the development team to review.
IntegrationEvent is null
Raise a support ticket for further investigation. The support team will reach out to the development team to review.
Salary cannot be empty
Ensure the salary value has been assigned to the pay record.
Salary cannot be less than 0
Ensure the salary value has been assigned to the pay record and is a number greater than 0.
Effective date cannot be before the minimum salary effective date
Ensure the salary record does not have an effective date before the earliest pay record the employee has.
New salary cannot be empty
Ensure the salary value has been assigned to the pay record.
New salary cannot be less than 0
Ensure the salary value has been assigned to the pay record and is a number greater than 0.
Original salary effective date is not set
Ensure the pay record has an effective date assigned.
Existing salary change not found
Salary records rely on matching effective dates to update via integration - this error can appear when salary effective dates in PeopleHR and Paycircle do not match.
Raise a support ticket for further investigation. The support team may reach out to the development team to review.
{IntegrationEvent.Event.PayElementName} pay element already exists
Check if the team member has this pay element on their profile in Paycircle as well as PeopleHR. If the element is in both places, delete this element from the team member in both Paycircle and PeopleHR, and then recreate in PeopleHR.
{IntegrationEvent.Event.PayElementName} pay element already exists with the same name
Check if the team member has this pay element on their profile in Paycircle as well as PeopleHR. If the element is in both places, delete this element from the team member in both Paycircle and PeopleHR, and then recreate in PeopleHR.
{IntegrationEvent.Event.PayElementName} pay element could not be found
Ensure that an element with an exact matching name in Paycircle exists. If the element doesn't exist, create it and then retry the event.
Only fixed value pay elements can be created
Double check your data in PeopleHR to ensure the value entered is correct.
Unsupported event type {Event.GetType().Name}
Recreate the change in PeopleHR and ensure that the pay element being assigned/amended exists with the same name in Paycircle.
Current pay period not found
Return to PeopleHR and check that the effective date aligns with the current period.
{(IsOneOff? "Payment" : "Effective From")} date was not provided
Ensure an effective date is assigned to the record in PeopleHR.
The {effectiveDateInterpolationString} date of {EffectiveFrom.Value.ToDateString()} doesn't fall in a valid pay period
Ensure the entitlement/deduction in PeopleHR is correct. You may need to delete and recreate the entitlement/deduction record if you can't see any issues with the dates.
{Type} sent with an effective date in the past so it will become effective from the start of the current pay period
Paycircle does not currently support backdated payments for entitlements/deductions, so if an event is received with a historic date, it will become effective from the start of the current period.
{Event.PayElementName} pay element does not exist
Ensure that the pay element named in the error exists with the same name in Paycircle. This may also indicate a mapping issue, so if the element exists on the team member in Paycircle, remove it from both Paycircle and PeopleHR and then recreate the entitlement / deduction in PeopleHR to send over new event and trigger the mapping.
Multiple {Event.PayElementName} pay elementsfound with the same ID
This can occur when occur when multiple elements share the same ID. You may need to delete the elements and recreate them in PeopleHR to activate the mapping.
{Event.PayElementName} pay element is not set as recurring
Double check that the associated record in PeopleHR is set as a recurring element in the correct area. One off payments and deductions should be created via the logbooks area.
{payElementType} sent with no effective date. The pay element was created in the past so it will become effective from the start of the current pay period
This issue occurs when an effective date is not sent through within the update event. However, as the element has been used historically, it will become effective from the start of the current period. If you do not want this to happen, you will need to delete and recreate the payment record in PeopleHR with the correct effective date.
{Type} sent with an effective date in the future so it will become effective from the start of the current pay period
Updates to entitlements and deductions are intended for current period changes, so if you're making a change for a future period, you will need to either:
Delete and recreate the entitlement / deduction in PeopleHR with the correct effective date
Wait for the relevant period to become the current period before making the change in PeopleHR.
The effective pay period for the {payElementType} cannot be updated as it was originally created in a future pay period but the update is for a previous pay period
Double check the dates of the associated record in PeopleHR. You cannot correct an element from a previous pay period to a future pay period.
The effective date of {EffectiveFrom.Value.ToDateString()} doesn't fall in a valid pay period
Double check that the dates entered into PeopleHR are correct and associated with a valid pay period. You may need to delete and recreate the entitlement / deduction to resolve this issue.
Could not find {IntegrationEvent.Event.PayElementName} pay element
Check that the pay element exists in Paycircle with the same name as sent from PeopleHR. If the element does not exist, you will need to create it. If the element does exist, check the team member and if the element is already assigned to them, remove the element from their record and then delete and recreate the associated record inside of PeopleHR.
{IntegrationEvent.Event.PayElementName} pay element cannot be updated
This indicates an error with the data in the update event. Check that the data is correct in PeopleHR.
{IntegrationEvent.Event.PayElementName} pay element cannot be deleted
Check the data is correct in PeopleHR. If it is correct, the issue may be due to missing mapping - you may need to delete the pay element manually in Paycircle.
Another {userPayElementHR.UserPayElementLabel} pay element already exists with the same ID
You may have multiple Pay Elements (e.g. Bonus). they all should have their own ID but if the user has come across an error where they have the same ID. You may need to delete the elements and re-create them in PeopleHR to re-do the mapping.
An effective from date was not provided
Ensure an effective date has been applied to the associated record within PeopleHR.
{Type} sent with a payment date in the past so it will become effective from the start of the current pay period
Paycircle does not currently support backdated payments for entitlements/deductions, so if an event is received with a historic date, it will become effective from the start of the current period.
Amount should not be equal to 0
You cannot create a zero value payment. Correct the data in PeopleHR to ensure the value is not zero.
Could not find {IntegrationEvent.Event.PayElementName} pay element by ID
This error indicates that the pay element may not exist. Go into the team members profile and double check that they have the pay element in Paycircle and PeopleHR.
You may need to do one or more of the following:
Create the element in Paycircle.
Update the pay element in Paycircle to ensure it has the same name as PeopleHR.
Remove the pay element from the team member in both Paycircle and PeopleHR and then recreate the record in PeopleHR.
{IntegrationEvent.Event.PayElementName} pay element (One-Off) is set as recurring
One off payments must be created via the logbooks and not via any other method. Check in PeopleHR that the payment has been created in the correct location.