How to sync SEB Lithuania transactions to YNAB

SEB Lithuania is one of the most searched banks among European YNAB users in Lithuania. The budgeting method works — but keeping accounts current when your bank and YNAB do not talk to each other creates weekly friction.

YNAB offers Direct Import in Lithuania through Plaid, but coverage is limited to certain institutions — and SEB Lithuania is often not on the list, or the connection breaks after credential changes. Many SEB Lithuania customers still export CSV files from online banking and import them manually each week.

Even when imports work, the process is fragile: export formats change, pending transactions appear twice, and your YNAB budget is only as fresh as your last upload. If you share a budget with a partner or track multiple SEB Lithuania accounts, the manual work multiplies.

BudgetSyncer is built for European YNAB users who want automatic bank sync without storing bank passwords. You connect YNAB once with OAuth, then authorize SEB Lithuania through regulated PSD2 open banking (via GoCardless). BudgetSyncer reads transactions and imports them into the YNAB accounts you choose.

Your SEB Lithuania login never passes through BudgetSyncer — authentication happens on your bank’s own secure consent screen, the same flow used by other open-banking apps in Lithuania. Access is read-only: BudgetSyncer cannot move money or change account settings.

Transactions sync on a schedule (several times per day). YNAB handles duplicate detection when transactions arrive — BudgetSyncer focuses on keeping the feed from SEB Lithuania reliable, including notifications when bank consent needs renewal.

Step 1 — Create a free BudgetSyncer account and sign in. You can browse supported banks and connect YNAB before subscribing. No credit card is required to explore whether SEB Lithuania appears for Lithuania in the bank directory.

Step 2 — Connect YNAB with OAuth. BudgetSyncer requests permission to read your budgets and accounts and to create transactions in the YNAB accounts you select. You can revoke access anytime from YNAB or BudgetSyncer.

Step 3 — Add a bank connection and select Lithuania in the country picker. Search for SEB Lithuania. If your branch or subsidiary appears under a slightly different name, pick the listing that matches your account — open banking directories sometimes use legal entity names.

Step 4 — Complete SEB Lithuania’s authorization flow in your browser. Your bank may ask you to confirm access in its mobile app or with strong authentication. Once approved, BudgetSyncer can read new transactions from the linked account.

Step 5 — Map the SEB Lithuania account to the correct YNAB account and enable sync when you subscribe. New transactions flow into YNAB automatically. Review imports in YNAB as you normally would; categorization and reconciliation stay in YNAB.

Bank connections run through GoCardless Bank Account Data, a PSD2-regulated provider. BudgetSyncer does not store your SEB Lithuania credentials. Consent expires under EU rules — when it does, you re-authorize through a short in-app flow.

You can disconnect SEB Lithuania from BudgetSyncer or revoke consent directly at your bank. We store only OAuth tokens and mapping settings needed to sync while your subscription is active, as described in our privacy policy.

Most users complete setup in under five minutes. After the first sync, check YNAB for imported transactions from SEB Lithuania and confirm payee names look right. You can adjust field mapping in BudgetSyncer if you want cleaner memos or payees.

Running a shared YNAB budget? Each linked SEB Lithuania account counts as one connection — map checking and savings separately if you track them in different YNAB accounts. Cancel anytime from account settings; bank consent can also be revoked at SEB Lithuania directly.

If SEB Lithuania is not listed for Lithuania, use the unsupported-bank form on this page — we track demand and expand coverage as GoCardless adds institutions. Pricing starts at 4.99€/month for one bank connection, with +1.49€/month for each additional linked account.