Skip to main content
Solved

Subaccount Mechanism Similar to NetSuite in Acumatica?

  • February 9, 2025
  • 3 replies
  • 41 views
L
Freshman I

Hi everyone,

I’d like to ask if Acumatica has a subaccount mechanism similar to other ERP software (as shown in the attached image from NetSuite).

In this structure, users are not allowed to post transactions directly to the parent account, and reports querying the parent account will automatically sum the data from its subaccounts.

Does Acumatica support this functionality, and if so, how can it be configured?

Thanks in advance!

Best answer by aaghaei

Hello ​@lacpham63 

  • Acumatica supports Account and Subaccount. You can use only Account (if Subaccount is not enabled in the Features) or use them in conjunction (Account + Subaccount). If Subaccount enabled in Features, it will become mandatory.
  • Behind the scene transactions are always posted to the combination of Account and Subaccount. If Subaccount is not enabled in the Features, Acumatica automatically uses the default subaccount shipped with the system automatically. As a result, in fact your GL Accounts are aggregation of the Subaccounts.
  • You can assign the Accounts to the Modules and block it from direct posting from GL. This will ensure GL Accounts always agree to Subledgers and accordingly to Subaccounts.
  • Accounts and Subaccounts do not have parent-child relationship. In other word any account can be combined with any subaccount. So it is on user or system config to ensure the proper mix of Accounts and Subaccounts are used.

Side note: Last bullet in my opinion is a blessing and curse. It provides flexibility and also opens door for errors. If I was the one who designs the system this is what I whould do. I would keep the existing logic but would add a layer of validation as follows.

  • I would add an option to create categories for the Subaccounts (i.e. Bank Account, Cost Center, Department, ...)
  • Whould link the Subaccounts to one of these categories
  • Would allow the Accounts to be linked to one or more Subaccount Category.

Whith this structure, system would keep the flexibility and prevent using of invalid combination.

View original
Did this topic help you find an answer to your question?

3 replies

aaghaei
Captain II
Forum|alt.badge.img+10
  • aaghaei
  • Captain II
  • 1204 replies
  • Answer
  • February 9, 2025

Hello ​@lacpham63 

  • Acumatica supports Account and Subaccount. You can use only Account (if Subaccount is not enabled in the Features) or use them in conjunction (Account + Subaccount). If Subaccount enabled in Features, it will become mandatory.
  • Behind the scene transactions are always posted to the combination of Account and Subaccount. If Subaccount is not enabled in the Features, Acumatica automatically uses the default subaccount shipped with the system automatically. As a result, in fact your GL Accounts are aggregation of the Subaccounts.
  • You can assign the Accounts to the Modules and block it from direct posting from GL. This will ensure GL Accounts always agree to Subledgers and accordingly to Subaccounts.
  • Accounts and Subaccounts do not have parent-child relationship. In other word any account can be combined with any subaccount. So it is on user or system config to ensure the proper mix of Accounts and Subaccounts are used.

Side note: Last bullet in my opinion is a blessing and curse. It provides flexibility and also opens door for errors. If I was the one who designs the system this is what I whould do. I would keep the existing logic but would add a layer of validation as follows.

  • I would add an option to create categories for the Subaccounts (i.e. Bank Account, Cost Center, Department, ...)
  • Whould link the Subaccounts to one of these categories
  • Would allow the Accounts to be linked to one or more Subaccount Category.

Whith this structure, system would keep the flexibility and prevent using of invalid combination.

Reza Aghaei CPA, M. Acc. & Acumatica Customization - If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
Chris Hackett
L
2 people like this
  • Chris Hackett
    Chris Hackett
  • L
    lacpham63
V
Acumatica Employee
Forum|alt.badge.img+12
  • vkumar
  • Acumatica Support Team
  • 871 replies
  • February 10, 2025

Hi ​@lacpham63 

The description of Parent account mentioned in above case is somewhat similar to Account class in Acumatica. Where one can group the actual GL accounts used on transactions for reporting purpose. One cannot post anything directly to an Account class. 

To suggest further, can you give an example of actual Parent account and sub account names, for what kind of transaction recording are they used for ? 

Regards,

VijayKumarU
Chris Hackett
L
2 people like this
  • Chris Hackett
    Chris Hackett
  • L
    lacpham63
L
Freshman I
  • lacpham63
  • Author
  • Freshman I
  • 1 reply
  • March 4, 2025
aaghaei wrote:

Hello ​@lacpham63 

  • Acumatica supports Account and Subaccount. You can use only Account (if Subaccount is not enabled in the Features) or use them in conjunction (Account + Subaccount). If Subaccount enabled in Features, it will become mandatory.
  • Behind the scene transactions are always posted to the combination of Account and Subaccount. If Subaccount is not enabled in the Features, Acumatica automatically uses the default subaccount shipped with the system automatically. As a result, in fact your GL Accounts are aggregation of the Subaccounts.
  • You can assign the Accounts to the Modules and block it from direct posting from GL. This will ensure GL Accounts always agree to Subledgers and accordingly to Subaccounts.
  • Accounts and Subaccounts do not have parent-child relationship. In other word any account can be combined with any subaccount. So it is on user or system config to ensure the proper mix of Accounts and Subaccounts are used.

Side note: Last bullet in my opinion is a blessing and curse. It provides flexibility and also opens door for errors. If I was the one who designs the system this is what I whould do. I would keep the existing logic but would add a layer of validation as follows.

  • I would add an option to create categories for the Subaccounts (i.e. Bank Account, Cost Center, Department, ...)
  • Whould link the Subaccounts to one of these categories
  • Would allow the Accounts to be linked to one or more Subaccount Category.

Whith this structure, system would keep the flexibility and prevent using of invalid combination.

Thanks, we got that!

Chris Hackett
1 person likes this
  • Chris Hackett
    Chris Hackett

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2024  Acumatica, Inc. All rights reserved