To fix 200 wrongly categorised rows quickly, do not open them one by one. Sort or filter so that similar rows sit together, change them in groups, and then teach your tool the rule so next month's import needs fewer fixes. Three or four passes usually clear the pile.
Why do gig workers get so many wrong rows?
A gig worker's statement is full of look-alike payments: platform payouts, fuel at the same few pumps, UPI payments to people with personal names, cash withdrawals and phone recharges. A tool that guesses from the merchant name will get the regular ones right and the personal-name transfers wrong, since a payment to a person can be rent, a helper's pay or a friend repaying you.
Pass 1: separate income from spending
Filter to credits first. Platform payouts, client payments and refunds go to income categories. Move everything else that is a credit, such as a friend's repayment, to a transfer or reimbursement category so it does not inflate earnings.
Pass 2: group by merchant
Sort the debits by merchant or description. Say 200 rows break down like this.
| Group | Rows | Right category |
|---|---|---|
| Fuel pumps | 64 | Fuel |
| Kirana and vegetable vendors | 41 | Groceries |
| Recharge and data | 9 | Phone |
| Cash withdrawals | 18 | Cash, to be split later |
| UPI to personal names | 46 | Needs checking one by one |
| Other | 22 | Review |
64 plus 41 plus 9 plus 18 plus 46 plus 22 equals 200. The first three groups hold 114 rows, more than half, and can be done in three bulk edits.
Pass 3: handle the awkward ones
- Personal-name UPI payments: open the ones above ₹1,000 first, since they matter most
- Cash withdrawals: leave them in a cash category and split once you remember what they covered
- Round-number payments: check whether they are rent, a helper or a loan repayment
- Repeated amounts to the same person: set them once and treat them as a pattern
SpendixAI's transactions support bulk edit and bulk delete, so selecting a group of rows and changing the category applies it in one action. Its categoriser also learns from your corrections, which become history, and you can add merchant aliases so one pump with three spellings lands together. Review the first month's result rather than trusting it blindly, since a statement layout can differ.
How do I stop it happening every month?
Fix the group once, add a rule for each repeating merchant, and the next import should arrive better sorted. For personal-name payments, a rule on the amount and the person is possible only if the pattern is stable; otherwise keep reviewing.
Do I need records for anyone else?
If a platform, a lender or your CA ever asks how much you spent on running costs, a clean category history makes it a two-minute answer. What counts as a business expense is for your CA to say.
Before you start, take a copy of your category totals, even just on paper, so you can compare after the edits. If the total for all categories together does not match the statement total, a bulk change went wrong somewhere, and it is easier to catch in the same sitting.
Do the work in short sessions. Fifteen minutes, two or three times, is better than an hour of fatigue in which you tag fuel as groceries. Stop each session by writing down which group you reached, so that you can pick up where you left off.
A tidy-up checklist
- Filter credits and sort them into income and transfers.
- Group debits by merchant and bulk edit the largest groups.
- Open the awkward ones, largest amounts first.
- Add rules or aliases for repeating merchants.
- Compare category totals with the statement total.
- Delete only after checking.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


