Directory "Address Abbreviations" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The catalog stores standardized abbreviations of address elements (street → "st.", avenue → "av.", region → "reg.", city → "c." etc.), used when forming and printing addresses in the information database. The values are used when entering address data for counterparties, organizations, warehouses, individuals, and other accounting objects where location needs to be specified. A unified set of abbreviations ensures uniformity in address recording and compliance with address classifiers. Filling the catalog is the task of the administrator/specialist for initial setup; in everyday work, users only select ready-made values.

Where to find:

• Navigation link 1C: e1cib/list/Catalog.AddressAbbreviations
• In the interface: section "Universal mechanisms" → "Address abbreviations".

2. Header Attributes and Table Parts

2.1 Header Attributes

Standard attributes (automatically created by the platform):

• Name — full name of the address element ("street", "avenue", "region");
• Code — unique code of the catalog element;
• service: Reference, DeletionMark, Predefined (if predefined elements are present).

2.2 Table Parts

The catalog does not have table parts. All information is stored in the header attributes of the element.

3. Forms

The catalog contains three forms:

4. Key Module Procedures

BSL code in the reference evidence is not attached, so below is a typical set of handlers for a catalog-classifier of this type. Specific procedure bodies should be viewed in the form modules and the manager module of the specific release.

Element form module (ElementForm):

• OnCreateOnServer — initial setup of field availability/visibility (Name, Abbreviation, Level);
• BeforeSaveOnServer / OnSaveOnServer — control of the correctness of filling before saving;
• field event handlers (AbbreviationOnChange, LevelOnChange) — if input checks are present.

List form module (ListForm):

• OnCreateOnServer — setup of the dynamic list, conditional formatting, selections;
• commands for group editing of selected rows.

Select form module (SelectForm):

• OnCreateOnServer — setup of selection mode, initial selection (for example, by level of the address element);
• SelectElement / processing BeforeEditingEnds.

Manager module:

• typical procedures for forming the element view and handlers for filling from the address classifier (when integrating with FIAS/KATO-like addressing mechanisms).

"Requires verification" — only the composition of predefined elements and the presence of auto-fill procedures from the classifier: they are version-dependent and may differ between releases 3.0.7x.

5. Posting and Movements

The catalog is not a document and is not posted — the posting mechanism to objects of the "Catalog" type is not applicable. The elements of the catalog do not generate accounting entries and movements in registers (neither in accumulation registers nor in the accounting register of the Standard Chart of Accounts of the RK).

The role of the object is exclusively regulatory and reference: the values of abbreviations are inserted into the string representation of the address of other objects and in printed forms. It does not affect tax calculations and does not participate in accounting operations. For reference, the catalog itself is not related to the accounts of the Standard Chart of Accounts of the RK (1210 "Short-term receivables from buyers", 1030 "Cash in current accounts", 1330 "Goods", 3310 "Payables to suppliers", 3130 "VAT payable", 6010 "Revenue from sales", 7010 "Cost of sales"), nor to the tax rates of Kazakhstan 2026 (VAT 16%, PIT, WPP, etc.) — all of them are implemented in accounting documents, not in this classifier.

6. Related Objects and Input Based On

• Input based on: not provided (not applicable for catalog-classifiers).
• Where used: the values of the catalog are used in the addressing subsystem when filling in address fields of objects working with contact information:
  • Catalog.Counterparties, Catalog.Organizations;
  • Catalog.Warehouses (storage locations);
  • Catalog.Individuals and other objects with address attributes;
  • data types/sets of address information, where the address is assembled from elements considering abbreviation and level.
• Functional connection: the attribute Level corresponds to the levels of the address classifier (country → region → city → street), ensuring the correct order of assembling the address string; the attribute Abbreviation is used for compact display and printing.

7. Extension Points

• Configuration extension (Extensions): adding attributes (for example, synonym of abbreviation, code by external classifier), additional forms and handlers without removing the standard configuration from support.
• Additional attributes and information (property subsystem): connecting the catalog to the characteristic types plan for storing atypical attributes of abbreviations.
• Event subscriptions (BeforeSave, OnSave) for validation and synchronization of values with external address services.
• Overridable common modules of the addressing subsystem — for embedding custom logic for assembling/parsing addresses using abbreviations.
• Data exchange / loading NRI: filling and updating the catalog from external address classifiers through loading processes.

"Requires verification": the set of available overridable modules of the addressing subsystem of the specific build 3.0.74.2 — clarified by the composition of common modules of the release.