ADVERTISEMENT



Google       

Home -> Law Blog Directory -> Litigation Blogs -> The FRAUDfiles Blog

OR PHONE (866) 635-1838 for Bankruptcy Help, (866) 635-6190 for Divorce,
(866) 635-2689 for Personal Injury or (866) 635-9402 for Criminal Defense

Find a Local Lawyer

Bankruptcy (866) 635-1838
Divorce (866) 635-6190
Personal Injury (866) 635-2689
Criminal Defense (866) 635-9402

Bookmark

Litigation

: The FRAUDfiles Blog

Koss Fraud: Unrecorded revenue?

By Tracy Coenen

ADVERTISEMENTS

How does a company with about $40 million in annual revenue fall victim to a $31 million (or more) fraud by the VP of Finance? Simply, Koss Corp. gave Sue Sachdeva the keys to the castle. She apparently ran the company’s finance function with little oversight from anyone else.

Koss has done something I think is a bit unusual. In a filing with the SEC, the company detailed the alleged theft by year:


2005 – $2,195,477
2006 – $2,227,669
2007 – $3,160,310
2008 – $5,040,968
2009 – $8,485,937
2010 – $10,243,310 (two quarters)

What’s unusual is that the company was willing to provide this significant information related to the fraud, but still has not given any information as to how the fraud was concealed by Sachdeva. Why release the amounts but not the methods? Certainly if the company knows with some certainty how much was stolen, they also know how it was done.

There are several theories about how Sachdeva hid her $31 million theft for more than five years. In my opinion, the most likely scenario was that she expensed the theft, most likely using cost of goods sold accounts because those would be some of the largest accounts and a variance in them is easily explained. This is also attractive because it does not create a need for additional accounting entries after the theft was booked. It’s not messy and it has a pretty good chance of going unnoticed by the auditors if it is done right.

But I’ve heard from a few sources who I consider to be very reliable that Sachdeva hid her theft by not recording revenue. This would mean that Koss’s revenue was understated by $31 million during the time she was committing her theft. There are pros and cons to concealing a fraud by this method.

Cons: Intentionally understating revenue to cover a theft is messy. If Sachdeva used this method to conceal her fraud, she would have had to devise a way to bill customers (so that the money actually comes in the door and is available to steal) but not have it show up on the books. How could this be achieved? Someone could create invoices outside the accounting system, and make them look like authentic invoices. The other option is to use Koss’s accounting system to generate the invoices, but later reverse those invoices so that revenue is reduced in an amount equal to the theft. It’s messy, and requires a fair amount of work either way.

Pros: There is almost no chance that the auditors will discover the theft and the cover-up.  he bulk of the auditors’ work is spent on the balance sheet. So long as transactions related to the theft don’t show up in the ending balances of the balance sheet accounts, she’s pretty safe there.

Then the auditors move over to the income statement. The procedures performed there are quite limited. The focus will be on the risks related to net profit. The biggest risk is that a company is overstating their profits, either by overstating revenues or understating expenses. There is very little risk that a company is going to understate revenue or overstate expenses, because both of those reduce net profit. (Yes, there are some circumstances in which companies might do this. For example, if they want to hold some revenue and push it into the next reporting period, they might purposely understate revenue for the current period. This is not that common, however.)

So on the revenue side, the auditors are most commonly looking for evidence that revenue might be overstated. They’re not looking for unrecorded revenue, which is what the rumor mill says Sachdeva was doing. Unrecorded revenue is nearly impossible to find, even if the auditors are actively looking for it. How on earth does one find evidence of sales that have not been entered into the accounting records? You can’t find something in nothing, so it’s unlikely that the auditors would uncover understated revenue unless there are some other clues that point to such a scheme.

Do I think that Sachdeva could have committed her fraud by underreporting revenues and stealing the customer payments related to those sales not on the books? Yes. It’s not the most palatable because it’s a bit messy to carry out. But the flip side is that the auditors have almost no chance of uncovering such a scheme.

Although Koss hasn’t told us much about how the fraud happened, they were kind enough to report to the public that since they’ve fired the employee responsible for stealing $31 million, their financial results will improve.  Indeed, if the unrecorded revenue theory is correct, that means that over the last five-and-a-half years, the company had at least $31 million more in revenue than reported on their financial statements. The bottom line is that their bottom line will go up by $31 million for that period, which is quite an improvement over the numbers previously reported.

Full post as published by The FRAUDfiles Blog on April 02, 2010 (boomark / email).

Bloggers, promote your law blog by nominating your blog for inclusion in USLaw.com's Law Blog Directory and RSS Reader. Benefits described.
Related Law Articles

Lawsuits and Settlements

Related Searches

























































































































US Law
#1 Online Legal Resource













Your Blog Subscriptions
Subscribe to blogs

10,000+ Law Job Listings
Lawyer . Police . Paralegal . Etc
Earn a law-related degree
Are you the author of this blog? Adding USLaw.com to your Blogroll increases relevance. You qualify to display a USLaw Network badge.
Suggest changes to this blog's description or nominate another for inclusion. Register for updates.


Practice Area
Zip Code:

Contact a Lawyer Now!






0.0171 secs (new cache)