MoneyKit
Menu

Methodology — How MoneyKit Computes Every Number

Last updated

Precision: every engine, every time

Every MoneyKit calculator uses high-precision decimal arithmetic so 30-year EMI totals or ₹100 crore retirement corpora match the bank’s and the regulator’s figures to the rupee. Native floating-point numbers are never used for monetary math — they drift by thousands of rupees over long horizons.

Input validation

Every engine validates its input against a strict schema (type, range, required fields). Invalid input throws a typed error rather than returning a silently-wrong result. Boundary values and out-of-range inputs are exhaustively covered by the test suite.

How we cross-check

Test pyramid

Regulatory references & update cadence

Every rate, slab, or threshold has a citation and a _next_review date. When the review date passes, the fixture test fails until a maintainer confirms the number is still current (or updates it). This prevents silent regulatory drift. The current reference set covers:

What this isn’t

MoneyKit output is a reference figure, not advice. Taxes, penalties, and bank offers vary with individual circumstances that no calculator can capture (DTAA treatment, legacy grandfathering, specific bank’s floor rate, etc.). Before acting on a material decision, consult a Chartered Accountant or a SEBI-registered Investment Adviser. See our financial disclaimer.