Some insights are less about your spending than about the quality of your data. The missing statements card is one of these. It names accounts where one or more months have no imported statement, and in doing so warns you that anything computed for those months is incomplete. Treat it as a request for maintenance, not an accusation.
What the card tells you
For each affected account, the card lists the months for which no statement has been imported. These gaps matter because transactions in those months may be missing, which skews totals, trends and comparisons. The same information appears as a coverage grid on the account detail screen, where each gap can be tapped to start an import.
Why gaps are costly
A missing month makes spending in that period look lower than it was. A trend that shows a fall may be an artefact. Budgets for the month show less used than reality. Balances may not reconcile. Everything built on the data inherits the gap, which is why closing it is a high-value task.
Closing a gap
Download the statement for the missing month from your bank. Import it into the right account, review the staged rows, and confirm. After the import, check the coverage grid: the month should now be marked as covered. Reconciling the account against the statement confirms that nothing else is off.
If a statement is not available, perhaps because the account is new or the bank only keeps a limited history, enter the largest known items manually, with a note saying the month is partly reconstructed.
Prevent future gaps
Make importing a monthly habit. When the statement arrives, import it. A good trigger is the monthly money review: before reading reports, check that every account is covered. Cards and wallets are the most commonly neglected, since their statements arrive by separate channels.
Not every gap is a problem
An account you opened mid-year will not have statements before that date, and a dormant account may truly have no activity. The card may flag these anyway. Use judgement: if there truly were no transactions, the gap is harmless. Archiving accounts you no longer use stops them cluttering your coverage view.
| Situation | Response |
|---|---|
| Recent month missing | Download and import now |
| Old month missing, statement available | Import to complete history |
| Account opened later | No action needed |
| Account no longer used | Consider archiving |
A worked example
An account shows coverage for nine of the last twelve months, with gaps in three. Importing the missing statements adds a few hundred transactions. After the review, the quarterly totals shift noticeably, and a reconciliation now agrees with the bank. The earlier reports were not lying, they were incomplete. The effort of closing the gaps repays itself the first time a decision depends on those months.
Who should do this
In a workspace with several members, the person who downloads statements is usually an owner, admin or accountant. Agree who imports each account and when. Without a named person, every month depends on someone noticing the gap, and the gap often goes unnoticed until the quarter is already closed. A single owner for each account removes the ambiguity.
Check the grid after every import
After each import, open the account and look at the coverage grid again. Confirm that the month turned from gap to covered. If it did not, the import may have used the wrong account or dates. Catching this immediately costs seconds; discovering it at year end costs hours.
Use it as a pre-flight check
Before any serious analysis, a budget review, a tax summary or an export for an accountant, glance at the missing statements card. If it shows gaps, fix them first. Analysis on incomplete data takes just as long as analysis on complete data, and is much less reliable.
The card is a small, steady reminder that good decisions begin with complete records.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


