Import, explained

Bring your records.
Check the result.

Four ways into one review queue. Numari reads the source on your device; you decide which transactions reach your ledger.

Paste text

Copy the text of a receipt, bank message or statement excerpt, then paste it into Numari’s text import. The app parses supported patterns into transaction candidates. You do not connect your bank or give Numari access to messages or your mailbox.

Start with one receipt or a short statement excerpt. Include the amount, currency and date where possible. If a field is missing or looks wrong, correct it in the review queue.

Choose a receipt image

Select a receipt photo or screenshot from your device. Text recognition happens locally through Apple Vision on iOS or Google ML Kit on Android. Numari does not upload the image.

On iPhone: Latin and Cyrillic recognition depends on the languages Apple Vision supports on your device. Numari checks that support before recognition. On Android: the recogniser supports Latin script only. For a Cyrillic receipt, copy the text and use Paste text.

A clear, upright image with the total and date visible gives the recogniser more to work with. Faded print, blur and unusual layouts can produce mistakes. Check every amount before approval.

Import a PDF statement

Choose an unencrypted statement with a readable text layer. Numari extracts that text on your phone and creates candidates for review.

Scanned and password-protected PDFs are not supported. A scanned PDF is an image of a page. If your bank offers a text-based PDF or CSV export, use that. You can also paste text that you can select and copy from a statement.

Map a CSV once

Select the file and map its date, amount and description columns. Check the separator, date format and decimal format against the preview. Save a mapping preset if you expect to use the same format again.

CSV exports vary by bank and exchange; compatibility is not universal. Transfers and fees need particular care. Review the direction, category and currency, as well as the amount.

Review, then approve

Detected rows wait in the local review queue. Edit the merchant, amount, currency, date or category; reject rows you do not want. Numari flags candidates that may duplicate an existing transaction.

Eligible high-confidence rows can be approved in a bounded batch. Incomplete, uncertain or possible-duplicate rows need individual review. Merchant rules can remember your preferred category.

Only approved transactions enter your ledger. Parsed candidates and source evidence are already stored locally so you can review them. There is no unattended auto-add setting.

When the currency differs

Check the original currency and the converted amount. Live exchange rates are optional and off by default. With rates off, you may need to confirm the amount in your base currency yourself.

If you enable rates, providers receive currency codes and, for historical lookups, the date being priced. They also receive your IP address as part of the connection. They do not receive amounts, merchants, notes or import files. Reference rates can differ from the actual rate charged by your bank.

What remains after import

Numari does not retain the original selected image or file after parsing. Parsed fields and relevant source rows or text snippets can remain in the local import history, including after acceptance or rejection. They support review and duplicate detection.

Settings → Delete all data removes financial records and import history. See the privacy policy for the full inventory and the preferences that remain.

When something does not work

Try a smaller sample or another supported format. A failed parser is a reason to check the source, not to assume a zero amount or a correct date. You can always add an entry manually.

Contact support with your app version, steps and a redacted example if needed. Do not send an unedited statement or backup.