Termination Process

Hi. There is a feature that turns off direct deposit information based on the relationship status. We could not get it to work and I was informed that in order for it to work the status has to be changed with the Termination Action and our Final Termination status is being changed with an Update Action.

Our process is the manager enters the termination request. This uses the Termination Action and updates the Relationship Status to Termpend. Once payroll issues the final check the date last paid field will get updated and there is an IPA that will run that will update the status to Term Final. This is done with an Update Action.

Can I ask how others are doing their termination process? Are you using the end Direct Deposit Information feature? If so do you use Termination Action for both the Term Pend and the Term Final? Trying to use as many of the automation features as we can.

Thanks

Syl

Find more posts tagged with

Accepted answers

All comments

Rachel Lake

Sorry I don't have an answer for you - but thank you for this post, because it appears we have the exact same issue! We do a termination action to put someone in a term pending status, but then a ChangeRelationshipToOrg 45 days after the termination date. So it looks like ChangeRelationshipToOrg doesn't inactivate bank details either. Interested to see what others say. When we first talked through the process, we didn't want to do two termination actions because that would mess with reporting.

Rachel Lake

Did you submit a ticket for this already? Is that where you were told it must be a termination action?

Sylvie Vincenti

Hi. I don't know anyone that doesn't do a termpend and then a termfinal. I would think Infor should have 2 separate actions for these. One for the request for termination and then do the termination action to do the final term. Or at least base the inactivating the direct deposit on the status and include the Update and ChangeRelationshipToOrg action to the logic along with the termination action

Like you we feel doing 2 termination actions would lead to issues with reporting. We already have enough issues with doing reporting in V11

I did not put in a ticket. We are still working on our implementation, and this was the answer from our Infor consultant. that the process is working as designed and it is not an issue.

Rachel Lake

Thanks for the response. I'll probably submit a ticket just to see what they come back with. W only went through implementation a few months ago; we discussed this process with our Infor consultant, and I don't recall them having any hesitations about a term, then a ChangeRelationshipToOrg.

If they come back with "working as designed" it'll be a case for an enhancement request.

robert-canham

We use the terminate action for both Term Pend and for Term Final just with different reason codes. We also do a timed term final that gets picked up by a processflow and updated that way. By using the reason codes, we can differentiate between them if needed when reporting on history.

Rachel Lake

Robert, did you do that specifically because you knew ChangeRelationshipToOrg or Update wouldn't work? Or was there a particular reason you chose termination for the term final?

robert-canham

I don't remember if we knew about the direct deposit inactivation, we just kept it terminate since it was still part of the termination process. We did it similarly when we did this in S3.

Karen Russell

That's very odd -- before we brought Payroll into Infor (while we had GHR only), we used the Term Pend / Term Final trick, where the Termination request action put them in Term Pend (set to keep the Work Assignment active), and then we used an ISD Update action later to swap them to Term Final (set to inactivate the Work Assignment). The automation of inactivating the Work Assignment based on the RelationshipStatus worked just fine even though it was driven by an Update action on the Employee business class. Why would it work for Work Assignment inactivation, but not Bank Details inactivation?

This is making me wonder if the Bank Details inactivation issue (bug?) is why our Payroll implementation consultant told us that we couldn't use the Term Pend / Term Final process anymore when we went live with Payroll. They made us update the process so that Term Pend isn't used at all, and Term Final doesn't automatically inactivate anything except the actor. They then built two process flows to inactivate Work Assignments and Bank Details 30 days after the term date (one flow for each). Since the flows have only been turned on for a few weeks, though, I'm not sure how they'll handle retroactive terms (e.g. submitted/processed in March, but effective date in January).

Tl;dr: our termination / final check payout / inactivation process is a pain; it doesn't seem like Infor has a way for it to NOT be a pain; we don't use the End Bank Details setting on the RelationshipStatus, possibly for the same reason you can't, which may be a bug; we use a process flow to inactivate Bank Details on a 30-day delay post-term.

