Email import
Send a bank statement to your own secret address. The transactions wait for your approval, or are imported on their own into accounts you choose. What the email must contain, how the account is suggested, automatic import, notifications, security, limits and what is kept where.
Last updated: October 27, 2026
Email import ends in the same import as uploading a file; only the route is different. Instead of signing in to Assetli, you send your bank statement as an email attachment to your own address. Its transactions appear in the app, and by default nothing is written until you approve the import. For selected accounts you can turn on automatic import.
The feature is part of the paid Premium and Max plans. On the Free plan the page shows the plans instead of an address.
Where to find it and how to turn it on
Open the page with the “Email import” button at the top of the Bank accounts section; when statements are waiting for approval, the button shows how many. Settings → Bank import links to it as well. Links from the app to this documentation open in a new tab, so you do not lose the page you are setting up.
Email import is off by default. Once you turn it on, you get your own secret address of the form i-<32 characters>@inbound.assetli.app. Do not share it. The “Generate a new one” button creates a different address and invalidates the old one immediately. Use it if you suspect the address has leaked.
Changing the address
You confirm the change in the “Generate a new address?” window, which first lists what will happen:
- The old address stops working immediately, and statements sent to it are discarded.
- Forwarding and rules in your mailbox need to be changed to the new address.
- Automatic import is turned off for all accounts. Turning it on again asks for your consent again.
- Allowed senders, the approval queue and the import history stay.
The address only changes once you confirm with “Generate”.
Steps
- Download the statement from your online banking as CSV, Excel or XML (
camt.053). MT940, OFX, QIF, GPC and national formats work too; see Statement formats. - Send it by email. Pick the account next to the Subject field. The “Write email” button opens your mail app with the address and subject filled in. If you write from another app, use “Copy subject”.
- Approve the import. The statement appears under “Waiting for approval” with a suggested account. Check the account and click “Import”, or “Discard” the statement. Next to the sender you see “Verified sender” (the message signature, DKIM/DMARC, confirmed it really came from that address) or “Unverified sender” — the address may then have been forged, so check the statement before approving.
What the email must contain
| Field | What goes in it |
|---|---|
| To | Your secret address |
| From | An allowed sender. The email of your Assetli account is allowed automatically; you can add more addresses under “Allowed senders”. |
| Subject | ”Statement – account name”. The account is suggested from the subject. |
| Attachment | A statement in a supported format (CSV, Excel, XML, MT940, OFX, QIF, GPC and others). One email can carry up to 20 statements, and each is filed separately. Each attachment can be at most 10 MB. |
| Message body | Not read. Only when the message has no attachment at all do we try to find a statement pasted into the body. |
Character encoding is recognised automatically, just as when you upload a file (see Statement formats).
What we cannot do yet
- Scanned PDF. We read a PDF with a text layer (downloaded from online banking or sent by your bank), but not a scanned one.
- Automatic import from PDF. A statement from a PDF always goes to approval, even if automatic import is turned on for the account. We rebuild the table from the positions of text on the page, so we want you to see the result before anything is written.
Which account is suggested
The account is only prefilled; you always confirm it. The suggestion is looked up in this order:
- your own account number stated in the statement itself (camt.053, MT940, OFX, GPC, CODA, CBI, Elixir, Raiffeisenbank, UniCredit — Air Bank does not include it in the statement),
- an account number or IBAN in the file name,
- the account name in the file name,
- the account name in the subject (only when the message carries a single statement),
- the bank, recognised from the statement format, if you have only one account at that bank,
- the only account in your profile.
When two accounts have the same name, nothing is suggested and the page tells you so. We recommend renaming them; otherwise you choose the account when approving.
Automation tips
You do not have to send every statement by hand. Pick what suits you. You can also forward statements that your bank emails to you as PDF. Statements in CSV, Excel or XML can also go through automatic import, but a PDF always waits for your approval.
Two more things apply to a message forwarded from your bank:
- The bank sets the subject. So we recognise the account by the account number in the file name. If it is not there, the statement waits for approval.
- The bank is the sender. A forwarded message keeps the bank as the sender, so the bank address has to be added under “Allowed senders”.
Gmail: forward bank statements automatically
Set it up once and every statement from your bank arrives on its own.
- In Gmail open Settings → See all settings → Forwarding and POP/IMAP → Add a forwarding address and enter your Assetli address (the To field on the Email import page).
- Gmail sends a confirmation code to that address. It appears on the Email import page (import must be on) — copy it and enter it in Gmail.
- Create a filter: From = the address your bank sends statements from, Has attachment → Forward it to your Assetli address.
- Add the bank address to the allowed senders — a forwarded message keeps the bank as the sender.
The bank sets the subject, so we recognise the account by the account number in the file name. If it is not there, the statement waits for approval.
Gmail forwarding confirmation code
Gmail sends a confirmation code to your Assetli address. The code appears on the Email import page in a blue box, “Gmail asks you to confirm forwarding”. The “Copy code” button copies it, and you enter it in Gmail under Settings → Forwarding and POP/IMAP.
- Only a message that Google really signed (DKIM) is shown. A message that merely pretends to come from Gmail shows no code.
- The code stays visible on the page for 7 days.
- Email import must be on, otherwise the address does not accept the message.
- Such a message does not go to quarantine, even if Google is not among your allowed senders.
Outlook: a forwarding rule
The same in Outlook.com or the Outlook app.
- Settings → Mail → Rules → Add new rule.
- Condition: From = the bank address; action: Forward to your Assetli address.
- Add the bank address to the allowed senders.
Some Microsoft work accounts block forwarding outside the organisation — then the rule sends nothing.
iPhone: a “Send to Assetli” shortcut
Send a statement downloaded in your banking app with two taps from Share.
- In the Shortcuts app create a new shortcut and turn on Show in Share Sheet (accepts files).
- Add the Send Email action: recipient = your Assetli address, subject = “Statement – account name”, content = the shortcut input. Turn off Show When Run so the email sends on its own.
- After downloading a statement in your banking app tap Share → Send to Assetli.
The email is sent from the account set up in the Mail app — it must be among the allowed senders.
Mac: a rule in Mail
When statements arrive in Mail on your Mac.
- Mail → Settings → Rules → Add Rule.
- Condition: From contains the bank address; action: Forward Message to your Assetli address.
- Add the bank address to the allowed senders.
The rule only works while Mail is running on the Mac.
Approval and what happens on import
By default nothing is imported on its own. Every statement waits under “Waiting for approval”, and batches that are not approved are deleted after 14 days. The only exception is accounts where you have turned on automatic import.
A statement we could not understand shows up in red with the reason and can be discarded. In that case upload the file manually on the Bank accounts page, where you can assign the columns yourself (see Importing data). The same happens to a statement whose columns cannot be recognised for certain (for example when dates only go up to the 12th, so day and month cannot be told apart). The import window would ask you to check the columns in that case, so email import does not approve it blindly either.
An approved import takes the same path as an uploaded file: duplicate detection, pairing of transfers between your accounts and a balance recalculation. The same plan limits apply. An account synced with Wallet by BudgetBakers accepts an emailed statement on the same terms as an uploaded one: only rows dated after its last synced transaction are imported, the rest are skipped, so the two sources cannot create duplicates.
Two more things work exactly as in the import window. A statement in a different currency than the selected account is not imported, and you see why: the amounts would be saved in the wrong currency. And if the account was empty before the import and the statement carries a closing balance, the account balance is set from it.
You can freely mix uploading a file and email import on the same account. Duplicate detection is shared, so a transaction that is already in your data is skipped, whichever way it arrived.
Automatic import
For accounts you send statements to regularly, you can skip approval. The “Automatic import” section has a switch next to each account. It is off for every account by default, and everything waits for approval.
The first time you turn it on, a consent window appears. The checkbox “I understand that statements for the selected accounts will be imported without my approval…” is required. If AI categorization after import is on and you have not yet confirmed consent to automatic AI credit use, the window also asks for a second checkbox.
The page shows your consent with the date and time you confirmed it, and we keep it in a consent log. When you turn automatic import off for all accounts, the consent lapses and turning it on again asks for it once more.
A statement is imported on its own only when all of the following hold:
- The account is certain. The file name contains the account number or IBAN, or the account name is in the file name or the subject. The guesses “the only account at that bank” and “the only account in your profile” are not enough. If the selected account appears in the statement as a transfer counterparty, the statement is from another account (nobody transfers money to the same account) and it waits for approval — this matters mainly for banks that do not put your own account number into the statement. If the statement carries its own account number and it does not match the selected account, the statement always waits for approval.
- The sender is verified by the email signature. DKIM or DMARC must pass. The result is computed by the receiving server of the provider Resend, so it cannot be forged. SPF alone is not enough.
- The statement makes sense. The format is recognised (not generic CSV), there are no broken characters, dates are no older than 3 years and no more than 3 days in the future, and amounts are numbers. The statement is in the same currency as the account.
- The statement has at most 1,000 rows.
- The import is allowed. On an account synced with Wallet by BudgetBakers the statement contains something newer than the last synced transaction, the import does not exceed your plan’s monthly import limit, and the plan is a paid one.
If anything does not fit, the statement stays under “Waiting for approval” with the reason “Not automatic: …” and you get a notification by email. Automatic import never throws anything away.
The other layers of protection still apply. A message from an unknown sender goes to quarantine, not to the queue. When a message comes from an allowed sender but the signature does not verify, the statement goes to approval.
Changing the address with the “Generate a new one” button turns automatic import off for all accounts, and turning it on again asks for your consent again (see Changing the address).
Categorization after import
Your categorization rules always run after an import, free of charge, whether you approved it or it ran automatically. AI categorization of the rest runs only when the “Categorization after import” switch is on. It is the same setting as Settings → Bank import, and it uses your AI credit (see Plans and credits).
You confirm turning the switch on (here and in Settings → Bank import) in a window: AI then uses your AI credit on its own after every import, automatic ones included. If you had AI categorization on before, you will see a “Confirm consent” prompt. Until you confirm, automatic import does not run AI categorization.
After an automatic import, AI receives only the transactions from that import, each one once. If it does not finish within the processing time limit or your AI credit runs out, the rest stays uncategorized and the notification tells you so.
Recently imported and undoing an import
The “Recently imported” list shows imports from the last 14 days, manual and automatic, labelled “Manual” or “Automatic”. The “Undo import” button deletes all transactions from that import and recalculates balances, including the counter-accounts of transfers. Categories you set on those transactions by hand in the meantime are lost.
Before undoing, a window shows exactly what will happen: how many transactions are deleted, from which account and period, how many stay on the account, how many of them are transfers to your other accounts, which accounts get their balance recalculated and how many manually changed categories are lost.
Transfers to your other accounts (the “Transfers to your other accounts (removed there too)” line in the window) disappear from the counter-accounts as well, and their balance is recalculated. Other transactions on your other accounts are not deleted.
Notifications
We let you know what happened to your statement. Settings → Notifications has three types. All of them are on by default in the app and by email, and you can turn each one off.
| Notification | When it arrives |
|---|---|
| Email import: statement imported | Automatic import wrote a statement into your data. With counts and a link to undo the import. |
| Email import: statement awaiting approval | A statement is waiting in the queue. With automatic import, also the reason it did not run on its own. |
| Email import: statement could not be read | We could not understand the statement. |
Notifications are sent right after the message arrives, not in a daily digest. One message with several statements triggers at most one notification of each kind.
Security
An inbound address is a route into your data, so four layers protect it, one after another:
- Secret address. Until you turn import on, the address accepts nothing. You can replace it with a new one at any time.
- Allowed senders only. Mail from other addresses is not processed.
- Quarantine. A message from an unknown sender appears under “Waiting for your decision” with the buttons “It is mine” and “Not mine”. The quarantine holds at most 5 addresses.
- Approval. By default nothing is imported until you click “Import”. You turn automatic import on yourself, account by account, and even then only a statement from an allowed sender with a verified email signature gets through. Every import can be undone within 14 days.
An email that merely pretends to come from an allowed sender therefore does not change your data without your click: it fails the signature check and ends up in the approval queue.
Each message is processed only once. If the provider delivers it again, the repeat delivery is ignored.
Limits
- The address processes 10 messages a day from allowed senders.
- After 20 rejected messages in a day from unknown senders, the address turns itself off and the page tells you it has probably leaked. The “Generate a new address and turn on” button creates a new address and turns import back on.
- When the whole service receives an unusual amount of unsolicited mail, receiving pauses until the end of the day (UTC) and the page shows “Receiving is paused for today”. Send your statements the next day.
Privacy and retention
- The attachment is not stored anywhere. It is read in memory, and only the parsed transactions stay in the queue. They are removed from the queue right after import, and unapproved ones after 14 days.
- Mail is received by the provider Resend. It keeps a copy of the message, attachments included, for 30 days and does not allow earlier deletion. See Who processes your data and How long data is kept.
When nothing arrives
The step-by-step checklist is in Import: what to do when it fails.