You do the books, not just the review
Advisor access in TaxItEasy isn't read-only. On a client's bank transactions you can categorize, correct VAT rates, confirm and reject invoice matches, link invoices manually (including across a currency mismatch, with an explicit override), request receipts, and clear transactions as booked, one at a time or in bulk. The client uploads; you book.
Category suggestions: Rules > Learned > AI
For open, uncategorized transactions the system proposes a category. Three sources compete, with strict precedence:
- Rules: the company's own matching rules. Deterministic and always first: an explicit rule outranks everything.
- Learned: the per-company memory of past categorizations of the same counterparty. It activates after the same category has been chosen 3 times for a counterparty, and a single correction makes the newest choice win. Learning is strictly per client company: no data is pooled across customers.
- AI: a model-based fallback for the long tail. Low-confidence guesses are dropped rather than shown.
Whatever the source, the suggestion renders the same way: a chip above the category dropdown ("Suggested: {Label} · Accept"), shown only when there is a suggestion and the transaction has no category yet. Accepting books it in one click and is recorded in the audit log. Nothing is ever auto-applied: a human decision sits in front of every booking, always.
Two timing details: your corrections teach the learned layer immediately, but a new suggestion chip appears with the next categorization batch run (a bank import or the nightly sweep) rather than instantly. And suggestions only ever propose. The receipt gate and clearing rules still apply to whatever you accept.
Creating categories inline
When the client's category list doesn't fit, you don't have to leave the panel: "+ Add category…" creates a new custom category on the spot, with account-code guardrails so the new category lands sensibly in the chart. The list you pick from combines the per-country standard categories with the company's custom ones, and a category that doesn't match the transaction's money direction is rejected rather than mis-booked.
Bounded access: what you can't do
The write access is deliberately fenced:
- No billing: you can't see or touch the client's subscription or payment methods.
- No team management: you can't invite or remove members, or add other advisors.
- No deletions: you can't delete the company, documents, or invoices.
- No company settings beyond the tax regime (itself behind a two-step confirm and audited).
- Strict per-client scoping: an advisor of company A gets a hard denial on company B, even in search results.
Every advisor action is written to an append-only audit log, every write shows up in the client's own activity feed with your name and role, and entries you create carry a "by tax advisor" badge in the client's lists. The client can revoke your access at any time. Revocation immediately deletes your per-document decryption keys, and if it happens mid-session the UI detects it and returns you to your dashboard. This is by design: bounded, transparent access is what lets clients hand their books to an external advisor with confidence.
Related
- The transaction work queue, explained is the queue you're booking from.
- How matching learns from you covers the learned layer in detail.
- Bulk clearing and smart cohorts is the 50-at-a-time version.
- Read-only scope: what I can and cannot see shows the access model from the client's side.
- Why VAT bookings need a receipt is the gate that clearing respects.