FullaBANK STATEMENT CONVERTER
All guides

CSV, XLSX, or JSON for bank statement data?

Use CSV for simple tabular exchange, XLSX for workbook review, and JSON for structured application data.

Updated 2026-08-31 5 min read

Step by step

  1. 01

    Identify the next system

    Decide whether a person, spreadsheet, import tool, or application will consume the approved rows.

  2. 02

    Choose the simplest compatible format

    Use CSV for flat exchange, XLSX for workbook features, or JSON for structured programmatic use.

  3. 03

    Approve once

    All three formats use the same approved persisted revision.

  4. 04

    Download before expiry

    Exports inherit the statement content deadline and remain available only within the 24-hour window.

Choose CSV for a simple table

CSV is usually the most portable option for flat transaction rows. It works well for import tools and spreadsheets that do not need workbook formatting.

CSV does not carry workbook features such as multiple sheets, formulas, or cell styling. Confirm the delimiter and date expectations of the system receiving it.

Choose XLSX for a workbook

XLSX fits review and handoff when people need filters, formatting, formulas, or a familiar spreadsheet file. It is the practical choice when the output will continue through an Excel-compatible workflow.

Choose JSON for an application

JSON keeps the output structured for software that will validate, transform, or store transaction records. Fulla also exposes an API contract for workspace-bound programmatic workflows.

Whichever format you choose, it is generated from the approved revision rather than an unsaved browser state.

Questions about this guide

Can I create more than one format?

Yes. Available exports use the same approved revision, so you can choose CSV, XLSX, or JSON as needed while the document is available.

Does format choice change the extracted rows?

No. Format changes the representation, not the approved transaction revision.