Maker

📌

Hey! I'm Michael, I've been building Bankstatemently (a bank statement converter) for the past 6 months. Here's the thing: I'm doing something a bit crazy. I'm giving away all the edge cases I've found while building my product. The stuff other companies would call their IP. While processing bank and credit card statements, I kept discovering quirks that break parsers. I've affectionately started cataloging them, and I'm at 36 now. Things like credit card charges showing up as positive numbers, Thai Buddhist calendar dates (year 2568 instead of 2025), or transaction dates hiding inside the description text. Why would I give this away? Because the challenges aren't a secret. Solving all of them at once, reliably, at scale is actually the hard part. Real bank data is private, so I've turned these challenges into synthetic statements that deliberately include them. 5 are live now, 10 more coming. Each uses a fictional bank with realistic formatting. No real customer data. I also had some fun designing them. Lastly, there's a free evaluation API. Submit your parsed output, and get accuracy scores back. I dare you to get a 100% 🙂 If you know a parsing challenge that's not in the list, tell me. The next 10 statements will partly depend on what you tell me is missing Thanks!

Report

5mo ago

Sans Writer

Love this Michael 💪

Report

5mo ago

Maker

thanks for you unwavering support, @angus_rogers 🙏

Report

5mo ago

This is genuinely helpful!

Report

5mo ago

Maker

@lak7 ah thanks! Glad to know that

Report

5mo ago

Bankstatemently Open Benchmark

Free synthetic bank statements for testing parser accuracy

Free synthetic bank statements for testing parser accuracy