Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
It's morning, you are sending an electronic invoice (ESF) for yesterday's sale. You click "Send" — and instead of "Document accepted," you get a red window: "Authorization error. Failed to log in to the service." Or the bank has stopped pulling the statement, and the exchange with 1C-Reporting asks for a login that you don't remember. All of this can be fixed in one place — in the directory "Internet Service Authorization Settings". Here are the credentials (who you are for the external service) and the "keys to the door": login, password, token, expiration date. Let's break down how this works and how to fix it.
1. Purpose
The directory stores the login parameters for external internet services that 1C exchanges with: ESF (electronic invoices and accompanying documents), reporting services, direct bank exchange services, and counterparty verification services. One element = one account for one service. It does not create entries or tax movements — this is a technical setup for communication, not an accounting document.
2. Where to find
There are no direct buttons in the accounting sections for the directory; it opens from places where authorization is needed:
- Administration → Exchange of electronic documents → Exchange with ESF — there is the ESF account setup and a transition to its authorization parameters.
- Administration → Internet support and services — authorization for internet support services.
- Bank and cash → Bank exchange settings (DirectBank) — banking service credentials.
To open the list directly: Service → "Functions for technical specialists" (or "All functions") and find the directory by name. The fastest way is through the navigation link. Copy it, then in the 1C menu Service → "Go to navigation link" and paste:
e1cib/list/Directory.AuthorizationSettings
2a. How to know your release
The menu "Help" → "About the program" (or the ℹ icon next to the username). In the opened window: at the top — platform version (for example, 8.3.24.xxxx), below — configuration release "Accounting for Kazakhstan," version 3.0. The instructions were checked on 3.0.74.2. If you have a different release, the screen names of the fields may differ by a word or two, but the logic remains the same.
3. How to fill
You open an element or create a new one by clicking "Create". Let's break down the fields — what each is for and what the consequences of an error might be.
| Field | Mandatory | Purpose / what happens in case of an error |
|---|---|---|
| Name | Yes | A clear name for the setting so you can distinguish it in the list ("ESF LLP Romashka," "Kaspi Bank statement"). If left blank — it will not be saved. |
| Service (type of service) | Yes | Indicates which service the data is for: ESF, reporting, bank. If you make a mistake with the type — 1C will send the login to the wrong place, and you will receive an authorization refusal. |
| Organization | Yes (for ESF/bank) | Links the account to your organization. If there are multiple legal entities in the database and the wrong one is specified — documents will be sent under someone else's BIN. |
| User (login / IIN-BIN) | Yes | Identifier for logging into the external service. For ESF, this is usually the BIN/IIN and taxpayer login. Incorrect login — "user not found." |
| Password | Yes | Secret for logging in. Stored in the database, masked when entered. Incorrect or outdated — "invalid login or password." |
| Token / access key | Depends on the service | Technical session key. Lives for a limited time; after expiration, access is lost. Usually updated automatically upon reauthorization. |
| Expiration date (valid until) | Filled by the service | Date until which the token/session is valid. If it has passed — the exchange will stop, and reauthorization is needed. |
| Certificate / digital signature key | Yes for ESF | Key from the National Certification Center of the RK (GOSTKNCA/AUTH or RSA) used to sign documents. Expired or incorrect key — the signature will not pass. |
| Service address (URL) | Filled by default | Connection point. Change only if the service has officially changed its address; an arbitrary address will break the connection. |
| Main / use by default | No | Flag for a service with multiple accounts — which one to use by default. |
The practical order: first Service and Organization, then User/Password, then click "Check connection" (or "Log in"/"Authorize"). If the check is green — 1C will automatically fill in the token and expiration date. Only after that "Save and close".
4. Analyzed example
Situation. LLP "Romashka" (VAT payer) sold a batch of goods to LLP "Client" for 1,160,000 ₸ with VAT 16%. An ESF needs to be issued. But when sending — an authorization error: the token for ESF expired a week ago.
What to do.
- Open the directory via the navigation link, find the setting "ESF LLP Romashka."
- You see the "Valid until" field with a past date — that's the reason.
- Click "Authorize", select the digital signature key (AUTH key from the National Certification Center of the RK), enter the key password. The service returns a new token, and the expiration field updates to a future date.
- Save and close, return to the sales document, click "Send ESF" again — the status changes to "Sent / Accepted by ESF."
Document numbers for understanding where the 16% comes from:
- Cost excluding VAT: 1,000,000 ₸
- VAT 16%: 160,000 ₸
- Total including VAT: 1,160,000 ₸
The entries are generated by the sales document itself, not this setting:
| Debit | Credit | Amount, ₸ | Content |
|---|---|---|---|
| 1210 | 6010 | 1,000,000 | Revenue from sales |
| 1210 | 3130 | 160,000 | VAT payable (16%) |
| 7010 | 1330 | (cost) | Write-off of the cost of goods |
The "Authorization Settings" directory in this scenario does not create any entries — it simply opened the "door" to ESF so that the document with the VAT amount of 160,000 ₸ could be sent to the state system. This is its role: without correct authorization, the ESF with these figures simply will not be sent.
5. Types of services (what the directory covers)
There are no separate "types of operations" like in documents; instead, there are different types of services, each storing its own account:
- ESF — issuance and receipt of electronic invoices.
- Accompanying documents (part of ESF) — accompanying invoices for goods.
- Reporting service (1C-Reporting / taxpayer cabinet) — authorization for submitting tax return forms.
- Direct bank exchange service (DirectBank) — downloading statements and sending payments.
- Counterparty verification — verification of BIN/IIN and VAT payer status.
- 1C Internet support — updates, service functions.
6. What is formed upon saving
This is a directory, not a processed document, therefore:
- No entries (Debit/Credit) — it does not create movements in accounts 1210/3130/6010 and others.
- It does not issue ESF and accompanying documents — they are created by sales/purchase documents; the setting only gives them access to ESF.
- When clicking "Save", the directory element itself and related service information registers (saved token, expiration date, active session flag) are updated.
- After successful "Authorization", the service returns a token — it is recorded in the element, and then 1C uses it automatically until expiration.
7. Printed forms
The directory does not have its own printed forms — there is nothing to print; this is a technical setup. The actual exchange documents are printed: ESF and accompanying documents are printed from their journals ("Sales → Electronic invoices (ESF)"), not from here.
8. Common errors
"Authorization error. Invalid login or password." Check the User field (for ESF — correct BIN/taxpayer login) and re-enter the Password. If the password was changed in the cabinet — update it here as well.
"Token expiration" / "Session ended." The "Valid until" field is in the past. Click "Authorize" and re-sign with the digital signature key — the token and expiration will be updated.
"Certificate not found" / "Digital signature key is invalid." The key from the National Certification Center of the RK is expired, reissued, or the wrong file is specified. Reissue the key on egov/pki, then in the setting, select the current AUTH key again.
"The specified organization is not registered with the service." The Organization field has a legal entity whose BIN is not registered in ESF, or organizations are mixed up in a multi-company database. Set the correct organization.
"Failed to establish a connection with the service." This is often a network/address issue: check the internet and the Service address (URL) field — it should be standard, do not edit it manually. There may be technical work on the side of ESF.
"Account is already in use in another session." The same login was used from another workplace. End that session or wait for it to expire, then log in again.
9. FAQ
Does this directory create accounting entries? No. This is a technical authorization setup. Entries (for example, Debit 1210 Credit 6010 and Debit 1210 Credit 3130 for VAT 16%) are created by sales and purchase documents, not by it.
Where is the password for ESF stored? In the corresponding element of this directory, in the Password field. It is masked when displayed. If you change the password in the taxpayer cabinet — be sure to update it here as well.
I sent an ESF yesterday, today — "authorization error." What happened? Most likely, the token has expired (check "Valid until") or the password for the digital signature key has changed. Click "Authorize" and re-sign — the exchange will be restored.
How to reconnect if the digital signature key has been reissued? Open the ESF service setting, select the new AUTH key from the National Certification Center of the RK in the certificate field, click "Authorize," enter the key password, and save. The old key can be removed.
I have two organizations in the database. Is there one account for all? No. Each organization has its own authorization record with its own BIN; otherwise, the ESF will be sent under someone else's number, and the state system will reject it.
Can I set up bank exchange (statements) here? Yes, for banks with direct exchange (DirectBank), the credentials are also stored in this directory, with the service type being banking.
Does the setting affect the VAT rate in ESF? No. The rate (in 2026, the base is 16%) is taken by the sales document from the nomenclature and contract data. Authorization only delivers the already formed ESF to ESF.
Is anything printed from this directory? No, it has no printed forms. Print ESF and accompanying documents from their journals.
Should I delete the expired setting or fix it? Fix it: click "Authorize" and update the token/key. Deleting will break the connection and require reconfiguration. Only delete completely unnecessary accounts (closed legal entities, left the bank).
Why is there a future date in the "Valid until" field, but the exchange still does not go through? Then the problem is not with the token: check the internet, service address, and whether there are any technical works on the side of ESF.
10. Related objects
- Exchange settings with ESF (Administration → Exchange of electronic documents) — the main point from where you come to the ESF authorization parameters.
- Documents "Sales," "Purchase" — they use this authorization to issue ESF and accompanying documents.
- Journal "Electronic invoices (ESF)" (Sales section) — where you can see the result of sending: "Sent," "Accepted," "Rejected."
- Bank exchange settings (DirectBank) — banking account, also relies on this directory.
- Certificates of digital signature keys — keys from the National Certification Center of the RK that you connect in the certificate field.
How to know your release. Menu "Help" → "About the program": there you will find the version of the 1C:Enterprise platform and the configuration release "Accounting for Kazakhstan," version 3.0.
The manual was prepared for release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). In adjacent releases, button names may differ slightly.