Applied solution development standards let developers focus their efforts on application business logic and avoid coding technological details, such as DBMS interaction, handling transaction locks, and the specifics of creating on-screen forms. To facilitate this approach, 1C:Enterprise applied solutions are developed based on a set of task-oriented objects. The set of objects is determined at the technological platform level.

Catalogs are intended for describing entities such as goods, counterparties, currencies, and warehouses. All of these entities have common qualities: internal object ID, hierarchy and grouping, embedded tables, and so on.

Constants are intended for storing data that is permanent or relatively permanent. For example, a constant can store a company name, or the full name of a manager or a chief accountant.

Enumerations describe lists of possible variable values. For example, an enumeration can store values that describe a customer status e.g., "bulk" and "retail".

Documents are intended for describing entities such as bills, invoices, and orders. These entities store the events that take place in the organization. They are time-stamped, contain embedded tables and they should be reflected in the accounting records.

The system supports real-time document posting, which streamlines concurrent user access.

The data storage feature is used to store multidimensional data on various parameters and their values. Examples of such values are currency exchange rates and competitor price lists as of a specific date. This data can be static or can change with time; in the latter case you have the option to store the change history.

The characteristics feature allows organizing the storage of object properties (catalogs, documents, and so on) that are not yet known at the time an application is developed. As a result, users can independently define new properties for items, such as color, size, dimensions, power rating, and others. 

This feature is intended for asset flow accounting, which includes cash, goods, materials, and so on. It automates warehouse accounting, mutual settlements, and planning. Accumulation registers store data on asset incomes and expenses, and the functionality of these objects includes retrieving balances for a specific date and time, calculating and cashing totals, and more.

The accounting feature allows you to build a model that implements the double-entry system. It provides tools for implementing multilevel charts of accounts with fixed or variable code length; multilevel and multidimensional analytical accounting; multiple charts of accounts; accounting in multiple companies; optional quantitative, value, and multicurrency accounting with a variety of breakdown options; and so on.

This feature can be used for implementing payroll calculation models. It provides tools for describing various calculation types (such as salary, alimony, bonuses, and penalties), specifying how calculation types affect other calculation types, and storing both intermediate data and calculation results. You can implement calculation of salary, individual income taxes, assignment of payroll calculation results to accounts, and so on.

The business processes feature can be used to create formal descriptions of typical task sequences within a company and generate tasks lists for the employees. For example, a sales process can include the following stages: creating an invoice and approving it, receiving cash payment, and shipping the goods. With different employees responsible for each of the stages, it is easy to determine the current stage and which employee should perform the next action.

External data sources are intended for retrieving data from external databases, including those that are not 1C:Enterprise-based.

This feature is used to generate new documents, catalogs, and other entities based on data stored in the infobase.

Filter criteria is used to filter infobase data (for example, to retrieve all the documents related to a specific vendor).

Bots are part of the Collaboration system and allow the user to communicate with the application solution through the familiar user interface of the Collaboration system.