On this page
What is HR master data workflow automation? It replaces email and Excel with one portal. Field coordinators raise changes, the system validates them and routes them through a defined approval ladder, and approved data syncs to SAP SuccessFactors. Every decision is recorded and searchable by Employee ID or Position ID.
- Industry
- Pharmaceuticals
- Teams
- Field Coordinators, divisional approvers, Payroll
- Platform
- Mendix low-code platform
- Integration
- SAP SuccessFactors (real-time or nightly batch)
- Scope
- Seven types of field employee and position changes
- Key result
- A manual, untracked process became a controlled, auditable workflow
Field force changes ran on email and spreadsheets
A leading pharmaceutical company with a large field force was managing every employee change, from transfers and promotions to resignations and salary revisions, through email and spreadsheets. There was no clear approval path, no single record and no easy way to check who approved what.
Field forces change constantly. Representatives move between headquarters, new territories open, positions are created and closed. Each change has to be correct in the HR system, because it affects reporting lines, payroll and sales coverage.
Handled by email and Excel, the process broke down in five ways:
- No approval path. Nobody could say for certain who needed to approve a change, or in what order.
- No single record. Request status was scattered across inboxes and files.
- No audit trail. There was no reliable proof of who approved what, and when.
- Avoidable errors. Wrong position codes and mismatched HQ, Pool or State data reached the HR system unchecked.
- Hard to trace. Finding an old change meant searching through mail threads.
One portal for every field master data change
The Field Coordinator Portal is a single place to request, approve and record every field master data change. It covers seven transaction types, and each one has its own approval ladder.
People changes
- Resignation
- Payroll Salary Revision
- Secondary HQ Addition / Deletion
Position changes
- Position Code Change
- No Position Code Change
- New Position Code Creation
- Position Code Deletion
Each of the seven transaction types follows its own approval ladder.
Raise, check, approve, sync, record
Every change, single or bulk, follows the same five steps:
- RaiseA coordinator submits a change on its own, or many at once using an Excel template.
- CheckThe portal validates the data and identifies the type of change automatically.
- ApproveThe request follows the right approval ladder. Any rejection must include a reason.
- SyncApproved changes go to SAP SuccessFactors, straight away or in the nightly batch.
- RecordEvery step is saved in the Master Console for future search and audit.
What changed for HR and Payroll
| Area | Before | After |
|---|---|---|
| Requests | Email and Excel | One portal |
| Approvals | Unclear, ad hoc | Defined ladder per change type |
| Data checks | None | Validated before submission |
| Rejections | Often unexplained | Reason always recorded |
| Audit trail | Scattered or missing | Searchable by employee or position |
| SuccessFactors update | Manual re-entry | Automatic, real-time or nightly |
Seven features behind one auditable workflow
Grouped by what they protect: who approves, what gets in, and what gets recorded.
Approvals and control
The right people, in the right order.
01Approval ladders for each transaction type
- Why it matters
- Every request reaches the right people in the right order.
02Mandatory rejection reasons
- Why it matters
- Requesters know what to fix, and every decision is explained.
03Division-based access
- Why it matters
- Users see only what belongs to their role.
Data quality
Errors stopped at entry, not discovered later.
04Validated Excel uploads for bulk changes
- Why it matters
- Errors are caught before submission.
05Automatic classification of each change
- Why it matters
- Each change is identified by type automatically, so it follows the right approval ladder.
Integration and audit
One source of truth, written to SuccessFactors.
06Flexible SuccessFactors sync
- Why it matters
- Changes reach SAP SuccessFactors in real time or in the nightly batch.
07Master Console with searchable history
- Why it matters
- Any change can be traced by Employee ID or Position ID.
Control, accuracy and one source of truth
- Control: every change follows the same governed path.
- Accuracy: errors are stopped at entry, not discovered later.
- Accountability: each approval and rejection is timestamped and attributed.
- Speed: no more chasing approvals over email.
- Visibility: HR, Payroll and leadership work from one source of truth.
Any large, distributed workforce on SuccessFactors
Any organization running SAP SuccessFactors with a large, distributed workforce:
- Pharmaceuticals and life sciences
- Medical devices
- Consumer goods
- Field sales teams in insurance and banking
Building on Mendix kept delivery fast and left the client with a platform that is easy to extend. New transaction types, approval rules or validation checks can be added without long development cycles. See our Mendix app development services.
Frequently asked questions
What is HR master data workflow automation?
It replaces email and spreadsheet requests with a single system where employee and position changes are raised, validated, approved and written to the HR system automatically, with a full record of every decision.
How does the portal connect to SAP SuccessFactors?
Once a request is fully approved, the portal pushes the change to SAP SuccessFactors. Teams choose whether each change syncs immediately or in the next nightly batch.
Which changes can the portal handle?
Seven types: Position Code Change, No Position Code Change, New Position Code Creation, Position Code Deletion, Secondary HQ Addition or Deletion, Resignation, and Payroll Salary Revision.
How does it reduce data errors?
Every request, including each row of a bulk Excel upload, is checked before submission. Wrong position codes and mismatched HQ, Pool or State values are flagged before they can reach SuccessFactors.
Can teams still work in Excel?
Yes. Bulk changes are uploaded through standard Excel templates. The difference is that each row is validated and then follows the same approval and audit trail as a single request.
How do auditors or managers trace a past change?
The Master Console records who requested a change, who approved or rejected it, the reason and the time. It can be searched by Employee ID or Position ID.
Who can see what in the portal?
Access is role-based and limited by division, so each user sees only the requests and records that belong to their role.
Why build it on Mendix?
Mendix is a low-code platform suited to workflow applications. It allowed fast delivery and makes it simple to add new transaction types, approval rules or checks as the business changes.
Is this only relevant to pharmaceutical companies?
No. Any organization with a large, distributed workforce and frequent position or location changes, such as consumer goods, medical devices, insurance or banking field sales, faces the same problems.
Can this approach work in any country?
Yes. The pattern applies wherever an organization runs SAP SuccessFactors and manages a large field team, regardless of region. Approval ladders and data rules are configured to local structures.
Still managing HR changes by email and spreadsheet?
Talk to our Mendix team about a validated, auditable SuccessFactors workflow for your organization.
The client's name is withheld under a confidentiality agreement. Any screens shown are anonymized.