Release PV640 SV100

The theme of this release is integration of the Account Reconciliation and Transaction Matching solutions into OneStream Financial Close. Integration between solutions is optional and each solution can be used independently.

Prerequisites

  • OneStream strongly recommends uninstalling the UI for Account Reconciliations and Transaction Matching before installation.

  • If Account Reconciliations or Transaction Matching are currently installed, you must be on these versions to be able to install OneStream Financial Close:

    • Account Reconciliations PV 440 SV 200 or later

    • Transaction Matching PV 530 SV 201

Compatibility

Component

Description

OneStream 6.4.0 or later

Minimum OneStream Platform version required to install this version of OneStream Financial Close.
Microsoft SQL Server

One of these versions of Microsoft SQL Server is required:

  • Standard Edition 2016 SP1 or later

  • Enterprise Edition 2012 or later

New

OneStream Financial Close

Initial release of OneStream Financial Close.

Account Reconciliations

  • New columns are added to the Detail Items table:

    • Transaction Date (MP1-175)

    • Aging (MP1-52, MP1-181)

    • Reference 1 and Reference 2 (MP1-58)

  • An option in the Global Settings lets you enable integration with Transaction Matching. (MP1-379)

  • A control list for Aging Periods is available. (MP1-191)

  • On the Analysis tab, an Aging Pivot analysis report is available. (MP1-151)

Transaction Matching

  • From the Transactions page, you can create detail items for matched or unmatched transactions which can be sent directly to Account Reconciliations. (MP1-72, MP1-1800)

Changed

Account Reconciliations

  • On the Analysis tab, the Aging Detail tab is renamed to Reconciliation Exposure. The Unexplained Aging label is renamed to Unexplained Totals. (MP1-1794)

  • On the Analysis tab, the Reconciliation Detail analysis report is removed. (MP1-1793)

  • After you setup tables, the transaction date and aging features for previously created detail items are enabled as follows: (MP1-53)

    • The default transaction date is the last day of the current period.

    • Aging is automatically calculated based on the default transaction date.

    • When a prior period detail item is pulled forward, the transaction date that was created upon install will appear and cannot be edited.

  • You can delete selected or all detail items in the Detail Items grid. (MP1-162)

  • When a detail item is pulled forward, the aging is recalculated for the current workflow period end date. (MP1-172)

  • You cannot make changes to any detail items that have been pulled forward except for the Note field, regardless of Item Type. (MP1-1913, TFS: 11038)

  • After B and X items are created, Item Type, Item Name, Transaction Date, Reference 1 and Reference 2 cannot be changed. Only the Note field can be edited. If a Preparer wants to modify an item that was imported, then a new detail item needs to be created. (MP1-47)

  • When you run Process and the reconciliation status changes to Balance Changed, Frequency Changed, In Process, or Auto-Rec, the user displayed in Status and Approval History is "System." (MP1-104)

  • When creating a new detail item, Item Name cannot be blank. (MP1-1612)

  • Previously created detail items with a blank item name can be pulled forward but if you change any field on the item, you must add an item name to be able to save it. Also, to upload T-doc or S-docs, Item Name must not be blank. (MP1-1795)

  • For B-items, the detail Item Name is automatically set to the name of the BalCheck Workflow Profile and Balance Check Level associated with the reconciliation. (MP1-2114)

  • Transaction Date and Aging columns are added to these reports on the Analysis and Reporting tab: (MP1-25)

    • Reconciliation Detail

    • Reconciliation by Preparer

    • Reconciling Item Analysis

    • Reconciling Item Aging

  • Transaction Date, Ref 1, Ref 2, and Aging columns are added to the All Audit, Audit, and Reconciliation reports in the Reconciliation workspace. Reports can be changed to legal landscape format if needed to fit the columns. (MP1-145)

  • Transaction Date, Ref 1 and Ref 2 columns are added to these templates: (MP1-48)

    • Basic Template

    • MultiCurrency Template

    • Multi Period Template

    • MultiCurrency MultiPeriod Template

  • You can run Discover on multiple workflows simultaneously as long as the workflows are not related. (MP1-1770)

  • On the Reconciliations page and the Analysis and Reporting page, if you are an Admin, the default View Type is set to As Admin. If you do not have Admin rights, then View Type defaults to As User. Previously scheduled data management jobs may need to be updated if the user who scheduled the job does not have the proper entitlements to run as an Admin. (MP1-1947)

  • When creating a detail item, the transaction date defaults to the last day of the current workflow period. You can change the date to be any date from the current workflow period or a prior period. After you save the detail item, you cannot change the transaction date. (MP1-51)

  • In Reports, when Multi-Currency is not enabled, from Currency Level, you can select Translated to Reporting to show the reports in the reporting currency selected in Global Options. This change applies to these reports: (MP1-153)

    • Reconciliation Status

    • Reconciliation Detail

    • Reconciliation by Preparer

    • Reconciliation Risk Analysis

    • Reconciling Item Analysis

    • Reconciling Item Aging

  • In the Explorer Pivot under Analysis, new columns are added at the far right of the table for: Transaction Date, Aging, Reference 1, and Reference 2. (MP1-1654)

