How to competently organize the work of the Accounting and Warehouse Department in 1C?

Question

1C

There is a construction organization that has:
- Accounting - sits in Moscow and works in its 1C database. Everything that is purchased at the facilities, invoices and invoices are held by the accountant at the facility remotely in this 1C database.
- Warehouse - at 2 construction sites, which are usually located far from Moscow, this organization organizes its own warehouses. The warehouse manager bought himself a 1C configuration as an individual, created his personal database and maintains it, the exchange with another object is done through uploading to mail.
All this results in the following confusion - the accounting department lives in one kingdom, the warehouse lives in another. That is, all item / inventory numbers, names, etc. the warehouse is completely different from the real-accounting. When the accounting department and the warehouse need to verify what, where it is, what has been written off, etc. (they do it, it seems, once a month), it requires too many unnecessary body movements.
Question:
How should the work of the Warehouse department be organized in fact? Is it possible and necessary to close the Warehouse at the base where the accounting department works? Maybe some kind of division is being made, according to configurations, for example, but so that they are somehow synchronized? What can be read about this?

Answer 1

That's what data exchanges are for. If trade management is used for the warehouse, for enterprise accounting, then data exchange can be used standard from the configuration. But in order to get the job done, you first need to bring the entire nomenclature to a single view so that any attribute of the nomenclature in the two databases is identical, for example, a name or code. Since the warehouse and accounting department never took care of this, it will most likely require a lot of manual work to fill in the initial data.
Or another option is to transfer everyone from UT + BP to integrated automation, then the warehouse and accounting department will work in the same database, having the functionality of both accounting and warehouse.
If trade management is used in the slightest degree seriously, then transferring everyone to accounting will most likely be undesirable

Answer 2

You didn't write what configuration you have in stock. If Trade Management, then there is built-in synchronization with the Accounts Department of the Enterprise through the so-called. exchange plan. There are alternative upload options on info start.ru.

Answer 3

Is it possible and necessary to close the Warehouse at the base where the accounting department works? Maybe some kind of division is made, according to configurations, for example,

It all depends on the type of accounting that is seen at the facilities.
I would consider one of the sync options:

1. If there is no problem with the Internet at remote sites, then you can install a web server on the server, publish the database on it and connect to it from anywhere. And with accounting, set up a typical exchange.
2. If there are problems with the Internet, and the database is always needed, then we set up a distributed information base for trade management. Each object will have its own local copy, which is exchanged with the central one, and the accounting department is already exchanging with the central database.
3. Using a typical exchange, set up regular synchronization via ftp, email, or a dropbox-type service.
4. If the same configuration is used at all points, then you can try to configure everything through an exchange between identical bases. At the beginning, you will have to clean up duplicates, but then there will not be much problems.