Generating and Validating a Workday EIB Spreadsheet Template Without Corrupting Headers

To generate a valid inbound Enterprise Interface Builder (EIB) load file in Workday, open the integration system's related actions and select Template Model > Generate Spreadsheet Template (or Generate Spreadsheet Template with Data). Every generated EIB workbook embeds hidden XML schema mapping metadata in Rows 1 through 5 and the first columns of each worksheet tab; deleting, reordering, or overwriting those header rows—or altering worksheet tab names—corrupts the template model binding and causes the inbound web service transformation to fail at launch.

How to generate and customize an inbound EIB spreadsheet template

Before generating a template, confirm your security group has Modify permission on the Integration Build domain (to create and customize EIBs), Integrations: EIBs (to launch EIBs), and Put (or business process initiating action) permission on the underlying web service operation's security policy.

Step 1: Customize the Template Model (Optional but recommended)

Instead of manually deleting or inserting columns in Excel—which breaks the XML mapping—customize the template inside Workday before generating the file:

1. Open the View Integration System page for your inbound EIB.
2. From the related actions menu, select Template Model > View (or Template Model > Edit).
3. Click Edit Template Model Sheet (or select a specific area in the left pane and click Edit Template Model Area).
4. Enable Separate Type Column: For reference ID columns where you might pass different ID types (or want Workday to expose an explicit ID Type column alongside the ID Value column), select the Separate Type Column checkbox and either specify a default Reference ID Type or clear it so you can populate multiple reference ID types in the spreadsheet.
5. Filter pre-populated data: If the web service supports Generate Spreadsheet with Data, scroll down on the View Template Model page and click Edit Template with Data Options. Select Condition Rule Filter to restrict which records Workday exports into the template (and click Test Condition Rule Filter to verify). Workday caps generated spreadsheets with data at 300 MB and a 2-hour generation limit, splitting output across multiple files when data exceeds 20 MB.

Step 2: Run Generate Spreadsheet Template

1. From the related actions menu of the inbound EIB, select Template Model > Generate Spreadsheet Template.
2. Choose whether to generate a blank template or select Generate Spreadsheet with Data (when supported by the Put operation, such as Put Advanced Lookup Table or Put Allocation Pool), select Confirm, and click Submit.
3. On the View Background Process page, click Refresh until completion, then download the spreadsheet from the Output Files tab or download notification link. (Note: Standard web service EIBs generate XML Spreadsheet 2003 .xml files or .xlsx files depending on the operation; Extend App Business Object EIBs strictly require .xlsx format.)

Anatomy of an EIB spreadsheet: Rows 1–5 and key columns

When you open a generated EIB spreadsheet in Excel, you immediately notice that the first visible row of column labels starts at Row 5, while Rows 1 through 4 are collapsed or hidden.

How Spreadsheet Key, Row ID, and Parent-Child keys work

Workday SOAP web services are hierarchical (for example, one Accounting Journal has many Journal Lines; one Payroll Input has multiple Related Calculation rows; one Advanced Lookup Table has multiple Snapshots and Row Data lines). Flat spreadsheet rows reconstruct that XML hierarchy using key columns:

1. Spreadsheet Key (or Header Key)

• Spreadsheet Key (Column B) groups rows into separate top-level web service requests (transactions).
• Every row that belongs to the same parent record or transaction must share the exact same Spreadsheet Key.
• When creating multiple independent transactions (for example, loading 50 separate workers or 50 student charges), increment the Spreadsheet Key (1, 2, 3...) for each distinct top-level transaction—or keep Spreadsheet Key as 1 across child rows that belong to the same parent container (such as adding multiple rows to a single Advanced Lookup Table).

2. Row ID (and Child Section Row IDs)

