Skip to content
KiweelyKiweelyKiweely

Why a Delivered Workday File Was Still Rejected

Workday can mark a file generated and delivered while the carrier’s companion guide still rejects segments, codes, or coverage. Those are different tests.

  • Checked against Workday on
  • Applies to Workday Extend
  • 9 min read
  • Published
  • By Kiweely
On this page
Why a Workday overnight integration “succeeded” and the vendor still rejected rows

Workday’s integration event and the vendor’s rejection file answer different questions. The event answers whether Workday generated the output and, for an outbound process with a delivery step, whether that file was handed to the endpoint you configured. The vendor answers whether each row satisfies that vendor’s companion guide. A night can be “Completed” in Workday and still produce a rejection of specific employees at the carrier or the payroll provider. That is not a contradiction in the event. It is a second test Workday’s benefits course tells you to run, and which the event status does not run for you.

Kiweely Roots is coming next and is built around that second test: the rows the other system rejected, reproven on Sandbox, held for approval when the integration is payroll, benefits, or tax. You do not need Roots to stop treating “Completed” as acceptance. This guide is the Workday behavior.

Two statuses that get collapsed into one email

An outbound integration business process, as Workday’s integration business process guidelines describe it, has a service step that fires the integration and, for outbound work, generates the file. A later document-delivery step sends that file to the external endpoint, such as an SFTP server or a web service. Workday’s example of a success notification is an email to payroll that the weekly file was generated and delivered. “Delivered” in that sentence means the delivery step finished. It does not mean the vendor posted every row.

When the file never arrives, Workday’s own troubleshooting table tells you to look at the process monitor and at both the fire-integration event and the deliver-document event. The cause it names is a failure before delivery, a failure of the delivery step, or the endpoint address and credentials. That is the right procedure for “the folder is empty.” It is the wrong procedure, used alone, for “the folder has a file and the vendor rejected 40 employees.” The file arrived. The rows did not pass the vendor’s rules.

The connector course lists what the background process page can show after a launch: Aborted, Completed With Errors, Completed With Warnings, Not Run due to Exceptions on Future Process, and the successful completion state operators summarize as completed. You also get processing time, a link to the integration event, who started it, an output-files tab for the generated file, and a messages tab. None of those fields is “carrier accepted this subscriber.” The output file is the file Workday produced. The vendor’s rejection is a different document, usually retrieved later or returned on a different channel.

What “Completed with errors” already admits

Studio’s logging course separates message severity from business acceptance, and it is the cleanest statement that a finished event can still be a bad file.

Severity on the message What the course says processing does Event status
Severity on the messageInfo What the course says processing doesContinues Event statusCompleted
Severity on the messageWarning What the course says processing doesContinues. A record or file may be skipped or included. Event statusCompleted with warnings
Severity on the messageError What the course says processing doesContinues. The record or file should be skipped. Event statusCompleted with errors
Severity on the messageCritical What the course says processing doesStops Event statusFailed

The course adds the caveat that matters: severity changes the event status, not the assembly’s behavior. The developer has to skip the bad record or stop. A global handler that never fires, and no error-severity message, produces Completed while a row the vendor will hate is still in the file. Completed with errors is the status you get when someone did emit an error-severity message and let processing continue. Operators who only page on Failed will not see either case until the vendor writes back.

The same course tells you not to log the raw message in production. People with access to the integration event can read it, and it can contain confidential data. So the event is also a poor place to stuff the vendor’s row-level rejection if that rejection contains the same data. Store the vendor outcome as a count and an identifier your support process is allowed to see, and keep the row detail in the system that already holds it. That is a design choice. Workday’s warning is the reason.

The benefits case, where Workday names the gap

Cloud Connect for Benefits is where Workday documents the vendor’s rules as a first-class test, not as an afterthought.

Design benefits connectors describes the ANSI 834 file many U.S. health plans exchange: segments, loops, a header, a trailer. Providers use the same format and different values. They publish companion guides. Workday says the companion guide does not list your integration attributes for you. You map Workday values to the endpoint’s values with attributes, maps, and field overrides, and you confirm the mapping by testing. Loop identity is a convention between Workday and the provider, not a label printed on each line.

Test benefits connectors splits testing into three cycles:

Cycle What it proves What a “success” here does not prove
CycleConnectivity What it provesA file can be delivered to the endpoint, or retrieved from it. What a “success” here does not proveThat the contents are valid. Delivery is this cycle.
CycleFile format What it provesThe file has the right records, segments, and fields, with valid types and codes, and the right coverage or termination status. What a “success” here does not proveThat Workday’s event status knew about the format. The course says functional data problems can cause these issues, not only a misbuilt connector. Use reports to see whether Workday has the data and whether the integration wrote it.
CycleData and events What it provesLife events and other scenarios appear correctly in the output. What a “success” here does not proveThat last night’s production population matches the scenario you tried.

