Comcast Threatens To Cut You Off Unless You Pay $0.00
This should be an easy one to resolve. Readers Rich and Alisa doesn't owe Comcast any money, and Comcast doesn't want them to pay any money. Still, despite this agreement about what is owed, the cable giant still felt the need to threaten to cut off their cable.
Alisa says:
So apparently, if we don't pay Comcast $0.00 by Monday, we'll get cut off.
Hey, we think you should pay them. If you don't, it says they'll cut off your 911 service.

Post a comment
Comments:
@azzie: I was thinking this also. Make sure to request a refund for overpayment too because I think most companies will not issue a refund for a few cents. it will end up costing them money
@egogg: That would be the equivalent of handing someone a soggy or halfway ripped dollar bill. Send them a blank sheet of paper.
I bet there's a fraction of a cent still on his account that the mail merge program is not catching.
After all: .1 of a cent rounded up is 0 cents to a program set to the $0.00 format. It'll take a sharp CSR or high level support to clear that one up...
EECB this one. Don't let it slip through the cracks or they'll get stupid (EG, send it to collections and that will ding your credit).
@Nighthawke: How would you even get a fraction of a cent on your account, except via software error?
@johnva: Sorry, it cut off my comment for some reason...
I meant to add that if it is a software error, I don't envy them the task of getting Comcast to admit that. It will be a wall of "the computer can't be wrong" when they call in.
@Garbanzo: I'm not sure how the law works for digital phone service, but cutting 911 is a big no-no. If a teleco were to try this i would guess the FCC or some emergency notice board would have some words for them.
Time is of the essence; don't mail a check, go to one of the walk-in payment centers and personally give them your check for $0.00. And be sure to get a receipt.
Send them a check for $1. What is probably happening is that there is a $.009 or less amount on the bill. The screens of the operators are formatted to show $.01 or greater so they do not see it. The bill if formatted to print $.01 or greater so it does not print the amount. However, the program behind the scenes is told to look for anywhere there is an amount greater than 0. $.009 is greater than 0 and that means that activity needs to happen on this account. Computers can only see in shades of 1 and 0, either true or false. They cannot recognize special situations unless programmed to recognize these situations.
Sending $1will pay off this account with some left over. You can send a smaller amount but $1 will play it safe. It will pay off whatever small amount is out there and then they can send you back the remainder.
@johnva: That is it, exactly. Monetary amounts are often stored as floating-point values. These have a tendency to be off by very small amounts, the maximum error usually somewhat proportional to the magnitude of the number (i.e. .0000001 might be of by only .0000000000000001 while 1000000000000000000 might be off by 1 or 2). This lack of precision is a daily fact of life in computing technology, and usually is small enough to ignore and correct by rounding.
The problem comes in the logic that decides that the bill is delinquent. It should be looking at whether the balance is less than $0.01, rather than less than or equal to $0.00, in order to squash this sort of nonsense.
@kc2idf: @johnva: I can see that. Any time you have a prorated portion of your bill, this would come into play. The explanation makes perfect sense, but given how often they have to prorate things, you'd think they'd have a decent number of angry customers with $0.00 bills and threats of service termination! Hope they kick some Comcastic ass.
@kc2idf: This is why competent programmers will usually store monetary values as an integer number in cents. (so $1.99 would be stored as the integer 199)
@kc2idf: You mean there are still programmers that dumb to use floating point numbers? A 64-bit integer could be used to process amounts up to $92,233,720,368,547,758.07 (and that's a lot of movies).
@kc2idf: If they're storing monetary values as floating point numbers in their accounting system, they need to fire their programmers. In accounting you should *always* used fixed-point math to avoid the exact problem you describe.
For the same reasons, good programmers who work with floating-point numbers learn to avoid using exact comparisons. Conditions like "if (amount == 0)" are bugs waiting to happen. Much better to use something like "if (amount < 0.01)".





















Bring exact change.