Workday Business Process Rescind, Cancel, and Correct: What Each Reverses

In Workday, Cancel stops an in-progress business process before it reaches its completion step, Rescind reverses an event that has already passed its completion step and restores the underlying object data to its prior state, and Correct edits effective dates or initiation inputs on an existing event without destroying and recreating the transaction. Choosing the wrong action either wipes out completed onboarding and compensation subprocesses unnecessarily or leaves committed staffing and payroll data active in the tenant.

How the completion step separates Cancel from Rescind

Every Workday business process definition designates one step as the Completion step (marked Yes in the Complete column on the View Business Process Definition page, or defaulting to the final step when none is explicitly set). The moment a business process finishes its completion step, Workday commits the transaction data to the database and exposes it to downstream modules such as Workday Payroll, Financial Accounting, and outbound integrations—even if post-completion onboarding, document review, or to-do steps remain open.

When and how to use Cancel

Use Business Process > Cancel from the event's related actions when an event was initiated in error—such as starting a job change on the wrong worker—and the event has not yet passed its completion step.

Parent versus subprocess cancellation

How Workday handles a cancellation depends on whether you target the parent event or an individual subprocess:

• Canceling the parent business process: Workday immediately terminates the parent workflow, skips any pending subprocesses regardless of their status, and cancels any subprocesses that have already completed inside that parent transaction.
• Canceling a standalone subprocess before parent completion: Workday marks the subprocess as Manually Skipped and allows the parent business process to continue. Even if the subprocess was configured as required, canceling it after the parent completion step still leaves the parent completed.
• Canceling a subprocess that is the Completion step: If a subprocess (such as Request One-Time Payment inside a Hire event) is designated as the parent's completion step and you cancel only that subprocess while earlier steps finish, Workday sets the subprocess to Manually Skipped and marks the parent Hire event complete.

For high-volume cleanups, administrators can run Mass Cancel Business Processes to cancel parent or child processes in bulk, or Mass Cancel Review Document Step to clear up to 2,000 lingering Review Documents steps on In Progress or Successfully Completed onboarding events.

When and how to use Rescind

Once a business process passes its completion step, Cancel is no longer available on the parent event. To completely undo the transaction—for example, when a candidate declines an offer after the Hire completion step has already executed, or when a Termination must be reversed—select Business Process > Rescind from the event's related actions.

When you rescind a parent event, Workday cascades the reversal across every subprocess called as an action within that workflow. For example, rescinding a Termination that triggered a Request One-Time Payment severance subprocess rescinds both the termination and the payment. You can also rescind certain subprocesses individually without rescinding the parent event; inspect the Business Process Configuration Options report to see which actions each business process type supports.

For batch loads that went wrong, run Mass Rescind Business Processes. Its Business Processes Loaded by EIB prompt surfaces integration events loaded via Enterprise Interface Builder where at least one event can be rescinded. Always constrain the prompt using In Date Range, By Integration System to avoid unintended reversals.

When and how to use Correct

Use Business Process > Correct when the transaction itself is valid, but an attribute entered on the initiation step—such as the effective date, termination reason, hire reason, or supervisory organization—needs to be fixed.

Key behaviors of Correct on staffing and operational events include:

• Bypasses re-approval: Corrections save immediately without re-triggering the main approval chain or subprocess approvals, and they do not send standard step notifications unless custom or alert notifications are explicitly configured for Correct. For this reason, restrict the Correct action on the business process security policy to administrators.
• Targets only the initiation step: On events like Hire or Termination, Correct only opens the initial step fields. To modify data captured inside a child subprocess (such as Propose Compensation Hire), navigate to the specific subprocess event and correct it directly.
• Out-of-order corrections: Workday supports out-of-order corrections on most staffing events (Hire, Change Job, Termination, Add Additional Job, Change Work Space) without forcing you to rescind later events in the worker's history, provided two rules hold:
  1. You do not change the worker's position or supervisory organization on a Change Job, or the pre-hire/position on a Hire.
  2. The corrected effective date remains in chronological sequence—on or after the immediately preceding staffing event and on or before the next subsequent staffing event.
• Subsequent Processes inspection: When correcting an event on a worker who has later staffing actions, expand the Subsequent Processes section on the Correct Business Process page to review later moves, reorganizations, or job changes. Note that except for Change Organization Assignments for Worker (which propagates corrected organization values forward until a later event changes that organization type), Workday does not automatically copy corrected field values onto later staffing events.

