---
title: "Directory \"Report Dispatches\" - Technical Description (Accounting for Kazakhstan 3.0.74.2)"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-07
canonical: https://buhgpt.kz/suraqtar/spravochnik-rassylkiotchetov-tehnicheskoe-opisanie-buhgal-en
source: BuhGPT
---

# Directory "Report Dispatches" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

> **TL;DR:** ```html 1. Identification Parameter Value Object Type Catalog Name ReportMailings Full Name Catalog.ReportMailings ( Catalogs.ReportMailings ) Synonym Report mailings Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Origin Library of standard subsystems (

---

```html
1. Identification

Parameter
Value

Object Type
Catalog

Name
ReportMailings

Full Name
Catalog.ReportMailings (Catalogs.ReportMailings)

Synonym
Report mailings

Configuration
Accounting for Kazakhstan, edition 3.0, version 3.0.74.2

Origin
Library of standard subsystems (BSP), subsystem "Report Mailings"

Hierarchy
Non-hierarchical (simple linear list)

Main Representation
Name

Purpose. The catalog is designed for centralized management of automatic report mailings to recipients according to a specified schedule. It is used by accountants, financiers, and managers for regular sending of reports to counterparties, employees, or external systems through channels: email, FTP server, network folder, file storage subsystem folder. It works in conjunction with the subsystem of scheduled/background tasks: active mailing is performed according to the schedule of the background task. It supports report personalization for each recipient, archiving results in ZIP, HTML emails with images, and password protection.

Important. This is an infrastructure object from BSP. It does not participate in accounting/tax accounting: it is not a document, does not post anything, and does not generate movements in accounting registers or postings according to the RK chart of accounts (1210, 1030, 3130, 6010, etc.). The Kazakh tax norms for 2026 (VAT 16%, MRP 4,325 ₸, deduction 30 MRP, etc.) do not apply to the catalog itself — they relate to the content of the reports being sent, not to the mailing mechanism. Section 5 below describes this explicitly.

Where to find in 1C:

- Section (subsystem) "Administration" / "Standard Subsystems" → "Report Mailings".

- Direct navigation link: e1cib/list/Catalog.ReportMailings.

2. Header Attributes and Table Parts

2.1 Header Attributes

Name
Type
Mandatory
Purpose

Author
CatalogRef.Users
Mandatory (logically)
Responsible for mailing; determines access to personal mailings

Personal
Boolean
DontCheck
Indicates personal mailing — available only to the author

ExecuteAccordingToSchedule
Boolean
DontCheck
Flag for activating automatic mailing according to schedule

ScheduleFrequency
EnumRef.ScheduleFrequenciesForReportMailings
DontCheck
Frequency (daily, weekly, monthly, etc.)

Personalized
Boolean
DontCheck
Generate a separate report for each recipient with individual settings (parameters, selection by recipient)

Archive
Boolean
DontCheck
Pack reports into a ZIP archive before sending

ArchiveName
String
DontCheck
Template for the ZIP file name (supports macro substitutions)

UseEmail
Boolean
DontCheck
Send reports via email

ReplyAddress
String
DontCheck
Email for replies to the letter (Reply-To)

TypeOfRecipientEmailAddress
CatalogRef.TypesOfContactInformation
DontCheck
Which type of contact information to use for obtaining recipient emails

EmailInHTMLFormat
Boolean
DontCheck
Send email in HTML format (otherwise plain text)

EmailImagesInHTMLFormat
ValueStorage
DontCheck
Image storage for HTML email

UseFTPResource
Boolean
DontCheck
Upload reports to FTP server

FTPServer
String
DontCheck
Address of the FTP server

FTPPort
Number
DontCheck
Port number of the FTP server (default 21)

FTPDirectory
String
DontCheck
Path to the directory on the FTP server for uploading

FTPLogin
String
DontCheck
Username for connecting to FTP

FTPPassiveConnection
Boolean
DontCheck
Passive FTP mode (for working through firewalls)

UseNetworkDirectory
Boolean
DontCheck
Store reports in a Windows/Linux network folder

UseFolder
Boolean
DontCheck
Place reports in the file storage subsystem folder

Folder
CatalogRef.FileFolders
DontCheck
Folder in the file storage subsystem for placing reports

In addition to the listed, the catalog contains standard service attributes for BSP (archive/connection passwords in a secure storage, publication flag, email text, email subject, "Prepared" flag, etc.). Passwords (FTP, archive, mailbox) are stored not in open attributes, but in a secure password storage (CommonPurposeStorage / attribute of type ValueStorage with encryption).

2.2 Table Parts

The BSP logic implements mailing through a set of table parts (names are given according to the typical structure of the "Report Mailings" subsystem):

