In 2026, a number in 1C should be corrected in the object specified in the full message text: a document number in the document itself, a bank card number in the counterparty’s card record, and the serial number generation method in the settings of the relevant integration. The provisions on reviewing applications for the refund of excess VAT and preserving the terms of investment agreements and contracts do not establish rules for numbering objects in 1C (Articles 833, 837, 838, 839 of the Tax Code of the RK).
What a Number in 1C Means
There is no single attribute called “number in 1C.” A number relates to a specific infobase object. For example, a document may have an internal registration number, a bank card may have a card number, and a marked product may have a serial number.
Therefore, an accountant should not correct the first attribute they find containing the word “number.” First, determine:
- which configuration the issue occurred in;
- which document, directory, or transaction is open;
- whether the error appears when saving, posting, exchanging, or generating data;
- the full text displayed by the application;
- which value is shown instead of the “%1” placeholder, if it has been populated.
An internal document number and a product serial number serve different purposes. Changing the document number will not resolve an error in bank card details, while manually correcting the product’s series or number will not correct an incorrectly selected method for generating them.
If the issue concerns a standard document number, open the document itself and check the details in its header. Before changing a document that has already been saved or posted, assess whether it is used in printed forms, reports, data exchanges, and related transactions. The location of the field and whether it can be edited depend on the configuration, document form, user permissions, and infobase settings.
“Card Number Specified Incorrectly: %1” Error
If this message appears, check the object containing the counterparty’s bank card and the value displayed instead of “%1.” The error text alone is insufficient to reliably determine all the conditions of the software validation: they depend on the configuration, its release, and changes made to the infobase.
The accountant should check the bank card record of the relevant counterparty, not the document, payment, or bank account number. The practical procedure is as follows:
- Make a note of or save the full message text, including the value shown in place of “%1.”
- Open the bank card of the counterparty involved in the transaction.
- Check whether the card number has been entered and whether the attribute contains any extraneous characters, spaces, or an incorrectly entered value.
- Make sure that the correct card record is being edited, especially if several cards have been entered for the counterparty.
- Compare the value with the document or information on the basis of which the card was entered into the infobase.
- After making the correction, try saving the object again or repeat the transaction during which the message appeared.
Do not enter an arbitrary number merely to save the record successfully. If the value matches the source information but the message appears again, record the configuration name, release number, full error text, and sequence of actions. This information will allow the support specialist to determine which validation is being triggered in the infobase in use.
Serial Number Error During Integration with IS MPT
The message “Unknown serial number generation method: %1” indicates a parameter used to generate a serial number during integration with IS MPT. In this situation, you need to check not only the resulting serial number as a string of characters but also the selected method used to generate it.
The message alone does not indicate a universal path to the setting in the interface. It depends on the configuration, release, user permissions, and the components of the connected integration. The verification procedure may be as follows:
- record the full error text and the value shown instead of “%1”;
- determine during which IS MPT integration transaction the message appeared;
- check whether the serial number generation method parameter has been populated;
- check whether the selected value is available in the configuration version being used;
- make sure that, following an update or data migration, the parameter does not contain a value absent from the current list;
- repeat the transaction after correcting the setting;
- if the error recurs, provide the specialist with the configuration name, its release, the message text, and a description of the action that caused it.
Do not manually replace product serial numbers until the setting for their generation method has been checked. Bulk editing of numbers may alter related data without correcting the invalid integration parameter value. If the setting is unavailable to the user, it should be checked by an employee with the appropriate permissions or by the specialist supporting the infobase.
What the Accountant Should Do Before Contacting a Specialist
First, take a screenshot and record the sequence of actions preceding the message. Save the configuration name, release number, name of the affected object, and full error text. Passwords, full bank card numbers, and other sensitive information should be obscured in screenshots and correspondence.
Then check that the attribute in the source object has been populated correctly. If the issue concerns a card, open the bank card record of the relevant counterparty. If the application reports an issue with the serial number generation method, check the integration parameter rather than only the resulting number.
Before changing settings that affect data exchange or serial number generation, coordinate the action with the person responsible for supporting the infobase. Do not manually renumber documents, cards, or product series in bulk: first identify the specific object and attribute causing the error.
If the error appeared after an update, inform the specialist of the previous and current configuration releases and indicate whether the transaction was completed successfully before the update. If only one user encounters the issue, also record their role and available permissions without disclosing the account password.
Frequently Asked Questions
Where can I find a document number in 1C? — Open the relevant document and check its header. The location of the field depends on the configuration and document form, so there is no single path for all solutions and releases.
Can a document number be changed manually? — This depends on the infobase settings, document form, and user permissions. Before changing a document that has already been posted, check whether it is used in printed forms, data exchanges, and subsequent transactions.
What should I check if the message “Card Number Specified Incorrectly” appears? — Check the number in the bank card record of the relevant counterparty and compare it with the source information. If the error persists, provide the specialist with the full message text, configuration name, and release number.
Why does 1C not accept the serial number generation method? — The message indicates that the generation method value being used was not recognized when the transaction was performed. Check whether the parameter has been populated, whether the selected option exists in the current configuration, and whether the setting is available to the user.
Is there a single article of the Tax Code of the RK concerning numbers in 1C? — Articles 833, 837, 838, and 839 of the Tax Code of the RK regulate the transitional procedure for reviewing applications for the refund of excess VAT and preserving the terms of certain investment agreements and contracts. These provisions do not establish rules for correcting document, card, or product series numbers in 1C (Articles 833, 837, 838, 839 of the Tax Code of the RK).
Sources
- Tax Code of the Republic of Kazakhstan, Article 833 — transitional provisions on reviewing applications and claims for the refund of excess VAT.
- Tax Code of the Republic of Kazakhstan, Article 837 — preservation of the terms of an investment priority project and agreements on investment obligations.
- Tax Code of the Republic of Kazakhstan, Article 838 — preservation of the terms of an investment agreement concluded before 1 January 2026.
- Tax Code of the Republic of Kazakhstan, Article 839 — preservation of the VAT exemption for imports of raw materials and supplies under an investment contract.