Let’s see how to create a Custom Extension for Data Import Tool in AccountingSuite.
In the world of enterprise resource planning and accounting automation, AccountingSuite offers a powerful built-in Data Import Tool (DIT) that allows users to import data from common file formats like CSV and Excel. However, this tool comes with a key limitation: it expects the file structure to strictly match the predefined data layout and field name of AccountingSuite.
But what happens when your client, supplier, or internal department sends data in their own unique format? Or when a simple data upload needs to trigger complex business logic – like creating new Items, generating Lots with custom properties, or populating custom fields? In such cases, the standard import tool falls short.
This is where the power of custom extensions comes into play.

Please note: Before you start working on an extension, it is highly recommended to watch these videos and read articles.
- AccountingSuite customization – About ACS customization in general
- 1C:Enterprise. First Step (video guides) – Getting started guide series
- 1C Development Basics. Junior Course (video guides) – More detailed course about development
Especially the “1C:Enterprise. First Step ” and “Junior Course”, as creating your own extension will require writing code and using the Configurator.
When Do You Need a Custom Extension? #
You should consider developing a custom extension if:
- The File Format is Non-Standard
Your data source uses a custom column layout, different delimiters, or special formatting that AccountingSuite does not recognize. - The Import Requires Additional Processing
You’re not just uploading data – you’re executing a multi-step routine. For example:- Creating new catalogue entries (items, clients, lots)
- Setting custom attributes or lot properties
- Validating, transforming, or enriching data during import
- The Standard DIT is Insufficient
When built-in mapping and validation options cannot meet your business logic or integration requirements.
How It Works: A Step-by-Step Overview #
The provided tutorial outlines a practical example of an extension designed to import data from a CSV file into a document’s tabular section.
Download ExampleImportDataTransaction.zip to use as an example for your code.
Creating an extension to import data from a file
Here’s a high-level breakdown of the process:
1. Adding Interface Elements via Code
- Use the
OnCreateAtServerprocedure in the document form with theAfterpreprocessor directive. - Create a new command and a corresponding button in the interface.
- Link the button to the import command.
2. Reading the CSV File
- The user selects a file, which is then read and passed as a string to a processing routine.
- Important: The parser handles commas inside quotation marks correctly, treating them as part of the value rather than as separators.
3. Processing the Data
- The logic resides in a common module within the extension.
- The file content is converted into a structured array for further manipulation.
4. Populating the Document
- In the
ComposeResultprocedure, the system iterates through the data array and fills the document’s table part. - Custom business logic can be embedded here—for instance, calling
GetProductsMapto optimize item lookup and lot creation.
5. Ensuring Data Integrity
- Remember to trigger
OnChangeevents such asProductOnChangeandQuantityOnChangeso that related fields (UoM, price, taxes, totals, etc.) are updated automatically.
6. Displaying Import Results
- Providing clear feedback is critical, especially when:
- The file contains a large number of rows.
- Some data fields cannot be mapped or processed.
- Unexpected errors occur during import.
Getting Started with Development #
Creating an extension requires familiarity with the 1C:Enterprise platform, including:
- Writing code in the built-in language
- Working with the Configurator
- Understanding common modules, forms, and events
If your team lacks in-house development expertise, it is advisable to engage a certified 1C partner or order the Customization to implement the solution reliably and in line with best practices.
Conclusion #
While AccountingSuite’s standard Data Import Tool is useful for straightforward uploads, real-world integration scenarios often demand flexibility and advanced processing. By developing a custom extension, you can tailor the import process to match unique file formats, automate complex data transformations, and seamlessly embed business logic – all while keeping the user experience intuitive and efficient.
Whether you choose to build it yourself or collaborate with a partner, extensions unlock a new level of adaptability and power in your AccountingSuite.