How to Write Budget vs Actual Variance Analysis With AI

Every month, someone at your firm turns the budget and the month's actuals into a page of variance commentary, how each line differs from budget and why, which the partners read before they decide anything.

The arithmetic takes an afternoon. The reasons take the rest of the week, because each one sits with whoever made the call: the partner who agreed a lower fee, the hiring manager whose start dates slipped, the person who coded an invoice.

An AI assistant can write that page now. It cannot know a reason nobody wrote down, so the reasons are what the agents go and get.

We ran this on an invented month: September at Tamberlin Wealth Partners, a made-up wealth management firm of about 180 people.

At Qvery, we help wealth and advisory firms put the monthly commentary in the partners' hands on close day and keep their finance people focused on the questions that matter, with custom AI agents that read your ledger, your billing system and your team's notes, split the fee line into what moved it, draft every reason with its source and send each open question to the person who can answer it.

The Fee Line Moves for Four Reasons, and One Is a Decision

A wealth firm's fee line is assets times a rate, so a fee miss is never one thing, and splitting it is the step that turns a variance into a decision.

The agents split the miss into four moves that add up exactly: where the month started, markets, net flows (money clients put in minus money they take out) and the fee rate, the first three priced at the budget's rate, on the balance, rate and period your billing used (our sample bills monthly in arrears on month-end assets).

The fee rate is the one move that was a decision the firm made. In our sample, one household's fee went from 0.80% to 0.55% on about $310M from September 1, a decision made to keep the relationship. That is $64,583 a month, about $775,000 a year if nothing else changes.

The Reasons Sit in Your Team's Notes and the Ledger's Postings

Handed only the budget and the actuals, an assistant says what moved and asks for the reasons, because the files hold none. The reasons sit with your team and in the ledger's postings, and the agents read both.

Our ten notes include one that explains nothing about September (a laptop refresh moved from October to November), as real notes do. A flagged line with no note stays unexplained in the commentary, with the name of whoever should be asked; the agents never fill the gap with a guess.

Look at the Travel rows. One posting there reads "Gold sponsorship, regional advisor summit", $31,000. The budget holds that sponsorship in Marketing, and the marketing team's note says it was paid as planned.

One coding error shows up as two variances: Travel $34,600 over and Marketing $28,000 under. No note mentions the coding, and only the postings show it.

Each Line Is a Decision, Timing, an Error or a Question

The skill in variance commentary is sorting what happened, because a page where every variance reads as a problem teaches the partners to ignore the page. Three of September's lines, sorted by what they are:

Advisor pay and marketing both came in favorable, and neither is good news: pay is under because people started late, marketing because a cost sits on the wrong line. A favorable variance with a timing or coding cause is not a saving, however good it looks on the page.

Two of the findings are errors in the books, and the agents propose the fix for both. They write each proposed entry into the workbook, with the posting reference and, for the prepaid, the monthly release; they never touch the ledger. A person posts, and a second person approves.

After the two entries, technology is $10,500 over, marketing $3,000 and travel $3,600: all three drop under the rule, and the commentary loses two paragraphs that would have explained an error as spending.

Anything that changes a client's fee, moves money, or edits a posted entry stays with people, because none of it can be undone from a spreadsheet.

Work out what the monthly commentary costs your finance team, and what the agents hand back.

The calculator opens on an example: three people on the pack, each about $146,800 a year with benefits (the Bureau of Labor Statistics' May 2025 median for financial and investment analysts, plus 30%). We assume each spends about three days of the month on it, which is that week of asking shared among three people, and that the agents take 60%: the reading, the split and the drafts.

On that example the job falls from $66,060 to $29,424 a year, the agents' running cost included (about $250 a month for model usage, hosting and upkeep). That is $36,636 a year and 562 hours back for the questions only your team can answer, and every $10,000 of the build is earned back in about 3.3 months.

Qvery's Agents Have the Pack Ready on Close Day

To have the pack waiting on close day, we build AI agents on your own ledger, your billing system and your team's notes. They start when the close is marked complete, so nobody has to remember to run them and nothing runs on half-booked numbers.

They read the ledger export, the billing system's assets report and the notes, and apply a materiality rule written before the month, which decides which differences are big enough to explain ($25,000 or 10% of budget in our sample), plus an inside check that opens any line on budget whose accounts moved against each other.

They draft every reason with its source and send each unresolved line to the person named beside it.

Then they stop for a person: someone approves every entry and the final page before anything leaves finance. Before they connect, we agree in writing what they may read and where the data is processed, every action they take is logged, and households appear by ID, never by name. Each month you see the hours from close to pack they save and the errors the review still catches.

Bring One Closed Month and Your Team's Notes

We map how your month-end runs and connect the agents to the accounting and billing systems you already use, then they draft the pack for a month you have already closed, beside the one your team wrote. The first working pack arrives within two weeks, we train whoever reviews the draft, and a person still approves and posts every entry.