---
title: "EIB mapping for Workday consultants — Kiweely"
description: "How to review an AI-drafted inbound EIB: web service, template model, reference ID types, and a SOAP fault check with Deployment Agent."
url: https://kiweely.com/guides/ai-workday-eib-mapping-for-consultants
---

# EIB spreadsheet mapping when an AI assistant drafts the load

Inbound EIBs load spreadsheet rows through a web service. This guide uses Workday’s payroll-input example to show ID type versus ID value, then uses the Deployment Agent SOAP example so a parent-element fault is not treated as a mapping success.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   7 min read
-   Published November 16
-   By Kiweely

An Enterprise Interface Builder (EIB) spreadsheet is a mapping document, not a free-form grid. Workday’s payroll-input example shows the pattern consultants should demand from any AI draft: name the web service, edit the template model so reference ID types are visible, generate the spreadsheet, keep the XML Spreadsheet 2003 format, and fill ID type and ID value from **Integration IDs**. A model that says “put the deduction name in column C” is not a mapping.

Security in that example is the **Integration Build** domain in the Integration functional area, plus **My Reports** in the System functional area to download the template. Build and launch in a non-production tenant. Deployment Agent can explain a SOAP fault in Implementation, Preview, Sandbox, or Customer Central. It does not launch the EIB.

## Separate the three Workday patterns people call “mapping”

| Pattern | What it maps | Where it is configured |
| --- | --- | --- |
| Inbound EIB template model | Spreadsheet columns to a web service operation, including reference ID type and value |  **Template Model** on the integration system, then **Generate Spreadsheet Template** |
| Calculated field on an EIB or document transform | Tenant data rewritten before it is sent or compared |  **Create Calculated Field**. Workday lists EIB and document transformation as a calculated-field use. |
| Outbound EIB fed by a custom report | Report columns to a file |  **Enable As Web Service** on an advanced or search report. Copy a standard report first so a Workday update does not break the file. |

An AI draft that mixes these will tell you to “map the calculated field in the spreadsheet ID column.” Those are different objects. Prove which one the load actually needs.

## Inbound payroll example, field by field

The example loads many payroll inputs or off-cycle payments, including a company deduction (parking, code `WE_PARK`) and a Workday-owned deduction (withholding order employer fee). One spreadsheet holds both.

1.  Create an inbound EIB. Payroll inputs use web service **Import Payroll Input**. Off-cycle payments use **Import Payroll Off-cycle Payment**.
2.  Create the company deduction and note its code.
3.  Open **View Integration System** for that EIB.
4.  Related actions: **Template Model**.
5.  Open **Payroll Input Data+** or **Off cycle Input Data+**, then **Edit Template Model Area**.
6.  On the row labeled **Deduction**, select **Separate Type Column**.
7.  Return to the template model and choose **Generate Spreadsheet Template**.
8.  Download from **My Reports**. Keep **XML Spreadsheet 2003**. Changing the format is how mappings silently fail on launch.
9.  Fill rows. The published sample is:

| Spreadsheet Key | Row ID | Deduction - ID Type | Deduction-ID Value | Amount |
| --- | --- | --- | --- | --- |
| 1 | 1 | Deduction\_Code | WE\_PARK | 25 |
| 2 | 2 | Workday\_Deduction\_Code | W\_WOFER | 50 |

1.  Look up ID types and values on **Integration IDs**. Do not copy codes from a slide.
2.  Complete the rest of the payroll input or off-cycle payment fields.
3.  Launch the spreadsheet upload.

**Separate Type Column** is the mapping decision. Without it, a company code and a Workday-owned code look like the same kind of identifier. With it, the sheet has a type column and a value column, and each row says which reference ID type it is.

## What to reject in an AI-drafted sheet

| Draft says | You do instead |
| --- | --- |
| “Use the deduction name the business uses.” | Use the reference ID type and value from **Integration IDs**. Names are not the ID type. |
| “Save as xlsx so it is easier to edit.” | Keep XML Spreadsheet 2003, as the example requires. |
| “One ID column is enough for Workday and custom deductions.” | Turn on **Separate Type Column** for Deduction so `Deduction_Code` and `Workday_Deduction_Code` can both load. |
| “Point the outbound file at the standard Worker report.” | Copy to a custom report, then enable that copy as a web service. |
| “The parent element is in the XML, so the load is valid.” | Workday’s SOAP example says a parent-element fault can be a missing child or a security gap. |

## When the launch returns a SOAP fault

