In a personal finance application, the most catastrophic bug is not a UI glitch, an unexpected crash, or a missing icon.

The most catastrophic bug is balance drift .

Balance drift occurs when an account balance displayed on the dashboard slowly diverges from the mathematical reality of its underlying transactions. The user has 15,000 rupees in their bank, but the app displays 14,200 rupees.

Once users notice that their account balance does not match their real bank statement, they lose all faith in the application.

Here is how FinLedger solved balance drift by establishing a single, authoritative posting engine in pure Kotlin.

The Architectural Flaw: Scattered Accounting Math

When apps grow quickly, financial calculations tend to scatter across different layers:

The TransactionViewModel updates a local state variable when a user creates an expense.

The AccountRepository runs an UPDATE accounts SET balance = balance - amount SQL query.

The DashboardScreen recalculates net worth by folding over…