Ideas for Acumatica

Feedback processing: We do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive. Ideas and comments may not appear immediately. Some legitimate ideas are flagged as spam and will be added when we review the spam folders.
Content: This portal is for product ideas and feedback only. If you need customer service assistance, contact your Acumatica Support Partner, submit a support case, or get assistance from community resources: LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal.

Add another account class column to chart of accounts and be able to use in ARM

A second account class column would be extremely useful in the chart of accounts screen for use with ARM. An example would be when I am asked by a client how to produce two sets of reports, like GAAP vs Management reports.

Currently, I create on set of reports using account classes and the other by using account masking/ranges.

It would save a ton of time, not just building the reports but also training the client. The majority really like the account class option and ask why they cannot do a second set of reports using account class.

As for setting up the account classes, keep all of them in the same place so all account classes can be used in the original and second columns.

Thanks for reading.

  • Melanie
  • May 9 2018
  • Gathering Feedback
ARM
  • Attach files
  • Mike Lupro commented
    May 21, 2018 14:26

    My additional thought here was to use Acumatica Attributes.  I'me sure this is not-yet a viable option with ARM as G/L accounts do not have an Attributes option but my comment is intended to suggest to Acumatica that GL Attributes may be a way to implement your idea.

    Your idea of multiple account classes is excellent for the reasons stated.  I've seen (in Dynamic Budgets for Microsoft Dynamics GP) a setup where there are 10 user-defined account classes.  You have to manually enter them, but it's similar to your idea and it gives reporting staff TONS of flexibility.

    IMHO, a feature to enable the use of Attributes on GL Accounts in ARM reports would be a better way to go than adding a grid of x-number of alternate G/L account classes.