Claude to post scanned receipts into Ledger
Erik Craddock built a local accounting routine around a ScanSnap iX1300 and Claude Code. Physical paperwork from the family inbox was scanned into PDFs, while email documents could be printed to PDF into the same inbox. A custom slash command then processed receipts, invoices and checks into organized files and Ledger accounting entries.
Original prompt
Shared by the source author. See source notes for context.
/process-inbox
Reach people exploring AI agents
See placements →What happened
The scanned inbox became filed documents and corresponding Ledger entries, with occasional manual accounting corrections.
Reported by Erik CraddockHow the agent did it
- Scan physical paperwork or save email documents as PDFs into the inbox.
- Run the custom process-inbox command with accounting reference files.
- Review Ledger balances and correct categories or clearing statuses.
Where a person stepped in
Craddock manually corrected occasional category and clearing-status errors and checked balances.
Erik Craddock built a local accounting routine around a ScanSnap iX1300 and Claude Code. Physical paperwork from the family inbox was scanned into PDFs, while email documents could be printed to PDF into the same inbox. A custom slash command then processed receipts, invoices and checks into organized files and Ledger accounting entries.
The agent read the documents, renamed them, filed them in the appropriate folders, and used reference information about payees, accounts and categories. It could create an entry or update a matching one, connecting the source document with the accounting record. This was a document-to-ledger workflow, rather than only a folder cleanup or a summary of spending.
Craddock also describes the parts that still require attention. Claude sometimes assigns the wrong category or clearing status. He corrects those mistakes manually and checks the resulting balances rather than treating a processed inbox as proof that the accounts are right.
The command's published technical artifact explains its matching and pending-entry behavior. That artifact is useful for understanding the reusable workflow, although its current contents should not be assumed to be identical to the command on the article's original publication date. The reported result is a functioning daily paperwork routine with accounting review still attached.
Prompt
Original prompt
Source: erikvancraddock.com · Erik Craddock
Frequently asked questions
What inputs went into the same inbox?
Scanned physical receipts, invoices and checks, plus email documents saved through Print to PDF.
What errors did the author still correct?
Occasionally the category or cleared status was wrong; he corrected entries and checked balances.
Does the linked command prove the original version?
It documents the reusable command now. The article supplies the dated firsthand account; the current artifact may have changed.
More details
About this account
Claude read PDFs, organized source files and created or updated Ledger transactions through a custom command.
Firsthand source opened and read. Prompt is a verbatim excerpt of the published original instruction.
Credit: Erik Craddock
Source published 17 Aug 2025
Source checked 14 Oct 2026
Tools and topics
Claude Code · ScanSnap iX1300 · Ledger · PDF inbox
Ledger accounting · Receipt inbox · Pending transactions
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.