Transaction Matching

  • To see transaction details, select a transaction from a data set and then click on the corresponding Details button located at the bottom of the page. (MP1-56)

  • On the Matches page, the Date Range filter options are Today, 7 Days, and All. (MP1-1967)

  • On the Matches page, only matches for the current workflow period are displayed. (MP1-2064)

  • You can accept multiple suggested matches with one click. (MP1-1968)

  • When you select Unmatched transactions on the Transactions page, a Match Reason Code drop-down list is available in the bottom of the screen so you can select a reason code and then create a match. (MP1-2016)

  • To return fields that are blank, create a match set rule using the = operator and leave the value blank. To return fields that are not blank, create a match set rule using the <> operator and leave the value blank. (MP1-2139)

  • On the Matches page, OneStream Administrators can remove all matches for the current filter selections. (MP1-1971)

  • The Match Set ID is displayed in the Settings > Match Sets list and is used for integration with Account Reconciliations. (MP1-1893)

  • When you select Matched transactions on the Transactions page, you can filter the list by Match Reason Code, Match Period, and Import Period. (MP1-1799)

Fixed

Account Reconciliations

  • When items are pulled forward, the Booked Period remains the period the detail item was originally booked in. (MP1-515)

  • The RCM_SolutionHelper Business Rule runs properly when an account name uses an apostrophe. (MP1-502)

  • The Legacy auto rec rule runs successfully and R-Docs are pulled forward as expected. (MP1-1922)

  • When Account Reconciliations dashboard launches, SQL error for too many parameters does not occur. (MP1-1819)

  • In the Reconciliation Inventory, the Access Group filter defaults to All. (MP1-2136)

  • Performance improvements have been made to the Reconciliation grid. (MP1-1902)

Transaction Matching

  • When you install or open Transaction Matching, there are no errors and you can access the solution. (MP1-1807)

  • Substring() argument works properly when used in a matching rule. (MP1-2168)

  • When creating a match set rule, the filter tab displays a combo box in the Field Name column. (MP1-1816)

Known Issues

Account Reconciliations

  • Performing an Uninstall UI resets the Workspace Dashboard Name (Custom Workflow) in Account Rec Scenario > Workflow Settings to (Unassigned). This setting must be reassigned in the Workflow Profile by an Administrator. (MP1-700 )

  • In Reconciliation Inventory, when filtering the WF Profile and Account Group columns, users are unable to filter based on the textual name. This is because the grid is doing a lookup on those IDs since a GUID data type is used and a numeric entry is expected. Sorting is allowed. (MP1-586)

Transaction Matching

None

Contacting Support

Contact OneStream Support by registering at http://support.onestreamsoftware.com and then emailing support@onestreamsoftware.com.