The December 2022 issue of IEEE Spectrum is here!

Close bar

In January of this year, the Wall Street Journal ran an interesting article about the potential computer integration problems banks were facing in light of all the mergers and acquisitions that were taking place. One bank highlighted was Toronto-based TD Bank, which had bought Commerce Bank in 2008.

The story noted that "about half of parent TD Bank Financial Group's 1,075 branches on the East Coast have two computer systems that can't talk to each other," and that this autumn, TD Bank would undertake the integration of the two systems.

The WSJ story went on to say that:

"TD began handling transactions by hand from its entire customer base at the combined bank's branches within days of the Commerce deal's completion. About half those locations were merged into one computer system in November."

"TD still uses a second system in those branches to handle customers like Mr. McKitty, who opened his account at a Poughkeepsie, N.Y., branch of TD Banknorth about a decade ago. That is the longtime name of TD's bank unit in the U.S., but it will be phased out this fall."

"Could it have been a nightmare? Absolutely,' says Linda Verba, who runs TD's retail operations in the mid-Atlantic region. 'But it got us closer to doing a big-bang system conversion and working out the bugs before we pulled the switch.' "

Well, if you read all the news reports this week, TD Bank did not work out all the bugs before its big-bang conversion and is now dealing with a nightmare situation after all.

This past Saturday, TD Bank merged the computer systems of two acquisitions: Banknorth in Maine and Commerce Bank in Cherry Hill.

Problems with the conversion became rapidly apparent by Monday morning.

This morning's Philadelphia Inquirerstory gives a nice accounting of the situation:

"Typically at any bank, customers deposit or withdraw money, write checks, or transfer funds online, in the bank, in stores, and at ATM machines during the day. All those transactions get reconciled overnight in a process known as "batch posting."

"On weekends batch posting takes place just after midnight on Sunday and into early Monday morning."

"Over the last weekend, after warning customers about the change, TD's computer people merged the two bank's systems. The trouble showed up with the first batch posting in the new system. Instead of finishing early Monday morning, the process took well into the day, leaving customers confused. Each subsequent night's batch posting had problems, and it will not be clear until this morning whether the problem is fixed."

No word at the time of this post whether last night's postings went well or not.

In addition to the posting issue, direct deposits like Social Security checks were not showing up in customer accounts, nor were automatic bank payments (like mortgage and tax payments) being made. Depositors also did not know whether they were overdrawn on their various bank-related accounts.

To say the least, a great number of the bank's 6.5 million customers are not happy, with many complaining that they cannot reach customer service for help.

This New York City CBS2 television channel report stated, probably with a bit of hyperbole, that,

 "Online computer glitches with direct deposit created a near run on the bank."

TD Bank hasn't helped itself much either by repeatedly declaring this week that the computer problem has been fixed, only for it to continue unabated.

The bank has issued a statement on its web site promising that the problems will all be resolved very soon and it has pledged to reverse any "fees, charges or interest incurred" as a result of the computer problems.

That may take awhile, however.

There is also no saying how long it will take TB Bank to regain its customers' trust.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}