AI suggests, the accountant decides
There is a version of AI in accountancy that should worry you: software that reaches a conclusion about a client's tax position and acts on it. Fynvro OS is deliberately not that. It surfaces what looks wrong and drafts the explanation — a person decides whether it is right and whether to send it. That distinction is the whole design.
Why the line matters here more than elsewhere
An accountant carries professional responsibility for advice given in their name. That responsibility cannot be delegated to software, and no client will accept “the system said so” as an explanation.
So the question is not whether AI is capable. It is which part of the job is safe to automate.
What is safe to automate
Noticing
Checking every connected client's ledger every day for the same ten patterns is work no human should do and no human does well. It is repetitive, it is rule-shaped, and missing something is the main risk. That is exactly what software is for.
Ranking
Deciding that a director's loan nearing the nine-month window outranks an aged receivable is a consistent rule, not a judgement call. Applying it the same way every morning is a machine's job.
Routing
Critical to partners, Warnings to the bookkeeping team, Info to advisory. A rule, applied identically every time.
Drafting
Explaining s455 in plain English is the same explanation every time, changed only by the numbers. Writing it from scratch on each occasion is wasted effort.
What must not be automated
Deciding whether the finding is correct
A pattern can flag a director's loan when the balance is actually a timing artefact of how something was posted. Only someone who knows the client can tell. The software is reporting a signal, not a fact.
Deciding what to do about it
Repay, declare a dividend, process as salary, accept the charge — that depends on reserves, the director's personal position, what happened last year and what is planned next. None of that is in the ledger.
Talking to the client
Tone, timing and context are professional judgement. The same true fact lands very differently depending on how and when it is delivered.
Anything filed
A submission is a statement made by the firm. It needs a human behind it.
Why a draft beats an automated send
Consider a director's loan approaching the s455 window.
Automated: the client receives an email about a tax charge, possibly without context, possibly wrong, possibly before their accountant has even seen it. If it is wrong, the firm's credibility takes the damage.
Drafted: a partner opens a prepared explanation with the right figures and the right dates, reads it in thirty seconds, adjusts a sentence because they know the client took a large dividend last year, and sends it. The work is done, the judgement is human, and the firm's name is on something a person approved.
The saving is the same either way. The risk is not.
The rule we hold to: Fynvro OS never sends a client communication on its own. Arya drafts; a person reviews and sends. There is no setting that changes this.
Being honest about what it does not know
A finding based on incomplete data should say so rather than present a clean number. If a bank is unreconciled, anything derived from that ledger is provisional, and the software should admit it.
That is the same principle that governs everything we build: a figure with a stated gap can be acted on. A confident figure hiding a gap cannot, and it is always wrong in the flattering direction.
What this means for your firm
You should be able to answer three questions about any tool you let near client data:
- What can it see? For Fynvro OS: connected clients' Xero data through twelve official OAuth scopes. It reads; it does not post to your clients' books.
- What can it do without a human? Notice, rank, route and draft. Nothing else.
- Who is accountable for the output? You are. The software is a colleague who reads everything and flags things — not one who signs anything.
If a tool cannot give you clear answers to those three, that is worth more attention than its feature list.
Frequently asked questions
Does Fynvro OS send emails to my clients automatically?
No. It drafts them and waits for a person to review and send. There is no automatic-send setting.
What can Fynvro OS see in my clients' Xero data?
Ledger data through twelve official OAuth scopes — Trial Balance, contacts, invoices, bills and bank reconciliation status. It reads only; it does not post journals or change anything.
Can AI be trusted with tax advice?
Not to give it. It can be trusted to notice things consistently and to draft explanations that a qualified person then checks. The judgement, and the responsibility, stay with the accountant.
What happens if a finding is wrong?
A person catches it, because nothing reaches a client without review. Patterns surface signals, not conclusions.
Who is responsible for advice based on a finding?
The firm. The software supports the decision; it does not make it, and it never communicates it on your behalf.