Extract Amount, UPI Transaction ID, and Note from Any Google Pay India Screenshot
Reading a Google Pay confirmation and typing the amount, UPI transaction ID, UPI ID, and note into a spreadsheet takes about 3 minutes per screenshot. This pulls all four fields from any Google Pay India screenshot in 5-10 seconds.
5-10s per screenshot · Up to 99% accuracy on printed text
What You Can Extract from a Google Pay India Screenshot
A Google Pay India confirmation screen shows several similar-looking values: a large Rupee amount, a payment handle, a long reference number, and whatever note was typed. The hard part is knowing which value means what. Name the columns you want, and the AI locates each field by understanding its semantic role, not its pixel position.
The largest Rupee figure on the confirmation screen. Google Pay uses Indian numbering, so ₹1,50,000 means 1.5 lakh, and basic OCR tools often misread it as separate values.
The 12-digit UPI transaction ID (also called the UTR) shown with the payment details. This is the primary reconciliation key, the number that ties a screenshot to a line on your bank statement.
The payment handle (e.g., name@okhdfcbank, name@oksbi). The suffix reveals the recipient's bank, which helps when you reconcile payments across multiple accounts or verify that funds went to the right institution.
The free-text field you type when sending a payment carries the real transaction purpose: "rent", "lunch split", "EMI for bike", "college fee". For Indian users tracking expenses across categories, this is often the most useful field on the screen.
Why a Google Pay Confirmation Screen Is Trickier Than It Looks
The confirmation screen looks simple, but three things make it harder to extract than a standard receipt.
"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. Is it possible through UiPath Studio? I have tried a lot ... but it is not 100% accurate."
Keshav, on the UiPath Community Forum, describing the challenge of reconciling Google Pay screenshots with bank statements
Two similar references, only one is the bank key
A Google Pay confirmation carries several numeric values beyond the amount, and only one of them is the 12-digit UPI transaction ID your bank statement uses. Position-based OCR grabs whichever number it finds first, so the wrong value can end up in your reconciliation column.
Indian numbering breaks comma-separated value parsers
"₹1,50,000" means 1.5 lakh, but a standard CSV parser or regex tool sees three separate number groups. The AI understands the Indian grouping convention and extracts the full value as a single field, not three fragments.
UPI terminology is invisible to generic OCR
A tool that doesn't know what "UPI transaction ID" or "UPI ID" means can't tell them apart. One is a 12-digit, transaction-level key; the other is a bank-linked handle. The AI understands the semantic difference.
The 12-digit UPI transaction ID is identified by its role
Custom Column Extraction reads the label beside each value rather than its position. It recognises the 12-digit UPI transaction ID for what it is, so the number your bank can look up lands in the right column even when other values sit nearby.
Indian number formats are parsed as a single value
The AI recognises the Indian numbering convention natively. "₹1,50,000" is extracted as one amount field, not as "₹1", "50", and "000". You can also define a Computed Column to normalise the output to a standard numeric format during extraction.
UPI ID and transaction ID are identified by role
Define columns called "UPI ID" and "UPI Transaction ID". The AI reads the confirmation screen, recognises which value is the bank-linked handle and which is the 12-digit transaction reference, and places each in the correct column. No manual labelling required.
A Folder of Google Pay Confirmations vs One Batch
Open the screenshot. The amount is the large Rupee figure, but it reads "₹1,50,000" and you have to decide whether to type it as "150000" or "1,50,000". The UPI transaction ID is a 12-digit number like "123456789012", easy to mistype. The UPI ID reads "user@okhdfcbank", and you have to work out which bank that is. The note says "rent for July", and you have to decide whether you need it in your records. Each screenshot takes about 3 minutes of reading, deciding, and typing. A month of Google Pay payments adds up fast.
Upload all your Google Pay screenshots into one batch. Type four column names: Amount, UPI Transaction ID, UPI ID, Note. The AI reads every screenshot at once: it identifies the large Rupee figure as the Amount, extracts the 12-digit UPI transaction ID, captures the UPI handle with its bank suffix, and pulls the free-text note. That is 5-10 seconds per screenshot, up to 18x faster than typing each field by hand. The output is a single XLSX, one row per payment, ready for bank reconciliation.
When It Works Best and When to Be Cautious
Understanding these boundaries helps you get the best results from Google Pay India screenshots.
When It Works Best
Direct device screenshots from the Google Pay app. Machine-rendered text has excellent contrast, with up to 99% accuracy on printed Rupee values and labels.
A consistent Google Pay layout. The confirmation screen follows a steady structure across payments, and the AI identifies each field by its semantic relationship rather than by fixed pixel position.
Batch processing across UPI payment apps. One column set handles Google Pay alongside PhonePe, Paytm, and BHIM UPI in the same batch, and everything merges into one spreadsheet.
When to Be Cautious
Compressed screenshots forwarded through messaging apps. Google Pay's text is machine-rendered, but heavy compression can blur smaller elements such as the 12-digit UPI transaction ID.
Dim or low-brightness screenshots. Low contrast makes small text, such as the 12-digit UPI transaction ID, harder to read. Bump the brightness before capturing.
Screenshots that hide the details. Recent Google Pay privacy updates can leave the UPI ID, the recipient's name, or the transaction ID off a plain screenshot. Open the transaction from history, or use the app's receipt-share option, to capture a version that shows the fields you need.
Frequently Asked Questions
Can I extract both the UPI ID and the UPI Transaction ID from one Google Pay screenshot?
Yes. Define columns for both UPI ID and UPI Transaction ID in the same column set. The UPI ID appears as the payment handle (for example, name@okhdfcbank), and the UPI transaction ID is the 12-digit code shown with the payment details. The AI identifies each by its semantic role, not its position, so you get both fields in the same row without conflict.
How does the tool handle Indian numbering like ₹1,50,000 (1.5 lakh)?
The AI reads the Rupee value as displayed, including Indian-standard grouping with commas at the thousand, lakh, and crore positions. A value displayed as ₹1,50,000 is extracted exactly as shown. You can then convert it to a standard numeric format in Excel, or use a Computed Column to normalise the output during extraction by defining a column such as Amount (Normalised) with a rule to strip commas and output a plain number.
Does a Google Pay screenshot always show the UPI ID and transaction ID?
Not always. Recent Google Pay privacy updates can leave the UPI ID, the recipient's name, or the transaction ID off a plain screenshot, especially when the image is shared. Open the transaction from Google Pay's transaction history, or use the app's receipt-share option, to capture a version that includes the fields you need before uploading it.
Can I process multiple Google Pay screenshots in one batch to get a consolidated UPI payments log?
Yes. Upload all your Google Pay screenshots, or mix them with PhonePe, Paytm, and BHIM UPI screenshots, into a single batch. Define the same column set once, and the AI processes every screenshot in the queue. The output is one unified Excel file with each row representing one payment, regardless of which UPI app the screenshot came from.
What's the difference between the UPI transaction ID and the UPI ID, and which one do I use for bank reconciliation?
The UPI ID (for example, user@oksbi) is the payment handle linked to the recipient's bank account, and the oksbi suffix tells you the bank is State Bank of India. The UPI transaction ID is the 12-digit reference assigned to that individual transaction, the same number that appears in your bank statement's UTR field. For bank reconciliation, use the UPI transaction ID: it is unique per payment and it is what your bank can trace. An app-generated transaction ID is a separate reference and is not a substitute, and the UPI ID only tells you who received the payment and at which bank.
From the parent Hub: Extract data from any payment screenshot: PhonePe, Paytm, GPay, and more
Also from this Hub: PhonePe screenshot field guide · Paytm screenshot field guide · the bank-agnostic UPI transaction ID guide