An AI that reads your client's actual books.
Not a chat window bolted onto a ledger. TAI learns a specific client from their own data and works inside the same rules as everyone else. It proposes, and people approve.
TAI · week of 16 March 2026
Reading the feed1,184
Posted
on this client's own history
47
In your queue
coded, reasoning attached
9
Routed to Ops
receipt, PO or W-9 missing
0
Uncategorised
and none in suspense
14 Mar · AWS EMEA SARL · INV 8F2K1QP
Posted. Matches 11 prior payments, split 68 / 32 across Production and R&D on the standing cost-allocation rule.
13 Mar · RAMP CARD SETTLEMENT · 41 items
Cleared against 41 receipts. 2 missing, chased J. Okafor and M. Silva, due 20 Mar.
12 Mar · WIRE · HEIDRICK & STRUGGLES
Matched to PO-1188. Contract is three instalments, with the remaining 84,000.00 accrued to 2100.
11 Mar · STRIPE TRANSFER · ST-99204471
Split three ways: 60,903.88 to 4000 Revenue, 2,004.26 to 6510 Processing fees, 1,000.00 to 2400 Refund reserve.
09 Mar · CHK 2214 · NW HOLDINGS LLC
First payment to this payee. Posted on the pattern from two prior contractors, W-9 requested, 1099-NEC flag set. In your queue to confirm or recode.
07 Mar · DEP · LANDLORD REFUND
Reversed the 2024 deposit. Lease ends 30 Jun, so the ROU asset and liability are remeasured, ASC 842 rollforward updated.
Already drafted, for dates that have not arrived
6 drafted aheadMonth-end close · 14 of 22 items pre-run
6 journal entries drafted: 9,750.00 rent accrual, 1,250.00 prepaid insurance, 6,133.00 depreciation across 14 assets, 22,910.00 deferred revenue release.
Accounting · D. Okonjo to review
Rent escalation +3.5%
Lease clause 6(b). ASC 842 remeasurement drafted: ROU asset +38,204.00, liability +38,204.00, straight-line rent re-spread over 27 months.
Accounting · schedule attached
AWS renewal · 50,190.00 / yr
Prepaid schedule drafted with 12 amortisation lines at 4,182.50. Seat count needs confirming before it posts.
Ops · A. Reyes, due 08 Apr
Ohio economic nexus · 94,120 of 100,000
Threshold trips at this run rate in about six weeks. Registration task created and assigned, ahead of the Q2 filing.
Ops · M. Silva, due 14 Apr
1099-NEC · 3 vendors missing W-9
Chased 04 Mar, two returned. Northwind Holdings outstanding; the filing is blocked on it and nothing else.
Ops · chase scheduled 21 Mar
Lease expiry · Suite 400
Termination notice is due 90 days out, on 01 Apr. Calendar item created, deposit reversal already posted this month.
Ops · decision needed by 25 Mar
Nothing waits in an uncategorised bucket. Where TAI is less than certain it still posts to the account this client's own books support, says why, and puts the row in your queue, so the review list is decisions to confirm, not a suspense account someone has to remember.
It starts by reading everything you imported.
TAI builds a picture of the client from their own material: the chart of accounts, the transaction history, the vendors, the documents, the correspondence. Not an industry template with the client's name on it.
That is why its suggestions are specific. It knows this client pays this vendor monthly, that this account is where the founder puts things they cannot classify, and that last March looked nothing like this March.
Offer · A. Reyes.pdf
ReadingOffer · A. Reyes.pdf
Source document · 2 pages
Read from the document itself. Nothing is created yet; the packet is staged as pending.
Vesting schedule
48 months · 12-month cliffVesting schedule · A. Reyes.xlsx
48 rows · exported for the cap table file
Approved · work created
ApprovingRecord 12,000 unit grant on the cap table
Finance · due 01 Apr 26
Cliff vest · A. Reyes
People ops · due 01 Apr 27
Policy acknowledgements
A. Reyes · due 08 Apr 26
Equity is gated to finance. Approved by anyone else and the grant parks as a high-priority finance task rather than landing on the cap table.
Tagging, drafting, and telling you what looks wrong.
It tags transactions, drafts the recurring entries a month needs, and keeps an insight queue of things worth a human's attention: the balance that moved when nothing should have moved, the vendor that appeared from nowhere, the account that has gone quiet.
Ask it a question about the books in plain English and it answers from the client's own ledger and documents, rather than from a general impression of how businesses work.
It also recommends structure: how this chart should be organised for an industry and a stage. That is the difference between books that merely balance and books someone can run a company from.
What TAI does
Proposes- 01Learns the client from imported data and correspondence
- 02Tags transactions and drafts recurring entries
- 03Keeps an insight queue of what deserves attention
- 04Answers questions from the client's own books
It proposes. It does not post.
Everything TAI produces arrives ready to approve, checked against the rules that govern the workspace, so review is a decision, not an investigation.
Where the data will not support an answer it says so. Ask for runway on a ledger with too little history and you are told there is not enough to work with, not given a number that looks authoritative and is not.
This is the part of an AI accounting product that decides whether you can put it in front of a client. Speed is easy. Knowing when to stop is not.
Proposal
Awaiting reviewScreen capture · TAI tagging, 11s. A batch of transactions is coded from the client's own history, one gets a question with a proposed answer, a person answers it on the spot.
Screen capture · TAI answering, 10s. Ask a question about a balance, show the answer and where it came from.
The junior who never gets tired, and always shows their working.
It does the volume. Your team does the judgment. That is the only division of labour that scales past twenty clients.