Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
You submitted the VAT declaration for the II quarter, balanced the accounts, and reported to the tax authority. A week later, the manager "corrected" the invoice dated May 15 — changed the quantity, and the sales amount "went off". Now your submitted report does not match the database, and you find out about it only during the next reconciliation. Familiar? To prevent this from happening again, 1C has Data Change Prohibition Dates — a mechanism that locks past periods. After setting the prohibition date, no one (or everyone except you) will be able to conduct, change, or delete a document dated before this date.
This is not a document or report in the usual sense — it does not create entries and does not issue printed forms. It is a protective setting. But in terms of importance, it ranks alongside closing the month.
1. Purpose
The prohibition date for changes is a time boundary, before which the database is "frozen". The program blocks the recording, conducting, re-conducting, and deletion of any documents and records related to the period before this date. It is needed to maintain the integrity of the submitted reports and protect against accidental or intentional retroactive edits.
2. Where to find
Menu path: section "Administration" → "User and Rights Settings" → in the group "Data Change Prohibition Dates" the link "Data Change Prohibition Dates".
First, you need to enable the mechanism itself: there is a checkbox "Data Change Prohibition Dates" (or "Data Change Prohibition Dates"). While the checkbox is unchecked, the settings form is unavailable.
1C navigation link: e1cib/list/Report.DataChangeProhibitionDates
To open the object directly: "Service and Settings" (▼ icon in the upper right corner) → "Functions for Technical Specialist" → "Go to Navigation Link" → paste the link above → "Go".
Do not confuse with "Data Upload Prohibition Date" — this is a separate setting that restricts changes only during exchange (synchronization) with other databases, not manual input.
2a. How to know your release
"Help" (or menu "Service and Settings" → "About the Program"). In the opened window, you will see two lines: platform version (for example, 8.3.24) and configuration release — "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". The instructions are relevant for release 3.0.74.2; in nearby releases, the location of the fields is the same.
3. How to fill
Step 1. Enable the mechanism (MANDATORY)
In the section "Administration" → "User and Rights Settings" check the box "Data Change Prohibition Dates". Without it, no restrictions will work, no matter how many dates you enter.
Step 2. Choose the date specification method
In the settings form, there is a switch "Method of specifying the prohibition date" with three options:
| Method | What it does | Who it suits |
|---|---|---|
| General date | One date for the entire database and all users | Small accounting, one accountant |
| By sections | Different dates for regulated accounting, payroll, bank, etc. | When the tax period is closed, but you are still calculating payroll |
| By sections and objects | Dates down to a specific organization / counterparty | Multiple legal entities in one database |
If you make a mistake with the method — for example, set "General date" to 31.12.2025, and you have not yet calculated payroll for January — the program will block the payroll documents for January... no, January is after 31.12 — it will open. However, December adjustments for payroll will not go through. Therefore, when there are different deadlines for submission, choose "By sections".
Step 3. Specify the date itself (MANDATORY)
In the column "Prohibition Date", you can set the date in two ways:
- Specific date — for example,
30.06.2026. Everything dated on or before this date is locked. - Relative date (selection button → "Other date") — "End of last month", "End of last quarter", "End of last year". Convenient because the date automatically shifts: set "End of last month" — and you do not need to change it manually every month.
What to remember: the prohibition is effective up to and including the specified date. A prohibition date of 30.06.2026 means that a document dated 30.06.2026 cannot be changed, while one dated 01.07.2026 can.
Step 4. Set who the prohibition applies to
The button "Set Prohibition Date" or the column "User". Options:
- "For all users" — a general lock, including the administrator.
- For a specific user or group — for example, managers are prohibited from 31.05.2026, while the chief accountant has no date at all (can edit).
Practical tip: set the prohibition "For all users" on the closed period, and create a separate line for yourself (the chief accountant) with a blank date or an earlier date. Then you will be able to make adjustments, while others cannot.
Step 5. Record the setting
Click "Save and Close". The date takes effect immediately; no restart is needed.
4. Analyzed example
Situation. LLP "Astana-Trade", a VAT payer, submitted the VAT declaration (form 300.00) for the II quarter of 2026. Sales for the quarter amounted to 5,800,000 ₸ excluding VAT, VAT 16% = 928,000 ₸. The chief accountant wants to close the period so that the managers do not touch the invoices from May and June.
Setting:
- "Administration" → the checkbox "Data Change Prohibition Dates" is checked.
- Method: "By sections".
- Section "Accounting" → Prohibition Date
30.06.2026→ "For all users". - Separate line: user "Chief Accountant" → prohibition date blank.
What happens next. Manager Akhmetov opens the expense invoice (sales) dated 20.06.2026 for product 1330 and tries to change the quantity. When attempting to conduct the document, 1C issues:
"Data Change Prohibition Date: 30.06.2026 (Accounting). Data change not performed."
The document remains unchanged. The entries of that invoice do not change and continue to exist as they were:
| Operation | Debit | Credit | Amount, ₸ |
|---|---|---|---|
| Income from sales recognized | 1210 | 6010 | 928,000 |
| VAT 16% accrued | 1210 | 3130 | 148,480 |
| Cost of goods written off | 7010 | 1330 | 610,000 |
This immutability is ensured by the prohibition date: the VAT amount of 148,480 ₸ that was included in the declaration will remain exactly the same.
And the chief accountant opens the same document and — if a correction is indeed needed — edits it, because for him the prohibition date is blank. He will not receive any error.
Note: the object "Data Change Prohibition Dates" does not create entries. The entries in the table are the movements of the sales that it protects from being changed.
5. Types of operations (configuration options)
There is no separate "Type of Operation" like in documents here. The roles of types are played by the methods of specifying the date:
- General date — a single prohibition for the entire database.
- By sections — separate dates for sections: "Accounting", "Payroll", "Bank and Cash", "Tax Accounting", etc.
- By sections and objects — dates detailed down to the organization (relevant for multi-entity accounting).
Plus two independent mechanisms nearby:
- Data Change Prohibition Date (manual input) — what we configure.
- Data Upload Prohibition Date — restriction during synchronization/exchange.
6. What is formed when setting
Honestly: the object does not create entries, movements in accounting registers, electronic invoices (ESF), or tax returns. ESF (through the ESF Information System) and tax returns are formed by sales/purchase documents, not by the prohibition setting.
What actually happens when recording:
- The date value is saved in service settings (information register with prohibition dates).
- The mechanism begins to check each attempt to record/conduct/delete a document: if the document date ≤ prohibition dates and the user has no exceptions — the operation is rejected with an error.
- The check works both during group re-conducting and when closing the month: the closed period simply will not be re-conducted.
7. Printed forms
The prohibition date settings do not have their own printed forms — there is nothing to print here. This is a service mechanism. Indirectly, the result of its work is visible where you try to change a closed document (a window pops up with a prohibition message).
8. Common errors
1. "Data Change Prohibition Date: 30.06.2026. Data change not performed." This is not a failure, but a trigger of protection. If a correction is indeed needed — temporarily shift the prohibition date forward, make the correction, then return the date back. Or include yourself in exceptions with a blank date.
2. Set a date, but documents are still being edited. The general checkbox "Data Change Prohibition Dates" in "User and Rights Settings" is not checked. While it is unchecked, the rows with dates do not work.
3. Blocked your current work. You set the "General date" too close to today's date — and fresh documents are not being conducted. Check: the prohibition is effective up to and including the date. Move the date back.
4. "No rights to change prohibition dates." Only a user with administrator rights can change the setting. Contact the database administrator or obtain the role.
5. Forgot about the relative date.
You set a specific 31.12.2025 and a year later are surprised that all of 2026 is "open". Use "End of last month/quarter" — the date shifts automatically.
6. Prohibition interferes with synchronization. If data is not being uploaded from another database — look not at this setting, but at the "Data Upload Prohibition Date". These are different mechanisms.
9. FAQ
Does this object create entries or electronic invoices (ESF)? No. This is a service setting for period protection. Entries, ESF, and tax returns are created by sales and purchase documents, and the prohibition date simply prevents them from being changed retroactively.
Does the prohibition date include the day itself or not? It includes. With a prohibition date of 30.06.2026, a document dated 30.06.2026 is already blocked, while one dated 01.07.2026 is available.
How to allow editing only for yourself and prohibit everyone else? Choose the method "By sections", set the date "For all users", and for your user (chief accountant) add a line with a blank or earlier date.
Can different dates be set for accounting and payroll? Yes. Choose the method "By sections" and specify your date in each section — for example, "Accounting" on 30.06.2026, while "Payroll" remains open.
How does the data change prohibition differ from the data upload prohibition? The data change prohibition restricts manual input and editing of documents. The data upload prohibition restricts only the reception of data during synchronization between databases.
Is it necessary to restart the program after setting the date? No, the prohibition takes effect immediately after clicking "Save and Close".
Does the prohibition date interfere with closing the month? On the contrary, it helps: the closed and protected period will not be accidentally re-conducted. If you need to re-close a closed month, first shift the prohibition date forward.
What to choose for multiple organizations in one database? The method "By sections and objects" — it allows you to set dates separately for each organization, to close the period for one legal entity without affecting another.
Who can change the prohibition date? Only a user with administrator rights in the database. A regular accountant does not have access to change the setting.
How to quickly remove the prohibition for urgent correction? Open the setting, clear the date (or shift it to the required day), make the correction, then return the prohibition date back.
10. Related documents
- Based on what it is configured: after closing the month ("Operations" → "Month Closing") and submitting regulated reports — VAT declaration (300.00), corporate income tax, reports on individual income tax/social contributions. The logic is simple: submitted the period — closed it with the prohibition date.
- What it protects: documents of sales and purchases. ```