What is
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
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 characters converted to half-width.
Example
Example
Scenario: A payroll file exported from an old ERP contains data records where the recipient name field holds full-width Katakana.
Input: ...0001ﾔﾏﾀﾞ ﾀﾛｳ (correct) vs. ヤマダ タロウ (invalid)
Result: Line 4 · Recipient Name: Contains Zenkaku charactersCommon use cases
Common 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.
Frequently asked questions