Do NOT uninstall your old version
Contact Treasury Software for licensing information prior to performing the steps below, as your existing license codes may not work with the new software.
Note: If you are upgrading one workstation then you should upgrade every workstation so that they are using the same version of the Treasury Software.
Please print these instructions prior to continuing.
Clear out any open transactions.
If using ACH Universal or Bank Positive Pay, first create output files for any untransmitted records. Exit the software.
Backup the databases per your corporate procedures.
Decide on a workstation to work from and confirm administrator credentials.
a. From this workstation you will be updating databases on the SQL Server.
We recommend that you use a non-production workstation, such as a machine from the IT department, from which you can use your sa rights.
If you do not have a non-production workstation available, then at the user's workstation, either:
--login into Windows on their machine as an administrator (your Windows login ID), or
--you'll use the sa password (will be entered later in this checklist).
Do not temporarily elevate a user's rights for this check list.
b. Confirm the SQL Server security model if you will be using the 'sa' password.
If you will be using an 'sa' password, confirm that your SQL Server is set to Mixed Mode Authentication (both SQL Server and Windows Authentication).
Confirm using SQL Server Management Studio, right click on the server, select properties, then Security:
Download and install the latest version of Treasury Software from the link below.
Start the software.
From the 'Welcome New User' screen, select the application you are using (ACH, Bank Reconciliation or Positive Pay).
Migrate to SQL Server
From the top menu select the 'Settings' tab > 'Migrate to SQL Express, SQL Server'.
Note: If you are using a version prior to 2013. From the main menu select 'File', 'Migrate to SQL'.
Point to the SQL Server in the drop down list.
If you don't see your server listed, you can type it directly into the box.
Tip - If there is an instance of SQL Server - don't forget it.
Example: If the instance was Accounting on Server7, it would be displayed as Server7\Accounting
Note: If you are unsure as to the exact server name, go to another workstation (or the older version - see below) that has Treasury Software up and running. Enter into an account. From within the software click on the Settings tab > Maintenance > 'SQL' tab. This will display the server name.
Enter in your SA credentials
IMPORTANT - Do NOT use a user level login ID as you will need the SA rights to enable the software to update the database structure in the steps below.
If you are using Windows Authentication - leave the id and password blank.
Otherwise, enter the 'sa' (or similar) id and password.
Click either 'Test Login ID' or 'Next' to complete the wizard.
The software will prompt you to exit and re-enter. Please do so.
When you re-enter, select the application you are using (ACH, Bank Reconciliation or Positive Pay) from the Welcome New Users Screen.
Note: Upon reentering the software, the system will prompt you to update the 'Sample' account to the current version. Follow the prompts and allow it to do so.
Add other accounts as appropriate - and update.
From the main menu select 'File' > 'New Account' > 'Add an Existing Account'. Select all the accounts that need to be updated.
Enter into each account to initialise it, by selecting from the main menu 'File' then select the account.
Note: If you are using a version prior to 2013, select 'File' > 'Open'.
a. Based on your original version, you may get a message warning(s). If so, simply click ok on any warning(s). To clear any future warnings simply open and then close the Options window. Do this by selecting from the main menu File > Options > General, and then closing the window.
Allow the software to update the account(s) when prompted.
Using a Global list of accounts?
While not common (only used for over 100 accounts) - see if you are using a 'Global' list of accounts.
--If so - enter into the Sample account.
--From the top menu select the 'Settings' tab > 'Import, System' tab > 'System' tab > 'Suppress Automation - Global Batch Process Menu' turn to 'Display'.
Note: If you are using a version prior to 2013 version. From the main menu select 'File' > 'Option's > 'System' tab > 'Suppress Automation - Global Batch Process Menu' turn to 'Display'. Exit and re-enter into the account.
--From the main menu select Automation > Global > click at the bottom 'Utilities to add/create' > click the 2nd button 'Auto-populate your local machine from the Global list'. Close the window when complete.
--Enter into one of the accounts to trigger the upgrade process.
b. Confirm that each account is set up for the correct program (ACH Universal, Positive Pay or Bank Reconciliation).
From the main menu select 'File' > 'Maintenance' > 'Switch Programs' tab to display the following. Update as needed, then click 'Continue'.
Note: The default checkbox is only significant when a user starts Treasury Software, but does not yet enter into an account.
Tip: If you have multiple accounts to confirm/update, you do not need to exit the software after each update. You can simply exit and re-enter after all of the accounts are done.
Required account maintenance - repeat for each account
Enter into an account. From the main menu select 'File' > 'Maintenance' > 'SQL' tab > 'Stored Procedures sub-tab and click on 'Service Pack Update'.
If the account is used in Bank Reconciliation - with the Maintenance window still open, select the last tab on the right, 'Other' and click on 'Update Reconciliation Statement Codes'.
Repeat the above step(s) for each account that you have upgraded.
Remove the SA login ID and password
If you are on a non-production machine (such as IT machine), you can skip this step if it is in compliance with your corporate policies.
Otherwise, if you have been performing these steps from a user's machine - you should remove your SA login ID at this point.
From the top menu select the 'Settings' tab > 'Maintenance' > 'SQL' tab and enter the user's ID and password. Click 'Update'.
Note: If you are using a version prior to 2013. Select 'File' > 'Maintenance' > 'SQL' tab and enter the user's ID and password. Click 'Update'.
Enter license and custom codes.
License - From the main menu select 'File', 'Enter License Codes'. Enter the codes and click 'Register'.
If you need a new license - contact licensing with your company name, phone number, email address and license ID (typically the main phone number). Ask for an upgrade coupon for the on-line store.
If you do not have your license information, you can find it on the old version (September 2007 and later). Using Windows Explorer, open c:\Program Files\Treasury Software\Treasury Desktop\TreasurySoftwareLicense.txt.
Install the new version of Treasury Software on the primary user's workstation.
Follow the directions to install the software at the primary user's workstation by following the check list at:
Tip: As this is an existing user, you may be able to skip the first section of the check list regarding SQL Server Management Studio.
Reminder - do NOT uninstall the older version.
Do NOT uninstall the older version. Uninstalling the older version will corrupt the new installation.
Once your primary user has confirmed the upgrade, repeat the above step for each user.
Note. Concurrent use of both versions - reminder - both versions are using the same database
Starting with version 2010 - you can run both the old and the new versions simultaneously.
Reminder: Both versions are pointing to the same database.
To access the older version, we recommend creating a shortcut to c:\Program Files(x86)\Treasury Software\Treasury Desktop\BRCOM.exe.
To create a shortcut:
--Open Windows Explorer and navigate to c:\Program Files(x86)\Treasury Software\BRCOM.exe
Right click on BRCOM.exe, select 'Send To', then 'Desktop (Create shortcut)'.
The #1 issue in any upgrade is security.
--Make sure that you have a system administrator login ID before starting
--Create/arrange for logins for all users
--don't rollout to the users until you have fully tested the new system.
2400 Old Brick Rd
Glen Allen, VA 23060
All submissions answered same day*