Grab the Amount, Merchant, and Reference ID from an OVO or DANA Screenshot
Manually matching OVO and DANA screenshots to your records takes 2-3 minutes per transaction. With custom column extraction, you get the same data in 5-10 seconds.
5-10s per screenshot · Up to 99% accuracy on printed text
What You Can Pull from an OVO or DANA Screenshot
OVO and DANA confirmations share the same four core fields — but they use different Indonesian labels and different layouts. With Custom Column Extraction, define the columns you need once and the AI locates the matching values on either app's screen by understanding what the field means, not where it sits.
| Amount (Nominal) | Merchant / Recipient | Reference ID | Date (Tanggal) |
|---|---|---|---|
| Rp150.000,00 | Indomaret / Budi S. | TRX240712ABC | 12/07/2026 |
Same Data, Two Different Apps, Three Payment Sources
OVO and DANA are Indonesia's two largest independent e-wallets — each with its own layout, and OVO further splits into three payment sources (Cash, Points, PayLater) that each produce a different confirmation screen. Template-based extraction would need four separate configurations for the same four fields.
OVO's Three Faces — Cash, Points, and PayLater
OVO offers three payment sources: OVO Cash (prepaid balance), OVO Points (loyalty rewards that offset payments), and OVO PayLater (BNPL credit). Each produces a different confirmation screen — the Points screen shows two values (IDR amount + Points used), while PayLater shows installment terms. One Indonesian Reddit user noted that "Indonesian is the only language OVO Pay uses," making screen navigation harder for non-Bahasa speakers.
DANA's Minimalist UI — Fewer Visual Anchors
DANA's confirmation screen is notably clean: the amount, recipient, and reference ID are spaced widely with minimal framing. Standard OCR tools that rely on bounding boxes or table structure detection struggle because there are no grid lines, no section headers — just a few lines of text on a white background. The field you need could be anywhere in the visual field.
Indonesian Number Format: The Silent Misread
Indonesian uses a period as the thousands separator and a comma as the decimal mark — the reverse of international convention. A DANA confirmation showing Rp1.500,50 is one thousand five hundred rupiah, not 1.50050. Standard OCR tools trained on U.S. formats routinely misread the period as a decimal point, producing values that are off by orders of magnitude.
One Column Definition Covers All Three OVO Sources
Define Amount once — the AI reads the IDR value on OVO Cash, OVO Points, or OVO PayLater screens alike. It distinguishes total from points-used by understanding label semantics, not by guessing position.
Semantic Reading Finds Fields on Any Layout
The AI locates Merchant / Recipient by understanding that "Penerima," "Tujuan," and "Merchant" all refer to the same logical field — the other party in the transaction. Whether it's a store name or a person's name, the same column works.
Indonesian Number Format Is Handled Natively
The AI treats period and comma in their Indonesian context — Rp1.500,50 is read as 1500.50, not 1.50050. Output normalizes to standard decimal notation for Excel formulas and pivot tables.
From Mixed OVO and DANA Screenshots to One Consolidated Spreadsheet
If you're reconciling payments from a week's worth of mixed OVO and DANA transactions — QR payments at Indomaret, transfers to friends, and Tokopedia orders — here's how they all end up in one table without sorting by app first.
Upload the Mixed Batch
Drop any combination of OVO and DANA confirmation screenshots into a single upload — OVO Cash payments, OVO Points redemptions, OVO PayLater installments, and DANA QR receipts all together. The tool doesn't need them sorted by app or payment source because the AI reads content, not layout.
Name the Columns
Define four column headers: Amount, Merchant / Recipient, Reference ID, and Date. One set of definitions covers every layout — OVO Cash, OVO Points, OVO PayLater, and DANA Balance — no per-source or per-app configurations needed.
Export the Consolidated Table
The output lands as a single spreadsheet — one row per screenshot, four columns, every transaction type consolidated. Export to Excel, CSV, or push directly into Google Sheets via the add-on. No more flipping between screenshots of different apps to match payments to your records.
When OVO and DANA Screenshot Extraction Works Best — and When It Doesn't
When It Works Best
Direct screenshots from OVO and DANA apps. Confirmation screens captured directly within the app provide the clearest text contrast and most reliable layout recognition.
Cross-wallet batch reconciliation. One column definition handles OVO and DANA screenshots in the same upload — plus GoPay, if you have all three Indonesian wallets in the same batch.
Mixed payment source processing. OVO Cash, OVO Points, and OVO PayLater screenshots can all be processed together with the same column definitions — no need to sort by payment source first.
When to Be Cautious
Forwarded or compressed screenshots. Messaging apps like WhatsApp compress OVO and DANA screenshots, potentially degrading text clarity. Capture directly from the payment app when possible.
Old app UI versions. Pre-2025 OVO and DANA layouts may differ from current versions. Semantic extraction still reads labels, so accuracy holds — but verify the first few rows when processing older screenshots.
Pending transaction screens. A transaction still showing "Diproses" (Processing) or "Menunggu" (Pending) may lack finalized field values. Wait for the "Berhasil" (Success) confirmation screen before extracting.
Frequently Asked Questions
Why does OVO show two amounts — Rp150.000 and Poin 150 — on the same confirmation screen?
OVO has a dual-currency system: OVO Cash (the real-money balance) and OVO Points (reward points that can offset payments). When a user pays with Points, the confirmation shows both the total amount and how many points were used. Define a column named Amount to capture the IDR value, or add a separate OVO Points column to capture the rewards portion separately.
Can I differentiate between OVO Cash, OVO Points, and OVO PayLater transactions?
Yes. Add an inferred column named Payment Source (OVO Cash / OVO Points / OVO PayLater / DANA Balance). The AI reads each screenshot and classifies the payment source automatically based on the labels and values visible on the confirmation screen — so you can filter or sum by payment type in your output spreadsheet.
Does the extraction handle the Indonesian comma-as-decimal format (Rp1.500,50)?
Yes. The AI reads number values semantically, so Rp1.500,50 is correctly interpreted as one thousand five hundred rupiah and fifty sen, not as 1.50050. The output normalizes the value to a clean numeric format ready for Excel calculations and formula work.
Why does the same field sometimes say "Penerima" and other times "Tujuan"?
OVO and DANA use different Indonesian labels for the same logical field depending on the transaction type. "Penerima" (Recipient) appears on person-to-person transfers, while "Tujuan" (Destination) or "Merchant" appears on QR payments to stores. The AI understands all three as referring to the other party in the transaction — define a single column as Merchant / Recipient and it captures the correct value regardless of the label used.
Can I batch OVO, DANA, and GoPay screenshots together in a single export?
Yes. Define a unified column set — Amount, Merchant / Recipient, Reference ID, Date — and the same definitions apply to OVO, DANA, and GoPay screenshots in one batch. Each screenshot becomes one row regardless of which app generated it, making cross-wallet reconciliation possible in a single export. See the payment screenshots hub for the full list of supported apps.
Sibling comparison: how GoPay handles Indonesian number format in the same market: GoPay screenshot extraction
Sibling comparison: how GCash handles the same multi-payment-source challenge in the Philippines: GCash screenshot extraction
Back to payment screenshots overview — see all supported payment apps