Three sets of Midas data


Last Close of Business

Stored in SQL Server, and also stored in Qlikview for superfast load times, for example two million postings in a few seconds are possible.

Historic Data

Files are stored by date to allow historic reporting or data investigation. History can also be built retrospectively from saved databases. You can store 1,000 days of transactions and accounts, or more, in the SQL Server database.

Intraday Processing

For selected files such as transactions, cashflows and swift messages. Intraday processing can be run on-request or refreshed automatically.


Features

SQL Server repository

We use an SQL Server as the repository for your banking data, such as Midas. On this server we store approximately 80 of your most important Midas files, and more can easily be added. With our streamlined processing you get the benefits of a data warehouse without the overheads.

Automatic document production

Qlikview publisher will automatically produce documents as part of post Close Of Business processing and distribute these documents to users.

Ad-hoc documents

These can easily be created based on existing documents or built from scratch.

Transformation of Midas data

Dates and amounts preformatted. User friendly field names and file names - full description not cryptic short name. Every Midas field from the selected files is available. More files, including in-house ones, can easily be added. UDFs (user defined fields) are available and easily linked. Live or historic data can be selected. Postings and balances have Base, Head Office and local currency equivalents on hand. Tables easily joined in Qlikview e.g. loans to facilities.

Reconciliation with Midas

Qlikview reports are provided to reconcile record count and # total of the Midas data, file by file, with the Qlikview database to prove the accuracy of the data.

Compatibility

Works with different Midas releases including Fusion.