What's new in the 2010 edition?

Transcription

1 What's new in the 2010 edition? Enhancements and Changes Table of Contents 2010a PROFITstar and PROFITability Page 3 PROFITstar Portfolio Page 7 PROFITstar Budget Manager Page 10 Fixes (in 2010a.199) Page Overview Page 11 PROFITstar and PROFITability Page 13 Fixes (in , , , , and prior) Page 24 Last content revision 01/05/2011 While PROFITstar has always allowed you to specify IRSA and Fair value rate shock ceilings or floors beyond the default 100, 200, and 300 scenarios, recent enhancements now give you the ability to define prepayment speeds, shocked quote values, and call behaviors to be used with any defined rate environment. Many of the topics listed below highlight these new enhancements, and the interactions between the new rate environment functionality and IRSA / Fair Value; reporting; and PROFITstar Portfolio. Rate Environments & Shock Scenarios: Rate Environments Setup Shocked Quote Values Prepayment Speeds and Rate Environments Call Source Rate Environments Sorting Rate Shocks and the Floating Flat Scenario

2 Sorting Upper and Lower Limits Selecting Scenarios for IRSA and Fair Value General: OTS Prepayment Coefficients are now Model Specific Change to the Rate Sensitivity Cash Flows Selection Allowing Servicing Costs to cause Negative Discount Rates Reporting: Rate Environments in the Prepayment Documentation Reports Quote Accounts Included in the Fair Value Documentation Reports ALM Risk Analysis Predefined Report Packet Change PROFITstar Portfolio: Synchronizing PROFITstar Rate Environments with PROFITstar Portfolio CMO Windows Determining whether a Security is Downloaded into PROFITstar When PROFITstar and PROFITstar Portfolio Versions do not Match Prepayment Field Names Changed Field Selection change in the Formula Assistant PROFITstar Budget Manager: Behavior of Account Balances when Subledger Accounts are Added Exported Organization Names 2010a Fixes: Missing Bloomberg Cash Flows Status Field Potentially Missing in Import Formats Copying Shocked Field Values when Advancing the Month Creating Callable Cash Flows while Downloading Cash Flows Page 2 of 54

3 PROFITstar and PROFITability ~Rate Environments & Shock Scenarios~ Rate Environments Setup This new Setup menu option can be used to create user-defined rate environments that correspond to additional data or information that you wish to model. This allows you to: Input prepayment speeds for the defined environments, on the Matr/Repr tab of Chart of Accounts Setup. The IRSA and Fair Value calculations have been extended to use all the supplied prepayment speeds. Expand the visible rate environments for Prepayment Rate Tables, and input prepayment speeds in these defined environments. Define call behavior for the defined environments, in the Call Source grid, on the Matr/Repr tab of Chart of Accounts Setup. Input quote values for the defined environments (when the Preferences Setup Enable Shocked Quote Values option is active). In PROFITstar Portfolio, import Cash Flows, Exercise Dates, Market Values, and Prepayment speeds for the defined environments. Generate reports and graphs that include information and results for all of your rate environments. Reports that display defined environment information include the Prepayment Documentation, Prepayment Customized by Month, and the Prepay Rate Tables reports. Note: The Rate Environments menu item is not available for PROFITstar Basic or PROFITstar Budget. Shocked Quote Values PROFITstar Only Selecting the Enable Shocked Quote Values option, on the Model Setup tab of Preferences Setup, now makes it possible to input and store quote values for each of the model's defined shock scenarios. To add shocked quote values to the History Balance Sheet grid, click the Data button and choose the new Shocked Quotes data item. When this is done, the layout switches to the Data Items as Columns Layout, by default, and shows each account that is set to Quote, along with each defined shock scenario. Page 3 of 54

4 Prepayment Speeds and Rate Environments Prepayment Speed data entry in Chart of Accounts Setup has been modified to display all the active defined rate environments. Values can be edited and saved in the Prepayment Speeds grid. These speeds are then used in the Maturity/Repricing module "behavioral" views, as well as in Projections, and in the IRSA and Fair Value calculations. In addition, the speeds are reflected in the Prepayment Documentation reports. Call Source Rate Environments The Call Source settings, found on the Matr/Repr tab of Chart of Accounts Setup, help the system know how to calculate the maturity date for an instrument during the download. In 2010a, when the Create cash flows for callable accounts Rate Sensitivity Cash Flows setting is active, the environments in the Call Source grid correspond to the cash flow schedules that were created for each defined rate environment, the last time the download was run. For accounts using the Create cash flows for callable accounts option, every Call Source rate environment is initially set to Call, since that matches the behavior of the model when the Callable Instrument option is not selected for an account and Call Dates are found for records downloading into the account. This is a change from prior behavior where everything was initially set to Calculate. Sorting Rate Shocks and the "Floating" Flat Scenario PROFITstar Only While the IRSA and Fair Value matrices have always let you to customize the Ceiling/Floor and Slope settings for six scenarios, the grids are now designed to keep the scenarios in order, from highest to lowest, and to allow the Flat scenario to "float" between the first positive and first negative defined scenarios. The sorting of the scenarios is based on each scenario's distance from the Flat scenario's ceiling rate. For example, while a scenario may have a Ceiling/Floor setting of 6.750, if the Flat rate is 3.250, then the scenario is considered a Rising scenario, and will be positioned among the other scenarios accordingly. The scenarios are reordered automatically when: The active matrix is calculated The Cash Flow Source setting is changed The matrix is re-opened In addition, the matrix can be sorted at any time by clicking the new Sort button. Page 4 of 54

5 Sorting Upper and Lower Limits PROFITstar Only In previous versions, when upper or lower policy limits were set up as IRSA and Fair Value matrix columns, the limits remained stationary in the grids and rarely needed attention. In the 2010a release, however, with the introduction of flexible rate scenarios and grid sorting, a scenario and its limits remain connected after a matrix is sorted, regardless of the Ceiling/Floor or Slope settings defined for that scenario. As a result, it is now more important than ever to pay attention to the limits assigned to each scenario, to make sure that the user-defined thresholds still fit with the rate shock currently being applied. Selecting Scenarios for IRSA and Fair Value PROFITstar Only In PROFITstar, the IRSA and Fair Value matrices are limited to six rate scenarios, in addition to the Flat scenario. When the IRSA or Fair Value matrix grid is displayed, a Select Scenarios button replaces the Sort button, if more than six cash flow scenarios have been downloaded or created. Clicking this button opens the Select Scenarios dialog, in which you can specify which scenarios to use in the current IRSA or Fair Value calculation. ~General~ OTS Prepayment Coefficients are now Model Specific Previously, the OTS Prepayment Coefficients stored in the program were not model specific. This could affect users who saved a projection to a What-If model and then downloaded the newest coefficient file during the monthly update. If the coefficients changed, all models were affected. In 2010a, only the active model is impacted when you download this information during the monthly update or manually edit the OTS Prepayment Coefficients grid. Note: The prepayment coefficient files are now identified as PrepayCoef.bsm for the Base model, PrepayCoef.WI1 for What-if #1, etc. When the file is automatically downloaded in the Update Wizard, the file extension is updated, depending upon the active model. If you manually download the file from the Client Portal, you will need to modify the file extension so that the correct model is affected. Page 5 of 54

