Directory "Email Accounting Records" — Technical Description

1. Identification of the Object

Purpose. The catalog stores and manages the settings for connecting to mail servers for sending (SMTP) and receiving (IMAP/POP3) emails directly from 1C. The records are used by accountants, managers, and administrators for integration with external mail services (Gmail, Yandex, corporate Exchange, etc.). An account can be shared (available to all users) or personal (linked to a specific user via the attribute AccountOwner). Auto-detection of parameters by email address, validation of settings, and secure storage of passwords in the protected storage of 1C are supported.

This is a service (infrastructure) catalog. It does not participate in accounting and tax accounting, does not generate entries, and is not related to tax rates of the RK. However, printed forms and electronic documents (ESF, SCT, reconciliation acts) are sent to counterparties through it.

Where to find in 1C:

• Navigation link: e1cib/list/Catalog.EmailAccounts
• Interface: section "Administration" → "Mail Settings" (or "Organizer" → "Mail" depending on the interface variant).

2. Header Attributes and Table Parts

2.1 Header Attributes

Standard attributes of the catalog: Name (representation of the account in lists), Code, DeletionMark, Predefined. Usually, there is a predefined element SystemAccount — a technical record for system mailings (error reports, notifications of scheduled tasks).

Passwords in the attributes of the catalog are not stored in plain text. SMTP and incoming mail passwords are recorded in a secure storage (CommonSettingsStorage / secure data storage of BSP) with a key linked to the account.

2.2 Table Parts

Table parts are absent for the object — all settings are placed in the header attributes. One account describes one connection (the pair "incoming server + outgoing server").

3. Forms

The element form is usually built dynamically: fields for SMTP login, ports, and SSL are revealed in "Manual Setup" mode; in simple mode, the user only inputs the address and password.

4. Key Procedures of Modules

Evidence with source code (BSL) for this version is not attached. Below are standard handlers of this type of object in BSP (subsystem "Email"/"Working with Email Messages"). Specific signatures and lines require verification with release 3.0.74.2.

Object Module (ObjectModule):

• FillProcessing(FillingData, FillingText, StandardProcessing) — filling default parameters (timeout, SSL flags) for a new element.
• BeforeWriting(Refusal) — normalization of the address, checking the consistency of flags (e.g., receiving enabled → incoming server and protocol specified).
• CheckFilling(...) (override) — control of mandatory fields EmailAddress, servers, Timeout.

Element Form Module:

• OnCreateOnServer(...) — reading passwords from secure storage, setting visibility of manual setup fields.
• CheckAccountSettings(Command) → server procedure for test connection: sets InternetMail/InternetMailProfile, attempts connection to SMTP and IMAP/POP3, returns result to the user.
• BeforeWritingOnServer(...) — writing passwords to secure storage (not to attributes).
• Handlers OnIncomingMailProtocolChange, OnUseSecureConnectionChange… — auto-insertion of standard ports (993/995/143/110, 465/587).

Common modules of the subsystem (standard logic points):

• WorkingWithEmailMessages / WorkingWithEmailMessagesServer — creating InternetMailProfile from the account, forming and sending InternetMailMessage.
• WorkingWithEmailMessagesService — auto-detection of servers by domain, access to secure password storage, connection check.

5. Posting and Movements

The catalog is not posted and does not generate movements in registers. This is a configuration object; it has no posting mechanism, accumulation/summary registers as a registrar, and, accordingly, does not create accounting entries.

Therefore, the standard chart of accounts of the RK and tax rates of Kazakhstan 2026 are not applicable to the object itself. The account is merely a transport: it sends emails and electronic documents, the amounts and taxes of which are calculated in source documents. For context, the "combat" parameters of RK-2026, appearing in sent documents (invoice/ESF, act):

• VAT rate 16% (account 3130 "VAT payable"); sales — 6010, cost of goods sold — 7010, accounts receivable from customers — 1210, cash — 1030, goods — 1330, payables to suppliers — 3310.
• MPR = 4,325 ₸, MZP = 85,000 ₸; basic deduction for individual income tax — 30 MPR/month (not more than 360 MPR/year).
• IIT 10% up to 8,500 MPR of annual income and 15% above; OPE 10% (base ceiling 50 MZP), OPEA 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%.

These numbers are generated in the corresponding accounting documents, and this catalog only delivers their printed/electronic representations to the recipient. The currency of calculations is tenge (₸).

6. Related Objects and Input on the Basis

Input on the basis for this catalog is not provided (service object).

Using objects and mechanisms:

• Sending printed forms by email — from any document (Sale, Invoice, Reconciliation Act) through the "Send by Mail" form, the account with UseForSending = True is selected.
• Report mailing (ReportMailing) — scheduled sending of reports uses the specified account.
• Electronic documents of the RK — sending/acknowledgment of ESF (IS ESF) and SCT to counterparties can use the mail account as a notification channel (main exchange occurs through IS ESF, but notification emails and accompanying documents are sent via SMTP).
• Interactions / Exchange with counterparties — incoming emails (IMAP/POP3) are linked to counterparties and documents.
• Scheduled tasks "Sending outgoing emails" and "Receiving incoming emails" work with all active accounts.
• Catalog.Users — attribute AccountOwner (personal accounts).
• Secure data storage (SecureDataStorage) — password storage.

7. Extension Points

• Configuration extension: adding attributes (e.g., default signature, OAuth2 token), overriding handlers BeforeWriting, CheckFilling via &Instead/&Before/&After.
• Element form: enhancement of connection check, adding support for OAuth2 (Gmail/Microsoft 365) instead of password authentication, additional domain validation.
• BSP programming interfaces: overridable modules of the "Email" subsystem (WorkingWithEmailMessagesOverridable) for configuring the list of auto-detection domains, rules for profile formation, and error handling for sending.
• Event subscriptions: BeforeWriting/OnWriting of the catalog — for example, auditing changes to server settings, automatic connection test after changing critical fields.
• Additional processing/reports (BSP "Additional Reports and Processing"): mass checking of account functionality, export/import of settings.
• Rights...