Current version configuration "Trade Management",
revision 10.3, intended for use with the system version
1C: Enterprise is not lower than 8.2.19. When working with operating system
Microsoft Windows 10 you need to use version 8.3 of the platform
1C: Enterprise in compatibility mode with version 8.2.
The update is intended for the following releases: 10.3.41.1, 10.3.42.1, 10.3.43.1
What's new?
Added functionality for controlling the periods of validity of formats electronic documents.
Added functionality for sending invitations to exchange for a specific ID of the EDF participant.
Retail
"Receipt Printer" hardware support
It supports printing settlement documents on a connected receipt printer or on an office printer and maintaining a "Journal of accounting of documents issued to the buyer during settlements" in accordance with the RF Resolution No. 296 of 03/15/2017.
Report "Log book of documents issued to the buyer"
Added report "Log book of documents issued to the buyer", see interface "Retail management", menu "Sales".
Directory "Cashier KKM"
The checkbox “Archive receipts” has been added to the form of the "Cash register cash register" reference book. When the checkbox "Archive receipts" is selected, the documents "Cash register receipt" after the shift is closed are not deleted, but marked as archived. Information from these documents is displayed in the report "Log of documents issued to the buyer".
Added service handling for ReceiptPrinter.epf
The processing carries out maintenance of the equipment supported by the "1C: Receipt Printer" driver.
New in version 10.3.43.1
Exchange of electronic documents
Added functionality for canceling an arbitrary electronic document.
Added functionality for viewing EDM regulations through the "Electronic Document Tree" form for an arbitrary electronic document.
The synchronization of the EDM state between all documents of the infobase participating in the exchange of the UPD / DCD has been implemented.
Implemented the possibility of one-time registration of all changes to the organization's certificates in the 1C-EDM service while saving the EDF Profile.
Added the ability to specify a list of users who have access to the certificate.
VAT accounting
In accordance with the decree of the Government of the Russian Federation of May 25, 2017 No. No. 625 in the issued invoices from 01.07.2017 it is necessary to indicate the identifier of the state contract.
In the document "Invoice issued" from 01.07.2017, the field "State contract identifier" is available for filling.
The printed form of the document "Invoice issued" has been brought in line with the decree of the Government of the Russian Federation of May 25, 2017. No. 625.
Retail
Added support for the fiscal data format version 1.0.5 in accordance with the order of the Federal Tax Service of Russia dated 03.21.2017 N ММВ-7-20 / [email protected]
"On approval of additional details of fiscal documents and formats of fiscal documents, mandatory for use."
To take advantage of the new features, an update of the service handles is required.
Correction cash register receipt document
Added document "Correction cash register receipt". To use it, you need to update the shop equipment service processings to version 1.7 or higher.
Directory "Commercial equipment"
Added the requisites "Method of format-logical control", "Allowable discrepancy in formatological control". Used when fiscalizing a check on a cash register with data transfer.
Documents "Receipt cash order", "Cash outflow order", "Payment from the buyer by payment card»
In the tabular section "Payment decryption" added the variable "Sign of the payment method", filled with a default value, available for editing, the user can change its value. The requisite is used when fiscalizing a check to a cash register with data transfer.
Documents "Sale of goods and services", "Return of goods from the buyer"
Added the ability to generate a fiscal receipt on cash register with data transfer.
Fixed bugs found
FLC - format and logical control, which is intended to assist taxpayers in filling out tax reporting forms, does not pursue the goal of conducting desk control, and is developed in accordance with the Rules for drawing up tax reporting forms.
According to paragraph 4-1 of Article 584 of the Tax Code of the FLC, consists in checking the completeness and correctness of its filling, is carried out when receiving and processing tax reports by the system for receiving and processing tax reports of tax authorities (hereinafter referred to as the system).
Confirmation of receipt and processing of tax reporting by the central node of the system is generated in in electronic format notification of acceptance or rejection of tax reporting by the system.
The system assigns to tax reports submitted in electronic form the status of acceptance ("Accepted"), and the status of processing for tax reports to be posted to the taxpayer's personal account ("Posted"), and also generates a notification about the acceptance or rejection of tax reports.
Thus, in the presence of the specified statuses of tax reporting in the notification, it is considered that the tax reporting has been checked by the requirement of format-logical control and does not fall within the norm of subparagraph 7) of paragraph 5 of Article 584 of the Tax Code.
Logical file structure
The lines of the attachment file (from the first line to the end of the file) contain the attachment data.
The lines of the file must be separated from each other by a pair of carriage return and line feed characters (codes 1310 and 1010), immediately following each other.
The file must not start or end with carriage return and line feed characters. Including empty lines in the file (repetition of the pairs "carriage return" and "line feed" several times immediately one after another) is not allowed.
Uploading information
Each line should contain the values of the attributes listed in Table A.1.
General requirements
The format-logical control log (FLC log) is generated for each attachment file.
The FLC log file name is constructed from the attachment file name by replacing the MO letters that start the file name with the letter L:
L + Information source + registry number-CMO / MO + YYYYMMDD, where
Source of information: 1 - SMO or 2 - MO,
registry number-CMO / MO - registry number CMO or MO
YYYYMMDD - the date on which the data was prepared.
The content of the file is transferred in the encoding of the Windows-1251 code page.
Logical file structure
The FLC log is transferred in a delimited text file. The file consists of lines separated from each other by a pair of carriage return and line feed characters (codes 1310 and 1010). A semicolon (";", code 3410) is used as a separator. Individual values must be enclosed in quotation marks when a semicolon or quotation marks are encountered within the value.
List of format-logical control errors
If at least one FLC error is found in a line, the line is not transferred for loading into the PC EPZ.
List of format-logical control errors
| The code | Field | Error description | additional verification |
|
| room | Column name |
|||
| Errors in specific fields of a record |
||||
| 2 | 3 | EPP | There is no EPP | There is no STP for the compulsory medical insurance policy of a single sample |
| 5 | 4 | Surname | Invalid characters or combinations of characters in the last name | The surname, first name or patronymic does not meet the rules of the FLC adopted in the EPZ |
| 6 | 5 | Name | Invalid characters or combinations of characters in the name |
|
| 7 | 6 | middle name | Invalid characters or combinations of characters in the middle name |
|
| 10 | 7 | Date of Birth | Date of birth not specified | |
| 11 | 7 | Date of Birth | Date of birth error | Unreal date specified:
|
| 21 | 13 | SNILS | Error in SNILS value | The specified value is either of the wrong length or contains characters other than numbers. |
| 22 | 13 | SNILS | SNILS check number error | The check digit (the last two digits) of SNILS was calculated with an error. |
| 25 | 2 | Polis_id | Series and number of DPFS are missing | There is no series and number for the old-style compulsory medical insurance policy or number for a temporary certificate |
| 242 | 15 | Attach_Mode | The code of the method of attachment to the MO is not specified | |
| 243 | 15 | Attach_Mode | Invalid code for the method of attachment to the MO | The attachment method code was not found in the coding system. |
| 246 | 17 | Attach_Date | Date error | Date errors: The date includes signs other than numbers, The number of digits is not equal to eight, The sequence of numbers cannot be interpreted as a valid date (for example, "19722510" or "19801234"). |
| 264 | 14 | ID_MO | Registry number not specified | |
| 265 | 14 | ID_MO | Registry number not found | The specified value was not found in the unified register of MO. |
| Other (common) errors |
||||
| 99 | – | – | An exception has occurred in the handler | |
Saving the declaration in the journal and using them as the initial data for the next period Powerful editor declarations Checking counterparties, loading declarations from xml files, powerful selections and much more ... And all this is even faster and more convenient New revision 3.1The most popular appendices of the alcohol declaration are appendices 5, 6, 7, 11 and 12.
The processing is intended for wholesalers or retail... In the updates for the future reporting company, the Appendices of the declaration are planned, which are necessary for enterprises engaged in the production of alcoholic beverages.
Even faster than ed. 2.x! High productivity of the formation of declarations according to the data of the infobase.
The implementation of the new edition for our clients with a network of about 150 stores showed the following results: Formation of Appendix 11 according to the information base (150 stores, more than 50,000 declaration lines) - about 3-4 minutes! Unloading in the FSRAR format - less than one minute! The same task in the Declarant-Alco program was completed for more than 48 hours.
Fully automatic filling of the declaration according to the information base.
All appendices of the declaration are filled in automatic mode... The data of the documents "Receipt of goods and services", "Sale of goods and services" are used, for Appendices 11 and 12 "Report on retail sales"," Transfer of goods "," Capitalization of goods "," Write-off of goods ".
Keeping a log of saved declarations
Now you can save reports to the journal. At the same time, it does not matter how your report was formed, according to the information base or it was downloaded from external file... You can use these reports to form the opening balances of the next reporting period.
Powerful declaration editor with the following functionality:
previously uploaded XML files, as well as declarations generated from the infobase data. The data of a newly generated report (not yet uploaded, i.e. directly from the monitor screen) can be manually edited with subsequent uploading of data to XML format;- Loading balances at the end of the previous reporting periodto data (in the form of initial balances) of the current reporting period with automatic recalculation of dependent indicators. This allows you to organize "selective" accounting, ie. by a limited subset of credentials contained in the infobase.
- Automatic filling of the columns "Receipt" and "Deliveries"In Appendix 5 and the column" Receipt"In Sec. 1 of Appendices 11 and 12. When correcting the data of Appendices 6 and 7, as well as Sec. 2 of Appendices 11 and 12, it is possible to automatically calculate the values of the indicators of the corresponding columns of Appendix 5 and Sec. 1 applications 11 and 12.
- The function of automatic recalculation of dependent indicators of the loaded report when editing baselines ... For example, when editing the opening balances, the ending balances are recalculated automatically.
Comprehensive verification of report data when uploading data to an XML file.
Indicators such as the presence of a product type code, the presence of a manufacturer, the correctness of the INN and KPP are checked (checking for the correctness of the INN and KPP is carried out via the Internet, using the service for checking counterparties for the Unified State Register of Legal Entities and USRIP), checking the ratios of the report's control indicators. If errors are found, the file is not uploaded, and the errors found are highlighted in red.
Automatic configuration of the information base for organizing the accounting of alcoholic beverages.
When you start processing for the first time or at any other time when you need it, the Accounting Setup Assistant will help you set up your account as quickly and comfortably as possible. information base for working with the product "Alcohol declaration". For example, the reference book "Codes of types of alcoholic beverages" is filled in automatically in accordance with the list of codes of alcoholic beverages approved by FSRAR.
Accounting for different manufacturers for one item of the item.
In UT10.3 and UT11 the mechanism of characteristics is used for this purpose. For each item characteristic used for accounting for alcoholic beverages, the "Manufacturer" property is added, which is filled in from the counterparties directory. For the BP3.0 version, this feature is not supported due to the lack of a characteristics mechanism in BP3.0. In this case, you need to use different items of the item for different manufacturers.
Drilling down the sum indicators of reports to the document and item level in one click.
It is not clear why this amount is in the report? You can get a detailed explanation of any amount in the report and, if necessary, open and edit directly the document or item of the item catalog that aroused your interest.
Possibility of reconciliation with counterparties thanks to a powerful selection system.
Selections are possible within the framework separate application, and for several applications of the declaration. For example, you can get data on a counterparty simultaneously for applications 6 and 7, which will allow you to reconcile data not only on deliveries, but also on returns.
Flexible system for managing report data sources.
The sources of data in the report can be: records of the accumulation register "Goods of organizations"; previously unloaded declaration files in the FSRAR format; when generating a report on the records of accumulation registers, it is possible to include or exclude the entry into the report of document movements without the mark “reflect in the account. accounting "
Signing, encryption and verification of declaration files is similar to FSRAR services
The generated files can be checked for compliance with the FCPAR format, signed and encrypted. You will not need to purchase such programs as Crypto AWP, everything is available from one workplace.
Works with basic versions
Processing does not require any configuration changes and can work with basic versions, significantly reducing the cost of implementation when using no more than one workplace.
Automatic update module via the Internet
Checking for updates can be carried out either at the user's request (in semi-automatic mode), and at each launch of the program. After purchasing the processing, you will receive an individual username and password for automatic updates.
Supported configurations
| Edition \ Configuration | Enterprise accounting | Trade management | Complex automation |
|---|---|---|---|
| 10.3 | |||
| 3.0 | |||
| 11.1, 11.2 | |||
| 1.1 |
You can get acquainted with the product in detail, having studied the documentation or if you contact us for advice.
The first idea of the product interface and some of its functionality You can see below in the screenshots, for different configurations.
You can always count on professional technical support from product developers with more than 3 years of experience in implementing alcohol declarations.
The delivery price includes technical support within 6 months after payment of the order.
.png)
Version for configurations 1C: Trade Management, rev. 10.3 and 1C: Integrated Automation 1.1
Version for configuration Trade management, revs 11.1, 11.2
Saved Declarations Journal
Declaration filling settings window
Money back guarantee
Infostart LLC guarantees you a 100% refund if the program does not match the declared functionality from the description. The money can be returned in full if you declare this within 14 days from the date of receipt of the money in our account.
The program is so proven in operation that we can give such a guarantee with complete confidence. We want all of our customers to be happy with their purchase.
Functioning efficiency automated systems depends on the degree of reliability of the input information. Distortion of information is possible at the stages of its registration, transmission and processing. A significant proportion of errors are introduced by the operator when registering information in the process of filling in primary documents. When transmitting data to a computer via communication channels, distortion of information is possible under the influence of interference, and in the process of information processing - as a result of failures and failures of individual computer devices.
To increase the level of information reliability, a variety of data control methods have been developed, which make it possible to detect errors that occur at all stages of information advance from the place of its origin to the place of processing. Since most of all mistakes are made when preparing information, we will consider methods of its control at this stage.
Information control during the preparation of primary documents includes various types of its checks, some of which are carried out directly in the process of preparing a document on a computer in the AWS system, the other part of the checks - in the central computer when entering a message.
Distinguish formatted and logical control.
When formatted control:
The number of characters in each entered message indicator is determined and compared with the required number;
The presence of an admissible number of indicators in the entered message is checked;
The presence of an alphabetic character is checked where the numeric character should be, and vice versa.
Under logical control:
The value of each indicator of the area message is checked permissible values, which is contained in the NSI;
A check is made for the mutual logical correspondence of individual indicators to each other within each phrase of the entered message and between different phrases (inter-phrase control);
The presence of errors in the most important indicators of the message, such as numbers of rolling stock units, stations, cargo, is revealed by calculating control signs.
Formatted and logical controls are performed for service and informational message phrases. If errors are detected, the subscriber who sent the message is issued a diagnostic message 497, which contains the error code and indicators where errors were made. The subscriber must correct errors, or re-enter the message.
Here are some examples of errors:
1. Formatting errors
1.1. Control of the correctness of the design of the message 02 as a whole.
| Start message | Message code | Train number | Train index | Conditional length | Train gross weight, t | Special marks | ||||||||||||
| ECP formation station | Squad number in order | ECP destination station | Number | Month | Hour | Minutes | Cover code | Oversized index | Livestock | Route | ||||||||
| № | ||||||||||||||||||
| (: | 03 |
The type of error shown in this example is a non-existent message code. Message 03 does not exist.
1.2. Format control of the service phrase
| Start message | Message code | ECP message transmission station | Train number | Train index | Sign of composition cheating (1- from the head, 2- from the tail) | Date and time of the end of the formation of the composition | Conditional length | Train gross weight, t | Special marks | |||||||||
| ECP formation station | Squad number in order | ECP destination station | Number | Month | Hour | Minutes | Cover code | Oversized index | Livestock | Route | ||||||||
| № | ||||||||||||||||||
| (: | 005 |
This shows a metric format error. The train number in order should consist of two characters, and not three, as in the example.
1.3. Format control of information phrase
| Carriage number in order | Inventory number of the car | Cargo weight, t | Cargo code | Consignee code | Special marks | Number of fillings | Number of containers | Wagon tare weight, t | Note | ||||||
| Cover code | |||||||||||||||
| № | |||||||||||||||
| 2011 | 00/00 | H0030 |
It also shows the formatted metric error. Owner's code, roller bearing mark must contain three characters.
2. Errors of a logical nature
2.1. Logical control of the service phrase.
The sign of the composition write-off must be equal to 1 or 2.
2.2. Logical control of information phrase
| Carriage number in order | Inventory number of the car | Owner code, roller bearing mark | Cargo weight, t | Car destination station code | Cargo code | Consignee code | Special marks | Number of fillings | Number of containers | ECP code of the exit border station | Wagon tare weight, t | Note | |||
| Belonging to the route, non-working fleet, group dispatch, coupled | Cover code | A special feature of the car (oversized, livestock, length, prohibition to dismantle from the hill) | |||||||||||||
| № | |||||||||||||||
| ____ | 00/00 |
If the weight of the cargo is non-zero, there must be information about the destination station of the car.
2.3 Logical interphrase control
| Carriage number in order | Inventory number of the car | Owner code, roller bearing mark | Cargo weight, t | Car destination station code | Cargo code | Consignee code | Special marks | Number of fillings | Number of containers | ECP code of the exit border station | Wagon tare weight, t | Note | |||
| Belonging to the route, non-working fleet, group dispatch, coupled | Cover code | A special feature of the car (oversized, livestock, length, prohibition to dismantle from the hill) | |||||||||||||
| № | |||||||||||||||
| 68011105 | 00/00 | ||||||||||||||
| 68011105 | 00/00 |
Identical inventory numbers of wagons
Conclusion
Based on the results of the control work, it is fashionable to draw a conclusion about the principle of functioning of the ASOUP.
When forming a train, the service and information blocks of message 02 (TGNL) are compiled, which is transmitted to the DCC. The service block contains information about the formed composition as a whole. The information block contains information about each carriage: inventory number, cargo weight, destination station, cargo code, etc.
If the composition does not correspond to the previously transmitted to the DVTs TGNL, then message 09 is generated, where all changes in the composition are indicated. The most common reason for this discrepancy is the planned uncoupling or coupling of wagons to the train en route, uncoupling of the wagon due to its technical or commercial malfunction.
When the train leaves the station, messages 200 are generated;
the arrival of the train at the station - message 201;
following the station by train - message 202;
disbandment of the composition - message 203;
loading a wagon - message 241;
unloading the wagon - message 242;
transfer of the car to the faulty group - message 1353
Each of the above messages gives information about the time of the formation of the train, the types of wagons in the train, the departure of the train from the station, the formation, loading and unloading of wagons, the hitching and uncoupling of wagons, the write-off of wagons to a non-working fleet, etc.
