<?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/"
     xmlns:georss="http://www.georss.org/georss"
     xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
     xmlns:media="http://search.yahoo.com/mrss/">
    <channel>
        <title><![CDATA[banking fraud - Savage Villoch Law]]></title>
        <atom:link href="https://www.savagelaw.us/blog/tags/banking-fraud/feed/" rel="self" type="application/rss+xml" />
        <link>https://www.savagelaw.us/blog/tags/banking-fraud/</link>
        <description><![CDATA[Savage Villoch Law's Website]]></description>
        <lastBuildDate>Wed, 06 Nov 2024 17:43:54 GMT</lastBuildDate>
        
        <language>en-us</language>
        
            <item>
                <title><![CDATA[In Wells Fargo Accounts Fraud Case, the Hits Keep Coming]]></title>
                <link>https://www.savagelaw.us/blog/wells-fargo-accounts-fraud/</link>
                <guid isPermaLink="true">https://www.savagelaw.us/blog/wells-fargo-accounts-fraud/</guid>
                <dc:creator><![CDATA[Savage Villoch Law, PLLC]]></dc:creator>
                <pubDate>Fri, 12 May 2017 14:00:23 GMT</pubDate>
                
                    <category><![CDATA[Blog]]></category>
                
                
                    <category><![CDATA[33602]]></category>
                
                    <category><![CDATA[accounts fraud]]></category>
                
                    <category><![CDATA[attorney]]></category>
                
                    <category><![CDATA[banking fraud]]></category>
                
                    <category><![CDATA[business litigation]]></category>
                
                    <category><![CDATA[financial fraud]]></category>
                
                    <category><![CDATA[identity theft]]></category>
                
                    <category><![CDATA[investment banking]]></category>
                
                    <category><![CDATA[investment-loss recovery]]></category>
                
                    <category><![CDATA[protecting your investments]]></category>
                
                    <category><![CDATA[tampa]]></category>
                
                    <category><![CDATA[Wells Fargo]]></category>
                
                
                
                <description><![CDATA[<p>We all remember that nastiness about Wells Fargo, right? You know, that little PR debacle where it turned out that, due to unrealistic sales initiatives, Wells Fargo employees initiated accounts fraud against millions of consumers. After the story broke, Wells Fargo lost a major vote of consumer confidence. The following weeks saw many customers closing&hellip;</p>
]]></description>
                <content:encoded><![CDATA[

<p>We all remember that nastiness about Wells Fargo, right? You know, that little PR debacle where it turned out that, due to unrealistic sales initiatives, <a href="http://54d.d17.myftpupload.com/blog/wells-fargo-pays-false-accounts-claim/" rel="noopener noreferrer" target="_blank">Wells Fargo employees initiated accounts fraud against millions of consumers</a>.
After the story broke, Wells Fargo lost a major vote of consumer confidence. The following weeks saw many customers closing accounts and executives getting raked over the coals, culminating in the resignation of the CEO and a large scale termination of employees who had participated in accounts fraud.
Finally, it seemed the dust had settled. The banking giant was ordered to pay out $190 million in federal fines and reparations to affected consumers. The bank also promised a change to corporate culture and initiatives, <a href="http://54d.d17.myftpupload.com/blog/wells-fargo-fraud-update/" rel="noopener noreferrer" target="_blank">announcing an end to aggressive sales goals.</a>
</p>


<h4 class="wp-block-heading"><strong>More Than Previously Expected</strong></h4>


<p>
Now it looks like it’s going to take a lot more than they thought. According to a recent <a href="http://www.reuters.com/article/wells-fargo-accounts-idUSL1N1IF00H" rel="noopener noreferrer" target="_blank">Reuters report</a>, the number of individuals affected by the accounts fraud scandal is far more than previously expected. In fact, it’s nearly double the initial figure.
What was once nearly 2 million unauthorized account creations has now ballooned into 3.5 million.
While the recent estimate is based on new case discoveries and hearings, Wells Fargo attorneys claim that it is largely “hypothetical” and “unverified”. Attorneys representing plaintiffs concur that it may be “over-inclusive”, but that the estimation provides a reasonable base for total compensation to plaintiffs.
</p>


<h4 class="wp-block-heading"><strong>Can a Settlement Be Reached?</strong></h4>


<p>
Understandably, Wells Fargo has been keen to settle the matter. The big bank’s attorneys have already increased its initial settlement figures from $110 million to $142 million to account for more-than-expected numbers of affected accounts.
</p>


<h4 class="wp-block-heading"><strong>Preventing Future Accounts Fraud</strong></h4>


<p>
The best method of preventing becoming a victim to accounts fraud is through awareness and education. Don’t be intimidated by big banks. You have the right to financial security. Make sure you regularly review all current accounts and monthly statements with any financial institution.
You can follow our blog to stay up to date on <a href="http://54d.d17.myftpupload.com/category/blog/" rel="noopener noreferrer" target="_blank">legal tips, news and insights</a>. Contact us with any <a href="http://54d.d17.myftpupload.com/contact/" rel="noopener noreferrer" target="_blank">legal questions or concerns regarding you financial security</a>.</p>


]]></content:encoded>
            </item>
        
    </channel>
</rss>