|
TUE · NOV 17 · EDITION |
Build a month-end flux commentary workflow with an AI assistant
Writing flux commentary from scratch eats time a controller does not have at month-end: this workflow takes a two-period trial balance export and produces a structured first draft, with bracketed placeholders wherever the assistant cannot infer cause from the data alone. It is built for the accountant who needs defensible workpaper commentary fast, not polished prose that obscures what still needs human judgment. The prompt enforces that discipline by design: the assistant is explicitly instructed not to remove bracketed notes to make the output appear more complete.
BUILD WITH AI
Build a month-end flux commentary workflow with an AI assistant
This workflow turns a two-period trial balance export into a first-draft flux commentary in one assistant session. The output is a structured draft with bracketed placeholders wherever the assistant cannot determine cause from the data alone.
1 |
Export a two-period trial balance from your accounting system as a CSV, with columns: account code, account name, prior period balance, current period balance, and variance amount. Remove subtotal rows. |
2 |
Open a general-purpose AI assistant that accepts file or text input, and paste or upload the CSV. |
3 |
Set your materiality threshold by including this instruction at the top of your prompt: 'Only comment on accounts where the absolute variance exceeds [your dollar threshold].' |
4 |
Paste the following prompt: 'You are preparing month-end flux commentary for an internal workpaper. The attached trial balance shows two periods. For each account where the absolute variance exceeds the threshold I specified, write two to three sentences explaining the likely cause based on the account name and the direction and size of the movement. Where the cause cannot be reasonably inferred from the account name alone, write the two sentences you can support and add a bracketed note: [Cause unconfirmed: reviewer to verify against subledger]. Group accounts by: revenue, cost of goods sold, operating expenses, other income and expense, balance sheet. Do not invent subledger detail. Do not remove any bracketed note to make the commentary appear more complete.' |
5 |
Review the draft output and confirm that every account meeting your threshold has an entry and that no account below the threshold has been included. |
6 |
Resolve every bracketed placeholder by pulling the relevant subledger report, accrual schedule or supporting document and writing the confirmed cause in plain language. |
7 |
Trace each figure the assistant states (dollar amounts, percentages, period references) back to the trial balance CSV before the commentary is copied into the workpaper. |
8 |
Have the responsible accountant or controller sign off on the final commentary as a named preparer step in the workpaper, not as an AI-generated exhibit. |
WORKED EXAMPLE
In practice
A controller at a 12-entity services firm is closing the month just ended. She has a two-period trial balance for one entity as a CSV: 47 accounts, prior and current period balances, variance column already calculated. She needs flux commentary for the management report due in two days.
What came back. The assistant returned commentary for 19 accounts, grouped correctly. Most revenue and payroll entries had clean two-sentence explanations consistent with the account labels and variance directions. Four accounts in prepaid expenses and intercompany receivables carried bracketed placeholders. One entry for a large increase in professional fees stated a cause (outside counsel costs) that was plausible but not supportable from the account name alone, and the controller added a placeholder there herself before moving on.
How it was checked. The controller opened the CSV alongside the draft and confirmed that every dollar figure the assistant cited matched the variance column exactly, and that no account below $10,000 had been included.
A constructed example. The prompt is usable as written; the figures show the shape of a result, not a measured one.
WHEN TO USE IT
| WHEN NOT TO
|
Attio is the #1 fastest-growing CRM on Brex and Ramp
Built for the most ambitious companies in GTM, Attio is an end to end revenue platform that allows teams to run multiple plays across different revenue motions and lifecycles.
Teams at the frontier are already building on it: Granola, turbopuffer, Modal, and many many more.
FROM OUR PARTNERS
1 | AI Starter Kit 1 friend · 10 copy-ready prompts for everyday work | Free gift |
3 | Close Prompt Playbook 3 friends · All 20 month-end prompts with reviewer's guides | $39 value |
5 | Playbook + Close Skills 5 friends · The Playbook plus five Claude skills: bank rec, flux review, duplicate payments, deferred revenue and journal entry review | $99 value |
10 | Month-end close kit 10 friends · The Playbook, the Close Skills and the AI-assisted month-end close workflow | $149 value |
Month-end close kit The whole month-end close, with AI doing the first pass. The AI-assisted month-end close workflow, the Close Prompt Playbook and all five Close Skills in one kit. One payment, 30-day refund.
New: the AuditFriendly Library, 49 close, audit and bookkeeping tools from $9, some free. Playbook buyers get the matching Library items free. Browse the Library |
GO DEEPER
Go deeper
Next issue: more of the tools and shifts reshaping how accounting gets done.
Forward this to the partner still doing it the old way.
An original workflow written for practitioners. Replicate it in a sandbox first; nothing here replaces your review.
How accountants are using AI, automation and smarter workflows to close faster, audit cleaner, and free up time for real work.
| Month End Closers · Everything that moved in accounting this week |
| Accounting Stack · The software, head to head |
| The Remote Accountant · Remote accounting roles with pay, every weekday |
| The Finance Nomad · Remote finance roles with pay, every weekday |
Audit Friendly · modernaccounting.ai · Audit Friendly Data

