Commentary

Ex Moto Exec Airs Dirty Laundry

Motorola's former CFO, Paul Liska, claims the company purposely misstated financial documents regarding its handset unit, and that he was unjustly fired for trying to blow the whistle.

Motorola's former CFO, Paul Liska, claims the company purposely misstated financial documents regarding its handset unit, and that he was unjustly fired for trying to blow the whistle.This is exactly the type of situation that Motorola needs to be avoiding right now. Paul Liska, the company's former Chief Financial Officer, said in Cook County court documents (obtained by BusinessWeek) that he became alarmed at what he thought were unsupportable projections on 2009 handset sales.

He "develop[ed] concerns that the executives within the Mobile Devices Business were, intentionally or recklessly, materially misstating its 2009 forecasts and strategic plan." He felt the statements would have "a significant deleterious impact on Motorola's credit ratings and relationships, particularly if Mobile Devices' actual results continued to fall well short of its actual forecasts."


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

When he approached Motorola's board about the issue, he was fired in what he calls a retaliatory discharge.

Motorola didn't take the charge lightly. It contends that Liska cooked up a "scheme designed to portray himself as a whistleblower and demand millions in return for his silence." It also named him a "treacherous officer."

Ouch.

Motorola has been having a hard enough time as it is. The company's handset division is barely a shadow of what it once was. It recently became public that Motorola CEO Sanjay Jha was the highest paid U.S. CEO in 2008, while at the same time, the company has laid off thousands of employees.

It will be up to the Cook County court system to determine who's telling the truth in this matter, but Liska's allegations aren't pretty. All thanks makes a bad situation look all the worse for the U.S. maker of cell phones.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links