The Reports Were Ready. The Firm Wasn’t.
A wealth management firm has 180 client reports ready for quarter-end. Then operations asks one question: ready for whom? A story about AI groundwork, review queues and the decisions that come afterwards.
At nine on Monday, the number on Nandita’s screen was 180.
One hundred and eighty client reports. Prepared for quarter-end. The regional heads had been asking for them all week, and the operations team had finally caught up.
For a few minutes, Nandita allowed herself to feel pleased. She ran operations at a wealth management firm. Her team collected statements, reconciled portfolios and prepared the figures advisors took into client meetings. Quarter-end usually meant late evenings, missing attachments and people asking whether the latest file was really the latest file.
This time the tracker said ready.
Then the head of advisory asked a small question.
“Ready to review, or ready to send?”
The firm, people and figures in this story are illustrative. They do not describe a named company or a customer deployment.
The queue nobody had counted
All 180 reports had been assembled. Only 156 had been approved.
The other 24 were waiting on questions that a finished-looking document could hide.
Seventeen included private-asset valuations with dates that needed checking. Four had unresolved ownership mappings. Three needed a decision about how to present upcoming cash commitments.
Those were different problems, but they landed on the same three experienced people.
The team had counted reports prepared. Advisors needed reports they could use. Between those two numbers sat another queue.
Nandita’s relief gave way to irritation. The tracker was technically correct. It was also telling her very little about whether the firm could meet its promises to clients.
She had more documents. She did not yet have more capacity.
Why the firm needs more than a faster report
A wealth firm works across a book of clients, with different advisors, accounts, entities and investment histories. A process that works for one portfolio can become difficult when the same team must repeat it across many.
A broker sends structured trades. A fund manager emails a statement. A private investment arrives as a PDF. An advisor uploads a document from a client. Market and holdings data come through third-party APIs.
Getting those sources into one place helps. It does not finish the work.
Someone still has to identify the account owner, reconcile holdings, check dates, prepare analysis and decide which exceptions need attention. The report has to pass through review before it reaches an advisor or a client portal.
Ownership, in particular, needs more than a familiar name. CDSL’s explanation of consolidated account statements says consolidation uses PAN and, for multiple holders, the first holder and holding pattern. A firm building a broader client view has to map those records deliberately. Two documents carrying the same family name do not settle which entity owns an investment.
Multiply that work across the firm, and the challenge changes. The question becomes whether the process can move through several teams without losing the source, the context or the person responsible for the next check.
Give the agent a job it can finish
Now imagine introducing an AI agent into Nandita’s reporting cycle.
The instruction should be specific:
Prepare quarter-end review packs for this client group. Use the records in the Vault. Show ownership and source dates. Reconcile the holdings, flag exceptions and prepare the drafts for human review.
The Vault holds the incoming documents and structured data. The agent runs the workflow: reading statements, extracting records, matching instruments, reconciling positions and drafting the requested reports.
That is substantial work. An analyst should not need to open every PDF just to copy the figures into another file.
But a firm should be able to tell which stage each piece of work has reached. Prepared is different from checked. Checked is different from approved. Approved information is what should feed dashboards, client reports and the portal.
If the agent simply produces 180 polished PDFs, Nandita can end up with the same problem she had on Monday, delivered faster.
The second surprise
Nandita looked more closely at the 17 valuation questions.
Several came from the same manager’s statement format. The team had read the document’s issue date as the date of the underlying valuation. The figure had been copied correctly. The date beside it meant something else.
The reviewers had been treating these as separate client problems. There was also a shared source problem to resolve.
They checked the manager’s document, established what each date meant and corrected the records. Each affected report still needed its own review, but the team no longer had to rediscover the same distinction from scratch.
This was the first useful change in Nandita’s morning. She could see which work belonged with the agent, which required a specialist and which recurring question needed to be captured for the next reporting cycle.
The human review had produced context the next workflow could use.
The reviewer needs evidence before approval
A paragraph saying “the portfolio is current” gives a reviewer very little to inspect.
She needs the statement, the relevant date, the ownership mapping and the reconciliation finding. She needs to see what the agent inferred and what the source actually says.
That is the job of the Review Desk: people check the agent’s work, resolve findings and approve the outputs before those outputs reach dashboards and reports.
There are two risks here. The agent can produce an unsupported answer. A person can also accept a plausible answer too quickly. NIST’s July 2024 generative AI risk profile identifies false but confident output and human over-reliance as risks. A review process needs to make checking possible, rather than merely put a human name on the result.
For Nandita’s team, that meant answering a practical question: could the reviewer resolve the exception from the evidence in front of her, or did she have to start the whole investigation again?
An approved report still needs an advisor
The three cash-commitment cases turned out to be different from the valuation questions.
In one, an advisor confirmed that a client had reserved money for a property payment. The payment had not happened. It was absent from the bank transactions. The advisor brought it into the workflow, and the revised liquidity view went through review and approval.
Only then did the dashboard show what the advisor needed for the conversation.
The next step was a decision: should the client postpone a new allocation, explore a smaller commitment or consider another source of liquidity?
Another client could have seen similar numbers and made a different choice. Priorities, restrictions and relationships still mattered.
Across the firm, this was the division of work Nandita wanted. The agent prepared the information. Reviewers checked and approved it. Advisors used the approved outputs, brought in client context and worked with clients on decisions.
When new context changed the information, it went back through preparation and review. The approval process did not make the client’s circumstances stop changing.
What changed for the firm
By the afternoon, Nandita had a better view of the reporting cycle.
| What she first saw | What she needed to manage |
|---|---|
| 180 reports prepared | 156 approved; 24 awaiting specific checks |
| 17 valuation questions | Source-date questions, including a recurring manager-format issue |
| Four ownership exceptions | Records requiring a confirmed client or entity mapping |
| Three cash-commitment cases | Advisor context to capture, review and include before use |
| One queue labelled ready | Preparation, review and approval as distinct stages |
The illustrative counts show the structure of the problem, not a measured productivity gain.
She could now decide where to assign review effort, which advisors had usable reports and which recurring issue deserved a change to the workflow. She could explain a delay without asking an analyst to read out the latest spreadsheet over the phone.
There was still work to do. But it was visible work, with a reason and a next step.
The enterprise question for AI
In our earlier article on AI and wealth software, we argued that preparation would become cheaper while context and judgment would remain valuable. At the level of a firm, that means redesigning the handoffs as well as the individual task.
This is the process we’re building SmartRich around:
Emails, files and APIs → Vault → agent workflows → Review Desk → approved dashboards and reports → human decisions.
Vault, Workflows and Review Desk are the core tools. The firm’s reporting, analytics, tax preparation and client publication depend on how well they work together.
Before the next reporting cycle, take one batch of client reports and count how many are prepared, how many are approved and why the rest are waiting. Look for the questions that recur across clients. Then ask which facts only an advisor or specialist can supply.
That gives the firm a concrete starting point for delegation. It also shows where more automation could simply send more work into an already busy review queue.
On Monday morning, Nandita wanted to finish 180 reports.
By the afternoon, she wanted a process her firm could trust across the next 180 as well.
If your team recognises that queue, let’s talk through one reporting cycle.