CAMT.053 to QBO Converter
Convert an ISO 20022 CAMT.053 statement into a QuickBooks Web Connect (.qbo) or .ofx file. Free, no signup, no size limit.
camt.053 version
Why CAMT.053 XML will not open in QuickBooks
CAMT.053 is the ISO 20022 BankToCustomerStatement message that has replaced MT940 across
SEPA and most of Europe. It is thorough — booking date, value date, bank transaction codes, remittance
info are all present — but it is XML, and QuickBooks Web Connect only accepts OFX SGML wrapped as
.qbo. There is no built-in path from one to the other, so a CAMT.053 file downloaded from
your bank's portal sits unusable until it is converted.
The detail that trips up naive conversions is the sign: CAMT.053 stores every Amt as
positive and keeps direction in a separate CdtDbtInd element (CRDT or
DBIT). This converter applies that indicator before handing rows to the OFX builder, so
debits post as negative TRNAMT values the way QuickBooks expects.
What gets built into the .qbo / .ofx file
- FITID from AcctSvcrRef / EndToEndId — the bank's own reference or the payment's end-to-end ID becomes a unique FITID, so re-importing the same statement does not create duplicate transactions.
- TRNTYPE from BkTxCd and remittance text — bank transaction codes and unstructured remittance info are matched to OFX transaction types (XFER, DIRECTDEBIT, FEE, INT, DEP).
- Namespace-agnostic parsing — camt.053.001.02 through .08 all parse the same way, since matching is done on element local names rather than a fixed namespace.
- <INTU.BID> caveat — QuickBooks Desktop only accepts a .qbo file when INTU.BID matches a financial institution it recognizes. If you don't have your bank's value, use the .ofx download instead, which has no such requirement and imports into Quicken, Xero, Wave, MoneyMoney and most accounting tools.
Balances and multi-account statements
A CAMT.053 document can contain several Stmt blocks — one per account — in a single file.
Each account here becomes its own OFX <STMTTRNRS>/<STMTRS> block with
its own <LEDGERBAL> taken from the closing balance (CLBD) entry, so
QuickBooks can flag a mismatch against the balance it already has on file.
Frequently asked questions
Is my statement uploaded anywhere?
No. Parsing runs through the browser's built-in XML parser and OFX/QBO generation happens locally too. There is no server and no upload endpoint — check your browser's network tab to confirm.
Which CAMT versions are supported for QBO export?
All of camt.053.001.02 through .001.08, the same coverage as the CSV/Excel converter, since the underlying parser is identical and only the export step differs.
Why did some entries come through with a generic TRNTYPE?
If a bank transaction code or remittance description doesn't match a known keyword, the converter falls back to a plain DEBIT or CREDIT type based on the CdtDbtInd sign — QuickBooks still imports it correctly, just without a more specific category.
My .qbo file is rejected by QuickBooks Desktop — what now?
This is almost always the <INTU.BID> value not matching a bank QuickBooks recognizes. Use the .ofx download instead — same transactions, no financial-institution check.