Bulk importing through an AI assistant works for lists you have typed yourself, such as cash spending, but it is the wrong tool for bank statements. Send entries in batches of ten, make the assistant repeat count and total before saving, and check both against your own notes. For statements, upload the PDF, CSV or Excel file to SpendixAI, which lets you review rows before saving.
When is an assistant the right route?
Use chat when the data exists only in your head or on scraps of paper: a month of cash purchases, small shop bills, a trip diary. Use statement upload when the data already exists as a file, because a file is exact and retyping it invites mistakes.
Why batches of ten?
Large pastes tempt assistants to skip lines, merge two rows or invent a missing date. Ten entries are small enough to check by eye in a minute. If one batch goes wrong, you redo ten rows, not a hundred.
A worked example with 25 cash entries
Say you kept a notebook of 25 cash purchases for the month. Split them into three batches: 10, 10 and 5. Add each batch yourself first. Say they total ₹2,940, ₹3,120 and ₹1,790. Grand total: 2,940 + 3,120 = 6,060, plus 1,790 = ₹7,850. After each batch, ask the assistant for the count and total of what it saved, and compare. After all three, the app's cash account should show 25 new rows and ₹7,850.
| Batch | Entries | Your total |
|---|---|---|
| 1 | 10 | ₹2,940 |
| 2 | 10 | ₹3,120 |
| 3 | 5 | ₹1,790 |
| All | 25 | ₹7,850 |
What should every line include?
- Date in day, month, year order.
- Amount, and currency if not rupees.
- Short payee name.
- The account, usually cash, so totals land in the right place.
- Category or the word 'unsure'.
Which checks catch most errors?
- Row count equals entries sent.
- Total equals your sum.
- No date lands in a different month by accident.
- No row went to the wrong account.
- No entry duplicates something already imported from a statement.
Possible duplicate imports are flagged in SpendixAI, and the Possible duplicate charges report lists the same amount to the same merchant within two days, which helps when a hand-entered item and a statement row describe the same payment.
What about the connection scope?
Adding entries needs more permission than reading. Connect with read-only first, and only grant a scope that allows changes when you are about to do a batch. When you finish, consider dropping back. You can disconnect at any time. Because the assistant provider sees what you type, leave out names and identifiers that do not need to be in an expense description.
What should you do about categories?
Decide categories before you start, not during. List the five or six you actually use, such as Groceries, Transport, Eating out, Household, Medical and Other, and tell the assistant to use only those. If it invents a new name like Misc food, the report splits one habit across two labels, which makes month-to-month comparison harder. Anything the assistant cannot place should be tagged as unsure, and you resolve those yourself after the batch, with the receipt or your memory in front of you.
What if you have hundreds of rows?
Hundreds of rows usually exist already in a file. Get a statement export from your bank, upload it with the right account selected, review the rows and save. If the data is in an old spreadsheet, tidy the columns to date, description, amount and save as CSV, then upload that. Keep chat for the stragglers. A good split is files for history and chat for the cash you carried in your pocket.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


