Delegate admin to AI safely: reviews, approvals, permissions

Delegate the preparing, keep the deciding. AI can sort, draft and check on its own; anything that leaves your business, moves money or becomes a record waits for your OK. Set the rights per person and per AI, review drafts against a short checklist, and fix mistakes with a cancellation, never by editing what you issued.

Which admin steps can you delegate fully, and which need your OK?

Sort every task by what a mistake costs and whether it can be undone. As of 08/10/2026 we suggest these lanes. They are our advice; the law doesn't set them.

Move a task to a lighter lane only after you have approved the same kind of draft many times without a change. The harder a step is to undo, the longer it stays with you.

What does a good review look like?

A good review takes under a minute and checks five things. Ask the AI to show them up front.

1. Who: the right client, the right address.
2. What: the lines match the work. Compare to your hours or your quote.
3. How much: amounts, VAT rate and totals. If the AI calculated, check the sum yourself.
4. When: dates, due date, service period.
5. What was guessed: ask "list every assumption". A guess is where mistakes hide.

Keep drafts and sending as separate steps, so nothing goes out by accident. And keep a log: who or what created or changed a record, and when. You'll only need it on the day something looks wrong. For a team, add a second pair of eyes on larger amounts. Art. 22 GDPR also limits decisions made only by automated means that have a legal or similarly significant effect on a person, so keep a person in the loop for anything that affects staff or consumers (general information).

How do you set permissions for people and AI?

Give the AI the rights of the person it works for, and nothing extra.

• By person: an owner sees everything; a member sees their own time and uploads; a bookkeeper works on the books. An AI acting for a member should not suddenly see invoices.
• By action: reading and drafting is open; sending and deleting ask first, and bank details are changed only by you.
• By tool: connect only the AI tools you use. Each connector can be revoked.

Check the setup in your AI app too. As of 08/10/2026, ChatGPT and Claude can both ask before a connected app acts, and on business plans an admin can limit what each connector may do. Settings differ by plan and change often, so the vendor's help page wins.

What happens when the AI is wrong?

Fix it like your own mistake. What counts is whether the record is already final.

• Before issuing: it is a draft. Edit it, or throw it away.
• After issuing: it stays as it is. In Germany the GoBD require that a record is not changed so that its original content is hidden (GoBD Rz. 58, § 146 Abs. 4 AO). In Austria § 131 Abs. 1 Z 6 lit. b BAO says the same for electronic records.
• The fix: a cancellation document with negative amounts and a reference to the original, then a new invoice. Small slips in details can be corrected with a document that refers to the original. Details: Cancelling or correcting a sent invoice.
• If VAT was shown too high: you owe it until you correct it (§ 14c UStG in Germany, § 11 Abs. 12 UStG 1994 in Austria).

The tax office doesn't care whether you or the AI made the error. You are responsible for the invoice, so the approval step is yours.

What does an AI-native back office feel like day to day?

You open one place and the work is already prepared. The week's hours are logged from a sentence, the invoice is drafted, the overdue client has a reminder waiting, a missing receipt is already flagged. You read, change a line, press approve. Then you get on with your actual work.

You decide everything that matters and rarely start from a blank page. Start with one routine, review it for a few weeks, then widen the lane.