Examples of loading xml files in 1c. XML file generation. Simple unloading for a third party application. The process of unloading data into xml. Fill records into the receiver

Data transfer is a very important process in any accounting system, the 1C 8.3 and 8.2 platform is no exception. Below we will look at the instructions on how to easily transfer data from one system to another with a similar configuration (for different configurations, you can use a tool for programmers - or).

Before any action is necessary, the changes are irrevocable!

The easiest and most convenient way to transfer data from 1C 8.3 to 1C 8.3 accounting 3.0 is to use the processing Unloading and loading data in XML format (download - for 8.2 or for 1C 8.3 or on ITS). The processing is universal and suitable for any configuration.

We will not go into details, we will consider the step-by-step instructions for migrating data using this processing using the example of the simplest transfer of goods.

Exporting data to XML

First of all, let's open the processing in the source database (from where we will unload the goods) and look at the interface:

Get 267 1C video tutorials for free:

It is immediately necessary to fill in the "File name" field - a new data file will be created along this path, which we will load into the receiver database. Slightly below, in the tabular section "Data for unloading", you must select the data that we want to unload from the database.

After selecting an object from the left tabular section, you can apply a selection in the right tabular section:

In our example, I want to unload all products with the name "Rake".

After all the settings are filled in, the data can be downloaded. To do this, click on the "Upload data" button:

Loading data from xml into 1c 8.3

The data has been unloaded from the source base, now it needs to be transferred to the destination base.

To do this, you need to start processing already in the database into which you need to load the data, and go to the "Download" tab, select the downloaded file on the disk and click on the "Load data" button:

This example is only suitable for transferring data between identical configurations on the 1C platform. To understand the exchange mechanism for programmers, we wrote an article -.

The transfer of information between databases is one of the tasks of their support and administration. For its effective implementation, processing is created in automated 1C complexes. They greatly facilitate routine work, speed up the process of uploading and downloading information and at the same time control its correctness. Unloading from 1c to xml allows you to create a file with the contents of any object of a configured configuration, and use it when you need to unload data into an identical configuration.

Tools for creating an upload

For the export of information contained in databases, the xml format is mainly used. For 1C, a lot of processing has been developed (for example, UnloadingLoadingDataxml82 epf), with the help of which it is possible to output to a file and load data. In this case, the user must receive a file of a certain structure, which allows loading the information stored in it into the native database or transferring it to another location. When creating an unload, the following rules should be observed:

Save the created files until the moment of complete recovery and the end of the procedures for checking the correctness of the transferred information;
In the case of using processing as a backup tool, create separate subfolders for copies of data and keep a log of their accounting for quick retrieval.

The universal processing "Upload and download XML data" supplied in the 1C user support program, which can be found on the ITS website or disks, is an excellent tool for exporting and importing information. A computer user can unload both the entire database and its individual objects, while in addition to the actual export, various information verification operations are performed to help get rid of critical errors in the data. Processing 1c unloading to xml works in two modes:

Unloading. Creates a file containing user-defined objects to be uploaded;
Loading. Reads a previously exported file and writes the information contained in it to the infobase.

Processing allows you to control objects for invalid characters, and also includes the function of exporting information with restrictions.

Unloading can be used not only when exchanging information between 1C bases. With its help, it is possible to ensure the integration of various complexes, for example, 1C and the Parus system. The versatility of the XML format allows you to create programs for transferring information for almost any information bank. Processing, uploading and downloading of xml data is the most important information exchange tool.

The process of uploading data toxml

Let's consider how to unload from 1c to xml in normal mode. After uploading the UnloadingLoadingDataxml.epf processing and opening it, you must perform the following steps:

Select objects for export;
Set up the necessary filters, for example, by period;
Determine the location of the information file on the disk subsystem;
Start unloading objects.

It should be remembered that the header part of the upload file format differs from the file format used when uploading according to exchange plans.

xml

Loading xml in 1c is performed in the receiving base with the configuration identical to the source base. Before loading in 1c xml 1c, you need to open processing in the receiver base. Then you need to specify the path to the previously uploaded file and load the data by clicking on the "Load data" button.

If necessary, the checkboxes are activated to load data in the exchange mode in a distributed infobase and to ignore the errors that occur when loading objects.

After that, you need to check the databases and make sure that all elements are loaded correctly so as not to get them lost, for example, if an error occurred in the event handler after loading the object.

This processing allows the exchange of data between the same (identical) configurations on the 1C 8.2 platform - Bukh, ZUP, UT, UPP and others, the main thing is that the configurations are the same!

