QMan, QStar and QRep are no longer maintained,
programs have proven themselves over time and have been used in multiple
countries by large corporations. Demonstration versions are available. If you
are interested in purchasing the source code (c++ / mfc) to improve on your own
internal reporting needs, or to expand your current commercial applications,
please contact me.
The code is the result of years of work and
covers many complexities of reporting needs discovered by the users over time.
I can initially provide you with demonstration
versions of the programs, which are fully functional (although cannot be
reconfigured). The demonstration version of QMan, QRep and QStar are fully loaded with
prior, actual and budget data for 6 entities allowing you to evaluate the
applications in a working environment.
you would like to receive further information, the demo programs or the
documentation (in word format)
please email me at leov@QMatix.com
To find out more about each application, continue reading below.
QStar converts the results of a local general ledger into the format and
requirements of a corporate reporting package, taking into account division by
thousands, exchange rate conversion, rounding eliminations, and 'fine-tuning' -
ensuring that like balances in a reporting tie (and correspond with the ledger).
It eliminates those time
consuming hours needed to prepare a reporting package, avoids re-keying data, and ensures accuracy and faster reporting by allowing the user to concentrate on
the ledger and the closing of the books for the month. In addition QStar
analyses the ledger data, and tracks imbalances between reports down to
the individual ledger accounts.
Having a centrally maintained chart of accounts (containing reporting logic),
the local user need only maintain the mapping information on how to convert the
local ledger. This is primarily a one time process, with maintenance depending
on reporting or ledger changes. A Conversion table allows the user to map, with
the use of wildcards, the local ledger accounts to the reporting structure. An
allocation table allows the user to further adapt the ledger results to the
required reporting breakdown, allocating data by fixed amount, percentage, or
relative to the balances of other accounts. A Non Ledger table caters for all
data that is not reported from the ledger such as headcount. The reported
balances are automatically updated while the user modifies the tables,
allowing the user to 'zoom in', seeing exactly what accounts are reported from
At month end, the user need only load an
extract from the ledger and click 'perform', which prepares the reporting
package. If the
ledger structure allows, additional departmental spending data is automatically
extracted and the output files created, which may in turn be loaded into QMan.
Once the user has performed a reporting, full information is provided in a
series of interactive reports showing how the ledger data was mapped, what
allocations were performed, if rounding and fine-tuning
adjustments were applied etc. In addition an exception report shows all information the
reporting finds incorrect, illogical or unmapped.
QMan is the data repository, storing all aspects of company data including
financial results, budgets, forecasts, headcount etc. Each site has their own
QMan containing local data, and regional and head office sites containing
sub-entity and consolidated results. QMan stores the data and applies all
reporting and consolidation logic. Data stored in QMan may be viewed by multiple
users in Microsoft Excel via QRep, allowing users and management alike to view
the data the way they want to, without the need to learn something new (or
create their own copy of the data.)
QMan's logic is centrally maintained, with local users receiving updated
logic files, which are simply applied by selecting 'maintenance'. Each QMan may have multiple
applications. With each application having multiple data categories, its own
chart of accounts and its own consolidation hierarchy, with no imposed limits.
And each category having multiple periods.
This allows each company to package the data as they wish. e.g. a company may
have applications covering department spending and financial results. Each
application having data categories for current financial data, prior fiscal
years, budget and forecast data. Another may prefer to have individual
applications for financial and budget data.
Each application has its own logic files defining accounts, sub accounts, sub
totals, totals and calculation logic along with the entity consolidation
QMan accepts data from QStar (a local entity preparing their reporting), from
another QMan (a regional entity consolidating the reported results of a local
entity), or from Excel and QRep, allowing users to prepare budget and forecast
data, and then store it allowing others to share the data, ensuring all are
looking at the same and last results.
QRep hooks into Microsoft Excel, and establishes a high speed link to all
data within QMan via formulae. This allows multiple users to view and generate
reports and graphs accessing the same common data, with the tools they
Allows a report to be
created once and used for different entities / periods etc, by simply changing
the parameters. Formulae are available to retrieve financial results as well as
entity / period / application / account and sub account descriptions, allowing
for the creation of complex reports within minutes.
There are formulas that not only retrieve data from QMan, but write data
allowing for additional reporting data, budgets and forecasts to be easily
prepared and integrated into the core reporting package, including formulas for
QRep allows for the creation of complex analytical spreadsheets, eliminating
the usual tangle of links between workbooks, ensuring accuracy, portability,