Extract the Amount, Beneficiary, and Narration from Any Nigerian Bank Transfer Screenshot
Manually typing the four fields from a Nigerian bank transfer screenshot into a spreadsheet takes 2 minutes per receipt — this does it in 5 seconds per screenshot, across GTBank, Access Bank, First Bank, UBA, and Zenith, without a single template.
5-10s per screenshot · Up to 99% accuracy on printed text
What You Can Pull from a Nigerian Bank Transfer Screenshot
A Nigerian bank transfer confirmation is a single screen — the same NIBSS data rendered differently per bank. With Custom Column Extraction, you name the fields and the AI finds them by label meaning.
Formatted as NGN1,500.50. May appear as "Debit Amount", "Amount Sent", or "Transaction Amount". The AI isolates the transferred principal from any fee.
The recipient's account name. Labeled "Beneficiary", "Recipient", or "Transfer To" — the AI identifies it by role regardless of the bank's wording.
The NIBSS-issued unique code — a 12-30 character alphanumeric string. Labeled "Session ID" (GTBank, Access Bank), "Reference" (UBA), or "Transaction Ref" (Zenith). The primary reconciliation key.
The free-text description entered by the sender — carries invoice numbers, payment purpose, and personal references. The most important field for Nigerian reconciliation.
Eight Different Bank Apps, One NIBSS Backend — Template Tools Can't Keep Up
NIBSS Instant Payment (NIP) powers every Nigerian bank transfer. But each bank renders the same data differently — different colors, label positions, layouts. Template tools break on the second bank.
Why Nigerian Bank Screenshots Break Traditional Tools
Same NIBSS data, completely different visual skins. GTBank's purple app positions Amount at top center. Access Bank's green app places it below a colored header. UBA's red interface uses a different card layout. First Bank's blue app puts fields in a different order. A template trained on one bank fails on the next.
Three amounts, one transfer — which is the real payment? Nigerian bank apps often display "Debit Amount" (including fees), "Amount Sent" (the principal), and "Amount Received" (what landed). A regex rule that grabs the "number after the label" has to know which label to follow.
The Session ID changes its label every time. "Session ID" in GTBank, "Reference" in UBA, "Transaction Ref" in Zenith, "NIP Session ID" in Access Bank — the same NIBSS code, different labels. Tools that search for a fixed label string find it on one bank and miss the next four.
How Semantic Extraction Reads Any Bank's Confirmation Screen
Labels are read by meaning, not by position. The AI understands that "Amount", "Debit Amount", "Transaction Amount", and "NGN1,500.00" all refer to the same field. It does not matter where the label sits — the field is identified by what it means.
The Session ID is found by its role, not its label string. Whether the bank calls it "Session ID", "Reference", "Transaction Ref", or "NIP Session ID", the AI recognizes it as the unique NIBSS transaction identifier. The alphanumeric pattern and its role as the primary reconciliation key are consistent across all banks.
Narration is captured as free text. The AI reads the narration at any length (12-40 characters typical) and preserves the exact text — invoice numbers, payment purpose, and personal references. This is the field that makes Nigerian bank transfers uniquely useful for reconciliation.
"In Nigeria, I am writing ten [parsers]. Because the rest of the world agreed on a format decades ago. We never did. Every bank speaks a different language. Different column headers. Different date formats. Different transaction descriptions. Different layouts entirely."
— Opeyemi Emmanuel, developer on LinkedIn
From Mixed Nigerian Bank Screenshots to One Clean Spreadsheet
Upload Screenshots from Any Nigerian Bank
You have a GTBank transfer confirmation for a client invoice, an Access Bank receipt for supplies, a UBA payment confirmation for utilities, and a First Bank success page for payroll. Four different bank apps, four different UI themes. Upload them all into one batch — JPG, PNG, or WebP screenshots of the confirmation screens.
Define Columns Once — Amount, Beneficiary, Session ID, Narration
Type the columns you need. The AI reads each screenshot independently: it isolates the transferred amount (not the fee) by reading the label meaning, identifies the beneficiary name from whatever the bank calls that field, captures the NIBSS Session ID whether it is labeled "Session ID", "Reference", or "Transaction Ref", and preserves the exact narration text including invoice numbers and payment purpose.
Get One Unified Table — No Sorting by Bank
Processing takes 5-10 seconds per screenshot. The output is one XLSX or CSV: four columns (Amount, Beneficiary, Session ID, Narration), one row per transfer. The GTBank, Access Bank, UBA, and First Bank screenshots each produced the same clean structure. Roughly 24x faster than opening each confirmation and typing the values by hand (~2 min manual per screenshot for 4 fields vs ~5s here).
What you get — across all Nigerian bank apps:
| Amount (NGN) | Beneficiary | Session ID | Narration |
|---|---|---|---|
| 150,000.00 | Chukwudi Okafor | NIP20250726123456 | Invoice INV-2026-042 |
| 45,200.00 | Lagos Supplies Ltd | SES2407150987654321 | Office supplies July |
| 850,000.00 | Fatima Abubakar | REF56892341AB2026 | July salary |
When It Works Best — and When to Be Cautious
Understanding the boundaries helps you get consistent results with Nigerian bank transfer screenshots.
When It Works Best
Direct screenshots from any Nigerian bank app. Full-resolution screenshots from GTBank, Access Bank, First Bank, UBA, Zenith, and others achieve up to 99% accuracy.
Mixed bank screenshots in a single batch. GTBank, Access Bank, UBA, and First Bank confirmations can be uploaded together — no need to sort by bank first.
Bulk reconciliation from multiple sources. Dozens of transfer confirmations from different banks produce a single sorted spreadsheet, ready for accounting software.
When to Be Cautious
Forwarded screenshots through WhatsApp or Messenger. Messaging platforms compress images, which may reduce character-level accuracy for the Session ID.
USSD confirmation screenshots. Some Nigerian banks (GTBank *737#, Access Bank *901#, UBA *919#) show transfers via USSD pages. These have less visual structure than app screenshots and may produce less consistent Narration results.
Architecture boundary: screenshot of confirmation, not a data feed. This approach works with screenshots — forwarded receipts, shared images, and saved screenshots — but cannot pull data from NIBSS or the bank's API.
Frequently Asked Questions
How does the AI handle the same NIBSS data rendered in different bank app UIs?
The AI reads the label that precedes each value, not its position on the screen. Whether the Amount is labeled "Amount" in GTBank's purple UI, "Debit Amount" in Access Bank's green app, or "Transaction Amount" in UBA's red interface, the AI identifies it by what the label means — not where it sits on the page. The same column definitions work across all eight major Nigerian bank apps without any template changes.
What is the difference between Debit Amount, Amount Sent, and Amount Received — and which one goes into the Amount column?
Debit Amount is what left your account (including any transfer fee). Amount Sent is the principal transfer before fees. Amount Received is what landed in the beneficiary's account. The AI maps the value labeled as the transferred principal — the figure that represents the actual payment — to the Amount column. The fee, if displayed separately, goes into a separate Fee column. You can also define a Computed Column to calculate the difference between Debit and Sent amounts.
Can I process screenshots from different Nigerian banks in the same batch?
Yes. Upload a GTBank screenshot, an Access Bank transfer confirmation, a UBA receipt, and a First Bank success page together in one batch. Define your four columns — Amount, Beneficiary, Session ID, Narration — once. The AI processes each screenshot independently, reading the labels on each bank's unique UI. The output is a single Excel file with one row per transaction, regardless of which bank each screenshot came from.
Does the Narration field capture the full text even if it is long?
Yes. The AI reads the Narration field at whatever length the sender entered, up to the typical 12-40 character limit of Nigerian banking apps. Narration is the most important field for reconciliation in Nigeria — it carries invoice numbers, payment purpose, biller codes, and personal references. The AI preserves the exact text, including numbers and special characters, so you can use it for matching against your internal records.
Can I extract the NUBAN account number of the beneficiary from the screenshot?
Some Nigerian bank apps display the recipient's NUBAN (10-digit account number) on the confirmation screen, and some display only the beneficiary name and bank name. When the NUBAN is visible on the screenshot, you can add it as a column and the AI will extract it. If the bank app shows only the last 4 digits for security reasons, partial extraction is still possible. For the beneficiary's full 10-digit NUBAN, you will need to reference the original transfer instruction or a bank statement.
See all payment screenshot types supported by this tool, from GTBank and Access Bank to Venmo and PayPal: payment screenshots overview
Another Nigerian payment platform with a different UI challenge: OPay / PalmPay screenshot extraction
Mobile-money format diversity from East Africa, another market where the same data appears in multiple app skins: M-Pesa SMS screenshot extraction