Import Errors and Explanations

001

Placement with ID [X] has existing shifts outside its date range

[shifts: 15/12/2016 to 15/12/2016, placement: 18/12/2016 to 25/12/2016]

When you change a placement the date range must include all existing shifts. In this example a timesheet has been submitted for the 15th Dec which is outside of the date range of the Placement. You will need to extend the date range of the Placement so that the timesheet date is included e.g. change the Placement date range to 15/12/2016 to 25/12/2016. If the timesheet should not be included then you will need to revert the timesheet.

002

Found more than one existing client with frontend ref aaaaaa

Reason 1

The Placement on InTime has Client Ref of aaaaaa but the import file has a Client Ref of bbbbbb i.e. the reference codes are different. The error is caused because the import is trying to move the Manager to a different client which is not allowed. To resolve the issue update the Client in Salesforce to have the same reference as InTime.

Reason 2

Client RefCode generator has been enabled. If it has this would cause an ItrisId to be assigned to the Client on import rather than applying the one from the import file. As the generator does not increment from an import the next Client would be assigned the same ItrisId. This is likely to be a rare occurrence. Request the support team (support@in-time.co.uk) check this.

003

Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1

See also Error 005 below

004

Cannot change client from X to Y - changing the client of an existing placement is not allowed

The import is trying to change the Client of an existing Placement to a different Client. This is not allowed. Review/amend the import file and rerun the import

005

Could not execute JDBC batch update

Reason 1

Check the BANK ACCOUNT NAME. If it is more than 30 chs long then amend the account name and re-import. If the account name is 30 chs or less then log a call with support (support@in-time.co.uk) to investigate further.

Reason 2

Case 55361

006

Error validating Worker (The field com.ipfour.intime.model. Worker.email cannot be null.)

Please ensure that you always have an email for a worker as it is mandatory for InTime. We suggest that your front-office system should enforce this field, either on entry or before export to InTime.

007

Existing manager with ref XXXXXX belongs to a different Client: YYYYYY

The Manager XXXXXX is already linked in InTime to Client YYYYYY. You will need to create a new account in Salesforce for the Manager and associate this account with the Placement you are importing

008

Currency not specified so setting to agency default value

009

Error validating Worker (Bank A/C Name, Number and Sort Code must be specified if paying by BACS)

If a worker is setup to be paid via BACS then the Bank details must be entered including Bank A/C Name, Number and Sort Code.

010

Placement with ID [CIS12940] - Error creating bean with name 'uk.co.revas.intime.invoicing.BankAccount': Initialization of bean failed; nested exception 

If the Placement has not successfully imported then log a case with Support via support.in-time@rsmuk.com otherwise ignore.

011

Error validating Worker - Worker date of birth cannot be blank

Update the Worker details and rerun the import.

012

Placement with ID [UMB8828] has an invalid PlacementTimesheetPeriod field. It is set to 'fortnightly'. Was expecting one of these values: [list of various system defined values]

Amend the Placement timesheet period to one of the listed values and re-import

013

Placement with ID [ORC11068] - Payroll employee update failed  for Worker Name (CS0011068) Payroll response: System.Web.Services.Protocols.SoapException: Transaction (Process ID 206) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.   at WebServices.Employee.UpdateEmployeeFullV4(String ticket, Int32 CompanyID, EmployeeV3 oEmployeeModel, EmployeeTax oEmployeeTaxModel, EmployeeNI oEmployeeNIModel, EmployeeBankV2 oEmployeeBankModel, EmployeeCIS oEmployeeCISModel, EmployeeBankV2 oEmployeeLoanBankAccount)

Check InTime to confirm if the update has occurred or not. If it hasn't then rerun the import. If the issue re-occurs and/or the record has not updated then log a case with Support via support.in-time@rsmuk.com.

014

Invalid adjustment value (value) for Worker

015

Column [Manager Frontend Ref] cannot be empty for Manager with frontend ref: for Placement:Frontend ref = AAAAAA

016

Found more than one existing user with frontend ref AAAAAA for Placement:Frontend ref = BBBBBB

017

Worker (worker name) is a leaver. They must be re-instated to allow updates for Placement:Frontend ref = BBBBBB

018

