The two-step rule: why Tia never auto-posts to your books
AI is right enough to be useful and wrong enough to be dangerous. The two-step rule keeps the human where it matters — and ships value everywhere else.
There's a rule we wrote down on day one of building Taskezy and have never broken: Tia never auto-posts to your books.
Every accounting action is two steps. Tia extracts the receipt, drafts the entry, and proposes it. You confirm. Then it posts. Three taps if you're moving fast, never zero.
This piece is about why that constraint is the whole product, not a polite limitation.
What AI gets right and wrong
Modern LLMs are about 95% right at extracting structured data from a receipt photo. That sounds great until you remember that 5% wrong, applied to the books, means a wrong VAT line, a misclassified expense, a journal entry pointing to the wrong project. Compounded across a quarter, that's a closed-period adjustment, an angry accountant, and a real cash impact.
The 5% isn't where AI is dumb. It's where AI is plausibly wrong — exactly the case that's hardest to catch in a downstream audit.
The cost of removing the human
The seductive demo is "I forwarded a receipt and it appeared in Zoho." That's two seconds of magic and a long tail of misery. Because once you remove the human from the loop:
- Wrong vendor mappings persist silently. Tia doesn't know the difference between "Plumbus Trading" and "Plumbus Trading LLC" until you tell her — and if she just posts both, you have two vendors in your books forever.
- VAT on the wrong line stays wrong until the FTA filing.
- The mental model the owner has of cash flow stops matching the books.
Trust, once eroded by a single bad post nobody noticed, is hard to rebuild.
Where we ship value anyway
The two-step rule is a constraint on posting. It's not a constraint on the rest. Tia still:
- Captures the receipt in two seconds — no app, no form.
- Drafts the entry with vendor, amount, VAT, project pre-filled.
- Reduces the action from "open Zoho, find the right form, type 11 fields" to "tap confirm."
- Asks once and remembers — the second time you forward a Plumbus receipt, the project field is already correct.
That last part matters more than the first three. The product gets sharper the more you confirm, because every confirmation is a labelled training example for your business.
Where it doesn't apply
The two-step rule is books-of-record only. For non-money actions — drafting a brief, summarizing a project status, looking up an invoice number — Tia just answers. There's nothing to confirm because nothing is being written.
The line is: if it changes a number that an accountant would care about, two-step. Otherwise, ship the answer.
What we tell every pilot
When we onboard a design partner, the question that always comes up is: can we turn off confirmations once Tia is good enough? The answer is no. Not because we don't trust the model — because we don't trust one of us, alone, at 11pm, on a phone, to be the only check on the books.
The two-step is for both of us. It's the contract.