Accounting firm
Find the missing document before the client goes looking for it
Chasing missing documents takes longer than the review itself. Every associate has their own method, and what the client agreed to provide — and by when — is written nowhere.
Create my first projectYou describe your work
Nothing to configure. The blueprint derives the agents, their speciality and the folders they need — and submits the lot before writing anything.
"We keep the books for small businesses. Before the review, I want to know which documents are missing on each file, and be able to tell the client in one sentence."
- Reconciler/statements
Matches bank movements against the documents provided
- Document checker/invoices
Spots missing or unreadable supporting documents
- Engagement keeper/engagements
Recalls what each client committed to provide
The workspace takes shape
What you upload and what has to be written together, kept apart. The folders carry the words of your trade — never /documents.
The folders are created in your drive. You put your documents in them.
- /statements/<client>12 files
Bank statements, one folder per client
- /invoices/<client>148 files
Supporting documents received, purchases and sales
- /filingsempty
Closed-year filings, for comparison
These documents do not exist yet. The assistant asks you questions and writes them.
- /engagements/scope.mdwritten
What each client provides, and by when
- /engagements/thresholds.mdto write
The thresholds above which a document is required
You ask, the team works
Every step is visible while it runs: the file read, the specialist consulted. The answer cites the paths it relies on.
Which documents are missing on the Fournel file to close the quarter?
- read_filereads /statements/fournel/q3.csv
- ask_agentconsults the reconciler
- read_filereads /engagements/scope.md
- ask_agentconsults the document checker
Where the AI stops and asks
These checkpoints are written into workflow.md, in plain text. Between two of them the AI works alone; it does not cross one. You decide where they fall.
- Before any chase is sent to the client: it is the firm speaking, not the tool.
- Before classifying a movement as impossible to justify.
- Before changing a threshold, which applies to every file.
The project remembers
Your decisions carry from one conversation to the next — and you can read them, correct them, erase them. A memory you cannot contradict is not one.
Re-read on every request. Correct what is wrong, erase what no longer serves.
## Decisions - Client Fournel provides documents on the 10th of the month, not the 5th. - Expense claims under €25 are not chased individually. - Internal transfers between the two accounts are not movements to justify. ## Preferences - One grouped chase list per client, never document by document.
Frequently asked questions
- Does Ts-Agents replace my accounting software?
- No, and it never substitutes for it. It works on the documents — statements, supporting files, engagement terms — to prepare and de-risk what you enter afterwards. Entry, filing production and electronic submission stay with your software vendor.
- Are my clients’ documents sent anywhere?
- They stay in your drive. Our database stores technical indexes only, never the content of your documents or your conversations. The extracts needed to answer a question go to the model provider you chose, on your own key.
- Can we have one project per client?
- Yes, and it is often the right split: each client has its own engagement terms, thresholds and memory. You open as many projects as you like — the subscription applies to a project, not to your account — and the same colleague can be invited to several of them without any control over billing.
Faithful reconstructions of the interface, built with the product's real components and colours. These are not screen photographs.
Other trades
Describe your work. See what we make of it.
The blueprint shows you the proposed organisation before writing anything to your drive. Judge it on the evidence.
Create my first project