Convert Truist PDF bank statement to Xero

Truist provides statements for personal and business checking, savings and business credit card accounts in US dollars. The reviewed statements include Business Value 500 Checking, Truist Focus Checking and Business Visa statements, one of them a text PDF with an OCR text layer.

Countries: United States
Supported statement formats: PDF
Supported destinations: QuickBooks Desktop, QuickBooks Online, Quicken, Xero, CSV/Excel

Truist PDF statement details

The following details were checked against Truist statements from 2022 to 2025: a Business Value 500 Checking statement, a Truist Focus Checking statement, and two Business Visa card statements. One of the checking statements is a text PDF whose text layer came from OCR, which is common for Truist statements that customers download and re-save, so the page covers both clean and OCR-layer files.

Settings for a Truist PDF statement

• Date: checking rows carry MM/DD with no year. The statement is dated in the header, For 03/27/2025, and the period is the span between "Your previous balance as of 02/27/2025" and "Your new balance as of 03/27/2025", so Truist cycles run mid-month to mid-month and cross the year in December. Card rows carry a transaction date and a post date, both MM/DD, with the year in "Billing cycle 02/08/25 - 03/07/25".
• Amount: comma for thousands, point for decimals. Checking amounts are unsigned; the section decides the sign. Card amounts carry a dollar sign, charges positive and payments or refunds with a leading minus, -$2,500.00.
• Account number: checking prints it in the page header after a state code, NC 1340009215548, and again in the account heading. Card statements print only "Account ending in 2362".
• Account type and currency: the account heading names the product, "TRUIST FOCUS CHECKING" or "BUSINESS VALUE 500 CHECKING"; card statements say "Business Visa". USD throughout.

Withdrawals come before deposits, and the sign lives in the section

A Truist checking statement lists "Other withdrawals, debits and service charges" first and "Deposits, credits and interest" after it, often on the next page. Both print positive numbers. A converter that assumes deposits come first, or that reads the amounts without tracking the section, gets every sign wrong. Each section closes with a total line, = $5,976.97, and the Account summary on the first page shows the same totals with their signs, which is the check.

The address block is printed letter by letter

The customer name and address on the first page come through as A N G E L D M I T C H E L L, one space between every letter. This is how Truist prints the mailing block, not an extraction error. It does not affect the transactions, but a converter that reads the account holder name from the statement has to collapse the spacing.

Description, state and card number are separate columns

A debit card row reads DEBIT CARD PURCHASE DUNKIN #362563 03-15 843-745-0892 followed by NC and 5070 as separate elements to the right. The state and the last four digits of the card are their own columns. A converter that joins everything after the date into one description gets a payee that ends in "NC 5070" on every card row; one that stops at the description column loses which card was used. The transaction date is inside the description as 03-15 for signature purchases and as 03-16-25 for PIN purchases, while the DATE column is the posting date.

The same text carries INT'L SERVICE ASSESSMENT FEE rows that repeat the merchant of the foreign purchase they belong to, and CONVERTED CHECK - ARC rows for checks the payee turned into electronic debits, which are listed here and not in the Checks section.

Checks are printed three per row

The Checks section has three groups of DATE, CHECK#, AMOUNT side by side, so a single row holds up to three checks that are not in date order with each other. A * after a check number marks a gap in the sequence and a • before it marks an electronically converted check, explained in a footnote under the table. Neither mark is part of the number.

Some Truist PDFs are scans with an OCR text layer

One reviewed checking statement is a text PDF, but the text was produced by OCR before the file reached the converter. The signs are doubled spaces inside phrases, DEBIT CARD PURCHASE, spaces inside amounts, 63 .59 and 200 .00, check numbers with junk attached, 2548,--,, a page count read as Page 3 of S, and left edges of the date column that drift by fifty pixels down the page because the scan was skewed. A converter must treat such a file like a scan: normalize spaces inside numbers before parsing them, group rows by position with a wider tolerance, and reconcile every section total.

Business Visa statements

Card rows have five columns: transaction date, post date, a 23-digit reference number, a description and an amount. The description is padded to fixed widths, merchant, city and state, so the city runs into the state when it is long, PEMBROKE PINEFL, FORT LAUDERDAFL. The reference number is unique per row and is the right transaction ID. Refunds carry a leading minus like payments do. There is no running balance; the check is Total transactions and other debits minus Total payments and other credits equals Balance in the Account summary.

