CAMT.053 XML to OFX Converter

CAMT.053 to OFX Converter

Many accounting and personal finance packages still import bank activity from OFX, even when the bank itself only offers ISO 20022 camt.053. This converter takes the <Ntry> entries from a camt.053 statement and writes an OFX 1.0.2 file, with one <STMTTRN> block per transaction, so an OFX import screen can read the activity without a manual rebuild.

The OFX output uses the same mapping as the rest of the finance converters on this site. Each transaction gets a posted date, a signed amount (DEBIT for money out, CREDIT for money in), a name taken from the remittance or counterparty, and a stable transaction id. The conversion runs in your browser, so the camt.053 file is not uploaded.

Key features

• Writes an OFX 1.0.2 SGML file with a header, a bank account block and one STMTTRN block per entry.
• Signs amounts with the DEBIT and CREDIT transaction types and the matching TRNAMT sign.
• Keeps the bank reference as FITID and makes duplicate references unique.
• Shows the first rows in a preview before you download the .ofx file.
• Runs in the browser with no account and no upload.

About the CAMT.053 XML to OFX format

OFX is a bank-statement container with a header, a sign-on block and then a list of statement transactions. Each transaction needs a type, a posted date in YYYYMMDD form, an amount and a unique FITID. The converter writes these from the camt.053 fields: the booking date becomes DTPOSTED, the signed amount becomes TRNAMT, and the account servicer reference is used as the FITID when it is unique.

OFX names are limited to 32 characters. When a camt.053 remittance line is longer, the converter keeps the first 32 characters in NAME. If the entry has no memo of its own, the full text goes to MEMO so nothing is lost. The bank identifier in the header defaults to 3000 and can be changed in the form.

How it works

The converter first reads each camt.053 entry into a row with a date, description, signed amount and reference, using the same rules as the camt.053 to CSV converter. It then writes those rows as STMTTRN blocks, escaping characters such as & and < so the file stays valid.

The bank reference is always used as the FITID. Repeated references in one file receive a numeric suffix so that each FITID is unique. The suffix is applied in file order, so the first occurrence keeps the original reference.

Common use cases

• A small firm receives camt.053 from its bank but its accounting software only imports OFX.
• A bookkeeper tests an import template with a converted statement before loading a full month of activity.
• A household finance tool needs a file it can read, and the user only has the bank’s ISO 20022 export.

How to use this tool

1. Download the camt.053 statement from your bank for the account and period you need.
2. Open the camt.053 to OFX converter and upload the XML or paste it.
3. Check the preview: the number of STMTTRN blocks should match the entries you see in the bank portal.
4. Download the .ofx file and import it into your accounting software, then confirm the totals.

Example

<Ntry><Amt Ccy="EUR">39.99</Amt><CdtDbtInd>DBIT</CdtDbtInd>
<BookgDt><Dt>2026-05-03</Dt></BookgDt><AcctSvcrRef>BK-1001</AcctSvcrRef>
<RmtInf><Ustrd>Invoice 4411</Ustrd></RmtInf></Ntry>

<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20260503
<TRNAMT>-39.99
<FITID>BK-1001
<NAME>Invoice 4411
</STMTTRN>

Tips for best results

• Leave the bank identifier at 3000 unless the import screen asks for a specific number. The value is written to the FID and INTU.BID tags.
• Import into a test company or a copy of the ledger first. Many importers use the FITID to skip transactions they have already loaded, but that behaviour depends on the software, so check it with a small file.
• Compare the total of the TRNAMT values with the closing balance on the bank statement before you import.
• Keep the original camt.053 file. The OFX is a derived copy and cannot be turned back into the bank’s own message.

Common pitfalls

Trusting the placeholder header values. The currency is the first Ccy attribute in the file, and if none is found, USD is written with no warning. The account number is always 00000000 and the ledger balance always 0.00, so compare the closing balance with the <Bal> block in the camt.053 file instead of the OFX.

Expecting a category or account code. OFX has no category field, so the CSV-style category is not written.

Importing a camt.053 that holds several accounts into one OFX. Each account needs its own file, because OFX statements are per account.

Relying on the time of day. DTPOSTED is written as midnight of the booking date (YYYYMMDD000000), so the OFX holds no time of posting and late-evening entries keep the booking date the bank reported.

Frequently asked questions

For more background on data formats and conversion workflows, read our format guides.