If you need to move a worker's hire date across existing downstream events, use the dedicated Request Worker Start Date Correction task (Correct Worker Start Date business process) or check Business Process > View Hire or Contract Start Date Correction Conflicts on the Hire event first.

Downstream impact on Payroll and Integration Transaction Logs

Every Cancel, Rescind, and Correct action writes a timestamped entry to the business process audit trail and affects downstream consumers differently:

1. Workday Payroll and Retro Calculation:
   • Rescind or Correct on completed events: If a worker has already been paid in a completed pay period and you rescind a Change Job, rescind a Request One-Time Payment, or correct a Hire or Change Job effective date into a prior pay period, Workday flags a retroactive event. The next time you run Run Retro Pay Calculation, Workday compares the prior pay results against the restored or corrected staffing state and generates retro differences.
   • Blocking Payroll results: Workday blocks you from rescinding a Hire or Position event if the worker has completed on-cycle or off-cycle payroll results, time tracking actuals, or benefit deductions tied to that employment record.
2. Core Connector and Transaction Log Integrations:
   • Subscription-based integrations (such as Core Connector: Worker or Document Delivery integrations subscribed to the Transaction Log service) evaluate transaction status changes.
   • A Correct action generates a Corrected transaction log entry, while a Rescind action generates a Rescinded entry (and can also trigger a configured Workday Orchestration on Cancel, Rescind, Correct, or Deny). If your outbound integration only subscribes to Successfully Completed events without handling Rescinded or Corrected log types, downstream third-party systems will retain stale hires or terminations until reconciled.

Troubleshooting: Why Workday blocks a Rescind or Correct

When Rescind or Correct fails with a validation error or does not appear in the related actions menu, work through these checks:

1. Verify Business Process Security Policy permissions: Open View Business Process Security Policy for the event's business process type. Confirm your security group is listed under Who Can Do Actions on Entire Business Process for Cancel, Rescind, or Correct, and that pending changes were activated via Activate Pending Security Policy Changes.
2. Resolve dependent chronological events (LIFO order): Workday enforces referential integrity across effective-dated worker history. You cannot rescind a Hire while the worker has a completed Change Job, Termination, completed pay result, or active benefit election chronologically downstream. Open Worker History > View Worker History, inspect all events after the target event, and rescind dependent events in reverse chronological order (last-in, first-out).
3. Check uneditable structural fields on Correct: If a field is grayed out during Business Process > Correct, check whether it is structurally locked. On Change Job, you cannot correct the supervisory organization, job/position, or headcount options; on Termination, you cannot correct the Close Position checkbox; on Hire, you cannot change the pre-hire or position without rescinding and re-initiating.
4. Clear Hire Date correction conflicts: Before moving a start date later, run Business Process > View Hire or Contract Start Date Correction Conflicts from the Hire event's related actions to identify benefit, time off, or compensation events whose effective dates would fall before the proposed hire date.

How kiweely fits

Before an administrator rescinds or corrects a staffing event in production, tracing every dependent subprocess, downstream payroll lock, and integration subscription by hand across Worker History and Full Process Record takes significant time. kiweely connects to your Workday tenant to inspect the event hierarchy, surface chronological blockers and security policy gaps, and verify how a proposed Cancel, Rescind, or Correct will affect downstream staffing records and integrations. 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

Can you undo a Rescind or Cancel in Workday?

No. Once you confirm a Cancel or Rescind action on a business process event, Workday permanently terminates or reverses that instance. To reapply the change, you must initiate a new business process event and complete its steps again.

Why is Rescind missing from the Business Process related actions menu?

Either the event has not yet passed its Completion step (in which case Cancel is the valid action), the business process type does not support rescinding (verify via the Business Process Configuration Options report), or your security group lacks Rescind permission on the business process security policy.

Does correcting a staffing event re-trigger approvals or notifications?

No. Business Process > Correct commits changes directly without routing the event back through approval steps or subprocesses, and it suppresses standard step notifications unless an administrator has specifically configured custom notifications, alerts, or orchestrations to fire on the Correct trigger.

When can I correct a staffing event out of order without rescinding later events?

You can correct Hire, Change Job, Termination, and Change Work Space events out of order as long as you do not change the worker's position and the new effective date stays between the immediately preceding and immediately following staffing events in the worker's history.