Import a Bank Statement Into Patriot Software

Why Patriot won't import your PDF

Patriot's Accounting imports bank transactions from spreadsheet files, CSV, XLS, and XLSX, but it cannot read a PDF. A PDF is a printed statement, not a table of dated transactions, so there is no column of amounts for Patriot to bring in. When your bank only gives you a PDF, the transactions sit in a document Patriot has no way to open. Converting that statement to a CSV turns the pages into rows Patriot can import, which is the whole point: you avoid typing a month of transactions into the register by hand and instead upload them, map a few columns, and review.

Importing a CSV in Patriot's Accounting

The manual bank import in Patriot is built for exactly this. Normally you download a CSV or Excel file of transactions from your bank and upload it, but a converted statement gives you the same file when the bank only offers a PDF. In Patriot's Accounting, open the bank import for the account, choose your converted CSV, and upload it. Patriot reads the rows and moves you into a mapping and review step before anything posts. Because the import creates journal entries from the rows, getting a clean file in, one with a clear date, description, and amount, is what makes the rest of the process quick.

Header rows and column mapping

Patriot maps what it can automatically and lets you handle the rest. If your file has a header row, leave the box labeled the first row in my file is a header row checked; if it does not, uncheck it so Patriot does not treat a transaction as column titles. Patriot then matches the columns it recognizes, and for any it cannot, you map them by hand, while any extra columns you do not need can simply be left unselected. A converted file helps here because the columns come out clean and consistently labeled, so the automatic mapping catches more and you confirm rather than correct.

Pending transactions: accept or dismiss

Imported transactions do not post straight to the books in Patriot. They land as pending, and you work through them by accepting the ones that belong, which posts them and creates the journal entries, or dismissing the ones you do not want, such as a duplicate or a transfer already recorded. That review step is a safeguard: it lets you categorize and confirm each line before it hits the account rather than after. Since every transaction was also reviewable in the converter before export, the pending list you accept in Patriot should be clean, with few surprises to dismiss.

Getting clean data in, and privacy

The quality of a Patriot import comes down to the file you feed it, and a converted statement gives you consistent Date, Description, and Amount columns with no currency symbols or stray characters to trip the mapping. That keeps the pending list accurate and the reconciliation short. Because bank statements hold sensitive detail, files are processed to build the CSV and then deleted automatically, with nothing retained on a server afterward. For a bookkeeper importing into Patriot for several clients, that automatic deletion keeps account data from lingering in a third-party tool while still turning PDFs into clean imports fast.

Frequently Asked Questions