Verified on release 3.0.74.2 "Accounting for Kazakhstan" (revision 3.0).
The director has been on a business trip for three days, but an ESF needs to be issued and signed for the buyer today — otherwise you'll miss the shipment. The accountant can't sign: they don't have the right of first signature, and the director's certificate "hangs" without its owner. Or another situation: an act has gone "for approval," but no one understands who should endorse it first — the lawyer or the chief accountant — and the document has been stuck for a week. It is precisely these knots that the "Signing Routes" document untangles. You describe once who signs documents, in what order, and with what signature, and from then on the program itself guides the document along this chain.
An important note upfront: this is an organizational/administrative document, not a "primary" document. It does not make accounting entries Dr/Cr and does not accrue taxes. Its task is to set signing rules. Entries and VAT appear in the documents (sale, ESF, act) that will go along this route.
1. Purpose
The document sets a route — a sequence of approval and signing steps for a specific type of document and organization. It determines who signs, in what order, with what signature (approval / endorsement / EDS), and whether the step is mandatory. Then documents automatically go along this chain.
2. Where to find it
You can open the list of routes as follows:
- Section "For the Manager" (or "Administration" → "EDM and Signing", depending on the configured interface) → "Signing Routes".
- The "Create" button — a new route.
A quick way to open the list right in 1C: Main Menu → "Functions for the Technical Specialist" → "Navigate by link" (or the navigation field), paste:
e1cib/list/Документ.МаршрутыПодписания
The functional option for electronic document management / signing must be enabled beforehand ("Administration" → "Electronic Document Exchange" and EDM settings). If the section is not visible — the option is disabled.
2a. How to find out your release
"Help" → "About" (or the "i" icon in the top right corner). In the window that opens you will see the platform version (for example, 8.3.24.x) and the configuration release — the line "Accounting for Kazakhstan, revision 3.0 (3.0.74.2)". It is the configuration release that you should compare with this guide: the set of route fields changes between releases.
3. How to fill it in
We'll go through the fields in order. Mandatory ones are marked explicitly.
| Field | Why it's needed and what happens if there's an error |
|---|---|
| Name (MANDATORY) | A clear route name, for example "ESF sale — standard". You will use it to select the route in documents. An empty name won't let you save; a vague one — you won't find the right one later. |
| Organization (MANDATORY) | The route operates within its organization. Make a mistake — documents of another organization won't pick up the route, and signing will "hang". |
| Date | The date the route was entered/took effect. Affects from what moment the rule applies. |
| Document type (kind) to which the route applies | You specify what we are routing: ESF, SNT, work completion act, contract, etc. The wrong type — the document will go "past" the route or the route won't be offered at all. |
| Effective / Active (flag) | Puts the route into operation. An unchecked flag = the route is described but not applied. |
The tabular section "Route Steps" (the heart of the document):
| Step column | Why and what happens if there's an error |
|---|---|
| Order / Step No. (MANDATORY) | The sequence: first step 1, then 2, etc. Mix up the order — the chief accountant will endorse before the executor, and the approval logic will break. |
| Signatory — employee/individual or role (MANDATORY) | Who performs the step. You can specify a particular person (director Kim A.) or a role ("Manager", "Chief Accountant") — then the step will be assigned to whoever is currently in that role. An empty signatory = there's no one to perform the step, the document will stall. |
| Action type | What the signatory does: Approval (endorsement), Endorsement, or Signing with EDS. For ESF the key one is the step with EDS; without it the document won't go to the IS ESF. |
| Certificate / EDS key | For the EDS step — which certificate is applied. An incorrect or expired certificate = a signing error at the most critical step. |
| Mandatory step (flag) | A mandatory step cannot be skipped. An optional one can be skipped. Make "director's endorsement" optional — the document will go out without the key signature. |
| Condition (if supported by the release) | A constraint under which the step is enabled (for example, an amount above a limit). Requires checking in your release — the set of conditions is version-dependent. |
Check: each step has order and signatory filled in, and the last step for electronic documents is signing with EDS. Then "Save" and "Post".
4. Worked example
Task. Set up a route for outgoing sales ESF at LLP "Astana Trade". The rule: first the accountant endorses the document, then the director signs with EDS.
We fill in the route:
- Name: "ESF sale — standard"
- Organization: LLP "Astana Trade"
- Document type: Invoice (ESF)
- The "Effective" flag — checked.
Steps:
| No. | Signatory | Action type | Mandatory |
|---|---|---|---|
| 1 | Accountant Nurlan S. | Approval | Yes |
| 2 | Director Kim A. | Signing with EDS | Yes |
We post the route. There are no accounting entries — the document only writes service records (see section 6).
How it works next. We sold goods for 1,160,000 ₸ with 16% VAT. Breakdown of the amount:
- Cost without VAT: 1,000,000 ₸
- 16% VAT: 160,000 ₸
- Total: 1,160,000 ₸
The entries are made not by the route but by the "Sale of Goods and Services" document and the ESF associated with it:
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 1,000,000 | Income from sale (without VAT) |
| 1210 | 3130 | 160,000 | 16% VAT payable |
| 7010 | 1330 | (cost) | Cost of goods written off |
When the accountant sends this ESF for signing, the program will guide it along the "ESF sale — standard" route: first the accountant's endorsement (step 1), then the director's EDS (step 2), after which the ESF goes to the IS ESF. Until both mandatory steps are passed, the document will not be sent to the state system.
5. Operation types
The route usually does not have a separate "Operation type" field — the "type" is in effect the document type for which the route is created. Typical scenarios:
- Route for ESF (outgoing invoices).
- Route for SNT (accompanying waybills for goods).
- Route for sales acts/waybills.
- Route for contracts and internal documents for approval.
- Different routes by organization within one database.
6. What is generated on posting
- There are no accounting entries. This is not a primary document.
- Records are generated in the signing/routing registers — the binding "document type + organization → route and its steps". It is from these that the program takes the chain when you send a document for signing.
- Tasks/approval stages appear for the assigned signatories (in the "for signing/for approval" list).
- The route does not itself create the ESF and SNT and does not send them to the IS ESF. Sending happens from the ESF/SNT itself after the route steps are passed.
7. Printed forms
For a service document like the route, the set of printed forms is minimal:
- "Signing Route" — a description of the route with a list of steps and signatories (for internal regulations/order).
- "Approval Sheet" — for a specific document that has passed the route: who endorsed it, when, and with what signature.
The actual printing of ESF, SNT, acts, and waybills is done from the corresponding primary documents, not from the route.
8. Common mistakes
"The 'Organization' field is not filled in". The route is not bound to an organization. Fill in the "Organization" field — without it the rule won't be picked up by documents.
"The signatory in row N is not filled in". The step has an empty responsible person. Specify an employee or role in each row of the tabular section.
"No signing route found for this document type for the organization". You are sending, for example, an ESF for signing, but there is no active route for this type. Check: the route is created for the right organization, the correct document type is specified, and the "Effective" flag is set.
"Signature certificate not found / validity period expired". An invalid certificate is specified at the EDS step. Update the certificate in the route step and in the signing settings.
"Cannot complete: a mandatory step has not been passed". Someone is trying to send the document, bypassing a mandatory endorsement/signature. Either the step must be performed, or remove the "Mandatory" flag (deliberately) in the route.
The document "hung" at approval. The signatory is specified as a particular employee, but they have been dismissed/are on vacation. Replace them in the step or use a role instead of a specific person.
9. FAQ
Does the "Signing Routes" document make accounting entries? No. It is a service document. It does not generate Dr/Cr and does not accrue taxes. The entries are made by the documents that go along the route (sale, ESF, etc.).
How does the route differ from the ESF itself? The route is the rule "who signs and in what order". The ESF is a specific electronic invoice with amounts and VAT. The route only guides the ESF along the signing chain.
Can you set up separate routes for ESF and for SNT? Yes. Create a route for each document type. One organization can have several routes for different types.
What to specify in a step — an employee or a role? Better a role ("Manager", "Chief Accountant"): with personnel changes the route won't break. Specify a particular person when the signature is strictly personal.
The director is away — how to sign an ESF? Either provide in advance for a substitute signatory/role in the route, or temporarily change the step. A mandatory step with EDS cannot be skipped — without a signature the ESF won't go to the IS ESF.
Does the route affect the VAT amount in the document? No. VAT (in 2026 the rate is 16%) is calculated in the ESF/sale itself. The route does not affect amounts and rates.
Why does it say the route is not found when sending an ESF? There is no active route for this document type and organization. Check the document type, organization, and the "Effective" flag.
Can you make a step optional? Yes, uncheck the "Mandatory" flag. Then the step can be skipped. For manager's endorsement and EDS this is not recommended.
Where can you see who has already signed the document? In the printed form "Approval Sheet" for a specific document or in the list of approval/signing tasks.
Do you need to re-post the route after changing the steps? Yes. After editing the steps, save and re-post the route so that the routing service records are updated.
10. Related documents
- What it is entered on the basis of: a standalone configuration document. It relies on the reference books "Organizations", "Employees/Individuals", EDS certificate settings, and EDM.
- What the route uses: the documents that go along it — Invoice (ESF), SNT, Sale of Goods and Services, Work Completion Acts, contracts, etc.
- Related mechanisms: electronic document exchange (IS ESF, SNT), the list of approval/signing tasks, signing settings.
How to find out your release
"Help" → "About": there the 1C:Enterprise platform version and the configuration release are indicated. Compare the line "Accounting for Kazakhstan, revision 3.0" with the release number of this instruction.
This guide was prepared for "Accounting for Kazakhstan", revision 3.0, release 3.0.74.2. In other releases, the set of route fields and steps may differ.