The report library covers many standard questions, but sometimes yours is specific: how much did all the work travel on one card cost between two dates, grouped by month? The report builder exists for such cases. It rewards a clear question, and punishes vague tinkering, so the first step is to write the question down.
Begin with a one-line question
Write something like: what did I spend on groceries and eating out in the last three months, by merchant? That sentence contains the ingredients of a report. Spending is the measure, groceries and eating out are filters, the last three months is the period, and by merchant is the grouping.
If you cannot write the sentence, you are not ready to build; the result will be a pile of numbers without a point.
The controls
The builder offers a handful of controls that map to the parts of your sentence.
- **Filters** restrict the data: by period, category, account, business or personal, and other fields.
- **Group by** decides how rows are combined, for example by category, merchant or month.
- **Sort by** and **then by** order the result, so the biggest items rise to the top.
- **Name** lets you save the report for reuse.
As you change controls, the builder shows summary figures such as total spend, number of transactions and the average per transaction. These work as a live check on whether your filters are doing what you intended.
Test with a small slice
Begin with a narrow period or a single category and look at the result. If the summary figures match what you know, widen the filters. If the builder reports that no spending matches, it suggests a wider period or fewer filters. That message is usually a sign of over-filtering.
Save the ones worth keeping
If the report answers a question you will ask again, give it a name and save it. Choose a name that states the question, such as Work travel by month, rather than a vague label. A saved report turns a ten-minute build into a ten-second visit next time.
Export when it needs to travel
When the report must leave the app, export it as CSV. The builder will refuse to export if there is nothing to include, and tells you to adjust the filters first. Keep in mind who will read the file and what they need; a short, focused export is better than a sprawling one.
| Part of your question | Builder control |
|---|---|
| What kind of spending | Category or merchant filter |
| When | Period filter |
| Which money | Account filter |
| How to slice it | Group by |
| What matters most | Sort by |
A worked example
Consider the question: how much did I spend on fuel and parking for work from one card in the last quarter, by month? Filters: business, two categories, one account, last three months. Group by month. The builder shows a total, a count and an average. If the count is lower than expected, some entries may be uncategorised or unflagged; fixing them and returning to the report is a quick loop.
Each pass makes the records better, which is a side benefit of building reports.
Know the limits
The builder works on the data you have. If categories are muddled, a report grouped by category will be muddled too. The quality of any custom report depends on the quality of the records beneath it, so tidy categories and merchants first. A good builder cannot repair a poor ledger.
Used with a clear question and clean data, the builder becomes the quickest way to produce exactly the view an accountant, partner or your future self will need.
Useful ideas start with a clearer picture of your own spending.
Explore your reports
