Dozens of UPI screenshots in your gallery are evidence, not records. To turn them into entries, sort them by date, match each to a line on your bank statement, and type only the few that the statement does not explain. Do not try to retype every screenshot; the statement will do most of the work.
Why screenshots pile up and then stall
Gig workers pay and get paid in small, frequent UPI transfers: fuel for a delivery shift, a platform's weekly settlement, a helper's daily wage. A screenshot feels like a quick receipt. Weeks later there are ninety of them, no order, and nobody wants to type them.
Step 1: count and sort before you type
- Open the gallery and select the screenshots in one month.
- Sort them oldest to newest.
- Delete obvious duplicates, such as two shots of the same confirmation.
- Make three groups in separate albums: money you paid for work, money you received for work, personal payments.
- Leave the personal group alone.
Resist the urge to retype before you sort. Typing ninety entries feels like progress but leaves you with ninety unchecked numbers. Sorting first tells you how many actually need a human, and for most months the answer is a handful.
Step 2: let the statement carry the weight
Download your bank statement for the same month as PDF, CSV or Excel. Every successful UPI payment will be a line there with a date and an amount. Tick each statement line for which you have a work screenshot. This gives you a complete list without any typing.
SpendixAI takes statements in these formats, lets you choose the account before importing, and shows rows for review before saving. It does not read SMS and is not linked to your UPI app, so the statement is your source. Screenshots can be kept with transactions as receipts.
What do I do with the payments the statement cannot explain?
Cash tips, a payment through someone else's account, or a refund shown in a different month will not match neatly. Make a short list called leftovers. For each, write the date, amount, who, and why, from the screenshot if you have one.
A worked example with made-up figures
| Group | Count | Total |
|---|---|---|
| Fuel for delivery shifts | 14 | ₹6,300 |
| Helper's daily wage | 8 | ₹4,800 |
| Platform payouts received | 4 | ₹38,500 |
| Phone recharge | 1 | ₹299 |
| Leftovers with no statement match | 3 | ₹1,150 |
Costs for work are 6,300 plus 4,800 plus 299, which is ₹11,399, with a further ₹1,150 awaiting explanation. Against payouts of ₹38,500, you can see roughly what the month kept: 38,500 minus 12,549, which is ₹25,951, before anything personal.
Gig income is uneven, so keep a running total of payouts for the month beside the costs. When payouts drop in a slow week, the costs of fuel and helpers do not, and seeing both on one page is what tells you whether the week paid for itself. A simple two-column note is enough to start.
Make next month easier
- Rename or album each screenshot the day you take it.
- Set a weekly ten-minute slot to match the week's screenshots to statement lines.
- Add cash spends by hand in a batch rather than one by one.
- Use the possible-duplicates view, if your tool has one, before totalling.
If the backlog is already huge, do not aim for perfection. Start with the most recent month, finish it, and see how long it took. Then decide whether older months deserve the same effort or only a summary total from the statement. A finished recent month is more useful than five half-sorted ones.
Useful ideas start with a clearer picture of your own spending.
Explore your reports