Processing screenshots

(foto)

Modes of operation

Processing implements 2 modes of operation: Unloading (creating an unloading file specified by the user) and Loading (reading the unloading file created by the mode of the same name and writing the data available in it). The mode is set by selecting in the Mode field.

Before starting this or that mode (pressing the Run button), you need to specify the name of the upload file either by entering it manually in the "File name" field, or by using the button for selecting this field and the standard file selection dialog.

In the download mode, it is possible to edit the use of totals when writing registers, which may affect the download speed.

The buttons "Disable totals" and "Include totals" are available when the checkbox "Enable the ability to edit the use of totals during data loading" is checked and are used to manually control the mode of using totals when loading data.

Conditions of applicability of processing

Processing can be used only in cases where the infobase in which the data was downloaded and the one in which the data is loaded are homogeneous (the configurations are identical, the data may differ), or all unloaded objects are almost completely identical in composition and types of attributes and tabular sections, properties of the "leading" metadata object, and so on. It should be noted that, due to the specified restrictions, processing is mainly intended for exchange between homogeneous information security.

The format of the upload file differs from the format of the file created when uploading according to the exchange plan by the header part. To unload data (elements of directories, sets of register records, etc.), processing uses the same XML serialization mechanism as unloading according to exchange plans; in this part, the file formats are identical.

Determination of the composition of the unloading

Processing allows both full and partial uploading of infobase data to a file. Configuring the composition of the uploaded data is done in the dialog by checking the boxes in the column of the tree displaying metadata objects, the data on which can be uploaded. An additional column of flags, "If necessary", sets the necessity of unloading objects of this type "by reference". That is, if the checkbox is selected only in the "If necessary" column, then the data for such an object will not be fully unloaded, but only to the extent necessary to maintain referential integrity in the infobase that will load the unloading file.

When the form is opened, processing sets the sign of unloading by reference to all objects, which guarantees the referential integrity of the unloaded infobase fragment.

When you click on the "Define objects to be uploaded by link" button, the processing analyzes the links to which data can be contained in objects that have the complete upload flag set, and automatically fills in the column of flags indicating the need to upload by link. If the object already has the full unload checkbox selected, then the unload by link checkbox is not set.

Possible applications

The use of this processing is possible, for example, for creating a full or partial backup of data, for exchanging data between infobases, and also as an auxiliary tool in restoring problem infobases.

In an organization, accounting can be kept not only in solutions based on the 1C: Enterprise platform, but also in other software packages (Galaxy, Parus, SAP, etc.). In this case, the tasks of integrating two applications appear.

