--- title: "Error: Organization code is not filled in the banking system when exporting a SWIFT file" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-23 canonical: https://buhgpt.kz/suraqtar/oshibka-ne-zapolnen-kod-organizacii-v-bankovskoy-sisteme--en source: BuhGPT --- # Error: Organization code is not filled in the banking system when exporting a SWIFT file > **TL;DR:** In brief: the error "Organization code in the banking system is not filled in" when exporting a SWIFT file occurs because the organization codes in the banking system are not filled in on the organization card, and 1C cannot correctly generate the file. To fix the problem, ope --- In brief: the error "Organization code in the banking system is not filled in" when exporting a SWIFT file occurs because the organization codes in the banking system are not filled in on the organization card, and 1C cannot correctly generate the file. To fix the problem, open the organization card, go to the "Organization codes in the banking system" section, create and save a new entry — after that the codes will be linked to the organization and the export will complete without errors. Why the error occurs A SWIFT file is a payment file in an international format that the bank uses to process transfers (most often currency or international payments). To generate it correctly, the program needs to know under which codes your organization is registered in the banking system. If this reference list on the organization card is empty, 1C cannot insert the required details into the file and interrupts the export with a message about the unfilled code. Typical situations when this happens: - the organization card was filled in manually, and the section with banking codes was simply skipped; - the organization was copied or transferred from another database, but the service reference lists were not carried over; - there are several organizations in the database, and the codes are filled in for the wrong one from which the payment is being generated; - payments in this format had not been exported before, so filling in the section was not required. How to fix: step-by-step procedure - Open the card of the organization on whose behalf the SWIFT file is being generated (the organization settings section / company details). - Make sure the correct organization for the payment is selected — with several legal entities this is critical. - Find the "Organization codes in the banking system" section. - Create a new entry in this section and fill it in with the data provided by your servicing bank. - Save the entry. - Repeat the SWIFT file export — with the codes correctly linked, the error will no longer appear. The values of the codes themselves should not be made up: they are issued by the bank where the account is opened. If you are not sure which values to specify, request them from a bank teller or the bank's customer support — this way you will avoid a repeated error due to incorrect details. If the error recurs after saving Sometimes the message appears again even after the entry has, seemingly, been created. Check the following: - The entry was actually saved. Close and reopen the "Organization codes in the banking system" section and make sure the created row is in place and has not been left in edit mode. - The entry belongs to the correct organization. Make sure the codes are linked specifically to the organization on whose behalf the file is being generated, and not to another legal entity in the database. - The bank/account matches. Check that the entry corresponds to the bank account used for the export — with several accounts, the data may relate to a different bank. - All required fields of the entry are filled in. An empty required field within the entry will also cause 1C to consider the code unfilled. Typical mistakes - Filling in the codes for one organization while generating the payment from another — in multi-company accounting this is the most common cause of the recurring error. - Creating an entry but not clicking "Record"/"Save", so the data is not committed to the database. - Entering codes "by guess" instead of those provided by the bank — the file may be exported, but the bank will not accept it. - Confusing the bank account: filling in codes for one account while exporting a payment for another. - Editing the organization card in a test or outdated copy of the database while working in a different one. What to check - Whether the correct organization is selected in the payment document itself and in the export settings. - Whether the "Organization codes in the banking system" section is filled in for this specific organization. - Whether the entered codes match the data received from the servicing bank. - Whether the entry matches the bank account for which the SWIFT file is generated. - Whether the entry was saved after creation (check by reopening the section). - Whether the database in which the edits are made is current, if you have several copies. Once the organization codes in the banking system are correctly filled in, linked to the right organization and account, and saved, the SWIFT file export should proceed without errors. If the problem persists despite all the checks, it makes sense to clarify the file format requirements with the bank and compare them with the exchange settings in 1C:Accounting for Kazakhstan. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_