Cards and UPI

UPI collect request vs pay: how each appears in your records

UPI collect request vs pay: how each appears in your bank records and why a collect request you approve is just a normal debit in your tracker.

Editorial illustration for UPI collect request vs pay: how each appears in your records

A UPI collect request and a UPI pay look the same once the money has moved: both are a debit from your account to the other party. The difference is only who started it. With pay, you initiate the payment. With collect, the other side asks for money and you approve it, so your tracker should treat an approved request as an ordinary expense.

What is the practical difference?

AspectPayCollect request
Who starts itYou, by scanning, picking a payee or entering a handleThe other party, who raises a request to you
What you doReview and authorise the paymentReview the request, then approve or decline it
Money moves whenYou authoriseYou approve
Shows in your records asA debit to the payeeA debit to the payee, once approved
If you ignore itNothing is sentThe request lapses without a debit

Whether a given app still offers collect requests, and for which kinds of payments, has changed over time and differs between apps. Look at your own app's screens to see what is currently available.

How does a collect appear in your statement?

As a normal debit on the day you approved it. The narration may look no different from a pay, or may carry a different code. Do not expect your statement to separate the two. If the other party tells you a request is coming, match it to the statement row by amount and date, not by narration.

What do you do with it in your tracker?

  1. Treat it like any other expense: record the date, amount and payee, and give it a category.
  2. Use the payee name from the request, because that name explains the debit better than the narration does.
  3. If the request is for a recurring bill, note it in your list of regular payments so that you spot the next one.
  4. Ignore declined or expired requests, because no money moved.

For instance, say a dairy sends you a request for ₹1,260 on the first of the month, and you approve it. Your record is simply one debit of ₹1,260 to the dairy under Groceries. There is no separate category called collect.

Why is it worth being careful with collect requests?

Because approving one sends money out. Your UPI PIN is needed only when money leaves your account. If someone asks you to approve a request in order to receive money, something is wrong, so decline it and stop. A genuine refund arrives in your account without you approving anything. Always read the payee name and amount on the approval screen, even when the request comes from someone you know.

A worked month with three requests

Say three requests reach you in a month. A dairy asks for ₹1,260 and you approve it. An electricity biller asks for ₹2,100 and you approve it. A stranger asks for ₹4,999, and you decline it. Your records should show two debits, ₹1,260 and ₹2,100, a total of ₹3,360, and nothing at all for the third. If your statement ever shows the ₹4,999, that is a reason to contact your bank straight away.

Does SpendixAI treat them differently?

No. SpendixAI works from your bank or card statement, so an approved collect request arrives as one debit like any other and is categorised by your rules, your history or, if you have switched AI on, an AI model for what is left. Correct it once and the correction becomes history. If you ever see two near-identical debits after approving a request twice, the Possible duplicate charges report is where to check.

Quick checks each month

  • Debits to payees you do not recognise, which may be a request you approved in a hurry.
  • Recurring requests from the same biller, to confirm the amounts match your bills.
  • Any request from a stranger that you declined, to be sure no debit followed.
SPENDIXAI JOURNAL

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

Explore your reports