1. Identification of the Object
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | IncomingElectronicMail |
| Full Name | Document.IncomingElectronicMail |
| Synonym | — (not set) |
| Subsystem | Interaction Management (CRM), "Email" library of the BSP |
| Configuration | 1C:Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2) |
| Type by Accounting Role | Not an accounting document. Does not generate movements in accounting and accumulation registers |
Purpose. The document is intended for registering and storing incoming electronic mails in the interaction management system. It records correspondence with counterparties, partners, and other contacts received through configured email accounts. It is created automatically upon receiving emails through integration with mail servers (POP3/IMAP) or registered manually. It ensures the connection of correspondence with accounting objects (counterparties, contracts, projects, folders) and stores the history of interactions. Access is granted to users responsible for interactions and individuals with rights to the corresponding email account.
Where to find in 1C:
- Navigation link:
e1cib/list/Document.IncomingElectronicMail - Interface: section containing the "Interactions" subsystem / "Mail, Tasks" → journal "Interactions" (incoming emails are displayed in the general list of interactions).
2. Header Attributes and Table Parts
2.1 Header Attributes
| Attribute | Type | Purpose |
|---|---|---|
Number, Date |
String / Date | Standard document attributes; date is usually = date of receipt of the email |
SendingDate / ReceivingDate |
Date | Date of sending the email by the sender and the date of actual receipt by the server |
EmailAccount |
ReferenceLink.EmailAccounts | The mailbox to which the email was received |
Sender |
Composite (address / contact) | Address and name of the sender; matched with the contact during parsing |
SenderRepresentation |
String | Displayed name of the sender (“Ivanov I. ivanov@mail.kz”) |
Subject |
String | Subject of the email |
Importance |
Enumeration (Low/Normal/High) | Priority of the email |
Encoding |
String | Text encoding of the email (used when re-encoding “garbled text”) |
TextType |
Enumeration (PlainText/HTML/FormattedText) | Format of the email body |
Text / HTMLText |
String (unlimited) / FormattedDocument | Body of the email in the corresponding format |
Size |
Number | Size of the email in bytes |
MessageIdentifier (MessageID) |
String | Unique identifier of the email on the server (anti-duplicate) |
MessageIdentifierReference (InReplyTo) |
String | Reference to the email to which this reply is — for assembling the chain |
Author / Responsible |
ReferenceLink.Users | Responsible for the interaction |
Reviewed, ReviewDate |
Boolean / Date | Indicator and date of processing the email |
InteractionBasis |
DocumentReference | Parent interaction in the chain of correspondence |
Comment |
String | User's service comment |
2.2 Table Parts
| Table Part | Key Columns | Purpose |
|---|---|---|
Recipients (To) |
Address, Representation, Contact | List of email recipients (To) |
CCRecipients (CC) |
Address, Representation, Contact | CC recipients |
BCCRecipients (BCC) |
Address, Representation, Contact | BCC recipients |
Email attachments are stored not in the table part, but in attached files (subsystem "File Management"): a directory of attached files linked to the owning document.
3. Forms
| Form | Purpose |
|---|---|
DocumentForm |
Main form for viewing/editing the email: header, recipients, body, attachments panel, "Reply", "Reply All", "Forward" buttons |
ListForm |
List of incoming emails (usually part of the general interactions journal) |
SelectForm |
Selecting an email from other objects (for example, when specifying a basis) |
| Encoding selection/clarification form | Service form for changing text encoding when displaying incorrectly |
| BSP "Interactions" forms | General forms for parsing contacts, selecting folders, configuring the interaction list |
4. Key Module Procedures
Evidence contains a reference to the general module of the subsystem, but without exact line numbers in BSL. Below are handlers for the actual evidence and typical handlers for this type of BSP object.
From evidence:
Interactions.OnDocumentSave(...)— called from theOnSavehandler of the object module. Records in the information registers of the interaction subsystem (see section 5): fixes the connection of the email with contacts, processing status, and belonging to a folder/item.
Typical handlers of the object/module (BSP "Interactions", "Email"):
FillProcessing— filling in attributes upon creation (email account, date, responsible person, parsing sender/recipient addresses into contacts).BeforeSave— control of mandatory fields (email account, subject/recipient), updating service fields.OnSave— callsInteractions.OnDocumentSaveto update information registers (contacts, statuses, items).OnCreateOnServer(form) — initialization of the attachments panel, "Reply"/"Forward" buttons, configuring the display of the email body according toTextType.Reply / ReplyAll / Forward(form commands) — creating a new outgoing email document with the subject (Re:/Fwd:), quoting the body and transferring attachments (for "Forward").ParseContacts— matching addresses with contacts/counterparties; in case of ambiguity, a contact clarification form opens.ChangeEncoding— re-decoding the email body in the selected encoding.
Typical Errors (exactly from code, release-specific)
| 1C Message | Where it occurs | Condition |
|---|---|---|
Invalid object call on the client. |
Object module | Attempt to call a server method of the object in a client context |
⚠️ Requires verification for 3.0.74.2: texts and presence of handlers are recorded for release 3.0.68.1; in 3.0.74.2, there may be changes in the composition of service methods of the interaction subsystem.
5. Posting and Movements
The document is not a postable accounting object. It does not generate movements in the accounting and accumulation register — the set of register_records in the metadata is empty. Therefore:
- No postings. Accounts of the typical chart of accounts of the RK (1210 "Short-term receivables from customers", 1030 "Money in current accounts", 1330 "Goods", 3310 "Payables to suppliers", 3130 "VAT payable", 6010 "Revenue from sales", 7010 "Cost of sales") are not affected by this document.
- Tax calculations (VAT 16%, PIT 10%/15%, OPE 10%, OPEA 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%, MRP 4,325 ₸, MZP 85,000 ₸) do not apply to this object — it performs exclusively CRM functions. These indicators are provided as a country context for the configuration, but the email does not use them.
Interaction with information registers (performed in OnSave through Interactions.OnDocumentSave):
| Information Register | What is recorded |
|---|---|
InteractionsContacts |
History of interactions with contacts: linking the email to the sender/recipient contacts |
InteractionStatuses |
Status of processing the email (read/unread, reviewed) |
FolderItems |
Connection of the email with the folder and item (project, contract, counterparty) |
6. Related Objects and Input on Basis
Related objects:
Reference.EmailAccounts— receiving mailbox.- Interaction contacts:
Reference.Counterparties,Reference.Individuals,Reference.Usersand other types allowed in theInteractionsContactsregister. - Attached files (attachments) of the file management subsystem.
Document.OutgoingElectronicMail— when performing "Reply"/"Forward".- Folder items: projects, contracts, and other objects linked through
FolderItems.
Input on basis (created from the email):
- Outgoing electronic mail — "Reply", "Reply All", "Forward" (with transfer of subject, quotes, and attachments).
- Other interactions/tasks of the subsystem (with typical settings): meeting, phone call, planned interaction with maintaining the connection to the item.
Based on the email, it can create (with expanded mechanisms of the subsystem): counterparty/contact from the sender's address; if necessary — accounting documents manually (invoice, sale, etc.), but there is no direct typical command for input on the basis of an accounting document from the email.
7. Extension Points
- Object module handlers:
FillProcessing,BeforeSave,OnSave,BeforeDelete— for fine-tuning auto-filling, anti-duplicates byMessageIdentifier, additional binding to items. - Document event subscriptions (
OnSave/BeforeSave) — for integrations without changing the object module. - Overridable BSP modules of the "Interactions" and "Email" subsystems — rules for parsing contacts, determining item/folder, formatting responses.
- Configuration extension: adding attributes (for example, "spam" indicator, category, tag), form commands, columns in the list; intercepting "Reply"/"Forward" commands.
- Additional attributes and information (properties mechanism) — marking emails without changing the metadata structure.
- Exchange/integration rules with external mail and CRM systems through interaction registers.
⚠️ Requires verification for 3.0.74.2: the specific composition of overridable procedures of the interaction subsystem and method signatures depend on the version of the BSP included in 3.0.74.2.