• Whenever a single parent transaction (for example, Spreadsheet Key = 1) has multiple child items in a repeating section—such as multiple Journal Lines, multiple Additional Input Details on a payroll input, or multiple Row Data entries in an Advanced Lookup Table—you leave the parent-level columns blank on the second and subsequent child rows and increment the Row ID (1, 2, 3...) for each child item.
• Concrete example (Import Payroll Input with Related Calculations): To load an Hourly Pay earning of 1600 with two related calculations (Hours = 40 and Hourly rate = 10) for a single worker input:

• Preventing duplicate loads on rerun: On operations like Import Payroll Input, always populate the explicit reference ID column (e.g., Payroll Input ID) if you may need to update or reload the file later. If you leave Payroll Input ID blank, Workday auto-generates a new reference ID on every upload, creating duplicate pay inputs if the same spreadsheet is run twice.

Populating Reference IDs and dates without errors

1. Always use Integration IDs, not display names: Workday EIB columns expect reference IDs (such as Employee_ID, Position_ID, Cost_Center_Reference_ID, Academic_Period_ID, or Currency_ID), not UI display names. To find any object's reference ID in Workday, open its related actions and select Integration IDs > View IDs.
2. Use Paste Special > Values: Copying cells directly from a Workday Excel export or external workbook into an EIB template overwrites Workday's cell data types and number/date formatting. Always use Paste Special > Values (or Values and Number Formatting only after verifying the format).
3. Preserve leading zeros: Employee IDs, Cost Center IDs, and Custom Worktag IDs (such as 01 or 00452) frequently start with 0. If you open an intermediate .csv in Excel before pasting into your EIB template, Excel strips leading zeros (01 becomes 1), causing Invalid ID value errors during the load. Format reference ID columns as Text before pasting.
4. Clear ghosts below your last data row: If you previously had 500 rows in an EIB template and pasted 100 new rows over them, select Rows 106 to 505, right-click, and choose Delete (entire spreadsheet rows, never Rows 1–5). Simply pressing the Delete key on cells can leave empty XML <Row> tags that Workday attempts to process as blank records.

Troubleshooting common EIB template corruption errors

When an inbound EIB fails immediately at launch or rejects rows with schema/mapping errors, check these causes:

How kiweely fits

Building inbound EIB spreadsheets by hand—hunting down Reference IDs across Integration IDs > View IDs, aligning parent Spreadsheet Key and child Row ID columns, and diagnosing cryptic XML transformation errors—is slow and repetitive. kiweely inspects your tenant's EIB template models, validates reference IDs and required keys against live tenant metadata before you launch the load, and helps isolate and repair failed rows without corrupting template headers. Kiweely Personal is free for your Workday personal developer account and its tenant. Any other tenant needs a Personal licence, $99 a month, or a seat in your firm.

Frequently asked questions

Why are Rows 1 through 4 hidden in a Workday EIB spreadsheet template?

Rows 1 through 4 store the internal XML element names, XPath hierarchy paths, and reference ID types that Workday's inbound EIB transformation engine uses to convert spreadsheet cells into a SOAP web service request. If you alter or delete those hidden rows, Workday cannot parse the file.

Can I delete unused optional columns from an EIB spreadsheet in Excel?

Do not delete columns directly in Excel, as doing so can misalign the hidden XML header metadata in Rows 1–4. If you want a cleaner spreadsheet with fewer columns, select Template Model > Edit on the EIB in Workday, click Edit Template Model Sheet, uncheck or hide optional areas/columns there, and run Template Model > Generate Spreadsheet Template again.

When should I check "Separate Type Column" on the EIB Template Model?

Select Separate Type Column when a field in your EIB can accept multiple Reference ID types (for example, Employee_ID vs. Contingent_Worker_ID, or different Calculation/Organization ID types) or when the default Reference ID Type on the template does not match the IDs you maintain in your tenant.

How do I reload only the rows that failed in an EIB upload?

Launch your EIB with Add Errors to Attachment checked. After the run finishes, check the Execution Summary on the Messages tab to confirm whether valid rows committed, open the error attachment from the Integration Events report to review the cell comments on failing rows, and paste only the corrected failing rows (using Paste Special > Values) into a clean copy of the generated template.