Quote Originally Posted by Bulba View Post
I'm sorry for casting aspersions or for any negative implications. But I saw this question elsewhere and I couldn't find an answer :

How many people in the project team have access to this accountant?

If it's more than one, can the other person(s) verify what Oru has said?

This accountant should have known the tax implications. And they should have had professional insurance to cover a mistake like this. That's what they are paid for.
I’ve addressed this “elsewhere” but as a repeat here:

I want to be clear, I know it's hard to understand the tax situation but its as real as death and I am personally contributing a large sum of money along with others on staff to just make it go away. I trust Oru deeply, I've spoken with him and I have spent many hours of my life with the core team working to make our environment work like a clock so we're all having fun. What is often not said or understood is the devs enjoy, well, being devs and we want the community to enjoy the results of our work. Meanwhile, it comes as a stab directly to the heart when trolls attack, we are just people like everyone else, we have lives, children, dogs, cats, and work and we come to this community contributing our skills to have fun and empower others to have fun. Its fun to think of conspiracy theories but Occam's razor teaches us the simplest explanation is most likely. I've seen the documents, I've used google translate to read them (hard but not impossible) and the situation satisfies me enough that I'm helping pay the bill directly with my own personal money. I've run companies for 25 years of my life and I know how complicated it can be, how expensive lawyers and accountants are and how easy it is to make a costly mistake. We were going to post the documents but then we noticed personal info like addresses and tax ids in them and we were concerned about exposing Oru to trolls in real life. Oru will need to redact them and post later but then they exist and have convinced me to act. We will learn from this event and find solutions to keep it from happening again.