The lower part of the first page is a remittance block marked "For information only, Do not remit payment" on company copies, with the account ending and the balance repeated. It is not a transaction.

Rows that are not transactions

The Account summary with its signed totals, the section total lines, the "Average Posted Balance in Statement Cycle" line, the page header with the account number, the page footer split into PAGE, 2, OF, 3, and the notices about fees and services that fill the rest of the last page.

PDF input challenges

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.

Page breaks

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.

OCR

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.

PDF questions

Can I convert a scanned bank statement?

Yes. Review the OCR result and reconcile every balance movement. Scans with faint printing, rotation, or handwritten marks need more checking than searchable PDFs.

Why does copying and pasting a PDF into Excel fail?

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.

How do I know whether the PDF contains searchable text?

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.

Xero import settings

Xero imports bank transactions through Accounting, Bank accounts, Import a Statement (also reached as Manage Account, Import a Statement). The file goes into the bank account's reconcile list, where Xero matches each line to invoices, bills and bank rules, or creates a spend or receive money transaction.

• OFX is the format to aim for. It carries the date, the amount, a payee, a description, a reference, a check number and a unique transaction ID. Xero uses the ID to skip lines it already has, so re-importing a period does not double it.
• QBO and QFX are OFX with extra header fields for QuickBooks and Quicken. Xero reads them as OFX, either directly or after renaming the extension to .ofx. If a QBO, QFX or OFX file downloaded from a bank is rejected, the file usually has a header, encoding or date format Xero does not accept; converting it to a plain OFX fixes that.
• CSV works when the columns match what Xero expects. A CSV downloaded from a bank often needs mapping on import and sometimes fails on the date or amount format. A CSV written for Xero carries the column names Xero maps on its own: Date, Amount, Payee, Description, Reference, Check Number.
• PDF must be converted first, to OFX or to a Xero CSV.

Settings that matter:

• Account: the Xero bank account is chosen before the upload. The account number inside the file is not used to pick the account, but keep it stable per account so the file is recognized on the review screen.
• Account type: bank or credit card. Xero keeps the statement's sign convention for credit cards, so a card purchase stays a debit; the converter should not flip signs for Xero the way it does for some other targets.
• Dates: four-digit years. In CSV, use one order for the whole file and confirm it on the import screen; day-month and month-day are both accepted but Xero must be told which one.
• Amounts: one signed Amount column, or separate Debit and Credit columns, in a CSV. No currency symbols or thousands separators. Money out is negative in the single-column layout.
• Payee and description: Xero shows Payee as the contact and Description as the transaction text, and bank rules match on either. Put the merchant name in Payee and the bank's transaction text in Description. Reference is a free field that other targets do not have; use it for the bank's reference number.
• Transaction IDs: unique per line and stable per transaction, so a second import of the same statement skips what is already there instead of duplicating it.
• Balances: Xero does not read an opening or closing balance from the file. Check the statement balance in Xero against the printed closing balance after import.

Xero questions

Should I import OFX or CSV into Xero?

OFX. It carries the payee, description, reference and check number in separate fields and gives Xero a transaction ID for duplicate checks. CSV is fine when the file was written for Xero with the right column names; a bank's own CSV usually needs mapping and cleanup.

Xero says my OFX, QFX or QBO file is invalid. What is wrong?

Most often the file has a header Xero does not read, non-UTF-8 text, dates in a format it does not accept, or a missing transaction ID. Convert the file to plain OFX and import that. Renaming QBO or QFX to .ofx helps only when the content is already clean.

Why did Xero import only some of the transactions?

Xero skips lines whose transaction ID it already has, and for CSV it skips lines it reads as duplicates by date, amount and description. Two genuine identical lines on the same day can be dropped from a CSV. Use OFX with unique IDs for those.

Why are the dates wrong after a CSV import?

The date order was misread. A file with 03/04/2026 can be read as 3 April or 4 March. Set the order on the import screen, or export dates as YYYY-MM-DD, which Xero reads without asking.

How do I undo an import?

Open the bank account, go to the statement lines or Bank Statements tab, select the imported statement and delete it. The lines disappear from reconcile and the file can be imported again.

Can I import older periods into Xero?

Yes. There is no date limit on file imports. Import periods in order and do not overlap them, so the balance in Xero follows the statements.

Does Xero read the opening balance from the file?

No. The statement balance in Xero is computed from the imported lines. Compare it to the printed closing balance after each import. If they differ, a line is missing, doubled, or has the wrong sign.