united-kingdom common-law contract-law business european-union
Can a company handle paying taxes and other bureaucracy work for a freelancer
<p>Pardon my terminology. I'm very much not a lawyer, but I used to watch Ally McBeal as a kid, so I think I got the hang of this.</p>

<p>This is actually a subset of a vastly larger problem, so the arrangements may seem a bit weird. This is an EU question, but having any common law jurisdiction answers would certainly help, as would anything even tangential on this.</p>

<p>We have the following legal entities:</p>

<p>Main company X, located in either Ireland or Northern Ireland (UK)</p>

<p>Accounting company Y, located somewhere in EU, could be the same country as X if that makes things easier.</p>

<p>Freelancer A (and others), located somewhere in EU, ideally the globe.</p>

<p>X has made a contract for service with A. X wants to lower the bureaucracy overhead for A, as it is essential for the business model for make it easy to join as a freelancer (think Uber). Ideally this would be as hassle free for A as having a contract <em>of</em> service with X. </p>

<p>For this, X has two different models:</p>

<p>1) A sends X all the necessary paperwork. When A gets paid, X pays income taxes, pension payments, VAT and whatnot for A and sends the rest for A.</p>

<p>2) A sends Y the paperwork, X sends Y the full amount payable to A and the info required, Y pays the taxes etc and sends the rest to A.</p>

<p>Are either of these (or modifications of those) possible without the relevant authorities interpreting this as a contract <em>of</em> service instead of as a contract <em>for</em> service as intended.</p>

<p>It is worth noting, that even without X handling tax bureaucracy for A, it is not completely clear if the model would pass as a contract <em>for</em> service. Based on the IRS 20 questions on the subject 15 or so say it's <em>for</em>, 3 are indecisive and 2 say <em>of</em>. It would also not make any sense for X and A to have a contract <em>of</em> service relation (again, think Uber).</p>

<p>EDIT:</p>

<p>A few things to clarify:</p>

<ol>
<li><p>Our goal is not (necessarily) to minimize taxes for A, but to minimize bureaucracy overhead for working small sporadic gigs for the company</p></li>
<li><p>Scope of A's work could range from anywhere from an hour to a few years</p></li>
<li><p>Ideally A would just have to provide X (or Y) the required paperwork, then receive payments as if he would be an employee and not have to worry about taxes or social payments.</p></li>
<li><p>Having an employer-employee relationship between Y and A is almost as bad as having it between X and A</p></li>
<li><p>The main reason why we want to avoid employer-employee relationship is not tax optimization or avoiding social payments, but avoiding minimum wage regulations. This may seem quite exploitative, so I might need to open up the idea a bit more:</p></li>
</ol>

<p>The point of company X is essentially to provide a legal &amp; software (latter one being our core competence and first one just a major obstacle) platform for collaboration between the mentioned 'independent contractors'.</p>

<p>As a simplified example that wont catch many of the reasons why we need a legal platform as well:</p>

<p>Freelancers A and B collaborate together to build the ultimate fart app. A handles the coding and clocks in 100h while B farts on mic for 50 hours, both work being deemed equally valuable. When the project cashes in, A will get 2/3 of the profits and B 1/3. A and B can also sell their equity to 3rd parties any time they want.</p>

<p>This would be implemented by having a (quite exotic) contract for service between company X and independent contractors A and B. </p>

<p>Now consider the two following scenarios:</p>

<ol>
<li><p>The app ends up grossing very little or nothing at all, meaning that hourly rate for A and B would be way below minimum wage. This would obviously mean a disaster for company X if the authorities interpreted the relationship as employer-employee, so that is why we absolutely need to steer clear of it.</p></li>
<li><p>Freelancer C joins the project and does 10 hours of design work. Let's say that C his main source of income from a steady 9-5 elsewhere and does not really do freelancing other than this gig. While setting up a service company for A and B would possibly be an option (given that this is not their only collaboration under company X), the overhead for C would be completely unbearable. </p></li>
</ol>

<p>This is a well established model in the UK. One route is the <a href="https://en.wikipedia.org/wiki/Umbrella_company" rel="nofollow">umbrella company</a>. Y here would be the umbrella company. A would then either be providing services to Y or be employed by Y. You may be wondering what use it is if A is employed by Y. The answer here is that whilst A may not benefit from the tax treatment, X does not bear the burden of running PAYE etc. Further, because of regulations such as <a href="https://en.wikipedia.org/wiki/IR35" rel="nofollow">IR35</a>, it may be that there is a doubt as to whether employment tax apply even if there is a contract for service. Essentially disguised employment means taxes are levied on the employer as if an employment existed; however, in this situation X has the comfort that if this arises they will (normally) fall on Y rather than X. Another route is the service company, where normally A himself will own it (or it is owned between A and A's spouse), take a combination of salary and dividends out (using two allowances if owned between spouses), and he will bill X or Y; companies exist which will perform all the necessary paperwork to do this (in which case Y is called a <a href="https://en.wikipedia.org/wiki/Managed_service_company" rel="nofollow">managed service company</a>), as opposed to a personal service company (if A sets it up himself).</p>

<p>It's not clear where you are based, but if you are based outside the UK (and possibly if you are inside the UK) there are accountancy companies that specialise in setting all this up. </p>

<blockquote>
  <p>Can a company handle paying taxes and other bureaucracy work for a freelancer?</p>
</blockquote>

<p>Yes. The recipe is not very easy but robust:</p>

<ol>
<li>No employee-employer relationships / contracts <em>of</em> service with the freelancers whatsoever. This is not just because of the minimum wage concerns, but also because of visa/work eligibility issues in case you go beyond EU for finding freelancers;</li>
<li><strong>Divide and conquer</strong>: the freelancers will have two separate contracts:

<ol>
<li>Contract for service CFS1 where A (or company Z owned by A, see below) provides services to X e.g. hourly paid programming/design work. To avoid doubt, this will have nothing about the A's taxes/pensions etc. as if A had to worry about that stuff like a classic independent contractor;</li>
<li>Contract for service CFS2 where Y (or even X) provides accounting/compliance managing services for A. This will include the registration of sole trader (or even a company Z completely owned by) A, filling annual returns, paying taxes and whatnot to make A not worry about anything but the work itself. In this contract, A will authorise Y/X to act on his/her behalf to the extent required to make their work bureaucracy-free, even if this will require nominating people from Y/X to be the directors of Z.</li>
</ol></li>
</ol>

<p>Now, the most challenging bit in that scheme is this:</p>

<blockquote>
  <p>Freelancer A (and others), located somewhere in EU, ideally the globe.</p>
</blockquote>

<p>Essentially, Y/X would need to design separate CFS2 solutions for every country/jurisdiction A may reside in, learn location-specific nuances and communicate with the corresponding authorities. Say in some places it might be enough to register A as a sole trader and file personal income tax returns, while in others you might need to register company Z and figure out how to Z will pay to A.</p>

<p>Hint: find a local accounting-focused freelancer in every place you want to have freelancers from ;)</p>
