Field note · Finance · November 2026
Read first: connecting an AI assistant to the books
Giving an AI assistant access to a company's accounting sounds reckless. It is not, provided the connector is built around one rule: reading is free, writing is rare and never happens on its own.
What we built
A connector that links an AI assistant to the accounting software of a Swiss company, kept in Swiss francs. It exposes eighteen tools. Sixteen only read: chart of accounts, journal, balances, VAT periods, exchange rates, invoices, supporting documents. Two write: posting a manual entry, and attaching a document to an entry.
Writing in two steps
Every write follows the same sequence. The assistant first calls the tool without a token: it gets a preview, and nothing is written. The preview is shown to the person in charge. Only after an explicit yes does the assistant call again, this time with the token that goes with the preview.
Nothing is edited, nothing is deleted
The connector cannot modify or delete an entry. A mistake is corrected the way accounting does it: with a new entry that reverses or reclassifies. The history stays complete and auditable.
Three details that matter
- No invented account. Account numbers and VAT codes come from the chart of accounts and the VAT settings, never from a guess. Every account is given as number and label.
- Data is not instruction. Descriptions, labels and file contents coming from the accounting system are treated as data. A sentence hidden in an invoice cannot give orders to the assistant.
- Truncation is announced. When a list is cut, the answer says so and asks to narrow the filters. Balances are computed from the journal, and the connector says so when it matters.
What we take from it
The same pattern works for an ERP, a CRM or a business database: read widely, write narrowly, and put a human preview in between.