Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
You won a bid on the public procurement portal, signed a contract, and a month later you're shipping goods to the government customer. The accountant asks: "Which contract should this go under? I need the contract number from goszakup for the procurement register." You open the invoice — but the "Government contract" field is empty, because you never entered the contract itself into the database. Or the other way around: the customer sent a reconciliation act showing the contract amount as 12,400,000 ₸, while your database shows shipments totaling 12,600,000 ₸ — an overage against the contract, and your payment will be withheld. To avoid this, each government contract is entered once into the "Government Contracts" directory, and then referenced from all shipments, invoices, and e-invoices.
1. Purpose
The "Government Contracts" directory stores records of agreements concluded under public procurement (in 1C, this is a separate type of agreement with a government customer). It is needed to link sales, invoices, and electronic documents (e-invoices, waybills) to a specific contract, to maintain separate accounting for each agreement, and to control the shipment amount against the contract amount.
2. Where to find it
- Via the section: "Reference Data and Administration" (or "CRM and Marketing" / "Sales" — depending on interface settings) → "Settings and Directories" group → "Government Contracts".
- From the government customer's counterparty card: open the partner → "Contracts/Agreements" tab → the list of linked government contracts is also available there.
- Direct 1C navigation link:
e1cib/list/Справочник.ГосударственныеКонтракты. Copy it, in 1C click "Tools" → "Go to navigation link" (or Alt+F1 / "More" menu → "Go to link"), paste it in — the directory list will open directly.
To create a new record — click "Create" in the list that opens.
2a. How to check your release
Main menu (question mark icon or "Tools") → "Help" → "About". The window will show two lines: "Platform version" (e.g., 8.3.24) and "Configuration" with the release number — you need the configuration release, which should be 3.4.5.21. If your release is different, some fields and printed forms may differ.
3. How to fill it out
Below are all the key fields of the record. REQUIRED fields are marked explicitly.
| Field | Why it matters / what happens if you get it wrong |
|---|---|
| Name (REQUIRED) | A short name for the contract, which you will use to find it in documents. Fill it in clearly: "GC-2026/114 Astana City Akimat." If written vaguely — you won't be able to find it later in the selection list when shipping. |
| Customer / Counterparty (REQUIRED) | The government agency or quasi-public sector entity the contract is concluded with. Its details are pulled into the e-invoice. Get the counterparty wrong — the e-invoice will go to the wrong recipient and will be rejected in the e-invoice IS. |
| Contract number on the portal (registration number) (REQUIRED) | The contract number from the public procurement system. This is the key for the register and for reconciliation with the customer. An empty or incorrect number — the contract won't be pulled into procurement reporting. |
| Conclusion date | The date the contract was signed. Delivery deadlines and the validity period are calculated from it. |
| Validity period (from / to) | The contract's effective dates. If you ship after the "to" date — under the contract this is already a delay, and the amounts may not be accepted for payment. |
| Contract amount (REQUIRED for control) | The total contract amount including VAT. It's used for control: the sum of all shipments must not exceed it. Understate it — the program won't let you ship the remainder; overstate it — you'll lose control over overages. |
| VAT rate | For 2026 government contracts — 16%. Don't leave the old 12% rate from previous contracts: the e-invoice IS will reject an e-invoice with the wrong rate. |
| Currency | Tenge (₸). Government contracts in Kazakhstan are conducted in the national currency. |
| Organization | Your supplier organization. Needed if there are several in the database — so the contract goes into the correct accounting. |
| Person responsible / Manager | Who manages the contract. Doesn't affect reporting, but helps distribute work. |
| Comment | A free-text field for notes (payment terms, specifications, advance payment). |
After filling it out, click "Save and close." Until the record is saved, you won't be able to select the contract in a shipment.
4. Worked example with journal entries
Scenario. Astana-Snab LLP (VAT payer) won a government procurement bid. Contract GC-2026/114 with the State Institution "Department of Education of Astana," amount 12,400,000 ₸ including 16% VAT, term from 02/01/2026 to 12/31/2026. In March, a batch of office supplies is shipped.
Step 1. Create a record in the directory: name "GC-2026/114 Dept. of Education," customer — the State Institution, registration number — 114-2026, amount 12,400,000 ₸, rate 16%.
Step 2. Create a "Sales of Goods and Services" document for this month. In the header, in the "Government contract" field, select the GC-2026/114 record. Shipment: goods worth 3,480,000 ₸ including VAT, of which VAT = 3,480,000 × 16 / 116 = 480,000 ₸, cost excluding VAT = 3,000,000 ₸. Cost of the goods — 2,100,000 ₸.
Journal entries when posting the sale (the directory itself doesn't create entries — they are generated by the document, where the contract serves as an analytics dimension):
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 3,000,000 | Revenue from sale to government customer recognized (excluding VAT) |
| 1210 | 3130 | 480,000 | VAT payable accrued (16%) |
| 7010 | 1330 | 2,100,000 | Cost of goods sold written off |
Step 3. From this same sale, issue an e-invoice, and if the goods are on the exemptions/traceability list — a waybill (SNT). The contract from the header will appear in the electronic documents as the basis.
Step 4. The customer makes payment. Receipt to the account:
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1030 | 1210 | 3,480,000 | Payment received from government customer to current account |
Contract control. After this shipment, 3,480,000 of 12,400,000 ₸ has been fulfilled. Remaining balance to ship — 8,920,000 ₸. When the total shipments approach 12,400,000, the program will warn about the limit.
5. Operation types
The directory itself is an analytics record; it doesn't have "operation types" like a document does. But a contract from it participates in various scenarios:
- Sale to government customer — direct sale of goods/works/services under the contract.
- Return from government customer — the reverse operation, also linked to the contract.
- Advance payment — prepayment under the government contract (if the terms provide for it).
- Separate accounting — grouping revenue and VAT by each contract for reporting.
- Performance control — comparing shipments against the contract amount.
6. What is generated upon posting
The directory itself, when saved, only creates a record in its own table (the card). Accounting entries are generated by the documents that reference it. When such a sale is posted, the following is generated:
- Journal entries (see example above): revenue 1210/6010, VAT 1210/3130, cost of goods 7010/1330; upon payment 1030/1210.
- Electronic documents: an e-invoice (in the e-invoice IS) indicating the contract; if needed — a waybill (SNT).
- Register movements: "Sales revenue and cost," "VAT," "Customer settlements," inventory movement registers — everywhere the contract appears as an analytics dimension/measurement, which provides separate accounting.
7. Printed forms
Mostly reference information is printed from the directory record, while primary documents come from the contract's documents:
- Contract card (contract details) — from the directory itself.
- Invoice for payment — from the "Customer Invoice" document.
- Goods release waybill (Form Z-2) — from the sale.
- Certificate of completed work (services rendered) — from the sale of works/services.
- Invoice (e-invoice) — electronic form from the e-invoice IS.
- Reconciliation act — for settlements with the government customer by contract.
8. Common errors
- "Field 'Name' is not filled in" — the record name is not set. Enter a short, clear name and save again.
- "Counterparty (customer) not filled in" — the government customer is not selected. Select it from the counterparty directory; if it doesn't exist — create it first.
- "Document amount exceeds contract amount" — total shipments exceeded the contract limit. Check the contract amount in the record and the shipment volume; if there's a supplementary agreement, increase the contract amount.
- "VAT rate does not match document date" — the 12% rate is still set in the record or document. For 2026, set it to 16%.
- "Document date is outside the contract validity period" — the sale date is later than the "to" date. Verify the period in the record or arrange an extension.
- E-invoice rejected in the e-invoice IS due to recipient — incorrect BIN/customer details in the record. Verify the government agency's details and reissue the e-invoice.
9. FAQ
1. How does a government contract differ from a regular customer agreement? It's a contract record specifically for a public procurement deal: it stores the registration number from the portal, the limit amount, and the government customer, and separate shipment control is maintained against it.
2. What is the VAT rate for a government contract in 2026? 16%. Don't use the old 12% rate on new contracts — e-invoices with it won't be accepted.
3. Does the directory generate journal entries? No. Journal entries are generated by documents (sales, payment receipts), where the contract is specified as an analytics dimension. See the example entries in section 4.
4. How is an overage against the contract amount controlled? The program compares the total of all shipments under the contract with the amount in the record and warns when approaching or exceeding the limit.
5. What if the customer sends a reconciliation act with a different amount? Open the reconciliation act by contract, check the shipments and payments. Discrepancies are usually due to a shipment made without a specified contract or an incorrect VAT rate.
6. Is a waybill (SNT) required for a government contract? If the goods are on the traceability/exemptions list or cross the state border — yes, an SNT is required; an e-invoice is always issued.
7. Where do I get the contract registration number? From the public procurement portal — it's the registered contract number. This is the number that goes into reporting and reconciliation.
8. Can one contract be linked to multiple sales? Yes. Under one contract, you can make as many shipments as you like within its amount — all of them reference the same record.
9. How do I increase the contract amount for a supplementary agreement? Open the record and change the contract amount to the new amount per the supplementary agreement, then save. After that, you can ship the remainder.
10. Is the government contract currency always tenge? Yes, public procurement in Kazakhstan is conducted in tenge (₸). Foreign currency is not used in a government contract record.
10. Related documents
- Basis for entry: data is taken from the signed public procurement contract (goszakup portal) and from the government customer's counterparty record.
- What is entered with a reference to the contract: "Customer Invoice," "Sales of Goods and Services," "Sales of Works/Services," "Return of Goods from Customer," payment receipt documents, e-invoice and waybill (SNT), reconciliation act.
How to check your release. Main menu → "Help" → "About": this shows the platform version and configuration release.
Material prepared for "Trade Management for Kazakhstan," release 3.4.5.21 (edition 3.4). Rates and figures — per Kazakhstan regulations for 2026: VAT 16%, MCI 4,325 ₸, minimum wage 85,000 ₸.