Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
You filed the VAT declaration (form 300.00) for the first quarter. A week later, a manager "corrected" the March sale — re-posted the document, and the VAT amount shifted by 12,000 ₸. The declaration no longer matches the database, and you only find out during reconciliation. Sounds familiar? To prevent this, 1C has a mechanism called "Data Change Restriction Dates": you set a date before which no one (or only selected users) can add, re-post, or delete a document. The Report.ДатыЗапретаИзменения report shows which dates and for whom are currently in effect.
1. Purpose
"Data Change Restriction Dates" is protection for a closed period. You set a date before which data cannot be edited. The report of the same name displays a summary: who, for which section, and with what date is currently restricted. This is a service administration mechanism, not an accounting document — it does not generate postings.
2. Where to find it
Two things are located in different places — the date setting and the report on them.
Date setting:
Master Data and Administration → User and Rights Settings → block "Data Change Restriction Dates" → enable the checkbox "Data Change Restriction Dates" → link "Set up".
Report (summary of active dates):
Opened via a navigation link. Menu Tools → All Functions → branch Reports → Data Change Restriction Dates (if "All Functions" is hidden — enable it in Tools → Options).
To open the report directly: Tools → Go to navigation link → paste:
e1cib/list/Отчет.ДатыЗапретаИзменения
2a. How to find your release
Help (the "?" icon in the top-right corner or the main menu) → "About the program". In the window that opens, you will see the platform version (e.g., 8.3.24.xxxx) and the configuration release — a line like "Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)". Check that the release matches the one specified at the top of these instructions: the location of checkboxes sometimes changes between releases.
3. How to fill it out
It is the setting itself that is filled in (the report only reads the result). The order is as follows.
Step 1. Enable the "Data Change Restriction Dates" checkbox (REQUIRED). Without it, the entire mechanism is disabled, and the date has no effect on anything.
Step 2. Choose the method for specifying the date (REQUIRED). The button/switch "Method for specifying the restriction date":
| Method | When to use |
|---|---|
| Common date | One date for everything and everyone. The most common choice for a small company. |
| By section | Different dates for different accounting sections (e.g., "Regulated Accounting" is closed through 03/31, but "Orders" is not). |
| By section and object | Additional detail by organization. Needed if the database has multiple legal entities and you close them one by one. |
If you choose the wrong method, you'll get the wrong restriction scope: you'll set a "Common date" when you only wanted to close regulated accounting, and end up blocking managers' operational orders.
Step 3. Set the restriction date (REQUIRED). In the "Restriction date" field, specify either a specific date (03/31/2026) or a relative one. A relative date is convenient because it moves automatically:
| Value | What it means |
|---|---|
| End of last year | 12/31 of the previous year |
| End of last quarter | last day of the closed quarter |
| End of last month | last day of the previous month |
| Previous day | everything up to yesterday is closed |
Meaning of the date: it is forbidden to change data whose date is less than or equal to the restriction date. If you set 03/31/2026, March and earlier are closed, and April is open.
Step 4. Configure who the restriction applies to. By default, the restriction applies to all users. You can add exceptions: a row "For all users" plus separate rows for a specific user or group. Logic: the chief accountant's date can be left blank (can edit everything), managers' date — 03/31/2026. If you leave the date blank for everyone, the mechanism effectively does not work.
Step 5. Save and close. The setting takes effect immediately. Open the Report.ДатыЗапретаИзменения report and make sure you see the expected picture.
4. Worked example
Situation. "Astra" LLP is on the general tax regime. In March 2026, a sale of goods to a customer was posted: goods worth 250,000 ₸ excluding VAT, VAT 16% = 40,000 ₸, total 290,000 ₸. An e-invoice (ESF) was issued. The 300.00 declaration for Q1 was filed on 04/15/2026.
Here are the postings for that very sale you are protecting from edits (standard Kazakhstan chart of accounts):
| Dt | Ct | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 250,000 | Sales revenue excluding VAT |
| 1210 | 3130 | 40,000 | VAT payable (16%) |
| 7010 | 1330 | 160,000 | Cost of goods written off |
Action. To prevent anyone from rewriting these figures retroactively, you go to Master Data and Administration → User and Rights Settings, enable "Data Change Restriction Dates", choose the "Common date" method, and set the restriction date to 03/31/2026. For the chief accountant, you leave a separate row with a blank date.
Result. On 04/20/2026, a manager tries to re-post the March sale — 1C refuses and states that changing data before 03/31/2026 is forbidden. The VAT amount of 40,000 ₸ and revenue of 250,000 ₸ remain untouched, and the declaration continues to match the database. The chief accountant, if a corrective e-invoice is needed, can still edit the period — their date is blank.
Note: the mechanism itself does not generate postings. It only prevents changes to postings that already exist.
5. Operation types (setting variants)
The full set of modes provided by the mechanism:
- By date specification method: common date, by section, by section and object.
- By date type: absolute (specific date) and relative (end of last month/quarter/year, previous day).
- By scope of persons: for all users, for an individual user, for a group of users.
- Separately — "Data Import Restriction Date" (in the same window nearby): restricts not manual editing, but data import/exchange up to the specified date. Useful when synchronizing with an accounting database or GIS.
6. What is generated
To be clear: this is a report and a setting, not a document.
- No postings. The mechanism does not post anything to accounts — it blocks changes to movements that already exist.
- Electronic documents (ESF, SNT) are not created. But it is precisely this period protection that prevents an already-sent e-invoice from being accidentally reissued or deleted retroactively in the information system.
- Setting storage: the specified dates are stored in a service information register of restriction dates. The
Report.ДатыЗапретаИзмененияreport reads this register and displays the current values by user, section, and object. - Trace in the log: the fact of changing the setting is visible in the
Event Log(Master Data and Administration→Support and Maintenance→Event Log).
7. Printed forms
The mechanism has no specialized forms — this is internal control, not primary documentation. Standard options are available from the report:
- Print the generated report (the "Print" button / Ctrl+P).
- Save the result to a file: Excel (.xlsx), PDF, spreadsheet document (.mxl) via the "Save" button.
- Send the report by email directly from the form (if an account is configured).
8. Common mistakes
"Changing (writing) data related to a period before <date> is forbidden. Please contact the administrator." Classic: a user tries to post or re-post a document dated within a closed period. The correct fix is either to set an open-period date on the document, or (if the edit is legitimate) have the administrator temporarily move the restriction date / add an exception for that user.
The setting is configured, but the restriction doesn't work. Check the "Data Change Restriction Dates" checkbox — it must be enabled. Also check whether the user has a blank date in their personal row: a blank date means "can edit everything".
The restriction affected future documents.
You set an absolute date in the future or mixed up the method. Open the Report.ДатыЗапретаИзменения report and check which date is actually applied to the user.
Cannot issue a corrective/additional e-invoice for a closed period. Correcting an e-invoice is legally possible, but the period is closed by the restriction date. Add a personal row with a blank date for the chief accountant, or carefully move the common date, make the correction, and move the date back.
"All Functions" is empty, can't find the report.
The "All Functions" menu is disabled. Enable it: Tools → Options → checkbox "Display the 'All Functions' command".
9. FAQ
(see FAQ block)
10. Related documents
- "Data Import Restriction Date" — an adjacent setting in the same window; restricts import/exchange, not manual editing.
- Data synchronization settings — when exchanging with an accounting database, the import restriction date prevents documents from being pulled into a closed period.
- Event Log — records who changed the restriction dates and when.
- Month-end closing / routine operations — a logical trigger: you closed the period, filed 300.00 and 200.00 — immediately set the restriction date.
- This mechanism has no separate source document and nothing is entered based on it — it is an administration setting.
How to find your release: Help → About the program — there you'll find the platform and configuration release.
Guide prepared for "Trade Management for Kazakhstan", edition 3.4, release 3.4.5.21.