Moneydance+ only reaches back as far as your bank's connection, and older months are stuck in PDF statements. Upload them here and get OFX files Moneydance imports with account details and transaction IDs, or CSV if you want to edit first.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
Moneydance cannot import PDF files. It imports OFX, QFX, QIF and CSV, and its own help center rates OFX as the best. Convert the PDF statement to OFX, then choose File, Import in Moneydance, select the file and confirm the account. The transaction IDs in the OFX stop overlapping imports from creating duplicates. Import one statement month per file.
Moneydance imports OFX, QFX, QIF and CSV, and nothing else. Bank sync covers recent months at best, older downloads disappear, and a year of a busy checking account is close to 1,000 lines to type by hand.
One upload gives you an OFX file with account details, signed amounts and transaction IDs, or a clean CSV.
The format Moneydance rates best, with a statement header and closing balance.
The same statement always gets the same FITIDs, so a repeat import does not double your register.
One signed amount column and US dates for a short mapping screen.
Paper statements scanned or photographed are read with OCR.
The same routine on Mac, Windows and Linux.
Upload one statement month above and download it as OFX.
In Moneydance choose File, Import and select the .ofx file.
Accept the account Moneydance suggests or pick the right one.
Confirm the transactions and check the balance against the statement.
People who need more history than their bank connection will give them.
Filling the months between the old program's last QIF export and the first bank sync.
Loading a full tax year of a business checking or card account for Schedule C.
Catching up a client who keeps books in Moneydance and hands over a folder of PDFs.
Choose File, Import in Moneydance and select an OFX, QFX, QIF or CSV file, then confirm the account the transactions belong to. Moneydance reads the file, adds the transactions as unconfirmed entries, and lets you accept them in the register. What it cannot do is read a PDF. If your bank only gives you PDF statements for the months you need, convert them to OFX first with the upload box on this page, then import the OFX.
Most people land here for one of three reasons. They just switched from Quicken or Microsoft Money and the bank connection in Moneydance+ only reaches back a few months. Their bank quietly stopped offering the OFX or QFX download on older statements. Or they are catching up a year of a small business account that was never tracked. In each case the history exists, but only as PDF documents, and Moneydance has no way to open them.
Infinite Kind's own help center is blunt about the ranking: OFX and QFX files are the best formats to import, QIF files are second best, and CSV files are a distant third. PDF is not on the list at all. Here is how the files you are likely holding line up.
| What you have | Moneydance import | What to do with it |
|---|---|---|
| OFX file | Yes. Infinite Kind ranks OFX and QFX as the best formats to import | Import it through File, Import. Transaction IDs make repeat imports safe |
| QFX file (Quicken Web Connect) | Yes, same family as OFX | Import it like an OFX file |
| QIF file | Yes, rated second best | Fine for moving history out of older software. No transaction IDs |
| CSV download | Yes, rated a distant third | Map every column by hand. Not accepted for investment accounts |
| PDF statement, digital or scanned | No | Convert it to OFX with the upload box above, then import |
| Paper statement | No | Scan or photograph it, then convert. OCR reads the scan |
The reason OFX wins is the transaction ID. Every OFX transaction carries a FITID, a unique identifier. Moneydance keeps it, so if you import a file whose dates overlap with one you already loaded, it recognizes the transactions it has seen. QIF and CSV have no such field, which is why the same overlap in a CSV can leave you deleting duplicate rows by hand.
Convert the PDF to OFX, then import the OFX through File, Import. The conversion reads the transaction table on each page, including scanned statements through OCR, and writes one OFX file per statement with the date, signed amount, description and a stable transaction ID on every line. Here is the routine that keeps a year of history clean.
One month per file sounds slow, but it is faster overall. Each import is small enough to review, and the monthly balance check tells you at once whether anything was missed. A gap equal to one transaction means a line was skipped; a gap of twice a transaction amount means a sign came in wrong. Both are quick to fix in the register before you move on.
CSV import works in Moneydance, it just asks more of you. You choose the field delimiter, set the date format and decimal character, then assign a Moneydance field to every column. The help center warns that the number of fields you define has to match the number of columns in the file, with extra columns set to Ignore rather than left out. CSV is also not accepted for investment accounts.
That trade can still be worth it. If you want to split a transaction, fix payee names in bulk, or delete transfers you already recorded before anything touches your Moneydance file, export the statement as CSV from the same upload, clean it in Excel or Numbers, and import that. Our PDF bank statement to CSV converter writes a single signed amount column with US dates (MM/DD/YYYY), which keeps the mapping screen short. For anything you will import as is, OFX is less work and safer.
| Route | Best for | What you do in Moneydance | Duplicate protection |
|---|---|---|---|
| PDF to OFX (recommended) | Checking, savings and credit card accounts | File, Import, select the .ofx, confirm the account | Yes. Each transaction carries a FITID Moneydance stores |
| PDF to CSV | When you want to edit rows in a spreadsheet before importing | File, Import, set delimiter, date and decimal format, map each column | No transaction ID, so an overlapping import can double rows |
| Moneydance+ bank sync | New transactions going forward | Connect the account through the subscription | Handled by the sync, but it only reaches as far back as the bank serves |
| Typing it in | A handful of lines | Enter each transaction in the register | Whatever care you take |
For most people the answer is both: Moneydance+ or the bank's own download for the months the bank still serves, and converted PDF statements for everything older. The OFX files do not depend on a subscription and do not expire, so you can build the back history once and keep the files.
Every export uses the OFX 1.02 SGML format with a statement header, the account number and account type read from the statement, and one STMTTRN block per transaction with TRNTYPE, DTPOSTED, TRNAMT, FITID and the payee text. Card statements go out as a credit card statement rather than a bank one, so Moneydance treats charges and payments the right way round. When the statement prints a closing balance, it goes into LEDGERBAL, which gives you the number to reconcile against.
Re-exporting the same statement produces the same transaction IDs. That matters if you convert a month, import it, then realize you uploaded the wrong page range and convert again: Moneydance sees the same IDs and does not double the register.
Moneydance brings over data from both programs through QIF, and that covers the years the old software already held. The gap is usually the months after you stopped using it, or accounts you never tracked. Convert those statements to OFX and import them after the QIF history is in. If you are still deciding where to go after Money, our comparison of the best Microsoft Money replacements covers how each one takes your data. If you are staying on Money for now, the Microsoft Money import converter writes the same OFX Money Plus Sunset reads.
The demo converts up to 15 pages with no credit card, enough to test one or two statements end to end in Moneydance. A year of a typical checking account is 12 statements of 2 to 6 pages each, well inside the Starter plan at $49 a month (2,500 pages a month on the faster AI model, up to 25 pages per statement). Cancel after the month if the backlog is done. Bookkeepers catching up several clients, or anyone with statements longer than 25 pages, will want Plus for bulk upload of up to 50 files at once. See pricing for the current plans.
Compare that with typing: a business checking account with 80 transactions a month is close to 1,000 register lines a year, each one a chance to transpose a digit. The converter reads them in minutes and the balance check proves the result.
No. Moneydance imports OFX, QFX, QIF and CSV files, not PDF. Convert the PDF statement to OFX first, then choose File, Import in Moneydance and select the file. Scanned paper statements convert the same way, because the converter reads them with OCR before writing the OFX.
Moneydance imports OFX, QFX, QIF and CSV files through File, Import. Infinite Kind rates OFX and QFX as the best, QIF as second best and CSV as a distant third, mainly because OFX and QFX carry a transaction ID that prevents duplicates when imports overlap.
Choose File, Import and select the CSV. Set the field delimiter, the date format and the decimal character, then assign a Moneydance field to every column, using Ignore for columns you do not want. The number of fields must match the columns in the file. CSV cannot be imported into investment accounts.
Open the register of the account you are importing into, choose File, Import, select the .ofx file and confirm the account Moneydance suggests. The transactions arrive unconfirmed; accept them, adjust categories, then compare the balance with the closing balance on the statement.
For OFX and QFX files, yes. Each transaction has a FITID that Moneydance stores, so an overlapping import is recognized. QIF and CSV files have no transaction ID, so importing the same dates twice can create duplicates. Import one statement month per file and keep date ranges from overlapping.
Moneydance+ bank sync only gets what your bank's connection serves, which is often a few months. Older history has to come from files. If the bank offers OFX or QFX downloads for old months, use them; if it only offers PDF statements, convert those to OFX and import them.
Yes. Moneydance brings in Quicken and Microsoft Money history through QIF exports, one account at a time. Months after you stopped using the old program, or accounts it never tracked, can be filled from PDF statements converted to OFX and imported afterward.
Moneydance is a $65 one-time purchase that includes the next major upgrade, and Moneydance+ bank sync is an optional add-on at $4 a month or $40 a year (checkout prices, September 2026). The free trial is fully functional but limited to 100 manually entered transactions, and purchases carry a 90 day money back guarantee.
You can test up to 15 pages with no credit card. A year of statements for one or two accounts fits in one month of the Starter plan at $49, which includes 2,500 pages a month on the faster AI model. Cancel when the backlog is imported.
The general PDF to OFX converter behind this page.
PDF statements to CSV for the Moneydance CSV importer.
Credit card statements to OFX for card accounts.
Paper and scanned statements to OFX with OCR.
The same OFX files for Microsoft Money Plus Sunset.
Import steps and fixes for OFX, QFX and CSV files.
Moneydance and the other replacements compared.
Get started converting bank statements to OFX.
USD
per month
per month
$294 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion with bulk upload, custom templates and reports.
USD
per month
per month
$894 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
per month
$ charged today
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |