An expense policy often describes what happens after a business journey. It explains which costs are eligible, what evidence is needed and how reimbursement is processed. Those questions matter. But the employee must first arrange and pay for the travel, and that earlier moment can contain an assumption the policy barely acknowledges. Approval to undertake work does not establish that someone has agreed to provide personal funds until the company pays them back.
In 2025 we had seventy-two approved client-travel assignments organised around a pay-first-and-claim arrangement. Twenty-one requests for advances or direct booking made us examine the model. The requests were evidence of a practical question, not a diagnosis of the employees' circumstances. We did not know, and did not need to infer, whether someone had limited cash, preferred not to use a personal card or had another reason. Treating all twenty-one requests as one financial story would have invented facts about people.
My concern as CHRO was that the company's instruction should be workable on the terms it actually offered. Operations needed colleagues to travel for client service. Finance needed appropriate payment arrangements and controls. Employees needed to know how an approved assignment would be organised before departure. Those needs belong in the same discussion. A reimbursement policy can be administratively complete and still leave them disconnected if it assumes the employee will bridge the gap privately.
A request is not a financial diagnosis
There is a risk in trying to make a compassionate case for change by speculating about hardship. It can turn an ordinary request into a judgement about a person's income, creditworthiness or ability to manage money. That was not necessary here. The company had approved the work, and the question was how it should arrange the required expenditure. We could examine that responsibility without asking employees to explain unrelated personal finances or provide private bank statements to justify the enquiry.
We also avoided treating silence as evidence that the existing approach suited everyone else. Fifty-one assignments had not produced one of the stated requests, but that did not tell us why. It did not prove that every affected employee preferred reimbursement or that they had experienced no difficulty. The count was a reason to review the arrangement, not a survey of personal circumstances. A disciplined people account should preserve that distinction even when a more emotional interpretation might make a stronger presentation.
Finance and operations worked with us on company booking and invoicing for the seventy-two assignments. The design did not require a personal credit card. Finance retained payment controls, and operations retained itinerary and client-service decisions. HR helped make the work expectation explicit and considered how the process would be explained to employees. None of those contributions transferred responsibility for supplier commitments or financial authorisation to the people function merely because employee experience had prompted the discussion.
Moving the question into the operating plan
The change moved an early funding question into the company's own arrangements. It did not eliminate the practical work of travel. Someone still needed to make bookings, handle changes and obtain timely instructions. Direct invoicing required suitable supplier and payment processes. An employee could still encounter inconvenience or need an itinerary altered. The case should not be read as a claim that one booking model resolves every problem connected with business travel.
We recorded ₹1.1 crore of travel spend and a separate ₹32 lakh of extra coordination and administration expense. The separation matters. The travel amount described the journeys' expenditure, while the additional expense described work needed to support the changed arrangement. Combining them into a vague initiative total would make it harder to understand the tradeoff. Claiming a saving would be still less defensible, because the account supplies no evidence that the new model reduced the cost of travel or administration.
The account also does not say that all seventy-two journeys were completed. It describes the adopted approach for those approved assignments. A completed trip, a changed itinerary and a cancelled assignment would each require their own record if they were material to a later outcome claim. Preserving the boundary is not pedantry. It keeps an operating decision from acquiring a successful delivery result simply because the narrative needs a satisfying ending after the policy changes.
The cost belongs beside the principle
It is easy to state that employees should not be expected to fund company work without acknowledging what an alternative requires. The company needs people, supplier arrangements and controls to take on that responsibility. Our ₹32 lakh additional expense was part of doing so. A leadership account that celebrates the principle but removes the administrative cost makes the judgement appear easier than it was. The tradeoff belongs in the explanation, especially for a reader considering how to change a similar arrangement elsewhere.
There may be circumstances in which different travel methods are appropriate. This fictional case is not a statement of a universal legal rule or a prescription for every employer. Qualified assessment and actual employment, supplier and financial arrangements matter. My contribution is a question about what the company is asking someone to provide before they can do approved work. That question can be useful without assuming that every organisation must choose the same operating process in response.
For managers, the practical habit is to examine the interval between approving an assignment and expecting it to happen. What has the employee been asked to arrange? Which resources are assumed to be available? Which part should the company organise itself? These questions should be asked without turning the employee into a case study about private circumstances. They can reveal a gap in the work plan even when the expense rules are clear and the eventual reimbursement process is reliable.
For a board, the issue is how management understands the demands embedded in its operating model. A policy may appear inexpensive because it leaves time, money or coordination with individuals without making that reliance explicit. Directors can ask what resources the company expects employees to supply and whether those expectations have been considered responsibly. They need not approve individual itineraries to challenge an enterprise account that treats approved work as automatically practical for everyone assigned to it.
The twenty-one requests changed where we looked. Instead of asking only whether reimbursement would be correct later, we asked how the work would be funded and arranged beforehand. We retained uncertainty about personal reasons and later travel outcomes, and kept the added cost visible. That is the leadership lesson I take from the case: listen to the request without inventing the person's story, then examine the assumption in the company's own instruction. The practical response becomes stronger when it addresses what management can actually change.