XLSX to BAI2 v2 converter

XLSX → BAI2

Convert a supported financial workbook to BAI2 v2 after checking account identity, statement scope, banking dates and transaction type evidence.

Start converting Browse converters

Purpose

What this converter does

The Excel import reuses the approved canonical workbook or MAPPED_V1 sheet mapping. The SHA-256 covers the original XLSX binary; confirmed bank identifiers remain text with leading zeroes intact.

Workflow fit

When this route is useful

For accounting or treasury teams receiving structured XLSX extracts that must be exchanged with a downstream system expecting BAI2 v2.

Implementation note

What to expect

Not all sheets or cell types are supported. Numeric account identifiers, formulas and incompatible dates may be rejected. Mapping a sheet does not produce a verified bank manifest; genuine account, statement and entry identities must still be established.

BAI2 v2

BAI2 v2 output: prerequisites and limitations

What happens to Excel account numbers and formulas?

The original XLSX bytes are submitted to Java and account IDs must retain leading zeroes as text. Numeric identifiers, unsupported formulas or other incompatible cell structures may fail. Selecting a worksheet never proves the bank account or statement identities.

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.

Before uploading a BAI2 export sourceThis is a conservative writer, not an XML-to-text formatter. Transaction booking dates, detailed CAMT movements and unverified account identities can make a file non-representable. No opening balance, as-of date or bank type code is invented.

Related converters

Explore other production-ready routes connected to this format.

XLSXMT940

Production readygeneric-v1