What a QIF file actually contains
A QIF file is just text. You can open it in any text editor and read it. Each transaction is described by a short line, where the first character is a code that tells the software what the rest of the line means.
Common codes include D for the date, T for the transaction amount, P for the payee, M for a memo, L for the category or account, and N for a check or reference number. A single caret character on its own line marks the end of one transaction and the start of the next.
The file also begins with a header that names the account type, such as Bank, CCard, Cash, or Invst. That header tells the software how to interpret the records that follow.
When you would use a QIF file
QIF is most useful when you are importing transactions into a program that supports it but does not connect directly to your bank, or when you have data that started life as a PDF or spreadsheet and needs to land in a register.
Quicken historically used QIF for imports, though newer Quicken versions favor other formats for downloaded transactions. Many small-business and personal finance tools still accept QIF as a manual import option, which makes it a reliable fallback when a direct bank feed is not available.
If your accounting software offers a choice, check which formats it imports. Some prefer OFX, QFX, or QBO files; others accept CSV or QIF. Pick the one your software handles cleanly.
QIF versus OFX, QFX, and CSV
OFX, QFX, and QBO are newer XML-style formats. They carry more structured detail, including unique transaction IDs that help software avoid creating duplicates. QBO files in particular are tied to QuickBooks and may require a financial institution identifier known as an INTU.BID to import.
QIF has no such duplicate-prevention IDs, so importing the same file twice can create duplicate entries. It also does not always carry running balances or rich metadata. Its strength is simplicity and broad, long-standing support.
CSV is even simpler and opens in any spreadsheet, but most accounting programs need you to map columns to fields during import. QIF already labels its fields with codes, so a program that supports QIF can usually import it without a mapping step.
If your goal is to move bank statement data into books, the right format depends on the destination. QuickBooks Online often works well with QBO or CSV. Xero accepts CSV and OFX. Wave supports CSV and OFX. Quicken and some legacy tools accept QIF.
How to create or edit a QIF file
You can build a QIF file by hand in a text editor if you understand the codes, but that is tedious and error-prone for more than a few transactions. Most people generate one from another source instead.
If you are starting from a PDF bank statement, you first need to extract the transactions into structured data, then export to QIF. A conversion tool that reads the statement and outputs QIF saves the manual typing and keeps dates and amounts consistent.
Before importing, open the file in a text editor and check a couple of records. Confirm the account type header is correct, that dates use a format your software expects, and that amounts have the right sign, with withdrawals negative and deposits positive.
Always back up your books or create a test file first. Because QIF lacks duplicate detection, import a small batch, confirm it looks right, then proceed with the full file.