​Reporting Model Definition - With the aha! model management tool, you can create any 4 level hierarchy and include an alternate mapping. You could use it to group together entities with common demographics or perhaps product groups. Once your model is complete, you'll be able to just drag and drop the source fields into your new model

Whether you are an outside consultant trying to help a create a group of categories for similar businesses so you can compare KPI's or an organization that is trying to model multiple company's financials into a common chart of accounts, you will appreciate the simplicity of being able to build or import a reporting model

The Alternate mapping field expands your reporting capabilities even more by allowing you to build subgroups within an alternate hierarchy.

Because we know some people will want to iterate over their models, we built in the ability to increment (or NOT increment) depending on how the model has been used. 

Start with one of our templates, import from CSV, or start from scratch.

Automatically map accounts

Multiple select to speed your mapping

Source Definition - By default, AHA users have the ability to connect directly to QQUBE Accounts, QQUBE Companies  and QuickBooks accounts but we are not limited to those lists!  When a user selects the file option, they have the ability to pull in a source definition file that allows them to specify a source data that can come from ANY ODBC database. That is the point of this screen, to define where the information will come from.

All a user has to do is use SQL to specify where specific fields will come from in the ODBC source and we save that definition for them so it can be used over and over again. Since it is a simple text field, users  can share the source with others as desired.

When a source is used, we save that definition in the aha file.

Multiple models - same financial data

A Colorful interface - After we built the base tool, we found that some users experienced challenges mapping because they had accounts with very similar names BUT very different account types.  Typically, we saw Cost of Goods sold and income accounts with names fashioned after a line of business. That was the inspiration for adding in colors to each list item.  Income accounts have green, COGS are in blue and as always, expenses make you see red. Beige shows up when we're just not sure. 

Map any ODBC Source to your model

Automap saves the day  - We built in a couple of different ways to get the program to do the mapping work. One way is to have consistent account numbers and then automap by account number. This is really good for when an industry creates an industry standard chart of accounts and many companies have already adopted it. Accounts that match-map.

Another way to map is by account category. The financial hierarchy model we ship is a great example of this. When the category matches the account is mapped. 

Color Coded Account Types

Select multiple accounts - CHECK - As users started working with AHA and becoming more accustomed to mapping items a pattern that emerged was the need to go thru the chart of accounts and select multiple accounts that might end up being mapped to a new category. Our multiple account sect feature addresses that need.

Once users decide to jump into multi-select mode,  they check off as many accounts as they want and then highlight the row in the reporting model they want those accounts to move to before selecting the finalize button to move them.

Some of the AHA Features most talked about are...