Excel to QBO requirements

Excel to QBO file requirements: prepare the first worksheet, then test the candidate.

BankFileKit can read an XLSX, XLS, or CSV table locally and create a candidate QBO Web Connect file. That output is a beta structure check, not a verified QuickBooks Desktop import.

Updated July 25, 2026 · Examples use fictional data.

Use the next step nowChoose a local XLSX, XLS, or CSV source, confirm the table mapping, and review the candidate boundary.

Open the Excel to QBO beta

Current input and output boundary

Item	Current behavior
Accepted source	XLSX, XLS, or CSV; one file at a time, up to 20 MB and 50,000 transaction rows.
Worksheet selection	For a workbook, BankFileKit reads the first worksheet only.
Output	A candidate `.qbo` Web Connect file for US English and USD testing.
Not supported	Multiple-sheet selection, PDF statements, QIF, IIF, QBW, QBX, images, bank logins, or complete company migrations.

Put one clean transaction table on the first worksheet

Make the first sheet a simple rectangular table. Start with a header row and one transaction per following row. Remove title bands, subtotals, repeated headers, merged decorative cells, and unrelated notes from the table area before conversion.

Provide the minimum fields

Field	Requirement	Tool behavior
Date	A date that consistently uses one selected convention.	Invalid dates block export; numeric dates that could be month/day or day/month require an explicit confirmation.
Description	Readable transaction text.	An empty description is a warning to review, not a substitute for a bank reference.
Amount	One signed Amount column, or one non-zero Credit or Debit value per row.	Missing/invalid amounts and conflicting Credit/Debit values block export.

Use values that can be reviewed

Prefer exported values rather than a presentation sheet full of merged labels, charts, footnotes, or calculations that need a separate workbook context. BankFileKit does not execute workbook macros, external links, or spreadsheet scripts.

Review date and duplicate warnings

If a date like 01/02/2026 can mean two different calendar days, choose the convention and explicitly confirm it before download. If two rows share the same date, amount, and description, the tool warns for review but never deletes either row automatically.

Fictional first-sheet example

Posting Date | Details | Deposit | Withdrawal
07/24/2026 | Fictional Design Payment | 625.00 | 
07/25/2026 | Fictional Office Supply |  | 48.20

Test the QBO candidate cautiously

Review the preview row count, date range, directions, and descriptions.
Download the candidate QBO locally.
Back up the target company and test in a blank QuickBooks Desktop company.
Compare the actual import result with the source table; do not call the candidate compatible until a real test passes.

Local processing does not make Desktop compatibility automatic

The selected source is read, mapped, previewed, and exported in browser memory. It is not uploaded to BankFileKit, analytics, or an AI service. That privacy boundary is separate from whether QuickBooks Desktop accepts the candidate output.

Sources checked July 25, 2026: Intuit: Import and export data in QuickBooks Desktop; Intuit: Fix Web Connect import errors; Open Financial Exchange specifications.