1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | PrintFormTemplates |
| Full Path | Catalog.PrintFormTemplates / Catalogs.PrintFormTemplates |
| Synonym | Print form templates |
| Configuration | 1C:Accounting for Kazakhstan 3.0.74.2 |
| Subsystem | Standard subsystems (BSP) → “Print forms” / “Design templates” |
| Object Character | Service (system), non-hierarchical, primarily edited by the administrator |
Purpose. The catalog stores and manages templates (designs) of printed forms of documents and reports. It provides centralized storage of templates with support for multilingualism, versioning, and conditional visibility in the “Print” menu. The object is mainly operated by the system printing mechanisms of BSP automatically — users rarely access it, except for administrators configuring customized (user) print forms. The read frequency is high (each print call accesses the catalog), while write is rare (when updating the configuration or creating user templates).
Where to find in 1C:
- Section “Administration” → “Print forms, reports, and processing” → “Print form templates”.
- Navigation link:
e1cib/list/Catalog.PrintFormTemplates
2. Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| DataSource | CatalogRef.ObjectIdentifiersOfExtensions, CatalogRef.ObjectIdentifiersOfMetadata |
Not checked | Reference to the metadata object or extension for which the template is intended. Links the template to a specific document or report. |
| IsUsed | Boolean |
Not checked | Flag of the template's activity. Controls the availability of the print form in the print menu. The only attribute available for bulk editing. |
| Identifier | UUID (String) |
Not checked | Unique identifier of the template for programmatic search. Encoded in the name of the catalog item with the prefix PF_. |
| Template | ValueStorage |
Not checked | Main data storage of the template (table document, data composition template, etc.) for the main language of the system. |
| VisibilityCondition | ValueStorage |
Not checked | Saved conditions for displaying the form in the “Print” submenu (e.g., only for certain types of operations or document types). |
| TemplateType | String |
Not checked | Type of the stored template (TableDocument, DataCompositionScheme, etc.) for correct interpretation of the contents of the attribute Template. |
Note. Standard attributes
Code,Name,DeletionMark,Predefinedare present as in any catalog. The name of the item is formed according to the templatePF_<Identifier>, which allows the printing mechanism to find the template by string name.
2.2 Table Parts
Views
Purpose: storage of localized versions of the template for different interface languages.
| Name | Type | Purpose |
|---|---|---|
| LanguageCode | String |
Language code according to ISO (ru, kk, en) for which the version of the template is intended. |
| Name | String |
Localized name of the form displayed in the print menu to the user with the corresponding language. |
| Template | ValueStorage |
Version of the template for a specific language. If not filled for the requested language, the template from the header (main language) is used. |
For Kazakhstan, standard languages are
ru(Russian) andkk(Kazakh); bilinguality of print forms is a standard requirement of the RK.
DataSources
Purpose: list of metadata objects for which this template is applicable (one template can be used by several types of documents).
| Name | Type | Purpose |
|---|---|---|
| DataSource | CatalogRef.ObjectIdentifiersOfMetadata / ...ObjectIdentifiersOfExtensions |
Owner object, to the print menu of which the template is connected. |
3. Forms
| Form | Type | Purpose |
|---|---|---|
ListForm (ListForm) |
List | Main administration form: view all templates, filter by the “IsUsed” flag, selection by data source, mark for deletion. |
ElementForm (ElementForm) |
Element | View/edit properties of the template, open the template in the table document editor, manage localized views and visibility condition. |
SelectForm (SelectForm) |
Select | Programmatic selection of the template from other forms (e.g., when connecting an external print form). |
In the standard BSP, editing the contents of the template is usually performed through the specialized processing “Print Form Management” / “Print Form Templates”, rather than directly in the element form.
4. Key Procedures of Modules
No separate BSL code (evidence) for the object modules is attached. Below are the typical handlers of this type of object in the BSP “Print”:
- ManagerModule →
PrintByTemplate/GeneratePrintForm— extractsTemplate(or localized version from the table part “Views”), deserializesValueStorageand passes the table document to the printing mechanism. - ObjectModule →
BeforeWriting— control of uniqueness ofIdentifier, synchronization of the namePF_<Identifier>, check of fillingTemplateType. - ManagerModule →
FindTemplate(Identifier)— search for the item by encoded name/identifier for programmatic access of the printing mechanism. - Element form →
OpenTemplate/LoadTemplateFromFile— editing the contents of the template, saving toValueStorage. DetermineVisibilityInMenu— calculation ofVisibilityConditionfor forming the “Print” submenu of the source document.
“Requires verification”: the exact names of the export procedures of the printing mechanism depend on the version of BSP embedded in 3.0.74.2.
5. Posting and Movements
The catalog is not a document and does not generate postings and movements in registers. It is a data storage serving the printing subsystem. No records in accounting, accumulation, or information are created when writing an item.
The impact on accounting is only indirect: templates determine the appearance of primary documents and print forms that accompany business operations. The postings themselves are generated by source documents that use these templates. For reference, here are the typical accounts of the RK involved in documents to which print forms are connected (numbers and rates are according to the norms of Kazakhstan 2026):
| Operation (source document) | Typical Posting | Comment |
|---|---|---|
| Sale of goods (act/invoice, STS, ESF) | Dr 1210 Cr 6010 — revenue; Dr 1210 Cr 3130 — VAT 16 % | Printing of invoice, bill (ESF via IS ESF), STS |
| Cost of sales | Dr 7010 Cr 1330 | Writing off the cost of goods |
| Receipt of goods | Dr 1330 Cr 3310 | Printing of receipt invoice |
| Payment from the customer | Dr 1030 Cr 1210 | Printing of bank/cash forms |
VAT in the examples is 16 % (RK rate for 2026). Electronic documents (ESF, STS) are uploaded to government systems by separate mechanisms; this catalog is only responsible for paper/printed representations.
6. Related Objects and Input on Basis
- Catalog “ObjectIdentifiersOfMetadata” and “ObjectIdentifiersOfExtensions” — data sources (owner objects of templates).
- “Print” mechanism of BSP (common modules
PrintManagement,ClientPrintManagement) — main consumer of the catalog. - Processing “Print Form Management” — administration interface for creating and uploading user templates.
- Source documents (Sale, Receipt, Invoice/ESF, STS, payment and cash documents) — call templates through their “Print” submenu.
Input on basis: not provided and not applied for service catalog. New items are created manually by the administrator or uploaded during configuration/extension updates.
7. Extension Points
- User (external) templates. Creating an item with the
IsUsedflag and filledDataSourceconnects a custom print form to the document menu without changing the standard configuration. - Multilingualism. Adding rows in the table part “Views” (
ru,kk) ensures the display of the form in the user interface language — relevant for bilingual primary documents of the RK. - Conditional visibility. Through
VisibilityConditionit is possible to limit the display of the form to certain types of operations/organizations. - Configuration extensions. Templates of extension objects are registered through
ObjectIdentifiersOfExtensions, allowing the addition of forms without removing the standard from support. - Programmatic subscriptions/overrides of the printing mechanism of BSP (overridable modules
PrintManagementOverridable) — for intercepting the formation and substitution of the template.
“Requires verification”: the composition of overridable modules and API for connecting external forms depends on the version of BSP in 3.0.74.2.