Rachel Lake

Very odd! We were told that most people used a Term Pend/Term Final process in GHR. I'll also keep you updated with the result of my ticket.

Jennifer Stroud

We use a ChangeRelationshipToOrg action for the term pending and leave the final term action "pending" in the inbasket until after their final check has been processed. This avoided having two term actions, but allowed us to track term pending with a term date.

Sylvie Vincenti

Thank you everyone for your responses. You would think something as basic as terminations wouldn't be so complicated in V11. I find it to be standard on how everyone processes terms. But looks like they have everyone doing it differently.

Jennifer.. your process makes sense. Is the ChangeRelationshipToOrg for the term pending automated by the manager entering the termination action request? And how is the termination action processed when the final payment is made? Is there an IPA that runs that picks up a flag set to allow final termination or is it a manual process? Would you be willing to share your process. Not sure if Infor will let us change what they have set up for us already but worth a try if I can give them specifics of what would be needed to make it work. This process would still allow us to identify who are in term pend status, not have to have 2 term actions and also allow us to use the automation for the direct deposit ending for our payroll department that is already built into the system without needing to create a special program to do so.

Rachel Lake

Just an update - Infor did respond to my ticket with "working as designed." So only a termination action is inactivating bank details, not changerelationshiptoorg. Here's the enhancement request - please endorse!

mingle-portal.us2.prd3.inforcloudsuite.com/.../

Noe Ramos

we also use the Term pending and then go back with ISD to term final method for last paycheck processing.

we use ChangeReltoOrg mainly for part time to full time changes only.

looking at the LPL i see where the termination process is stated to end bank details.

looking at the section for ChangeReltoOrg i do not see any mention of bank details. I could see you creating an action for your ChangeReltoOrg ipa to include actions to update the bank details as you are wanting. that would be your best bet to have done quicker than the enhancement request but i do see what you are saying.

below are the actions and rules for the ChangeReltoOrg from the lpl viewer.

InitiateRequest Rules

include CreatePositionPlanPendingRequest

if (HROrganization.CreateOrgUnitPfiVariables

and config.HCM_ChangeRelationshipToOrganizationOrgUnitKillSwitch != "true")

include HCM.AddHROrganizationUnitVariable

replace HROrganizationUnit with ActivePrimaryWorkAssignmentRel.HROrganizationUnit

UpdateRequest Rules

include UpdatePositionPlanPendingRequest

if (HROrganization.CreateOrgUnitPfiVariables

and config.HCM_ChangeRelationshipToOrganizationOrgUnitKillSwitch != "true"

and PfiWorkunitVariableRel exists)

include HCM.UpdateHROrganizationUnitVariable

replace HROrganizationUnit with ActivePrimaryWorkAssignmentRel.HROrganizationUnit

CancelRequest Rules

include BackoutPositionPlanPendingRequest

Action Rules

include UpdateForSort

Exit Rules

if (InactivateWorkAssignments)

invoke Inactivate ActiveEmployeeWorkAssignmentsRel

invoked.PrmContractDateFromEmployee = effective date

include InactivateSecondaryWorkAssignments

include InactivateFutureWorkAssignments

include InactivatedMentorRecordMaintenance

if (DeleteActorRoles)

invoke Delete ActorRoleRel

if (InactivateActor)

LocalActor = AgentEmployee

invoke Update ActorRel

invoked.IsActorDisabled = true

include BackoutPositionPlanPendingRequest

if (BenefitEnrollmentEvent entered)

invoke CreateBenefitEnrollment

invoked.BenefitEnrollmentEvent = BenefitEnrollmentEvent

invoked.EnrollmentDate = EventDate

invoked.ExtensionDays = ExtensionDays

if (RelationshipStatus changed

and RelationshipStatus.DisablePaperlessDelivery)

YearEndDeliveryPreference = false

HealthCoverageDeliveryPreference = false

Rachel Lake

Thank you!

Copyright © 2025 Infor. All rights reserved.