--- title: "Document \"ПисьмоОбменСБанками\" (Letter with bank) — Accounting for Kazakhstan 3.0" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-23 canonical: https://buhgpt.kz/suraqtar/dokument-pismoobmensbankami-pismo-s-bankom-buhgalteriya-d-en source: BuhGPT --- # Document "ПисьмоОбменСБанками" (Letter with bank) — Accounting for Kazakhstan 3.0 > **TL;DR:** 1. Object identification Parameter Value Object type Document ( Документ ) Name ПисьмоОбменСБанками Full name Документ.ПисьмоОбменСБанками Synonym “Letter to bank” Configuration Accounting for Kazakhstan, revision 3.0 (version 3.0.74.2) Posting Not posted (see section 5) Where --- 1. Object identification Parameter Value Object type Document (Документ) Name ПисьмоОбменСБанками Full name Документ.ПисьмоОбменСБанками Synonym “Letter to bank” Configuration Accounting for Kazakhstan, revision 3.0 (version 3.0.74.2) Posting Not posted (see section 5) Where to find (interface) Section “Electronic interaction” → “Letter to bank” Navigation link e1cib/list/Документ.ПисьмоОбменСБанками Purpose. The document is intended for registering and processing electronic correspondence between the organization and the bank within the electronic interaction system (technology 1С:DirectBank). Through it messages, notifications, requests and responses are sent and received: free-form letters, currency control documents, accompanying correspondence for payment orders. The document is used daily by accounting and treasury users when sending and receiving electronic documents. The list displays incoming and outgoing letters with the ability to filter by organizations, banks and letter types. The document implements precisely correspondence (exchange of letters), not monetary transactions. Financial movements on the settlement account (account 1030 “Cash in current bank accounts”) are generated by payment documents (payment order, payment warrant), not by a letter. 2. Header attributes and tabular sections Below are the field purposes according to the standard 1С:DirectBank electronic exchange document model. The specific set of attributes should be verified in the configurator of the particular release. 2.1. Header attributes Attribute Type (standard) Purpose Номер String Number of the letter document in the information base Дата Date Date of letter registration Организация СправочникСсылка.Организации Organization — party to the exchange Банк / БанковскийСчет СправочникСсылка.Банки / БанковскиеСчета Recipient/sender bank and the associated bank account НастройкаОбмена СправочникСсылка.НастройкиОбменаСБанками Active 1С:DirectBank exchange setting through which transfer occurs ВидПисьма / ТипСообщения Enumeration Type of correspondence (request, notification, response, free-form letter) Направление Enumeration (Incoming/Outgoing) Direction of the letter Тема String Subject/heading of the message Текст / СодержаниеПисьма String (multiline) Body of the letter ПисьмоОснование ДокументСсылка.ПисьмоОбменСБанками Original letter when composing a response (scenario 3.3) ДокументОснование ДокументСсылка Related document (e.g., payment order — scenario 3.4) Статус / СтатусОбмена Enumeration Exchange state: prepared, sent, delivered, error, etc. Прочитано Boolean Flag indicating an incoming letter has been read (scenario 3.2) ИдентификаторДокументаОбмена / GUIDСообщения String/UniqueIdentifier Message identifier on the DirectBank service side Автор / Ответственный СправочникСсылка.Пользователи User who composed the letter 2.2. Tabular sections Tabular section Key columns Purpose Вложения / Файлы File name, Data (ValueStorage), Type Files and electronic documents attached to the letter Подписи / ЭП Certificate, Owner, Verification status, Timestamp Electronic signatures of the letter and the results of their verification (scenario 3.6) The exact list of attributes and tabular sections is version-specific — verify against the object metadata in your release. 3. Forms Form Purpose ListForm (Форма.ФормаСписка) Main list of incoming/outgoing letters with filtering by organizations and banks. Executes ЗаполнитьСпискиОрганизацийИБанков — selection of available DirectBank exchange settings supporting letters ПисьмоВБанк (Форма.ПисьмоВБанк) Outgoing letter form. The ОформитьШапкуФормы method checks for active exchange settings for a new letter Подписи (Форма.Подписи) Working with electronic signatures of the letter: viewing certificates, verifying electronic signatures. The ОткрытьСертификат method opens the certificate selected in the list Incoming letter / viewing form Viewing a received letter, marking it “Read”, composing a response 4. Key module procedures The following code locations are confirmed by evidence (release 3.0.68.1, message texts — verbatim from the configuration): Procedure / method Location What it does ЗаполнитьСпискиОрганизацийИБанков Форма.ФормаСписка Builds lists of available organizations/banks based on DirectBank exchange settings. If the result is empty (НЕ ТаблицаРезультата.Количество()), it displays: “No 1С:DirectBank exchange setting with letter-sending support was found.” ОформитьШапкуФормы Форма.ПисьмоВБанк When creating a new letter (ЭтоНовый И НЕ ТаблицаРезультата.Количество()) checks active exchange settings; if none exist, it displays: “There are no active 1С:DirectBank exchange settings with Sberbank.” ОткрытьСертификат Форма.Подписи Opens the selected electronic signature certificate. If nothing is selected (Элементы.ЭП.ТекущиеДанные <> Неопределено) it displays: “Select a certificate in the list of installed signatures.” Standard handlers (by object type — non-posting exchange document) - ОбработкаЗаполнения (object module) — filling attributes when entering on the basis of (payment order, incoming letter). - ОбработкаПроверкиЗаполнения — checking mandatory fields (organization, bank, exchange setting) before writing. - ПередЗаписью / ПриЗаписи (object module) — recording the exchange status, updating message identifiers. - Client form handlers: ПриСозданииНаСервере, ПриОткрытии — initialization of visibility and availability of elements depending on the direction and status of the letter. - DirectBank integration procedures: sending a message, synchronizing statuses and loading incoming letters (scenario 3.5), verifying electronic signatures (scenario 3.6), exporting data for technical support (scenario 3.7) — implemented in the common modules of the bank exchange subsystem. 5. Posting and movements The document is non-posting. The object metadata lacks a register_records section (register movements), and the modules have no ОбработкаПроведения procedure. As a result: - The document does not generate accounting entries and does not create records in accumulation/information registers as part of its own posting. - It records the fact and content of correspondence with the bank, not a business transaction. Accordingly, the letter does not affect such accounts of the standard RK chart of accounts as: Account Name 1030 Cash in current bank accounts 1210 Short-term accounts receivable from customers 3310 Short-term accounts payable to suppliers Cash and settlement transactions (movements on 1030, mutual settlements on 1210/3310, revenue recognition 6010, cost of sales 7010, VAT on account 3130 “VAT payable” at the rate of 16%) are reflected by dedicated documents (payment orders/warrants, sales, receipts), as well as by electronic documents ESF (IS ESF) and SNT. The letter to the bank merely accompanies these transactions with correspondence. If an audit of movements is required, they should be sought in the related financial documents, not in the letter. 6. Related objects and entry on the basis of Main work scenarios No. Scenario When applied 3.1 Sending a new letter to the bank Free-form request/notification/document outside standard payment operations 3.2 Viewing an incoming letter and marking it as read A new letter has been received from the bank 3.3 Replying to a letter from the bank Response linked to the original letter (ПисьмоОснование) 3.4 Creating a letter on the basis of a payment order Additional letter related to a specific payment 3.5 Synchronizing with the bank and receiving new letters Loading new letters and updating statuses of sent ones 3.6 Verifying electronic signatures of the letter Verifying authenticity of an incoming/correctness of an outgoing letter 3.7 Saving information for technical support On an exchange error or when transferring data to technical support Related objects - Bank exchange settings (1С:DirectBank) — a mandatory source of connection parameters; without an active setting, creating/sending a letter is blocked. - Catalogs “Organizations”, “Banks”, “Bank accounts” — header attributes. - Payment order — the basis document for the letter (scenario 3.4, ДокументОснование). - ПисьмоОбменСБанками (itself) — the “letter → response” chain via ПисьмоОснование (scenario 3.3). - Electronic signature key certificates — used in the “Подписи” form for signing and verification. Entry on the basis of - From a payment order → “Letter to bank” (scenario 3.4): organization, bank and exchange setting attributes are carried over from the basis document. - From an incoming letter → response letter (scenario 3.3): ПисьмоОснование is filled, subject/addressee are inherited. 7. Extension points - Configuration extensions (form modules): intercepting ЗаполнитьСпискиОрганизацийИБанков, ОформитьШапкуФормы, ОткрытьСертификат via &Вместо/&После for custom filtering of exchange settings or additional validation. - Object module: extending ОбработкаЗаполнения (rules for entry on the basis of), ОбработкаПроверкиЗаполнения (additional mandatory fields), ПриЗаписи (integration hooks, exchange logging). - Event subscriptions (document ПередЗаписью/ПриЗаписи) — for external auditing of correspondence without interfering with the object module. - Additional attributes and information (properties mechanism) — for marking letters without changing the metadata. - Common modules of the exchange subsystem — points for modifying the synchronization logic (scenario 3.5) and electronic signature verification (scenario 3.6). Since the document is non-posting, adding your own movements (registers) via an extension is possible but atypical: use dedicated posting documents to reflect financial transactions, and keep the letter as a means of correspondence. Typical errors (verbatim from code, release 3.0.68.1) 1С message Where it occurs Condition in code No 1С:DirectBank exchange setting with letter-sending support was found. Форма.ФормаСписка / ЗаполнитьСпискиОрганизацийИБанков НЕ ТаблицаРезультата.Количество() There are no active 1С:DirectBank exchange settings with Sberbank. Форма.ПисьмоВБанк / ОформитьШапкуФормы ЭтоНовый И НЕ ТаблицаРезультата.Количество() Select a certificate in the list of installed signatures. Форма.Подписи / ОткрытьСертификат Элементы.ЭП.ТекущиеДанные <> Неопределено If you see such a message, check the condition in the third column. The message texts and procedure names require verification when moving to a different release — they are version-specific. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_