The Baltimore Sun has a story today reporting that a computer problem in State Farm Insurance's automated billing system double-billed monthly premiums this past month.

According to the Sun, nearly 80,000 State Farm customers in Delaware, Florida, Georgia, Iowa, Nebraska, Pennsylvania, Ohio, Maryland, North Carolina, South Carolina, Virginia, West Virginia and the District of Columbia who have monthly premiums automatically debited from their bank account were affected.

State Farm said that it became aware of the problem on Wednesday, and that the problem was corrected by yesterday. The company added, however, that its customers should check their statements anyway and let it know if the problem was not fixed.

The Sun noted that State Farm had another billing problem in May of this year. Nearly 12,500 Visa credit card customers of State Farm Bank were erroneous charged as much as $20,000. That error was a result of a "coding error" at the Bank's credit card billing vendor.

In related billing problem news, the Army and Air Force Exchange Service (AAFES) is warning anyone who used a credit or debit card (except the AAFES Military Star cards) between the 7th and 9th of August at any of its locations world wide to check their card statements for billing anomalies.

An AAFES spokesperson says in this Stars and Stripesarticle that the problem, which was found on the 10th of August, was due to a computer security upgrade:

"During the implementation of a Payment Card Industry application change to provide added protection to customer data through encryption, files with duplicate credit data were transmitted to the credit processing center in error."

AAFES also said customers who were affected didn't have to do anything, although it may take a few weeks for the fix to show up in a customer's billing statement.

AAFES has not said how many of its customers were affected. However, according to the AAFES fact sheet, it operates 3,100 facilities serving 12.2 million customers in 30 countries. So the number is likely to be pretty large.

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
A plate of spaghetti made from code
Shira Inbar

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