Coming SoonWindows

File bank statements without opening every PDF.

Monthly statements often arrive as eStmt.pdf or download (3).pdf. 2cmd™ Ledger is Coming Soon: read supported statement PDFs locally, suggest a clear name and folder, and wait for your confirmation.

Statements mix with everything else you downloaded

Bank and card statements share a Downloads folder with manuals, tickets, and invoices. The institution and period are on page one; the filename rarely is.

People keep statements for records, disputes, and tax prep. They need the PDF intact, stored where they will look next year—not ingested into a cloud bookkeeping product.

How Ledger would organize statements

Select the folder that contains statement PDFs. Ledger would discover supported files and skip types it does not handle.

For a supported bank statement it can read, it would suggest a filename and a Bank Statements destination when confidence is high enough. Account digits would not be invented to pad a name.

You would review the batch, keep the original PDF, and apply only what you accept. The last applied transaction is intended to be undoable.

Local processing

Statements are among the most sensitive household files. Ledger is designed as local-first: v1 would not require uploading them. A future paid licence is intended to check entitlement without sending document content.

Nothing changes until you approve it

No rename or move would run until you confirm the preview. Collision handling is meant to protect files that already exist at the destination.

What this is not

Ledger is not a bank feed, reconciliation tool, or accounting system. It does not connect to banks. If a statement is a scan or an unusual layout, fields may be omitted rather than guessed.