Check for a direct export
Check online banking first for a direct QuickBooks Desktop export covering the required account and period. If it is not available, use the statement.
PNC Bank provides statements for personal checking and savings accounts, including Virtual Wallet, and for business checking accounts in US dollars. The reviewed statements include a Virtual Wallet Spend statement and a Business Checking statement, two layouts that both take the sign of each amount from the section heading rather than from the row.
Full name: PNC Bank
Countries: United States
Supported statement formats: PDF
Supported destinations: QuickBooks Desktop, QuickBooks Online, Quicken, Xero, CSV/Excel
Check online banking first for a direct QuickBooks Desktop export covering the required account and period. If it is not available, use the statement.
For a short statement, type the date, memo, and amount into the destination. Reconcile the result to the closing balance.
Open the PDF statement, review the extracted transactions, choose QuickBooks Desktop, and save the converted file on your computer.
Choose the posted transaction date, supply a missing year from the statement period, and check statements that cross January.
Remove currency symbols from numeric cells, preserve the decimal separator, and verify debit and credit signs against the running balance.
Keep the payee or customer reference that helps identify the transaction, while avoiding repeated headers and unrelated reference numbers.
The following details were checked against two PNC Bank statements from 2020 and 2024: a Virtual Wallet Spend statement for a personal checking account and a Business Checking statement. They are two layouts from one bank. The personal layout has three columns, Date, Amount and Description. The business layout has four, Date posted, Amount, Transaction description and Reference number, and splits the activity into more sections. Both put the sign of every amount in the section heading, not in the row.
MM/DD with no year, 12/26 and 01/22. The year comes only from the period line in the header, "For the period 12/23/2023 to 01/24/2024" on the personal statement and "For the Period 01/01/2020 to 01/31/2020" on the business one. The personal period crosses a year end. Fee rows add a third format on their second line, "Effective 01-10-24".2,618.47 and 17.62. Amounts under one dollar drop the leading zero, .84 for an international POS fee and .00 in the services table. The daily balance tables mark an overdrawn day with a trailing minus, 134.68-.Every transaction date is month and day only, 12/29 on one row and 01/12 a few rows down. The personal statement runs from 12/23/2023 to 01/24/2024, so the same page holds December 2023 and January 2024 rows with nothing on the row to tell them apart. A converter that takes the year from the statement end date moves the December transactions eleven months forward. It has to read the period line, give the December rows the start year and the January rows the end year, and do that again on every page, because the period line is the only place the year is printed.
No row carries a sign. On the personal statement the money in is under "Deposits and Other Additions" and the money out is under "Banking/Debit Card Withdrawals and Purchases", "Online and Electronic Banking Deductions" and "Other Deductions". The business statement has "Deposits and Other Additions" with Deposits, Fee Refunds and Other Additions under it, and "Checks and Other Deductions" with Debit Card Purchases, POS Purchases, ATM/Misc. Debit Card Transactions, ACH Deductions and Service Charges and Fees. A section that runs over a page break repeats its heading with "- continued" and repeats the column header. A converter that reads every amount with one sign ends up with an ending balance that is off by twice the deposits, and one that forgets the heading at a page break flips the sign of every row on the next page.
The personal statement prints a short summary in the right margin of each section: "There were 4 Deposits and Other Additions totaling $5,614.17." and "There were 52 other Banking Machine/Debit Card deductions totaling $4,188.36." The note starts on the same line as the section heading and wraps into two or three lines that land between the column header and the first transaction. A converter that reads the page line by line sees "totaling $4,188.36." as a line of its own with an amount and no date, and either drops it, adds it as a transaction or joins it to the first row of the section.
Rows read 6831 Debit Card Purchase Heb Online #108, 6831 Recurring Debit Card Netflix and N1226 6831 Payment Affirm San Francisc Ca. The first token is the last four digits of the debit card, and some rows put a code such as N1226 in front of it. The business account has two cards, 3031 and 9090, in one statement. The rest of the merchant name, or the city and state, wraps to a second line with no date: Amzn Mktp on the first line and US*Ot4R71N23 on the second, Brazil Bakery Corp and then Pompano Bea Fl, and a phone number split as Spectrum 855- and 7077328. A converter that keeps the first line only gives every Amazon purchase the same payee, and one that keeps the card digits in front makes every payee start with a number, which defeats the payee matching in the accounting software.
The business layout has a Reference number column on the far right. In the Debit Card Purchases section the 20-digit reference, 47702860099813087004, is printed a little higher than the date and amount of its own row, so in the extracted text it appears as a line by itself between two transactions. In the POS Purchases section the reference is split into two pieces on the row, POS93006417 and 1860471. In the ACH Deductions section it sits on the row in one piece. A converter that treats every line with digits as a transaction creates rows with no date; one that joins a stray line to the previous description appends a 20-digit number to the wrong transaction.
Both layouts have a Balance Summary with beginning balance, deposits, deductions and ending balance in one row, an Overdraft and Returned Item Fee Summary with a period total and a year to date total, and a Daily Balance table with three or four date and balance pairs on one line, 12/23 1,504.21 01/02 2,207.19 01/11 134.68- 01/18 618.36. The personal statement adds a Transaction Summary with counts, and the business statement adds a summary table with Items and Amount in two side by side columns, Deposits 5 4,872.50 on the left and Debit Card Purchases 37 1,264.03 on the right, and a "Detail of Services Used During Current Period" table on the last page whose charge posts next month as one line. The first page of the personal statement has no transactions at all, only a notice about debit card limits. A converter that takes any line with a date and an amount as a transaction reads each daily balance line as up to four transactions and the summary rows as more.
Compare the converted transaction count and totals with the statement, then confirm that the calculated final balance equals the printed closing balance.
Yes. If the PDF statement is readable, its age does not prevent conversion. Confirm the year when transaction rows omit it.
No. Convert posted transactions that contribute to the statement balance. Pending or future-dated items should not be mixed into that reconciliation.
Use the destination-specific settings below, then review the file before import. The destination may require particular columns, dates, account identifiers, or sign rules.
A bank PDF can contain searchable text, scanned page images, or a mixture of both. Searchable text still needs layout analysis because transaction descriptions wrap, columns move, and headers or balances repeat at page breaks. A scanned statement adds OCR uncertainty.
A transaction may begin at the bottom of one page and continue on the next. Continuation pages can omit column headings, repeat an opening balance, or insert footer text and legal pages between transaction pages. A conversion should join split rows and exclude repeated page furniture before it writes the output.
On scanned pages, OCR can turn 0 into O, 1 into l, or 5 into S. It can also lose a minus sign or decimal mark, read two columns in the wrong order, or struggle with skewed and faint pages. The running balance is the best check: a damaged amount or missing row breaks the balance sequence.
Yes. Review the OCR result and reconcile every balance movement. Scans with faint printing, rotation, or handwritten marks need more checking than searchable PDFs.
PDF text stores page positions rather than a spreadsheet table. Wrapped descriptions, repeated headers, and visually aligned columns can paste in the wrong order or into the wrong cells.
Try selecting a transaction description in a PDF reader. If individual words can be selected, the page probably contains text. If the whole page behaves like one picture, it requires OCR.
QuickBooks Desktop imports bank transactions in two formats: QBO (Web Connect) and IIF. They go into QuickBooks through different doors, and the right one depends on the QuickBooks version and on how much detail the file must carry.
Settings that matter for a QBO file:
Settings that matter for an IIF file:
Parent:Sub.Use QBO when QuickBooks is less than three years old and the transactions should go through Bank Feeds for review and matching. Use IIF when QuickBooks is discontinued, when the transactions should land directly in the register, or when each row must carry a vendor and an expense account.
Not with QBO. A discontinued QuickBooks version refuses QBO files and no longer connects to online banking. IIF still imports, because it does not depend on Intuit's servers.
The bank ID in the QBO file is not one QuickBooks recognizes. A converter sets the bank ID from its own list. Choose a listed bank, or use an ID that QuickBooks accepted before.
The account ID in the file does not match the ID QuickBooks stored for the existing account. Use the same account ID as the last successful import, or connect the file to the existing account when QuickBooks asks.
QuickBooks skips rows whose transaction ID it has seen before. Missing rows usually mean repeated IDs in the file. Doubled rows usually mean a statement that was already imported with different IDs. Both are fixed by importing each period once, with IDs that stay the same for the same transaction.
Yes, in both formats. For QBO, match the file to the sub-account in Bank Feeds. For IIF, write the full path Parent:Sub as the account name.
QuickBooks writes a new IIF file next to the original with a timestamp in its name, containing only the failed rows and an error message per row. Fix the cause in QuickBooks, usually a missing account or vendor, and import the timestamped file.