A payroll mapping fix that goes to Production because the integration “completed” is how a bad earning code becomes a bad paycheck. The extract Workday built is evidence of what you sent. The corrected extract, on Sandbox, against the same workers, is evidence of what you are about to send. Production waits on the second file.
Creating PECI Integrations describes the Payroll Effective Change Interface as a full stack: each change for each worker, with effective date and entry date, inside peci:Effective_Change, in sequence. Section and field flags say whether the value was added, updated, or deleted, and an updated field can carry priorValue. Workday also says you can see payroll errors at the worker level without leaving Workday. That is the grain a fix should use. A green launch of fifty thousand workers does not identify the forty whose cost center or pay component mapped to a code the vendor rejected.
PECI does not decide the vendor’s layout. Payroll Vendor is a reporting label and does not change the XML. If the vendor is not in the menu, you select Other. Field overrides and calculated fields are how internal values become the external code, and Workday tells you to test the calculated field in a report before it is on the integration. Staffing History - All is called out as a field that can damage performance. The planning questions include how many clones you need. The course’s typical answer is one clone for testing and manual runs, and one for the schedule. Sandbox is that test clone’s home. See also the change-detection rules in what breaks the night before pay. The test launch has to use the same detection method as the run that failed, or you will “fix” a population the vendor never received.
What to put in front of the approver
| Piece | Why it has to be the real rows |
|---|---|
PieceThe workers the vendor rejected, or the workers whose priorValue and new value are wrong |
Why it has to be the real rowsA sample employee with a clean history hides a retroactive change in the effective stack. |
| PieceThe Sandbox output for those workers after the override or map change | Why it has to be the real rowsPECI can emit every change in order. The approver should see the sequence, not only the top of the stack. Payroll Interface reports the net change only, and some vendors require that. Match the template you will send. |
| PieceThe pay group, period, and detection method | Why it has to be the real rows“All changes effective in the period” and “entered since the last successful run” return different people. A future-period effective date is excluded until that period is the one being processed. |
| PieceWhat the change does, and the way back | Why it has to be the real rowsA payroll correction is not done when the file looks plausible. It is done when you can say what the data will become and can reverse that change. |
Overview of Third-Party Payroll lists the categories vendors need, including compensation, benefit elections, absence, time, withholding orders, and tax elections. A mapping fix in one of those categories changes pay. Withholding orders and tax elections are covered in files that succeed while the amounts are wrong. Do not treat a withholding-order fix as a directory tweak.
Workday’s security chapter for integrations is the other half of the proof. Run the test as the integration system user that will run Production, and compare it with a person who can see the data. Missing workers are often missing permissions. One integration system user per integration system is the recommendation, with only the domains that integration needs.
How Roots states the same gate
Kiweely Roots (coming next) publishes this gate for payroll, benefits, and tax: prove the fix on Sandbox with the rows that failed, then wait for approval. The page’s payroll example is a change that touches payroll, so it waits even after the Sandbox test. Before and after are shown, and the change goes back in one step. Directory and reporting feeds are the other setting: fix, test, turn the feed back on, and tell the owner. You can move any integration between those settings.
The integration that runs is tested code. Agents design, build, test, and fix that code. They are not the path the payroll rows travel. Nothing from the run is kept except times, counts, and outcomes. Each integration has its own API client, scoped to what it reads. Claude, ChatGPT, and Gemini can ask Roots, over MCP, whether last night’s file went and whether a payroll change is still waiting. The wait is the product rule for payroll.
Roots is coming next. There is no price on the page. Register interest at kiweely.com/roots and say which pay file you want proven on the failed rows before anyone approves Production. This article does not describe an ADP or UKG API. Workday’s pages checked for it do not publish one, and Roots does not fill that gap with an invented layout.