Built in a practice, not a startup office

myfinmak started with a straightforward annoyance: a client would send a year of bank statements as a PDF, and someone in the office would spend the better part of a day retyping them into Excel. Every tool that promised to do it automatically either broke on Indian statement formats, split one transaction across three rows, or — worse — produced numbers that looked right and were not.

So we wrote our own. It was used on real client statements for months before anyone thought of putting it online. The features exist because a real file broke the tool and it had to be fixed: multi-line narrations, scanned co-operative bank statements with no text layer, PDFs locked with the client’s date of birth, and the running-balance check that catches a mis-read figure before it reaches a filing.

Why we check the balance chain

A converter that crashes is annoying. A converter that quietly reads ₹1,17,400 as ₹117.400 is dangerous, because nobody notices until an assessment. Every statement with a running balance column gets reconciled row by row, and you are shown the result. That verification is the point of the tool, not a feature on the list.

Where this is going

The bank statement analyzer is the first of a small set of tools for the repetitive parts of Indian practice work — consolidating multiple accounts, pulling 26AS and AIS into usable schedules, extracting invoice data, reconciling GSTR-2B. Not an accounting platform, not a replacement for anything. Just the specific jobs that eat evenings.

Who is behind it

myfinmak is run from Kerala, India by a practising chartered accountant. Small, self-funded, no investors to answer to — which is why the roadmap is decided by what practitioners ask for rather than what looks good in a pitch deck.