AI-generated financial reports vs live, scoped access: what fractional CFOs should use for boards and investors

If you run finance for several companies, you have probably already pointed an AI assistant at a Xero or QuickBooks export and asked it to summarise the quarter. It is good at that. The question is not whether to use it — it is which parts of stakeholder reporting it is the right tool for, and which parts it is not.

This guide is about that split: what AI assistants do well for board and investor reporting, where they run out, and what live scoped access does instead.

What AI assistants are genuinely good at

Give an AI assistant a trial balance, a P&L export or a list of transactions and ask what changed, and it will come back quickly with something useful. Specifically:

• Drafting the narrative. Turning a variance into two paragraphs a board can read is writing, and writing is what these tools are for. A first draft in seconds beats a blank page.
• One-off analysis. "Which cost centres grew faster than revenue this quarter?" is a question you might otherwise spend an hour pivoting towards.
• Summarising at the right level. The same figures described for a founder, a lender and a department head are three different documents. Producing those three from one set of numbers is well-suited to a language model.
• Getting unstuck. Asking for the three things worth investigating in a set of accounts is a reasonable use of a tool that has read a lot of accounts.

None of that is in question, and none of it is what the rest of this guide argues against.

Where it runs out for ongoing stakeholder reporting

The difficulty is not quality. It is that a report is a document, and stakeholder reporting is a standing need. Those two things fit badly, and the gap shows up in five places.

Every update is manual. Pull the data, prompt, read the output, check it, format it, send it. Then do it again for the investor who needs less detail, and again for the department head who needs a different slice. Then do all of it again next month. The effort does not fall as the number of stakeholders grows — it multiplies.

A sent report is out of date the next day. A pack describes the business as it was when you built it. An invoice raised the following morning is not in it, and nothing about the document tells the reader that. Every question it provokes comes back to you, and the answer is another export.

Controlling who sees what is hard, and over-sharing is easy. Scoping a report by hand means remembering, every month, that this board member sees everything, that investor sees the summary, and that department head sees only their cost centre. One copy-paste of the wrong file and somebody has payroll.

There is no access control, revocation or record. Once a PDF is sent it is out of your hands. You cannot withdraw it when somebody leaves the board, and you cannot answer "who looked at the September pack" because nothing recorded it.

The figures still need checking. Anything generated from your data should be read against the books before it goes to a board — the same standard you would apply to a number typed by a person. That check is quick, and it does not go away, so it is part of the per-update cost rather than something a better prompt removes.

What live, scoped access adds

A live view is the other half of the job. Instead of producing a document and sending it, you connect the company's Xero or QuickBooks once and give each stakeholder their own view of it:

• Scoped per person. By account, tracking category, customer or supplier — individually or combined. The board sees the whole company, the investor sees a summary, a department head sees their own cost centre and nothing else.
• Always current. Everyone is looking at the figures from the latest sync, so there is no version to chase and no pack that aged out the day after it was sent.
• Read-only for viewers. An invited viewer can look and cannot change anything.
• No accounting login. Viewers sign in with a one-time email link. They never need Xero or QuickBooks credentials and never reach the books.
• Revocable. Access can be withdrawn when somebody's role ends, which is not a thing a sent file supports.

See secure financial sharing for how the scoping works.

Use both

These are not competing answers to the same question. They answer different ones:

The division that works in practice: AI for the analysis and the narrative, live access for the numbers stakeholders rely on. Write the commentary with an assistant, check it, and send it as commentary — then let the board, the investor and the department head open the current figures themselves instead of asking you for them.

That also makes the drafting better. When the numbers are already available to the reader, the written part can be about why rather than about what, which is the part a fractional CFO is actually being paid for.

How to set it up in Vizii

1. Connect the company's Xero or QuickBooks. One connection per company, through the platform's own authorisation.
2. Run a sync to pull the current data.
3. Open Invite and enter the stakeholder's email address.
4. Choose the scope. Full company for the board; a tracking category for a department head; specific accounts for a lender.
5. Send it. They sign in with a one-time email link and open their own view.

Repeat step 3 onward for each stakeholder. Changing the figures later takes no further action — a sync updates every view at once.

Vizii for fractional CFOs covers the rest of the setup across several client companies.

FAQ

Should I stop using AI assistants for financial reporting? No. They are good at drafting narrative and at one-off analysis, and this guide does not argue otherwise. The point is that a generated document is the wrong shape for a standing reporting need, not that the generation is poor.

Can I use an AI assistant and live access together? Yes, and that is the combination we would suggest. Use the assistant for the commentary and the analysis, and give stakeholders live scoped access to the figures the commentary is about.

Do the figures from an AI assistant need checking? Anything going to a board should be read against the books first, whether a person or a tool produced it. Build that check into the process rather than treating it as optional.

How is a live view different from emailing a dashboard screenshot? A screenshot ages the same way a PDF does and carries no access control. A live view is current whenever it is opened, is scoped to that person, and can be revoked.

Does a stakeholder need a Xero or QuickBooks login to open their view? No. They sign in with a one-time link sent to their email, and receive read-only access to the view you assigned. They never see the books.