Locate the DKK Amount, CPR-Linked Name, and Danish Notes from a MobilePay Screenshot
Manually logging each MobilePay payment from a screenshot into e-conomic or Dinero takes 2-3 minutes of retyping — this extracts the amount, CPR-linked name, and Danish notes in 5-10 seconds per image.
5-10s per screenshot · Up to 99% accuracy on printed text
What You Can Locate on a MobilePay Confirmation Screen
MobilePay's confirmation carries four fields that matter for Danish bookkeeping. Define your columns — the AI finds each value by understanding what it means, not where Denmark's most popular payment app places it.
Danish kroner only — no multi-currency ambiguity. The confirmation shows the gross amount; the 4,000 DKK fee threshold is invisible on screen.
The legal name tied to the recipient's Danish CPR number — not a changeable display name. From the sender's view, this is who received the money.
Up to 30 characters of free text — often carries invoice references with Danish characters (æ, ø, å) that pixel-level OCR misreads under compression.
Shown as an absolute timestamp on the confirmation screen — unlike the feed view which uses relative labels.
A CPR-Linked Name, Danish Characters, and an Invisible Fee — Why MobilePay Is Not a Simple Three-Field Screenshot
MobilePay's confirmation looks simple — amount, name, notes, done. Three Danish-specific details make it harder, each defeating a different flavour of traditional extraction.
The Recipient Name Is CPR-Linked — and the Payer Is Invisible
The name on a MobilePay confirmation is the recipient's legal name from the Danish CPR registry — a stable identifier, but it belongs to your account, not the person who paid you. The payer's identity never appears on the screen. UiPath developers report that payment screenshot extraction "sometimes changes the date and time, or even sometimes it doesn't reads amount" — dump OCR has no semantic context.
Danish Characters That Pixel-Level OCR Cannot Read
MobilePay's "Besked" field carries Danish references — "Faktura 1042," "Tak for i går," "Husleje juli" — every one containing æ, ø, or å. These are distinct Danish letters, not accented variants. Traditional OCR must detect the dot on the ø at the pixel level, which JPEG compression blurs beyond recognition. "Møde" (meeting) silently becomes "mode" (fashion).
The DKK 4,000 Fee Threshold Is Invisible on the Confirmation
MobilePay charges no fee for P2P transfers up to 4,000 DKK. Above that, a 1% fee applies on the excess. The confirmation shows only the gross amount — the fee is deducted from the sender's account invisibly. A dump OCR extracts "5,000.00 DKK" with no context about what the recipient actually receives.
Label-Aware Reading Captures the Right Name
Define Recipient Name as a column. The AI reads the label context — it finds the name positioned after the amount and before the notes field. It knows this is the recipient because the screen layout consistently pairs the name with the CPR-linked registration. The invisible payer is a limitation of the source, not the extraction; ask senders to include their name in the notes field, and the Notes column captures it.
Holistic Word Reading for Danish Characters
The AI reads "møde" as a complete word — not by decoding each diacritic at pixel level. æ, ø, and å are recognised as whole characters within their word context. Your Notes column gets the exact Danish text. The same approach handles Swedish characters in batch Swish screenshots.
Custom Column + Computed Column for the True Net
Define Amount (DKK) for the gross figure. Add a Computed Column — Net After Fee (Amount (DKK) - IF(Amount (DKK) > 4000, (Amount (DKK) - 4000) × 0.01, 0)) — to derive the reconciled net during extraction, ready for e-conomic.
From MobilePay Screenshots to a Bookkeeping-Ready Row in Three Steps
If you receive 20-30 MobilePay payments a month for freelance work or a small business, here is how a folder of screenshots becomes a spreadsheet ready for e-conomic or Dinero — without opening a single image to retype.
Upload the Screenshots
Drop a batch of MobilePay confirmation screenshots — JPG, PNG, or WebP. MobilePay uses a single app layout across all Danish banks (Danske Bank, Nordea, Nykredit, Jyske Bank, etc.), so every confirmation looks identical. Always capture the confirmation screen rather than the transaction history view — the history omits the notes field entirely.
Name the Columns
Define Amount (DKK), Recipient Name, Notes, Date. One set of columns for every screenshot. The AI reads the large centred amount as DKK, identifies the CPR-linked name by its label position, and captures the notes with Danish characters intact. Add the computed column for the net fee calculation if you need the reconciled figure.
Export and Import
Download as XLSX or CSV — four columns plus your computed net, one row per screenshot. Import into e-conomic (the market leader with over 200,000 Danish business users), Dinero, or Billy. Denmark's Bookkeeping Act (Bogføringsloven) requires businesses to retain transaction records for at least five years in a machine-readable format — a structured spreadsheet satisfies that requirement without manual data entry.
When MobilePay Screenshot Extraction Works Best — and When It Does Not
When It Works Best
Direct MobilePay app confirmation screenshots — high-contrast machine-rendered text at up to 99% accuracy for the amount and name fields.
Danish character recognition — æ, ø, and å are read as complete characters in context. Accuracy matches English on standard screenshots.
Batch with Swish — same field structure across Nordic payment apps, one column set for both.
When to Be Cautious
Forwarded or compressed images — MobilePay screenshots forwarded through chat apps lose resolution; the notes field may need a quick spot-check for æ/ø/å accuracy.
Transaction history view — the in-app history displays a condensed format that omits the notes/besked field. Always capture the individual confirmation screen for full four-field extraction.
Payer identity is not on the screen — MobilePay's confirmation shows the recipient's name only. To match incoming payments to customers, coordinate with senders to include their name or invoice number in the notes field.
Frequently Asked Questions
Can I extract the Recipient Name from a MobilePay screenshot even though the confirmation shows my own name rather than the sender's?
Yes. The name displayed is the CPR-linked legal name of the account holder — a stable, verified identity marker. Define a column called "Recipient Name" and the AI reads the label beside the name to capture it correctly. The limitation is that the payer's identity is not printed on the confirmation screen; ask regular senders to include their name or invoice number in the notes field, and the Notes column captures that context.
Will the extraction handle Danish characters like æ, ø, and å in the Notes field accurately?
Yes. The AI reads Danish text holistically — "møde" is understood as a complete word, not assembled from individual pixels. æ, ø, and å are recognised as distinct characters. This is the key difference from traditional OCR, which must detect each diacritic mark separately and frequently loses the dot on the ø under image compression. Expect accuracy comparable to English on standard screenshots.
Can I extract the fee MobilePay charged for a transfer above 4,000 DKK from the screenshot?
The confirmation screen does not display the fee. MobilePay deducts the 1% fee on the excess amount from the sender's account invisibly. Extract the gross Amount (DKK) as shown, then define a Computed Column with the formula Net After Fee (Amount (DKK) - IF(Amount (DKK) > 4000, (Amount (DKK) - 4000) × 0.01, 0)) to derive the reconciled net during extraction.
Can I batch MobilePay screenshots with Swish (Sweden) or Vipps (Norway) in the same export?
Yes. All three Nordic payment apps share the same field structure — amount in local currency, phone number, and a notes field carrying national characters (æ/ø/å for Danish, å/ä/ö for Swedish). Upload them together with one set of column definitions — "Amount (Local)", "Recipient Name", "Notes", "Date" — and each screenshot becomes one row in the same spreadsheet, regardless of which Nordic app generated it.
Does the extraction work for MobilePay Business account screenshots or only personal accounts?
Both. MobilePay Business accounts display the same confirmation screen layout — amount, recipient name linked to the business registration, and a notes field. Business accounts have higher transaction limits (configured per merchant agreement rather than the standard 50,000 DKK daily personal cap) and may include additional reference numbers. The column definitions remain unchanged; the AI locates fields by semantic meaning, not account type.
Deep dive into MobilePay screenshot field locations: How to find the amount, recipient, and notes on MobilePay screenshots — including the Danish-specific DKK limit and æ/ø/å handling
Swish and MobilePay share the same field structure for batch processing across Nordic payment apps: Swish screenshot extraction — BankID recipient name, Meddelande with Swedish characters, and batch workflow