1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | NotificationOfDiscrepanciesInESF |
| Full Name | Document.NotificationOfDiscrepanciesInESF |
| Synonym | — (not specified in the delivery) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Accounting Currency | Tenge (₸) |
| Navigation Link | e1cib/list/Document.NotificationOfDiscrepanciesInESF |
Purpose. The document is intended for accounting and processing notifications of discrepancies between the data of the organization's information system and the state system ESF (Center for Electronic Document Management of Marked Goods) of the Republic of Kazakhstan. It records discrepancies in the quantity or composition of marking codes (MC) between the sent documents and those actually registered in the ESF information system.
The notification can be incoming (received from a counterparty or the ESF system itself) or outgoing (generated by the organization upon discovering discrepancies during acceptance). This is a service (informational) document of electronic document management — it accompanies the work with marked products and is not a primary accounting document for accounting or inventory.
Where to find in 1C: section "Sales" → "Notification of Discrepancies (ESF)". Access is organized through two specialized lists — "Incoming Notifications of Discrepancies" and "Outgoing Notifications of Discrepancies".
2. Attributes of Header and Table Parts
2.1. Mandatory Header Attributes
All listed attributes are mandatory to fill: if a field is not filled, the platform will not allow the document to be processed/recorded and will issue an error of the type "Field ... is not filled".
| Attribute | Type | Purpose |
|---|---|---|
Supplier |
ReferenceDirectory.Counterparties | Reference to the supplier counterparty (the party that sent the original document) |
SupplierName |
String | Name of the supplier in the notification attributes (replicated from ESF/counterparty data) |
SupplierIdentificationNumber |
String | BIN/IIN of the supplier — identifier for verification with the ESF information system |
Recipient |
ReferenceDirectory.Counterparties (or Organizations) | The recipient party of the goods to which the discrepancy relates |
RecipientName |
String | Name of the recipient in the notification attributes |
RecipientIdentificationNumber |
String | BIN/IIN of the recipient |
In addition to the mandatory attributes, the header typically contains service attributes of the ESF document management: document number and date, type of notification (incoming/outgoing), processing status in the ESF information system, reference to the underlying document (Acceptance Transfer Act, Internal Movement Act, Notification of Import from EAEU), notification identifier in the system.
2.2. Table Part "Typical Errors"
Contains a list of validation and processing errors received from the ESF information system or generated during local document verification.
| Column | Type | Purpose |
|---|---|---|
Text |
String | Error message text |
Field |
String | Name of the document field where the error was found |
Typically, the document also contains a table part with a list of marking codes (MC) for which discrepancies in quantity/composition have been recorded — it is filled with data from the response of the ESF information system or from the underlying document.
3. Forms
| Form | Purpose |
|---|---|
| Document Form (DocumentForm) | Main form for editing the notification: attributes of the parties, ESF status, table of MC with discrepancies and table of "Typical Errors" |
| Incoming List Form | Separate list of notifications received from counterparties/ESF system |
| Outgoing List Form | Separate list of notifications generated by the organization |
| Selection Form | Selecting a notification when referencing from other objects |
The separation into incoming/outgoing lists is implemented by filtering by the type of notification in one or more list forms.
4. Key Module Procedures
Evidence for specific lines of BSL for this assembly is not attached. Below are typical handlers for the service document of this type; the actual bodies of procedures should be viewed in the configurator (object module / form modules).
ProcessingFilling(object module) — filling in the attributes of the parties and the MC table when entering based on the underlying document or when loading an incoming notification from the ESF information system.ProcessingCheckFilling(object module) — control of filling mandatory fields (Supplier, identification numbers of the parties, etc.) before recording.BeforeRecording/OnRecording(object module) — fixing the status of document management, setting the type of notification.- List Form Handlers — setting filtering by type (incoming/outgoing), commands for updating status from the ESF information system, sending/revoking/rejecting notifications.
ProcessingConducting— absent (see section 5).
5. Conducting and Movements
The document does not generate accounting entries and does not have a ProcessingConducting procedure.
This is an informational/service document intended solely for document management with the ESF system. It does not directly affect accounting and inventory accounting registers — it does not create movements in the accounts of the RK chart of accounts and does not change the balances of goods and settlements.
Adjustment of accounting data upon identified discrepancies is performed by separate documents (see scenario 3.6). These adjustment documents generate actual movements. For reference — typical accounts of the RK chart of accounts involved in related adjustments:
| Account | Purpose |
|---|---|
| 1210 | Short-term accounts receivable from customers |
| 1030 | Cash in current bank accounts |
| 1330 | Goods |
| 3310 | Short-term accounts payable to suppliers |
| 3130 | VAT payable (VAT rate in RK from 2026 — 16%) |
| 6010 | Revenue from sales |
| 7010 | Cost of sales |
The notification itself does not create entries with these accounts — they are generated by acceptance/sales documents and adjustments to which the notification refers.
6. Related Objects and Input Based On
Underlying documents (incoming notification arises as a reaction to discrepancies in them):
- Acceptance Transfer Act (ESF);
- Internal Movement Act;
- Notification of Import from EAEU.
Adjacent electronic documents: ESF (ESF information system), SCT (accompanying invoice for goods) — the overall contour of electronic document management for marked products in RK.
Typical Work Scenarios:
- Receiving an incoming notification of discrepancies — the counterparty or ESF information system detected discrepancies in a previously sent document.
- Creating an outgoing notification — the organization discovered discrepancies with the data of the supplier/ESF during acceptance.
- Rejecting an incoming notification — the organization disagrees with the stated discrepancies.
- Revoking an outgoing notification — the notification was created/sent by mistake and is revoked before processing by the counterparty.
- Updating the document status — regular synchronization of statuses with the ESF information system.
- Entering an adjustment document based on the notification — after analyzing the incoming notification, accounting data is corrected (it is the adjustment document that generates accounting/inventory movements).
7. Extension Points
- Configuration extension to add attributes/columns of MC and override list form handlers (without removing from support).
- Event subscriptions (
BeforeRecording,OnRecording) — for additional integration logic and logging of exchanges with ESF. - Input rules based on — extension of the list of adjustment documents entered from the notification (scenario 3.6).
- External processing/HTTP services for exchange with the ESF information system — connection point for status synchronization and loading incoming notifications.
- Table "Typical Errors" — extension point for custom local validation rules before sending to ESF.
Requires verification in a specific assembly: the exact composition of ESF document management attributes and names of exchange commands — they are version-specific and may differ in different releases 3.0.7x.