6 Change to the Rate Sensitivity Cash Flows Selection PROFITstar Only On the Model Setup tab of Preferences Setup, the selection functionality for the Rate Sensitivity Cash Flows setting has been changed. Previously, you could only select one of the items in the associated list. Now either or both of the Download cash flows and the Create cash flows for callable accounts options can be selected by marking the check boxes. If both options are selected, PROFITstar will not create calculated cash flows for accounts that are targeted by a downloaded cash flow file even if the callable flag is active for that account. In these cases, the rates defined in the Scenario Control file will determine which rate scenarios are "calculated" for the accounts marked as callable. Allowing Servicing Costs to cause Negative Discount Rates In prior versions of 2010, the Servicing Cost assigned to an account could, in some circumstances, cause the account's Discount Rate (on the Fair Value Documentation report) to be negative. Now, you have the option of allowing or not allowing this behavior. If the Allow negative Discount Rate due to Servicing Cost setting is selected (on the Model Setup tab of Preferences Setup), then the prior behavior is retained. (This is the default setting.) If, however, this new option is not selected, then the Discount Rate will not drop below zero. ~Reporting~ Rate Environments in the Prepayment Documentation Reports PROFITstar Only A new Documentation > Prepay / Decay report has been created Prepay Rate Tables. This report shows all defined rate environments and the specified prepayments set up in any of the Prepay Rate Tables. The other Prepayment reports (Prepayment Documentation and Prepayment Customized by Month) have also been extended to show all the defined rate environments and the active prepayment speeds. Page 6 of 54

7 Quote Accounts Included in the Fair Value Documentation Reports PROFITstar Only The Fair Value Documentation report has been updated so that it now includes every account set up as Quote whether an account's Quote values come from PROFITstar Portfolio or were input in History. In a Fair Value Documentation report for a specific scenario, if the change from the Flat rate to the Discount rate exactly matches a defined rate environment then the corresponding Quote value entered in History will be seen on the report. If the actual shock amount does not exactly match a defined scenario interpolation will be used to calculate the Combined fair value for the Quote account. ALM Risk Analysis Predefined Report Packet Change PROFITstar Only Several headings in the ALM Risk Analysis predefined report packet have been updated to better respond to the flexibility of the IRSA and Fair Value scenarios. The last two pages of the report were originally designed to show rate shock results for the Rising 100 and Falling 100 scenarios. Data from Scenarios C and D were brought into the report, using Rising 100 and Falling 100" in the page headings. Now, since the C and D scenarios will not necessarily be the +100 and -100 shocks, the packet has been updated to use Scenario C and Scenario D in the page headings and graphs. In addition, the actual rate scenario basis point value is included in the graph header. PROFITstar Portfolio Synchronizing PROFITstar Rate Environments with PROFITstar Portfolio After setting up new user-defined rate environments in PROFITstar, you can then add them to PROFITstar Portfolio simply by opening the Portfolio program. When this is done, a message is displayed listing the rate environments that will be added to Portfolio, if the Sync Now option is selected. Note: No message will appear if you are opening Portfolio outside of PROFITstar and the data is not linked. In addition, you will not see the message if the PROFITstar model in which you have defined new rate environments is not the same as the PROFITstar model associated with your "Base Portfolio." However, the message will be presented if you subsequently switch to a different Saved Portfolio, which is associated with the model containing the additional rate environments. New rate environments that are synchronized with Portfolio are visible throughout the program. Page 7 of 54

8 Adding or removing rate environments will cause rate shock-related fields to be added or removed from the groups of fields such as $ Change in Value which are affected by shocks. New rate environment fields can be populated via the Import process or by manually inputting the necessary values. CMO Windows A new security Category called CMO Tranche has been added. This security type utilizes two unique fields Open Date and Close Date to model when principal payments will begin and end. The cash flow, for this type of security, will be interest only until the Open Date, after which the cash flow will include principal and interest, until the Close Date. During this "window," the principal amount which is the calculated payment amount for the instrument, less the interest will be completely amortized by the time the Close Date is reached. Open and Close dates, for each defined shock, can be imported. In addition, these fields can be modified in the Current Portfolio grid or in the Security Information screen, on the new CMO Information tab. Following the conversion to 2010a, the old CMO category will still exist, to preserve the prior behavior and results. You are encouraged to examine the securities that use the CMO category type to determine if any of them now need to be reclassified as CMO Tranche. This can be done after the import by manually editing the Category field, or it can be done prior to a new import by changing the mapping. Note: Related to this enhancement, the name of the MBS/CMO Information tab, on the Security Information screen, has been changed to MBS Information. Page 8 of 54

9 Determining whether a Security is Downloaded into PROFITstar A PROFITstar Portfolio security's Purchase Date is now used to determine whether it will be downloaded into PROFITstar. Previously, the Settlement Date was used to make this determination. If securities have a future Purchase Date: The records will be shaded in Portfolio. The balances will not be imported into PROFITstar's current month of History. The balances will not be included in the amounts seen in the Maturity/Repricing module. The balances will not be included in IRSA or a current month Fair Value calculation. The balances will be seen in Projections on the New Volume: Portfolio line. The balances will be included in a Future Fair Value calculation if the Purchase Date is historical to the calculated time frame. When PROFITstar and PROFITstar Portfolio Versions do not Match If the version of Portfolio you are running does not match your version of PROFITstar, you will now get a Version Mismatch warning. You will still be allowed to open Portfolio, but the Data Link to PROFITstar will be disabled until the programs are upgraded to use the same version. Prepayment Field Names Changed Previously, the fields related to Prepayments had titles that began with a plus or minus sign and a basis point shock amount. As a result, these fields were positioned at the top of any field list, while all of the other shock-related fields started with the field name, followed by the shock amount. The prepay field names have been changed to follow this standard naming convention. For example, +300bp Prepay now appears in the field lists as Prepay +300bp." Page 9 of 54

10 Field Selection change in the Formula Assistant The Formula Assistant is available wherever you can set or modify the Rate Spread, Life Rate Cap, Life Rate Floor, or Max Rate Adjustment fields such as when a variable-rate security is being modified on the Interest Rate Options tab of the Security Information screen. Beginning with the 2010a release, when a shock-related field is selected, only the Flat scenario will be available. (Not all of these use the identifier "Flat" in their field names.) If you have existing formulas that contain references to shocked fields, a warning message will be displayed the first time you open Portfolio, following the 2010a conversion. A Show details link will provide the field names and the associated CUSIP numbers. If the formulas are not modified, the Flat value for the fields will be used in any calculations and the program will continue to remind you about this situation. PROFITstar Budget Manager Behavior of Account Balances when Subledger Accounts are Added Previously, when a PROFITstar Budget Manager subledger account was added, its balances were zero, which caused the balances of any data items associated with the parent account to be set to zero as well, since the parent account's balances were determined by the subledger accounts totaling into it. This behavior is changed in 2010a. Now, when the first subledger account is created, any balances from the parent account in all of the account's associated data items are transferred to the subledger account. These balances also continue to show up in the parent account's "subtotal" row. Any additional subledger accounts will be created with zero balances. Be aware, however, that the initial balances of the parent account will not be restored if all of its subledger accounts are later deleted. This has not changed. Exported Organization Names In prior versions of PROFITstar Budget Manager, if a budget was exported and then an organization's name was changed in PROFITstar, that organization's name was not updated in Budget Manager when the organization was reexported. Now, if the name of an organization in PROFITstar is changed, the new name will be used the next time the affected organization is exported. Page 10 of 54

