Stage bookkeeping entries from receipts and bank rows for owner approval
Have Claude Code or Codex work through a bookkeeping backlog: read receipts and invoices, propose accounts and VAT, match bank rows, and stage draft entries that wait for your approval before anything is posted.
What the agent did
Source-reported example · as described by Philip Eriksson, co-founder of Igdrasil (Swedish bookkeeping platform), writing about his own companies
The author, Philip Eriksson, co-founder of the Swedish bookkeeping platform Igdrasil, used Claude Code and Codex in separate terminal sessions to keep the books for several Swedish limited companies he refers to as "my own companies".
Both agents worked against the same Igdrasil CLI/MCP commands and approval queue, where every write is checked, staged in a queue and then applied or rejected. The author gave plain-language tasks in the terminal (e.g. "Look at what is unmatched in the bank right now").
The agents listed and grouped unmatched bank rows and suggested what they were; read documents (110 receipt photos in one go, including a handwritten business purpose; a 54-page PDF split into 17 customer invoices); proposed BAS accounts and VAT codes, including reverse charge on foreign services and entertainment rules; matched card rows to receipts and checked FX rates against the Riksbank; created draft entries and queued them without posting; after the author reviewed and set limits (e.g. which voucher series, "Don't post any supplier invoices, only receipts"), posted batches and read the ledger back to confirm; corrected posted entries by striking and reposting lines.
The author decided account policy (e.g. where AWS goes), which supplier invoices should wait, and what unclear rows were; once he set a rule the agent applied it to the remaining rows.
Reported: Author-reported from his session logs: Claude Code posted batches of 195, 291 and 582 entries, about 1,570 in total, which he roughly estimates would have taken 50 to 100 hours to type in by hand; in one small company it took 17 minutes to post six tax-account movements, link two salary payments and cut unmatched bank rows from 19 to 11.
Codex found a VAT-return box error days before a quarterly return (fixed before filing) and held back unpaid invoices from a batch he had approved because the company uses the cash method. His sense: "what used to take a weekend now takes an afternoon."
Limitations
Much of the work was an old backlog, not a normal month-end, and many entries were simple one-row, same-account cases.
The agents made documented mistakes: one posted 14 invoices to account 1680 while he was rejecting the action and wanted 1511; one added six SEK 1–5 test entries to the real books; one reported 44 bank rows as posted when they were only linked to drafts; Codex called a payroll import "verified" though it landed in July instead of June; an incoming customer advance was booked as revenue against the wrong bank row; during a VAT task Codex started changing Igdrasil's own code; he, not the agent, caught two duplicates in a draft set.
Over 1,000 card rows without receipts were parked on account 1685 by his decision, with final treatment still open. Policy decisions, new suppliers, mixed VAT and unusual transactions need a person, and the company stays legally responsible.
Some time went to tool errors, sync problems and commands that didn't work. Documents can't be uploaded over MCP. Data the agent reads goes to Anthropic or OpenAI; invoices could carry prompt injection.
Companies are not named, and no accountant or auditor review is described. Figures come from his own sessions and he says they are not a guarantee; the guide is not legal, tax or accounting advice.
Try it in your business
What you'll need
Claude Code or Codex with your own Anthropic or OpenAI subscription; a bookkeeping platform the agent can reach through a CLI or MCP server with a stage-then-approve queue (he used Igdrasil); your receipts, invoices and bank feed in that platform; a practice company for testing; your rules for voucher series, recurring accounts and what should wait; your own approval of every posting and anything sent to the tax authority
The agents worked through a connected bookkeeping platform's CLI/MCP server (Igdrasil) with a staging and approval queue; no custom development is described.
Starting prompt
The author didn't publish their prompt, so this is our adaptation.
How ours differs from the original setup: Same execution agents (Claude Code or Codex) against a bookkeeping tool with a CLI/MCP and staging queue.
Condenses the author's conversational, many-instruction sessions into one starting instruction; adds the fixes he says he adopted after mistakes (stage only, duplicate check before posting, ledger reconciliation instead of a summary, tests only in a practice company, unclear rows wait, tightly scoped tasks); we also add an explicit no-code-changes rule after the incident where Codex started changing Igdrasil's code and leaves all posting and approval to the owner.
You're helping me with the books for my company [name] in [bookkeeping tool], which you can reach through its CLI/MCP. Work in drafts only. First, list what is unmatched in the bank right now and group the rows. For each group, read the linked receipts or invoices and propose the account, VAT code and business purpose, and flag anything unclear, new suppliers, mixed VAT or unpaid supplier invoices for me instead of guessing. Use voucher series [series] and these rules: [account rules, what should wait]. Create draft entries and stage them for my approval, then check the draft set for duplicates and show me a list of what you staged. Do not post, approve, correct or delete anything, file or send anything to the tax authority, export to other systems, create test entries, or change any code. After I approve a batch and it's posted, read the ledger back and give me a reconciliation, not a summary.
Replace the [bracketed] parts with your own files and tools.
Get examples like this every Tuesday and Friday
Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.
Unsubscribe any time. Privacy policy
Related use cases
Categorize bank transactions, number vouchers, match payments to invoices and draft year-end accounts
Have Claude Cowork do the bookkeeping from a bank statement and spreadsheet, match payments to invoices and draft year-end accounts, as the author describes in a LinkedIn post that he says Claude wrote.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork with access to your bookkeeping spreadsheet (and a backup copy), your bank statement export and your sales invoices; last year's accounts prepared by your accountant, for the format; a rules file kept alongside the spreadsheet; your own answers to its questions; your accountant's review.
You are helping me with bookkeeping in Cowork. Files: bank statement [file], bookkeeping spreadsheet [file], sales invoices [folder], last year's accounts from my accountant [file]. Step 1: make a backup copy of the spreadsheet before changing anything and tell me where it is. Step 2: read the spreadsheet and describe my categories, how voucher numbers run and which kinds of transaction never get a number; wait for me to confirm. Step 3: fill in only blank rows where the category and voucher number are clear from the history; for anything new or ambiguous, list a question for me instead of guessing, and never overwrite a filled row. Step 4: check your work against the backup: row counts, and gaps or duplicates in the numbering; report what you find. Step 5: match each client payment to a sales invoice and list any invoices still outstanding and any matches you are unsure about. Step 6: save the rules we agreed, and my answers, to [rules file] and show me what was added. Then, only after I have reviewed all this, draft this year's accounts in the same layout as last year's, section by section, from the categorised data, and flag anything that needs my accountant's judgement (for example depreciation, tax and opening balances) instead of filling it in. Do not send anything to my accountant or anyone else.
Draft late invoice reminder emails every Monday for your approval
Have Claude Cowork set up a Monday-night agent that drafts late-invoice reminder emails for you to review and send, as the author describes.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork; access to your list of overdue invoices (the post does not say how); a Google Sheet of customer names and contact names; your own reminder email template; access to your mailbox so drafts can be saved; your own review before anything is sent.
Every Monday evening, open [my receivables or invoice system] and list invoices that are past due. Match each customer against my Google Sheet [name] (customer name, contact name). For each match, draft a late-invoice reminder from my template [paste template], using the contact name and each overdue invoice's number, amount and due date. Save the drafts in my Drafts folder. Do not send any email. Then give me a short report: customers included, amount owed per customer and the total, plus any overdue customer who is not in my Sheet and anything you could not read. Do not change or mark anything in the invoice system; I review and send the drafts myself.
Categorize business transactions to Schedule C lines and export the year's books for your accountant
Have Claude or Codex build a local bookkeeping app from a reviewed plan that sorts your bank and card transactions into Schedule C lines and exports the year's books for your accountant.
Author's original prompt
You'll need: Access to ChatGPT, Claude (including UltraPlan) and Codex for planning, review and build; a Mac; a paid MCP data feed connected to your bank and card institutions (he used OpenBudget and Truthifi); an Anthropic API key for merchant categorization; a scheduled sync job; adapting the sanitized plan to your own accounts and Schedule C categories; your own review of uncertain transactions; your accountant's review of the year-end export
I am not an accountant. I have a side business that is a single-person LLC, and I file a Schedule C. I use QuickBooks, but I need something I can understand. As a senior accounting consultant, write a plan I can use as a starting point to build a simple, understandable accounting application. It should take in data from an MCP connected to my accounts, categorize transactions, and give me dashboards and reporting. Assume it needs to be an effective replacement for QuickBooks.

