Directory "File Synchronization Accounting Records" — Technical Description (BK 3.0.74.2)

1. Identification

Purpose. The catalog stores connection settings to cloud services and external file storage for automatic synchronization of files between the 1C information base and external platforms (Google Drive, Dropbox, OneDrive, corporate file servers, etc.). Each record describes one synchronization channel: target service, root folder of the exchange area, and access credentials.

The catalog is managed by administrators and privileged users. Records are created and changed rarely — usually once during initial setup or when connecting a new channel. After saving, key parameters (service, root folder) are locked from modification to avoid disrupting already configured exchange processes.

Where to find in 1C: section "Standard Subsystems" → "File Synchronization Accounts". Navigation link: e1cib/list/Catalog.FileSynchronizationAccounts

2. Attributes and Table Parts

2.1 Header Attributes (stored in the database)

Service Fields of the Form (not stored in the catalog attributes):

• Login — credentials for accessing the external service.
• Password — password or authorization token; stored in a secure form (secure storage / CommonSettingsStorage or BSP secure password storage), not in an open attribute.
• ServiceRepresentation — human-readable name of the service; locked after record creation.

2.2 Table Parts

Table parts are absent. The catalog has a simple flat structure: one record = one synchronization channel.

3. Forms

Composition of ElementForm — 51 control elements, including:

• 6 input fields: Name, Service, RootFolder, Login, Password, FileAuthor.
• 1 action button: CheckSettings — test connection to the service with the entered credentials.
• 5 groupings for structuring the interface (service attributes, authorization, author attribution, etc.).
• 2 radio buttons for selecting the mode of operation of the channel (e.g., direction/mode of synchronization).

4. Key Module Procedures

Evidence with the original BSL code of the modules is not attached, so below are typical handlers of the catalog of this type (element form module and object module). Specific names/strings require verification with the configuration version.

Element Form Module (ElementForm):

• OnCreateOnServer — form initialization: substitution of ServiceRepresentation, setting availability/locking of fields Service and RootFolder for existing (non-empty) records, reading password/token from secure storage.
• OnOpen — final adjustment of element availability, setting the state of radio buttons mode.
• CheckSettings (command handler) → server procedure for test connection: forms a request to the service API with login/password, returns the result as a message to the user.
• BeforeWriteOnServer / AfterWrite — saving password/token in secure storage (not in attribute), fixing the locking of key fields after initial record.
• Handlers ...OnChange for fields Service/Mode — recalculation of representation and availability of dependent elements.

Object Module:

• CheckFillingHandler — control of mandatory attributes Service and RootFolder (corresponds to the ShowError property).
• BeforeWrite — prohibition of changing locked key attributes of an already existing element; normalization of paths.

Requires verification: exact names of procedures, presence of a custom list form, and method of storing the password (BSP secure password storage vs. common storage) — version-dependent.

5. Posting and Movements

The catalog is not a document and is not posted — it does not generate registers and accounting entries. It is a service (configuration) object of the file synchronization mechanism; in accounting data, it serves only as a reference to the exchange channel settings.

Therefore, typical accounts for the Tax Code of the RK (e.g., 1210, 1030, 1330, 3310, 3130, 6010, 7010) and tax movements (VAT, PIT, OPE, etc.) do not apply to this object: it is outside the contour of accounting and tax records.

Indirect influence on accounting is possible only indirectly: files uploaded from external storage through the configured channel can be attached to accounting objects (documents, catalog elements) as attached files, but the actual economic operations and amounts are recorded by receiving documents, not by this catalog.

(Relevant parameters for the configuration in 2026 for the RK — VAT rate 16%, MRP 4,325 ₸, MSP 85,000 ₸, basic deduction for PIT 30 MRP/month (not more than 360 MRP/year), PIT 10%/15% with a threshold of 8,500 MRP, OPE 10% with a base ceiling of 50 MSP, OPER 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6% — relate to accounting documents of the configuration and are provided here for reference; they do not affect this catalog.)

6. Related Objects and Input on the Basis

• Catalog.ExternalUsers, Catalog.Users — through the attribute FileAuthor (attribution of created files).
• File attachment mechanism / BSP file storage — the account defines the external storage to which/from which attached files are uploaded and downloaded.
• Secure password storage (common BSP mechanism) — stores login/password/token associated with the catalog record.
• Registers/settings of the file handling subsystem — the account is used as a parameter for background synchronization tasks.

Input on the basis: not provided. The catalog is not entered on the basis of anything nor serves as a basis for entering other objects (filled manually in the element form).

7. Extension Points

• Configuration extensions: adding attributes (e.g., additional proxy parameters, limits, schedule) and form elements through borrowing ElementForm; overriding OnCreateOnServer/BeforeWriteOnServer.
• Handler CheckSettings: point for connecting a new service provider — extending the list of allowed values for the attribute Service and adding an exchange branch via its API.
• Object module: redefinition of CheckFillingHandler and BeforeWrite for additional business rules (path validation, rights limitations).
• Subscriptions to events of the catalog record — for auditing changes in settings or invalidating the cache of background synchronization tasks.
• Roles and RLS: restricting access to synchronization settings only to administrators/privileged users.

Requires verification: the specific interface for connecting providers (general "overridable" module) depends on the version of the file subsystem in 3.0.74.2.