How a One‑Digit Decimal Error Multiplied Interest Tenfold – Database Lessons

Background

The common interest calculation formula is:

Interest = Principal × Daily Rate. Daily Rate = Annual Rate / 360

Initially the daily rate was stored with 7 decimal places. Later the business required 11 decimal places, so the daily rate was recalculated and stored directly in the database.

After the change went live, the business asked to increase the precision to 11 decimal places for existing data. The developer wrote three SQL statements to update the historic configurations, but one of them contained a typo: the daily rate was written as 0.00069444444 instead of the correct 0.00006944444, inflating the rate ten‑fold.

Because the incorrect value was only a factor of ten, the resulting interest amounts were also ten times larger, but the error was not caught during code review (the developer reviewed his own code) or testing (the test only verified that the SQL executed without syntax errors and that the values had 11 decimal places, not that they were mathematically correct).

Production verification also missed the issue because the developer randomly sampled two rows, both of which happened to be from the correctly updated SQL, giving a false sense of correctness.

Why Was It Not Detected?

The change bypassed a formal code‑review process; the author had both commit and review permissions and approved his own change. The testing phase only checked format and execution, not the actual numeric impact. Production validation sampled a small subset of data, which happened to be correct, so the error remained hidden.

How Was It Exposed?

The mistake surfaced only when, three days after deployment, the author noticed an unusually large interest amount while performing an unrelated data check. Tracing the anomaly led back to the faulty SQL. If this accidental discovery had not occurred, the error would likely have been noticed later by business users during reconciliation.

Reflection

The incident underscores the importance of strict data‑change procedures, multi‑level approvals, and thorough validation beyond mere syntax checks. It also illustrates how a single misplaced digit can cause a cascade of financial errors, and why developers should avoid directly manipulating critical business parameters without proper governance.