Cards and UPI

Missing month in your imported statements? A gig worker's gap check

Find which month is missing from imported bank statements by matching each statement's closing balance to the next opening balance, with a gig-worker example.

Editorial illustration for Missing month in your imported statements? A gig worker's gap check

To find a missing month, list the date range each statement covers and check that every closing balance equals the next statement's opening balance. Where they do not meet, a stretch of days was never imported. For gig workers the gap is easy to miss, because payouts come weekly and the money still looks busy.

Do the check each time you import, not at year-end, when a friend or a lender asks for twelve months of proof.

Why do months go missing?

  • The bank's download screen defaults to the last 30 days, not the calendar month.
  • You downloaded a statement for a different account, such as the payout wallet, and forgot the main one.
  • A file failed to import and you did not notice the failure.
  • The statement period runs from the 15th to the 14th and you assumed it ran by calendar month.

How does the balance chain expose a gap?

Say your statements cover these ranges.

StatementFromToOpeningClosing
First1 Apr30 Apr₹6,200₹11,850
Second1 May31 May₹11,850₹9,400
Third1 Jul31 Jul₹14,300₹8,950

The second closing balance is ₹9,400 but the third opening balance is ₹14,300. Nothing covers June. During those weeks, ₹4,900 net moved into the account, because 14,300 minus 9,400 is 4,900. That one subtraction tells you how big the hole is before you open a single transaction.

What do I do about June?

  1. Download a statement for 1 June to 30 June from the bank, with exact dates.
  2. Import it into the same account, not a new one.
  3. Check that its opening balance equals ₹9,400 and its closing balance equals ₹14,300.
  4. If the chain closes, the gap is filled. If not, a day inside the month is still missing.

Does an overlap cause double entries?

Sometimes people download extra days to be safe. If you import 25 May to 5 June after already importing May, the five days in May appear twice. SpendixAI flags possible duplicate imports and keeps an import history with a status for each file, so you can see what was uploaded and whether it failed. A Possible duplicate charges report lists the same amount to the same merchant within two days, which is useful for payouts that look repeated.

What if I use more than one account?

Run the chain for each account separately. A month can be complete in your bank account while the platform wallet has none. Keep the files in folders named by account and month, such as Bank-2026-06, so a gap shows in the folder list.

Is a month with no transactions suspicious?

Not necessarily. A gig worker may take a fortnight off, or a platform may pause payouts. But a statement with a genuine gap should still show an opening and closing balance. If both are the same, the account really did nothing; that is a valid statement, and you should import it so the coverage has no hole.

If, instead, the file is empty because the download failed, the balance chain will not match, which is how you tell the two apart.

A quick audit you can do tonight

  1. Open your list of imported statements, sorted by date.
  2. Write down the first and last day of each.
  3. Look for any day that is not covered.
  4. Download and import the missing range.

If you are asked for proof of income for a loan or a visa, a gap-free set of statements saves an awkward conversation.

SPENDIXAI JOURNAL

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

Explore your reports