← All notes
November 21, 2026Engineering Leadership6 min read

Why AI-Drafted Accounting Entries Need an Immutable Ledger

On 18 November 2026, OpenAI launched an Accounting plugin for ChatGPT. It runs in the ChatGPT desktop app for Business and Enterprise workspaces. What I noticed first was not the partner list. It was the review step: the plugin prepares draft entries, and a person still has to approve them.

That is the right default. I have been building an open-source budget app around a similar idea, just from the other side of the stack. The model can draft. The ledger has to stay honest.

What the plugin actually does

OpenAI’s own documentation is fairly plain about this. The plugin is meant to help with recurring work such as reconciling transactions, drafting invoice entries, and preparing month-end reports from your records and templates. You install it from the plugin directory in the desktop app on macOS or Windows. ChatGPT Business members can install it themselves. In an Enterprise workspace, an admin has to approve it first. The 18 November date is in the ChatGPT release notes.

The partner connections listed in that help article are BILL, Campfire, FreshBooks, Oracle NetSuite, Oracle QuickStart, QuickBooks Online, Rillet, and Xero. Where an app has no plugin, OpenAI says ChatGPT can still operate it on screen through computer use.

I am not going to pretend every connection can write to the books. OpenAI says a connection that lets you read transactions may have different permissions for entering records, and tells you to check each listing. Some partners are read-only. Others can create entries, still within the signed-in user’s permissions, and still with a review step. The official product page says you review the supporting records, calculations, and suggested coding before approving an entry or a report.

I have not used the plugin myself, so this is based on OpenAI’s documentation, not a hands-on review.

Why this interested me

I manage engineering work, and I also write software. A lot of the AI tools I see are good at a first draft. The usual failure is not an empty draft. It is a draft that looks finished, gets written into a system that can be edited in place, and later nobody can tell what changed.

Money makes that worse. If a balance can be overwritten, you do not have a history. You have the latest version of a number. That is fine for a note. It is not fine for a ledger.

This is why I built Open Budget Tracker the way I did. I wrote up the design earlier this year. The short version is that money is stored as events, and balances are derived.

How the ledger is designed

Open Budget Tracker is an open-source, self-hostable budget app for personal and household use. The source is on GitHub under the MIT license. It runs on Postgres and Supabase. The interface is bilingual in English and Arabic, including a right-to-left layout, and wallets are in two currencies, USD and LBP.

The financial core is an append-only journal. Each change to money is an immutable typed event. A wallet balance is never edited in place. If a record was wrong, you do not change the old row. You post a new, linked correction. The old event stays, the correction points at it, and any balance can be reconstructed from the journal.

That sounds strict, and it is meant to be. Reversals are explicit. Two reports cannot quietly disagree because one feature kept its own running total. A draft also stays a draft until it is posted through the same boundary as every other money change.

Planning targets stay separate from posted money, so a target never changes a balance. I already covered the loan subledger, the USD-to-LBP exchange command, and the retry behaviour in the earlier post, so I will not repeat that here.

The part that matters for AI is simpler. If a model proposes an entry, you need a safe place to put that proposal, a person who can accept or reject it, and a ledger that will not forget the decision.

Drafting is useful. Editing history is not

I think the shape of what OpenAI shipped is sound. A plugin that drafts a month-end report or a suggested invoice entry can take over a lot of mechanical work. Flagging missing information or uncertain coding is useful too. None of that means the model should become the system of record.

The trust sits in two places.

The first is the human approval step. OpenAI is explicit about this, and that should stay explicit. A suggested account code is a suggestion. If the review step turns into a habit of clicking through, the draft might as well have been posted automatically.

The second is the ledger the approved entry lands in. If that ledger lets you edit an old row, an approved AI entry and a later manual fix can erase each other from view. You are left with a number and no reliable story of how you got there. If the ledger is append-only, you can still see the original posting and any correction that followed.

I built Open Budget Tracker for personal and household budgets, not as a replacement for QuickBooks or NetSuite. A household ledger and an enterprise close are not the same problem. The same rule still applies in both places. AI can help prepare the work. The books still need to be immutable and auditable.

What I would want stored with the draft

If you connect a model to a ledger, I would want the proposal itself stored, not only the final posting. Which invoice it came from, which account it suggested, who approved it, and whether a later correction was needed. That is ordinary audit design. It is also the only way to tell, later, whether the drafting step is actually helping or quietly creating cleanup work.

I would also want write access to stay narrower than read access, which some of the partner plugins already do. Reading a transaction and creating one are different decisions, and they should stay that way.

Open Budget Tracker does not have a ChatGPT plugin, and I am not announcing one. It is a small open-source app with an immutable journal, derived balances, linked corrections, two currencies, and a bilingual interface. For the design details, or to run it yourself, start with the earlier post and the repository.

The Accounting plugin is a useful reminder that this design is not a niche preference. Once a model can draft financial entries, the ledger underneath is no longer an implementation detail. It is what makes the draft safe to use.

Join the conversation

Your email address will not be published.