For example, in some application (let's call it "X") you want to read a list of configuration documents. We will not talk about the practical benefits of solving such a problem, I will only note that the most convenient and universal way in such a situation will be to unload a list of documents in XML format.

Exchange using this format is universal since most applications can work with it. Let's consider how it is possible to unload the list of configuration documents into an XML file from 1C: Enterprise.

Export to XML

And so, let's move on to the main thing. We need to traverse the document metadata list and form the list in an XML file. The following screenshot shows the algorithm for generating an XML file:

NewXML () Export function // Get the name of the temporary file Path = GetTemporaryFileName (); // Initialize the "XML Writer" class Record = New XML Record; // Open a temporary file for writing - 8 ") ; // Write the XML file declaration Recording. WriteXMLDeclaration (); // Record. WriteItemStart (" DocumentsConfigurations") ; // First item // Attribute of the first element with the date of the file formation Recording. WriteAttribute ("generated", Format (CurrentDate (), "DF = yyyy- MM- ddThh: mm: ss; DLF = DT")) ; // Write an item for each configuration document. Place the name of the document in the text. For Each Dock From Metadata. Documents Cycle Recording. WriteElementStart ("Document"); Recording. WriteText (Doc. Name); Recording. WriteEndElement (); End of Cycle; // Finish writing the first item Recording. WriteEndElement (); Recording. Close (); // Close the file // Get the binary data of the file and put it in temporary storage BinaryData = New BinaryData (Path); Address = PlaceTemporaryStorage (BinaryData, New UniqueIdentifier); Return Address; // Return the address of the file in the repository EndFunction

Each element created must be completed correctly. After executing the "WriteElementBeginning ()" method, the "WriteElementEnd" method must be executed, otherwise the structure of the XML file will be incorrect.

The general pattern for creating XML files is the following sequence:

// 1. Initialize the class "XML Writer" Record = New XML Record; // 2. Open a temporary file for recording Recording. OpenFile (Path, "UTF-8"); // 3. Write the declaration of the XML file Recording. WriteXMLDeclaration (); // // 4. ++ Writing the content of the XML file Recording. WriteElementStart ("XML Element"); Recording. WriteEndElement (); // - Write the contents of the XML file // 5. Close the file Recording. Close ();

With these five steps, you can create almost any XML file.

In our example, the generated file is converted to binary data and returned to the place where the CreateXML function was called. This file can then be written to the file system.

You could see an example of an uploaded file in the screenshot above.

Third party application

For the example, I created a .NET Framework application to demonstrate how to read an XML file in a third-party application.

The program reads the created file and displays the documents in the form of a list:

You can try it yourself, the application is available for download at the link at the end of the article.

Versatility

The XML format is used in most configurations for data exchange between application solutions on the 1C: Enterprise platform. Another commonly used exchange method is a COM connection. XML allows you to exchange with almost any application, which is why it deserves to be called universal.

Downloads:

XML file reader application.

XML file generation processing.

When an enterprise constantly uses some kind of software complex in its work, then, naturally, the question of its constant support and administration always arises. At the same time, you cannot do with the tasks of data exchange, storage and recovery. Let's consider how to load or unload data from 1C in XML format, since this is an important procedure in this topic.

They are built so that when unloading, you can get an XML file, in which the data necessary for the client will be written. At the same time, simultaneously with the recording, the correctness of the transferred records is checked for critical errors.

Thus, unloading into an XML file (importing records) from one infobase and then loading from XML into another is an exchange of data in XML format between databases.

This procedure, especially with large amounts of information, saves a lot of manual work.

Import (resulting file) can also be used as an archive for recovery in unforeseen situations (in case of loss or damage).

A lot of such processing tools have been developed, and they are available on the Internet. Responsibility for their use falls on the shoulders (and head) of the client.

But for the official users of oneeski, the developers have created a universal "XML data upload / download" handler.

IMPORTANT. Export to XML in 1C and further loading into XML from 1C is permissible for identical configurations - otherwise it will be damaged.

Generic handler

Highlights for using a generic developer:

Save the import of files until the end of the transfer of records and checking their correctness;
When used as backups, you should keep track of them for sorting searches.

It has two modes of operation: creating a file when saving information and reading / writing it when importing.

In addition, the user can set additional restrictions both when exporting and loading data.

Retrieving records

You can upload data both throughout the database and selectively - by object.

After downloading, installing and opening the handler, the following is done:

They are selected in the dialog box that opens after launch. To do this, check the boxes in the list that displays the metadata objects to be retrieved;

The necessary filters are configured (for example, by date);
A place on the disk space is selected;
The operation itself starts.

Fill records into the receiver

The first step to receive data into the target database is to open a handler program in it.

After the path to the source file is specified and the checkboxes of the procedure settings are activated (if necessary), you can start the process with the button “Load data”.

Now you know how to load or unload data from 1C in XML format to save data and exchange between databases.

Write in the comments about your experience in this matter.

- well-known web pages, which are also analogous to XML with lax checks.

Objects of reading / writing XML, FastInfoset, HTML extend the possibilities of reading a text file with built-in processing of markup tags.

They are also used for DOM Builder / DOMWrite objects (see below) as data sources.

1C XML files contain text information, that is, they are text files. Objects ReadingXML 1C and WritingXML 1C are "add-ons" that simplify the work with the tags of the XML file 1C.

The objects Reading FastInfoset 1C and Writing FastInfoset 1C, Reading HTML 1C and Writing HTML 1C are completely similar to Reading XML 1C and Writing XML 1C and are used to work in the same way with other formats.

1C XML file used in the examples

Reference>

Text valueProps>
Reference>
Configuration>

Example 1. Reading a 1C XML file into a value tree using XML 1C Reading

// open the 1C XML file for reading using XML 1C Reading
File = New XML Read ();
File.OpenFile ("D: \ StructureConfiguration.xml");

// prepare a tree of values
// each XML branch can have a name, attributes and value
dzXML = New ValueTree ();
dzXML.Columns.Add ("Name");
dzXML.Columns.Add ("Value");
dzXML.Columns.Add ("Attributes");

// since an XML string can have several attributes, we will write them to the table of values
// each attribute has a name and a value
tAttributes = NewValuesTable ();
tAttributes.Columns.Add ("Name");
tAttributes.Columns.Add ("Value");

// the nesting level will help us understand when it is necessary to add a nested branch, and when it is necessary to return one level up
Nesting Level = 0;
// current line - tree line, will change with increasing nesting
CurrentString = Undefined;
// 1C XML file is not read line by line, but by structure, at the end of the file, reading will return FALSE
Bye File.Read () Loop

// we are interested in three kinds of nodes - the beginning of the element, the text (value of the element) and the end of the element (to return one level up)
If File.NodeType = HostTypeXML.ItemStart Then

Nesting Level = Nesting Level + 1;

// if this is the first line, then add it to the very top of the tree and save only the name
If CurrentString = Undefined Then
CurrentString = dzXML.Lines.Add ();
CurrentString.Name = File.Name;
Proceed;
Otherwise
// nested lines
CurrentLine = CurrentLine.Lines.Add ();
CurrentString.Name = File.Name; // save the name

// does this XML element have attributes?
If File.NumberAttributes ()> 0 Then
// if yes - copy the prepared empty table to save the attributes
tAttributesNode = tAttributes.Copy ();
// loop over the number of attributes of this element
For MF = 0 by File.Number of Attributes () - 1 Cycle
// for each attribute, remember the name and value
String = NodeAttributes.Add ();
String.Name = File.AttributeName (N);
String.Value = File.AttributeValue (N);
End of Cycle;
// save the element's attribute table to the current row
CurrentString.Attributes = tAttributesNode;
EndIf;
EndIf;

ElseIf File.NodeType = XMLNodeType.EndItem Then
// at the beginning of the element, increase the nesting level, at the end of the element, decrease
Nesting Level = Nesting Level - 1;
// return the current line one level up
CurrentLine = CurrentLine.Parent;

ElseIf File.NodeType = HostTypeXML.Text Then
// if the element has a value, just save it
CurrentString.Value = File.Value;

EndIf;

End of Cycle;

File.Close ();

Example 2. Recording a 1C XML file using the 1C Record XML object

// create a file Record XML 1C
File = New XML Record ();
File.OpenFile ("D: \ StructureConfiguration.xml", "UTF-8");
File.WriteStartElement ("Configuration");

// by metadata we go through all the directories (for more details see "Working with metadata")
For each Reference from Metadata References Cycle

// WriteElementStart - opens a new [subordinate] branch
File.RecordElementStart ("Reference");
// WriteAttribute - writes the attribute to the previously opened branch
File.RecordAttribute ("Name", Directory.Name);
File.WriteAttribute ("Synonym", Directory.Synonym);

// by metadata we go through all the details of the directory
For each Attribute from the Directory. Attributes Cycle

End of Cycle;

// by metadata we go through all the tabular parts of the directory
For each PM from the Handbook. Tabular Parts Loop
File.WriteElementStart ("TabularPart");
File.RecordAttribute ("Name", PM.Name);
File.WriteAttribute ("Synonym", PM.Synonym);

For each Attribute from PM. Attributes Cycle
File.RecordElementStart ("Props");
File.RecordAttribute ("Name", Props.Name);
File.WriteAttribute ("Synonym", Props.Synonym);
File.WriteElementEnd ();
End of Cycle;

File.WriteElementEnd ();
End of Cycle;

// WriteElementEnd - "closes" the previously opened branch with WriteElementBeginning
File.WriteElementEnd ();
End of Cycle;

File.WriteElementEnd ();
File.Close ();

Simple data exchange between various accounting programs is one of the key points of their prevalence; in practice, it is enough to load XML into 1C or another product. Moreover, most often it is easy to do without converting it: all databases support the format standard in full. In practice, there are many ways to use XML to transfer data, all of them are implemented in 1C and compatible products.

How to upload an XML file to the 1C database?

The downloaded databases, individual documents can be transferred from users through any communication channels - on removable media, by e-mail or through cloud storage. The format lends itself well to compression using archivers, which significantly speeds up copying and saves disk space.

The procedure for loading data from an XML file is broadly as follows:

Allow the display of the "All functions" menu item. To do this, put a tick in the corresponding item of the "Parameters" window (the tab is located in the "Service" section of the menu).

In the menu "All functions" through the plus to open the list of options, where and select the item "Processing".

In the offered list, open the item "Universal data exchange in XML format".

By pressing the button "Load data" they will be read from the file, saved to the database with simultaneous verification of their correctness. If errors are found in the document, the procedure will be terminated with the issuance of a specific text indicating the reason.

How are XML files used in 1C?

Using the same processing, the user can upload a selected list of data or the entire database to XML, thereby creating a backup copy of it. This must be done before the introduction of serious adjustments to the global 1C module, if you cannot manage with external processing for some reason.

The format is used on the 1C: Enterprise 8 platform in the following areas:

Unloading of price lists, orders, printed forms of documents.

Data exchange with banks, tax service, extra-budgetary funds.

Transfer of payroll calculations from 1C: ZUP and other "specialized" configurations to the "general" 1C: Accounting 8.

The same universal processing implementation is used throughout. If its functions are few, then they resort to developing their own versions of this module. Moreover, there is no need to change the standard files, it is enough then to connect the necessary processing and launch them at choice - depending on the specific task.

If a company chooses a separate method of accounting and tax accounting, then the processing of uploading / downloading financial data via XML format will become very popular. With its help, the numbers necessary for calculating the tax base are transferred to the 1C: Taxpayer program or to a similar software product. Due to the fact that files of this format are easy to edit, using the Microsoft Office package it is easy to correct their content before sending to the tax office.

The same applies to KUDiR (book of income and expenses), a journal of accounting of issued or received invoices. All this is transmitted through the VLSI ++ system and, in addition to the process of editing the tabular section of the XML file, unloading in this format is necessary for subsequent loading into the service and data transmission to the Federal Tax Service.

Exchange is often in demand with such a configuration as 1C: Trade Management, since in business it is used to organize sales, management accounting, and accounting based on 1C: Accounting 8 functions autonomously, receiving only summary data on all movements of goods and cash funds.

If the unloading of orders or price lists is easy to set up, since it is easy to use "any" data format here, then the same bank statements have to be saved in XML (as a generally accepted standard).

Most often, the exchange takes place with the Client-Bank program. The upload process looks like this here:

An extract is generated for the period required by the user.

Depending on the version of the program, either the “Export” or “Export” button is pressed.

In the window that opens, the desired folder and file name are selected.

After completing the procedure, the document can be transferred to removable media or via the Internet (e-mail, cloud storage with shared access, etc.). When you need to load a statement into the 1C configuration, you select the "Bank and cash desk" section, then go to the "Bank statements" journal.

In front of the tabular part of the document (in the right corner), press the "More" button, after which a list of functions appears, where the item "Exchange with the bank" is selected. The "Download bank statement" tab allows you to import data on the specified company name or on a specific bank account.

After uploading the statement to the 1C database, you will still need to carry out payment orders, this happens in manual mode. An accountant can order the development of processing that will automate the process, but here you need to contact a competent programmer.

The XML format is also used to load various classifiers (KLADR, OKOF, ENAOF). If they are absent in the 1C program, you must avoid manually filling them in, since it is easy to make a mistake when specifying the codes. It is worth using the XML file once by downloading the classifier from a trusted source.

This can be done both by the user himself and by an invited specialist:

In the main menu, select the "References" section.

The button "Configure actions" is pressed.

In the window that opens, indicate the item "Load okof classifier", and then click on the "Add" button.

In the "Service" section that appears, select the desired command and press "OK".

It remains to click on the "Open and read the file" button, specify the desired one on the disk or removable media, open it with the appropriate key. Standard classifiers are automatically copied to the hard disk during platform installation and 1C configuration. Moreover, when updating a version of one or another, folders with a revision number are created, where the current file is located that meets the current requirements. Version 7-7 also has the ability to load XML files, but this legacy platform often requires professional help.

Tools for creating an upload

Save the created files until the moment of complete recovery and the end of the procedures for checking the correctness of the transferred information;
In the case of using processing as a backup tool, create separate subfolders for copies of data and keep a log of their accounting for quick retrieval.

Supplied in the 1C user support program, which can be found on the ITS website or disks, is an excellent tool for exporting and importing information. A computer user can unload both the entire database and its individual objects, while in addition to the actual export, various information verification operations are performed to help get rid of critical errors in the data. Processing 1c unloading to xml works in two modes:

Unloading. Creates a file containing user-defined objects to be uploaded;
Loading. Reads a previously exported file and writes the information contained in it to the infobase.

Processing allows you to control objects for invalid characters, and also includes the function of exporting information with restrictions.

Unloading can be used not only when exchanging information between 1C bases. With its help, it is possible to ensure the integration of various complexes, for example, 1C and the Parus system. The versatility of the XML format allows you to create programs for transferring information for almost any information bank. Processing, uploading and downloading of xml data is the most important information exchange tool.

The process of uploading data toxml

Let's consider how to unload from 1c to xml in normal mode. After uploading the UnloadingLoadingDataxml.epf processing and opening it, you must perform the following steps:

Select objects for export;
Set up the necessary filters, for example, by period;
Determine the location of the information file on the disk subsystem;
Start unloading objects.

It should be remembered that the header part of the upload file format differs from the file format used when uploading according to exchange plans.

xml

If necessary, the checkboxes are activated to load data in the exchange mode in a distributed infobase and to ignore the errors that occur when loading objects.

Allows you to save time on entering information about the purchase of Peterhost services in 1C.
To do this, you need to load an XML file into 1C and a document "Receipt of goods and services" containing information about the purchased services will be formed from it. An invoice can be generated based on this document.

Detailed instructions are presented below.

1. Connecting external processing

1.1. If the 1C: Enterprise 8.X infobase is used with the Enterprise Accounting 2.0 configuration, to upload a document in CommerceML format, you need to connect external processing ()
This can be done in two ways:
1. Save the external processing file locally to disk and open it via the "File" → "Open" menu before each loading of data in CML format.
2. Connect processing to the infobase (IB) permanently. Then it will be available to everyone (in the case of working over a network) from the menu "Service" → "Additional reports and processing" → "Additional external processing".

In the "Service" menu, select "Additional reports and processing" - "Additional external processing".
Click the "Add" button. A form for adding a new catalog item will open:
In the “Name” field, specify the name of the processing, for example, “Loading data in CommerceML format (RU-CENTER Group)”.
Press the file selection button and specify the path to the download processing file ().
Press the OK button. The processing is now connected to the infobase and is located in the Additional external processing reference book, and you can open it by double-clicking it.

1.2. In the case of using the configuration "Manufacturing enterprise management" (version 10.3 and higher) and "Trade management" (version 1.3 and higher), this processing is already enabled and you can go to step 2.

2. Formation of the document "Receipt of goods and services"

As a result of the actions performed below, information about the services purchased from Peterhost will be entered into 1C.
1. Next, you need to save to your computer an XML file with the data of the document “Receipt of goods and services” for the required period. The file in XML format is located in the Personal Account section under the link "XML for 1C".
Press the selection button to the right of the "Data file name" field and select this file (see Figure 1). To the question "Read data from a file?" answer "OK". The data file will be read by processing.
2. If the processing succeeds in determining all the correspondences of the data elements of the file with the data of the infobase, the question "Save data to the infobase?" Will be asked. If you answer “Yes”, then a new document “Receipt of goods and services” will be created. Go to step 3.
3. If not all data matches are determined, a message will be displayed: "When loading data, the program could not automatically find IB objects corresponding to the elements transferred in the exchange file ..." and will offer to perform the matching manually. In this case, you must do the following:

Click "OK". The form for mapping file objects and IB will open. It has several tabs that correspond to different types of objects (organizations, contractors, items, etc.). If data of some type was not matched, then on the corresponding tabs there will be red exclamation marks (see Figure 2).

Go to the corresponding tabs and manually set the correspondence of the elements. It should be noted that the correspondences of counterparties and organizations are searched for by the TIN, and the correspondences of the nomenclature - first by the article, then by the name. If the element that corresponds to the file data is not in the IB, then it can be created automatically from the file data by clicking the "Create from file data" button.
When adding an item, it is necessary to tick the "Service" property (see Figure 3). You can also change the full and short name of the item.

On the “Accounts” tab, it is advisable to add item accounting accounts, so that when creating the document “Receipt of goods and services,” these numbers are added automatically. For example, the following values can be set for services: "Accounting account" - 25 (General production costs) and "VAT claimed account" - 19.04 (VAT on purchased services) (see Figure 4).

After matching all the elements and pressing the "OK" button, the program will ask for confirmation to upload the document to the IB, after which it will create a new document "Receipt of goods and services" (see Figure 5).

3. Posting the document "Receipt of goods and services"

To post the document "Receipt of goods and services", you need to open it by double clicking and fill in the missing fields, such as "Offset of advances" (for example, "Automatic") and the fields on the "Accounts" tab (see Figure 6). The values of these fields are determined by your organization's accounting policy. To post the document, you must press the "OK" button.

4. Formation of the document "Invoice"

After the successful creation and posting of the document "Receipt of goods and services", you can create a document "Invoice received" on the basis of it. To do this, you must click on the corresponding link in the lower left part of the document form.