1. Identification of the Object
| Parameter | Value |
|---|---|
| Object Type | Report |
| Name | TaxAccountingRegisterForAcquisition |
| Full Path | Report.TaxAccountingRegisterForAcquisition |
| Alias | Tax accounting register for acquisition |
| Configuration | Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2) |
| Formation Mechanism | Data composition system (DCS) |
| Navigation Link | e1cib/list/Report.TaxAccountingRegisterForAcquisition |
Purpose. The report generates a tax register for accounting acquired goods, works, and services in the Republic of Kazakhstan in accordance with the requirements of the Tax Code of the RK. It is used by accountants and tax specialists for preparing VAT and CIT reports, controlling the accuracy of incoming operations (receipt of goods, works, services), reconciling data with electronic invoices (ESF) and accompanying documents (SNT). It is generated periodically (monthly, quarterly, annually) depending on the organization's tax period. It supports standard and custom presentation forms with configurable grouping, selection, and breakdown to primary documents.
Where to find in 1C: section "Taxes" (subsystem "Accounting for Kazakhstan") → "Tax accounting register for acquisition". Direct transition — via the navigation link above.
2. Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| StartPeriod | xs:dateTime |
DontCheck | Start date of the formation period. Lower boundary of the data selection interval for tax accounting. |
| EndPeriod | xs:dateTime |
DontCheck | End date of the period. Upper boundary of the selection interval. |
| Frequency | xs:decimal |
DontCheck | Frequency (monthly, quarterly, annually). Manages the automatic calculation of period boundaries when selecting standard intervals. |
| Taxpayer | CatalogRef.Organizations |
ShowError | The organization for which the register is generated. Mandatory attribute: defines the context of all data and affects the choice of footer template (legal entity/sole proprietor). |
| ReportType | xs:string |
DontCheck | Type of report (standard/custom). Affects the display of grouping header layouts and composition mode. |
| ListOfOrganizationsRepresentation | xs:string |
DontCheck | String representation of selected organizations for the header/filters during multi-selection. |
| ListOfDepartmentsRepresentation | xs:string |
DontCheck | String representation of selected departments for report settings when filtering by organizational structure. |
| PlacementOfAdditionalFields | xs:decimal |
DontCheck | Placement of additional fields in the layout (separately / together with the main ones). Manages the visual representation of columns. |
| BreakdownMode | xs:boolean |
DontCheck | Indicator of breakdown mode. When enabled, standard grouping headers are hidden, and a context menu for navigation to primary documents is activated. |
2.2 Table Parts
Grouping
Manages the hierarchy of data groupings in the report (by counterparties, contracts, nomenclature, accounts, etc.).
| Name | Type | Purpose |
|---|---|---|
| Usage | xs:boolean |
Flag of the grouping row's activity — whether this grouping is applied during formation. |
| Field | xs:string |
Identifier of the grouping field ("Counterparty", "Contract", "Nomenclature", etc.). Used by the data composer. |
In reports of this type (DCS), alongside the table part "Grouping", standard service sets of DCS settings are also typical: selection, sorting, conditional formatting, and selected fields. They are stored in the structure of the composition settings, not in the attributes of the object.
3. Forms
| Form | Purpose |
|---|---|
| ReportForm (main) | Unified form for launching and outputting. Contains the result field (tabular document), settings panel (period, organization, frequency, report type), buttons "Generate", "Settings", "Breakdown". Provides interactive work with the composer. |
| SettingsForm (DCS settings form) | Editing the structure of groupings, selections, formatting, and selected fields. Opens from the main form. |
For reports in DCS, a custom form may be absent — then an auto-generated composition form is used. The presence of an explicit ReportForm in this configuration is due to the custom panel for period/taxpayer and the logic of selecting the footer template (legal entity/sole proprietor).
4. Key Procedures of Modules
Evidence with the source text of BSL modules is not attached, so below are typical report handlers in DCS for this type of object. Specific names and lines should be checked with the form module and the object module of the specific delivery.
Object Module / Manager Module:
OnResultComposition(ReportResult, BreakdownData, StandardProcessing)— overrides the standard composition: substitutes the header of the register, taxpayer attributes, selects the footer template (legal entity/sole proprietor) based on theTaxpayerattribute, adds headers and signatures.CalculateSelectionPeriod(Frequency, StartPeriod, EndPeriod)— calculates the boundaries of the interval based on the selected frequency (month/quarter/year).
Form Module:
OnCreationOnServer(Error, StandardProcessing)— initialization of default settings, setting the current organization and period.OnFrequencyChange/OnPeriodChange— recalculation ofStartPeriodandEndPeriod.TaxpayerOnChange— updates the data context and footer template.Generate(Command)— starts composition in the result field.ResultBreakdownProcessing(...)— processes the breakdown whenBreakdownMode = True: navigation to the primary document (receipt, ESF, SNT).
5. Data Sources and Accounting Registers (Accounts RK)
Important: this report — it is not processed and does not generate its own movements. It reads data from accounting registers and specialized tax accounting registers reflected in primary acquisition documents.
The report aggregates data on acquisition operations, which are reflected in receipt documents according to the standard chart of accounts of the RK:
| Operation | Debit | Credit |
|---|---|---|
| Receipt of goods (TMC) | 1330 "Goods" | 3310 "Short-term liabilities to suppliers and contractors" |
| Incoming VAT on acquisition | 1420 "VAT to be refunded" / offset VAT | 3310 |
| Accrual of VAT payable (upon sale) | — | 3130 "VAT payable" |
| Payment to supplier from current account | 3310 | 1030 "Cash in current bank accounts" |
The register is built on the data of incoming ESF (IS ESF) and SNT, matched with receipt documents. The VAT rate for calculating offset amounts is 16% (Kazakhstan, 2026).
Breakdown leads to primary documents: "Receipt of TMC and services", "Invoice (received)" / ESF, "Accompanying invoice for goods (SNT)".
6. Related Objects and Input on the Basis
The report is not an object for input on the basis and does not serve as a basis itself. It is related to the following objects:
- Documents: "Receipt of TMC and services", "Receipt of additional expenses", "Advance report", "Invoice (received)", ESF, SNT.
- Directories:
Organizations(attributeTaxpayer),Counterparties,Contracts,Nomenclature,DepartmentsOfOrganizations— fields of groupings and selections. - Registers: accounting register (Cost Accounting) and tax accounting accumulation registers for VAT/acquisition.
- Exchange: IS ESF (electronic invoices), SNT system (accompanying invoices) — sources for reconciliation.
7. Extension Points
- Configuration Extension (CFE): overriding handlers
OnResultCompositionandGeneratethrough &Instead/&Around for custom header, additional columns, or custom groupings. - DCS Settings: user report options (saved settings for groupings, selections, conditional formatting) without changing the configuration.
- Additional attributes of the organization: affect the choice of footer template (legal entity/sole proprietor) — extendable through the mechanism of additional information.
- External printed forms / layouts: substitution of footer and header layouts.
- Subscriptions to events / common modules of tax accounting: influence on generated data through overriding the filling of source registers.
Requires verification for specific delivery 3.0.74.2: the exact composition of VAT source registers and names of the object module procedures — depend on the version and should be checked with the configurator, as version changes may occur in this part of the configuration after updates to the legislation of the RK in 2026.
