--- title: "Upload configurations and generate Workday EIBs" description: "Upload configurations and generate Workday EIBs" canonical_url: "https://support.pave.com/articles/upload-configurations-and-generate-workday-eibs-OF3LP1bP5z" md_url: "https://support.pave.com/articles/upload-configurations-and-generate-workday-eibs-OF3LP1bP5z.md" --- # Upload configurations and generate Workday EIBs Everything you do with Workday EIBs inside Pave happens in one place: your merit cycle's settings. There you download Pave's configuration templates, upload your filled-in workbooks, and generate the EIB files. This article walks through each step, from downloading templates to downloading your finished files. For how to fill in a workbook, see the article on filling in a Workday EIB configuration workbook. ## Find Workday EIB configurations 1. Go to **Compensation Planning** and open the cycle's configuration. 2. Select **Cycle settings**. 3. Under **Cycle downloads**, find **Workday EIB configurations**. When the cycle has no configurations yet, you see one button: **Upload EIB config**. Once at least one configuration is uploaded, the button changes to **Reupload EIB config**, a **Generate** button appears, and each configuration is listed below with the date it was last uploaded. ## Download the templates 1. Click **Upload EIB config**. 2. In the upload window, click the **here** link in "Download our default configuration templates here." This downloads `Workday_EIB_Configuration_Templates.zip`. It contains one workbook for each EIB and each Change Job sub-process, named after the process, for example `Workday_EIB_Configuration_requestCompensationChange.xlsx` and `Workday_EIB_Configuration_changeJob_proposeCompensation.xlsx`. You only need to fill in the workbooks for the EIBs you plan to generate. For Change Job, fill in the main `changeJob` workbook plus one for each sub-process you want filled. ## Upload configurations 1. Click **Upload EIB config** (or **Reupload EIB config**). 2. Drag your filled-in workbooks into the window, or click **Browse files** to select them. You can upload several workbooks at once. Only `.xlsx` files are accepted. You don't need to tell Pave which EIB each workbook is for. Pave reads it from cell A2 of the workbook's **📋 Field Mappings** tab. Pave checks each file in two stages: 1. **A quick check in the upload window.** Pave confirms the file can be read, has the **📋 Field Mappings** and **🔗 Reference IDs** tabs, and is a recognized EIB. If a file fails, the error appears in the window next to the file name. Other files in the same upload continue. 2. **A full check in the background.** Files that pass the quick check start importing, and the row shows each one as importing while Pave checks every row against Workday's template and your cycle's columns. When the full check finishes, Pave sends you an email and an in-app notification: * **"Your Workday writeback config has been uploaded"**: the configuration is saved and now appears on the row. * **"Issue uploading your Workday writeback config"**: the configuration wasn't saved. The email includes the error to fix. If the full check fails, the importing line disappears from the row without a message. Check your email for the error. ### Fix upload errors Upload errors name the tab and, where relevant, the rows. For example: ``` 📋 Field Mappings: unsupported Pave Column Keys * row 14: "meritIncrease" is not supported ``` Pave stops at the first tab with a problem, so fix what's listed and upload again to find any others. For the most common workbook errors and how to fix them, see the article on filling in a Workday EIB configuration workbook. Two errors come from the upload itself rather than the workbook's contents: `We couldn't identify this workbook as a supported EIB type`: Cell A2 of **📋 Field Mappings** doesn't contain a recognized EIB name. Start from a fresh Pave template and copy your mappings into it. `This writeback config upload is already being processed`: An earlier upload of the same EIB is still importing. Wait for it to finish, then upload again. ## Preview, replace, or delete a configuration **Preview:** click a configuration's name on the row to see what Pave saved. The preview shows when it was last uploaded, with a tab each for **Reference IDs**, **Field Mappings**, and **Employee Filters**. **Replace:** a cycle holds one configuration per EIB. To change one, edit your workbook and upload it again with **Reupload EIB config**. The new workbook fully replaces the old configuration, and nothing from the previous upload is kept. If the new workbook fails the check, your existing configuration stays as it was. **Delete:** click the **X** next to the configuration, then click **Delete** in **Delete EIB Config?**. You can't delete a configuration while it's importing or while an EIB is being generated. ## Generate EIBs 1. On the **Workday EIB configurations** row, click **Generate**. 2. In **Generate Workday EIB(s)**, select the EIBs you want. 3. Click **Generate**. The button shows how many items you selected, for example **Generate (3)**. The window lists one checkbox per uploaded configuration: * **Request Compensation Change, Request One Time Payment, and Add Stock Grant** each have their own checkbox. * **Change Job** has a checkbox with its sub-processes listed underneath. Only sub-processes with an uploaded configuration appear. Selecting Change Job selects all of its sub-processes. Clear any you don't want before generating. * If sub-process configurations are uploaded but the main Change Job configuration isn't, Change Job shows **(Configuration Required)** and can't be selected. Each EIB you select becomes its own file. Change Job and the sub-processes you selected come together in one file, with the main Change Job sheet always included. After you click **Generate**, a message confirms that each file is being generated and that a download link will be emailed to you. While files are generating, the **Generate** button shows **Generating...** and you can't start another generation or delete a configuration. The cycle doesn't need to be finalized. Each file reflects your cycle data at the moment it's generated. ## Download your files When a file is ready, Pave sends you an email with the subject **"Your writeback export file"**, and an in-app notification. Click **Download file** to download it. Only the person who clicked **Generate** receives the link. The email notes that the file is deleted after 7 days. To get a new copy after that, generate it again. Files are named `writeback___.xlsx`, for example `writeback_requestCompensationChange_...xlsx`. ### What's in the file Each file is Pave's copy of Workday's EIB template for that process, filled in with your employees: * **Workday's sample rows are removed**, and your employees start on the first data row below the header rows. * **The header rows and the Overview tab are kept as they are.** * **Every column in the template is kept, in its original order.** Columns you didn't map are left blank. * **Sheets that weren't selected are left empty.** For example, a Change Job file includes every sub-process sheet in the template, but only the ones you selected are filled. * **Values are written as text**, exactly as your configuration produced them. Amounts aren't rounded or padded unless a transformation such as `precision` or `divideBy` does it. For who appears in each file and how Spreadsheet Keys and Row IDs are numbered, see the article on filling in a Workday EIB configuration workbook. ## If generation fails If Pave can't build a file, you get an email with the subject **"Issue generating your writeback export file"** instead of a download link. No partial file is created. The email lists each problem once, with how many times it occurred and up to three example employee IDs. For example: `Required field "Amount*" (Pave Column Key: newBase) resolved to an empty value. (12 occurrences, e.g. EMP1, EMP2, EMP3)` Common problems: `Required field ... resolved to an empty value`: Workday requires this field, and it came out blank for these employees. Check that the cycle column has a value for them, or add an **OR Constant Value** or a `fallbackSource` transformation to cover blanks. For fields that use Reference ID rules, add a catch-all rule. `No writeback config has been uploaded for ...`: A selected EIB or sub-process doesn't have a configuration in this cycle. Upload one, or clear it from your selection. `This employee cannot be written to the ... sheet`: An employee qualifies for a Change Job sub-process but not for Change Job itself. Every employee on a sub-process sheet must also be on the main Change Job sheet. The email lists up to 10 distinct problems, most frequent first, and notes how many more there are. Pave also stops checking after 100 errors. Fix what's listed and generate again to see the rest. ## Things to know * **Files reflect the cycle when you generate.** If planners change anything afterward, generate the file again. * **Generating doesn't change your cycle.** You can generate as many times as you need.