Given that there have been significant changes to budgets structures careful consideration need to be given when upgrading. This section is divided into two sections
- Automatic upgrade – this describes the automatic migration of your configuration
- Manual steps – these describe manual configuration steps that may be required
UPGRADING TO FINANCE V2.0
The Finance functionality designed in this guide is described within release notes as Finance V2.0 and is a mandatory upgrade for this release.
Within the new Chart of Accounts feature you will find a dedicated screen to assist you in this process. This is accessed from the front screen of the Chart of Accounts feature via the following widget
Upon clicking the configuration cog you will be presented with the following screen.
This screen will perform the following upgrade steps.
UPGRADE |
STEPS |
Chart of Accounts |
In Finance V1.0 you will have most likely configured a set of Reserve codes for defining your budgets. During the upgrade, the system will convert these into Chart of Account Segments and Values. Since the new Chart of Accounts relies on these codes being unique it will apply some logic to these existing values to derive unique codes for all “old” reserve values. Since these codes are presented to end users as quick “short cuts” when entering transactions, you may wish to review and if necessary, change these codes following the upgrade. |
Invoice Phase Features |
Legacy phase features that were used to configure Invoices will be migrated to settings on the new Invoice Aspects. |
Payment Phase Features |
Legacy phase features that were used to configure Payments will be migrated to settings on the new Payment Aspects. |
Settlement Outcome Options |
In Finance V1.0 Different budgets views were used for Reserves/Awards and Settlements. This has changed to use a new Budget Phase Model where “Settlement” is considered to be a phase of a budget. As part of this upgrade, you existing configuration for Settlement Reasons will be migrated to the relevant Budget Phase plan. |
Budget Configuration |
Your existing configuration for Reserves/Awards will be migrated to the new Budget Configuration Model. |
Invoice Transactions |
In Finance V2.0 we have introduced a new transaction and posting model. As part of your upgrade your existing transactions for Invoices will be migrated to this model. |
Payment Request Transactions |
In Finance V2.0 we have introduced a new transaction and posting model. As part of your upgrade your existing transactions for Payments will be migrated to this model. |
Invoice Receipts |
In Finance V1.0 invoice receipts were recorded directly against the invoice. This model has changed fundamentally in Finance V2 with invoice payments being able to be captured and then allocated across multiple invoices. Invoice Payments are managed by a new transaction work type and your existing invoice receipts will be migrated to this new work type. |
Reserve Transactions |
You existing audit of reserve transactions will be moved to the new model for budget transactions. |
AUTOMATIC UPGRADE
When the system upgrades your configuration, it will perform the following steps
- Reserve Types, Reserve Categories, Reserve Accounts and Head of Loss Categories (from Finance v1) will be migrated to Finance v2 Chart of Accounts segment codes with the relevant hierarchy.
MANUAL UPGRADE
When the system upgrades your configuration, it will perform the following steps
- Via a manual running of the Finance V2 Migration pipeline (a one-time administrator action) the following updates will be made to the system: -
-
Configuration Migrations
- Migrated chart of accounts codes are the deduplicated to ensure that a chart of accounts “code” property is unique for a given segment.
- For example, Finance v2 does not permit two segment codes with a code definition of “CO” (using “Costs Own” as an example for illustration). In this scenario, the second instance of the code will be automatically renamed as “CO.1”.
- Invoice and Payment Request Features are migrated to Chart of Accounts Work Type Configurations with the appropriate Phase level settings preserved from their Finance v1 counterparts.
- Account Code Combinations are created for financial work types which previously had reserve type restrictions in Finance v1
- Settlement Outcome Options are migrated to the relevant Budget Settlement Outcome Reasons option sets (one for Positive and one for Negative outcomes).
- Budgets and associated Budget Configurations are migrated from the existing Finance v1 Reserve Account settings. This migration comprises: -
- Addition of a new budget structure for each unique reserve account / head of loss category combination
- Creation of Budget Structure Position Types from the Reserve Account “Display Settings” property.
- Creation of Budget Structure Segment Values from the Reserve Account “Display Settings” property.
- Creation of Budgets Work Type Configuration records from the existing reserve – work type associations.
- Migration of Finance v1 “Settlement” records to a Budget Structure with the appropriate “Settled” phase.
- Migrated chart of accounts codes are the deduplicated to ensure that a chart of accounts “code” property is unique for a given segment.
-
Data Migrations
- Invoice Transactions are migrated to the Chart of Accounts model with appropriate matching to the relevant codes via the existing reserve types.
- Payment Request Transactions are migrated to the Chart of Accounts model with appropriate matching to the relevant codes via the existing reserve types.
- Invoice Receipts are migrated to the new Invoice Payments work type, with associated Invoice Payment Transactions, which are again matched to the relevant codes via the existing reserve types.
- Reserve Transactions are migrated to Budget Transactions, where the positions and mapped to the appropriate budget structure position types and reserve types are mapped to the relevant Chart of Accounts codes.
-
Portal Updates
- Given the wealth of new portal widgets and configurability available in Finance v2, it is likely that work type portals will need to be reviewed to ensure the best view of Finance data is available to users.
-
Execution Engine Plans
- Although existing commands surrounding “reserves” and “settlements” have been updated to utilise the new Budgets framework, it is likely that some of the specific reserve account – budget structure configuration will need to be reviewed to ensure the correct budget structures are managed during action plan processes.
-
Configuration Migrations