11 2010 Overview The 2010 release contains important enhancements, like Non-Accrual and FAS 91 handling in Projections, as well as numerous PROFITability improvements. In addition, our new and powerful update process is in place for all clients who upgrade to The 2010 release also includes a technology upgrade making PROFITstar a 100%.NET application. Be aware that because of this conversion to.net, some minor reporting and graphing differences may be observed in the 2010 edition. For those clients who previously upgraded to any earlier version of 2010, please review the following list for a summary of the improvements made and issues addressed since the release. Report Wizard: Column width differences caused some reports to require more pages Row height differences occasionally resulted in longer reports Saved Custom Reports could forget secondary report list selection Unable to rename an existing Saved Custom Report Big Six Assumptions time frame selections not saved after conversion ALM Risk Analysis Predefined Report Packet cell-referencing issues Gaps in Variance Report column shading Reports using certain font sizes show blank text when saved to PDF Income Statement Post Allocated, Pass by Line default layout was lost Post-Allocated Income Statement reports data has changed footer lost Page Scaling issues with PDF output Appropriate number of (cont) rows not always displayed Impact of Variance Report Column Width (minimum) in 2010 Column Header truncation issues Undesirable behavior of long formulas/text wrapping across page breaks Maturity/Repricing Narrative Report text issue Report footers not respecting changes to the default report type font Duplex printing did not always work as it did in 2009 Page 11 of 54

12 Report Writer: Text and Titles overlapping other cells or rows Report Writer footer displaying in a single cell Ratios in IRSA Matrix formulas not always converted correctly Embedded Pie graph colors not converting to the same default colors Unable to modify or define a graph name in an embedded graph Borders added to all embedded graphs or images, whether wanted or not Formulas not adjusted when beginning/ending point of range is deleted Report Writer arrows were missing black borders Formula recalculation issue IRSA Matrix account incorrectly referenced in a formula returned an error Graphs: Auto Minimum settings not saved Error when graph data exceeded defined Minimum / Maximum range Growth Line not adjusting to Growth % font size changes Solid color selected for a graph background, not honored Background and Appearance options not saved in certain situations Pie graph Rotation setting not properly saved Changing graphs to display fewer Bottom Axis time frames Custom Headers and Footers overlapping report or graph data Colors not retained when UD Graph is inserted into Report Writer Option added to provide crisper and cleaner-looking graphs in PDF files IRSA / Fair Value Instant Graph 3D line edge colors not adjusting properly Issues with background images that did not cover a graph s background Unnecessary message displayed when 2D line graph used Outline option Problem with UD Graphs if orientation was different from template used Page 12 of 54

13 PROFITstar and PROFITability ~Download~ New Download The new Download (also referred to as the Move & Link process) is now active for all clients who upgrade their software to the 2010 edition. A conversion of the old Download s settings will occur automatically, during the upgrade, for clients that were not previously using the new Download. The new Download provides improved ease of use when adding to or modifying your Download settings, as well as improved exception handling allowing you to address exceptions before the Link process occurs. Following the Download conversion, you will just have a few new screens with which to become familiar. To help you learn how to find and use these screens, you are encouraged to view the New Download Training tutorials, on Jack Henry's "Know It All" system: eventmonthyear=&event_id=2461&keyword=&postingform=default.aspx&cid=ja ckhenry&pid=1&lid=3&cart_currency_code=&payment_type=&orderby_location= &orderby_date=&newregistration=&bundle_location_group= Important Change Affecting Downloaded Actual Maturities In prior versions, downloaded Actual Maturity balances were only consolidated into roll-up organization levels if the balance in each of those consolidating levels was zero. This process worked well if users just downloaded Actual Maturity data to their subentities. Then, when the data was consolidated, it was brought up to the roll-up levels. There was an issue, however, if users subsequently edited Actual Maturity values in their subentities and then reconsolidated. In this instance, the old value remained at the roll-up levels (since the balances were no longer zero). This behavior has been changed. Actual Maturity balances will now always be consolidated into roll-up levels. If you are currently downloading your Actual Maturity data only into your top level, then when you run consolidations, zeros from the subentities will overwrite your Actual Maturity values. As a workaround, clients in this situation are encouraged to see if they can get Actual Maturity data by branch (which is especially important if you are doing projections at the branch level). If this is not possible, or if you don t project at the branch levels, then the files containing Actual Maturities will need to be set up to download into subentities. Page 13 of 54

14 ~Projections~ Non-Accrual Handling A new Loan field Non-Accrual Flag has been added to the download, which makes it possible to identify non-accrual loan records. With non-accrual loans flagged, PROFITstar can now download the information necessary to let you see the effect these loans have on yields and maturities, in Maturity/Repricing and Projections. Interest-Only Repayment Periods Institutions, with existing loan volumes that are currently in an interest-only repayment period, can now set up PROFITstar to download and project these types of instruments. FAS 91 Handling In PROFITstar, it is now possible to amortize the remaining deferred fees amounts for existing loan products and automatically calculate projected deferred fees, for new and existing loan volume. The model is then able to recognize the amortized portion of the deferred fee amount as income. Change to the Instrument Level Detail Prepayment Calculation This change may affect IRSA and Fair Value results, for clients who utilize Instrument Level Detail, with accounts using PSA and/or OTS prepayment methods. For clients using Instrument Level Detail, 2009 and previous versions of PROFITstar utilized the Funding Date in prepayment speed calculations. In 2009a and all later versions, the Instrument Level Detail prepayment speed calculation now uses the Origination Date. This is significant since the Last Repricing Date field previously determined the Instrument Level Detail Funding Date. If the Last Repricing Date field was not downloaded, the model used the current month as the default Funding Date. When the program used the current month as the Funding Date, the affected instruments were treated like new instruments and were assigned the lowest seasoned prepayment speeds. Accounts utilizing the PSA and OTS prepayment methods were affected since these methods take into account the seasoning of an instrument (the time elapsed since the loan was originated or last repriced) and the impact that this has on customer prepayment behavior. Page 14 of 54

15 In 2009 and previous versions, these calculations could have caused low prepayment speeds, which would result in low prepayment behavior having very little effect on the contractual repayment schedule. More of the outstanding principal balance would stay on the books longer. Assuming that the Discount Rate and the rate of the instruments are similar and assuming a flat rate environment, results would typically show a lower balance sheet fair value. However, more dollars on the books longer would typically increase the earnings until maturity affecting the income statement fair value component of the Fair Value calculation. With the 2009a change, where the Instrument Level Detail prepayment speed calculation now uses the Origination Date, the true seasoning of individual instruments is better represented thus allowing the assignment of a more accurate prepayment speed to each instrument. As a result, it is possible that higher prepayment speeds than those used in previous versions will now be applied to your portfolios. Because this higher prepayment speed will affect the maturity schedule of the instruments, IRSA and FV results will likely be impacted. Principal balances will appropriately mature faster than they would in 2009 and prior versions. Assuming that the Discount Rate and the rate of the instruments are similar and assuming a flat rate environment, results would typically show a higher balance sheet fair value. However, fewer dollars on the books in future time frames typically decreases the earnings until maturity again, impacting the income statement fair value component of the Fair Value calculation. Calculate Discount Spread For accounts set to discount to a Yield Curve, the ability to calculate automatically the Discount Spread has been added in Chart of Accounts Setup. Previously, when accounts were set up to discount to a Yield Curve, the user needed to define what spread over or under the yield curve was to be used for discounting purposes. As rates on the yield curve changed, the user had to modify the spread manually so that it remained accurate and appropriate. Now, when an account is set up with a Fair Value Treatment of Discount or FAS 107/Discount, and its Discount Rate is set to a Databank Yield Curve, the Spread Behavior option becomes enabled. Choosing Static gives you the old behavior; requiring manual updating of the Discount Spread. If the new Calculate option is selected, you must define the point on the yield curve that the account should be priced to, by entering a value (in months) in the Yld Curve Month box. The model will then use the rate that corresponds to that yield curve point, in conjunction with the account's defined Offering Rate, to arrive at a calculated Discount Spread. Page 15 of 54

