In 2026, an existing 1C database is added to the launch list using its actual address, after which users log in with their own account; Article 694 of the Tax Code of the Republic of Kazakhstan establishes the deadline for submitting the individual income tax and social tax return, but it does not establish the procedure for the technical configuration of the software (Article 694 of the Tax Code of the Republic of Kazakhstan).
How Logging In to 1C Works
Logging in to 1C consists of two separate stages. First, the platform must locate the infobase: it is added to the list that the user sees after launching the software. The user is then authenticated in the database itself—the user account is selected and, if required by the settings, a password is entered.
Adding a database to the launch list does not create a new accounting database or transfer data to it. The connection settings for an existing infobase are saved on the workstation. Therefore, before configuring it, it is important to determine where it is located: in a folder on the computer or network, on a 1C server, or at the address of a published database.
An accountant should not select a connection address at random. An incorrectly specified folder may lead to an old copy, a test version, or an archive. As a result, documents may be entered into a database other than the production database, even though the software name and interface look familiar.
How to Add an Existing Database
Open the 1C launch window and select the command for adding an infobase. Then specify that you need to connect an existing database rather than create a new one. In the subsequent steps, the required settings depend on how the database is hosted.
For a file-based database, you will need the path to the folder where it is stored. For a client-server database, you will need the server name and the infobase name. For a published database, you may need the connection address and access credentials provided by the administrator or support specialist.
It is best to obtain the complete path from the responsible specialist. If entering it manually, preserve the exact spelling of the server, folder, and database names. You should connect only to the address used by the organization for its current operations.
After adding the database, give it a clear name. A practical option is to include the organization’s name and the database’s purpose, for example, “Company — Accounting” or “Company — Payroll.” If production, test, and archive versions are used alongside one another, this distinction must be clearly reflected in their names.
Before entering documents for the first time, check:
- the organization’s name within the database;
- the working period currently open in the software;
- whether the latest documents entered are present;
- the name of the selected user;
- whether the required sections and reports are accessible;
- whether the name or interface contains any indication that this is a test or archive copy.
If the database already appears in the list but does not open, adding the entry again may not resolve the underlying issue. Check the saved path, access to the network folder or server, user settings, licence status, and whether the installed platform meets the requirements of the configuration being used.
What to Check Before the Accountant Starts Work
Access to the infobase should be configured according to the employee’s duties. Regularly working under a shared account makes it difficult to identify the user who created or modified documents. Full administrative rights should be reserved for the responsible specialists who need them to maintain the database.
The 1C user password and the remote access password may apply to different stages of the connection. The first is used for authentication within the infobase, while the second is used to log in to a server, remote computer, or publishing service. It is unsafe to send access credentials through open chats or keep them near the computer.
Before updating the platform, migrating the database, or changing the connection settings, prepare an up-to-date backup. You should also record the current database address and make sure that the backup can be used for recovery. The installation of a different platform version should be agreed with the specialist responsible for supporting the software.
Before starting work, it is useful to record the database’s current name in the launch list, the path or connection address, and the version of the installed platform. This information will help restore the settings after replacing the computer and make it easier to describe the issue to a specialist.
The cost and duration of installing the platform, configuring the connection, or reinstalling the licence depend on the terms of the specific service provider. If these services are ordered separately, the request should specify their scope: platform installation, database connection, launch testing, user configuration, and verification of access to the required sections.
If You Cannot Log In to 1C
First, record the exact text of the error message, preferably together with a screenshot. Saying “cannot log in” is not enough: the specialist needs to understand whether the software cannot locate the database, rejects the username or password, reports that no licence is available, prompts you to change the platform version, or stops working after launch.
Then check the network connection and the availability of other corporate resources. If the database is located on a server, a lack of connection to the corporate network may prevent login. For a file-based database, you should also check whether the specified folder exists and whether the user has been granted access to it.
If the authentication window opens but the password is not accepted, check the selected user and the keyboard layout. Do not repeatedly try different passwords or use someone else’s account. Access should be restored by a specialist authorized to manage the database’s users.
Do not remove the database from the launch list until its settings have been saved. Removing an entry from the list usually affects only the settings of that particular workstation; however, without the recorded address, reconnecting the correct database will be more difficult. You should also not replace the production database with a backup copy merely for testing purposes: data recovery must be agreed with the responsible specialist.
If the issue appeared after an update, data migration, or computer replacement, tell the specialist exactly what changed and when the database was last opened successfully. Specify the database name, username, connection method, and full error message. This will make it possible to systematically check access, connection settings, and the compatibility of the installed components.
Questions and Answers
Does adding a database to the launch list create a copy of the data? — No. The launch list stores the connection settings for an existing infobase. A copy or a new database is created through separate actions.
Why does the database appear in the list but fail to open? — Possible causes include an incorrect path, lack of access to the folder or server, incorrect user credentials, licence status, or incompatible platform and configuration versions. The exact error message is required for diagnosis.
Can I configure access myself? — Yes, provided that you know the correct database address, connection type, and your account credentials. It is best to obtain the settings from the administrator to avoid connecting to an archive or test copy.
Does an accountant need to log in with full permissions? — User permissions should be determined according to the user’s job duties. Administrative access is required by employees responsible for configuring and maintaining the infobase.
What should be done before migrating or updating 1C? — Prepare an up-to-date backup, save the current connection settings, and ensure that the platform version is compatible with the configuration being used. After the work is completed, check that the database launches and that the user has access to the required sections.
What to Keep for Support Purposes
For future support requests, it is useful to keep the production database name, its address, the connection method, the person responsible, and the procedure for obtaining access in the internal documentation. Passwords should not be included in such a memo. When the database address changes or the server is replaced, this information must be updated so that employees do not continue working in the old copy.