While there are a lot of numbers reported in Citibank's (C) recent quarterly earnings there is ONE critical comparison that is missing -- that is the sequential analysis of the credit losses (Q1 vs. Q2). I believe this is critical information not just for Citibank but for all financials.
First, here are the links to the Q1 report and Q2 report.
Getting to the point on credit losses:
April 17th report: Credit costs of $10.3 billion, up 76%, consisted of $7.3 billion in net credit losses, a $2.7 billion net loan loss reserve build, and $332 million of policyholder benefits and claims. The total allowance for loans, leases and unfunded lending commitments was $32.7 billion.
July 17th report: Credit costs of $12.4 billion, up 81%, consisted of $8.4 billion in net credit losses, and $3.9 billion loan loss reserve build. The total allowance for loans, leases and unfunded lending commitments was $37.0 billion, up from $21.9 billion in the prior year period.
As seen from these numbers, from Q1 to Q2 -- credit costs are STILL RISING. Losses were up by $1.1B and loan loss reserve is also higher by $1.2B. Unfortunately, from these reports, we do not get details of early delinquencies vs. late delinquencies; so a greater analysis of month to month trend is not possible based on these reports (companies like E*Trade Financial provide such details).
But given that on a quarterly basis numbers are still getting worse is an indication that problems at Citibank are FAR from being over. Indeed, increasing unemployment and recent indications that early stage delinquencies may be on the rise. For example, foreclosureradar.com's California report for June 2009, showed the HIGHEST number of notice of default on record ever.
First, here are the links to the Q1 report and Q2 report.Getting to the point on credit losses:
April 17th report: Credit costs of $10.3 billion, up 76%, consisted of $7.3 billion in net credit losses, a $2.7 billion net loan loss reserve build, and $332 million of policyholder benefits and claims. The total allowance for loans, leases and unfunded lending commitments was $32.7 billion.
July 17th report: Credit costs of $12.4 billion, up 81%, consisted of $8.4 billion in net credit losses, and $3.9 billion loan loss reserve build. The total allowance for loans, leases and unfunded lending commitments was $37.0 billion, up from $21.9 billion in the prior year period.
As seen from these numbers, from Q1 to Q2 -- credit costs are STILL RISING. Losses were up by $1.1B and loan loss reserve is also higher by $1.2B. Unfortunately, from these reports, we do not get details of early delinquencies vs. late delinquencies; so a greater analysis of month to month trend is not possible based on these reports (companies like E*Trade Financial provide such details).
But given that on a quarterly basis numbers are still getting worse is an indication that problems at Citibank are FAR from being over. Indeed, increasing unemployment and recent indications that early stage delinquencies may be on the rise. For example, foreclosureradar.com's California report for June 2009, showed the HIGHEST number of notice of default on record ever.
Notice of default is the "first" step towards foreclosure and is the early stage indicator of things to come. June 2009 being worse than the entire last year and this year is indeed quite scary and banks like Citi, Wells Fargo (WFC), Bank Of America (BAC), JPMorgan Chase (JPM) etc. are more likely to be impacted by this than some of the other banks. And this is only mid-summer. Seasonally, things get worse in real-estate late-summer and fall.
While I wish to remain optimistic, and have net long position on financials (through XLF) - it is hard to remain optimistic in light of these numbers. I have tried to hedge my long position in financials with some FAZ.
While I wish to remain optimistic, and have net long position on financials (through XLF) - it is hard to remain optimistic in light of these numbers. I have tried to hedge my long position in financials with some FAZ.
I'm already speechless when talking about this problem. Anyway, thanks for sharing.
ReplyDelete