Tallyproof Bank Statements

Both tools run the same downstream pipeline — reconcile to the cent, flag bad rows, suggest categories, and emit Excel/CSV/QuickBooks downloads — so the only real separator is input modality (attached file vs pasted text). The descriptions do state the boundary explicitly ('Do not use when a statement file is attached'), which rescues the pair, but an agent facing a mixed request (a file plus pasted rows) still has a genuine coin-flip.

Both names follow a clean snake_case verb_noun pattern (convert_bank_statement, summarize_transactions). Minor deviation: the verbs differ in emphasis (conversion vs summarization) for what is largely the same reconciliation output, and there is no shared domain prefix to visually group them.

Two tools is borderline thin; it is a defensible split by input type, but it leaves no room for adjacent operations like correcting a mis-parsed row or re-running without re-supplying input. Falls in the 'too few' band of 1-2 tools rather than a well-scoped 3-15 set.

The two entry paths (file and pasted text) plus reconciliation, categorization, and export cover the core workflow end to end. Notable gaps remain: no way to edit or fix extracted transactions after conversion, no multi-account or multi-statement handling, and no OCR path for scanned statements, which the descriptions acknowledge as a dead end.