Tag Archive: Compound Report Macros


Though an increasing number of firms pride themselves on their ability to fire out reports within the first week of the quarter, it seems that most firms still produce and mail out their statements in the second or third week.  Yes, I said “mail out.”  Even firms that have invested in the ability to post their reports to a web portal still mail most of their reports out due to low adoption rates by their clients.   Investment advisors that don’t get their reports out within the first three weeks of quarter end are operating outside of the norm.

There are 13 weeks in a quarter.  Given that most firms send quarter end reports during week two, operations folks aren’t thinking about doing an upgrade in week three.  They’re busy catching up on what they didn’t do in weeks one and two, while they were managing the client reporting process.  That leaves ten possible weeks for a system upgrade.  Weeks four through six are ideal, giving your firm adequate time to test your systems and apply fixes as necessary.

Weeks seven to 13 become increasingly unappealing; lucky number 13 is the worst possible time to perform a system upgrade.  Most people in the investment business know this.  With 25 years of experience installing Advent products, I consider the time approaching quarter end an obvious no-fly zone for in-place system upgrades, no matter how competent you are.  I was stunned yesterday when I received a call from a customer related to a system upgrade.

Apparently, someone working with Advent talked them into upgrading to Axys 3.8.5 last week, telling them they wouldn’t have any problems with the upgrade.  When you are unfamiliar with a client site, broad-sweeping statements like this are all too easy to make.  After the upgrade, their billing reports didn’t work.  The representative doing the upgrade was able to fix the standard billing report, but could not fix our compound billing report, which is used to generate client invoices.

Billing Report (created via compound reporting macros and replang)

Due to this issue, our customer’s billing process was on hold this week until the issue was resolved.  We received their call yesterday afternoon, and called them back before close of business, but didn’t hear from them until today.  We promptly connected to their system, reviewed their issue and resolved it; however, this incident certainly had the potential to end in technical tragedy.

I recently blogged on the different versions of Axys 3.x we see in use working with Advent clients.  The blog indicated that Axys 3.8.5 is a solid product release and should be an easy upgrade for users, but also underscored the need for users with customizations to anticipate difficulties.

Advent typically shows good sense in planning.  For example, in Axys to APX conversions, systems are run in parallel for months.  I am disappointed to hear about this incident, which I can only hope is an oversight, not the modus operandi for Axys upgrades.

Some people feel the need to push ahead no matter how close they are to quarter end.  Perhaps they make a bit more progress in doing so. Still the question for me is what benefit this upgrade had last week versus a couple weeks from now when quarter end reports have been produced.  If there is a benefit that offsets the risk, I am all for it.  In this case, I just don’t see it – not for my client.

About the Author:
Kevin Shea is President of InfoSystems Integrated, Inc. (ISI); ISI provides a wide variety of outsourced IT solutions to investment advisors nationwide. For details, please visit isitc.com or contact Kevin Shea via phone at 617-720-3400 x202 or e-mail at kshea@isitc.com.

In an earlier blog I emphasized the importance of mainstream client reporting.  As investment professionals once again turn to the dreaded task of busily cranking out their quarterly reports, it is relevant to share the process we have established to help many of them transition from tired, stale reports to a new generation of client reports. 

In this article, I’ll take you through our process for overhauling client reporting drawing upon specific references to a recent project. Whether you opt to utilize a third-party service provider like us, request Report Writing services from Advent, or produce your next generation client reports internally, you should find the following information useful.  Those that want to implement new reports for Q3 or Q4 of 2011 need to start the process now.

Our Process for Improving Client Reporting

Our fundamental approach addresses the most difficult reporting issues first, identifying any show-stopping problems as early in the process as possible.  We are able to create reports using a number of techniques.  If one way doesn’t work, we can always fall back on another, but our goal is to select the right method from the get-go.

1. Review

In the review stage, advisors need to appraise their current client reporting packages with a critical eye in order to identify what is good and bad about them.  In a nutshell, investors must preserve what is highly valued by clients and remove what is superfluous. The ultimate goal should be to create concise, comprehensive reports that are easily understood, allowing clients to view as little or as much detail as they desire.  Many advisors want to create visually crisp and professional reporting packages.  We understand the importance of this;  however, in the area of client reporting, meaningful content should trump form.

