Example of a subaccount definition

Consider an example that is explored in other articles in this section. North Serpent Company, with stores in the mountainous areas of California and Nevada, sells skis and snowboards and offers rental services. Each sale transaction of a ski or a snowboard is recorded to sales account 40000, but later, at the period closing, management would like to know the total sales on skis in Nevada store and the total sales on snowboards in California store, as well as the total rental of snowboards in California store and the total rental of skis in Nevada store. Thus, we can split the sales account into eight more specific accounts, for example, as shown below:

  • 40100: Ski sales in the Nevada store
  • 40200: Snowboard sales in the Nevada store
  • 40300: Ski rentals in the Nevada store
  • 40400: Snowboard rentals in the Nevada store
  • 40500: Ski sales in the California store
  • 40600: Snowboard sales in the California store
  • 40700: Ski rentals in the California store
  • 40800: Snowboard rentals in the California store

To enter a transaction, a user has to remember all the accounts, but it is easy to mistype the account. The following section explores some ways Visma Net makes this process easier and less error-prone.

Parent topic:
Manage subaccounts - overview

Related concepts
About account IDs
Overview of budgets

Related reference
Chart of accounts (GL202500)
Subaccounts (GL203000)Segment keys (CS202000)