Loading
No recruitment module, no performance management. One structural idea instead: internal movement built as an approved event that updates the employee record directly, rather than a change several people each act on.
Client
COD
Location
Published
October 2026
Reading Time
8 min read
Implement Zoho People and Zoho Payroll with a custom employee transfer module in which approved changes propagate directly into the employee database — making internal movement a controlled event with a single owner.
COD engaged Interloop to implement core HR and payroll with a specific emphasis on internal employee movement: transfers initiated by HR, routed for approval, and reflected automatically across the employee record. Probation automation and letter generation completed the scope. Recruitment and performance management were deliberately left out, the client having no requirement for either. Delivery ran across two phases — core HR, attendance, exit, probation and the transfer module in the first, payroll in the second — closing with admin enablement and documentation.
Joiners and leavers are visible events with a form attached. Transfers are neither, which is why they tend to be the least structured part of an otherwise well-run HR process. A transfer affects location, reporting line and payroll at the same time. Handled as a communication, each of those updates is made separately by whoever is responsible for that system, which means the employee record becomes current in stages rather than at a moment. Giving the transfer a form, an approval and a defined effect turns it into a single event with one owner — and that is as much about clarity of responsibility as it is about speed. The absence of a recruitment module made this more significant rather than less. Where external hiring is steady, internal movement is the main mechanism by which the organisation changes shape, which puts the transfer record on the primary path rather than an edge of it.
Transfers without a structured step: Joiners and leavers had forms; transfers were communicated as they arose, leaving several people each responsible for part of the update.
A record that becomes current in stages: With updates made separately, the employee record reflects a transfer progressively rather than at a single point.
Internal movement as the primary change mechanism: With steady external hiring, transfers rather than recruitment were how the organisation reshaped itself.
Automation writing to the employee master: A form that updates the employee record directly needs its behaviour confirmed before it is relied on, because there is no natural point of detection afterwards.
Probation outcomes documented individually: Confirmation, extension and non-confirmation were each tracked and written by hand.
Modules without a requirement: Recruitment and performance management were available in scope but had no identified user at this organisation.
Interloop followed a structured, eight-step implementation across two delivery phases — discovery, policy blueprint, configuration, custom module development, a bounded verification period for the automatic update, and go-live with hypercare. The design decision that shaped the engagement was brief to state: the approved transfer updates the record rather than notifying someone to. A module that notifies depends on attention under load; a module that updates depends on nothing.
Implementation Approach
This engagement gave Interloop a question now asked in any HR data review: how does a transfer reach the employee record, and who owns that step? Where the answer involves several people each updating part of it, there is a single structured event waiting to be built.
Joiners and leavers have a process. Transfers deserve one.
| Aspect | Before | After (Interloop) |
|---|---|---|
| Internal transfer | Communicated as it arose | An HR-initiated form with defined approval |
| Employee record update | Made separately across systems | Propagated directly on approval, as one event |
| Ownership | Distributed across whoever held each system | A single owner and a single moment of effect |
| Payroll after a transfer | Confirmed against the latest understanding | Drawn from a record already current |
| Probation outcomes | Tracked and written individually | Three defined routes with generated letters |
| Automation confidence | — | Behaviour confirmed under manual verification before reliance |
Communicated as it arose
An HR-initiated form with defined approval
Made separately across systems
Propagated directly on approval, as one event
Distributed across whoever held each system
A single owner and a single moment of effect
Confirmed against the latest understanding
Drawn from a record already current
Tracked and written individually
Three defined routes with generated letters
—
Behaviour confirmed under manual verification before reliance
Before vs. After
COD processes internal movement as a single approved event that updates the employee database directly, with payroll and reporting drawing on current data from the first cycle after any transfer. For Interloop, the engagement demonstrated custom module delivery with a measured risk model around automations that write to the employee master — and reinforced that some of the most useful implementations address the step nobody had thought to call a process.
Continue Reading
A wealth-management firm replaced fragmented spreadsheets with a secure, compliance-ready Zoho CRM — centralizing client data and eliminating manual follow-up risk.
DKC Exports replaced fragmented, manual HR processes with a centralized, automated Zoho People platform — streamlining onboarding, offboarding, and internal communication.
Streamline HR processes with a secure, scalable system that centralizes data, automates tasks, ensures compliance, boosts efficiency, and enhances employee engagement.