Locate the Amount, PayID, and Osko Status from an Australian PayID / Osko Screenshot
Most payment tools work on tables or forms — an Australian PayID/Osko screen buries the same 3 fields inside a dual-identifier system that doesn't exist outside Australia. This one reads them by meaning in under 10 seconds.
5-10s per screenshot · Up to 99% accuracy on printed text
What You Can Extract from a PayID / Osko Confirmation Screen
An Australian payment confirmation isn't a table — it's a single screen carrying the same NPP data rendered differently by every bank. With Custom Column Extraction, you name the fields you need; the AI locates each value by understanding what the label means, not where the bank positioned it.
The dollar figure in Australian format — may appear as "Amount", "Debit Amount", or "Transaction Amount" depending on the bank app. The AI isolates the payment value from any fees shown on the same screen.
The recipient identifier — could be a mobile number (0412 345 678), an email address ([email protected]), or an ABN. Unlike BSB+Account, the PayID is what the sender sees as the destination. The AI reads whatever form the PayID takes.
The Osko-specific text fields — a 280-character Description (supports emojis) and a 35-character End-to-End ID for invoice numbers. The AI captures whatever the sender typed, preserving invoice references and payment purposes.
The Same NPP Data, Rendered Differently by Every Australian Bank
Every PayID/Osko payment runs through the New Payments Platform — the same backend sends the same data. But CommBank, Westpac, NAB, and ANZ each display it in a completely different layout, and no two apps put the 3 fields in the same screen position.
The PayID Replaces the Account Number
Outside Australia, a bank transfer shows "BSB: XXX-XXX Account: XXXXXX" — a format every extraction tool expects. An Australian PayID screen shows a mobile number or email where the account number should be. Generic OCR tools flag it as noise or misclassify it as a contact field.
"Within a Few Minutes" Is Not a Status
Venmo and PayPal show "Completed" or "Pending" as a label. Osko shows a message: "Your payment will be processed in less than a few minutes." Marketplace sellers on r/AusFinance regularly report that "a screenshot is not payment" after buyers disappear before the Osko transfer lands.
No Two Banks Put the Same Label in the Same Place
CommBank places the amount at the top of a green confirmation bar. Westpac uses a white card layout. NAB wraps the Osko reference inside a collapsed section. A template trained on one bank fails on the next three.
The PayID Is Recognized by Role, Not Format
The AI identifies the PayID as the payment destination — whether formatted as an Australian mobile (0412 345 678), an email address, or an ABN. It reads the label as context, not a rule. One column extracts any identifier form.
Osko Status Reads the Confirmation Message
Define a "Status" column, and the AI reads whichever message the screen displays — the pre-settlement "within minutes" notice or the post-settlement confirmation. The Osko logo becomes a visual anchor: with a time estimate the payment is pending; with a checkmark it's complete.
One Column Set Covers Every Australian Bank
CommBank, Westpac, NAB, ANZ, and 90+ participating institutions — the same three column definitions (Amount, PayID / Recipient, Reference) produce a unified spreadsheet without template changes between banks.
From an Osko Payment Screen to a Clean Row in One Pass
If you're logging incoming PayID payments — Marketplace sales, freelance invoices — here's what happens when you drop the confirmation screenshot into the tool.
Upload the PayID / Osko Confirmation
Drop the screenshot — from your gallery, a forwarded message, or a client's email. Whether it's a CommBank green status bar, a Westpac white card layout, or an NAB screen with the Osko reference collapsed. JPG, PNG, or WebP, no cropping needed.
Type Three Columns — Amount, PayID, Reference
Define Amount, PayID / Recipient, Reference. The AI reads each bank's layout independently — it isolates the dollar figure regardless of label, recognizes a mobile or email as the PayID, and captures the Description or End-to-End ID.
Download a Unified Payment Log
Processing takes 5-10 seconds per screenshot. The output is a single XLSX — one row per payment, the three columns you defined, consistent across all Australian banks. Roughly 18x faster than opening each confirmation and typing the fields by hand (~90s manual vs ~5s here).
What three columns produce, across any Australian bank:
| Amount (AUD) | PayID / Recipient | Reference |
|---|---|---|
| $85.00 | 0412 345 678 | Marketplace — coffee table |
| $1,250.00 | [email protected] | INV-2026-089 |
| $340.50 | ABN 12 345 678 901 | Consulting — July |
PayID Screenshot Extraction Limits — When It Nails It and Where to Double-Check
Understanding these boundaries helps you get consistent results from PayID / Osko confirmation screenshots.
When It Works Best
Direct screenshots from any Australian banking app. Machine-rendered text on confirmation screens from CommBank, Westpac, NAB, ANZ, and 90+ participating institutions — up to 99% accuracy on printed fields.
Batch processing across multiple banks. One set of three columns handles PayID screenshots from different Australian banks in a single batch — no bank-by-bank sorting.
Regular payment logging or reconciliation. Processing 10-30 PayID confirmations per month replaces manual data entry with a single export.
When to Be Cautious
Compressed or forwarded screenshots. If a client forwards a confirmation via WhatsApp or Messenger, image compression reduces character-level accuracy — particularly for long PayID references and ABNs.
Mixed PayID and standard bank transfer screenshots. BSB+Account transfers and PayID screenshots look similar — separate them into different batches or add a "Payment Method" column to distinguish them cleanly.
Screenshot status ≠ settlement status. An Osko confirmation screen showing "payment sent" does not guarantee funds have settled. The AI extracts what the screen displays, not the actual bank settlement state — always verify received funds before dispatching goods.
Frequently Asked Questions
The PayID on the screenshot shows as a phone number — is that the account number or something else?
That phone number is the account identifier in Australia's New Payments Platform. Unlike a BSB+Account transfer where you see a 6-digit BSB and a 6-9 digit account number, a PayID payment uses a mobile number, email address, or ABN as the destination. The AI recognizes this field by its role as the payment recipient — whether it reads "0412 345 678", "[email protected]", or "ABN 12 345 678 901". Define a column called PayID / Recipient, and the AI extracts whichever identifier form the screen shows, alongside the recipient name if the bank displays it.
Can the AI tell whether the Osko payment is pending or completed from the screenshot?
Yes. Osko confirmation screens display a status message — typically "Your payment will be processed in less than a few minutes" when the transfer is initiated but not yet settled, or a confirmation notice once the funds have arrived. The AI reads this message and any visible Osko logo or checkmark on the screen. Define a Status column, and it extracts whichever label is visible. Because Osko payments can take a few minutes to settle, the screenshot status reflects what the sender's app shows, not necessarily whether the money has landed in your account — always check your own transaction history before releasing goods.
Can I process PayID/Osko screenshots alongside Venmo, PayPal, and Zelle in the same batch?
Yes, with one adjustment. PayID/Osko screenshots use different identifier fields (mobile/email/ABN) than US payment apps (username, $cashtag). Define a broader column set like Amount, Recipient / PayID, Reference that covers both AU and non-AU payment types, or keep them in separate batches with app-specific column names for cleaner output. The AI adapts its reading to each screenshot's actual content regardless.
The screenshot shows "Description" with 280 characters — can the AI extract the full text including emojis?
Yes. Osko's Description field supports up to 280 characters of free text, including emojis and special characters. The AI preserves the exact text visible on the screenshot — whether it's an invoice reference like INV-2026-089, a casual note like coffee ☕ thanks!, or an End-to-End ID like REF42831. Define a Reference column, and the full visible text lands in your spreadsheet.
How is AU dollar formatting handled — does the AI correctly read "$1.500,00" vs "$1,500.00"?
Australian banks conventionally use the same thousands/decimal formatting as US banks (period as decimal: $1,500.00), but some bank apps display amounts without punctuation or with bank-specific spacing. The AI reads the numeric value as it appears on screen and preserves the original string in the extracted cell. If you need a standardized numeric format for calculations, the Computed Column feature can normalize the amount during extraction — define a column like Amount (Normalized) with a formatting rule, and the AI outputs a clean number ready for spreadsheet math.
See all supported payment confirmation types — PayID/Osko alongside Venmo, PayPal, Zelle, and more: Back to payment screenshots overview
The Osko payment status problem explained in depth: Why a screenshot isn't the same as a settled payment — reconciliation across payment platforms