Convert CAMT.053 to BAI2: BAI2 v2 cash management

What the download contains

Produce representable BAI2 v2 or request an evidence-package-v1 ZIP with an additional record of omissions.

How to convert

Choose the original CAMT.053 XML, select the destination/profile, inspect it free of charge, review warnings and only then start a trial or paid conversion.

Important bank statement checks

CAMT.053 .001.01 through .001.14 are not interchangeable: acceptance depends on the actual XML schema, bank semantics, balances and target representability. Neither a successful parse nor a ZIP proves bank certification.

Trial, credits and privacy

A verified account has three successful trial conversions. Paid conversions use prepaid credits without a subscription; failed conversions do not use credits. Input limits depend on the route and the current commercial contract. Original financial contents are not published in these pages.

Questions before importing

Will every file in this format convert?

No. Free CAMT.053 inspection distinguishes a valid XML schema from the meaning of the banking data, balance consistency and what the target can represent.

Is the output certified by the bank or guaranteed to import?

BAI2 requires actual transaction type codes and bank evidence. Pending or unsupported facts cannot be silently rewritten.

Which CAMT.053 documents can become BAI2?

Only documents whose banking meaning fits the strict BAI2 v2 writer. Individual BookgDt, detailed TxDtls, reversals, pending transactions and inconsistent periods may be rejected. There is no dedicated CAMT BAI2-export inspection endpoint and no checkbox to change XML BOOKED status.

Can I export any CSV, Excel or CAMT.053 statement to BAI2?

No. Only BAI2 v2 (2005) with a representable set of actual financial facts is supported. CSV/XLSX may use canonical or explicit mapping; CAMT.053 is a strict subset. Proprietary BAI formats and universal conversion are not promised.

Does ValidConvert assign BAI2 type codes or bank dates automatically?

No. BAI2 transaction type 16 codes must come from actual source evidence or explicit manual declarations. The bank as-of date and time are not the same as technical file creation; missing facts are never filled from descriptions or credit/debit signs.

Can I force pending CAMT.053 entries to BOOKED?

No. CAMT.053 entry statuses come from the XML and cannot be overridden by a browser checkbox. For CSV/XLSX only, a distinct per-statement BOOKED attestation can be made if the person can genuinely verify it.

Are unsuitable files charged for an output?

A rejected conversion is not a successful charge. Successful web or API output follows prepaid credits by original input size, normally one credit per started 10,000,000 bytes. A free preparation inspection is not available for CAMT.053 BAI2 output in the current backend.