Greenshades Common Errors
If you encounter any issues with your Greenshades Integration, this article provides guidance to help you identify and resolve them. For information on resolving various Bullhorn Middle Office errors, see Pay & Bill Related Issues.
Fixes Within Bullhorn
Issue/Error | Cause | Solution |
---|---|---|
Pay Schedule does not exist |
The value in the Greenshades Pay Schedule field does not match a value in Greenshades. This is normally caused by an end user updating the GS Pay Schedule field on the placement and not the TimesheetCycleID to match. The GS Pay Schedule field sets the value in GS, but the TimesheetCycleID sets the value in BTE. |
|
Missing Value for GreenshadesID |
The candidate associated with the payable charge does not have a Greenshades ID on their candidate record. This should only be a problem with migrated approved placements. |
If the candidate does not exist in GS, an end user can either update the Placement Status from Approved to Submitted and then back to Approved, or change the Placement Greenshades Sync Status to Ready to Export. |
Missing Required Field |
A field on the placement or candidate record is missing a required value. Should only be related to migrated approved placements. |
The error should tell the end user which field is missing information. That field will need to be updated before the payable charge can be re-exported. |
Invalid Employee Type |
A payable charge connected to a placement with an employee type of not configured in Greenshades was included in the batch. |
That charge should not be included in a Greenshades batch, but should be sent to via the Accounts Payable process. |
Candidate is missing a "Greenshades Native ID" value which is required to sync Direct Deposit Account. Please confirm Candidate has been successfully synced to Greenshades. |
The candidate record in BH does not have a GS ID listed when a DD account was added to the candidate. |
|
Employee is not assigned to an active placement |
The placement information in Greenshades has been removed or is not accurate. |
An end user can either update the Placement Status from Approved to Submitted and then back to Approved, or change the Placement Greenshades Sync Status to Ready to Export. This will cause the placement information to resync with Greenshades |
Earn Code cannot contain units |
The earn code type associated to an earn code used is setup as an hourly or Amount type code. |
An end user needs to update the transaction to use the correct settings based on the earn code type. |
Candidate Does not Exist in Greenshades |
The candidate record in Greenshades has been deleted. |
Log into Greenshades and see if the GS ID on the candidate can be found. The ID may be connected to a deleted GS record. If the ID is not found or the record is marked as deleted, please contact BH support to have the GS ID removed from the candidate record in BH. |
Unexpected error in API |
Unknown error in API integration. |
Resend via BH export process. |
400 Bad Request { "errors": { "[0].AccountNumber": [ "'Account Number' must not be empty." ], "[0].RoutingNumber": [ "'Routing Number' does not match '^\\d{9}$' Regex.", "Invalid routing number. See checksum algorithm." ] }, "type": "https://tools.ietf.org/html/rfc7231#section-6.5.1", "title": "One or more validation errors occurred.", "status": 400, "traceId": This error may contain additional details for the traceId that are unique to each request. |
The routing/transit number for the direct deposit account that was attempting to sync contains less than 9 digis. A US based routing/transit number is required to contain 9 digits and the GS integration verifies that total. |
Have the employee re-enter their full direct deposit information via their onboarding platform. Once complete, that information will automatically sync to Greenshades, assuming the employee is still on an approved placement. If their placement is no longer approved (ended or completed), no data will sync and the customer team will need to reapprove the placement before the new direct deposit information will update. |
PayableChargeID:1 and PayMasterTransactionID:79, ErrorMessage:Candidate ID 2622032 does not exist in Greenshades workspace 100298470. Please ensure Candidate has been synced and reprocess |
The GS ID on the associated candidate record does not match an existing GS employee ID for the specified workspace. |
Verify that the correct GS ID is on the BH candidate record. It is possible that the corresponding GS record was soft deleted, as part of a clean up process which requires either the GS record to be undeleted or and GS ID in BH to be updated to an existing GS record. If the client has multiple workspaces, the GS ID might not exist in that specific workspace which would require a new candidate CO be created with the |
Error creating Work Location in Greenshades. Please contact Bullhorn Support for assistance |
Most often, this is caused when multiple placements are created simultaneously with the same new location. |
First, verify that the location does not exist. Most likely, the location does exist, but due to the way that a location is created when multiple new placements sync, this can be a false negative error. If the location does not exist, try and resync the placement. |
PayableChargeID:XXXX and PayMasterTransactionsID:XXXX, ErrorMessage: Failed due to accompanying transactions failing. |
Occurs when there is a mismatch in data between Greenshades and Bullhorn. This error typically occurs for adjustment/reversal transactions. |
Check the following data points:
|
Earning Code '[Earn Code Title]' cannot contain a negative rate; Total of existing + current amounts results in a negative gross pay amount. ($0.00 + ($30.00) = ($30.00)) |
This error typically occurs on adjustment transactions, where:
|
|
Workspace ID is not present. |
The Greenshades Workspace ID (Legal Business Entity) is not filled in on the Placement record. |
Fill in the Greenshades Workspace ID/Legal Business Entity on the placement record. Then attempt to export the payable charge again. |
Missing required field: Workers Compensation Rate Code; Missing required field: Legal Business Entity Number |
Workers Comp Code field on the placement is not filled in. |
Fill in the Workers Comp Code field on the placement record. Then attempt to export the payable charge again. |
ErrorMessage:Earning Code {earn code title] is not hourly or salary and cannot contain hours. Failed due to accompanying transactions failing. |
Export is failing due to either a misuse of an earn code (i.e. unit amount used instead of hourly) or the earn code is not present on the assignment in Greenshades. |
Double check the earn codes used. If you can not find the misused earn code, contact Bullhorn Support. |
ErrorMessage:Earning Code '{earn code title]' is not piece rate and cannot contain units.; Cannot continue processing because there are multiple in-progress adjustment pay runs. Found: 2 |
Export if failing due to a misuse of an earn code unit/hourly amount on a transaction |
Double check the earn codes used. If you can not find the misused earn code, contact Bullhorn Support. |
ErrorMessage:Cannot continue processing because there are multiple in-progress scheduled pay runs. Found: 2 |
This occurs when trying to export reversal/adjustment transactions and the prior transactions are currently being processed in pay run in Greenshades. |
Wait until the pay run is completed in Greenshades, then you can re-export the payable charges. |
Fixes within Greenshades
Issue/Error | Cause | Solution |
---|---|---|
Work location code does not exist. |
The location does not exist in GS. |
Work locations should be created when an assignment is successfully synced to GS, assuming the following:
|
Position Code does not exist. |
The workers compensation code on the placement does not match a code and state combination in Greenshades. |
Position Code equals Workers Compensation Code. Verify the Workers Compensation Code used on the placement also exists in Greenshades. |
Pay Schedule does not have a pay period for effective date. |
The check date entered is earlier than the earliest pay period date available in Greenshades. |
Verify the check date is correct. If necessary, reach out to Greenshades Support to have the necessary pay period opened. |
Employee set to Inactive. |
The employee record in Greenshades connected to the Greenshades ID on the candidate record has been made inactive. |
|
Earning Code does not exist. |
An earn code associated with a pay transaction within the payable charge has not been created in Greenshades. |
Verify if that selected Earn Code does exist in Greenshades.
|
Department Code does not exist. |
The department code in Greenshades is the Placement “Time and Expense Branch” field in BH and it needs to match exactly to an existing department value in Greenshades. |
Verify that the Time and Expense Branch exists in Greenshades. If not, reach out to Peoplelink management to verify the Branch was setup correctly in both Bullhorn and Greenshades. |
Total of existing + current amounts resulted in a negative gross pay amount. |
A negative transaction (or multiple) within the Payable Charge was not able to find a parallel positive charge within Greenshades. This results in a negative total which Greenshades cannot process. |
|
Failed due to accompanying transactions failing. |
This is an update to the above error message. Originally, only the negative charges within a payable charge would fail, which often lead to an overpayment because the offsetting positive transactions would pass over with the associated negative transactions. This error now fails all transactions within a payable charge to avoid that overpayment. |
These transactions will need to be manually added into Greenshades. Once that is complete and processed, a Bullhorn support ticket will need to be created, including the payable charge ID, to ask for the payable charge export status to be updated to “Exported”. |
PayableChargeID:68 and PayMasterTransactionID:32383, ErrorMessage:Invalid GoLocationIds provided: 1772766021, 1772742245. |
Often happens when a post migration location clean up is done within Greenshades to remove locations (for a variety of reasons). |
Reach out to Greenshades support with the GoLocationIDs and have them verify that those locations have been soft deleted. They will need to re-enable those locations. |
Cannot continue processing because there are multiple in-progress adjustment pay runs. Found: 3 (could be any number) |
Within Greenshades, there are multiple open adjustment pay runs with the same pay schedule. The payable charge does not know which run to use and therefore errors. |
Find the additional open adjustments pay run in Greenshades and either Submit or Cancel them. |