Coming SoonWindows

Stop downloading invoices as Document.pdf.

Vendor portals and email attachments often save invoices as invoice.pdf, Invoice (1).pdf, or Document.pdf. 2cmd™ Ledger is Coming Soon: a local Windows workflow to suggest names from the page, with a preview before any rename.

Invoice downloads rarely keep useful names

A freelance month can produce twenty PDFs that look identical in Explorer. The vendor, invoice number, and date are on the page, but the filename is whatever the browser used.

Renaming by hand means opening each PDF. Letting a generic bulk-renamer run overnight risks mixing invoices with unrelated files in the same folder.

How Ledger would rename invoices

Point Ledger at the folder where invoices land. It would look for supported PDFs and images, not every file type on the disk.

When an invoice is recognized with enough confidence, Ledger would suggest a conservative filename and a folder such as Invoices—not a custom taxonomy you have to design first.

You would edit vendor names, drop rows you do not trust, and apply a journalled batch. Uncertain numbers and dates would not be fabricated to make a prettier name.

Local processing

Invoices can include account numbers, addresses, and line items. Processing is intended to stay on your Windows PC. v1 would not require sending those PDFs to 2cmd for conversion or naming.

Nothing changes until you approve it

Preview comes first. Apply is explicit. The design is to refuse silent overwrites of files that are already in the destination, and to undo the last completed transaction if the batch was a mistake.

What this is not

Ledger does not create invoices, send them, or post them to accounting software. Classification can be wrong; that is why review is mandatory. DOCX, XLSX, and email messages are outside the intended v1 file types.