Bank export, PDF upload or converter: start with what you have

The files you have narrow the choice

• A recent CSV or QBO download comes first if its dates and format fit the destination.
• Older PDFs mean checking your existing app's coverage, access and review tools before looking elsewhere.
• For scans, check readability and every page, as well as whether the route supports scans.
• With many accounts or clients, start by inventorying periods, separate destinations and overlaps.
• For a one-off job, compare total charges for native options and manual templates before paying.
• Monthly work may suit a bank feed or repeatable export, but still needs checks for missing history and a review each month.
• A non-QuickBooks destination needs a download or converter whose output it supports. Renaming the file won't do that.
• For row-to-source review, you need to be able to locate and correct each row.

These are starting points, not performance rankings. Intuit's manual upload guide, updated August 24, 2026 documents both transaction-file and statement-image routes. Xero's current guides cover direct PDF import and Hubdoc extraction, including scan requirements. They were checked October 17, 2026; no update date was displayed on those Central pages.

We checked on October 17, 2026 using US QuickBooks Online help, not Desktop, and Xero Central with United States selected. Confirm your country, edition, subscription, permissions and account type in your app. Xero's PDF-specific guide excludes the Ledger plan and limits direct PDF imports to US and Canadian organizations. The opened pages do not establish PDF-upload eligibility for every QuickBooks plan or region, or Hubdoc entitlement for every Xero subscription.

Compare the work, not just the upload

Before comparing routes, list the accounts, periods and destination you need and check what's already in the books. Then ask:

• Can you get every missing date and statement page? The bank's download controls or a request for historical data can help you establish coverage. We don't assume the same historical limit across banks.
• Can your account accept the file, and can you import it? Conversion can't grant permissions or subscription features.
• Can you compare dates, signs and amounts with the source, correct rows and keep the reviewed result?
• What must you buy? Minimum purchases, recurring commitments and allowance expiry all belong in the comparison, along with preparation and checking time. An included feature is not a free standalone subscription.
• Are you allowed to send this client's statement to the provider? Its processing, human-access, retention and deletion terms need to be acceptable before you upload.

A representative statement lets you try the route before preparing an archive. If the importer is unfamiliar, learn it with synthetic data in a separate test company or organization rather than experimenting in a client's live books.

What each route gives you

We checked these capabilities on October 17, 2026, without independent benchmarks. Before choosing a separate converter, check its input requirements and actual outputs.

A bank download may still need formatting. Intuit's CSV guide, updated August 24, 2026 says banks format CSVs differently. QuickBooks Online documents three columns (Date, Description, Amount) or four (Date, Description, Credit, Debit). Make any layout changes in a working copy so you can keep the untouched download and PDF separately.

QuickBooks documents extracting transactions from English PDFs or images, with source review. The manual upload guide tells you to compare extracted data side by side with the statement, edit fields and review everything before saving. Some statements may be reviewed by Intuit's global experts, so don't assume processing stays in your browser. You don't need to pay for a converter just to see the original beside the extracted data.

Xero's CSV import guide, checked October 17, 2026 recommends bank-native OFX, QFX or QuickBooks files when available. It also documents bank CSVs and a template for making your own. Its direct PDF import guide, checked October 17, 2026 documents English PDF import into statement lines in eligible Xero organizations, without an intermediate CSV. You still need to check ready rows, warnings, errors and excluded duplicates, because warnings do not automatically prevent import. The guide recommends bank-native OFX over PDF when available.

Hubdoc is optional, not a required Xero step. Its extraction guide describes extraction from eligible scanned or downloaded PDFs into CSV for manual import. You'll need to review the extraction, then the import. Hubdoc can highlight extracted transactions on the statement, but you still have to compare the values. Source-assisted review isn't unique to a standalone converter.

File limits and account access can rule a route out

In Intuit's August 24, 2026 manual upload page, the transaction-list guidelines specify English and 350 KB or less. The list-upload section allows up to 1,000 lines, one transaction per line. These are list-import limits: the page does not establish the same cap for PDF uploads. Do not mistake a transaction limit for a PDF page limit. For long histories, prepare smaller, non-overlapping periods and keep a record of which files were imported.

Account structure matters too. Intuit's CSV errors guide, updated August 3, 2026 identifies importing to a subaccount as a current limitation. It points to connecting the subaccount to a feed, manual entry or support for unusual setups. Confirm the appropriate route rather than moving transactions into a different account merely to make the upload succeed.

Xero's CSV guide requires the administrator or standard plus bank accounts user role. The direct-PDF guide also lists the cashbook client role. The CSV template is regional, with browser language affecting the downloaded headings. Get the template from the intended account rather than copying an unexplained spreadsheet from elsewhere.

The current Hubdoc statement requirements include English, all pages of one statement, at most 100 pages per PDF, a file of 35 MB or less, minimum resolution of 200 DPI, maximum page dimensions of 40 inches and a straight scan. Xero's direct-PDF guide specifies the same size, resolution, language and scan limits, and excludes password-protected files. Both routes allow unsupported banks but warn that extraction accuracy can vary. Check the statement type and review the result; a supported-bank listing is not an accuracy guarantee.

One catch-up job, two kinds of source file

Suppose you need January through June 2026 for one USD checking account, and the books already contain July onward. The bank offers April through June as a structured download, but January through March are PDFs, with March scanned. These dates are fictional, not a claim about any bank.

