Get the Amount, Reference Number, and Sender from a GCash Screenshot
Extract 4 key fields — amount, reference number, sender or store name, and date — from any GCash confirmation screen, whether it's Send Money, Pay QR, or Bills Payment. The reference number is the one universal identifier present across every transaction type.
5-10s per screenshot · Up to 99% accuracy on printed text
What You Can Pull from a GCash Screenshot
Any GCash confirmation screen carries the same five fields regardless of transaction type. With Custom Column Extraction, define the columns you need — the AI locates each value by understanding what the field means, not where it sits in the layout.
| Amount | Reference No. | Sender / Store | Date | Type |
|---|---|---|---|---|
| ₱1,250.00 | MRCJ20240714123 | Juan D. / Mercury Drug | Jul 14, 2026 | Send Money |
A Universal Reference Number — Across Four Changing Layouts
A GCash confirmation screen looks simple. The catch is that Send Money, Pay QR, Bills Payment, and Buy Load each render a different layout, even though they share the same core fields. Template-based tools need separate configurations for each — which defeats the purpose when you're reconciling mixed transaction types.
Four Layouts, One Reference Number
The reference number appears on every GCash confirmation screen, but its position and format shift between transaction types. A template tool configured for Send Money won't find it on a Pay QR receipt — and a developer on Reddit manually parsing these with Tesseract OCR reports the same text blocks land in different coordinates depending on the layout.
Two Identities in One Field
"Received from" shows a personal GCash-registered name for person-to-person transfers and a store or business name for merchant QR payments. Same field label, two completely different categories of data — and your record-keeping needs to distinguish between them.
No Batch Export for Individuals
GCash offers CSV export only to Business account holders. Individual users — freelancers, sari-sari store owners, online sellers — are left manually screenshotting each confirmation or, as one cashier observed, writing reference numbers into a physical logbook.
Semantic Reading Spans All Layouts
Define Reference Number once — the AI locates it on Send Money, Pay QR, Bills Payment, and Buy Load screens alike, because it reads the label text, not the pixel coordinate. No per-type configuration needed.
Auto-Classification with an Inferred Column
Add an Inferred Column named Transaction Type (Send Money / Pay QR / Bills Payment / Buy Load). The AI reads each screenshot and classifies it automatically — so a row showing "Mercury Drug" in the sender column is clearly a Pay QR payment, not a person-to-person transfer.
Batch Processing Closes the Export Gap
Upload 50 GCash screenshots across all transaction types at once. The AI processes every layout variant with a single column definition, and the output lands as one unified Excel sheet — rows sorted, types classified, amounts summed.
From Mixed GCash Screenshots to a Single Spreadsheet
If you're reconciling a day's worth of GCash payments — QR sales mixed with direct transfers and bill payments — here's how they all end up in one table, no per-type sorting required.
Upload the Mixed Batch
Drop any combination of GCash confirmation screenshots — Send Money transfers, Pay QR receipts, Bills Payment acknowledgments — into a single upload. The tool doesn't need them sorted by type because the AI reads content, not layout.
Name the Columns
Define five column headers: Amount, Reference Number, Sender / Store, Date, and an inferred Transaction Type (Send Money / Pay QR / Bills Payment / Buy Load). One set of definitions covers every layout — no per-type presets required.
Export the Consolidated Table
The output lands as a single spreadsheet — one row per screenshot, five columns, every transaction type consolidated. Export to Excel, CSV, or push directly into Google Sheets via the add-on. No more flipping between screenshots to match payments to a logbook.
When GCash Screenshot Extraction Works Best — and When It Doesn't
When It Works Best
Clear screenshots from the GCash app. Direct confirmations from Send Money, Pay QR, Bills Payment, and Buy Load screens where text contrast is stable and elements are well-spaced.
Mixed-type batch processing. One column definition handles Send Money, Pay QR, and Bills Payment screenshots in the same upload — no per-type sorting required.
Daily reconciliation at volume. Processing 20-50 GCash payments per day replaces manual screenshot-by-screenshot transcription with a single export.
When to Be Cautious
Cropped or forwarded screenshots. Messaging apps compress GCash screenshots and may crop the reference number area. When possible, capture from the GCash app directly.
Old app UI variants. Pre-2025 GCash layouts shift element positions. Semantic extraction still reads labels, so accuracy holds — but verify the first few rows when processing very old screenshots.
Pending transaction screens. A transaction still showing "Processing" may lack finalized field values. Wait for the confirmed status screen before extracting.
Frequently Asked Questions
Can I extract the GCash reference number from every transaction type?
Yes. The Reference Number is the one identifier that appears on every GCash confirmation screen — Send Money, Pay QR, Bills Payment, and Buy Load all display it. Define a column named Reference Number or Ref No. and the AI locates it by reading the label, not the position, so format variations between transaction types don't affect accuracy.
Why does the "Sender" field show a person's name on one screenshot and a store name on another?
GCash handles two distinct scenarios. Send Money transfers between users show the sender's GCash-registered name. Pay QR payments to merchants display the store or business name in the same position. Define a single column as Sender / Store — the AI returns whatever identifier is visible. Adding the inferred Transaction Type column clarifies which scenario each row belongs to.
Does the extraction work with GCash screenshots taken in dark mode?
Yes. The AI reads text by semantic meaning, not pixel color, so inverted backgrounds don't affect recognition. Dark mode screenshots from recent GCash app versions produce the same accuracy as light mode — provided the screenshot is a direct, clear capture from the app rather than a forwarded copy through a messaging platform.
How do I handle the ₱ symbol when extracting amounts?
Define a column named Amount or Amount (₱) — the AI extracts the numeric value regardless of whether the peso sign is visible. The output uses the raw numeric value so you can sum, filter, or convert currencies in Excel without cleaning the data first.
Can I batch GCash screenshots with Venmo or PayNow screenshots in the same export?
Yes. Define a unified column set — Amount, Reference Number / Transaction ID, Sender, Date — and the same definitions apply to GCash, Venmo, PayNow, and KakaoPay screenshots in a single batch. Each screenshot becomes one row regardless of which app generated it, making cross-platform reconciliation possible in one export. See the payment screenshots hub for the full list of supported apps.
Why the GCash reference number is the one field you should never skip: it's the only transaction ID that's universally present across every GCash transaction type
Sibling comparison: how KakaoPay handles the same chat-app-embedded payment challenge differently: KakaoPay screenshot extraction
Sibling comparison: PayNow (Singapore) — another Asian mobile payment system with a similar confirmation screen pattern: PayNow screenshot extraction
Back to payment screenshots overview — see all supported payment apps