Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

  > After a while someone realised that a group of engineers 
  were consistently booking shitty travel around the same time,
  and then travelling first class the rest of the year.
How's that different than having an annual travel budget? Sounds like they sacrificed to feast later instead of holding accommodations constant at "above average."

I think you did a good job telling the story, but maybe I'm missing how gaming travel expenses is unique to Google.



Crucial point which I didn't communicate properly: they were block booking spurious/unnecessary travel well in advance (by years).


They still had to justify that travel expense in the corporate card, which is charged when the booking is made. So their managers must not have though of those trips as unnecessary.


How can you even book flights years in advance when airlines only publish schedules 330 days in advance?


You can book hotels years in advance and flights ~1 year in advance.


Oh! Yeah, that (embezzlement/fraud) is why they got in trouble.


The difference is that if you know your budget is X, you'll probably try to spend X - epsilon, because that maximizes your personal outcome within the rules.

But if you get a credit based on the difference, then you'll have a shared incentive with the budget-maker to spend much less than X.

However, then you have the problem that if X is per trip, then there's a perverse incentive to maximize the number of trips (even if they're each well under budget) because you pocket the cumulative credit. Then you can go way over X on the trips you actually care about.


Giving credits for cost-saving isn't the problem. Companies do that with travel expenses. What you're describing is really the same as giving employees an annual discretionary travel budget.

Here's the problem: It sounds like Google didn't implement financial controls. The employees committed fraudulent transactions by booking travel from outlying years and get credits for use in the current year. That shouldn't have been allowed.

This was unclear in the original post and the commenter graciously clarified.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: