---
title: "Workday EIB error explainer: paste errors, get the fix"
description: "Paste the error messages from a Workday inbound EIB and read each one explained, with the fix, from Workday's documentation. Free; nothing you paste is sent."
url: https://kiweely.com/tools/workday-eib-errors
---

# Paste your EIB errors. Get the fix.

Each message explained from Workday’s own documentation. It runs in your browser, and nothing you paste leaves this page.

## Where to copy the messages from.

The integration event of the load: open it from View Background Process.

1.  For a run that finished as Completed With Errors, select the **Number of Errors** link and copy the messages.
2.  Or download `ErrorsAndWarningsSpreadsheet.xml` from the Output Files tab, open it and copy the message column. Workday keeps it for 60 days.
3.  Lost the page? Search with the `intsys:` prefix for the integration system, or run the Integration Events report.

## The messages it explains.

Each one checked against Workday’s documentation, with the source linked.

**Invalid ID value: a Related Calculation or Deduction ID**

 `Validation error occurred. Invalid ID value. 'W_NETGU is not a valid ID value for type = 'Related_Calculation_ID'`

The file uses the wrong Reference ID type. Related calculations have two ID types, Related\_Calculation\_ID and Workday\_Related\_Calculation\_ID, and deductions have Deduction\_Code and Workday\_Deduction\_Code; Workday-owned codes use the Workday\_ type.

**Invalid ID value: Ledger\_Account\_ID**

 `Invalid ID value. '5000' is not a valid ID value for type = 'Ledger_Account_ID'`

On an accounting journal load, Workday names one cause for this: the Account Set field is empty in the journal line (the Journal Entry Line Replacement section).

**Invalid ID value: any other ID**

 `Invalid ID Value. “WOK is not a valid ID value for type = “Company_reference_ID.”`

The value in that column does not match the Reference ID of any record of that type in Workday. The message names the value and the ID type. A record that doesn’t exist yet gives the same message.

**Doesn’t meet the restrictions defined for this field**

 `The entered information does not meet the restrictions defined for this field. (Company_Reference).`

Workday documents this as security: the person who launched the EIB can’t act on the record in the field named in brackets. The message names no wrong value and doesn’t say ID after the field.

**The task submitted is not authorized**

 `Processing error occurred. The task submitted is not authorized.`

Workday’s web service guides describe this as security: the account that ran the load lacks the business process or domain access the web service needs.

**The field is required**

 `Validation error occurred. The field Expense_Report_Data is required.`

Usually a required value is missing. Workday also notes that it can name a parent element when the real problem is a missing value inside it or a security requirement.

**The web service is set to Add Only**

 `The Web Service is set to Add Only; documents cannot be resubmitted.`

The load was run as Add Only, which only creates records, and a row names one that already exists. Workday raises an error when Add Only finds an existing instance.

**Invalid format for date**

 `Invalid format for date text=3/1/2020 on attr Event Effective Date`

A date isn’t in the format Workday reads. Workday uses YYYY-MM-DD for date fields.

**The accounting journal is posted or canceled**

 `The Accounting Journal is posted or canceled or is an intercompany or reversal journal and cannot be submitted.`

The journal uses the same Accounting\_Journal\_ID as one that is already posted, canceled, reversed or intercompany.

**The journal isn’t balanced**

 `Journal cannot be submitted unless it is balanced by balancing Worktag.`

Debits and credits of an imported journal must balance by company, and by the balancing worktag when worktag balancing (for example fund balancing) is on in the tenant.

**No valid ledger period for the date**

 `The date selected does not have a valid ledger period associated with it.`

Workday checks the journal’s accounting date against the ledger periods of the company. The date in the journal header applies to every line.

**Only one worktag of each type per line**

 `Only one worktag for each type is allowed for each document line.`

A journal line holds two worktags of the same type. Workday allows one of each type per line.

**Hire: applicant data with an applicant ID**

 `Validation error occurred. Multiple Element Contents, including Hire Employee Business Process Data/a1/Applicant/CL] contain data where only one is allowed by mutex Hire Employee Business Process Data.`

The row gives a pre-hire (applicant) ID or a former worker ID together with other data about that person, such as name, country, email, phone or addresses. With an ID, nothing else about the person may be filled.

