Enhancements & Revisions

Adagio Receivables 9.2A

June 25, 2015

·    Added new specification codes:
   M40 Company City, State/Province, Zip/Postal
   C92 State/Province, ZIP/Postal (formatted)

· Formatted addresses in customer and when converting from prior versions now support Puerto Rico and the US Virgin Islands: St. Thomas, St. Croix, and St. John.

· In Receivables 9.2A, if you previewed statements or letters and then printed them from the preview, there was an Access Violation error.

· Statement balances did not match the backdated Aged Trial Balance report for Balance Forward customers in some cases.

· Viewing a PDF of an invoice that was created by Adagio PDF and then appended with scanned documents caused the Adagio PDF Viewer to crash in some cases. This has been corrected. However, the Viewer may not show the scanned PDF correctly. This will be corrected in a future release. In the interim, the document can be open from your default PDF viewer by clicking the lower leftmost button on the Adagio Viewer.

· In Receivables 9.2A, Batch Listing reports sorted the accounts within an entry instead of in the order they were entered, which is how they were sorted in prior versions and how the drilldown to Transaction detail in the customer shows them. This has been corrected.

· In Receivables 9.2A, the Aged Trial Balance report did not print Adagio Time&Billing File/Docket descriptions.

· In Receivables 9.2A, some reports displayed an error similar to “Cannot open file "\DATA\ARxxnnnnR.DAT". The system cannot find the file specified.” on systems with many Windows users (approximately more than 100).

· The performance of the Customer Transactions report has been significantly improved when printed for a large number of transactions across a network.

· The Calculate Customer Aging function also calculates the customer statistics field 'Oldest Unpaid Invoice Date', which is the oldest invoice transaction with a non-zero balance. When the ‘Document Date’ aging option was used, the oldest invoice date was determined regardless of whether it had a zero balance or not.

· The G/L Account and G/L Department fields are validated when importing batches, similar to validation in batch entry. This prevents batches accidentally being imported and posted with blank GL accounts.

· After posting a cash batch in a MultiCurrency database, the Data Integrity Check reported an error indicating the computed home balance did not match the stored home balance for a transaction, when in fact there was no error. This was partially fixed in 9.2A and is now correct in all cases.

· After deleting an Alert for a customer in some cases, the Data Integrity Check reported an error indicating an Alert was missing a summary record, when in fact there was no error.