Once you've checked coverage, use the download for April through June. For January through March, check native extraction, including March's scan eligibility, before using conversion or manual preparation for remaining gaps. Agree the historical opening-balance treatment first, and leave July out because it's already in the books. The historical import guide covers dates and overlaps.

All five March transactions are below. Positive amounts increase bank cash, while negative amounts decrease it. The opening balance is USD 1,750.00 and the printed closing balance is USD 2,020.00.

Net transactions are 950.00 - 600.00 - 85.40 + 15.40 - 10.00 = 270.00. Opening 1,750.00 plus 270.00 gives 2,020.00. All running balances agree too.

If any route returns only the first four rows, closing becomes 2,030.00, or 10.00 too high. The missing March 31 fee is the row to find on the source and correct in the extracted or transcribed data. An unexplained adjustment won't fix that omission, whatever the import preview looks like.

You need a route that lets you find and fix that row before posting. We verified the arithmetic here, not a product failure, and even a zero difference can hide two offsetting errors or an incorrect description.

You may not need another provider

If a bank download covers the job, there's no reason to reconstruct it from PDFs. A feed is a separate choice for future work: Intuit's upload guidance distinguishes ongoing connections from older transactions.

If QuickBooks is your destination and its statement upload meets your extraction and review needs, you can skip the intermediate spreadsheet. An eligible Xero organization can use direct PDF import, while Hubdoc suits those with access who want CSV and highlighting. Neither needs a separate converter if you can review the result adequately.

For a small, readable job, you can transcribe every row into the destination's documented CSV layout. You'll still need an independent check against the statement: doing it by hand avoids another extraction provider, not transcription risk.

When you're dealing with many accounts, keep an inventory of each account alias, currency, statement dates, source file, route and import status. The accounts need to stay separate through extraction, review and import. Xero's CSV instructions call for a separate download per bank account. One spreadsheet for every client won't replace that control.

A separate converter needs to fill a gap

If native downloads or your app don't meet your output and review needs, you can convert a statement with AnyStatement. It exports Excel, CSV (including QuickBooks and Xero layouts), QBO, QFX, OFX, QIF and JSON. You can follow transactions back to source PDF lines, and it checks opening balance plus transactions against closing balance, along with running balances when provided. Those checks test statement arithmetic, not ledger reconciliation or authenticity. Exports aren't guaranteed to work with every accounting edition. A bank-native export or manually prepared destination CSV is still a valid alternative.

For a one-off job, our pricing definitions checked October 17, 2026 include a USD 9 one-time pack of 100 pages, valid for 12 months from purchase. Free allowances are 3 pages per UTC day without an account (shared per network), or 30 pages per UTC calendar month with a free account. Pro offers 600 pages a month for USD 19 billed monthly, or USD 144 billed annually (equivalent to USD 12 a month, not a USD 12 monthly payment). Pro renews until canceled. Annual billing does not turn the monthly page allowance into an upfront annual pool. Pro replaces the 30 free monthly pages, and unused monthly allowances do not carry over. Packs require a free account. Check current pricing and promotion terms before purchase; this comparison did not test checkout.

The billing unit is a PDF page, not a statement or a row. Normally only transaction-bearing pages count; when source locations are missing, the statement's full page span can count instead. A charged conversion uses at least one page. Pages are spent when every statement in a conversion adds up to its printed balances and your allowance covers it, or when you choose to unlock a result that could not be verified. Failed conversions and repeat exports are not counted. Inspect the displayed page charge before unlocking.

Default document retention is 24 hours after upload, with expiry enforced on access and deletion performed by a periodic sweeper. A signed-in owner can explicitly keep a batch longer, up to 30 days after upload. Save the original and reviewed exports in your own approved records location; the converter is not your permanent document archive.

If your bank supplies a usable file for every required date, or QuickBooks, Xero PDF or Hubdoc already does the job, skip separate conversion. It won't fix import permissions, account restrictions or an unsupported destination, and it isn't a continuing bank feed. You also need authorization to use another processing provider; without it, don't upload. Conversion cannot establish authenticity, tax treatment or a completed ledger reconciliation.

Check the file, then reconcile the books

Your statements and downloads should stay untouched, so review a copy. Check the account, currency and required period against the books, then compare every page, transaction date, payment sign, refund, fee and amount with the source. Check opening balance plus net transactions against closing, along with available running balances.

Before importing, investigate duplicate candidates and coverage gaps so you know what belongs in the upload. Confirm the destination account, date interpretation, column mapping and import preview, then record imports and keep the reviewed result.

The CSV checking guide and the statement balance checker cover the file-review step. That's not the end of the job: Intuit's next steps after upload include matching, categorizing and reconciling. Arithmetic tests statement data, while reconciliation compares it with the books. Neither establishes authenticity.

What we checked, and what we didn’t test

On October 17, 2026, we opened the linked Intuit US manual-upload, CSV-formatting and CSV-error pages. We also opened Xero Central's CSV-import, direct-PDF-import and Hubdoc extraction pages in a browser with United States selected and expanded their instructions. Central displayed no update dates.

We checked our README, architecture, account and billing contracts, help docs, billing catalog and pricing components, and independently recomputed the fictional five rows, running balances and missing-fee difference with Python Decimal. We didn't use a bank login or customer statements, or run live extraction, QuickBooks or Xero imports, checkout, accuracy benchmarks, timing comparisons or retention-system tests. These recommendations compare documented fit, not demonstrated superiority.

If a route or limit has changed, send us the documentation link. Please don't send statements or account details.