Statement
Reconciles bank statements against invoices across three file formats. Built for Receipts — build something that makes a messy pile of documents answerable. CSV, PDF, and OFX parsing plus fuzzy matching. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Statement — main view
Statement — result state
On the clock
What shipped, what didn't
Completed in time
CSV, PDF, and OFX parsing plus fuzzy matching.
Unfinished / faked
Fuzzy matcher over-matches on round numbers.
Obstacles
Rate limits hit at minute 20 and forced a caching layer I hadn't planned for.
Lessons learned
Test the demo path once at minute 25. I didn't, and it showed.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Statement data model before writing any interface code. Full prompt log is in the repository under /prompts.
Fairness
Disclosures
Declared by the builder at submission time, visible to judges before scoring.
Reused a personal utility file for date formatting (~40 lines), linked in the repo README.
Judging
Public feedback
Judges' private notes stay private — this is what they chose to say publicly.
Elena Voss
VP of Engineering, Harbor Compute
Good instinct on the problem. I would have liked to see the model doing more of the reasoning rather than formatting output.
Claudia Reyes
Staff Engineer, Vantage Analytics
Nice work under the clock. The unfinished list is longer than the finished one, but what shipped works and you were straight about it.
Hana Kobayashi
Principal Research Engineer, Independent
Solid build with a clear user in mind. The interface is doing less than it could — a second pass on hierarchy would lift this considerably.
Discussion
0 comments
No comments yet.