16 Changes Affecting Balance Sheet Statistical Items in Projections Because the FAS 91 Deferred Loan Fees amount relies on the Number of New Accounts projected for future time frames, the way that the Number of Accounts and Number of New Accounts statistical data items are calculated in projected time frames has changed: Number of Accounts is now system calculated in Projections. (Formula: Month-End Balance / Stat Avg Balance.) Number of New Accounts is now interrelated with the Avg Bal New Accts item, so that the first one defined (along with the New Volume: Purch row's amount) will be used to calculate the projected value of the other. If you are using the Number of Accounts or the Number of New Accounts values in Projection Formulas, be aware that these statistical items now respond to changes in volume projections. It is no longer necessary to modify these numbers manually during the initial projection, or when modifications are made to existing assumptions. Zero Projected Time Frames The Zero Month-End Projections Distribution Action, which was an option for Balance Sheet accounts, has been renamed Zero Projected Time Frames. In addition, it is now also available for projected Databank and Non-Interest Income/Expense accounts. ~FTP~ FTP Logic Improved - PROFITability Several enhancements have been made to improve the logic of Matched Funded FTP calculations: Matched Funded FTP calculations now include records that paid off or closed during the month which have month-end balances of zero but still have nonzero average balances. These records will be included in the FTP rates export to third party systems. The Matched Funded FTP logic now allows for loans that have been purchased. FTP calculations will use the Acquisition Date for funding purposes rather than the note s Origination Date, if this field is available. Page 16 of 54

17 ~Setup~ Documentation Provided When Deleting an Allocations-Related Account In previous versions of PROFITstar Suite and PROFITability, the Delete button was unavailable when you were focused on a Databank, Balance Sheet, or Income Statement account that was tied to some aspect of the Allocations process typically to a rule or methodology. Now, the Delete button appears active for these accounts. However, when it is clicked, the program scans the chart of accounts to determine which accounts are deleteable. If the program determines that the account on which you are focused cannot be deleted, a Why this account cannot be deleted log will now be displayed, which lists all the Allocation Methodologies and Rules that depend on this account. For Databank accounts, the log will also show a list of accounts from FTP Setup, which are using this account as their selected Rate Account. (Rightclick the log to print it.) This new documentation is designed to help make users aware of the implications of deleting an account with Allocations-related dependencies to prevent actions that could change post-allocated results. Note: Contact your Client Services Analyst if you have more questions about deleting this type of account. Balancing Accounts Checked When Exiting the Chart of Accounts The accounts designated as Balancing Accounts must be set up as fully liquid accounts. Any balances currently held must be able to mature immediately, and any balances in future time frames must be allowed to mature fully the following month. To ensure that the Balancing Accounts are set up properly, a 'sanity check' for correct settings has been added to the tasks the system performs when you click OK to end a session in Chart of Accounts Setup. Any account using the Balancing Acct special account code will be checked for the following settings: Auto Update Action should be Historical Balance in First Maturity Type should be Number of Months Maturity Interval should be 1 A message will be displayed if any of these settings needs to be adjusted before you leave the Chart of Accounts. Page 17 of 54

18 Saving Yield Curve Twist Shapes In the Yield Curve Twist Projection wizard (in User-Defined Quick Projections Setup), it is now possible to define a shape, and then name and save that shape. User-defined shapes are added to the Yield Curve Shapes list, along with the historical time frames all of which represent specific yield curve shapes. These defined shapes can then be individually assigned to the Horizon points selected in the wizard. Note: When a user-defined shape is used to define a Horizon point, the rates associated with the shape are assigned to the specified Horizon point. Although the Horizon point will continue to use the assigned rates until you pair it with a different shape, there is no ongoing connection between user-defined shapes and Horizon points. Therefore, if you define a new shape and save it to an existing shape's name, no Horizon points will be automatically refreshed to use the newly defined shape. Copy Relative Ranking Setup between Dimensions PROFITability The Relative Ranking Capital allocation methodology requires the assignment of a relative risk factor for each risk component, for each account or subtotal. Previously, if this allocation methodology was to be used in each PROFITability dimension (Organization and Product), it had to be manually set up twice. Now, it is possible to copy the setup from one dimension to the other. If you are on the Organization tab, right click the grid and select Copy to Product. On the Product tab, select the Copy to Organization right-click option. Renaming Budgets It is now possible to rename a Budget as easily as renaming a Model. From the Main screen, verify that you are in the appropriate Model and that the active Budget is the one to be renamed. Then, on the Model Setup tab of Preferences Setup, modify the Budget's name in the Current Budget Name box. (Budget names are limited to 16 alphanumeric characters.) ~Maturity/Repricing~ Clear Reconciled Differences If the instrument level detail Reconcile Differences distribution action has been applied to an account in the Maturity/Repricing module, you can now roll back this action with the new Clear Reconciled Differences option. Previously, the Clear Instrument Level Detail Tools menu option was the only way to reverse a distribution action applied to an account's instrument level detail. Page 18 of 54

19 ~Reporting~ More Reports Added to the Examiner Report Packet PROFITstar Only Six more reports have been added to the Report Wizard's Examiner Report Packet. These are: OTS Prepayment Rate Estimates (Documentation Prepay / Decay) OTS Decay Rate Estimates (Documentation Prepay / Decay) Balance Sheet to Balance Sheet Ties (Documentation Scenario) Projection Formulas Offering Rate (Documentation Setup) Projection Formulas Volume (Documentation Setup) Projection Formulas Income (Documentation Setup) Improvements to the Allocation Rules Setup Report PROFITability The Allocation Rules Setup report has been enhanced in the following ways: If a rule is set up so that selected Target Units are included or excluded, the specific organizations or products are now listed on this report. Any current notes associated with a rule will also be included on the Allocation Rules Setup report, for both organization and product rules. This Report Wizard report is found at Documentation Setup Allocation Rules. Date Source Settings Added to the New Volumes Report PROFITability New settings have been added to the PROFITability program's Analytical New Volumes report. These Date Source options let you specify whether the Origination Date or the Funding Date will be used as the controller, for the data from each application file type that is used in the report. One of the primary benefits of this enhancement is the ability to fine-tune New Volumes results for time deposits with Roll Dates. Unit Classification Summary Report Comparison Time Frames PROFITability The PROFITability program's Analytical Unit Classification Summary report has been enhanced to let you select the comparison time frames used in the report. Previously, the report compared product unit income/expense to a rolling 12- month average (based on the 12 months prior to the month selected for the report). Page 19 of 54

20 Weighted Average Life Information in Maturity/Repricing Reports Each Balance Sheet account's weighted average life value, from the Maturity Repricing module, has been added to the following Maturity/Repricing reports: Detail Gap Cumulative Gap Maturity/Repricing The WAL values included in these reports can be affected by your Prepayment Type selection (Contractual or Behavioral), just as the Data button options in the Maturity/Repricing module (Contractual or Prepay), can impact the information displayed below the grid. Note: The weighted average life (WAL) information is shown under each account title. New Output Option in Report Central Report Central users can now choose a Single PDF File Per Report option when generating a multiple reporting group. This option is available from the File Export To PDF menu command or the PDF speedbutton. Two New Day / Time Functions Added to Report Writer Two new Day / Time functions are now available for use in Report Writer formulas: DaysInYear This function returns the total number of days in the year, based on the selected time frame. DaysYTD This function equals the number of elapsed days in the year, through the specified month; based on the selected time frame. Miscellaneous Report Wizard Enhancements Other 2010 enhancements to Report Wizard reports include: A new copy option has been added to the View Data screen The Copy entire grid to clipboard button should be used when you want to copy the whole grid (including row and column headers) to the clipboard. A column for Book Value (current month balance) has been added to the Fair Value Combined (Last Calc) report. After calculating Fair Value, this report can be requested from Risk Analysis Fair Value Combined (Last Calc). (PROFITstar only.) The Post-Allocated, D/I/O Combined and Segregated reports can now be generated for multiple Custom time frames. (PROFITability only.) The ability to choose between layouts using either Organizations/Products or Time Frames as columns has been added to the Post-Allocated, D/I/O Combined and Segregated reports. (PROFITability only.) Page 20 of 54

21 ~General~.NET Technology Migration The 2010 version of PROFITstar and PROFITability is now 100% Microsoft.NET. This technology migration is an important upgrade to allow us to take advantage of the latest Microsoft technologies in future product releases. General program functionality has not changed, but you may notice some screens or reports that have a slightly different appearance due to the use of new.net software components and controls. Please note that the 2010 version uses a new.net reporting component. In most cases, reports (Report Writer and Report Wizard) will look as they did in previous versions with little-to-no significant changes. In a few cases, adjustments may be needed if specific reports require the same number of rows, for example. Please see the topics on column widths and row heights for more information on possible report formatting differences. Searching for Accounts by Short or Long Titles The ability to search for accounts by either Short Title or Long Title has been added to the account lists in Chart of Accounts Setup and Databank Setup. CalcuWeighter Available in History, Projections, and Budget Modules The CalcuWeighter tool is now available in the History, Projections, and Budget modules, for rates only. Previously, you could only access this tool in Maturity/Repricing. In this module where an account's Maturity/Repricing amounts and rates are interrelated the CalcuWeighter is used when you need to manually input an account's maturity or repricing schedule information for a single month. As values are entered, amounts are summed and rates are weight averaged. Both are then saved in the appropriate places. In History, Projections, and Budget, there is no amount/rate relationship. When the CalcuWeighter is used to calculate a weighted average rate in any of these modules, the calculated rate is saved to the selected cell, but the total amount is disregarded. Storing Cents in the Data Grids When manually keying or pasting values into the data grids, the program will now allow you to input both dollars and cents. While the grids only display rounded, whole dollar amounts, the cents are stored and can be viewed in the Calculator tool when it is opened on a cell containing such a value. If you copy data out of a data grid, the cents information is captured as well, and when the data is pasted, both dollars and cents will be displayed if the receiving cells are formatted appropriately. Note: A specific flag must be set before this functionality is available. Your Client Services Analyst can help you activate this extended precision. Page 21 of 54

22 Fixes While you are always encouraged to run the latest version of the software, please review this list of resolved issues to see if your institution would benefit from any of these changes. Version Release Date Items Addressed 2010a /03/2011 PROFITstar Portfolio and PROFITstar Fixes Missing Bloomberg Cash Flows In the prior version of 2010a, it was determined that when the Bloomberg Update was run, Bloomberg cash flows were not being updated and the Cash Flow Available field was reset to No. As a result, the program substituted PROFITstar Portfolio-calculated cash flows for any instruments that were missing Bloomberg cash flows. Call Schedules and Structured Note Schedules were also affected by this problem. All of these issues are corrected in the current release. Status Field Potentially Missing in Import Formats In PROFITstar Portfolio, Status is a user-defined import field that can be used to exclude rows of information during the import process. In 2010a, a problem was found that could have affected some clients who utilize this field. If a PROFITstar Portfolio import format which included a defined Status field was created in 2010 or a prior version, and was then opened or edited in 2010a.192, the Status settings would be lost (if the field was not subsequently reestablished). Other 2010a clients using the Status field would not have encountered this issue if: They converted to 2010a and never opened their import format(s). They converted to 2010a, opened their import format(s), noticed that the Setup field was not defined, and set it up again. While the underlying issue is fixed in 2010a.199, clients who utilize the Status field are encouraged to check their import format(s), following the installation of the latest version, to ensure that the field is set up properly. Page 22 of 54

23 2010a.199 continued Copying Shocked Field Values when Advancing the Month Prior to 2010a, prepay speeds and other data values for shocked PROFITstar Portfolio fields were copied into the new month, when the month was advanced. In 2010a, however, these values were cleared during the Advance Month process. Now, the previous behavior has been reinstated and the shocked field values are once again copied forward so that the new month starts with the same values as the prior month. The shocked fields affected by this change are: Close Date, Exercise Date, Market Value, Open Date, Penalty, and Prepay. Creating Callable Cash Flows while Downloading Cash Flows In 2010, the selection functionality for PROFITstar s Rate Sensitivity Cash Flows setting (in Preferences Setup) was changed so that either or both of the Download cash flows and the Create cash flows for callable accounts options could be selected, depending upon the user s selection. In 2010a, an issue was discovered that caused downloaded cash flow figures to be inflated if callable cash flows were created along with downloaded cash flows. This has been fixed in 2010a.199. Page 23 of 54

24 Version Release Date Items Addressed /16/2010 PS/PA Fixes Balance Sheet Accounts with Matched Funding Balance Sheet Ties ***Under very specific circumstances, only clients utilizing the PROFITstar Matched Funding Account Balance Sheet Tie option have a chance of being affected by this issue.*** In Chart of Accounts Setup, it is possible to define a balance sheet to balance sheet account tie, using the settings associated with the Balance Sheet Tie option, on the Advanced tab. If the Matched Funding Account setting is also selected, the model will override the maturity/repricing schedule of the target account (the account currently selected in the chart) and replace them with schedules identical to the source account (specified in the Balance Sheet Account Tied box). The maturity/repricing schedule of the target account is modified during the Auto Update calculations or when prepayment values are recalculated. In prior versions of 2010, it was discovered that certain accounts lost their maturity and repricing rates when the Auto Update calculation was run or when prepayment values were recalculated. This only affected accounts: With balances around $34,000,000 That were set up with a Balance Sheet Tie that utilized the Matched Funding option This issue is fixed in Page 24 of 54

25 continued New Download Date Conversion ***This only applies to clients who have not yet converted to a 2010 version of the software, and who use certain unique custom download date formats.*** Since the MonthYearDay or DayYearMonth custom download date formats (from the old download) are not supported in the new download, when a user attempted to perform any download-related action, following the 2010 conversion, the program would close with an error. Now, when users convert to , the Download Conversion Warnings log will provide the following notes, when needed: File: [file name], Field: [field name] Date format MM/YY/DD is not supported. File: [file name], Field: [field name] Date format DD/YY/MM is not supported. These date formats will be converted to the MDY format, for the affected fields, in the appropriate File Layout Setup screens. Going forward, the user will need to determine if further adjustments to the download settings, or to the extract file(s), are required. Page 25 of 54

26 Version Release Date Items Addressed /16/2010 PS/PA Fixes Restoring a Selected organizations backup The following fix information is only pertinent for PROFITstar users that utilize the Selected organizations backup option as part of their monthly processing. Under very specific circumstances, restoring a Selected organizations backup file could delete root organization records. All of the following conditions would have to be true before this issue would have affected a user: User had upgraded to a previous version of The All chart setup is global setting was unchecked. User had created a Selected organizations backup (which did not include the root organization) and then restored it into an existing model. This issue is resolved in Report Writer/Graphs Border/Outline Options Generated Message In Report Writer and User Defined graphs, an unnecessary message was displayed when a 2D line graph was created or modified so that a graph item s Border > Visible option was set to No and the Outline > Visible option was set to Yes. The message occurred when Report Writer s Graph Setup dialog was closed or when the Preview Graph option was selected in User-Defined Graphs. This is fixed in the current release. Graphs Creating New UD Graphs Using UD Graph Templates When creating a new User-Defined Graph, any User-Defined Graph template can be applied. In previous versions of 2010, if graph being created had a different orientation than the template, and the common Data Category used was Time Frames, then the resulting graph displayed inappropriate dates on the date axis. In addition, changing certain other axis settings could result in the program closing with an error. These issues have been corrected. Page 26 of 54

27 Version Release Date Items Addressed /01/2010 PS/PA Reporting Issues Printing Grids Top Margin Size When printing from grids such as the Maturity/Repricing Instrument Detail grid the top margin size increased, in the 2010 versions. For the current release, these margins have been reduced to match more closely the 2009 dimensions. Report Wizard Additional (cont) Rows Report Wizard can show additional "(cont)" rows at the top of the page, depending upon the report and the layout. Prior versions of 2010 did not always display the appropriate number of (cont) rows. This behavior has been corrected. Report Wizard Variance Report Column Width In prior versions of 2010, the Variance report Column Width (minimum) setting could cause more columns of data to appear on a page than were previously displayed on the same report in This issue is fixed in Page 27 of 54

28 continued Report Wizard Column Header Issues Some Report Wizard column headers were displayed with little or no margin between them and the neighboring columns. In addition, some longer headers were cut off in mid-word when they could have been truncated between words, or in a more intuitive manner. For the current release, the program will attempt to handle column headers in the following ways: If the text in a column header is too wide to fit, it will be truncated between words, whenever possible, instead of mid-word. This will generally provide more space between columns than what was observed in prior versions of If a header contains a very long word, it may still need to be divided between characters (mid-word). In rare instances, such as on the Balance Sheet Setup report, a few columns were widened slightly to allow the display of more meaningful headers. Report Wizard Reports with Wrapping Text Saved to PDF Several types of reports, which contained formulas or other text strings, demonstrated a problem when formulas or text tried to wrap to multiple lines, across page breaks. For example, when previewing the Documentation Setup Ratios report, if a ratio formula required two lines to display, the first part of a ratio s formula might be shown on one page, with the continuation of the ratio formula on the following page. However, when the report was saved to PDF, both lines of the ratio formula were displayed on the first page, with both lines of the formula repeated on the second page covering some of the header text. Now the behavior mirrors what was seen in 2009 with the exception that if not all lines of a formula or text string fit on the bottom of a page, then the multiple lines will be shifted to the next page. Report Wizard Maturity/Repricing Narrative Report Text In the Maturity/Repricing Narrative report, some text in the "The effect is that " column extended outside the boxed area, when printing to PDF. This is resolved in the current release. Page 28 of 54

29 continued Report Wizard Report Footers and Changes to the Default Font Report footers did not always respect changes to the Report Wizard default font specified for a certain report type. The affected reports included: Discount Spread Calculation Fair Value - Combined (History) Fair Value - Combined (Last Calc) Fair Value Current (FASB 107) OTS Prepayment Total Risk Evaluation Allocations reports Activity Cost reports This is fixed in Report Wizard & Report Writer Duplex Printing Using the Duplex option to print reports on both sides of each sheet did not always work the same way it did in Now, handles duplexing, with the following exceptions: When printing a Predefined Report Packet, out of Report Wizard, the Duplex option is ignored even if it is the default setting on the selected printer. To print a packet on both sides of the paper, save it as a PDF file and then print this file. When printing a Multiple Reporting Group, out of Report Central, the Duplex option is ignored even if it is the default setting on the selected printer. To print a group on both sides of the paper, save it as a PDF file and then print this file. Note: If the Multiple Reporting Group only contains a single report, graph, or graph group, then the program will treat it as a single report and will honor the printer s Duplex setting. Report Writer Adjusting Formulas when Report Data is Deleted If a cell, row, or column is deleted, which affects either the beginning or ending point of a formula range e.g., row 1 or row 9 in "Sum(B1:B9)" the formula does not adjust properly, in prior versions of Now, the range in the formula will adjust so that the deleted data is no longer referenced. Page 29 of 54

30 continued Report Writer Arrows Missing Borders In earlier versions of Report Writer, arrows were missing their black borders. This issue has been resolved. Note: The formula for adding arrows to a report is: =arrow(arrowtype,color) Refer to the online Help for more information about using arrows in Report Writer. Report Writer Recalculating Formulas An issue was observed in Report Writer where an action that forced all parts of a report to recalculate, subsequently prevented the very next edit from being reflected in dependent cells. For example, the sum at the bottom of a column would not be updated after a cell in that column was modified. However, additional edits did cause dependent cells to update as expected. Operations that force the entire report to recalculate, and therefore could have caused this behavior in previous versions of 2010, are listed below: Edit > Calculate Now (F9) File > Preview File > Print File > Export > PDF Edit > Paste (When pasting text that was copied from another application not from Report Writer into the grid.) Edit > Delete Edit > Replace Insert > Rows Insert > Columns Tools > Options > OK File > Page Setup > OK or Cancel Now, Report Writer calculations work as they did in Page 30 of 54

31 continued Report Writer Error if IRSA Matrix Account is Incorrectly Referenced If a Report Writer formula incorrectly referenced an IRSA Matrix account as line "0", an error was displayed in the affected cell. Then, when anything else in the report was subsequently edited, another error caused the program to close. Example formula: =Data(Acct(0, Chart(7) ), DataItem(53), Scen(3)) This issue has been corrected. Report Writer & Graphs Colors used in an Inserted Graph If a User-Defined Graph (bar, area, line, or point) was created, utilizing the Color Each Appearance options, and it was subsequently inserted into a Report Writer report (Insert > User-Defined Graph), the resulting colors in the graph were different. This behavior is fixed in the current release. Graphs Improved Graph Quality Option Available for PDF Output A new setting has been added to the Features in Use section of the Preferences Setup General Settings tab. Select the Print Graphs With High Quality (Slower) option for crisper and cleaner-looking PDF files, which include graphs or reports containing graphs. Windows 7 users should obtain the most benefit from this setting. Note: This option should not be selected when graphs that use patterns are saved as PDF files. Graphs IRSA / Fair Value Instant Graph 3D Line Edge Color In earlier versions of 2010, when the color of a graph item was changed, on an IRSA or Fair Value instant graph, the edges of the 3D line did not adjust to use the proper color for the border of the line. Now, when a user changes a graph item color, the system will select the same color for border lines. In addition, the new default for IRSA and Fair Value instant graphs, along with Yield Curve and GrafPlan graphs, is for the 3 Dimensions option to be set to No resulting in these graphs being displayed as 2D. Note: When displaying one of these instant graphs, the options on the Modify Graph properties panel can be used to change the graph s 3 Dimensions settings, but such changes will not be saved when the graph is closed. Page 31 of 54

32 continued Graphs Background Images that do not Cover the Entire Background If a graph had an image assigned to its background, the Image > Style was set to Normal or Centered, and the image's size was smaller than the background area of the graph, then when this graph was saved as a PDF file or printed, the area outside the image appeared black. Now, any background area not covered by such an image is treated as transparent. Note: Since the black color is being converted to be transparent, in these instances, it is possible that any black parts of the background image will appear white when such a graph is printed. Page 32 of 54

33 Version Release Date Items Addressed /28/2010 PS/PA Reporting Issues Report Wizard Column Width Differences Several 2010-related issues affected the width of columns in Report Wizard data reports. ( Data reports include Databank month-end (non-global); Balance Sheet all options; Income Statement pre- and post-allocated, chart; Rates; Ratios; and Risk Analysis Regulatory Ratios.) The following column width issues were observed in earlier 2010 versions: Unnecessary white space followed the information in the first column of the Report Wizard data reports. (The first column usually contains Account, Organization, Time Frame, or Product titles, depending upon the report and its layout.) This extra white space reduced the number of columns that could fit on a page adversely affecting reports that were designed to fit on a certain number of pages. In 2009, for reports using Organizations or Products as columns, the column title text was truncated, if necessary, to limit the width of a report s columns. (This behavior also affected some Documentation report types, such as Setup reports, where the names of certain options were truncated in the column header.) In 2010, however, report columns expanded to accommodate the names in the column header, which could cause reports to require extra pages. In some other situations, the column widths in 2010 were actually smaller than they were in In preparing the release, a concerted effort was made to ensure that you see little or no difference in the number of columns per page, in your 2010 reports, when compared to the same reports generated in 2009 or prior supported versions of PROFITstar and PROFITability. Note: No name or title information is lost if the program truncates column title text in a report. An option that would let the user control whether or not to truncate titles in column headers is planned for a future release. Page 33 of 54

34 continued The report examples below comparing the last 2009 version with the new 2010 version demonstrate how similar the column width formatting now is Reporting Example Column Comparison Reporting Example Column Comparison Note: If it is necessary to adjust further the number of columns displayed on each page of a specific report, you can use the Advanced settings on the Report Wizard s Format tab to adjust a report s right margin. Page 34 of 54

35 continued Report Wizard Row Height Differences Wherever a data value was followed by a cosmetic line, additional white space was observed between the two. If enough cosmetic lines were present, a report that had been modified to fit on one page might have had rows pushed onto a second page. In , a concentrated effort was made to keep report page counts from increasing. Now, the program is making better use of the available space. While some row spacing differences are expected in 2010 your report pages may contain a few more rows it should be rare for rows to be pushed onto a following page. The report examples below provide a comparison of row spacing, as it existed in 2009 and its current behavior in Row Spacing Example Row Spacing Example Note: If it is necessary to adjust further the number of rows displayed on each page of a specific report, you can use the Advanced settings on the Report Wizard s Format tab to adjust a report s bottom margin. Page 35 of 54

36 continued Report Wizard Saved Custom Reports and Secondary Lists Under certain circumstances, Saved Custom Reports with associated secondary reports lists, appeared to forget which report from the list should be selected. For example, if a user selected a Saved Custom Report, which happened to be one of these report types (listed at the bottom of this page), and clicked the Data tab, one of the reports in the secondary list would be selected. Example of a Data tab Secondary Selection List If the user then clicked back to the Start tab, selected a different Saved Custom Report, of a type listed below, then clicked back to the first report they had examined, and returned to the Data tab, the top report in the secondary list would now appear to be selected. Report Wizard report types containing a secondary selection list Commonly saved as Custom Reports Variance Reports (all) Analytical Trend Not typically saved as Custom Reports Download Extract File Layouts Download Account Link Setup Download Organization Link Setup Download Product Link Setup Download Multi-Column Account Links Download Move Results Documentation Setup Variance Report Setup Documentation Setup Quick Projection Setup Page 36 of 54

37 continued In , this behavior has been corrected, regardless of how a user navigates to the Saved Custom Report list whether by entering the Report Wizard directly or by selecting such a report via Report Central. Important: Users, who have been working in a previous version of 2010 and have Saved Custom Reports with corresponding secondary reports, will want to check these reports to make sure that all of the report associations are correct. Report Wizard Renaming an Existing Saved Custom Report If a user tried to edit the name of an existing Saved Custom Report, on the Report Wizard s Start tab, the first character entered was never shown. No matter where you originally placed the cursor in the Report Name box, the cursor was moved to the beginning of the name. In addition, after each keystroke, the user was asked if they wanted to save their changes. Finally, changes made to the name were immediately visible in the Saved Custom Reports list but were not immediately visible in the Report Name box on the right side of the screen. All of these issues have been corrected. Report Wizard Big Six Assumptions Time Frame Selections The time frame selections stored for the Big Six Assumptions report converted correctly to prior 2010 versions. However, whenever these settings were subsequently modified, those changes were not saved. All time frame changes are now retained. Report Wizard ALM Risk Analysis Predefined Report Packet Following the conversion to earlier versions of 2010, two reports in this report packet Credit Risk and Liquidity Risk were affected by cell-referencing errors. The cell-referencing issues were fixed in ; ensuring that graphs in the affected reports are displaying correct data. Page 37 of 54

38 continued Report Wizard Variance Report Column Shading Variance reports containing shaded columns displayed gaps in the shading, around cosmetic lines and sometimes between each row. This shading behavior was different from what was seen in 2009 and earlier versions. This has been corrected. Page 38 of 54

39 continued Report Wizard PDF Reports with Certain Font Sizes Show Blank Text In prior versions of 2010, it was observed that some larger font sizes such as the Arial 16 point font used in the following examples caused report data to display as blank text when sent to PDF Balance Sheet Month-end Report PDF A change to correct row space for the various font sizes resolved this issue Balance Sheet Month-end Report PDF Page 39 of 54

40 continued Report Wizard Default Layout for Income Statement Report In versions prior to 2010, PROFITability s Income Statement Post Allocated,- Pass by Line report would default to a layout where data for each selected time frame would show on the page, with the accounts as rows, and the organizations as columns. Columns for multiple organizations could then be seen on a page. In 2010, the report layout could unexpectedly change to a layout where data for each selected organization would show on the page, with accounts as rows, and time frames as the columns. Now, the default layout for this report has been restored. Report Wizard PROFITability Income Statement Reports Footers The PROFITability Post-Allocated Income Statement reports (other than Chart ) should include the following footer if the data is out of date: In earlier versions of 2010, this footer was not displayed when it should have been. Now this footer is appropriately displayed. Report Wizard/Writer Effect of Page Scaling Options When PDF reports, which were created in the Report Wizard or Report Writer, are previewed and printed with Adobe Acrobat, the Top and Left margins may appear larger than expected. This, in turn, may cause the size of the text in the report to be reduced (scaled). This behavior is due to a setting in Adobe Acrobat that affects how it prints reports. That setting is specific to Adobe Acrobat and is neither something that PROFITstar sets, nor anything that PROFITstar can affect when reports are generated. In Adobe Acrobat s File Print dialog, there is a Page Scaling option, which needs to be set to None. When this is done, Adobe will not scale the document which can increase the size of the margins. When the Page Scaling option is set to None, PROFITstar s PDF reports, which are printed from Adobe Acrobat, will appear nearly identical to the reports that are sent directly to a printer from PROFITstar. Page 40 of 54

41 continued Report Writer Text and Title Truncating Behavior In 2010, a reporting behavior was changed so that the entire contents of a cell would always display. This was implemented so that long Organization names or account names would not be truncated and would display fully on the printed report. However, when Report Writer reports were converted to 2010, the column widths were not automatically resized to adjust for the wider content. When all of the text in a cell was displayed, the problem most commonly observed was text from one cell overlapping the information in the cell next to it, or overlapping from one row to the one below. In response to this behavior, we have now made another change. The full text or title will now populate each cell, but it will again be truncated so only the text that the column width allows will show. If a user begins to make a cell/column wider, the full text in the cell will start to display. In addition, Report Writer s Wrap Text option has been modified. If the user chooses to wrap the text in a cell but the row is not tall enough to display the text that wraps to another line, it too will be truncated. Only the text that can show within a cell s current width and height constraints will show. Page 41 of 54

42 continued Report Writer Images in Custom Footers In prior versions of 2010, it was possible for an image in a Report Writer footer to end up displaying in a single cell. This is fixed in the current release. Page 42 of 54

43 continued Report Writer IRSA Formulas not Always Converted Correctly Under specific circumstances, if a ratio used in an IRSA Matrix formula existed in the Ratio chart of accounts below a ratio with a Product setting of PROFITstar Only, then following the conversion to prior versions of 2010, the formula would not be referencing the same ratio account. Ratios Setup Product Option In the following example, IRSA Matrix formulas were set up in 2009 that referenced the Earn Power Ratio (column highlighted in green), which was one of the ratios below the first PROFITstar Only ratio, in this set of data Report Writer Report with IRSA Account formulas Page 43 of 54

44 continued Following the conversion to 2010, the formulas in question referenced a different ratio (NIM Period) Report Writer Report with IRSA Account formulas For users who are upgrading from 2008 or 2009, the version converts IRSA Matrix formulas correctly. Important: Users, who were running an earlier version of 2010 and have Report Writer reports containing IRSA Matrix formulas, will need to review these formulas, after upgrading to The correct ratios will need to be reselected if this issue affects any of their IRSA Matrix formulas. Page 44 of 54

45 continued Report Writer/Graphs Pie Graph Section Colors Conversion Issue The default colors for Pie graph sections (and order in which they were used) changed between 2009 and earlier versions of If a user created a Pie graph in Report Writer and kept the default segment colors, in 2009, and then viewed the graph in a prior version of 2010, they might have seen different segment colors. In , default Pie graph segment colors now convert correctly. Important: Users who worked on an earlier version of 2010, and have graphs of this type embedded in Report Writer reports, may need to reselect segment colors. Report Writer/Graphs Embedded Graph Name When a pre-2010 Report Writer report containing an embedded graph, which relied on data in the report, was converted to 2010, the graph title could no longer be edited. In addition, if a new report was created with an embedded graph (based on data in the report), it was not possible to define a graph title. In both cases, the Text box was grayed out and displayed a Value of n/a. Both issues have now been corrected. Page 45 of 54

46 continued Report Writer/Graphs Embedded Graph Border Report Writer reports that contained embedded graphs or images, converted to 2010 displaying a border (outline), whether the user had specifically created a border for the embedded object, or not. In , borders not initially set by the user are removed. Page 46 of 54

47 continued Graphs Auto Minimum Settings In User-Defined Graphs and Report Writer graphs, if the Auto Minimum option was set to No and Minimum was set to a value such as zero (in the Modify Graph properties panel), these selections were not saved. After leaving the graph and then returning to it, the properties of the graph in question incorrectly showed an Auto Minimum setting of Yes. In , changes to these settings are now properly saved. Page 47 of 54

48 continued Graphs Error when Graph Data Exceeded Min / Max Range If a graph was saved with custom minimum / maximum limits, on any axis, and the data upon which the graph was based violated this range, then entering the Modify Graph properties panel and attempting to adjust the Graph Axes Grid options resulted in an error. The message informed the user that the graph s minimum / maximum values were outside of the valid range, but the user was not allowed to access the necessary settings to make adjustments. This situation has been resolved. Graphs Growth Line Font Size Issue When the Draw Growth Line option is selected for a User-Defined Graph, the Graph Axes (Bottom Axis) Title Text Style Font setting is used to control the font, style, effects, and size used for the growth line s Growth % values. If a larger font size was selected, the Growth % values responded appropriately, but the line itself did not move up or down to adjust for the text size change. As a result, the line could be drawn across the text instead of being positioned below it. This behavior is fixed in Page 48 of 54

49 continued Graphs Selecting a Solid Color for a Graph Background If a user selected Graph Area Background Style Solid Color, in the Modify Graph properties panel, and chose one of the available colors, the color selection was not honored. (The Gradient setting was working correctly.) As part of the fix for this item, users will now choose Graph Area Background Style Pattern, and will then select the Solid pattern option. This selection process is consistent with the terminology and options used when users change the background color for a Title, Subtitle, or Legend. Graphs Editing Background and Appearance Options In prior 2010 versions, edits to Graph Items in all graph types (User- Defined, Report Writer, and Instant) were not saved for Patterns and Marks in the following situations: Patterns on Graph Items set to something other than solid or clear, changed back to solid, if the user modified the background color of the graph. Marks using a pattern, other than solid or clear, changed back to solid when the user saved the graph and then opened it again. Marks using a gradient style, set to Radial or From Center, changed to a different gradient direction upon saving the graph and opening it again. These options work correctly in the current version. Graphs Pie Graph Rotation Setting In version 2009 and earlier, if a user created a pie graph and then modified Pie Pie Setup Rotation, in the Modify Graph properties panel, the display of the graph would change. The change, however, was not saved as part of the graph. If the graph was re-opened, the graph would display as if the Rotation value was 0, but the modified, nonzero Rotation setting was still displayed in the properties panel. In the 2010 versions, the displayed pie graph will now properly honor the Rotation setting. Page 49 of 54

50 continued Graphs Changing Graphs to Display Fewer Bottom Axis Time Frames In version 2009 and earlier, when a User-Defined line or bar graph was created, time frames were selected, which were typically used to define the Bottom Axis. Users could subsequently modify the Graph Axes (Bottom Axis) Grid Scale settings, in the Modify Graph properties panel, to specify that a smaller number of time frames should be displayed. With the version 2010 release, the graph-rendering package that PROFITstar utilizes was upgraded. One of the results of this upgrade affected the method for defining a smaller sub-set of time frames to display in the graph axis. To accomplish this now, use the Time Frames option on the Graph Setup tab (when the Graph Axes (Bottom Axis) Grid Auto Minimum and Auto Maximum options are set to Yes). Page 50 of 54

51 continued All Output Sources Custom Header and Footer Overlap If custom headers or footers were defined and used in Report Wizard reports, Report Writer reports, or in Graphs, the header or footer information might overlap (or underlap) the data in the report or graph when it was previewed or printed. This behavior was most commonly observed when images or larger font sizes were used in headers or footers. Report Writer Example (Overlap) Multiple Graphing Group Example (Underlap) These issues with custom headers and graphs have been corrected. Corrected Report Writer Example Page 51 of 54