What it is about
It is a method for an accounting professional to use an assistant with file access to prepare close reconciliations. It is more like putting an intern to work with a file system, clear instructions and a review cycle than chatting with a chatbot.
What it offers, according to the source
Stated by the post’s author: from 2–3 days of heavy, interrupted work to a little over an hour of review. The author insists that it is not an AI “doing the accounting” but an orderly environment with rules and a review cycle. Accounts such as the bad-debt provision needed several rounds of comments.
Stated figures. An identified person or organization states that they have used it. The results are stated by the source; we have not audited them.
What has really been tested
The author did it himself with the data from his March close; he does not publish the data or the account figures. The repository contains the process template and examples of instructions, not the real data, and it does not declare a formal license (it only invites using and adapting the template). We have not reproduced the flow.
How to follow it
Try first with a close that has already been reviewed and with one or two accounts, to compare the result with a person’s work. Remove client names and personal data from the folders before giving an AI assistant access and check your provider’s terms. Follow the steps below and do not post anything based on the assistant’s work without a person reviewing it.
- Create a working folder for the close (for example, MARCH_RECON) and give Claude access only to it. Inside, add subfolders for documentation, evidence, inputs, reports, scripts and the trial balance.
- Drop into the inputs folder the CSV, XML and PDF files you export from your programs. Rename only the files that are opaque.
- Write a short text file with what you want: review the documents and tie them to the trial balance, use a fixed tag (#TB:account:balance) so you can check them later with a script, create one file per account explaining how it was reconciled and keep a summary and a to-do list.
- Give that file to Claude and ask it to rewrite it and to ask you whatever questions it needs. Save the final version in the folder as claude.md.
- Tell it to start reconciling.
- Review the result as you would a junior accountant’s, ask for changes and have Claude document each new instruction for next time. Fix logic and edge cases and iterate.
What to keep in mind
- The method does not depend on a specific ERP: it starts from exports of the programs you use.
- The useful idea is the fixed tag so that a script can check that each reconciled balance matches the trial balance. It is a mechanical check that does not depend on the assistant being right.
- In the LinkedIn post, the accountant adds that the repository includes his instructions; we do not copy those texts and link to the original.
Sources
- LinkedIn — Tyler Whitlock, CPA, MBA: Reconciling Accounts with Claude Cowork (walkthrough) (opens in a new tab) (primary)
- GitHub — tylerwhitlock50/month_end_claude (folder structure and reconciliation instructions) (opens in a new tab)
We wrote this entry in our own words from the sources above and checked that the links worked on October 17, 2026. Is anything incorrect? Tell us.