Column [Worker's National Insurance Number] invalid format for Worker

Check the workers NI number

019

Error validating Worker (Invalid Email Address)

Check the format of the workers email address. Does it contain invalid characters?

020

Tax Code 'CLI_TAX_CODE' not found.

If this is reported for Row 1 of the import file then it is likely that you have included the row headers in the file.

021

Incorrect number of tokens

This means the CSV file doesn't have the same amount of columns as InTIME is expecting.

Usual reasons:

Reason: There is probably a new-line character in one of the fields in your input file. This is often an address field.
Resolution: You need to check the CSV file which was uploaded to InTime and identify the field with a new line character. Once you have found this then correct your data in your front-office system and re-send the placement. You should raise a request with your front-office system to remove new line characters from any field in file sent to InTime.

Reason: You have added a column to the CSV data and not advised InTIME support to amend the importer configuration to match.
Resolution: Contact support and ask for your import specification to be modified. There may be a charge associated with this.

022

Invalid Payroll (Worker's Payment Frequency) value

Check the Worker has a valid Payment Frequency

023

Cannot parse column (Worker's Date of Joining) value () as date using format

024

Column [Worker First Name] cannot be empty for Worker:Agency Name: null9754 ( null) for Placement:Frontend ref = 9754

025

Column [Worker Starter Statement A] invalid value, should be 2 or 5 digits e.g. 'AN' or 'CYN2Y' for Worker:Agency Name: nullCS0013059 (Worker Name) for Placement:Frontend ref = CIS13059

026

Column [Worker's Bank Account Number] is invalid, check number of numeric digits for Worker:Agency Name: Worker Name (Worker Name) for Placement:Frontend ref = CIS13059

027

Invalid column [Worker CIS Unique Tax Reference] value [4469044558101] (exceeds permitted database length of [10]) for Worker:Agency Name: nullCS0013091 (Worker Name) for Placement:Frontend ref = CIS13091

028

Existing user with ref name is not a Consultant for Placement:Frontend ref = ORC11653

029

Tax Code 'CLI_TAX_CODE' not found for My Pay Portal for Placement:Frontend ref = PLA_ITRIS_ID 

See 20 above

030

Cannot parse column [Placement Start Date] value [2016/12/03] as date using format 'yyyy-MM-dd' (Unparseable date: "2016/12/03", format: [yyyy-MM-dd], name: [PLA_START]) for Placement:Placement: ID=null RefCode=null Frontend ref=CIS12977 Worker=Agency Name: nullCS0012977 (Worker Name) Manager=Agency Name: Manager Name (Manager Name) Placed on 2017-01-05 Starting Unknown Finishing Unknown

031

Error validating Manager (The manager with Id [14710] has already been assigned to a different client with id [2054] for the placement on row [1])

The Manager already exists on InTime but with a different Client than the one on the import file. A Manager can not exists on more than one Client. You can resolve this issue by creating a new manager record in your front-office system.

032

Placement with ID [PCN949] - Currency exchange rate not configured from USD to GBP 

033

Invalid column [Client Frontend Ref] value [Client Name] (exceeds permitted database length of [30]) for: Client: Fixed for Placement:Frontend ref = UMB12024

034

Split Consultant not found: GMK for Placement:Placement: ID=null RefCode=null Frontend ref=B1000382257_83665 Worker=Agency Name: 10135753 (Worker Name) Manager=Agency Name: 106492 (Manager Name) Placed on 2016-10-25 Starting 2016-10-14 Finishing 2016-10-14

The Split Consultant either needs to be amended on the import file or set up on InTime

The Consultant must exist on InTime before the split can be imported.

035

Error validating Worker - Worker gender cannot be blank

036

Cannot parse column [Pay Rate] value [] as decimal number (null)

037

Cannot parse column [Worker's Notional Salary] value [] as decimal number (null) for Worker:My Pay Portal: Worker Name (Worker Name) for Placement:Frontend ref = NORCN430

038

Rejecting because the payroll cannot be found.

Case 55361

039

Cannot parse 'Rate Period' column [141] - value [Standard] as decimal number (Unknown Rate Period Name: Standard)

Case 62693

The rate period value is not being accepted as the rate period is not recognised; as the error advises the problem rate has a rate period of 'Standard'; the importer is expecting: H, Hourly, F or Fixed. 

040

Placement with ID [3198] has no default rate [STD]

Case 62693

Check that the rate on the P Line "PLA_DEFAULT_RATE" matches the rate on R line

041

Row (1) Placement with ID [HQ00044960] - could not insert: [com.ipfour.intime.model.Rate]; SQL [insert into RateTable (charge, name, pay, refCode, placement_, job_, period, timepattern_, periodDuration, originalRate_, backendRef, frontendRef, timesheetFields, selectableByWorkers, viewableByConsultant, viewableByLtdCoUser, viewableByManager, viewableByWorker, priorityOrder, secondaryPay, roleTemplateID, proRata, awr, effectiveFrom) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; nested exception is org.hibernate.exception.DataException: could not insert: [com.ipfour.intime.model.Rate] - P_3300-1578480216194.csv

1. Related to an incorrect configuration for the values -

   import.placement.rate.timesheetFields.tickbox/decimal/hourly.notime/hourly

001

Placement X: Update:Can not change client as timesheets or expenses exist

The placement has been created with a client but the update has come in with a manager which already exists in InTime but attached to a different client. If the client for the placement is not correct then the placement will need to be ended and a new placement created in Bullhorn with the correct client. If the placement has the correct client a new manager record for this person will need to be created in Bullhorn which is attached to the same client. This will allow the manager on the placement to be changed and will also create a new user account for the manager which only relates to the new client. 

002

Create:Customisation error: Alt manager does not belong to placement client, client Contact ID:1461

The alternate manager which is assigned to the placement in Bullhorn already exists in InTime with a different client to that of the placement manager.

003

Bullhorn Update Failure: Unique Taxpayer Reference must be a ten digit number"

InTime is expecting this data to be supplied from Bullhorn. If you no longer store this data in Bullhorn then the Bullhorn customization specific to your agency will need to be amended. Log a call with support.in-time@rsmuk.com

004

Successfully handled event: Bullhorn Placement does not have import status - will not create

Amend the status of the Placement in Bullhorn to "Approved - InTime". This will allow the Placement to be imported.

005

Create:An error occurred running pre-import checks: null

1. Check the terms type of the Client in Bullhorn. The error indicates this is missing.

2. Potential issue with rates (Case 89840). No pay or charge values when a valid rate exists

006

Create:Unable to import worker from Bullhorn, worker is a Provider type but has no provider set. Worker ID:xxxxxx

Set the Provider on the worker or change the Worker type and then retry.

007

Create:Customisation error: For input string: "Umbrella Company Name"

Case 61808

The issue is with customText14 on the Placement. This is configured in the script as the the umbrella company BUT the field type is not the right one for this to be the case. It is Text and needs to be Picker:Client Corporation. Amend this and then assign the umbrella and save the placement with the new field format and it should import.

008

Create:Manager ID not present for placement

The failed status returned indicates that the manager ID (clientContact ID) has not been specified on the placement in the relevant mapped field. For Bullhorn CORE integrations this would be the reportTo field on Bullhorn. See also Error 023 below

009

Create:*(Consultant/Manager/Worker)* field does not contain an ID. Value: xxxxxxxxxxxxx

If the field doesn't contain an ID it show what it has in the field by the xxxxxxxxxxxxx. If this is a string is it likely that the field is a Picker:Text:Internal (Consultant) or Picker:Text:Client (Manager) or Picker:Text:Candidate (Worker). These are required to be Picker:Internal (Consultant) or Picker:Client (Manager) or Picker:Candidate (Worker). If they are already this type and have been updated it may be that the placement data has not been updated since the field has changed type and the placement just simply needs to be re-edited and saved for the field to be updated to the ID from the string.

010

Unable to convert updated Corporate User to Consultant from Bullhorn, Client contact ID = XXX

Generally these can be acknowledged. Typically the error is generated as a consultant has been deleted/removed from Bullhorn which then pings an event to InTime.

011

Unable to import: No rates configured for this placement (Custom Object 2)

First step is to try re-importing the placement. If this works then acknowledge the error.

012

Exception ocurred importing placement: org.springframework.dao.DataIntegrityViolationException: could not insert: [com.ipfour.intime.model.Worker]; SQL [insert into UserTable (emailFormat, title, firstname, middlename, lastname, password, passwordHash, username, agency_, refCode, itrisId, contact_, status, pin, securityAnswer, securityQuestion, created, modified, exportedPayroll, exportedAccounts, creationMethod, lastPasswordChange, noCommunications, simpleMenu, roleLevel, failedLoginCount, failedPinCount, lastPINEnterDate, lastLogin, akaFirstname, akaLastname, inpayUserId, timeZone, detectedTimeZone, applicantType, userType) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 1)]; nested exception is org.hibernate.exception.DataException: could not insert: [com.ipfour.intime.model.Worker]

013

Create:Unable to read ClientContact for placement from Bullhorn, with ID:xxxxx

014

Create:Placement is perm type but has no fee

By default any Bullhorn placement with the term "PERM" in the placement type e.g. "Contract to PERM" is treated as a perm placement in InTime and InTime is then expecting a perm fee to be present. If the Placement is not Perm and needs to be treated the same way as a Contract Placement with rates and timesheets then the placement type should be changed to something that does not have the term "perm" in it e.g. Contract.

015

Create:Could not convert rates for placement

Client to review placement in Bullhorn

016

Exception ocurred importing placement: org.springframework.dao.DataIntegrityViolationException: not-null property references a null or transient value: com.ipfour.intime.model.Rate.job; nested exception is org.hibernate.PropertyValueException: not-null property references a null or transient value: com.ipfour.intime.model.Rate.job

Support. Check alignment of the Pay Element code in InTime with the Bullhorn Pay Element codes in the configuration list. Update the config list to align with the Pay Element code.

017

Create:Customisation error: Could not match Client terms template:GBP IDF

Client to review placement in Bullhorn

018

Error importing placement: Manager field does not contain an ID. Value: Timesheet DefaultApprover

Check placement in Bullhorn to ensure it has a Manager assigned and they have an email address

019

Error importing placement: Unable to read ClientCorporation for placement from Bullhorn

Login to Bullhorn with the API credentials. Search for a placement that has failed to import. On the Overview TAB the Company - Details section will likely display a message - "Error load data". Client will need to raise Bullhorn support as the API will need access to this.

020

Error importing placement: Unable to read CorporateUser for placement from Bullhorn, with Id:xxxxxx

Login to Bullhorn and check that you can see the Corporate User section

021

Error importing placement: No such property: mobile for class: com.ipfour.intime.model.Worker

27/10/21 - This was an error in the default integration code and should now be resolved and not re-occur.

022

Error importing placement: not-null property references a null or transient value: com.ipfour.intime.model.Rate.job

Check InTime Config aligns the Bullhorn Pay Element Code with the InTime Code (not the Pay Element Name)

023

Error importing placement: Manager ID not present for placement

The Bullhorn->InTIME integration always needs a manager, whether a PERM placement or not. There are no email communications sent on a PERM placement when it’s imported but most clients add the Sales Manager to the Manager mapping for PERM placements just so that is seen. The manager needs to be from the client as this is where the client for the placement is mapped from the client of the manager.

024

Update Error: Manager ID not present for placement

See error 023 above

025

Error importing placement: Salary/Pay Unit not set - can not determine Time Period for rates

026

Error importing placement: Invalid charge terms days value:30

027

Error importing placement: Yearly rate used in Bullhorn - not supported by intime

Check the Contract Placement Information TAB in Bullhorn for the Placement. The Pay Unit is probably set to Yearly.  This determines the period type of rates on the placement. InTime only recognises the following values so please set the value list to these: Per Hour,Per Day,Per Month

028

Error importing placement: Cannot get property 'id' on null object

029

Error importing placement: Placement has a fee but no salary was available as multiplier

030

Error importing placement: Column 'job_' cannot be null

1. Check the pay element in the Bullhorn config list aligns with what has been defined in InTime

031

Error importing placement: Unable to import: Rate Template not selected for new placement

001

Error: Row (851) Col (3) Column [Job Title] cannot be empty for Placement:

Placement: ID=null RefCode=null Frontend ref=16162

 Worker="Agency Name": 3121 (Worker Name)

Manager="Agency Name": 13170 (Manager Name)

Placed on 2016-04-25 Starting Unknown Finishing Unknown;

Row (852) Missing or invalid preceding placement row for rate row;

Row (853) Missing or invalid preceding placement row for rate row

The Job Title for a Worker is mandatory. Update Colleague and rerun the import.

002

Could not find an existing approval route called: 'Auto"Approval"Route' for Placement:Placement: ID=null RefCode=null Frontend ref=610007043 Worker=InterQuest Group: 104011644 (Warren Bowden) Manager=InterQuest Group: 610012480 (Chris Manley) Placed on 2016-11-22 Starting 2016-12-24 Finishing 2017-02-24; Row (2) Missing or invalid preceding placement row for rate row

There were invalid characters in the import file that were changing the Approval Route to one that was not recognised in InTime. Need to edit the file in a specialised text editor. Request client to refer back to Colleague to check the import file.

003

 Error validating Worker (Bank A/C Name, Number and Sort Code must be specified if paying by BACS)

If a worker is setup to be paid via BACS then the Bank details must be entered including Bank A/C Name, Number and Sort Code.

004

 Worker's National Insurance Table Letter not updated because InPay is enabled

005

 Error validating Manager (Invalid Email Address: tbc@c)

006

 Error validating Worker - Worker title cannot be blank

007

Error validating Worker - Worker date of birth cannot be blank

008

Error validating Worker - Worker NI number cannot be blank

009

Error validating Worker - Worker tax code cannot be blank

010

Error validating Manager (The manager with Id [200222453] has already been assigned to a different client with id [300026301-EUR] for the placement on row [30])

The Manager already exists on InTime but with a different Client than the one on the import file. A Manager can not exists on more than one Client. You can resolve this issue by creating a new manager record in your front-office system

011

Error validating Worker (The field com.ipfour.intime.model.Worker.email cannot be null.)

Please ensure that you always have an email for a worker as it is mandatory for InTime. We suggest that your front-office system should enforce this field, either on entry or before export to InTime.