Though we are available and qualified to review client reports and make recommendations for new ones, most firms prefer to do this internally. 

2. Mock-up

A new report always starts with an idea.  Oftentimes, this is shown with a mock-up expressing the look of the desired end product.  In some cases, our customers produce mockups in Excel, but others cut and paste pictures together, or simply sketch them freehand.  Any of these options are fine.  As they say, a picture says a thousand words:  the more detailed the pictures, the less you will have to explain to those writing the reports. 

Most clients have a strong preference as to whether reports appear in landscape or portrait. This aspect of your reports will be more expensive to change as you progress further into the project.  We understand that this decision may have more to do with aesthetic presentation issues, but some report layouts simply require more vertical space or horizontal space than others.  If you are dead-set on a certain orientation, you may need to be more flexible about report content.

Over the years, we have created a wide variety of quarterly reporting packages for clients. Some samples of our work that may help you with your mockup appear on our website under the menu titled “Custom Reports for Axys/APX.”  They fall into three categories:

1 – samples of reports produced by extracting data from Axys/APX and generating reports through traditional report writers like Crystal Reports and SSRS

2 – samples generated directly from Axys/APX through the use of compound report macros

3 – older samples of reports that were generated through a variety of methods

While browsing these above samples, click on any report to view it in larger size.

After viewing all of our online samples and PDF documents, our client produced the following mock-ups for us:

3. Draft

The draft process, as we define it, is one where the reports’ framework is established in the chosen environment.  Roughing out the reports helps determine their feasibility. In the attached example, we started by spending a day onsite, drafting the four account summary-type reports that were requested.   We used a combination of REPLANG, Report Writer Pro, and compound report macros. During this phase of the process, we are not overly concerned about individual details. Instead, we focus on the big picture. Is it possible to create the reports requested? What type of challenges will we face? What tools will be required? What resources, including time, will be required?

There are two possible outcomes to this stage:

  • Validation that the reports can be produced in the selected environment, as well as a better understanding of what they will look like and how much time they will take
  • A recommendation for another methodology, such as SSRS or Crystal Reports, based on the difficulties encountered in attempts to draft the basic report framework

After drafting the four requested summary reports, we were in a better position to estimate the amount of time necessary for development, knew what features would be difficult to implement, and were confident that we could deliver the reports on time.  Our client was also included in the process.  As we drafted each report, we sought their feedback to determine whether things were taking shape as intended.

4. Design

A significant amount of time needs to be spent in the design phase, selecting fonts, styles, colors, chart details, and other elements of presentation related to the reports.   Our client preferred to use the traditional Times New Roman font, but this font choice is one of the reasons most Axys and APX reports look so similar. We selected title bars rather than title boxes to give added flexibility regarding the placement and size of report elements.  Colors are very important. In the past, I have seen clients struggle to pick a palette of colors for charts and graphs. Our client picked vibrant colors that complemented their logo. If you are not already familiar with it, Adobe has a very useful and free resource that you can use to select a color scheme for your reports:

 http://kuler.adobe.com

As a general rule, one should complete design of the master page or default style for all reports before moving on to the next phase.  Report writers and developers are not necessarily graphic designers.  You can save your staff or vendor a lot of grief by having your color schemes selected and logos produced by professional designers.  In particular, your designer should produce images of the proper size, format and quality required.

5. Build & Test

We minimize formatting and style changes by beginning work in this phase only when a client has committed to a design specification.  Ideally, we wouldn’t make any changes to design once we have begun the build phase, but some customers change their minds between the design and build phases.  We also occasionally run into difficulties with pieces of the implementation process or come up with a better way to design something in the process of its implementation.

No matter how a report is created, the formatting of the first in a series of client reports to match the design layout is the most difficult.  However, once the initial report is completed, the rest of the reports come together much faster. The bulk of the time on your project will likely be spent on implementation.  This time depends on the number and complexity of reports you plan to produce, and the resources available.  It will likely take days, if not weeks.

In initial testing, we run reports for a small control group that represents the client’s various types of accounts. We also do a number of report runs for the full group of reports that will be run at quarter end. We find that doing full-scale tests is the best way to identify exceptions and deal with them proactively. As we find issues with individual reports, we apply fixes to address them, and must test again to validate the fixes.

