A bank statement converter built by a CPA, for the people who do the books.

Every practice has the same month-end: a stack of PDFs, a ledger waiting for them, and a converter somewhere in between. The converters all did the same thing. They read the PDF, handed back a spreadsheet, and left the checking to whoever opened it next.

That checking is not a small job. A balance carried forward can be read as a transaction. A description that wraps onto a second line can arrive as two rows or as none. Nothing about the output looks wrong, so it goes into the ledger, and the problem surfaces weeks later as a reconciliation that won't close by an amount nobody can place.

The statement already contains the answer. It prints a running balance next to the transactions, which means every row can be checked against the document it came from. That check is what BankWriter was built around: convert the statement, then prove the conversion against the statement itself, and flag the rows that don't agree before anyone imports anything.

The second decision was where the work happens. Client bank statements are among the most sensitive documents a practice handles, and the simplest way to keep them safe is to never move them. BankWriter runs on the machine in front of you. There is no upload, because there is nowhere to upload to.