Mahipal Jyani

Financial integrations aren't like other integrations. When you sync a contact record wrong, someone's name is misspelled. When you sync a journal entry wrong, the books don't balance and an accountant calls you at 4 PM on a Friday asking why the trial balance is off by $47,000.

The QuickBooks integration Mahi built handles three distinct journal entry types. Disbursements and advances — money going out to borrowers. Repayments — money coming back in. Closing costs and fees — the operational revenue that keeps the lender running. Each type has its own debit and credit structure, its own account mappings, and its own edge cases. The sync is bi-directional, which means changes in either system have to propagate correctly to the other without creating duplicates or orphan records.

The loan modification engine is similarly unforgiving. When a borrower's terms change — interest rate adjustment, term extension, principal reduction — every downstream calculation has to recompute: remaining interest, updated payoff amount, revised fee schedule, new amortization table. Version three of the engine handles all of this, including modifications on top of modifications, because that's what happens in real lending — terms change, and then they change again.

This is the kind of work where you need someone who won't cut corners. Where “close enough” doesn't exist. Where the code has to be right, not because of professional pride (though there's that too), but because real money moves based on the numbers. Mahi is that person.

Having a development partner you can trust with the hard problems is invaluable. Not a contractor you have to micromanage. Not someone who needs every requirement spelled out in a 30-page document before they can write a line of code. A partner who understands the domain, grasps the business logic, and ships working solutions.

Mahi is that partner. He works with me at Cloud Nimbus LLC on the Salesforce development for Mobilization Funding. When I needed the QuickBooks integration built — bi-directional journal entry sync across three entry types, correctly mapping debits and credits for each — Mahi shipped it. When the loan modification engine needed to be upgraded to handle cascading term changes, Mahi shipped v3. When the financial calculations needed to be bulletproof because real loan economics depended on them, Mahi made them bulletproof.

The thing about working with Mahi is that you can throw a complex problem over the wall and know it's going to come back solved correctly. Not “mostly working.” Not “works in the happy path.” Correctly. With the edge cases handled. With the error scenarios accounted for. That's rare in this industry, and it's what makes Mahi essential to what we've built at Mobilization Funding.

His consultancy is called Untangle It, and I can confirm — that's exactly what he does. Every codebase gets tangled eventually. The business adds requirements. Edge cases multiply. The original architecture can't quite handle what the business needs now. Mahi steps in and untangles it. He refactors the logic, restructures the flow, and delivers something clean and correct. Then we ship it and move on to the next hard problem.