In the example below, our client did a great job illustrating exactly what they wanted and let us focus on producing the report.

Account Summary Mock-up

The final report that we created based on our client’s mock-up shown above follows:

To see other samples of the final reports click here.

It took roughly 30 days to produce the final versions of our customer’s four account summary reports.  The customer was very engaged in the process and highly motivated, facilitating progress by providing quick responses to our questions.   Similar projects take 4-6 weeks, but could take significantly less time if you are working from established reports that just need modification.  You may remember that our initial draft took a day; we spent the rest of the time working on the more difficult aspects of the project.  Our summary reports brought data that needed verification into focus.  Based on exception testing and other issues, we made our final modifications to the reports’ appearance.

The project referenced in this article included new custom reports, quarterly packaging automation, integration of new custom reports, and conversion of legacy packaging to our new report packaging environment.  The project’s total cost was about 20k, nearly double what it would have been with our preexisting custom reports, but the only recurring cost is maintenance.  Many of today’s alternatives feature a sizable implementation cost and significant monthly fees.

Improving your client reporting is one of the most important things you can do to communicate more effectively.  Your next generation of quarterly statements should make it clear to your clients that you are investing in a process that directly benefits them.  If you do it right, you are bound to receive positive feedback from your clients once they have your new reports in hand.

There is no time like the present to start working on your next generation of client reports.

About the Author:
Kevin Shea is President of InfoSystems Integrated, Inc. (ISI); ISI provides a wide variety of outsourced IT solutions to investment advisors nationwide. For details, please visit isitc.com or contact Kevin Shea via phone at 617-720-3400 x202 or e-mail at kshea@isitc.com.

Whether you are an investment professional or an individual investor, you want to be on the respective sending or receiving end of meaningful statements that effectively convey what has transpired on a quarterly basis. These reports may represent clients and investors’ only communication of the quarter. As such, the importance of mainstream client reports cannot be underestimated. Advisors do not necessarily need a state-of-the-art reporting package, but they also cannot afford to have their reports look dated.

A couple of years ago, I was approached by an investment firm looking to overhaul their client statements. The impetus was the departure of a client, who was “nice” enough to drop off a sample of their new investment advisor’s reporting package. I was presented with the package and asked how much it would cost to do something like this for them.

I went through the lengthy presentation-quality package in detail. It was clearly something that was produced through a custom report-writing engine or a third-party, and not a standard report package by any means. The reports included comprehensive summaries of holdings, allocation, fixed income, equity, and performance. All of the reports contained detailed graphs and charts.

We came up with a number – roughly 50k – and we were not surprised when the prospective client did a double take and put the project out for other bids. Our bid was for a system that worked with the underlying Advent data, but stood on its own. In order to produce the high-quality output they wanted, we needed to get the data out of Axys and into a format where we would be able to use report-writing tools like Crystal Reports and SQL Server Reporting Services (SSRS). That would enable us to create reports of the same caliber. We had done it successfully for other clients and knew what was required.

However, our prospective client made some internal concessions on the presentation-quality aspect of the reports they wanted versus that original package, and eventually agreed to have a less expensive, but well-known competitor do the work as custom compound reports. Shortly after the job began, they started hearing a two letter word few advisors like — NO. It was the answer to whether they could have certain reports in landscape or portrait. And it was the answer to whether certain report components could appear on the same page.

With that experience in mind, the client called us back and asked us if we could do the job using compound reports. We agreed and said YES to all of their requests. We delivered their new reporting package, which consisted of the same types of portfolio summaries they had originally shown us. The reports are generated through the use of compound Axys reports and assembled via Encore, our PDF report packaging application.

The client reports that you send out every quarter are a representation of who your firm is and what you do. Good quarterly reports are an opportunity for your firm to maintain or improve your clients’ opinion of your service. Conversely, substandard quarterly reports are a liability that speaks to your clients every quarter. What do your quarterly reports say about your firm?

About the Author:
Kevin Shea is President of InfoSystems Integrated, Inc. (ISI); ISI provides a wide variety of outsourced IT solutions to investment advisors nationwide. For more information, please visit isitc.com , contact Kevin Shea via phone at 617-720-3400 x202 or e-mail at kshea@isitc.com.