"Account Correspondence Directory" (Catalogs.AccountCorrespondence)

1. Identification

Purpose. The catalog stores standard account correspondence pairs for accounting and metadata about the context of their application (document type, operation type, form tab, menu section). It serves as a supporting base for transaction templates: when entering primary documents and manual operations, the quick input mechanism substitutes a pre-configured "Debit - Credit" pair and the text of the operation, speeding up data entry and reducing errors.

Users are accountants and chief accountants. Frequency of access ranges from daily to weekly, depending on the intensity of primary document input.

Where to find in 1C: section "Operations" → "Account Correspondences". Navigation link: e1cib/list/Catalog.AccountCorrespondences

2. Attributes and Table Parts

2.1 Header Attributes

Along with the attributes, standard fields of the catalog are available: Code, Name, DeletionMark, Predefined, Reference.

2.2 Table Parts

Table parts are absent. The catalog has a flat structure: each element is one pair of corresponding accounts with metadata about the context of application. The implementation of the "one record = one template transaction" scheme simplifies quick selection and substitution.

2.3 Key Characteristics of the Data Model

• The correspondence describes one pair of Debit/Credit; composite transactions are assembled from several elements through the mechanism of standard operations.
• The fields DocumentType / DocumentOperationType / DocumentTab form the "context key," by which the mechanism selects appropriate correspondences for a specific form.
• UsageMoment is a service field for ranking by frequency/recency.

3. Forms

A separate element form is not highlighted as key in the delivery — editing is performed in the list form or in auxiliary dialogs of the standard operations mechanism. If necessary, the element form is generated automatically by the platform.

4. Key Module Procedures

The attached evidence does not provide the text of the modules (BSL) — standard handlers for a catalog of this purpose are provided. Specific signatures are clarified in the configurator version 3.0.74.2.

Object Module (ObjectModule):

• FillProcessing(FillData, StandardProcessing) — pre-fills DebitAccount/CreditAccount/Content when creating correspondence from the document context.
• BeforeSaving(Refusal) — controls the filling of accounts and normalizes string keys of the context.

List Form Module (ListForm):

• OnCreateOnServer(Refusal, StandardProcessing) — configures selection by DocumentType / DocumentOperationType / DocumentTab, passed as parameters of the form.
• Select(Element, SelectedRow, Field, StandardProcessing) — returns the selected correspondence to the calling document and updates UsageMoment.
• Handlers for dynamic selection and sorting of the list (by Menu, by recency of use).

Common Modules (interaction):

• Procedures for quick input of standard operations, which read the catalog, select appropriate correspondences by the context key, and substitute them into the document/manual operation.

If the object module in your build is empty — all selection logic is moved to common modules of the standard operations mechanism; this is version-specific and requires verification in the specific delivery 3.0.74.2.

5. Posting and Movements

The catalog is not a document and is not posted — it does not generate its own movements in the registers. Its role is to serve as a source of templates for transactions, which are created by documents and manual operations and enter the accounting register (BusinessAccounting) in the format Debit/Credit according to the standard chart of accounts of the RK.

Below is how selected pairs from the catalog turn into actual transactions. All accounts are from the standard chart of accounts of the RK; numbers are according to Kazakhstan norms 2026 (VAT rate 16 %).

Example 1. Receipt of goods from the supplier (context: DocumentType=IncomingInvoice, DocumentOperationType=GoodsReceipt), amount of goods 1,000,000 ₸, VAT 16 %:

Example 2. Sale of goods to the customer, selling price 1,500,000 ₸ + VAT 16 %, cost 1,000,000 ₸:

Example 3. Payment from the customer to the current account:

Example 4. Payment to the supplier from the current account:

Correspondence of accounts from evidence to the standard chart of the RK: 1210 — short-term receivables from customers, 1030 — cash in current accounts, 1330 — goods, 3310 — payables to suppliers, 3130 — VAT payable, 6010 — revenue from sales, 7010 — cost of sales.

6. Related Objects and Input Based On

• Chart of accounts Standard — source of values for the attributes DebitAccount and CreditAccount.
• Accounting documents (incoming/outgoing invoices, bank and cash documents, sales, etc.) — consumers of the catalog: when entering, they select correspondences by the context key.
• Operation (accounting), manual operations — use correspondences as ready-made transaction templates.
• Accounting register BusinessAccounting — final receiver of transactions assembled from correspondences.
• Electronic documents of the RK — operations of sales/purchases formed based on such transactions serve as data sources for electronic invoices (ESF) (ESF IS) and SNT; the catalog itself does not directly participate in the issuance of ESF/SNT but ensures correct correspondence for VAT (account 3130).

Input Based On. The catalog is not an object of basis and does not participate in "Input Based On" chains. Feedback is implemented through the quick input mechanism: from the document form, the ListForm opens, the selected pair returns to the document, and UsageMoment is updated.

7. Extension Points

• User filling. Adding custom correspondences for atypical operations of the organization (e.g., specific revenues/expenses with correct VAT binding at a rate of 16 %).
• Additional attributes/information through the chart of characteristics (without removing the configuration from support), if it is necessary to store additional classification attributes of correspondences.
• Configuration extension (Extension). Redefining the list form (additional selections, columns), adding handlers BeforeSaving/FillProcessing in the object module, inserting code into selection procedures via &Insert/&ChangeAndControl.
• Subscriptions to events on the record of the catalog element — for auditing changes to standard correspondences.
• Integration with the standard operations mechanism — extending the selection logic by context key (DocumentType / DocumentOperationType / DocumentTab) for industry-specific needs.

Version-specific and requires verification in 3.0.74.2: the exact composition of module procedures and whether the selection logic has been moved to common modules or to the list form module.