| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1211 |
| Technical Name |
pay_zengin_transfer |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1211 |
| Technical Name |
pay_zengin_transfer |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Japan Zengin Domestic Transfer File Generator
Build bank-ready 120-byte Zengin (å ¨éåè¦å®ãã©ã¼ããã) transfer files â ç·åæ¯è¾¼ / 給ä¸æ¯è¾¼ / è³ä¸æ¯è¾¼ â with automatic half-width kana name encoding. No gateway, no per-transaction fees, your data never leaves your database.
Upload directly to your bank's portal
Japanese banks accept payment instructions through the Zengin (å ¨å½éè¡åä¼, Zengin-kyokai) fixed-width file format. This module turns the vendor payments, payroll or bonus runs you already manage in Odoo into a clean, validation-passing Zengin text file that you upload to your bank's cash-management portal. The format and encoding are produced entirely inside your database â nothing is transmitted to any third-party service.
Key features
120-byte fixed-width records
A complete file with a Header (ãããã¼ã¬ã³ã¼ã, ãã¼ã¿åºå 1), one Data record (ãã¼ã¿ã¬ã³ã¼ã, 2) per beneficiary, a Trailer (ãã¬ã¼ã©ã¼ã¬ã³ã¼ã, 8) carrying the independent control totals, and an End record (ã¨ã³ãã¬ã³ã¼ã, 9) â every record exactly 120 single-byte characters, padded to the published JBA column positions.
Half-width kana name encoding
Requestor, bank, branch and payee names are converted to the legal Zengin half-width katakana (åè§ã«ã) character set automatically. Full-width katakana, hiragana and latin input are folded down; voiced and semi-voiced syllables (ã¬, ã, ã´) are decomposed into base kana plus the trailing ï¾ / ï¾ mark, exactly as the JIS half-width code page requires.
Three transfer kinds
Produce General / Accounts-Payable transfers (ç·åæ¯è¾¼, 種å¥ã³ã¼ã 21), Salary transfers (給ä¸æ¯è¾¼, 11) and Bonus transfers (è³ä¸æ¯è¾¼, 12) from the same screen â the kind code is written into the header and the bank routes the file accordingly.
Whole-yen amounts & control totals
Amounts are handled as whole yen (the Japanese yen has no minor unit in domestic transfers) and the trailer's total count and total value are computed exactly as the receiving bank re-derives them, so the file clears validation on the first upload.
Build from vendor bills
A one-click wizard turns selected posted vendor bills into a ready Zengin batch, grouping the amounts due per payee and pulling the bank code, branch code and account number from each vendor's bank account.
Bank-code validation & download
The 4-digit bank code (éèæ©é¢çªå·), 3-digit branch code (æ¯åºçªå·) and 7-digit account number (å£åº§çªå·) are validated on the bank record and every entry, with well-known Japanese banks labelled automatically. The finished file downloads as a Shift_JIS text file ready for upload, with an in-app preview and full chatter audit trail.
Record layout
| Record | Division (ãã¼ã¿åºå) | Length | Carries |
|---|---|---|---|
| Header (ãããã¼ã¬ã³ã¼ã) | 1 | 120 bytes | Kind code, requestor code/name, transfer date, origin bank/branch and charge account. |
| Data (ãã¼ã¿ã¬ã³ã¼ã) | 2 | 120 bytes | Destination bank/branch, deposit type, account number, payee name (kana), amount, customer codes. |
| Trailer (ãã¬ã¼ã©ã¼ã¬ã³ã¼ã) | 8 | 120 bytes | Total record count and total yen amount. |
| End (ã¨ã³ãã¬ã³ã¼ã) | 9 | 120 bytes | File-end marker. |
Deposit & transfer codes
| Field | Codes |
|---|---|
| Transfer kind (種å¥ã³ã¼ã) | 21 General / 11 Salary / 12 Bonus |
| Deposit type (é é種ç®) | 1 Ordinary / 2 Checking / 4 Savings / 9 Other |
| New code (æ°è¦ã³ã¼ã) | 0 Unchanged / 1 First time / 2 Account changed |
| Transfer method (æ¯è¾¼åºå) | 7 Telegraphic / 8 Document |
How it works
- Enter your requestor code/name and origin bank, branch and charge account once in Settings.
- Add the Zengin bank code, branch code, deposit type and kana name on each payee's bank account.
- Create a transfer batch (or build one from posted vendor bills) and add the beneficiary entries.
- Click Generate Zengin File, review the in-app preview, then Download and upload the file to your bank.
Disclosure
This module only builds the Zengin transfer text file for you to upload to your own bank. It transmits nothing to any external service and does not act as a certified intermediary. Compatible with Odoo 18 and Odoo 19, Community and Enterprise.
Screenshots
Transfer Batches
Build From Bills
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module