Common file-format issues on that page are the vendor rejection, written from Workday’s side: missing or incorrect records, segments, or fields; invalid data; blank values in required fields; incorrect data types; incorrect codes or identifiers; subscribers with the wrong coverage or termination status. If your carrier’s rejection says a required element is empty or a code is not in its guide, you are in cycle two, even when cycle one and the integration event are green.

The template you should be on, per the create-connectors chapter, is ANSI X12 834 version 2 for an 834 file. Workday says not to use named vendor templates that also produce 834 output, because those are not enhanced and will be deprecated. The version-2 template’s services include the transformation that produces the file, loop attributes, a sequence generator for the file name, a delivery service, and document retention whose default is 30 days. You enable one transmission mode at a time: changes only, actives only, or one of the full-file variants. The wrong transmission mode is a file the carrier can reject or, worse, accept as a full replace you did not intend. The event can still say the file was delivered.

Workday maintains end-to-end templates and says it updates them when the endpoint’s requirements change. That reduces this class of failure for carriers in the catalog. It does not close it. The design chapter’s point about companion guides is that two carriers on one standard still disagree on values. A template update on Workday’s release schedule and a carrier edit on a Tuesday are not the same clock. When they diverge, the event stays green and the rejection file does not.

There is a practical way to see one person before you see four hundred. The debug service on most benefits templates can include or exclude specific workers and dependents for a launch. Use it to reproduce one rejected subscriber. Mask support files when you have to send something to Workday Support. Cloning the integration system before you change a template is how you keep the previous configuration. None of that is automatic. It is the manual version of “rerun the rows that failed.”

Payroll vendors follow the same split, with less of it written down as a single chapter

This guide does not invent a payroll provider’s acknowledgment codes. Workday’s public pages read for this article do not give one table of “what ADP rejects.” The structural facts that do transfer are:

  • Outbound delivery confirms the transport, and Workday even tells you to test the transport on its own: connect, list the directory, or send a test file, and require a success message before you launch.
  • A transport test can succeed and say nothing about row content.
  • End-to-end connectors are also how Workday describes bulk transport of payroll-adjacent and tax files, on the planning chapter’s list of uses.
  • Studio severity can mark Completed while a row that should have been skipped is still in the output, if you never raised an error.

So a payroll vendor’s row rejection is the same kind of event as the carrier’s: it happens after delivery, it is authoritative for whether that vendor will pay or enroll, and it will not rewrite Workday’s integration event unless you build a later inbound integration to load the acknowledgment. If you have that inbound integration, its event is the acknowledgment load, not a correction of last night’s outbound status. Last night can remain Completed. The acknowledgment is a new event. Reporting has to join them on purpose. If you do not join them, the operations mailbox and the Workday status will disagree forever.

What to change in operations this week

  1. Split the alert. Page on Failed and on delivery-step failure, because the file did not leave. Separately, ingest the vendor’s rejection or acknowledgment. Do not use one inbox rule for both.
  2. For benefits, treat the three test cycles as production monitors, not as a project phase. Connectivity is the delivery step. File format is the vendor response. Data and events is how you reproduce a life event that went out wrong.
  3. When the vendor rejects a population, rerun those workers with the debug service or an equivalent filter. Compare the segment to the companion guide. Confirm the value exists on a Workday report before you change the map. The course’s order is: is the data in Workday, and did the integration write it.
  4. Do not “fix” a green event by resending the same file. If the map is wrong, the second send is wrong again. Resend only after the format test for the rejected workers passes.
  5. Put a person in front of payroll and benefits changes. Workday’s business process can require approval before the fire-integration step. Use it when the review matters. An approval of an unchanged regenerated file is not a review of a new map.
  6. Keep row-level vendor payloads out of broad logs. Studio’s warning applies to your acknowledgment loader too.

Where an outside platform fits, without skipping the Workday test

An outside platform is justified when you want the vendor’s rejection, not the Workday event, to start the repair, and when you want that repair retested on the rejected rows before anyone approves a new send. That is what the Roots page specifies for benefits and payroll, and the product is coming next. It does not replace the 834 template when the template matches the carrier. Workday maintaining the template is a reason to stay. Roots is a reason to add a loop the event does not have: rejection in, Sandbox proof, approval, then a new file.

If you build that loop yourself, the behavior to copy is the test chapter, not a retry button. Connectivity you already have. The missing cycle is file format, on the workers the vendor named, against the guide that vendor published.

Register interest in Kiweely Roots if that loop is the work your team repeats after every open enrollment. Until then, the event status is necessary and it is not sufficient. The vendor’s file is the other half of “succeeded.”

Sources checked

Let Workday check the work.

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

Get the next guide in your inbox.

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

We’ll email you once to confirm. Unsubscribe in one click from any issue.