Question

I’ve seen this twice now, and I just don’t understand it. When calculating a “Finance Charge” for a fixed rate loan, applications make the user enter in all possible loan amounts and associated finance charges. Even though these rates are calculable (30%), they application makes the user fill out a table like this:

Loan Amount    Finance Charge    
100            30
105            31.5

etc, with the loan amounts being provided from $5 to $1500 in $5 increments.

We are starting a new initiative to rebuild this system. Is there a valid reason for doing a rate table this way? I would imagine that we should keep a simple interest field, and calculate it every time we need it.

I’m really at a loss as to why anyone would hardcode a table like that instead of calculating…I mean, computers are kind of designed to do stuff like this. Right?

Answer 1

It looks like compound interest where you’re generously rounding up. The 100 case + 1 is pretty boring. But the 105 case + 1 is interesting.

T[0] = FC[105] => 31.5
T[1] = FC[136.5] => ?

Where does 136.5 hit — 135 or 140? At 140, you’ve made an extra $1.05.

Or… If the rates were ever not calculable, that would be one reason for this implementation.

Or… The other reason (and one I would do if annoyed enough) would be that these rates were constantly changing, the developer got fed up with it, and he gave them an interface where the end users could set them on their own. The $5 buckets seem outrageous but maybe they were real jerks…