Statement2Sheet

CSV, OFX or QBO: choose a bank statement export

Use CSV when you need a readable transaction table. OFX is a financial-data format used by accounting software; QBO is intended for QuickBooks imports. Statement2Sheet generates these files, but acceptance by your accounting software must be tested separately.

By Statement2Sheet · Updated

Upload a statementLimits and pricing

Compare the files Statement2Sheet produces

What each file contains today, not an external import certification
FormatWhat you getBefore you use it
CSVA transaction table with Date, Description and Balance, plus separate Debit/Credit columns or one signed Amount column. No row review highlighting.Check date and text import settings, column mapping and amount signs. Keep application warnings available.
OFXA financial-data file containing transactions, currency, account information, the statement period and closing balance.Confirm the account number, dates, closing balance and amounts. Check whether your software accepts the file before importing real records.
QBOA file intended for QuickBooks, with transactions and statement information. Check that names and descriptions display correctly after import.QuickBooks imports have not been verified for your bank. Try a sample first; if the file is rejected, use CSV instead.

If you need visible row status and review formatting, use XLSX alongside the application review screen. The CSV guide shows actual split and signed synthetic exports.

Check signs, dates and the account number

Signed amounts use credit − debit: deposits and payments are positive; withdrawals and card purchases are negative. In signed CSV and OFX/QBO, a card closing balance owed is negative. Split CSV keeps separate Debit and Credit columns and the source balance convention.

OFX/QBO transaction dates use a posting date when available, otherwise the transaction date. CSV uses the transaction date. Confirm the account number in the application before downloading OFX or QBO.

Use the same account number for each month you import. Before importing a file again, check how your software handles duplicates; Statement2Sheet does not guarantee that repeat imports will avoid duplicate transactions.

Review the result before importing

  1. Compare the extracted rows and balances with the original statement. Leave anything flagged for review unresolved until the source proves a correction.
  2. Inspect the columns, dates, descriptions and destination account. Statement2Sheet checks each file it generates, but it does not open QuickBooks or another external application.
  3. Import an invented sample into the exact receiving software and version. Check the account destination, count, signs, dates, descriptions, closing balance and repeat-import behavior before using real records.

The pass and review examples show when a statement is flagged for review rather than marked as converted. The sandbox API quickstart exercises upload, status and CSV retrieval, with fixed synthetic responses.

Questions about this workflow

Will renaming a CSV file to .qbo make it importable?

No. Your accounting software expects a file prepared for its import process. Renaming a CSV does not turn it into a QuickBooks export or make it compatible.

Does Statement2Sheet guarantee QuickBooks or Xero imports?

No. QuickBooks and Xero import compatibility has not been verified. Test a synthetic file in the exact software and version you use before relying on an import.

Does a successful file download mean every transaction is verified?

No. CSV, OFX and QBO do not carry XLSX-style row review status. Review warnings and reconciliation first; file generation and software acceptance are separate from transaction correctness.