Part 3 of 6 · The one-person finance team
How do you build for the future while rebuilding the past?
The old books couldn't be saved. Agents, a skill and one shared folder let me rebuild FY25 while building what came next. Whether I should have is another question.
In this part
- The FY25 books couldn't be saved. Accountants rebuilt them while Claude's agents gathered the contracts, invoices and payment evidence.
- One session's work became a reusable skill that improved with every correction.
- A shared folder, a daily index and saved skills let Claude run four workstreams at once. Someone still has to check the work.
New to the series? It follows one finance lead rebuilding a startup's finance function with Claude. Start with Part 1.
One month in, I'd scraped together a runway model (Part 1), set up Xero as the new general ledger (Part 2), onboarded a new corporate secretary, and built Q1's books from scratch. But our problems were just beginning.
Our FY25 annual report filing was due soon, and a quick look at the handover materials from the former corporate secretary revealed a major issue: the FY25 closing balances didn't match the bank statements.
Fearing the worst, I dove deeper and gradually felt my stomach sink:
- A deferred revenue balance and capitalized development costs carried forward unchanged from FY24,
- No revenue in accounts receivable, and
- Customer receipts unmatched to any invoice.
Incomplete, unreconcilable, and reported on a cash basis. We couldn't use it for the filing. Not without a full rebuild.
1. Claude-analyzed, human-verified
I brought in a new firm to work on rebuilding FY25 revenue on an accrual basis. While they inspected and verified revenue, contract by contract, a small group of Claude's agents set about a workflow:
- Scour the shared Google Drive for contracts.
- Draft a Slack message to the contract owner when a contract isn't a signed PDF.
- Gather every invoice tied to a contract into one folder with it.
- Add the contract to a contract list, linked to its folder.
- Build a helper sheet listing every invoice sent.
- Read the bank statements and confirm each invoice was paid.
When the accounting lead reached out for new contracts, I'd share a new batch the agents had compiled. When they had questions, I'd draft my own answer, ask Claude for its, and compare.
2. Accidental up-skill.md
At the end of June, the accountants came back with bad news. It would be faster, they said, to rebuild FY25 costs from scratch than to repurpose the old ledger. Its classifications were so unreliable that recoding them line by line would take longer than starting over.
I went back to the sessions where I'd consolidated and classified bank transactions (Part 1) and asked:
"Hey Claude, review the entire session, the inputs and the attached latest version of the output. Turn it into a skill. Every time we run the skill and I give you feedback, update the skill."
Then, in a new session, Claude transcribed the OCBC statements and combined them with Wise exports a subagent had cleaned. The skill brought back the chart of accounts and the team tags, suggested a classification for each line, and applied it wherever a transaction cleanly fit the rules I'd set.
After a few rounds of feedback for the edge cases, the accountants verified the worksheet before posting the journal entries.
3. How Claude became my project manager
Over those two months, I'd gradually refined how I used Claude until it did the work of an analyst, an associate, and a project manager concurrently. I was limited only by my own ability to multitask and instruct.
The trick was the setup. I made one folder the working repo for the whole finance function: source files, workbooks, notes, and an always up-to-date index at the top saying what everything is and where it lives.
Google Drive became the home for outputs, the deliverables other people open.
Each workstream got its own Claude thread, and sometimes a cluster of threads. Whatever one thread learned was indexed in the repo, where every other thread could read it but not change it.
Three habits turned Claude from an assistant into a project manager:
- Indexing, scheduled, daily. Each day Claude re-read what had changed and updated the index.
- Folder cleanup, scheduled, daily. Superseded files went to an archive and live files followed a naming convention.
- A skills repo, with every repeated method saved. Any thread's work could become a method, and each correction improved it.
By the end of July, FY25 was in Xero, and it tied to FY24's closing balances on one side and FY26's opening balances on the other.
Cake ain't a piece of payroll
Claude was in a hurry. In one early draft, it guessed that any payee who sounded like a person might be on payroll. A hotel in Bangkok and a cake shop briefly joined the team, until the review sent them back to travel and meals. Lovely staff, presumably. Not ours.
When I asked how it had labeled everyone else, Claude came clean: it hadn't. It had gotten lazy and skipped 85 rows.
Both fixes went into skills: the HR system is payroll's source of truth, and anything unlabeled goes to a human (me).
What I'd do differently
Hire a controller as soon as I could. The books balanced, and balancing proves they're complete. It doesn't prove every line landed in the right account. With four streams running, I was the only second pair of eyes, and a controller alongside me would have been the check I didn't have time to be.
Takeaway: Just because Claude lets you run parallel workstreams doesn't mean you should.
The past was fixed. The present wasn't slowing down: every month brought more transactions than the last.