This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
StatementDecoder
Find out who's really behind a charge — or convert it
Bank statements are written for payment processors, not people — "SQ *BLUE BTTL 0412" is a coffee shop. Paste one cryptic charge and StatementDecoder names the merchant with a confidence level, or upload a whole statement (PDF, CSV, Excel or a photo) and get every line identified, subscriptions and yearly cost surfaced, fees and duplicates flagged, and the totals reconciled against the statement itself. Exports to CSV, Excel, QuickBooks, Xero, QIF, OFX. No bank logins; files deleted in 24h.
Hi PH 👋 I built this because I kept getting charges I couldn't recognise and hated the choice between "panic-dispute" and "ignore it." The name on a statement is almost never the shop you paid — it's the processor (SQ*, PAYPAL*, TST*) or a legal holding-company name.
So it does two things: decode a single descriptor, or read a whole statement. Structured files (CSV/OFX) are parsed exactly; PDFs that defeat rule-based parsers go through AI extraction, and every date and amount is re-validated by code afterwards — and if the totals don't reconcile against the statement's own balances, it tells you instead of hiding it. Matches carry honest confidence labels; it never pretends certainty.
Since then it's grown past statements: invoices, receipts, purchase orders and general PDF tables go through the same path, with the line items checked against the subtotal, tax and total before you're asked to trust them.
It's early and I'd love the brutal feedback — especially weird bank PDF layouts that break it. Happy to answer anything about the parsing horrors.
About StatementDecoder on Product Hunt
“Find out who's really behind a charge — or convert it”
StatementDecoder was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #82 on the daily leaderboard. Bank statements are written for payment processors, not people — "SQ *BLUE BTTL 0412" is a coffee shop. Paste one cryptic charge and StatementDecoder names the merchant with a confidence level, or upload a whole statement (PDF, CSV, Excel or a photo) and get every line identified, subscriptions and yearly cost surfaced, fees and duplicates flagged, and the totals reconciled against the statement itself. Exports to CSV, Excel, QuickBooks, Xero, QIF, OFX. No bank logins; files deleted in 24h.
On the analytics side, StatementDecoder competes within Productivity, Fintech and Accounting — topics that collectively have 709.2k followers on Product Hunt. The dashboard above tracks how StatementDecoder performed against the three products that launched closest to it on the same day.
Who hunted StatementDecoder?
StatementDecoder was hunted by John Ajimoti. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of StatementDecoder including community comment highlights and product details, visit the product overview.
John Ajimoti