10.07.2015 Views

Transfer pricing perspectives: Winds of Change - PwC

Transfer pricing perspectives: Winds of Change - PwC

Transfer pricing perspectives: Winds of Change - PwC

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The recent decision <strong>of</strong> the Tax Court<strong>of</strong> Canada (“TCC”) in Alberta PrintedCircuits Ltd. v. The Queen included someinteresting observations regarding risks42 <strong>Transfer</strong> Pricing Perspectives. October 2011Perspectives on risk from CanadaThe Canada Revenue Agency (CRA) wasactively involved in developing Chapter 9<strong>of</strong> the OECD Guidelines, but it is too soonto tell how it will interpret and apply thisguidance. That said, the CRA has statedthat business restructuring is a primaryarea <strong>of</strong> focus, and this is evident from itsaudit activity. Subsection 247 (2)(b) <strong>of</strong>Canada’s Income Tax Act actually gives theCRA a specific statutory tool (in additionto a broad General Anti-Avoidance Rule)to support “re‐characterisation”. Thissubsection, which has been actively usedby the CRA since its introduction in 1997,addresses transactions that “would nothave been entered into between personsdealing at arm’s-length” and, in certaincircumstances, authorises the CRA toamend these to transactions “that wouldhave been entered into between personsdealing at arm’s-length” under arm’s-lengthterms and conditions. As <strong>of</strong> June 2011,48 re‐characterisation cases have beenconsidered (such cases must be reviewedand approved by a senior CRA committeebefore they can be pursued by auditors),with 11 assessed and 10 ongoing. It is ourexperience that the allocation <strong>of</strong> risk istypically an important factor in these cases;audits routinely probe where risks aretruly borne and whether the ‘risk-bearer’has the financial capacity and managerialsubstance to bear the risk.However, even with Chapter 9 in hand asa defence, taxpayers should be aware thatthe CRA strongly endorses a transactionalapproach to transfer <strong>pricing</strong>. For example,a “risk-transfer payment” that reduces aCanadian entity’s pr<strong>of</strong>it to a certain levelmust be strongly supported by evidence<strong>of</strong> the arm’s-length nature <strong>of</strong> the actualpayment (i.e. matching the payment withwhat the payment is for) rather than relyingon a TNMM analysis to support the pr<strong>of</strong>itleft behind in Canada.The recent decision <strong>of</strong> the Tax Court <strong>of</strong>Canada (“TCC”) in Alberta Printed CircuitsLtd. v. The Queen included some interestingobservations regarding risks. The caseinvolved Alberta Printed Circuits Ltd.’s(“APCI Canada’s”) payment <strong>of</strong> service feesto a related company in Barbados (“APCIBarbados”). The TCC found that APCIBarbados (as a captive service provider)bore the biggest market risk because ithad only one customer (i.e. APCI Canada,the service recipient), leading the TCCto conclude that APCI Barbados couldnot be an appropriate tested party forapplication <strong>of</strong> the TNMM. As this scenariois common in related party transactions,a careful analysis <strong>of</strong> the balance <strong>of</strong> risksin service-provider transactions should beincluded in any Canadian transfer <strong>pricing</strong>documentation. Further, because theCRA places a lot <strong>of</strong> weight on the terms <strong>of</strong>legal agreements, companies that want togenuinely transfer the significant risks <strong>of</strong>a service provider should ensure that therelevant intercompany service agreementdoes achieve this risk transfer. For example,in the event <strong>of</strong> a closure (e.g. if servicesare no longer required), agreeing that theservice recipient is responsible for closurecosts is one step to support a lower riskpr<strong>of</strong>ile for the service provider.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!