An acquired employee should not lose their history in the new system

Integration plans tend to favour a clean starting point. One system, one process and one set of records appear easier to operate than the arrangements inherited from an acquired business. For employees, however, the transaction date is not the beginning of their working life. They may have years of service, recorded balances and earlier commitments that remain relevant. If the new administration treats those facts as inconvenient legacy detail, a technically efficient migration can create an employment question the business has not actually decided how to answer.

I saw this during an acquisition that brought 420 colleagues into Praneri. The proposed HR-system setup used standard starting records, while employees were asking what would happen to their earlier service dates and leave. The gap was not necessarily evidence of bad intent. The integration team wanted a manageable process, finance needed an account of the obligations and source records were not equally clear in every case. The difficulty was that the system proposal could turn an unresolved question into an apparent company decision without anyone explicitly choosing that outcome.

## Identify the commitment before configuring the record

The starting conversation should concern what the transaction and the company have agreed to preserve, change or review. That requires employment advice and attention to the particular facts; it cannot be settled by a general preference for consistency. HR should work with transaction leaders, finance and advisers to make the position understandable. A record is then a representation of that decision. Reversing the order allows available system fields or an implementation deadline to determine the substance of a commitment that may matter greatly to an employee.

In our case, we agreed to preserve specified service dates and accrued leave balances while standardising future administration. The negotiated plan recognised ₹76 lakh in assessed accrued-leave obligations. That was an assumed cost within the transaction, not an HR saving. I am careful about that distinction because integration reports often encourage functions to present every resolved issue as a benefit achieved. Sometimes the responsible result is simply that the company has identified an obligation accurately and arranged to honour it. The value lies in a dependable decision, not a favourable description of its amount.

The approach should not be read as a universal legal prescription for acquisitions. Different structures, documents and circumstances require their own assessment. My point concerns the management process around that assessment: identify the question, obtain appropriate advice, decide through the authorised route and ensure the administration reflects the decision. An employee should not have to infer a change in their position from an altered date in a portal. Equally, a reassuring verbal statement should not be allowed to stand apart from records that show something materially different.

## Make uncertainty visible without transferring it to employees

Source records may contain discrepancies. A service date might differ across documents, a balance may depend on an adjustment not yet entered or a manager may remember an exception that was poorly recorded. Those issues require investigation. They do not justify assuming that the easiest value is correct, nor do they make every employee claim automatically conclusive. I want a review process that can explain which evidence is being considered, who will decide and when the employee can expect a response. Uncertainty should have an owner and a route to resolution.

We provided individual statements and a correction process. That helped colleagues understand the account being carried forward, but also created work. Questions arrived that the transaction timetable had not anticipated, and configuration took three weeks longer than the original plan. We continued temporary administration during that period. The delay was a real cost and inconvenience, which belonged in the integration report. It would have been misleading to describe the approach as frictionless merely because we believed the alternative would produce more difficult disputes later.

There is a balance between asking employees to verify their records and making them prove their whole history again. The company should first do the work available to it: reconcile source files, consult relevant decision-makers and document the basis it intends to use. Employee review then becomes a meaningful check rather than a transfer of administrative responsibility. Where an employee identifies an error, the response should address that particular issue. A general assurance that the acquisition is beneficial does not answer a question about a missing balance or a date that has changed.

## Keep the explanation after the integration team leaves

The period immediately after completion receives considerable attention. Later, the transaction team disperses, temporary support ends and the common system becomes ordinary infrastructure. Yet an employee may raise a question years afterwards, perhaps when leaving, seeking a benefit or reviewing an earlier decision. The record needs enough context for a person who was not present during the acquisition to understand it. A note that says an exception was agreed is less useful than an account of what was agreed, the authority and the evidence supporting it.

I therefore ask who will own the historical explanation in normal operations. This does not require every employee to remain on a separate process indefinitely. It requires the business to preserve the reasons that continue to matter while simplifying the administration around them. A good common system can make those reasons easier to retrieve. Standardisation becomes harmful when it removes distinctions before the company has determined whether they are still relevant. Uniform presentation should be the consequence of clear decisions, rather than a way of avoiding them.

A board reviewing acquisition integration can ask whether material employment commitments appear in both the financial plan and the implementation account. Directors need not adjudicate individual balances. They should understand whether the process has reliable records, appropriate advice and continuing ownership, and whether significant discrepancies will be escalated. The question is especially useful when the deal case depends on a rapid move to common operations. Speed has value, but the company should know which unresolved matters it is carrying rather than allow them to disappear inside a progress percentage.

For the 420 colleagues in our acquisition, the agreed service and leave records were preserved. That result did not settle every employment issue or mean that no future change would occur. It established a dependable account of a particular commitment. I would begin the record review earlier next time, before technical integration choices narrow the discussion. An acquisition changes ownership and organisation; it should not inadvertently rewrite an employee's history because the new system was easier to configure that way. The company must decide what changes, and take responsibility for explaining it.