Ashish · field notes
All notes
← back to the system map
BuildingFinance & Books2 min read

Docyt bookkeeping automation

I'm teaching Docyt to run as the portfolio's bookkeeper, with every payment gated behind my authorization.

Bookkeeping across a dozen entities (bill intake, categorization, month-end review) is a full seat. I run it on Docyt layered over QuickBooks, and I want an agent to do the repetitive parts of that seat without ever being able to move money on its own.

How it works

Bills arrive per entity at dedicated intake inboxes. The agent categorizes them, queues them, and works month-end review, driving Docyt through a logged-in browser session. Payments run on mailed checks and ACH. The chart of accounts lives in QuickBooks and Docyt mirrors it, so structural edits happen at the source and sync back. The whole thing is scoped so the agent categorizes, approves, and queues, and I authorize every payment send.

It is building. One entity is the pilot, a portfolio-wide chart-of-accounts standardization is well underway, and a human-in-the-loop pause/approve/resume layer (signed single-use tokens, a PreToolUse hook, a chat approval) is built and tested to gate the money and login steps.

This is the seat I am most careful with, because it is the one where a mistake spends real money. The bet is not "let the agent do the books." It is "let the agent do the books up to the exact line where a human has to decide," and make that line un-crossable in code.

Got an idea? Tell me →More field notes