Product guides

Reading reports while a month is half imported

Statements arrive late and imports lag. Know how to interpret reports on incomplete data and when to wait before drawing conclusions.

Editorial illustration for Reading reports while a month is half imported

Real-life data does not arrive on the first of the month. A card statement lands on the tenth, a bank file is downloaded on the twentieth, and a few cash entries never get logged. If you open reports during that gap, you are looking at a partly complete month. The reports are not wrong, but they must be read differently.

Know what is in and what is missing

Before reading anything, ask which accounts have data for the period. The account detail screen shows a coverage grid of months with imported statements and highlights gaps. If a key account has no statement for the month, any report about total spending is understated.

Insights may also point this out. A missing statements alert exists for precisely this reason: to say that a conclusion rests on incomplete data.

Totals will be low; shares can mislead

The most obvious effect is that totals are lower than reality. Less obvious is the effect on proportions. If a card with mostly shopping is missing, the category mix will tilt towards the accounts that are present, perhaps towards bills and groceries. Do not trust the donut chart's proportions until all main accounts are in.

Which conclusions are safe

Some readings survive missing data better than others.

  • **Safe:** the amount spent on things in the accounts you do have.
  • **Risky:** the total, proportions, and any comparison with a complete month.
  • **Unsafe:** conclusions about savings, since income and spending may be unevenly covered.

If you must decide mid-month, anchor on the accounts that are complete, and treat the rest as unknown.

Fixing the gap

The simplest remedy is to import the missing statements. If a statement is not yet available, consider entering the largest known items manually, flagged with a note, then replacing them when the statement arrives. Take care not to create duplicates when the import eventually comes; the review step flags rows that look like transactions you already have.

Comparing with last month

Avoid comparing a half-imported month with a complete one. The comparison will show an apparent fall in spending that is only an artefact. Instead, compare like with like: the first half of this month against the first half of last month, using a custom range, if both are complete for that stretch.

A simple checklist before reading

  • Do all main accounts have data through the end of the period?
  • Is the review queue cleared?
  • Have duplicates been checked?
  • Are there cash entries I have not logged yet?
Data stateReading approach
All accounts completeRead normally
One account missingRead per-account, avoid totals
Many accounts missingWait, or use only for rough orientation
Provisional manual entriesMark in notes and replace later

Use the gap productively

A half-imported month is a good moment for the unglamorous jobs. Categorise leftover items, set merchant defaults, resolve duplicates and match receipts. When the missing statement arrives, the import will land in a tidy system and review will be quick. The waiting time becomes preparation rather than frustration.

Record what you know is missing

Write a one-line note somewhere visible, such as card statement for this month not yet imported. It reminds you not to trust the totals, and when you look back at the screenshot or export you made that day, the note explains why it looked low.

Wait when you can

If the decision is not urgent, wait for the data. A budget review on the fifth, with complete statements, is worth more than one on the twentieth of the previous month with holes. The habit of reviewing once the month's data is complete is itself a reliable way to avoid false alarms.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports