Infosys worker refuses to fly home, loses unfair dismissal claim

His own email helped sink the case

Infosys worker refuses to fly home, loses unfair dismissal claim

An IT worker's refusal to return to India after his Australian assignment ended cost him more than his job - it cost him the right to challenge the dismissal at all.

The Fair Work Commission dismissed the unfair dismissal application on November 19, 2026, finding it lacked jurisdiction. By the time the worker was fired, the Commission held, his employment no longer had a sufficient connection to Australia.

The worker had been employed by Infosys Limited in India since late 2019, based in Pune. In April 2023, he was deputed to the Perth office of Infosys Technologies Limited - Infosys Limited's registered Australian branch - to work on major client accounts, including BHP and Woodside Energy.

His deputation letter was explicit. Infosys Limited in India remained his employer. His relationship with the Australian branch was that of "deputee." His presence in Australia was temporary, and he was to return to India once the assignment wrapped up.

The assignment was initially set for 22 months. It was extended multiple times through a series of letters between 2023 and 2025. The final extension pushed the end date to January 31, 2026.

Then the deputation ended. The worker did not leave.

Five months, no flight home

According to evidence before the Commission, Infosys Limited directed the worker to return to India after his deputation concluded. He did not comply. His delivery manager reminded him on February 23, 2026. Still nothing.

A disciplinary process followed. A Teams meeting was scheduled to discuss the refusal - the worker asked for questions in writing instead. A second meeting was set for April 2, 2026. He declined, citing health issues and medical treatment. A formal show-cause notice issued on April 17, 2026, setting a deadline of April 21, 2026. The worker missed the deadline and an extension of it.

Infosys Limited terminated his employment by letter on June 26, 2026.

The worker filed for unfair dismissal on July 10, 2026. But he named Infosys Technologies Limited - the Australian branch - as his employer.

That proved to be a problem on two fronts.

Wrong company on the paperwork

The Commission found that Infosys Limited in India - not the Australian branch - was the worker's employer. The employment contract, signed in India in November 2019, fixed his location as Pune. Every deputation letter reinforced that his existing terms with Infosys Limited continued "in full force and effect" and that the Indian entity remained his employer. The worker signed each of those letters.

The worker argued the deputation documents were mere formalities for immigration processing and that he had been told he was employed by the Australian branch. The Commission gave that assertion no weight, noting the worker provided no detail about who had told him this or when.

He also pointed to Australian payslips naming Infosys Technologies Limited as his employer, and WorkCover WA records identifying the same entity. The respondent's position was that Australian payroll processing and workers' compensation coverage were the ordinary administrative incidents of an international assignment, arranged to satisfy local regulatory requirements rather than to change who the employer was.

Connected to Australia - until he wasn't

Even setting aside the wrong-employer issue, there was a bigger jurisdictional hurdle. Under the Fair Work Act 2009, unfair dismissal protections only apply where an employment relationship has a sufficient connection to Australia. Working in Australia is not enough on its own - the connection has to exist at the time of dismissal.

During the deputation - from May 2023 to January 31, 2026 - the Commission accepted that connection was clearly there. The worker performed duties in Perth, reported to Australian-based managers, was paid in Australian dollars, and Australia was the applicable tax jurisdiction.

But five months separated the end of the deputation from the dismissal. By June 26, 2026, the worker had spent those months in Australia without an authorised assignment, without performing work for the Australian branch or on client projects, and against repeated directions from Infosys Limited to return to India. His continued presence in Australia was, in the Commission's words, "unauthorised" and "expressly and repeatedly disavowed" by Infosys Limited.

The worker's own correspondence worked against him. In a November 12, 2025 email to his line manager, he had acknowledged the deputation was temporary, expressed support for Infosys Limited's initiative to facilitate his return, and confirmed his intention to "relocate to [his] base location."

The Commission held that what occurred before January 31, 2026, was not relevant to the jurisdictional question. When the dismissal happened, the only connection to Australia was that the worker happened to be physically present there - unapproved and unendorsed by his employer.

The jurisdictional objection was upheld and the application dismissed.

For HR teams managing international secondments and deputations, the decision is a reminder that contractual documentation carries significant weight in establishing - or losing - an employment connection to Australia, and that once an assignment ends, the jurisdictional clock may reset regardless of how long the worker spent on the ground.

LATEST NEWS