CSV → BAI2
Prepare a BAI2 v2 bank statement from structured CSV only when the actual accounts, period, transaction codes and source facts can be justified.
Purpose
The CSV importer uses its approved canonical or MAPPED_V1 mapping flow; canonical files may provide a server-verified statement manifest. Export metadata is bound to the original file and checked by the Java BAI2 writer.
Workflow fit
For finance integrations requiring a BAI2 v2 exchange file when the available source is a verified, structured CSV statement rather than a native BAI2 feed.
Implementation note
Not a one-click converter for arbitrary CSV. Canonical input can reuse the authenticated source manifest; mapped CSV requires accurate expert-declared identities when the backend offers no post-mapping manifest. BAI2 type 16 codes and bank as-of facts are never inferred.
BAI2 v2
No. An exactly canonical CSV can provide identities from an authenticated manifest without selecting the BAI2 converter in inspection. MAPPED_V1 has no post-mapping manifest in this backend; the user must know the exact identities and counts or stop. BOOKED and BAI2 codes remain separate confirmations.
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.
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.
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.
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.
Related converters
Explore other production-ready routes connected to this format.