<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:wfw="http://wellformedweb.org/CommentAPI/"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
     xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    >
    <channel>
        <title>AdviserVoiceFOS / AFCA transition involves much work for AFL licensees - AdviserVoice</title>
        <atom:link href="https://www.adviservoice.com.au/2018/10/fos-afca-transition-involves-much-work-for-afl-licensees/feed/" rel="self" type="application/rss+xml" />
        <link>https://www.adviservoice.com.au/2018/10/fos-afca-transition-involves-much-work-for-afl-licensees/</link>
        <description>Financial planner information &#38; financial planner education/CPD - AdviserVoice</description>
        <lastBuildDate>Fri, 19 Jun 2026 00:51:49 +0000</lastBuildDate>
        <language>en-US</language>
        <sy:updatePeriod>hourly</sy:updatePeriod>
        <sy:updateFrequency>1</sy:updateFrequency>
        <generator>https://wordpress.org/?v=7.0</generator>
                    <item>
                <title>FOS / AFCA transition involves much work for AFL licensees</title>
                <link>https://www.adviservoice.com.au/2018/10/fos-afca-transition-involves-much-work-for-afl-licensees/</link>
                <comments>https://www.adviservoice.com.au/2018/10/fos-afca-transition-involves-much-work-for-afl-licensees/#respond</comments>
                <pubDate>Mon, 01 Oct 2018 21:45:10 +0000</pubDate>
                <dc:creator>
                                    </dc:creator>
                		<category><![CDATA[Regulation/Reform]]></category>
		<category><![CDATA[Chris Deeble]]></category>
                <guid isPermaLink="false">https://adviservoice.com.au/?p=57820</guid>
                                    <description><![CDATA[<div id="attachment_54891" style="width: 660px" class="wp-caption alignleft"><img fetchpriority="high" decoding="async" aria-describedby="caption-attachment-54891" class="size-full wp-image-54891" src="https://adviservoice.com.au/wp-content/uploads/2018/04/deeble-chris-650.jpg" alt="" width="650" height="350" srcset="https://www.adviservoice.com.au/wp-content/uploads/2018/04/deeble-chris-650.jpg 650w, https://www.adviservoice.com.au/wp-content/uploads/2018/04/deeble-chris-650-300x162.jpg 300w" sizes="(max-width: 650px) 100vw, 650px" /><p id="caption-attachment-54891" class="wp-caption-text">Chris Deeble</p></div>
<h3>By now, all credit and financial services licensees, and superannuation trustees must have joined AFCA. But don’t overlook the additional work required to effectively transition from your existing external dispute body to AFCA by 1 November 2018.</h3>
<p>The two key things you need to do are:</p>
<h2>1. Update documents and your website to refer to AFCA</h2>
<p>Any documents or information on your website that refers to CIO, FOS or the SCT need to be updated.</p>
<p>Different timeframes apply to various types of documents:</p>
<ul class="li-listing">
<li><strong>Disclosure documents</strong> such as FSGs, PDSs and Credit Guides can refer to FOS/CIO from 21 September 2018 to 31 October 2018. By 1 July 2019 they must refer to AFCA.</li>
<li><strong>National Credit Code forms</strong> i.e. the ‘things you should know about’ forms for credit contracts, guarantees and leases i.e. Form 5, 9 and 17 must be updated by 1 July 2019 (provided you update your broader communications about how to complain with AFCA’s details by 1 November 2018).</li>
<li><strong>Other National Credit Code forms and notices</strong> e.g. default notices, must be updated with AFCA’s details by 1 November 2018.</li>
<li><strong>Complaints information </strong>on your website, complaints policy or in brochures can give details of FOS/CIO/SCT from 21 September to 31 October 2018, but must be updated with AFCA’s details by 1 November.</li>
<li><strong>IDR delay and final response letters</strong> must refer to <em>both</em> FOS/CIO/SCT and AFCA from 21 September 2018 to 31 October 2018. By 1 February 2019, these letters must only refer to AFCA.</li>
</ul>
<h2>2. Notify your AFCA membership details to ASIC</h2>
<p>You should have been a member of AFCA by 21 September 2018. You will be able to notify ASIC about your membership between 1 and 30 November 2018. Diarise this, so you don’t forget it.</p>
<p>Yes, it’s complicated, but there’s a helpful table on <a href="http://www.afca.org.au/letting-your-customers-know-about-afca/" target="_blank" rel="noopener">AFCA’s website</a> – it sets out the timeframes and provides AFCA’s preferred disclosures wordings.</p>
<p><em><strong>By Chris Deeble</strong></em></p>
]]></description>
                                            <content:encoded><![CDATA[<div id="attachment_54891" style="width: 660px" class="wp-caption alignleft"><img decoding="async" aria-describedby="caption-attachment-54891" class="size-full wp-image-54891" src="https://adviservoice.com.au/wp-content/uploads/2018/04/deeble-chris-650.jpg" alt="" width="650" height="350" srcset="https://www.adviservoice.com.au/wp-content/uploads/2018/04/deeble-chris-650.jpg 650w, https://www.adviservoice.com.au/wp-content/uploads/2018/04/deeble-chris-650-300x162.jpg 300w" sizes="(max-width: 650px) 100vw, 650px" /><p id="caption-attachment-54891" class="wp-caption-text">Chris Deeble</p></div>
<h3>By now, all credit and financial services licensees, and superannuation trustees must have joined AFCA. But don’t overlook the additional work required to effectively transition from your existing external dispute body to AFCA by 1 November 2018.</h3>
<p>The two key things you need to do are:</p>
<h2>1. Update documents and your website to refer to AFCA</h2>
<p>Any documents or information on your website that refers to CIO, FOS or the SCT need to be updated.</p>
<p>Different timeframes apply to various types of documents:</p>
<ul class="li-listing">
<li><strong>Disclosure documents</strong> such as FSGs, PDSs and Credit Guides can refer to FOS/CIO from 21 September 2018 to 31 October 2018. By 1 July 2019 they must refer to AFCA.</li>
<li><strong>National Credit Code forms</strong> i.e. the ‘things you should know about’ forms for credit contracts, guarantees and leases i.e. Form 5, 9 and 17 must be updated by 1 July 2019 (provided you update your broader communications about how to complain with AFCA’s details by 1 November 2018).</li>
<li><strong>Other National Credit Code forms and notices</strong> e.g. default notices, must be updated with AFCA’s details by 1 November 2018.</li>
<li><strong>Complaints information </strong>on your website, complaints policy or in brochures can give details of FOS/CIO/SCT from 21 September to 31 October 2018, but must be updated with AFCA’s details by 1 November.</li>
<li><strong>IDR delay and final response letters</strong> must refer to <em>both</em> FOS/CIO/SCT and AFCA from 21 September 2018 to 31 October 2018. By 1 February 2019, these letters must only refer to AFCA.</li>
</ul>
<h2>2. Notify your AFCA membership details to ASIC</h2>
<p>You should have been a member of AFCA by 21 September 2018. You will be able to notify ASIC about your membership between 1 and 30 November 2018. Diarise this, so you don’t forget it.</p>
<p>Yes, it’s complicated, but there’s a helpful table on <a href="http://www.afca.org.au/letting-your-customers-know-about-afca/" target="_blank" rel="noopener">AFCA’s website</a> – it sets out the timeframes and provides AFCA’s preferred disclosures wordings.</p>
<p><em><strong>By Chris Deeble</strong></em></p>
<p>The post <a href="https://www.adviservoice.com.au/2018/10/fos-afca-transition-involves-much-work-for-afl-licensees/">FOS / AFCA transition involves much work for AFL licensees</a> appeared first on <a href="https://www.adviservoice.com.au">AdviserVoice</a>.</p>
]]></content:encoded>
                                    <wfw:commentRss>https://www.adviservoice.com.au/2018/10/fos-afca-transition-involves-much-work-for-afl-licensees/feed/</wfw:commentRss>
                <slash:comments>0</slash:comments>                            </item>
            </channel>
</rss>