<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
	<title>Financial Standard Comments - FASEA attempting to re-write law: AFA</title>
	<description>The Financial Adviser Standards and Ethics Authority is using its Code of Ethics to re-write the law rather than providing genuine guidance to financial advisers, the industry association believes.</description>
	<link>https://www.financialstandard.com.au/feed/latest?story=149018438</link>
	<lastBuildDate>Mon, 02 Dec 2019 12:47:40 +1100</lastBuildDate>
	<pubDate>Mon, 02 Dec 2019 12:47:40 +1100</pubDate>
	<language>en-AU</language>
	<copyright>Copyright 2026 Financial Standard</copyright>
	<ttl>5</ttl>
	<item>
		<title>Comment by Roger Patterson (Blue Path)</title>
		<link></link>
		<guid isPermaLink="false"></guid>
		<description><![CDATA[
<p><p>From someone with no dog in this race, I couldn&#39;t help notice another conflict of interest: adviser organisations shooting from the hip at the Code of Ethics in a desperate attempt to stay relevant. Of course, they suffer zero consequences from getting their criticisms wrong?unlike their misled, confused members who have to sit the exam. Remuneration under the Code is really not unclear. Read Standard 7 and the Royal Commission report: the Part 7.7A Div 4 ban on *adviser* Conflicted remuneration is preserved. Exceptions under the Act are exceptions under the Code. The Code however also prohibits the payments Commissioner Hayne had concern about, for recommending ones own products and recommending action when none was appropriate. All FASEA&#39;s latest Guidance does is explain how certain specific cases will be dealt with. Unfortunately the more guidance FASEA produces the more some parties with no interest in understanding it will try to hang FASEA with it.</p></p><p><a href="">Reply to article</a></p><p>For original story, <a href="">Click Here.</a></p>
]]></description>
		<dc:creator>Roger Patterson (Blue Path)</dc:creator>
		<pubDate>Mon, 02 Dec 2019 12:47:40 +1100</pubDate>
	</item>
</channel>
</rss>