Zengin Bank File Format Validator
Audit fixed-width Zengin (.txt) files for field length violations, invalid Zenkaku characters in Hankaku fields, and trailer hash total mismatches.
Zengin File Validator
Validate Zengin format (.txt) files field by field. Detects full-width characters in half-width fields, fixed-length violations, and trailer total mismatches.
Paste the content of a Zengin (.txt) file into the textarea above, or load the sample to try it out.
Common Problems
Why does my Zengin file get rejected with an Invalid Format error?
The most common causes are full-width characters in half-width fields and records that are not exactly 120 bytes. Use this validator to identify the exact line and field causing the failure. The error list shows you the specific violation so you can fix just that field rather than rebuilding the entire file.
How do I check whether full-width characters are in half-width Zengin fields?
Paste the file content and click Validate. The tool scans recipient names, bank names, and branch names in every data record and flags any that contain full-width characters. Legacy ERP exports and copy-pasted data from spreadsheets are the most frequent sources of Zenkaku contamination in Zengin files.
How do I fix a mismatch between the trailer total count and actual data records?
The trailer record (type 8) must report exactly the same number of data records (type 2) that appear in the file. This validator compares both counts automatically and flags a mismatch if they differ. The most common cause is manually adding or deleting rows after the file was exported from an ERP system.
What causes Zengin records to be the wrong length?
Each Zengin record must be exactly 120 single-byte characters. Records longer or shorter than 120 characters cause the entire file to be rejected. Common causes are pasting from Excel which strips trailing spaces, line-ending characters being included in the field count, or fields being padded with full-width spaces instead of half-width spaces.
What are the valid account type codes in Zengin format?
The Zengin specification allows only three account type values: 1 for ordinary savings (普通預金), 2 for current account (当座預金), and 4 for savings account (貯蓄預金). Any other digit will cause the record to be rejected. Fixed-term deposits (code 3) are not valid targets for bank transfer files.
Workflow
What is Zengin Bank File Format Validator?
Legacy ERP systems and payroll software often output Zengin files with subtle formatting issues that only surface at upload time: full-width Katakana in half-width fields, records that are not exactly 120 characters, or trailer records whose total count does not match the actual data rows. By then, the entire batch fails silently.
This validator parses each Zengin record by field — header (type 1), data (type 2), trailer (type 8), and end (type 9) — and flags every violation with a line number and field name so you can fix it before it reaches the bank portal.
How to use Zengin Bank File Format Validator
Paste the raw text content of a Zengin .txt file into the textarea and click Validate. The tool checks each record type individually and lists all field-level violations. Click any error row to inspect that record's parsed fields. Use the Copy auto-fixed button to get a version with full-width ASCII, digits, spaces, punctuation, and plain (non-voiced) Katakana converted to half-width — Katakana with a dakuten/handakuten mark is left untouched since converting it changes the field's byte length.
Example
Scenario: A payroll file exported from an old ERP contains a data record where the recipient name field holds full-width Katakana.
Input: ...サトウ ハナコ (invalid — full-width, no voicing marks)
Result: Line 3 · Recipient Name: Contains Zenkaku characters
Copy auto-fixed converts it to: ｻﾄｳ ﾊﾅｺ (fixed, same character count)Use Cases
1. Validating Zengin payroll files exported from legacy ERP or Excel before batch upload.
2. Diagnosing 'Invalid Format' rejections from Mizuho, MUFG, or other bank portals.
3. Auditing third-party vendor payment files for encoding compliance.
4. Verifying trailer record hash totals after manual row additions or deletions.
FAQ
Which Zengin record types does this validator support?
All four standard record types: header (1), data (2), trailer (8), and end (9). Each is parsed against the standard Zengin field layout with individual field-level checks.
Can this tool fix Zenkaku characters automatically?
The Copy auto-fixed button converts full-width ASCII letters, digits, spaces, and punctuation, plus plain full-width Katakana with no voicing mark (ア → ｱ), to half-width. It deliberately skips Katakana that carries a dakuten or handakuten (voicing) mark — for example ダ in 「ヤマダ」 — because converting a voiced character splits it into two half-width characters (ﾀ + ﾞ), which changes the field's byte length and would silently shift every field after it in a fixed-width record. For those, use the dedicated Zenkaku/Hankaku converter and re-check the field length by hand afterward. Structural issues like a trailer record count mismatch are outside auto-fix's scope entirely — those require correcting the actual data, not a character-width conversion.
Is it safe to paste payroll or banking data here?
Yes. All validation runs locally in your browser. No data is transmitted to any server. Your recipient names, account numbers, and transfer amounts stay entirely on your machine.