Can accounting errors ruin your life? JohnOliver explains how they can.

In this episode Last Week Tonight, John Oliver explores the world of debt buying:



The segment received wide publicity as he tried to out do Oprah by conducting the biggest giveaway on television - he bought $15 million worth of medical debt and forgave it. This article on Fortune does a good job of summarizing the show:

• US households owe $12 trillion in debt of which $436 billion is 90+ days past due. 
• Companies who discharge the debt sell it for pennies on the dollar to a growing number of companies that specializes in debt buying.  
• One company, Encore Capital, notes that in 1 in 5 Americans owes or has owed them money. 
• Debt that's been paid "come back to life", which is affectionately known as Zombie debt.

There was some controversy, however, about who he worked with to write-off the debt (they noted their grievances here, to which John responded here) and the value of the debt. On the latter count, is it really fair to criticize an act of charity that improved the lives of approximately 9,000 people?  

Nothing good happens in Excel. 
But the segment which is most relevant to us is when he starts talking about how the information is actually sold.  It is sold on spreadsheets. Oliver gets quite dramatic as he shares his his phobia of Excel and notes how "nothing good happens in Excel". He also explains that the spreadsheets are sold "as is"; meaning that the seller does not guaranty accuracy of the information related to the debt contracts being sold.

And that's where the jokes stops.

In the segment, he has footage from interviews with Jake Halpern, who wrote "Bad Paper: Chasing Debt from Wall Street to the Underworld". The book follows the life of a debt buyer of Aaron Siegel, who is born to a rich family in Buffalo, New York. He takes an array of characters, including his Brandon, who is an ex-con who does that gritty part of work of finding the debt, ensuring its good and collecting on it.

What caught my attention as I was going through book, is that it gave a bit more detail to what John Oliver mentioned about the banks selling the paper "as is". Halpern notes on page 58 of his book (see below for the link to the book), that when Washington Mutual sold Joanna and Theresa's debt to Aaron, the credits awarded against their accounts that were not reflected in the spreadsheet that was given to the debt buyer.


And that's how accounting errors can ruin lives.

When you read the life stories of these two ladies it's heart wrenching to think that a few lines on an Excel spreadsheet could have a detrimental impact on their lives. Some would cynically say this is over dramatic and try to find reason to blame Joanna and Theresa falling into this problem. But I don't think that's fair. When you read the lives of these people, it's clear that they were affected by factors beyond their control. It's really this broken system of debt collection that is responsible for them failing to get the debt relief that they were owed.

The way accounting systems and spreadsheets are designed and operated can have real impact on real people. As an accountant myself, I often wondered what value is accounting in the grand scheme of things. But as Halpern's story illustrates the accountants, bookkeepers, etc. had a real impact on the livesof these two women.

No one is saying that accountants have the same impact on the lives of people the way a cancer specialist does. But at the same time a few a lines on Excel spreadsheet could be the difference between perpetual anxiety and a good nights sleep.

BNY Mellon Software Glitch: Time to make SysTrust mandatory?

As was widely reported in the business press, BNY Mellon experienced a technical glitch that affected its ability to price mutual funds accurately. Based on the press release from one of the affected funds, the problems started on Monday August 24th, where one of BNY Mellon's system "InvestOne" managed by SunGard was pricing about 800 mutual funds inaccurately.

So what was the cause of this fiasco?

According to CNN, "BNY Mellon outage occurred after a SunGard accounting system it uses became "corrupted" following an upgrade. A back-up also failed."

Normally, this type of thing will force the party experiencing the breach intense scrutiny over what went wrong. However, as I went through the timeline posted by the company, I found (reading between the lines) that they did a number of things right, such as:

• Incident Management Communication Plan: One of the aspects of incident management is communicating to the public and making them aware of the issue. As it can be seen, the company posted details on estimates as to when the system would be ready as well as what was the source of the delay when they didn't meet their estimated deadline. 
• Contingency planning: BNY Mellon was able to get the Net Asset Values (NAVs) "using a secondary and more manual process" to the clients without the production system. According to WSJ, this involved "mobilizing more than 100 accountants to manually calculate the values of thousands of fund securities". The secondary procedure was not perfect as small differences were noted between the fund and, as reported the WSJ, this could expose the bank to "potential liability from the resolution of trades that may have been made during the pricing fog".  
• Effective Service Level Agreement (SLA) with SunGard: Based on the close coordination with SunGard, it appears that they were able to get SunGard to eventually rebuild the system "from scratch". 

That being said, there is always room for improvement. When I was reflecting on this, I speculated that this was another case of inadequate testing of the system upgrade. However, according to SunGard, this was not the case. As they noted on their website:

"The issue appears to have been caused by an unforeseen complication resulting from an operating system change performed by SunGard on Saturday, August 22nd. This maintenance was successfully performed in a test environment, per our standard operating procedure, and then replicated in SunGard’s U.S. production environment for BNY Mellon. This change had also been previously implemented, without any issues, in other InvestOne environments. Unfortunately, in the process of applying this change to the SunGard production environment of InvestOne supporting BNY Mellon’s U.S. fund accounting clients, that environment became corrupted. Additionally, the back-up environment hosted by SunGard, supporting BNY Mellon’s U.S. fund accounting clients, was concurrently corrupted, thus impeding automatic failover. Because of the unusual nature of the event, we are confident this was an isolated incident due to the physical/logical system environment and not an application issue with InvestOne itself."

Given my background as a CA, CPA and CISA, I have always thought it is an odd contradiction that we expect infrastructure (road, dams, bridges, etc.) to be certified by engineers to be in working order (key word is expect, as John Oliver notes in the video below, this is not exactly up to snuff!), but do not have the same expectations for the technology that runs the Information Age.

And that's where I have always proposed that it is necessary to have a framework like SysTrust (now SOC2 and SOC3) in place that requires companies to ensure that their systems are reliable: secure, available, and able to process information without messing it up.

Based on the experience between SunGard and BNY Mellon, I think it actually proves the case. Although companies, like SunGard, likely have such controls in place it is beneficial to others to have a second set of eyes on those controls, ensuring that they are in place, are designed effectively and are operating effectively. The reason is that with such mandatory audits in place, it will allow for the circulation of best practices through such audits. This occurs in the financial auditing world through "management letter points".

One other area that we should explore is the total impact of this error, as it will give insights into the "total impact of failed IT controls". This will be the topic of the next blogpost.