Parsing bank CSV exports into OFX 1.0.2 locally
Banks often limit direct automated feeds to 90 days or drop regional accounts altogether, leaving bookkeepers with raw CSV downloads. Converting those spreadsheets into Open Financial Exchange (OFX 1.0.2) files with a browser-based OFX file generator lets accounting software ingest months of history without repetitive column mapping.
Detecting date, description, and amount columns automatically
The CSV parser supports comma, semicolon, and tab delimiters up to 15 MB per file while validating unclosed quotes under IETF RFC 4180 CSV Format Specification rules. It scans headings case-insensitively for Date, Posted Date, Description, Payee, Amount, or paired Debit and Credit columns.
If your bank provides statements only as PDFs instead of spreadsheets, you can extract transactions from PDF bank statements to Excel or CSV using the same local parser engine. When a Balance column exists, the preview highlights rows whose running balance fails to reconcile.
Skipping bank header metadata and resolving date order
Many online banking portals prepend account holder names, IBANs, or export timestamps in the first few lines above the actual table. The importer automatically skips every row until it locates a valid date heading, so you do not need to edit raw downloads in Excel first.
When Dates in the statement stays on Work it out, the parser scans all rows for numbers above 12 to distinguish DD/MM/YYYY from MM/DD/YYYY. If every date falls on or before the 12th of the month, switch the dropdown explicitly to Day first (25/03) or Month first (03/25).
How does an OFX file prevent duplicate bank transactions?
Accounting software deduplicates OFX imports using a unique <FITID> (Financial Institution Transaction ID) inside each <STMTTRN> block. Because this converter builds each <FITID> deterministically from the transaction date, description, signed amount, and same-day occurrence index, re-importing an overlapping date range lets your ledger skip previously loaded entries automatically.
Deterministic FNV-1a FITID hashing across overlapping imports
According to the OFX 1.0.2 SGML Specification, every <STMTTRN> element requires a persistent <FITID> alongside <TRNTYPE>, <DTPOSTED>, and <TRNAMT>. Here, the worker combines the normalized row key with a 32-bit FNV-1a hash prefixed by YYYYMMDD so identical CSV rows always yield identical IDs.
If two identical purchases occur on the same day, an incrementing counter appends to the hash input so both stay distinct. Quicken .qfx and QuickBooks .qbo files share this OFX structure, except QuickBooks requires an <INTU.BID> tag, so generate QuickBooks Web Connect QBO files with an Intuit bank ID for QuickBooks Desktop or QFX workflows.
Normalizing UTF-8 merchant names into CP1252 SGML tags
OFX 1.0.2 uses SGML syntax (OFXHEADER:100, DATA:OFXSGML, VERSION:102) with ENCODING:USASCII and CHARSET:1252. To respect tag ceilings, <NAME> truncates to 32 SGML-escaped characters while <MEMO> stores up to 255 characters whenever the full description exceeds 32 characters or contains escaped symbols (&, <, >).
OFX account tags and software compatibility reference
Selecting the right Account type writes the exact SGML message wrapper expected by desktop and cloud bookkeeping tools. Choosing Checking / current or Savings emits <BANKMSGSRSV1> and <BANKACCTFROM>, while Credit card switches to <CREDITCARDMSGSRSV1> and <CCACCTFROM>.
| Accounting target or setting | SGML structure or tag emitted | Practical import behavior |
|---|---|---|
| Checking / current | <BANKMSGSRSV1> + <ACCTTYPE>CHECKING |
Maps to standard business or personal checking registers |
| Savings | <BANKMSGSRSV1> + <ACCTTYPE>SAVINGS |
Maps to reserve, tax, or high-yield savings accounts |
| Credit card | <CREDITCARDMSGSRSV1> + <CCACCTFROM> |
Omits <BANKID> and matches credit card liability feeds |
Currency (10 presets) |
<CURDEF> (USD, GBP, EUR, CAD, AUD, etc.) |
Sets statement currency without manual ledger overrides |
| Account number | <ACCTID> (up to 22 characters) |
Helps software match the right account; last 4 digits suffice |
As documented in the Xero Central Bank Statement Import Guide, Xero reads these structured tags directly from .ofx uploads without asking you to remap columns. If your European bank exports SWIFT MT940 files rather than CSV, you can convert SWIFT MT940 bank statements to CSV or OFX directly.
Handling credit card signs, multi-file merges, and privacy
Credit card CSV exports frequently invert debits and credits compared to bank checking statements, and reconciling those signs before download saves tedious manual deletions inside your ledger.
Fixing inverted credit card charges with Swap money in and out
When a card issuer lists purchases as positive numbers, the preview table displays them under Money in instead of Money out. Ticking Swap money in and out flips every row’s polarity immediately so charges export as negative <TRNAMT> debits and card repayments export as positive credits.
Note that when Swap money in and out is active, the converter omits <LEDGERBAL> closing balance overrides so inverted card balances do not confuse your accounting software. For European corporate treasury feeds delivered as XML, use the ISO 20022 CAMT.053 XML bank statement converter.
Running balance checks and zero-upload browser security
To prevent character-encoding errors in legacy parsers, merchant strings pass through NFKD decomposition as defined in the MDN String.prototype.normalize() Reference, stripping diacritics cleanly into plain ASCII.
Tip: Enter only the last four digits under Account number (such as
4821) so your exported.ofxfile identifies the right register without storing your full bank account number.
All file reading, date disambiguation, and OFX serialization run strictly inside your browser’s Web Worker, keeping private banking records off external servers. This converter formats transaction files for bookkeeping convenience rather than certified accounting advice.