Export / reference
CSV, XLSX, JSON, or OFX for bank statement data?
Use CSV for simple tabular exchange, XLSX for workbook review, OFX for QuickBooks Online or Xero statement imports, and JSON for structured application data.
At a glance
Start with the receiving system
A flat table for an importer
Confirm its columns, date format, sign conventions and delimiter expectations.
A workbook for a reviewer
Keep transactions, statement context and original fields on separate sheets.
Structured data for your code
Map approved conversion output to your application. A fetched result is not approval.
Step by step.
Identify the next system
Decide whether a person, spreadsheet, import tool, or application will consume the approved rows.
Choose the simplest compatible format
Use CSV for flat exchange, XLSX for workbook features, OFX for an accounting statement import, or JSON for structured programmatic use.
Approve once
Every format uses the same approved persisted revision.
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 OFX for QuickBooks Online or Xero
OFX is the bank statement format accounting software imports directly. QuickBooks Online accepts .ofx files through Upload from file, and Xero imports OFX statements, so dates, signed amounts and balances arrive without mapping spreadsheet columns.
Each OFX file covers one account. Every row carries a stable transaction ID, which lets importers that de-duplicate by that ID skip rows you already loaded. Fulla does not produce QFX or QBO Web Connect files for Quicken or QuickBooks Desktop.
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.
Compare the same approved rows in every format
The sample pack contains the same fictional approved rows as CSV, XLSX, OFX and JSON. Use CSV for a mapped table import, XLSX for a workbook handoff, OFX for a compatible statement importer, and JSON for software that validates a structured record.
Choose based on the receiving workflow, then inspect its requirements. A richer Fulla CSV may need a separate mapped copy; OFX is one account per file; a workbook is not a live sync. Keep the unchanged approved output alongside any transformed import file.
Sample files and references
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, OFX, 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.