Intuit’s help pages say QuickBooks downloads the last 90 days of transactions when you first connect an account, and that for earlier dates you upload a bank file. So a feed that starts three months ago is normal, not broken. The job is to bring in the months before it, and nothing that overlaps it.
Feeds also develop holes later: a connection expires, a client changes online-banking credentials, an account is re-linked. The repair is the same.
Find the seam first
Before converting anything, open the account in QuickBooks, sort the register by date, and write down the date of the oldest transaction already there. Call it D. Everything dated D or later is covered by the feed, so your upload must end on D minus one day. Intuit’s guidance is blunt: if the account is already connected, uploading overlapping files may create duplicates that you then delete or exclude by hand.
Why overlap duplicates, and what a FITID is
Each transaction in a QBO (Web Connect) file carries a FITID, a transaction ID. QuickBooks keeps the IDs it has already accepted for an account and ignores repeats; Intuit’s Web Connect documentation says transactions with duplicate IDs are ignored, and Online typically behaves the same way. A bank-issued file and a live feed often do not share IDs, and a PDF has none at all, so whatever converts the statement must invent them, usually from the row’s date, amount and description. Those invented IDs cannot match the feed’s, so the same purchase on both sides of D arrives twice. The fix is not a cleverer converter. It is a clean cut-off date.
Step by step: fill the months before the feed
- Mark the cut-off. Sort the account register by date and note the oldest transaction already in QuickBooks. The last transaction in your upload must be dated at least one day earlier.
- Collect the statements. Get every statement for the missing months, plus the one that straddles the cut-off so you can see exactly where the feed begins.
- Convert and tie out. Convert each PDF and confirm opening + deposits − withdrawals = closing for every statement, then confirm each closing balance equals the next opening balance.
- Trim the straddling statement. Once that statement has tied out, delete the rows dated on or after the cut-off from its upload file.
- Split to fit. Keep each file under 350 KB and 1,000 lines, the limits Intuit lists. One month per file keeps both limits and your audit trail simple.
- Upload to the matching account. In QuickBooks Online open Bank transactions, choose Link account, then Upload from file. Select the file, pick the bank or credit card account it belongs to, select the transactions and confirm. Menu names move between versions.
- Reconcile each month. Reconcile against each statement’s ending balance before starting the next month. The difference must be 0.00.
Prove the seam after uploading
Once the months are in, open the register and read the balance at the end of D minus one day. It should equal the statement’s balance for that day. If it is off by a round amount or by exactly one transaction, suspect a duplicate at the seam, a dropped row, or an opening balance that was never entered. The balance-check guide explains how to read that difference.
Your options for the gap
| Option | Duplicate risk | Best for | Watch for |
|---|---|---|---|
| Statement PDF to QBO | Low if the cut-off is clean | Any month you hold a PDF for, including scans | Needs a balance tie-out before upload |
| Bank’s own QBO or OFX download | Medium: its IDs may differ from the feed’s | Banks that still offer file downloads for older dates | Banks limit how far back they go; some offer no file |
| Statement PDF to 3-column CSV | Higher: CSV carries no IDs | When a QBO file keeps being rejected | Column mapping and signs are on you |
| Manual entry | None from imports | A handful of lines | Slow, and typos do not announce themselves |
What can go wrong
- Overlap at the seam. One day of overlap duplicates every transaction on that day. Compare your last uploaded row with the first feed row.
- Wrong account type. A bank file loaded into a credit card account, or the reverse, can be refused or post with inverted signs. See the credit card sign guide.
- Files over the limits. Intuit lists 350 KB and 1,000 lines per upload. Split larger files by month.
- A register that disagrees with the statement. If the account never had an opening balance, or earlier months were keyed by hand, the register total will not match the statement even when every row imported. Reconcile shows the difference.
- Closed books. If a closing date is set in QuickBooks, posting into earlier periods may prompt for a password or be blocked.
- Deleted or excluded lines. Because QuickBooks remembers IDs it has seen, re-uploading typically will not bring back a line you deleted. Restore it from the excluded list.
Where SheetParser fits
SheetParser turns a statement PDF, digital or scanned, into one row per transaction, checks opening + deposits − withdrawals against the closing balance, and exports a QuickBooks .QBO, a Xero CSV or an Excel file. It does not connect to your bank or to QuickBooks; you upload the file yourself, which is what a fill-in needs. Free accounts convert 1 file a day, up to 10 pages; paid plans take up to 150 pages per file. Keep the pre-import checks from the PDF to QBO guide close at hand.