Workday’s Deployment Agent SOAP example is an expense report, not payroll, but the method is the one to reuse. The fault is:

> Validation error occurred. The field Expense\_Report\_Data is required.

The consultant had already confirmed `Expense_Report_Data` was in the XML. The topic says Workday SOAP sometimes raises that generic parent error when a child element is missing or a security requirement is not met.

Ask in **Deployment Agent** with the CRAFT split the example uses. First the role and the service, then the exact string and what you verified:

> I am an integration consultant working on a Financials implementation. I am calling the Submit\_Expense\_Report web service and receiving a ‘Validation error occurred’ message regarding a missing field.

> The error says: ‘The field Expense\_Report\_Data is required.’ I have confirmed this field is in my XML. What are the most common hidden missing fields or security issues that cause this specific SOAP fault for this service?

Then, if you need permissions:

> List the specific functional area and security domain permissions my Integration System User (ISU) needs to initiate this specific web service.

For an EIB, swap in the operation you actually launched (`Import Payroll Input` or `Import Payroll Off-cycle Payment`) and paste the message from the integration event. The published troubleshooting sample for a different path is:

> I am getting a SOAP error while using Object Transporter to migrate Payroll data. What are the common causes for this error and how do I fix them?

That sample does not paste the fault. Prefer the longer SOAP example: exact message, plus what you already ruled out.

The agent returns areas to check. You still compare them to **Integration IDs**, the template model, and the integration system’s security. Then rate the answer with thumbs up or thumbs down.

Calculated fields that override data for an EIB or document transform are a separate edit in **Create Calculated Field**. They are not columns you invent on the spreadsheet after generation. If the agent tells you to add a calculated field, prove it with **Calculated Field Exception Audit** before the next launch. Numeric fields display up to 6 decimal places. A payroll amount that looks right in chat can still round differently in the field definition.

## Outbound files that start from a report

If the “mapping” is an outbound EIB, the report has to be a web service:

-   Advanced or search report only.
-   **Enable As Web Service** on the Advanced tab.
-   Namespace format `urn:com.workday.report/` plus the report name. Renaming the report does not change the namespace. Editing the namespace breaks callers until you update them. Workday does not enforce unique namespaces.
-   CSV drops group headings and can reorder columns. Simple XML flattens instances to strings and drops times on date-only fields. Workday XML is the literal payload and includes XSD and WSDL URLs.
-   The report owner’s username cannot contain a backslash or GET requests fail.

Agree the output type with the consumer before the first production file. Changing it is a new mapping.

## Proof before you call the load done

1.  Template model shows **Separate Type Column** where more than one reference ID type can land in the same element.
2.  Every ID type and value on the sheet exists on **Integration IDs** in this tenant. Codes from Production are not automatically the codes in a partly loaded Sandbox.
3.  The file is still XML Spreadsheet 2003.
4.  A two-row test (one company-specific ID, one Workday-owned ID) launches and the integration event has no validation fault.
5.  If a SOAP fault named a parent element that you can see in the file, you checked child elements and domain permissions before editing the sheet again.
6.  Outbound reports used by EIBs are custom copies with a recorded namespace and output type.

## Watch Kiweely Vine build and load an EIB

![Workday's execution summary for the cost center EIB Kiweely Vine loaded: 18 records processed, none failed](https://kiweely.com/guides/ai-workday-eib-mapping-for-consultants/media/vine-eib-cost-centers-d2a43dc234d0.webp)

From the film: 18 records processed, none failed.

Kiweely Vine takes a messy cost center spreadsheet, lists its problems, asks only the business questions, builds the EIB on Workday’s own template and launches it in a Workday Development tenant. Workday reports 18 processed, 18 loaded, 0 failed. 97-minute recorded run, first-use setup included.

[Watch the film (13 min)](https://www.youtube.com/watch?v=o1lMLI_Pbsc) · [Start for free](https://kiweely.com/sign-in?intent=signup)

## Frequently asked questions

### Can the assistant generate the spreadsheet for me?

The example generates it from the template model with **Generate Spreadsheet Template**, then you download it from **My Reports**. A spreadsheet created outside that path will not match the operation.

### Is Object Transporter the same as an EIB?

No. The sample prompt uses Object Transporter for migrating Payroll configuration. The payroll example uses an inbound EIB against **Import Payroll Input** or **Import Payroll Off-cycle Payment**. Say which one failed.

### Do I put calculated fields in the ID type column?

No. ID type and ID value come from **Integration IDs**. Calculated fields are definitions on a business object that reports, processes, and some integration transforms can call.

### What if Deployment Agent is not enabled in this tenant?

You can still complete the template-model steps. The SOAP prompts require the **Deployment Agent** task in a non-production or Customer Central tenant, with Tenant Inspection when you need a tenant-aware answer. The integration event remains the source of the error text either way.

## Sources checked

Frontmatter pages, fetched 2026-11-16. The deduction rows and the SOAP prompts are the published examples.

## Sources checked

-   [Example: Include Workday and Company-Specific Deductions in EIB Spreadsheets](https://doc.workday.com/admin-guide/en-us/payroll/payroll-input/sls1518168222109.html)
-   [Example: Troubleshoot a SOAP Error with the Deployment Agent](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/example--troubleshoot-a-soap-error-with-the-deploy.html)
-   [Setup Considerations: Calculated Fields](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/calculated-fields/ova1547251060954.html)
-   [Concept: Reports as a Service (RaaS)](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/reports-as-a-service-raas-/dan1370796320263.html)
-   [Deployment Agent Sample Prompts for Implementation Environments and Customer Central](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/reference--deployment-agent-sample-prompts-for-imp.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Financials and payroll prompts for the Workday Deployment Agent Workday’s samples already cover a Financials calculated field, an Object Transporter payroll error, a Submit\_Expense\_Report SOAP fault, and a Payroll Specialist field-access case. This guide quotes those prompts and shows the few fill-ins that stay inside the same CRAFT rules.](https://kiweely.com/guides/workday-ai-prompt-library-financials-payroll)
-   [### Prove an AI-suggested Workday calculated field before it drives a condition rule Deployment Agent’s documented example suggests Evaluate Expression logic for a Worker field and you build it in Create Calculated Field; Configuration Cloud (partner early access) can make approved changes. This guide shows how to prove the field before a rule or integration uses it.](https://kiweely.com/guides/ai-workday-calculated-fields-condition-rules-proof)
-   [### Custom reports and RaaS when an AI assistant is helping you build them Advanced and search reports can be enabled as web services. Copy a standard report before you expose it, keep the namespace stable, and use Deployment Agent only to find which custom reports exist in the tenant. You still choose the output type and the security.](https://kiweely.com/guides/ai-workday-custom-reports-raas-for-consultants)
-   [### CRAFT prompts for the Workday Deployment Agent Workday’s Deployment Agent sample-prompts topic, updated 2026-11-06, says accurate answers come from five CRAFT elements. This guide restates that method, shows which elements you can omit, and rewrites the published samples so an administrator can see what each word is doing.](https://kiweely.com/guides/workday-deployment-agent-admin-prompt-patterns)

### More guides on Integrations and APIs

[All 89 guides](https://kiweely.com/guides#integrations)

-   [Run Workday Studio AUnit Before You Accept AI Edits](https://kiweely.com/guides/workday-studio-aunit-before-ai-edits)
-   [What AI tools can a Workday consultant use to build reports, calculated fields and EIB loads faster?](https://kiweely.com/guides/ai-tools-for-workday-reports-calculated-fields-eib)
-   [Which Workday Integrations May Auto-Remediate](https://kiweely.com/guides/which-workday-integrations-may-auto-remediate)
-   [An Integration Run Book Assistants Can Query](https://kiweely.com/guides/workday-integration-run-book-for-assistants)
-   [When Workday Integrations Should Leave the Tenant](https://kiweely.com/guides/when-workday-integrations-leave-the-tenant)
-   [Workday API Rate Limits When Many Employees Ask Questions in Chat](https://kiweely.com/guides/workday-rate-limits-when-employees-ask-in-chat)
-   [Workday SFTP File Contracts, PGP, and Overnight Failures](https://kiweely.com/guides/workday-sftp-file-contracts-pgp-overnight-failures)
-   [Recover Workday Integration Attributes After a Sandbox Refresh](https://kiweely.com/guides/workday-sandbox-refresh-integration-attributes)

### From the blog on Integrations and APIs

[All posts](https://kiweely.com/blog)

-   [Untangling Inherited Workday Studio Integrations: A Practical Modernization Playbook](https://kiweely.com/blog/untangling-inherited-workday-studio-integrations)
-   [Why Most Workday Studio Integrations Ship Without Tests](https://kiweely.com/blog/workday-studio-integrations-without-tests)
-   [The Slow Change Cycle in Workday Studio (and How to Break It)](https://kiweely.com/blog/workday-studio-slow-change-cycle)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
