The Takeover of My Computer Business
Years ago, I ran a computer business that was eventually taken over by a larger company. The agreement was that my business would become the computer division of this larger company, where I would continue to work as an employee. The takeover agreement was detailed and even more favorable than I had expected.
The deal was broadly as follows: they took over all the inventory and paid for it, plus a percentage of the profit from that department for the next three years. Even if things went poorly, a minimum amount was set. It seemed like a good arrangement.
We got started, and I received the money for the inventory. Within the company, I was even assigned to work on the software package. As employees, we also had the advantage of purchasing products at cost price, which was convenient because I was in the process of setting up my new business in short-stay accommodations and needed various appliances: coffee makers, washing machines, mini-fridges, irons, and more.
My Background in Software
Since the time of the Osborne computer, I had experience with software and databases. Back then, I worked with a dBase solution where you could program databases with an accessible language. Due to my educational background in Cobol, Fortran, and even machine language, dBase was a fun package to work with.
Later, in my computer business, we switched to purchased PMS software that integrated purchases, sales, invoicing, and accounting. The backbone of that software was FoxPro. I recognized the database structures and language behind the frontend, and with a separate tool, it was possible to look into those tables. I even acquired FoxPro manuals to delve back into it.
Within my company, I was the person who knew the back-office and internal software best. I was well-versed in FoxPro and knew the ins and outs of that package very well. The acquirer of my computer business worked with the same software.
The Incident with the Washing Machine
At a certain point, I took a washing machine. Naturally, for everything that was taken, the necessary delivery notes had to be made. The software was excellent and recorded all purchases, sales, and movements. Everything was logged so that even months later, it could be checked when an item was moved or when something disappeared. There were even cameras, so everything was fully monitored.
With my knowledge of the software, it would not have been difficult for me to commit fraud if I had wanted to, but of course, I did not. On the contrary, I worked there in trust and adhered to the agreements.
When I took the washing machine—a product that did not belong to my department—I assumed that the necessary documents would be prepared by someone else. The washing machine was neatly loaded into the car with the help of other employees, and everything seemed in order.
The Confrontation and Lawsuit
A few weeks later, however, I was called into the office and confronted with the fact that I had stolen a washing machine because no receipt had been made. Trust was broken, and I was asked to sign a confession of guilt. I refused to do so because then my entire payment arrangement would be nullified.
The situation was bizarre; everyone was surprised, myself most of all. Eventually, it led to a lawsuit. During the trial, I was portrayed in a bad light and lost the case. We appealed, but I lost again.
The crux of the matter was clear: if I had wanted to commit fraud, I could have done so very easily with my knowledge. It turned out that my case was the last case of my lawyer, who was retiring. Also, lawyers usually plead without the presence of their clients. I was there each time, and my lawyer did a poor job.
I was portrayed as a fraudster, but in reality, a document was simply forgotten.
A simple lie to put someone in a bad light, defended with the argument of the complexity of the software, proved to be an impossible case to fight against.
