Skip to main content

The stupidity of systems

A couple of weeks ago, I called the customer service at PayFlex. PayFlex is the company used by my employer to manage our Flexible Spending account. Usually the threat of losing unused money kept me away from participating in the plan. But since I was gonna have kids last year, I participated. So on December 31st, I realized that I had some money ($43.34) left over in my account. Well it was 10pm and everywhere was closed on New Year's eve. So I went online to CVS and bought qualifying items using my PayFlex debit card. The receipt was time stamped 10:49pm. Boy was I lucky to have remembered before midnight.

Forward several weeks later and I get an e-mail from my company's HR person saying I still had $43.34 left over. After I got over the shock, I searched my hotmail account and luckily I still had the order confirmation from CVS. I pdf'ed it and uploaded it to PayFlex. Thinking that was the end of it, I checked this morning and low and behold I still had $43.34 left over. Turns out they paid the CVS claim from this year's plan.

I called their customer service said their system shows CVS processed the payment on 1/6/2010. I said that's great but I have a receipt that shows I bought the items on 12/31/2009. Anyway to cut a long story short, her position was this:
  • If I had used any other credit card, merely submitting a claim with my receipt showing 12/31/2009 would have been good enough to get the claim processed in the correct year
  • However, since I used my PayFlex MasterCard, they have to go by the processing date from CVS. So essentially, by using their debit card I am subject to the whims of CVS.
Took me a while to explain the absurdity of that point of view. Eventually, she left, consulted with others and came back with "You have to file an appeal by fax". Yes by fax. In 2010.

I understand the need for organizations to have systems but I hate that people seem to surrender their ability to think. At least in this case, they had a procedure, albeit one that relied on archaic technology, in place. The last time this happened to me, I spent an hour on the phone with VA's DMV trying to make the woman see that their system was wrong. In the end, I got a letter of apology, a free record of my driver's license history and a massive headache.
Reblog this post [with Zemanta]

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology.

InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options:

convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations)use one of Al Gore's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously. You'll need every bit of time you can get.
quit immediately while you still have your sanityFirst, InfoPath:

To me InfoPath is like programming in assembly language. Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button:

in most technology: buttonA.enabled = false (or something similar).

In InfoPath, you simply can't do this.…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horri…