Table Part
Key Columns
Purpose

Reports
Report (CatalogRef.MetadataObjectIdentifiers/report variant), Representation, Settings (ValueStorage), SaveFormat
List of reports included in the mailing and their saved settings/formats (XLSX, PDF, ODS, etc.)

Recipients
Recipient (CatalogRef.* — counterparties/users/partners), ContactInformation
List of mailing recipients; for personalized mailing, sets individual parameters

SaveFormats
Format, Usage
Selected formats of the result files

Schedule (or storage attribute)
ScheduleValue (ValueStorage with ScheduledRegulatoryTask)
Stores the schedule object according to which the background task is launched

The exact composition and names of table parts are version-dependent. Please check in the configurator on release 3.0.74.2 (this is indeed a version-specific point).

3. Forms

Form
Purpose

ListForm (ListForm)
List of all mailings; filters by author, "Personal" flag, "Execute According to Schedule" status; commands to start mailing manually

ElementForm (ElementForm)
Main form for configuring mailing: reports, recipients, delivery channels (email/FTP/network/folder), schedule, email and archive parameters

SelectionForm (SelectionForm)
Select mailing from other configuration locations

Schedule Configuration Form (auxiliary / common BSP form RegulatoryTaskSchedule)
Edit the schedule for executing the background task

Input Parameters for Sending/Delivery Form
Configure channels, check connection (FTP test, email test)

Additionally, the subsystem uses common BSP forms for the history of mailing executions and viewing delivery results.

4. Key Module Procedures

In the attached evidence, the source code (BSL) of the modules is not provided, so below are typical handlers and procedures for the catalog of the "Report Mailings" subsystem of BSP. Specific paths module:string should be verified in the configurator of the release.

Object Module (Catalog.ReportMailings.ObjectModule):

- BeforeWriting(Refusal) — check for author completion, control of delivery channels (at least one included), check for schedule correctness.

- OnWriting(Refusal) — synchronize the mailing status with the regulatory/background task: if ExecuteAccordingToSchedule = True, a task is created/updated, if False — it is disabled.

- BeforeDeletion(Refusal) — delete the related background task and clear passwords in secure storage.

Catalog Manager Module (ManagerModule):

- ExecuteMailing(Mailing, ExecutionParameters) — generate reports, apply personalization, pack into archive, deliver via included channels, register result in the log.

- GenerateReports(...) / PrepareAttachments(...) — generate tabular documents and save in selected formats.

- DeliverByEmail(...), UploadToFTP(...), SaveToNetworkDirectory(...), PlaceInFolder(...) — implementations of delivery channels.

Element Form Module:

- OnCreationOnServer — initialize visibility of channel groups by flags UseEmail, UseFTPResource, etc.

- Handlers OnChange of channel flags — manage availability/visibility of related fields.

- Commands ExecuteNow, CheckSettings, ConfigureSchedule.

Common modules of the subsystem: ReportMailings, ReportMailingsService, ReportMailingsClient — server and client logic for preparation and delivery.

5. Posting and Movements

The catalog is not a document and is not posted. It does not generate:

- accounting postings according to the RK chart of accounts (for example, 1210, 1030, 1330, 3310, 3130, 6010, 7010);

- movements in accumulation/information registers of accounting or tax accounting;

- tax liabilities (VAT 16%, PIT, WPP, OSSC/VOOSC, CO, social tax) and electronic documents (ESF/SNT).

Instead of posting, the object generates infrastructure actions:

Action
Mechanism

Activate Mailing
If ExecuteAccordingToSchedule = True, a regulatory (background) task is created/updated with the schedule from the storage attribute

Execution
The background task calls ExecuteMailing → report generation → delivery via channels

Logging
The delivery result is recorded in the service information registers of the subsystem (mailing history) and in the registration log

Connection with tax numbers of the RK. Indirectly, the object affects accounting only by which reports are sent. If, for example, declarations/registers with tax calculations are included in the mailing, then the current norms of Kazakhstan for 2026 are applied in these reports: VAT rate 16%, MRP 4,325 ₸, MZP 85,000 ₸, basic deduction for PIT 30 MRP/month (no more than 360 MRP per year), PIT 10% up to 8,500 MRP annual income and 15% above, WPP 10% (base ceiling 50 MZP), WPPR 3.5%, VOOSC 2%, OSSC 3%, CO 5%, social tax 6%. The catalog itself does not calculate these values.

6. Related Objects and Input on Basis

References to:

- Catalog.Users (Author);

- Catalog.TypesOfContactInformation (type of recipient address);

- Catalog.FileFolders (folder for storing results);

- Enumeration.ScheduleFrequenciesForReportMailings;

- reports of the configuration (through identifier

```

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_