Import (or build) your reporting model
The final solution
Managing individual companies mapping in a multi-company scenario
Use Case : Multi-organization account normalization
While accounts are important, the AHA tool also can map all of the companies in a QQUBE file so you can group them in ways that help with your companies rollup
The customer in this case had not started using our favorite tool - Power BI and wanted an Excel based solution. The mapping of the accounts was easy enough but how would they be able to use the mapping with QQUBE. We built a Power Pivot solution for them using QQUBE's template for Financial statements and simply adding in the mapping files but we all found that solution slow. We settled on a faster solution that stacks all the tables need in Power Query to present a single view to Excel.
When you start a new model, you are prompted for what company you want to map (see image inset left) and what reporting model (aka Rollup Definition) you will use.
Once you have mapped your accounts and saved the aha file, we ALSO export out the mapping into a CSV file that represents the mapping for JUST that company. Users can share these files into a single directory or, since they are just a text file, they can be copied as needed
A client approached us with a simple problem, they had been acquiring organizations and the consolidated financial reporting has become a nightmare. While they wanted the ability to use QQUBE for consolidated reporting and they had a standard chart of accounts, account names used in the subs frequently did not match across organizations perfectly and so they needed to be able to group accounts based to their standard. Because they had a csv with the chart of accounts, this is when we added the ability to import a reporting model to make onboarding them faster.
Since then, many other companies have had the ability to import reporting model in order to be able to map all of the subsidiary companies to the standard.
The first problem in building consolidated financial reports is trying to get to a common standard for the char of accounts. Of course you can start with the basic types, cash, current assets etc but being able to group the next level is harder. For example, grouping all the cash accounts by something like operating account vs payroll account vs reserve accounts without updating the bank names is a where the power of aha! shines.
Example of the import file and the resulting reporting model
It is worth repeating, aha is for more than just accounts