EAFlow centralizes request, approvals, documents, signatures and operational handoff in a single queue for HR Shared Services. It coexists with HCM, Payroll and e-signature; it adds workflow, routing and evidence.
01 · The problem
An agreed employee separation can involve manager, HR, Payroll, Legal, documents, signatures, approvals and updates in core systems.
When that process lives in emails, spreadsheets or informal conversations, traceability is lost: who requested, who reviewed, which condition applied, which document was signed and when the case was closed.
EAFlow turns every negotiated separation into a governed case, with owners, states, approvals, documents and evidence.
02 · The solution
HR Shared Services receives the request, validates the context, coordinates internal reviews, manages approvals, prepares documents, controls signatures and leaves the case ready for operational closure.
EAFlow connects every step in a single flow over the Operational Graph: intake, routing, approvals, document package, e-signature, HCM/ERP handoff and audit-ready evidence — with each case connected to its employee, legal entity, country, owner, policy, documents, signatures, SLA and evidence.
The journey coordinates the requesting manager, payroll administration and the approval step on a single form, with rules specific to each legal entity and country. A return to correct data or complete documentation is an intermediate case state, not its closure: the case goes back to whoever can resolve it and keeps its history. The separation event is pushed to the corporate people system through a service interface, and operational closure is confirmed from that same source. BPMflow supports the journey —cases, assignment, approvals, due dates, exceptions and evidence— from the approved definitions in the graph: the process grows from the graph, not from an isolated flow.
The result is not another inbox. It is a complete operational case file.
03 · Capabilities
Controlled intake of negotiated offboarding requests, with minimal data, employee, legal entity, country and operational reason.
Flows that adapt by country, legal entity, internal policy, role, required documentation and approvers — no rigid hard-coded rules.
Coordination across manager, HR Shared Services, Payroll, Legal, Compliance and other defined owners.
Preparation, review, signature and filing of the documents associated with the case.
Comments, attachments, approvals, signatures, states and decisions stay in a traceable case file.
Operational closure ready for update in HCM/ERP, Payroll or document systems — without extending the core.
04 · Roles
Initiates the request and provides the case context.
What they see
The status of their request, what information is missing and who the next approver is — on a single view.
What they do
Initiates the request and provides the case context for evaluation.
Coordinates the flow, classifies and monitors.
What they see
The queue with cases by status, country, legal entity, owner and SLA; the case history; the associated documentation.
What they do
Coordinates the flow, classifies the case, monitors states and manages hand-offs.
Validates conditions, impacts and risks.
What they see
The cases escalated to their area, with the applicable policy, the documents and the case context.
What they do
Validates conditions, payroll impacts, documents, risks or required approvals.
Configures the flow and its parameters.
What they see
The configuration: categories, routing rules, owners, SLAs, templates and states.
What they do
Configures categories, routing rules, owners, SLAs, templates and flow states.
05 · Rollout
EAFlow is implemented over the current operating model. It does not require replacing HCM, ERP, Payroll or e-signature.
1 · Operating model discovery
Legal entities, countries, roles, policies, approvals, documents and systems involved. Scope is declared on the Operational Graph.
2 · Workflow configuration
Rules by country, legal entity, separation type, owner, required approval and associated documentation.
3 · Launch & handover
Operational queue, forms, states, reports, training and handover to the Shared Services team.
06 · Scenarios
Agreed employee separations should not depend on scattered emails. EAFlow lets HR Shared Services run every case with workflow, approvals, documents, signatures, handoff and traceable evidence.
HR Shared Services — Negotiated Offboarding is a solution on the EAFlow Operational Graph for HR Shared Services. It runs alongside the HCM/ERP, Payroll and e-signature tools — it does not replace core systems or compute settlements; it adds workflow, routing, approvals, traceability and evidence.
