I had an AI build an open-source Stripe accounting tool. Here is what happened after 810 tests.

I wanted to know whether an AI coding agent could build something real instead of a demo, so I gave it Stripe accounting. The money has to add up, and every entry needs a reason.

The result is Ledgerly, an open-source TypeScript library with an optional self-hosted receiver. It turns Stripe events into balanced double-entry books you can send to QuickBooks or Xero. I made the accounting and release calls. The agent wrote the code, tests, docs, and build work.

You can try the mapping in about ten seconds without installing anything:

cat event.json | npx ledgerly

It reads a Stripe event and shows the balanced entry. It can also make the right QuickBooks or Xero text. There are 57 sample events in the project if you do not have one.

Where it is now:

- It handles 18 kinds of Stripe events.

- Annual payments are spread across the right months.

- Paid plan changes keep past months and rebuild only the months left.

- Cancellations stop later revenue after the real last service day.

It also keeps sales tax, customer credits, business bills, and currency gains or losses separate.

There are 810 tests, 57 sample events, a public package, and a ready-to-run image.

A safety check found a one-cent error when one payment had several refunds in another currency. Failed refunds could also change the later math. Both problems were fixed before release.

The most useful feedback now is about the money rules. Which Stripe case would you want this to handle before you trusted it?

https://github.com/jakethehoffer/ledgerly