Retrieve UPI Transaction Data — RRN, Amount, and Status — from Any UPI Screenshot
Most tools treat UPI as a single app — but UPI is India's universal payment protocol, embedded inside PhonePe, GPay, Paytm, BHIM, and dozens more. This extracts the four standard UPI confirmation fields from any app's screenshot in under 10 seconds — 18x faster than typing each field by hand.
5-10s per screenshot · Up to 99% accuracy on printed text
Four Fields That Every UPI Confirmation Screen Shares
Whether the screenshot comes from PhonePe, GPay, Paytm, BHIM, or CRED, the underlying UPI standard defines the same four data fields. With Custom Column Extraction, the AI reads the label beside each value — not its pixel position — so a PhonePe confirmation and a Paytm receipt land in the same spreadsheet columns.
The 12-digit alphanumeric Retrieval Reference Number assigned by NPCI to every UPI payment. This is the universal reconciliation key — the single number your bank needs to trace a transaction. Different apps label it differently: "UPI Ref No" on PhonePe, "Transaction ID" on GPay, "UTR Number" on Paytm.
The Rupee figure with Indian lakh/crore comma placement — Rs 1,50,000 means 1.5 lakh, not 150,000. The AI reads the numeric value, not the comma string, so Excel calculations work without manual correction.
The virtual payment address in user@bankhandle format — e.g., name@ybl (Yes Bank), name@paytm, name@oksbi (SBI), name@okhdfcbank (HDFC). The suffix reveals the payment service provider linked to the recipient's bank account.
The transaction result — Success, Pending, or Failed. Critical for reconciliation: only confirmed payments should be matched against bank statements, and pending transactions can flip to either state.
UPI Is Not an App — It's a Protocol. The Extraction Shouldn't Care Which App You Used.
Every UPI payment — whether sent through PhonePe, GPay, Paytm, BHIM, or CRED — generates the same four standard fields. The challenge is that each app renders them in a different layout, with different labels, and sometimes different names for the same field.
"I have to extract data from the payment screenshots like GPay, PhonePay, Paytm, etc., and after extracting, I have to make an Excel to store all the details like sender name, date, time, amount, etc. After doing this, I have to match the payment transactions with the bank statement. Sometimes it changes the date and time, or even sometimes it doesn't reads amount."
— Keshav, on the UiPath Community Forum, describing the struggle of reconciling UPI screenshots from multiple apps against bank statements
Same Field, Three Different Labels Across Apps
The 12-digit NPCI transaction reference is called "UPI Ref No" on PhonePe, "Transaction ID" on GPay, and "UTR Number" on Paytm. A user who doesn't know these are the same field may extract the wrong identifier — or extract both, unsure which one the bank needs for a dispute.
P2P, P2M, and Collect Requests — Three Different Screen Layouts
A person-to-person transfer shows the recipient's name and UPI ID. A merchant QR payment shows the store name. A collect request says "Request from" instead of "Paid to." Each layout places the same four fields in different positions, with different surrounding labels.
Indian Numbering Stops Standard CSV Parsers Cold
Rs 1,50,000 uses commas after the hundreds place (1,50,000) instead of after the thousands (150,000). A generic OCR pipeline passes the comma string through, so Excel sees text, not a number. The same problem affects crores: Rs 1,00,00,000 = one crore.
UPI-Aware Extraction Recognises the Field by Its Role
The AI understands that "UPI Ref No", "Transaction ID", and "UTR Number" all refer to the same NPCI-level reference. Define a single column called UPI Transaction ID — the AI reads the label context and extracts the 12-digit code regardless of how the app labels it.
Semantic Positioning Works Across All Transaction Types
The AI identifies the four UPI fields by their semantic relationship, not by pixel coordinates. It finds the 12-digit reference at the bottom of a GPay card or beside "UPI Ref No" on PhonePe with equal reliability. A P2P transfer, merchant QR, and collect request all resolve to the same column set.
Indian Commas Interpreted as Numeric Values
The AI reads the actual numeric value of the amount, not the comma string. Rs 1,50,000 is extracted as 100,000 — the Indian lakh notation is understood natively, and the output lands in Excel as a clean number rather than a text string that needs manual reformatting.
From a Mixed Folder of UPI Screenshots to One Clean Spreadsheet
If you are reconciling UPI payments from multiple apps, here is how a single batch handles all of them.
Upload the Screenshots
Drop in a folder of UPI confirmation screenshots — some from PhonePe, a few from GPay, one from Paytm, another from BHIM. Native screenshots or photos of the screen both work. The AI reads the UPI fields directly from the confirmation card regardless of the app's visual skin.
Name the Columns Once
Define four columns: UPI Transaction ID, Amount, UPI ID, Status. The AI reads the label context on each screenshot — the 12-digit code beside "UPI Ref No" (PhonePe), "Transaction ID" (GPay), or "UTR Number" (Paytm) all land in the same column. Add an Inferred Column like App Source (options: PhonePe/GPay/Paytm/BHIM) to track which app each screenshot came from.
Export the Unified Spreadsheet
The output is a single XLSX or CSV file — one row per screenshot, regardless of which app it came from. The UPI Transaction ID column contains the 12-digit RRN for every row, ready for VLOOKUP against your bank statement. Amounts are parsed as clean numbers with Indian lakh/crore notation resolved. Export to Excel, CSV, or push directly into Google Sheets via the add-on.
When UPI Screenshot Extraction Works Best — and When It Doesn't
When It Works Best
Standard UPI confirmation screens from PhonePe, GPay, Paytm, BHIM, or CRED. All four fields are machine-rendered with high contrast — the 12-digit RRN, the amount, the UPI ID, and the status label are consistently readable.
Batch processing across multiple UPI apps. One column set extracts from PhonePe, GPay, Paytm, and BHIM in a single batch — all rows merge into one spreadsheet with consistent headers.
Reconciliation and expense tracking. The 12-digit UPI Transaction ID is the universal key across the NPCI network — matching screenshots against bank statements becomes a straightforward VLOOKUP on the RRN column.
When to Be Cautious
Heavily compressed screenshots forwarded through messaging apps. WhatsApp compression can blur the 12-digit RRN, especially the smaller font size at the bottom of the confirmation card. Use direct screenshots when possible.
Banking app screenshots that show the UPI transaction. Some Indian banking apps embed UPI transaction details inside their own UI — the layout differs significantly from standard UPI app confirmation screens and may reduce accuracy.
Pending or failed transactions with provisional data. A pending status may show estimated amounts that don't match the final settlement. Confirm the Status field shows "Success" before relying on the data for reconciliation.
Frequently Asked Questions
Which identifier from a UPI screenshot should I use for a bank dispute — the UPI Transaction ID (RRN) or the app's internal Transaction ID?
The UPI Transaction ID (also called RRN — Retrieval Reference Number, or UTR) is the 12-digit universal reconciliation key assigned by NPCI to every UPI payment. This is the number your bank needs to trace and dispute a transaction. Each app also shows its own internal Transaction ID (alphanumeric, often longer), but banks cannot look up app-specific IDs. The AI extracts both when you define separate columns — UPI Transaction ID and App Transaction ID — so you always have the correct reference ready for disputes.
Can I batch UPI screenshots from different apps — PhonePe, GPay, Paytm, and BHIM — in the same export?
Yes. Define one column set — Amount, UPI Transaction ID, UPI ID, Status — and the AI processes UPI screenshots from any app in a single batch. Every UPI confirmation screen shares the same underlying fields regardless of the app's visual skin. The output merges into one spreadsheet with consistent headers, so you can reconcile payments from PhonePe, GPay, Paytm, and BHIM side by side. See the payment screenshots overview for the full cross-app capability.
Can I extract data from a UPI collect request screenshot, not just a payment confirmation?
Yes. A collect request screen shows the same four UPI fields — the UPI Transaction ID, Amount, UPI ID of the requester, and Status (often pending until you approve). The key difference is the label: instead of "Paid to", the screen says "Request from" followed by the requester's name or UPI ID. The AI reads the label context and identifies the UPI ID under "Request from" as the payee, so the same column set works for both payment confirmation and collect request screenshots.
How does the tool handle Indian numbering like Rs 1,50,000 (1.5 lakh) on UPI screenshots?
The AI reads the Rupee value as a single numeric figure, not a comma-separated string. Rs 1,50,000 (one lakh fifty thousand) is extracted as 150,000 — the Indian comma placement after the hundreds is understood natively, so the output lands in Excel as a clean number without manual correction. For crores (Rs 1,00,00,000 = 10 million), the same logic applies.
What does the UPI ID suffix (@ybl, @paytm, @oksbi) tell me — is it useful for reconciliation?
The UPI ID suffix reveals the payment service provider (PSP) that handles the transaction for the recipient. For example, name@ybl means the recipient uses Yes Bank, name@oksbi means State Bank of India, name@paytm means Paytm Payments Bank, and name@okhdfcbank means HDFC Bank. This is useful for reconciliation because it tells you which bank ultimately received the funds — even if the sender used a different app to send the payment. The UPI Transaction ID (RRN) is the primary key for matching transactions, but the UPI ID suffix helps verify that the funds landed in the correct bank account.
From the parent Hub: Extract data from any payment screenshot — PhonePe, GPay, Paytm, BHIM, and more
Also from this Hub: PhonePe screenshot field guide · Google Pay India screenshot field guide
Paytm screenshot field guide — another UPI app with Wallet, UPI, and Card payment sources