Installs the AdagioPDF printer driver. All reports and printouts from Adagio can be printed to the AdagioPDF printer to create a PDF document in the data folder.
Supports the features in Adagio ePrint. When ePrint is installed you can print reports to PDF files in configurable folders determined by the Report Type (General, Transaction or Audit). Receipts print to a separate, configurable Forms folder. Fields can be embedded to establish the file and folder names (User, Session Date, System Date, Time). Click the ePrint button (red "EP" icon) on any report dialog to print the report to PDF. The Paperless Reports option forces all reports to be printed to PDF. Reports can be printed to PDF and attached to an email (MAPI) with a single button click.
Report Favorites allow saving Reports with specific options chosen. Click the Favorite button (a star icon) on any report dialog to create a Favorite. Favorites for a report can be accessed from the report dialog in a drop-down field. Private Favorites are yellow, Public Favorites are blue. Added Favorite Reports and Print/Delete Favorites functions to the Reports menu. Multiple favorites can be defined for the same report. Favorites can be private to the Adagio user or public for use by all users.
Report Sets allow the grouping of Report Favorites into a single print job that will run unattended. Report Sets may be printed to printer or PDF files. Report Sets may be launched from a command file or a scheduled Windows task by running brwin.exe with the parameter /R followed by the Report Set (ex. /RMonthEnd). A progress dialog lists the reports in the Report Set, the printing status of each, the destination folder, filename and conflict strategy. A log is generated that records the printing status of each report in the set. Use Report Sets to automate the printing of all your daily or month end reports.
BankRec supports the new 'Append by type' option for Payment Methods that will be added in Receivables 9.0C: Payment methods set to ‘Batch by date’ always created batches by date and by payment method. Now, if you have ‘Append to existing batch’, but do not have ‘Batch by date’, you can choose ‘Append by type’. This allows you to separate out the checks you deposit into two separate batches – checks drawn on the depositor’s (your) bank and checks drawn on other banks. It also allows you to separate checks and EFT payments of the same date for the same bank.
The Retrieve from Payroll function now allows you to retrieve reversed checks. The entry in the resulting retrieved batch will have a negative amount. If a negative amount exactly matches the check number and amount of an existing check record on file, that record will be marked as “Reversed” during the posting of the batch. Otherwise, the negative amount will be written to the reconciliation file. If the check that is being reversed had already been reconciled, the reversal is not matched. Note that retrieved batches cannot be edited.
Account Styles were added in Ledger 9.0D. They are now supported in GL account finder grids in BankRec.
On the Open database dialog you can now use Alt-B to open the browse and Alt-F (for Favorites) to open the previously opened list. In previous versions you had to use the mouse to select the folder buttons.
Alt-X now selects the Excel Direct button on grids where it is available. In previous versions you had to use the mouse to select Excel Direct.
The vitalEsafe upload progress dialog has been improved and the progress bar now accurately shows the percentage. It is no longer necessary to install the vitalEsafe patch.
New program icon and toolbar buttons provide a cleaner look and differentiate this new version visually.
Problems Fixed
If a filter is based on a range for any field that is right-justified (such as customer number, single segment item number, vendor number, etc.) then additional records will be selected by the search that should not have been. For example, if the range is from 1 to 2, then not only would records 1 and 2 be selected, but also 10, 11, 100, 101 etc.
A Cash Invoice payment for a tax only AP Distribution generated an extra G/L transaction to the tax payable account for zero dollars.
When converting to BankRec 8.1C the conversion message indicated that the new version would be 9.0A (rather than 8.1C). The message now says 8.1D.
In BankRec 8.1C, the Date for Receipts transactions in a Deposit Only batch changed to the batch date when the entry was saved.
The Find did not work correctly for selecting a customer with a leading zero in the Name field, such as for a numbered company. As result a receipt transaction could not be created for the customer.
The date for the reversing entry generated for the originating bank when using the 'Automatic transfer on posting' feature (typically used for EFT) was set to the session date. The date is now set to the highest date found in transactions in the batch. Deposit batches will use the Deposit date.
If your Ledger data was created with version 9.0x and you never used Ledger 8.1A or earlier versions, after printing the G/L Transactions report in BankRec, the Consolidate G/L Transactions dialog did not show the 2 options to consolidate by Fiscal Period.
The Create Batch function in Reconcile Bank creates batch entries where the Reference contains a hyphen. For example "ER110628-3" (which stands for Electronic Reconciliation, transaction date in YYMMDD format, dash, 3rd entry in the batch). If 'Alphanumeric manual check numbers?' was off in the Payables company profile, you got the error "The check number is invalid" if you edited an entry and saved it. A hyphen is now ignored in all cases.
There were errors when opening DataCare if you used BankRec but did not have Receivables.
When importing a Detail Only deposit batch, if consecutive records had the same Check Number they were consolidated into a single entry in some cases, depending on whether other fields were imported and the values in those fields. The behavior changed in 8.1C from earlier versions and in some cases was not desired behavior. The import now determines a break between entries using the following logic. If Entry Number is imported it signals the change of entry, else if Bank Reference is imported it signals the break, else if Check Number is imported it signals the break, else Customer Number signals the break.
When a new Bank was created in BankRec, with a Last Statement Balance as of the Last Statement Date, when the Bank Reconciliation report was run as at the Last Statement Date it showed an incorrect balance and Last Statement Date.
BankRec 8.1C did not print transaction reports with correct Region/Language settings for French (Canada).
When batches or entries were copied or moved to an existing batch that had a status of 'Printed' the status of that batch was not changed to 'Open'.
BankRec suppressed "Canada" in the address print on Receipts if the Home Country in the Receivables Company Profile was "USA" and the 'Suppress home country on forms' option was selected. It also suppressed "USA" if the Home Country was "Canada". The fields from the Customer
The Bank Reconciliation report as of a prior date correctly calculates the 'Cash Balance' and 'Report balance' when Reversals are present.
When entries are copied into a printed batch, the print status should change on batch copied.
The statement file for BMO Bank of Montreal could not be imported until the dollar symbol $ was deleted from amount fields by manually editing the file. The import now handles this. However, the final 'T' record at the end of the file must still be deleted manually. This file is a non-standard structure, using variant record formats, which cannot be by the Adagio import object at this time.
BankRec 8.1C was updated from version 7 to version 8.5 of the Crystal Reports print engine. When installing Adagio for use with Remote Desktop Services (Terminal Services in Windows Server 2008 and previous versions), this necessitated manually copying the crystal folder from the main windows folder to the windows under each user. For example, on Server 2003 you had to copy the crystal folder from C:\windows\ to C:\Documents and Settings\username\windows. This is no longer required. The install and workstation installs will do the copy. The BankRec program will also do the copy if possible, which will avoid the need to do a workstation install in some cases.
When installing Adagio to a computer or server where no Adagio modules had previously been installed, if you installed an Adagio module that does not use the Crystal print engine first (such as Lanpak or GridView), when you installed BankRec you received the error "Adagio has been established on destination folder: [x:\SOFTRAK]. Yet the install cannot detect the corresponding Reports Tables..." and were unable to proceed. If the first module installed uses the Crystal print engine there was no problem.
The install (full/upgrade, NFR, Evaluation and Service Pack) no longer allows you to proceed if other users have Adagio programs running. This was previously allowed to avoid having to get all users to exit Adagio before installing, in cases where you knew the files that could not be updated because they were open by other users had in fact already been updated. However, in practice it was found this caused problems because sites proceeded with the install when they should not have.
The updated version of vitalEsafe no longer triggers a workstation install if it has already been installed by the workstation install for another Adagio module. This is also the case when installing Adagio for use with Remote Desktop Services (Terminal Services in Windows Server 2008 and previous versions).
When running any Adagio module that installs vitalEsafe (or WebSafe as it was previously known as) on a Windows 7 (or Vista) station, in some cases the auto-workstation install ran every time you started the application, even if you had done a workstation install. This happened if the user was not an Administrator on their own machine (the default for a new computer) but rather a Standard user, and User Account Control (UAC) was on, and you had not installed any module with a release date of October 2011 or later and done a workstation install for it on the station. This has been resolved. To resolve this problem for ALL other modules, install any module with a release date of October 2011 or later and do a workstation install for it on the station.