The insights screen has a button labelled explain this month. It produces a short written summary of your spending for the period: what stood out, where money went, what changed. Used well, it saves the effort of reading several reports. Used carelessly, it risks being taken as a verdict. A few notes on how it works help you get the best from it.
What happens when you press it
Before it runs, the app asks whether you want to generate it. The dialog explains that it uses a small amount of your AI budget, and that the use is recorded in AI usage. That transparency matters: the summary is not free in the sense that it draws on a budget set by your workspace.
If the narrative is switched off, the screen says so and points to AI settings where it can be turned on. Those settings are managed by the workspace owner, so a member may need to ask.
What the summary is built on
The narrative draws on your recorded transactions and the figures computed from them. It is only as good as the data. If a statement is missing, a category is muddled or a month is half imported, the summary will reflect those flaws. Before generating it, spend a minute on housekeeping: clear the review queue and check that accounts are up to date.
Reading it critically
Treat the summary as a first draft of your own observations. Read each statement and ask whether you can see it in the numbers. Where it mentions an increase, check the figure in a report. Where it mentions a cause, look at the transactions. Insights provide a way to see the transactions behind a figure, which is the best route for verification.
The summary is a starting point for questions, not a source of advice. It does not know your plans, your obligations or the reasons behind your spending.
Choosing when to use it
The feature earns its cost when you do not have time for a full review, or when you want a fresh angle on a month you have already read. It is less useful when you have just done a careful review yourself, or when the data is incomplete. Using it once a month, after the data is in place, is a reasonable rhythm.
Keep the AI budget in mind
Because each run uses part of an AI budget, avoid generating it repeatedly for the same period. If it was useful, note the points that mattered. If you need more detail, use the question box on the insights screen sparingly, or consult the reports directly, which do not draw on that budget.
| Do | Avoid |
|---|---|
| Generate after data is complete | Generating on half-imported months |
| Verify claims against transactions | Taking the text as fact |
| Note two or three useful points | Running it repeatedly for the same period |
| Check AI settings if it is off | Assuming the feature is broken |
What to do with the output
If the text raises something you want to remember, copy the key points into a note with the date, or act on them straight away. Narratives are easy to forget because they feel like reading rather than doing. Attaching one concrete action to each helpful statement, such as adjusting a budget or writing a rule, is what makes the feature worth its cost.
From narrative to action
The best use of the summary is to turn it into a decision. If it observes that eating out grew, check the category and decide whether to adjust a budget. If it observes a new recurring charge, check the list of bills. The text is only valuable if it changes something you do, and verifying before acting keeps that change sound.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