**Hire: both a position and a job requisition**

 `Validation error occurred. Multiple Element Contents, including Hire Employee Business Process Data/d1/Job Requisition for Fill WWS Events Secured by Transactions [WS]*ST, contain data where only one is allowed by mutex Hire Employee Business Process Data.`

The row fills both the position and the job requisition. A hire takes one or the other.

**Hire: the Employee ID is already in use**

 `Validation error occurred. Enter a unique Employee ID. The ID is already in use by xxx`

The row uses an Employee ID that was used before, which happens when people were hired and the hires then rescinded.

**Hire: not tracked for the Location Context**

 `Gender is not tracked for the specified Location Context. The Location Context is derived from the Country of the Location for the Position.`

These are fields set per country, and the web service can’t find the country to check them against: it comes from the location of the position.

**Put Applicant: ethnicity doesn’t exist in the Location Context**

 `Validation error occurred. The ethnicity doesn’t exist in the specified Location Context. The Location Context is derived from the Country of the Location of the Position.`

Workday’s Put Applicant guide sends you to the country’s localization settings for this one.

**Change Job: Proposed Position Restriction is required**

 `Validation error occurred. Either the Proposed Position Restriction is required or Create Position needs to be true.`

The position doesn’t belong to the organization the worker is moving to.

**Payroll input: changing the worker isn’t allowed**

 `Changing the worker associated with a Payroll Input is not allowed when updating an existing Payroll Input.`

Some Payroll Input IDs in the load were used before, so Workday tries to update those inputs and can’t: they are completed or belong to another worker.

**Off-cycle: no eligible processing period**

 `Validation error occurred. No eligible processing period exists for the period date.`

Workday can’t find a pay period for the off-cycle payment: the period before isn’t complete, or the Period Date, Run Category and Pay Group don’t lead to one.

**Leave of absence: each correction needs a comment**

 `Each correction must have a comment.`

A correction to a leave of absence event needs a comment.

**Time off: one Spreadsheet Key per worker**

 `To allow Time Off Requests to process correctly all Time Off Requests for each individual Worker must be on the same Spreadsheet Key.`

A worker’s time off rows are spread across more than one Spreadsheet Key.

**Duplicate ID values are not allowed**

 `Duplicate ID values are not allowed.`

Two rows give the same ID where each must be unique, such as the Time Off Entry ID.

**Time off: not enough balance or not eligible**

 `The worker doesn't have sufficient balance or isn't eligible for the time off request for [type and date].`

Workday checks each request against the worker’s balance and eligibility for that time off type on that date, and this one fails.

**Time tracking: more than 24 hours on a day**

 `More then 24 hours have been reported by the worker, [worker], on [date].`

The rows report more than 24 hours for one worker on one day.

**Time tracking: Time Entry Code not valid for the worker**

 `Time Entry Code [tec] is not valid for [worker].`

The worker can’t use that Time Entry Code.

**Time tracking: the date is locked**

 `[date] is locked for time entry for [worker].`

The date is locked for time entry for that worker.

**Statistic: worktags for required dimensions**

 `Enter Worktags for each Required Dimension.`

Workday’s guide gives two causes: the Year or Fiscal Time Interval isn’t right, or the Statistic Definition has required dimensions (worktags) the statistic lines leave out.

**Statistic: worktags not allowed**

 `The following worktags are not allowed`

The statistic lines include dimensions (worktags) that the Statistic Definition lists as neither required nor optional.

**Statistic: worktag is not valid**

 `Worktag is not valid`

The worktag is inactive, refers to a related worktag that is inactive, or isn’t set up in the structure dimension (or is, without all its members).

**Statistic: fiscal period**

 `A Fiscal Period does not exist for the year and posting interval provided`

The Year or Fiscal Time Interval in the file isn’t right.

**Out of memory (Java heap space)**

 `java.lang.OutOfMemoryError: Java heap space.`

The EIB ran out of memory. Workday notes that EIBs with custom XSLT transformations can take several times the memory of the data, and points to inefficient XSLT.

## Let Kiweely Vine run the load.

Kiweely Vine turns your spreadsheet into an EIB, loads it in your tenant and reads back every row. Free on your own Workday developer tenant.

[Start for free](https://kiweely.com/download) [See pricing](https://kiweely.com/pricing)
