Skip to content
SageFin

Importing transactions from a file

For a bank that will not connect, history older than a connection reaches, or an account you keep by hand. If your bank exports CSV or OFX (often called a Quicken download), SageFin can read it. For a checking, savings or credit card account it can also read the statement PDF itself — see Importing from a statement PDF below. Moving from Quicken? See Leaving Quicken: importing a QIF file.

Getting a file in

Open the account, choose to import, and pick the file. SageFin previews what it found before writing anything — nothing is imported until you have looked at it.

It works out the columns. Files disagree about what a date column is called and where the amount sits, so SageFin proposes a mapping and you correct it if it has guessed wrong.

It works out which way the amounts point. Some exports write a purchase as a positive number and some as a negative one. SageFin looks at the file and decides which convention it is in — worth glancing at in the preview, because a file read backwards turns a month of spending into a month of income, and it is obvious in the preview and confusing afterwards.

The three ways to handle overlap

The important choice, and the one that decides whether you end up with duplicates. It matters because a CSV row and a synced row share no identity — your bank does not put the same reference in both — so SageFin cannot simply match them up.

Skip what is already there

The default, and right nearly always.

It skips any row identical to one from a previous import, and any row dated inside the stretch your provider already covers. That second rule is coarse on purpose: rather than guessing whether a particular row is a duplicate, it declines to import into a period the connection already owns.

It errs toward importing too little, which is the recoverable direction. Missing rows can be imported; doubled history has to be found and removed.

The file is authoritative

Deletes every transaction in the account between the file's earliest and latest dates, then imports all of it.

This is the only option that removes data, and it is the right one when the file is better than what is there — a period that synced badly, or an account whose provider sent nonsense. Check the date range in the preview before you use it, because that range is exactly what gets deleted.

Import everything

No matching at all. Duplicates are the expected outcome rather than a failure.

The escape hatch for when the other two get it wrong — an unusual file, or an account where you know exactly what you are doing.

Importing from a statement PDF

For a checking, savings or credit card account, connected or kept by hand, you can choose the PDF statement your bank or card issuer gives you, up to 4 MB. It is the way to bring in history from before your connection's first day when the bank offers no CSV that far back. Open the account, choose to import, and pick the PDF.

SageFin's AI model reads it. The PDF is sent to the AI model SageFin uses (or your household's own AI provider, if you have set one), which reads the statement's period, its opening and closing balances, its summary totals and every transaction line. Statements carry more personal detail than a receipt — your name, your address, your account number — so this is only offered when your household has turned on Enable AI Assistant in Settings → Preferences, and a private household's file must be unlocked. The PDF is not kept: it is read while you wait and dropped straight after. What is saved is only the lines you confirm, with anything that looks like an account or card number cut down to its last four digits.

Nothing is imported until you confirm. You see every line it read, and can untick a line, change its date or amount, or switch it between money in and money out.

The balance check has to pass. Starting from the statement's opening balance, the lines you keep have to add up to its closing balance to the cent. If they do not, SageFin will not import them, and it says by how much they are short or over and — by comparing the lines with the statement's printed totals for purchases and payments, or withdrawals and deposits — which side to look at. A line read twice, a line missed, or one going the wrong way is the usual cause. If the statement prints no opening or closing balance, there is nothing to check against: SageFin says so, and you can choose to import after comparing the lines yourself.

What the connection already covers is skipped. On a connected account, lines dated inside the stretch your bank already syncs are shown as already synced and left out, for the same reason as the default for CSV above. Importing the same statement twice adds nothing the second time. If you know better, Import everything writes every line anyway.

A statement for several accounts — a combined checking and savings statement — is matched to this account by the last four digits of its number. If SageFin cannot tell which part is this account's, it asks you.

A statement covering a long period can have more lines than SageFin can read at once; it says so rather than importing part of one. Use a statement for a shorter period, or your bank's CSV or OFX download.

Leaving Quicken: importing a QIF file

Quicken keeps your data in a .qdf file, which only Quicken can read. To bring your history to SageFin, export it from Quicken as QIF (in Quicken for Windows, File → Export → QIF File), choosing the accounts to include, and import the .qif file here: open any account, choose to import, and pick the file. A .qif file from your bank's website works the same way.

One file can hold several accounts. A Quicken export of more than one account lists each account it found, with how many transactions it has and the dates they cover. Choose which of your SageFin accounts each goes into, or leave it out, and they are imported together. Only accounts of a matching kind are offered — a Quicken credit card into a credit card account, a bank account into checking or savings — so add the SageFin accounts first if they are not there yet. An account whose name is the same as one in the file is chosen for you. A file with a single account goes into the account you started from.

What is left out. Quicken's Opening Balance line is the account's starting balance rather than a transaction, so it is not imported, and nor are records for $0.00 such as voided cheques. Investment accounts, the category list and memorized transactions are listed as not imported. Quicken's categories and splits are not brought across either: SageFin categorizes the transactions itself, as it does for any import. A transaction's memo and cheque number are added to its description.

Check the date order. QIF files write dates without saying whether 3/4/2025 is 4 March or 3 April. When some date in the file can only be read one way — a 25 in the first place means the day comes first — SageFin reads every date that way. When every date could be read either way, SageFin reads them month first, as US Quicken writes them, and asks you to check: switch to Day first if the dates look wrong.

Which way the amounts point is not a question here. Quicken writes money into an account as positive and money out as negative, a credit card's charges included, and SageFin turns that the right way round itself. Each account in the preview shows its money out and money in, so a file that was written the other way round shows before you import.

The three ways to handle overlap work as they do for CSV, applied to each account you chose. Importing the same QIF file twice adds nothing the second time.

Where duplicates actually come from

Almost never from importing the same file twice: an identical row from a previous import is recognized.

They come from importing over a period your connection already covers, which the default is designed to prevent, or from reconnecting a bank in a way that creates a second account. SageFin treats an account reached through a different provider as a new account rather than the same one — so after a re-link you can see two of everything, and the fix is not to delete transactions but to move the history onto one account and keep that one.

After an import

The rows are ordinary transactions: they categorize, budget and report like any other, and you can edit them. If a batch has landed in the wrong categories, bulk edit is faster than one at a time — changing a transaction.