If fewer rows were saved than your PDF statement shows, first check whether you removed them in the review step, then look at page breaks and wrapped narrations, and finally compare the row count with the statement's own count. A CSV or Excel download of the same period is the quickest cross-check.
Start with what you did yourself
It is easy to forget that the review step lets you decide what gets saved. If you left out rows that looked like clutter, or saved only part of a long list, the missing entries may never have been rejected by the software at all. Open the import history for that upload and see how many rows it recorded, then compare with the number you saw in review.
Where do PDF rows usually go missing?
| Cause | What it looks like | What to check |
|---|---|---|
| Page-break lines | A transaction split across two pages is read as two half-rows, or dropped | Rows at the top and bottom of each page |
| Merged narrations | Two transactions end up in one line, so one amount is lost | A row with a very long description or an odd amount |
| Summary pages | Opening balance, totals or a charges summary are not transactions | Rows near the first and last pages |
| Faint or tiny print | A scanned or compressed PDF reads poorly | Whether you can select the text in the PDF |
PDF is a layout designed for printing, not a table, so reading it back into rows involves some guesswork. That is why a CSV or Excel file is usually more reliable when your bank offers one.
How do I count properly?
Many statements print the number of entries, or you can count them in a few minutes by page. Say page one has 18 transactions, page two has 22, and page three has 9. That is 18 + 22 + 9 = 49. If your import saved 46, three rows are unaccounted for, and you can narrow the search to the page boundaries first.
- Count the transactions on each page of the PDF, ignoring summary rows.
- Count the saved rows for the same account and period.
- Note the difference.
- Compare dates around each page break first.
- Check the first and last rows against the first and last dates on the statement.
Try the same period in another format
Download the statement for the same dates as CSV or Excel and upload it as a separate attempt. If the rows come through fully, you have a cleaner source, and you can compare the two lists. If your bank only offers PDF, keep the PDF as your reference and add what is missing by hand.
Can I just add the missing rows manually?
Yes. SpendixAI allows expenses to be added by hand, one or several at once, which suits a handful of missing lines. Enter the date, amount, narration and the right account. Just be careful not to add something that is already present, or the totals will drift the other way.
When to stop and ask
- The statement is very long and many rows are missing, so a manual fix would take hours.
- The PDF looks like a scan or photo rather than text.
- The layout is unusual, as with a small bank or co-operative.
Keep a note of what you changed
When rows go missing, the trail is easy to lose, so keep a short list as you work: which page, which date, which amount. A line such as 14 March, ₹850, grocery, page two is enough to search for later. If you find that the same kind of row goes missing every time, such as the last line of each page, you have learned something about the layout, and that is worth remembering for the next statement from the same bank. It also tells you which edges of a file to look at first on future uploads, before any totals are compared.
In those cases try the CSV or Excel route, or split the statement into shorter periods and import each separately. A month at a time is easier to check than a full year. SpendixAI cannot promise that every layout will parse perfectly, so treat the review step as the moment you confirm the data, not a formality.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

