Zengin Format Test Data
Use bulk transfer dummy data inspired by the Zengin Association's 120-byte fixed-length bulk transfer format to test file generation and parsing for payroll, accounting, and fintech systems together.
Compliance disclaimer
This content is a technical sample and is not intended for actual submission to the Zengin network or real fund transfers. Header/trailer records are not included, so coordinate with your systems team and bank before production use.
Bulk transfer data involves fixed-length format and character-encoding constraints, which makes preparing test data time-consuming on its own. A standard schema lets you reproduce the key use cases safely.
The Zengin format schema covers everything from payee details to the 120-byte fixed-length data record. Below are representative fields and references. Field names stay in Japanese even in the en-US locale, so they work directly for payroll/accounting file validation.
| Field | Description | Reference |
|---|---|---|
| 振込ID | Internal management ID | An auxiliary field for managing test data; not part of the Zengin format itself |
| 振込指定日 | Transfer execution date (YYYY-MM-DD) | Set via the transferDate parameter |
| 銀行コード | Financial institution code (4 digits) | Uses real codes published by the Zengin Association; set the target codes with the bankCodes parameter |
| 支店コード | Branch code (3 digits) | A fictional branch code, not intended to match any real branch |
| 預金種目 | Deposit type code | One of three types: 1 = ordinary, 2 = current, 4 = savings |
| 口座番号 | Account number (7 digits) | A fictional account number that always starts with 9, chosen to avoid resembling a real account |
| 受取人名カナ | Payee name (half-width katakana) | Half-width katakana notation that follows the Zengin format rules |
| 振込金額 | Transfer amount | Randomly generated within the amountMin–amountMax range |
| 新規コード | Code indicating a newly registered payee | Adjust the ratio with the newCodeRatio parameter |
| EDI情報 | Extended info for the Zengin EDI system | Toggle output with the includeEdi parameter |
| 状態 | Status such as completed or error | Adjust the share of error records with the errorRatio parameter |
| 全銀レコード | 120-byte fixed-length data record string | A string assembled to match the Zengin Association's bulk-transfer data-record layout |
This schema outputs only the data-record portion; it does not include header, trailer, or end records. If you use it as an actual file, add the header and other records yourself according to the Zengin Association's specification. The character encoding may also need conversion (e.g. to Shift_JIS) — handle that conversion on your own system.
This schema outputs only data records. If you use it as a real file, add the header record, trailer record, and end record yourself, following the Zengin Association's specification.
The generated data is UTF-8 based, so build in and test the conversion to whatever encoding your actual transmission format requires, such as Shift_JIS.
Verify with your real validation logic that the bank-name and payee-name katakana fields fit within half-width katakana and the specified character limits.
Use the errorRatio parameter to mix in intentionally invalid records (bad digit counts, code mismatches) and verify detection and rejection during import.
A. No. This schema generates only the data record (120-byte fixed length). If you send it as an actual file, add the header record, trailer record, and end record yourself, following the Zengin Association's specification.
A. No, the generated data is UTF-8-based text. If you use it as an actual Zengin-format file, perform the character-encoding conversion (e.g. to Shift_JIS), including for the half-width katakana fields, on your own system.
A. Yes — turning on the includeEdi parameter generates records with Zengin-EDI-compatible extended fields (customer codes, etc.), which you can use to test payment-reconciliation logic.
A. Account numbers are generated as fictional numbers that always start with 9 and are not intended to match any real account. Only the bank code uses a real financial-institution code published by the Zengin Association, so treat other fields such as branch code and account number as fictional.
Get bulk transfer data aligned with the 120-byte fixed-length data record and half-width katakana notation as CSV, JSON, or via the REST API. Combine it with invoice and corporate master data to build end-to-end payment-execution test scenarios.
Download a ready-made sample for each schema to check the format before touching the generator.
100-row sample with dummy watermark