Contact
Email is the only channel — there is no support desk and no chatbot, but messages are read by the person who wrote the tool.
Replies usually go out within two to three working days. Messages are answered by Md Hussain, who builds and maintains this site.
What to write about
A statement did not convert cleanly
Tell me the bank name and what went wrong — missing rows, amounts in the wrong column, dates read as text. Do not attach your real statement; a screenshot with the amounts blurred, or a one-page sample with fake figures, is enough to fix the layout.
Email about thisRequest an export format or software
If your accounting software is not in the list of 42 formats, send its name and a link to its import documentation (or a sample import template). Formats with published layouts usually get added quickly.
Email about thisPrivacy, advertising or data questions
Questions about how files are processed, what cookies the site sets, or a request relating to your data under applicable privacy law.
Email about thisPlease do not send bank statements
A real statement is not needed to fix a parsing problem and email is not a secure way to move one. What actually helps is the bank's name, the row that came out wrong, and a screenshot with the amounts and account number covered. If a sample file is genuinely required, replace every figure with dummy numbers first.
What to include
- Bank name and country — statement layouts differ per bank, sometimes per branch.
- Whether the PDF was digital or scanned — the two are read by completely different code paths.
- The export format you picked — Excel, Tally XML, OFX, and so on.
- What you expected versus what you got — one line each is plenty.