01 Import

Four ways in. All of them stop at your review.

Numari never connects to your bank. You bring the data in yourself, and nothing is saved until you have looked at every row. Here is what each path can and cannot do.

Paste text

Copy a store receipt, a message from your bank, a push notification, or a few lines out of a statement. Paste it in. Numari reads it on your phone and turns it into transaction candidates.

It takes free-form text. You do not set up a template for your bank first, and you do not tell it which line is the amount. This path asks for no permission at all, which is why it works the same on iPhone and on Android.

Worth being plain about: pasting text into a tracker is not something only Numari does. Several apps offer a version of it. What differs here is that the text is parsed on the device, by an app with no account and no server behind it.

Photograph a receipt

Point the camera at a receipt, or pick a screenshot. The text is recognised on the device itself — on iPhone with Apple Vision, on Android with Google's ML Kit. The image is never uploaded, and Numari cannot browse your photo library; it sees the one picture you choose.

The honest limit: on iPhone the recogniser reads Latin and Cyrillic text. On Android, the on-device recogniser Numari uses has no Cyrillic model at all, so it cannot read a Russian receipt. If you are on Android and the receipt is in Cyrillic, copy the text and paste it instead. We would rather say that than let you find out by failing.

PDF statements

Pick the PDF your bank gave you. The text layer is extracted on the device and the rows become transaction candidates.

Two limits, stated up front. A scanned statement is a photograph of a page: it carries no text layer, so there is nothing to extract, and Numari will tell you so rather than guess. A password-protected PDF is rejected — Numari does not try to open it. Save an unprotected copy from your PDF reader, or download a statement without the password, then import that.

CSV statements

Every bank lays its CSV out differently, so the first time you import from a new bank you tell Numari which column is the date, which is the amount, and which is the description. It remembers that mapping for that bank. The next statement goes straight through.

If your bank hands you an XLS file, or a PDF only, or nothing at all, the paste path is the fallback that always exists.

The review queue

This is the part that matters, and it is identical whichever path the rows came from. Every detected transaction waits. You can correct the merchant, the amount, the currency, the date and the category before approving, or swipe it away. Rows that look like something you have already recorded are flagged as duplicates.

Two optional conveniences: you can tell Numari to remember that a given merchant belongs to a given category, and you can let it auto-add only the rows it is confident about. That second setting is off unless you turn it on. Your own rules always beat the built-in ones.

Nothing is saved until you approve it. That is the whole design.

What none of these paths do

• They do not connect to your bank. There is no bank login and no open-banking link.
• They do not read your email. See the FAQ on that.
• They do not upload the file, the photo, or the text you pasted.
• They do not need an account, because Numari does not have accounts.

The one optional network feature in the app is live exchange rates. It is off by default, and it sends only currency codes and dates — never amounts, never merchants.

Questions

Which import path should I use?

Whichever your bank makes easy. If it sends you a message about the payment, paste that. If you have a paper receipt, photograph it. If your bank only gives you a statement, import the PDF or the CSV. All four end in the same review queue, and all four are parsed on your device.

Does pasting text need any permission?

No. Pasting is just text you hand the app. There is no SMS permission, no notification listener, no bank login. Photographing a receipt asks for access to the one image you pick, and importing a file asks for that one file — nothing else, and never the whole library.

Why can’t Numari read my scanned PDF?

A scanned statement is a picture of a page. It has no text layer to extract, so there is nothing to read. Ask your bank for a normal PDF statement, or paste the text if you can select it. Password-protected PDFs are rejected too — open the file, save an unprotected copy, then import that.

Is anything saved before I look at it?

No. Every detected transaction waits in the review queue until you approve it. You can fix the merchant, amount, currency, date and category first, or reject the row. There is an optional setting, off by default, that auto-adds only the rows Numari is confident about.

Does the file or the photo stay on my phone?

It is read on your device to create the transactions, and it is not kept after the import. Nothing is uploaded at any point. The transactions you approve are what remains, in a local database on the phone.