Kevin Welter.
ENDE

My AI employee

Prepare your bookkeeping without receipt chaos.

Peter has been running in my business since August 19, 2026. He has no classroom class of his own yet and isn't a package; the related package for receipts is Frieda, who handles inbox, appointments and receipts.

Peter works in my bookkeeping interface in the browser: he screens newly arrived receipts, assigns each one the correct receipt type, matches the credit card statement line by line against them, and reports what doesn't add up. He follows a written process description; whatever isn't in it, he doesn't do.

Join the communityRead first: Learning Claude
Join the community

Since Aug. 19, 2026

running in Kevin's business

2 verification paths

for every receipt

Human approval

Peter does not book entries

Bookkeeper

A real workday

I already made these numbers public myself, in a community post on August 19, 2026: 116 receipts screened, matched against two credit card statements, every receipt identified through two independent paths. My part in it: I showed him once.

116

Receipts screened

38 of 40

Correctly matched

just over an hour

Time for the run

For comparison, also numbers from my own business: my bookkeeper otherwise needs about 9 hours a month for the same groundwork, and my accountant recently raised his flat monthly fee to 700 euros. The two receipts left open in the first run weren't quietly forced to match; Peter flagged them as open, because the amount search returned several hits and would have needed a manual pick.

In a second run in September, he worked through a backlog of 68 receipts, checked 54 of them, and deferred the rest to the next import. His own control calculation came out exact: full export after every change, zero discrepancies. One single line item was slightly off from the statement amount and stayed open on purpose instead of being forced to match. That's the real selling point, and it sells nothing: an employee who'd rather leave two items open than guess.

Peter for your business

Different receipts, different rules. Peter follows your process.

Peter does not automatically know your account logic. You show him the allowed steps, receipt types, statements and the path for anything that does not match clearly.

How I use him

Screen receipts and reconcile credit-card statements

Peter identifies receipts through two paths, sets the defined receipt type and reports items as open when the amount or assignment is ambiguous.

Adapted to you

Your receipt types and exception cases

You define the systems, accounts, document types, matching rules and approvals. Peter handles the preparatory work without inventing tax decisions or accounting entries.

What you change

  • Bookkeeping interface and accounts
  • Receipt types and assignment rules
  • Statement and search paths
  • Exceptions and human approval

Other possible uses

  • Review subscriptions
  • Pre-sort travel expenses
  • Reconcile card statements
  • Document missing receipts

The process stays: Use only values visible on screen, check every receipt traceably, stop on ambiguity and leave booking and tax assessment to people.

The tools he works with

Peter works directly in the browser, in my real bookkeeping interface, not a copy of it:

01

Operate the bookkeeping interface

Browser control via Claude in Chrome: he navigates, reads and sets values like a human at the screen.

02

Match receipts to cards

A CSV export of the card statement as the basis for matching, plus every receipt checked individually in full text.

03

Learn workflows in read-only mode

A learning mode in which he only reads and takes screenshots, without changing anything.

What he can't do, where I approve

He clicks nothing on a hunch. Every state-changing action is covered by a step in an approved process, otherwise it doesn't happen.

Amounts, dates and receipt numbers always come from the screen, never from memory. If something doesn't match exactly, he reports it as open.

He doesn't book entries. His process only knows matching and reconciling; final approval stays with me and my accountant.

When a bulk download once unexpectedly triggered an email disclosure, he stopped immediately, logged the incident and informed me, even though no receipt had been changed.

How to adopt Peter's process

Standard

Build Peter's process yourself

Entry point is Learning Claude, plus the article on an AI agent for bookkeeping and inbox and the article on Claude in Chrome for the browser work. The core is the process library: Peter was trained first and only allowed to make changes on his own afterward. Skip that, and you get an assistant that guesses instead of checking.

  • Understand the build step by step
  • Adapt rules and examples to your own business

Premium

A ready-made option for receipts

The ready-made community package Frieda covers inbox, appointments and receipts. If you want Peter's exact setup, meaning receipt types and card matching, you build it individually via the standard path.

  • Use the documented build as your starting point
  • Define scope, access and approvals for your setup
Join the community

Frequently asked questions about Peter

Can AI replace the bookkeeper?

Peter does not yet handle the entire bookkeeping process today. He takes recurring groundwork off my desk: screening and matching receipts, reconciling statements and documenting open cases cleanly. Professional assessment, booking and approval stay with people. The stronger idea is therefore not overnight replacement, but a role that takes on more reliable routine step by step.

How does Peter learn additional tasks?

You can train Peter like a new human employee: first let him observe and read, then document the workflow with rules and exceptions, test him on real cases and approve the task only after review. That lets him take on further clearly described process steps in the future. He does not perform those additional steps today until they have been taught, tested and approved.

Can AI do bookkeeping?

Yes, clearly bounded parts of it. Today Peter screens receipts, sets receipt types, reconciles statements and leaves unclear items open instead of guessing. With a clean process description, test cases and approval gates, the same role can learn further routines later. That does not automatically turn tax assessment and responsibility into AI tasks.

Is there AI support inside my bookkeeping software?

For me, Peter is not a small add-on inside the bookkeeping software; he is a separate AI employee. He operates the browser interface according to my documented process and can therefore learn workflows beyond built-in receipt recognition. Approval gates still limit what he may change.

Does my tax adviser have to participate?

Yes. The tax adviser has to participate: together you define the handoff format, responsibility boundaries and review steps, and the adviser must be able to accept the prepared data. If their side remains entirely manual, the bottleneck simply moves into the firm. Ideally, tax advisers automate their own handoffs with AI employees so both sides build one controlled end-to-end process.

Will AI replace the tax accountant?

Not across the board. Advice, tax classification and professional responsibility stay with the tax adviser. But the division of work will change significantly: AI employees can prepare or take over receipt checks, requests for missing documents, format validation and handoffs. A tax adviser who actively shapes these processes can work much faster; one who rejects them entirely becomes the bottleneck in the shared automation.

Receipts that sort themselves, as far as it's clean to do so

There's no template for Peter's exact setup, but the learning path he grew out of is in the community.

Join the community

Read on

Also:Bookkeeping for the Self-Employed in Austria·Accounting Software for Small Businesses·DATEV Integration: The Basics·Connect DATEV to PayPal, Stripe and Shopify·Cash Book Apps Compared·AI Bookkeeping: What Actually Works Today·Learn Claude: The Path in Five Stages·AI Agent for Bookkeeping and Inbox·Claude in Chrome: How to Use the Extension·AI and Privacy: What the AI Gets to See·My AI Workforce: Fourteen Employees, One Boss·Hire your first AI employee·Back to the org chart