• Payables has been updated to send additional information to JobCost 9.3A including Doc Link and Accounting Date.

• For JobCost 93A: the Company Profile, Integration tab has an additional Send to A/J desc. 2 field. 

• When Manual Checks Batches were imported, Payee Addresses were not being defaulted properly from the vendor.

• If 'North American Address?' is selected, the states for Mexico will be normalized to the 2 character state. 

• If the Company Profile is set to use “North American Address?, Import Vendors and Manual Checks will validate State/Province. If Country is imported, it will also be validated.

• The Country list that will be normalized when 'North American Address?' is selected has been expanded to include more countries.

A new option has been added to the Company Profile, System Options tab to work with ‘North American Address?’: ‘Normalize Country To’. The options are: Full name, 2 character ISO, 3 character ISO and Never. For Import or Edit for Vendors, Banks or Manual Checks, if the Country is recognized, variations on Country codes are standardized based on this setting.

Eg. For the Default setting: Full name, CA or CAN become Canada.

• With the Payables (230922) Hot Fix, the Company Profile report could not be printed.

• Export Invoice Batches has been added. Please note: the format is for a ‘Header fields on each record?' Batch import format.

Hdr-Application is no longer available in Import Invoices. 

• Payables has been updated to send additional information to JobCost 9.3A including Doc Link, Accounting Date and Entry Description Line 2.

• Updated Vendor comment lines were not printing on Additional Forms printed from System Check Runs Inquiry.

• For EFT batch format ‘RBC 152 format US ACH’, the Optional Record Indicator has been changed from N to Y in the Basic Payment Record.

 • When ‘Remember Batch Entry’ was selected in User Preferences and the vendor record did not have a default ‘Invoice Description’, multiple entries for the same vendor did not always default the description from the previous Manual Check entry.

Please note: for Miscellaneous vendor Cash Invoices, the default Description from the Company Profile will only default if ‘Remember Batch Entry’ is not selected.

• Emailing Letters was using the Vendor email address from the first vendor for all the vendors.

• The 9.3C (2023.06.12) Hot Fix had errors in Batch Entry for Detail type: Job cost, entries. This error appeared: Error Internal Error: field [87] of [KJ92AJOB] is not a string field, occurred when attempting to read record from jobs.

• The EFT batch format for Royal Bank ACH094 PDS for IAT records needed an adjustment for the Foreign Exchange Reference Ind field.

• In a Project related batch entry, if a distribution did not have an account with ‘Project tracking?’ selected, and the next distribution was for an account with ‘Project tracking?’ selected, the tab did not stop at the Project field, in some cases.

• The EFT format RBC ACH094 Credit PDS has been updated. The File ID Modifier is no longer blank. 

• In View/Edit Vendors, Transaction tab, if the mouse was dragged while viewing/selecting transactions, the cursor changed to show that the action is prohibited.

• Copying entries from Archived Invoices or Archived Manual Check Batches caused an “Orphan open document” Data Integrity error, in some cases. 

• For Cash Invoices, the ‘Invoice’ date was not validated against the Fiscal calendar when the Company Profile option for ‘Validate Closed Periods’ was set to ‘Disallow’.

• When the Smart Finder was used on a Filtered list of vendors, there was an error: ‘Internal Error: field number is out of range.

• The Payables 9.3C (23.03.15) HF has been  updated to correct the Account number field for the Caribbean EFT formats: BOSVG (CSV) and ECAB ACH (CSV).

• For the Caribbean, a ECAB ACH (CSV) EFT Batch Format has been added to the list of EFT Batch Formats

• For the Caribbean, a BOSVG (CSV) EFT Batch Format has been added to the list of EFT Batch Formats. The format is for: Bank of St. Vincent & the Grenadines Ltd.

Notes:

For the Vendor, on the Accounting tab, the first 9 characters of the Bank ID field are the Routing Number. The rest of the Bank ID is used as Account Number.

Account Type comes from the Vendor’s EFT tab. Set the Vendor's 'EFT Bank Acct Type.

• Multiple email addresses separated by semi-colons could not be imported for Vendors.

• If ‘EFT enabled?’ is set in the Company Profile, the options for a System Check run have been updated. Vendors can be selected based on the setting for ‘Enable EFT’. The options are EFT, Non-EFT or All.  If Non-EFT or All are selected for a Bank that has an EFT code, Checks will be printed.

• It is no longer possible to Print Manual Checks from the Manual Check Batches List while the Batch is open.  After printing the Manual Checks, the batch could be posted, causing Access violations and other errors.

· The CIBC ACH 094 EFT format needed corrections to the:

Fifth mandatory addenda record (7).

File Header Record and Batch Control Record to change the ‘Service Class Code’ to ‘200 – Mixed Debits & Credits’.

· A new specification code has been for: G17, G/L department.

· Crystal Reports used in printing Adagio Reports was not fully compatible with the Windows 22H2 update for Windows 11 and for Windows 10, in some cases.

·          With Payables 9.3C (2022.06.07) HF, creating a new EFT Provider using EFT Batch Format Peoples Bank-Greensboro USD ACH (AL) was causing an error message: Cannot focus a disabled or invisible window.

·          In Import Batches, if the file layout did not match the import template, an Access Violation appeared before the message that the file layout is incorrect.

·          Using Range in Payment Control to change the Document Status was causing Data Integrity errors.

·          Advice Email and Advice Contact have been added as fields for Email Cover Sheets.

·          A CIBC NACHA 94 IAT EFT Provider has been added for the CIBC NACHA IAT 94 byte file layout (CMO only) Format Specification.

Please note: If this format is used, these related fields on the Vendor's EFT tab must be updated:

Transaction Type (22-Checking Account or 32-Savings Account).

US trans. code

Optional EFT string (Vendor's Bank Name for Addenda 5).

·          A Wells Fargo US ACH EFT Provider has been added for the CSV file specification for the DAC payment type. CCD and PPD Standard Entry Classes are supported for USD payments.

·          In Automation, the SetSessionDate command has a new noun for: Yesterday.

·          A Peoples Bank-Greensboro AL USD ACH094 EFT Provider has been added for the NACHA Format Specification. CCD and PPD Standard Entry Classes are supported.

·         For Automation and the Post command for Manual Check Batches, a new Modifier has been added for Retrieved Check Batches.

If a vendor was edited that had detailed Notes, and then immediately afterward a new vendor was created, the notes from the previous vendor were incorrectly carried over to the new vendor.

Invoices marked forced in invoice entry were not updating the Total Forced or Total On Hold amounts in the vendor statistics during posting resulting in a Data integrity errors. The Total Forced and Total On Hold amounts are only a statistic inn the vendor information, so this is did not cause any data corruption.

If an invoice was setup with maximum payment equal to the invoice amount, and that invoice was to be paid in full by a system check run, and then the maximum payment was set to zero, and the system check run posted, a Data integrity error was caused because the Reserved payment total on that invoice was not updated correctly. 

When the company profile option Uppercase Document Number was enabled, invoice batch entry would not immediately recognize duplicate invoice numbers if the vendor number was typed in and then the user clicked into the Document field.

When viewing a Vendor and on the Transactions tab with an active Grid Search, clicking the Preview or Next buttons did not refresh the grid for the next vendor. Now the Grid Search is removed and the correct transactions are displayed.

Import invoices was not checking for invoice duplicates in the vendor transaction file. This verification was added. Import cash invoices was not checking for duplicate cash invoice numbers in the vendor transaction file. This verification was added.

Deleting a filter record from the Filter List failed if the grid was sorted by Priority or if the grid was sorted by description and the Show filters option was set to All

Vendor edit was requiring a nonblank ID number when the Company profile option 1099 Express Integration was turned on. This requirement was removed.

Using Crystal Reports to add new tables or sub-reports to a report could cause an error 'Failed to open the connection' due to a change in how Crystal runtime SP 25 loads tables.

Update PDF Viewer for issues with some PDF’s not displaying correctly.

·        Importing Invoice entries for vendors with default projects was not using the project from the import file.

·        If multiple non-consecutive batch numbers are selected in Batch Status Inquiry that have consecutive posting sequences, the Print PJ button is now active and builds the posting sequence range. Previously the posting journal report screen required editing to the desired range.

·        Posting an unapplied credit note or debit note with either Payment Control status of Forced or On Hold selected would not calculate the vendor total correctly and cause a data integrity error.

·        When Blank Check Stock was printed, the printing confirmation message incorrectly referred to the Park button that is not available for this function.

·        If the Check Reconciliation Report was printed with the Option to 'Print Descriptions', the Description field did not print properly.

·        When importing invoices that have a distribution code with a default Ledger Project Code defined, a false verification error would appear if the Project field was imported and blank for this detail. This has been fixed, and the default project from the code is correctly used.

Problems Fixed

·    When copying invoice or cash invoice batch entries, the detail descriptions were changed to the header description value.  Now, when copying these batch entries, the detail descriptions will be unchanged unless the vendor is configured with auto-generated Invoice Descriptions, in which case, these values will override both header and detail descriptions on the new invoice.

·    In Email Cover sheets, Vendor data fields were not expanding properly.

·    In Edit Distribution Sets, the Default amount field was not editable in some cases.

§   %usr - for User ID

§   %unm - for User name

§   %sdt - for Session Date

§   %syr - for Session Year

§   %smh - for Session Month

§   %sdy - for Session Day

§   %dat - for Actual Date

§   %tim - for Actual Time

§   %bat - for Batch Number

Edit

·    Additional contact information for Cell Phone and Toll Free Phone numbers have been added to Edit Vendors, Import/Export Vendors, and the Vendor List and Statistics report.

·    Project codes created in Adagio Ledger can be assigned as default values to Distribution Codes and Distribution Set details.

·    Distribution Sets that use 'Auto-distribute?' may have distributions with blank Account/Departments. When the Distribution Set is added to an Invoice entry, the Vendor's Default Acct/Dept will be used. If the Vendor's Default Acct/Dept has been left blank, the Distribution Set Details will be added to the Invoice Batch entry with the blank Acct/Dept. The entry cannot be saved until the Invoice Detail has been updated.

Designer

·    Check specification codes for new Vendor fields: V95 Cell Phone V96 Toll Free Phone

·    New specification code for Payments that are Cash Invoices: G16 for Project name 2

System Check Runs

·    The Vendor Summary grid within System Check Runs on the Payments tab now has a new Net Issued column that can be added. This value will display 0.00 if a check will not be printed for the vendor, if the Net Payment amount is negative or outside the specified Vendor Payment range to match with the Pre-check Register report results.

·    The Net Issued value for System Check Runs, calculated from the Pre-check Register report, is now also displayed on the Payments tab in addition to the Selection/Status tab. This makes it easier to see what the total check run amount will be when selected vendors have negative outstanding balances.

DocStore

·    When using Adagio DocStore, printing the Pre-check Register report now correctly uses the %CDT code in eP Options to translate the Check Date of the System Check Run as part of either the PDF file name or save folder. Previously it was using the sign-on date.

Reports

·    Printing reports is now logged in the application log, in addition to accessing the print report screen from the menu.

·    For vendors that have been set up to track either 1099 or T5018 payments, a new statistic for Last Year payments is now accumulated in addition to Current and Next year amounts.

·    When integrated with Adagio DocStore, the Email Queue Listing report now supports all the Print to PDF features.

·    The Tax Tracking report now has floating date range options for This Month and Last Month, that can be used as part of Favourite Report settings and printing the report unattended from report sets. There is another new option to suppress records that have zero tax amounts, printing only transactions with tax.

·    When a report is printed and the data file either purged or consolidated, a record of this action is now saved in the Application Log.

EFT

·    For Telpay EFT and Conversion to Payables 93C, conversion will strip the dashes out of the 'Bank ID' on the Vendor's Accounting tab. In previous versions of Payables, the dashes were required. If the 'Bank ID' is not blank, it will be displayed on the EFT tab as the 'Bank account' formatted with dashes. If the 'Telpay EFT only?' option is set on the EFT tab, the 'Bank ID' may be left blank. System Check runs also recognize the 'Telpay EFT only?' option. If the 'EFT code' for the Bank is not set to use 'Telpay format' for the 'EFT batch format', then vendors which have 'Telpay EFT only?' selected are skipped when 'Select Vendors' is set to EFT.

·    A CIBC 1464 format USD EFT Provider has been added for the CIBC EFT 1464 Byte File Layout. The Currency Identifier is USD for US dollars.

·    An RBC ACH094 Credit PDS EFT Provider has been added for the Royal Bank ACH094 Credit File Format Specification. Please note: If this format is used, the related fields on the Vendor's EFT tab must be updated: Transaction Type, Bank Dest. Country.

·    An RBC 152 format US ACH EFT Provider has been added for the Royal Bank ACH Direct Deposits (PDS) Service, RBC Standard 152 STD Credit File Format Specification. Please note: If this format is used, the related fields on the Vendor's EFT tab must be updated: Transaction Type, Bank Dest. Country, US Trans. Code and Company Entry Desc.

·    System Check Runs now have the EFT vendor selection option extended for a new choice to generate payments for vendors that do not have EFT processing enabled. This provides a clearer division for paying some vendors by EFT and others with printed checks.

·    A VanCity 1464 format USD EFT Provider has been added for the VanCity EFT 1464 byte file layout.  The Currency Identifier is USD for US dollars.

·    If Vendors were updated by importing changes for enabling and setting up access to TelPay and the EFT Country field was not included, that field would be blank on vendors and caused TelPay EFT to not work correctly. Data integrity check detects this condition and Rebuild will insert the correct value when missing.

·    EFT: for CIBC First Caribbean CSV files, if 'Include Reference' is selected and the 'Check Number' is being sent, the check number will have the first dash trimmed to fit the 10 character Reference field. In the file, the Check Number will now be: EFT{sequence}-{check number}.

·    For the Caribbean, an RBC Royal Bank (Barbados) CSV EFT Batch Format has been added to the list of EFT Batch Formats. It is for Direct Payments in CSV format for the RBC Royal Bank (Barbados) Limited.

Notes: For the Vendor, on the Accounting tab, the first 3 characters of the Bank ID field are the Bank Code. The next 5 characters are the Branch Code. The rest of the Bank ID is the Destination/Customer Acct #.

Controls-Grids

·    When a grid that supports the Grid Search feature has focus, a hint will appear at the left in the Status bar to indicate that the Ctrl-F keyboard shortcut can be used to open the search, and the Ctrl-Z shortcut for removing the last search level. When the mouse is used within the Grid search window to click an arrow button and change the column, the cursor will remain anchored on the clicked arrow to make it easier to move multiple columns over.

Import/Export

·    Importing Invoices now allows setting the Control Payment Status of Forced, On Hold or Normal as long as security rights to Control Payments is granted.

·    When Optional Fields are defined for either Vendors or Batches, the field titles now display in Import and Export template field lists, rather than a generic Optional Text 1 or similar label. This will make using optional fields easier to use.

·    When Editing properties for Text-type Optional Fields, a new Import button is now available to populate the list of possible values for this field. Only one-column Excel sheets without a header row are supported,

·    Import Vendors has new EFT related fields:

Telpay EFT only?

EFT account type/Bank Acct Type (Savings or Checking),

EFT Bank country code/vendor EFT tab Bank Dest. Country (USA or CAN)

EFT Company entry desc

Also, for non EFT methods, the Telpay EFT validation email has been renamed: EFT validation emails. If this field is non-blank, it will be used. If it is left blank, Emailing EFT advices will use the Advice email or the Contact email.

·    In Import Manual Checks, Hdr-Addr. Remittance Note will default from the Vendor's record if it is not imported.

·    Vendor Notes can now be Imported and Exported in the same way as Customer Notes in Adagio Receivables.

Inquiry

·    The GL Disbursement file now stores the second Description field that gets sent to the GL Retrieval batch, for use when inquiring on vendor transactions.

File 1099 Express Forms

·    Payables now has integration with 1099 Express for paperless e-filing to the IRS for NEC and MISC 1099s. If this Company Profile option is selected, the 1099 form types that have been assigned to Vendors should be updated to set the 1099 Express Options. There is a new function on the Maintenance menu to File 1099 Express Forms.

·    In Payables 9.3B, a new feature was added to allow sorting printed checks by various methods. A new sort option for Entry Number has been added in AP9.3C when printing checks from a Manual Check batch. It allows printing checks in the same order as in versions prior to 9.3B.

Posting

·    When integrated with Adagio JobCost, posting a transaction with a job detail now writes the job, phase and category values to the GL Disbursement data file. This information can be added to the grid within vendor transaction inquiry for GL distribution lookup.

·    When integrated with Adagio BankRec, posting manual check batches writes the Reference, 2nd Description and Batch Optional Fields to the batch retrieved into BankRec.

·    When Adagio BankRec is integrated and is at version 9.3A or higher, posting manual checks now writes the AP Reference, second Description and batch optional fields to the batch entries retrieved into BankRec.

Problems Fixed

·    Fixed a problem where, if a transaction entry amount was greater than 0.00 and the Distribution code it used was changed, the transaction entry amount would be changed also. Note that, if the transaction entry amount is 0.00 and the Distribution code is changed to one having a default amount of greater than 0.00, the transaction entry amount will be changed to be that of the Distribution code selected.

·    In Invoice Batch Entry, 'Auto-Distribute' was not setting the Tax Base to 0.00 in Invoice Details that were not Tax related.

·    Adjustments that affected retainage could be entered and posted without an Original document number. Batch Entry has been updated so that an Adjustment that updates Retainage can no longer be saved without an Adjusted document number.

·    Adding Manual Check Payment Entry, the new entry did not have cursor in the Vendor code field in some cases.

·    In Adjustment batch entry with MultiCurrency enabled, selecting a source currency vendor would not immediately populate the Exchange Rate value until an Adjusted Document number was selected. Now the current rate is initially loaded if the adjustment won't be applied, and replaced if an Adjusted Doc number is chosen.

·    Entry templates for Manual Check batch entry were not correctly hiding the Invoice Date field for cash invoices.

·    The Integrity errors \\\"Error: Payments have been over applied to Vendor nnnnnn document nnnnnn\\\" caused by changing the Vendor code on an existing Manual Check batch Payment entry won’t occur.

·    Manual Check Batch Payments can no longer be applied to Invoices if the Max payment is 0.00. System Check runs or other Manual Checks in progress may have set the Max Payment to 0. If the Max payment is 0 and there are no Checks in progress, use Payment Control to update the Max Payment for the invoice.

·    If a Manual Check batch Payment entry was attempted to be saved with neither the Print Check option nor a check number, and Auto Add Batch Entry was enabled, confirming the blank check number error would open a second batch entry screen before the first was complete. This has been corrected.

·    When viewing printed Cash Invoices or Prepayments in a manual check batch, previously you could view the details and the fields would be editable. However, nothing was able to be changed and saved, as an error would occur. Now the fields are correctly not editable in the first place.

·    When unsupported user defined codes were in the Send to GL Description setting in the company profile for Other entries, an access violation error when posting Check Reconciliation reversals could occur.

·    GL Description codes for Batch Optional and Time & Billing fields could be saved in the Company Profile for Other transaction types, even though these values are not supported. Now, these codes will give a verification error when editing and saving the Company Profile.

·    When selecting multiple batches on a grid sorted by Description, the Batch Listing report button is no longer active so that it is clear that the report only prints a single range of consecutive batches. If multiple batches are selected and the sort order is changed, the selection is cleared and a single row is highlighted.

·    If the filter Styles list was saved with the App Specific and Generic setting, this would cause the Manual Style field within Edit Vendors to show an incomplete list of styles and result in a List index out of bounds error.

·    An Error message appears instead of an Access Violation if a Favorite for the Pre-Check Register is printed from the Reports menu or added to a Report Set.

·    When printing System Checks, if the starting check number was changed from the default bank value, posting would write an audit sequence value with 18991230 to the Check Number Audit List report, rather than using the check date. This has been fixed.

·    In rare cases due to rounding, in System Check Processing, pressing the space bar on a vendor record to restore generated payments from zero would not do so.

·    After creating and saving a System Check Run, the Payables program window could be sent to the back of the Windows desktop and other open windows would appear on top.

·    System Check Runs now print the correct check amount when an invoice with a negative amount and Terms that calculate a Discount is selected to be included for the vendor payment. The Pre-check Register report was already correct.

·    Posting System Check Runs did not write a value to the Accounting Date field for the Ledger retrieval batch. This could potentially cause an error if the Payables batch was retrieved using the Subledger Period option.

·    The Bank ID field no longer allows non-numeric characters. If this field had been used for something other than a Bank Account number, it should be moved somewhere else. The data is not cleared during conversion but the field will be stripped if the vendor is edited and the field is visited.

·    If Telpay is the only EFT Provider, the 'Telpay EFT Only?' option on the vendor’s EFT tab will be enabled during data conversion.

·    When integrated with Adagio DocStore, deleting all attached PDFs from a batch entry but cancelling without saving changes would result in not clearing the Doc Link from the entry. This has been fixed.

·    Docstore errors appeared when attaching xlsx or JPG files in some cases. The related errors fixed are: 1) Error: User canceled path selection (5124) during call to ADocFilerPDFBrowse2. 2) Error: File name has unknown extension (10151) during call to ADocfilerCreateW

·    Drag and drop from an email was broken.

·    In version 9.3B, when integrated with Adagio DocStore, the ability to attach PDFs to printed manual checks was lost. Now, not only has the feature been restored, but there are 2 separate View PDF buttons - one for the manual check batch entry and the other for viewing attachments on posted invoices for Payments.

·    When printing the Check Number Audit List with a date range that does not have any checks, in some cases, an Access Violation error would occur.

·    The Check Number Audit List report printed the Home Equivalent amount with a value 100 times too large when MultiCurrency was enabled with the data. The data was correct but the report had a problem.

·    The Manual Check Batch Listing report was not printing the Revenue account associated with a Time Billing distribution from cash invoices in the GL Distribution Summary section. This has been corrected and is printing the same information as the Manual Check posting journal report.

·    When printing a report set directly to the AdagioV3PDF driver, and you choose to cancel printing for a particular report from the PDF Save As screen, you are now prompted to cancel printing just that report or the entire report set. This choice is written to the report log.

·    When printing Report Sets using either AdagioV2PDF or AdagioV3PDF as the specific printer, instead of using PDF Document as the destination, the report log now stores the PDF file name and save location instead of simply 'Printed to AdagioV3PDF'.

·    The next sequence number on the EFT Provider is now incremented during EFT Batch Creation when the Generate button is selected.

·    Within batch entry and accessing the Vendor information screens, the EFT Transaction Type field value was not loaded.

·    In Payables 9.3B and with the Adagio EFT add-on integration, the EFT Provider screen for the Montreal 80 format had the Send as Reference field hidden. The data was not affected, only the screen display. The field has been restored.

·    For EFT Vendors, if the Country for the Vendor's formatted address is not Canada or USA, the extra validation specific to Telpay will not be done.

·    The Email Setting for Wait Seconds Between sending emails is now used for sending email, in addition to sending emails from the Queue.

·    Viewing PDFs from the email queue for Letter and Advice forms gave a Failed to Launch error when Adagio DocStore was not integrated. This error no longer occurs.

·    Import Batches now gives a validation error when an optional field that requires a non-blank value, but is not verified against a predefined list, has a blank value in the import file.

·    Import Vendors: 'EFT Trans Type' has been updated to support 2 character Transaction Types for the Caribbean.

·    The Batch Status Inquiry screen incorrectly had an active Print PJ button when 2 or more Open batches were simultaneously selected. Now, the Print PJ button is correctly inactive unless at least one Posted batch is part of the selection.

·    Integrity errors were caused by editing a manual check payment, deleting the payment details and then saving the entry without any invoices being paid. This caused the error: 'Error: Manual checks have been over applied to Vendor...'.

·    Converting data from very old versions could result in Data Integrity Check giving an error ”'-' is not a valid integer value” if particular batch temporary files existed.

·    When a System Check Run has a Parked status but the data incorrectly has an empty Parked Check file, the data integrity check will now reset the Check Run status to Created, so that the payments can be recreated. Previously, the Resume status was available but could not complete the Check Run process.

·    In Adagio Payables 9.3B, printing some reports would log an error 4108 to the ADSError.log file due to a mismatch in the expected file size.

·    MultiCurrency data: Period End and the Open Payables and Aged Open Payables reports have been updated to make backdated reports more accurate.

·    Editing the Payment Control of an invoice now correctly prevents saving a Maximum Payment greater than the Current amount.

·    Changing the transaction clearing date on the Period End screen did not update the date value in the function summary of point E for deleting transactions.

·    User Preferences now has options for Archive Invoice and Manual Check Batches to automatically open on Start up.

·    Posting a batch with non-printed checks now correctly populates the batch (sequence) number for the Check Number Audit List report.

·    When posting a manual check batch with more than one non-printed entries, only the first entry had the audit sequence field of the check number audit list data file populated. This meant that printing the Check Number Audit List report with the Last Sequence option only printed the first check. Posting manual check batches has been fixed to prevent this scenario from happening.

·    If one user was retrieving posted checks into Adagio BankRec at the same time as another user was posting manual checks from the batch entry screen, resource locking didn't correctly prevent this and posting completed. Now, this is prevented. Resource locking was correctly in place if the user tried to post the manual check batch from the Post button on the toolbar.

·    System Check Runs for banks that support EFT processing now display the EFT code assigned to the bank, to assist in seeing what is set up for the bank.

·    Copying or Moving a single Archived Manual Check batch with Payment entries to a new Current Manual Check Batch, without updating either document numbers or dates, did not correctly update the Reserved Payment values on the paid invoice transaction records. This caused integrity errors both after copying and after posting.

Adagio Payables 9.3A (2020.09.05)

The sole purpose of this Service Pack is to provide Adagio AP9.3A compatibility with the upcoming upgrade release of BankRec 9.3A.

NOTE: Adagio Payables 9.3A MUST already be installed before you install this Service Pack. The install will warn you if you select a destination folder that does not contain Payables 9.3A.

Adagio® is a registered trademark of Softrak Systems Inc.

The programs and documentation are copyright 1999 - 2020 by Softrak Systems Inc., all rights reserved.

The software and documentation are provided “as is” and without warranty as to performance. Because of the many uses to which software may be put and the variety of hardware used in conjunction with it, no warranty of fitness for a particular purpose is offered. While the developer has invested considerable time and money to create a high quality product, the user must assume the risk of using this software.

·    In System Check Runs, paying multiple invoices for a vendor caused payments not to be properly matched to invoices in some cases. This also caused the Check Register report to print 0.00 for vendors that had been paid by check or EFT. Integrity errors were created.

·    With Payables 93B data, DataCare 93A was reporting an Access violation error during Rebuild, in some cases.

·    Drag and drop from an email was broken. This has been fixed.

·    For the Caribbean, a CIBC First Caribbean (CSV) EFT Batch Format has been added to the list of EFT Batch Formats. It is for Direct Payments in CSV format for the First Caribbean International Bank.

Notes:

If this Format is being used, you cannot also have an EFT provider that uses the Telpay format. Telpay requires Vendor Address formatting for Canada.

The Currency Code is defined on the EFT Provider. It will default to 00 = Local Dollars. There is also an option to include a Reference for each record.

For the Vendor, on the Accounting tab, the first 3 characters of the Bank ID field are the Bank Code. The next 5 characters are the Branch Code. The rest of the Bank ID is the Destination/Customer Acct #.

The Account Type Code and the Transaction Code are set on the EFT tab. The Account Type Code is limited to Checking or Savings. If the Transaction Code is not defined, it will default to 51 = FCIB Salary.

·    In MultiCurrency data, in some cases, for Credit Notes that were not applied to an existing original invoice, the exchange rate field became uneditable and was set to 0.000.

·    In check runs, the Parked Status was not reset to Open when the check run was resumed and ‘No’ was selected to void the printed checks, in some cases.

·   When the Style List was restricted to only app specific and generic styles, the style dropdown field did not display the correct font and color. This has been fixed.

·   A locking error may have been encountered in batch entry if the Find Vendor function had been used on a Filtered Vendor Lit. This may account for some data integrity errors regarding open invoice batch computed vendor amounts.

·   For the Caribbean and Scotiabank, a Scotia CSV Recipient Upload EFT Batch Format has been added to the list of EFT Batch Formats.

Notes:

If this Format is being used, you cannot also have an EFT provider that uses the Telpay format. Telpay requires Vendor Address formatting for Canada.

The Recipient account currency is defined on the EFT Provider. There is also an option to include a memo for each record.

For the Vendor, on the Accounting tab, the firt 9 characters of the bank ID field are the Routing Number (Designated Bank’s ABA number). The rest of the bank ID is the Branch Transit number (if required) and the Recipient’s account number. If the Bank requires the Account number to have leading zeros, they much be entered in the Bank ID.

The EFT Bank Account Type is set on the EFT tab.

·   Payables 9.3B added restrictions to payments for On hold and Inactive vendors. This has been relaxed.  If a document has a ‘Forced’ status, it will be included in a System Check Run.

·   In 9.3B, Prepayments with a ‘Forced’ status were not included in a System Check Run if the Prepayment date was after the Check date.

·    A new EFT Maximum field has been added to the bank record, to prevent generating an EFT total amount greater than this maximum. This is useful if you have a maximum submission amount from TelPay or the bank and can force you to lower the payments in order to get under that maximum.

EFT Maximum per run that is set to 0.00 means there is no limit.

·    The auto Add Entry option has been added to User Preferences for opening a new batch entry screen immediately after saving another entry.

·    The check Number Audit List report can now be printed and purged for specific dates or check runs or the most recent check run for printing or EFT.

·    Report sets can now be emailed to selected recipients when Adagio DocStore is integrated, with PDF or Excel file attachments for each report. Integration to Adagio Console 9.3A also supports emailing report sets through automation by attaching report PDFs to the automation log email.

·    New Vendor fields have been added for Contact and Email addresses for Advice, Payee and PO recipients. Import Vendors supports adding this new information. All email addresses can now be used for finding vendors, either from the vendor list or within transaction entry.

·    A new company profile option is available to set a default method for consolidating Ledger transactions after printing the report and is also used if the GL Transactions report is printed and consolidated from a Report Set.

Problems Fixed

·          When a dataset is created or converted using Payables 93B, there is a new Company Profile, Batch/System Check tab option for 'System Check Run Description'. It defaults to: Created by %usr on %dat %tim.

·          MultiCurrency: On the System Check Register Report, when a payment was made from a Bank with different currency decimals than the Bank Currency, the Check Amount was printed using the Vendor decimals instead of the Bank decimals.

·          MultiCurrency enabled reports with legal-sized output printed directly to PDF no longer cut off part of the right side, when the new AdagioV3PDF driver is used instead of AdagioV2PD

·          When Additional Forms were faxed, QIFAXQ data files were created as well as SDFAXQ files.

·          If a Report Favorite is created for the System Check Status report, the ePrint report code %BAT may be used to print the System Check Run Sequence number(s).

·          If a Manual Check, Payment entry with a Discount was changed to a different Payment type, integrity errors were caused because the Discount Amount was not cleared

·          Printing Additional Forms to PDF could create a file that had the wrong check number range as part of the name. This has been fixed.

·          Period End and Year End processinghave been updated to warn about System Check Runs that have not been completed.

·          If a Report Favorite is created for the Pre-Check Register, the ePrint report code %BAT may be used to print the System Check Run Sequence number.

·          Company Profile option, 'Days To Go Back In History When Backdating' set to 0 means that History will not be included in a Backdated Open Payables, Aged Open Payables or Aged Overdue Payables report.

·          If an email cannot be sent successfully, an error message with the reason for the failure will be displayed.

·          Emailing Additional Forms using Direct method failed when sent Now rather than from the email queue. This has been fixed.

·          Consolidate G/L Transactions was not checking if DocStore was enabled for the dataset.  This only affects data that is restored and then has DocStore disabled. An 'Invalid Document Filer Handle' error message would appear.

·          These new Specification codes have been added for Printing Checks:

V90 Vendor advice contact
V91 Vendor advice email
V92 Vendor payee email
V93 Vendor PO contact
V94 Vendor PO email

·          Vendors now have these new fields: 30-character Contact Name and 160-character Email for Advices and for PO. Payee Email has also been added.

·          Converting from the earlier versions to latest version of Payables willnow prompt to enable ExcelDirect Printing for all users.

·          In MultiCurrency data, if a Vendor was paid from a bank with a different currency and a limit was set on the Check amount, the Pre-Check Register report may have incorrectly stated that a check would not be printed for the vendor when the Check Run would include them.

·          Manual check batch posting supports the new EFT maximum setting on the bank where, if the total EFT amount value of the batch exceeds the maximum, submission will be prevented.

·          When DocStore is integrated and a System Check run was printed, choosing ‘No’ for everything printing successfully but entering the last check number as good did not generate the PDF Doc Links for the payment transactions. This has been fixed.

·          Vendors now have a 'Preferred Advice {Send} Method'. Select this Vendor's preferred way of receiving their Additional Forms from you (eg. Print, Email or Fax). By default, this option is set to Print.

Additional Forms can have Send methods of Printer, PDF, Email and Fax. The Send method you choose is remembered for the next time you print an Additional form, depending on what has been enabled in the User Preferences - Report Options. Ensure all the appropriate setting(s) are enabled before selecting the Print/Send button.
There is a 'Match Preferred Send Method' in the Print Additional Forms window. This option works with the 'Preferred Advice Method' dropdown option you set on the Vendor's Accounting tab.

When enabled, only Vendors having the same Preferred Advice Method set in their record as the setting(s) selected in the Send method field run will be sent the document.

If a Single check is printed from within a Manual Check batch or when reprinting Additional forms from System Check Runs Inquiry, the 'Match Preferred Advice Method' will be ignored. The exception is Manual Checks for Miscellaneous Vendors. Miscellaneous Vendors will have Print or if DocStore is installed, Print and PDF, available to them.

When 'Match Preferred Send Method' is disabled, Payables will create documents for Vendors based on their Advice print method option setting(s) on the Vendor's Accounting tab.

NOTE: A Vendor must meet all criteria specified on the print report window for Additional Forms/Letters to be produced for that Vendor.

NOTE: Alt/p, Alt/d, Alt/e and Alt/f may be used as keyboard shortcuts to enable or disable the Printer, PDF, Email and Fax Send method options.

·          Vendor email addresses are now available for finding vendors, either from the vendor list or within transaction entry. This includes using the new advice or alternate payee email addresses and, if multiple emails separated by semi-colons are stored in a single email field, then any one can be used for finding the vendor.

·          Emailing Additional Forms using the Email print option Now and the Email Setup option Outlook was sending the emails as MAPI instead of Outlook.

·          The Attachment Count was not being updated correctly in the email queue for Check Advices and Letters.

·          If the payment folder specified in an EFT provider does not exist, an Error message appeared during the EFT Batch creation. The fix now creates the payment folder if it does not exist.

·          During conversion, based on the state of the Check number audit list, this error may appear: ‘Error finding record with assigned check number, this record will be skipped.’ The message is information only.

·          In Vendor Edit/Inquiry, changing tabs back and forth from the Transactions tab went into a loop.

·          While you can have unlimited bank codes, the System Check Runs Inquiry can only display 300 of them.

·          If the Company Profile, Integration, General Ledger Option for 'Prompt to consolidate?' is not selected, Report sets details for 'Print/Consolidate G/L Transactions' no longer have an option for 'Consolidate?'. A new favorite must be created to see this change.

·          In System Check Run, if a pre-check amount maximum was set and a vendor with the One Check per Invoice option enabled had a total invoice amount to pay larger than this maximum, the pre-check register would list no check to be printed, but invoices lower than the maximum would in fact print. Now the pre-check register has a vendor amount range and no checks will print in this scenario.

·          System Check Runs Inquiry for Previous Year will allow you to print the Status Report and to print or reprint Additional Forms for System Check Runs that were created in 93B and moved to History by the Year End process.

·          If Payables was closed before the 'On start-up' functions were fully displayed, in some cases, there were Access Violations.

·          The Print Status date for 'Last Pre-Check Register printed on' is now updated with the System Date instead of the Session Date.

·          For a System Check run, on the Payments tab in the Details list, pressing Enter on a highlighted detail will open the Edit Payment window.

·          When GridView workspaces are added or removed from the Views folder, you are no longer prompted to update the menu and it happens automatically.

·          In MultiCurrency datasets, reversing source currency checks that had a current home equivalent balance of .01 caused an Integrity error: computed home balance does not match stored home balance.

·          In Batch Status and System Check Run Inquiries, Batches / Check Runs are displayed in reverse order so that the most current ones are displayed at the top.

·          If the data path folder name contained a period, browsing to the folder and double clicking on the global file caused the application to try to create a new dataset with the extension set to the part of the folder name following the period character.

·          If a user has access to the Maintain Automation Log feature, they also have the ability to view all of the automation logs for any user.

·          New automation command nouns have been added to allow attaching report set PDF/Excel files to the email with the automation log results to allow reports from multiple applications to be attached on a single email. The EmailPDFAutoLog has Overwrite/Attach and Append/Attach nouns to include PDF/Excel files from report sets. Adagio Console 9.3A is required to use this feature.

·          When Adagio DocStore is integrated, report sets can now be emailed to selected recipients with PDF or Excel file attachments for each report.

·          Dragging PDFs to attach documents within Applied Transaction Details caused an Error.

·    Viewing DocStore PDF attachments is now available from Check Reconciliation, when highlighting a check in the grid.

·    When integrated with Adagio EFT, more choices are available in the list of EFT transaction types, specifically codes 600 to 617.

·    Added ‘Blank on zero’ to Properties for quantity, amount and other numeric fields in the Specification Designer.

Vendors

·    Copying a vendor with an attached DocStore PDF previously copied the link to the new vendor. This no longer happens.

·    If an attachment is open in the PDF viewer from Vendor Transactions and the Vendor name is changed before the viewer is closed, document links cannot be properly updated. The error message “Storage PDF not found (11103) during call to ADocFilerReadW” was received when trying to view the PDF later from transactions. The viewer is now closed automatically before change of vendor name can occur.

·    If the View PDF window was open from the Vendor grid, and a different vendor record was highlighted that had no PDF attached, the view did not refresh properly. This has been fixed.

Batch Entry and Posting

·    Deleting batches no longer clears the associated DocStore PDF links, so that if you restore the batch at a later time, the document links will be restored as well.

·    Browsing for a payment folder in EFT Provider records now only requires selecting the folder, rather than a file within the folder.

·    For JobCost and Time&Billing related data, if there is a Type field in entry details, it will be first in the tab sequence for new details. For non AJ/TM related data, the Distribution Code will be the first field. If there are no Distribution Codes, this field is not displayed and the Account will be the first field in the tab sequence.

·    In some cases when starting Payables, and if Ledger data was not found, posting would revert to writing to the G/L subledger batch in an old layout, preventing the batch from being retrieved into Ledger. This has been fixed.

·    The second batch entry description is now saved correctly for adjustments when posting to the vendor transactions and posting journal file, and for manual checks to the posting journal file.

Check Designer/Printing and Reconciliation

·    Corrected a problem where the preview of checks to an Ultra High Resolution screen displayed shrunken in the upper left of the screen. The preview from the Specification Designer was also corrected.

·    Partially paying invoices through System Checks was causing Integrity errors. It was not updating the Vendor's Total forced amount properly and it was setting the 'Forced' Status to None.

·    If a manual check batch containing printed checks is deleted and then later recovered, posting the recovered batch now correctly writes the results to the check number audit list report.

·    An error using the SmartFinder on the Check Reconciliation screen in Payables 9.2B and 9.3A has been corrected.

Reports

·    The Aged Retainage report didn't show transactions when they landed on the page break in some cases.

·    The Check Register report now sorts paid invoices by document number, in the same way as the Pre-Check Register report.

·    Vendor Transactions, Aged Retainage and Open Payables reports printed in the Summary format printed a ‘Continued’ line at the top of the 2nd and subsequent pages.

·    The option on the G/L Transaction report to Show Description 2 was not working.

·    In the Vendor Transactions report, if the selected fields for sorting results in an index that is too long for exporting the report to Excel, a clearer error message will result, indicating what should be done to correct the error.

Importing

·    In Import Invoices, if the Hdr-Transaction Type field was not included in either the Imported or Defaulted field lists, incomplete information was previously imported with no indication of an error. Now the transaction type defaults to Invoice. Alternately, you can set a Transaction Type default of Invoice on the Field Default tab for the same results, as could have been done in prior versions.

·    Importing with Field offset was trimming the import field on the right instead of the left.

Miscellaneous

·    Corrected errors relating to Adagio DocStore that occurred at some sites and caused data integrity errors that had to be fixed by the Data Integrity Check function.

·    The system application log now stores the batch number that was edited, at the same time when logging when a user edits a batch.

·    Installing Payables 9.3A (2018.02.01) gave a false warning regarding the required version of Adagio SalesCQ.

·    Double-clicking the paperclip button or clicking it a second time when the Open PDF dialog was already open caused an error message. This is now prevented.

·    If you deleted a DocStore attachment immediately after adding it (for example if you attached the wrong document) an error was displayed.

·    Duplicate PDFs were added to DocStore for additional forms when checks were printed. Additional forms are no longer added to DocStore.

If a DocStorage Form is specified on the Bank, it will be the attachment. Otherwise:

- For printed checks, the printed Check specification will be attached.

- For EFT:
     a) if the Bank is set up with a Check specification or a Check specification is selected on the EFT Check Run window, a copy of the Check will be attached, or
     b) if there is no Check specification set on the Bank or selected during the EFT run, an Additional form set on the Bank will be attached, or
     c) if there are no Additional form specifications defined on the bank and the Check specification is left blank on the Bank and on the EFT Check Run window, nothing will be attached.

·    The message “There are no batches to post in the selected range” was displayed if you attempted to post a batch while another user was editing it. The message now says “Unable to post as batch [n, n] is currently being accessed by user [nnn].”

·    If duplicate check numbers were entered (incorrectly) when voiding checks, the Check Register reported invoices paid for the wrong vendor.

·    The Doc Link column on the Payments grid in System Checks showed blanks instead of ‘Linked’ when there was a DocStore PDF attached.

·    Printing and clearing the Archive Batch Status report cleared the Open batches, not the Archive batches.

·    The recoverable tax on the Reconciliation Posting Journal is now being shown correctly.

·    Creating an Archive batch in Payables 9.2B or 9.3A used the Next Batch Number for Current batches. This resulted in an error when creating a new Archive batch in some cases and there was a gap in batch numbers for Current batches.

·    The Data Integrity Check error for duplicate documents in manual check batches stated the error was in an invoice batch.

·    When importing invoice batches with validation for an import file with errors, if you cancelled before viewing all the errors, then imported another batch with errors, there were data integrity errors.

·    If a vendor name was changed by importing vendors, a new DocStore folder for the vendor was created instead of renaming the existing folder to the changed vendor name.

·    The EFT Trans Type field was always imported as blank.

·    Posting batches from the Post menu with the Backup Before option set to ‘Always’ did not do a backup. Posting from the batch grid did not have this problem.

·    In Payables 9.2B and 9.3A, importing invoice batches containing more than 1 invoice caused integrity errors in some cases.

·    In the Payables 9.3A Year End function when you selected ‘Run Only’ rather than ‘Backup/Run’, the year end was not performed.

New Features in Payables

·    An archive vendor PDF copy for advices/checks has been added for DocStore users. This allows EFT users to reprint / resend an EFT advice if required.

·    Written amounts on checks can now be in Spanish.

·    You can now leave the GL Account/Department fields blank in a Distribution Set. Similar to a Distribution, the Acct/Dept will default from the vendor. This saves you from having to set up a different Distribution Set for each expense Acct/Dept pair used. Note: The ‘Auto-distribute’ option cannot be used if the Acct/Dept is blank for any Distribution in the Distribution Set.

·    Added Related Data option to backup. It includes Ledger data files in the backup. This option is supported in automation jobs for Adagio Console users.

Problems Fixed

·    In Payables 9.2B, a negative Allocation % in a Distribution Set always rounded to a whole number.

·    In Payables 9.2A and 9.2B, when entering transactions to an invoice batch the error “Please enter a valid account” was displayed if the previous entry used a GL Account with a Department that did not exist for the current entry and the ‘Active records only’ option was on in the finder.

·    For System Checks in a foreign currency, a REGL transaction was not generated in the Payables GL distribution file for the vendor, although the correct GL transaction was generated for Adagio Ledger.

·    When posting an adjustment to a vendor who had no transactions in history, there was an error stating unable to post as the adjusted document exists in history.  This occurred if the invoice number being adjusted was the same as the first history transaction for the next vendor.

·    For a vendor with the ‘Print one check per invoice’ option enabled, the Pre-Check Register showed only 1 check would be printed when there were multiple checks to be printed.

·    After printing the Pre-Check Register or Revaluation report, you were prevented from adding a new Account in Ledger until Payables was closed. There was an error in Ledger, when this was attempted, allowing you to retry or cancel. If you cancelled, a fixable integrity error resulted in Ledger.

·    After printing the Check Register you were prevented from entering batches or editing vendors until Payables was closed.

·    When printing blank check stock in Payables 9.2A or 9.2B, the bank address did not print using Formatted Address codes.

·    When importing invoice or manual check batches in Excel format with the ‘Header fields on each record’ option enabled, the accounting date was set to the same value for all entries unless it was included as a field in the import file.

·    The GL Stat Units is a field in the Invoice Posting Journal file was not populated on posting. This prevented it from being used in GridView views or custom reports.

·    You can now save an invoice with no details.

·    Importing vendors did not update the Payee unless the Payee Name and Address 1 were non-blank. Now only the Payee Name must be non-blank.

·    When importing a manual check batch if the first entry was a cash invoice, then it was too big by $0.05 and there was a $0.05 detail discount.

·    Deleting history transactions for Pre-Payments caused a data integrity error. The error was fixed by a rebuild in the Data Integrity Check.

·    After reversing a cash invoice with an invoice date in the previous month and selecting the ‘Use document date’ option, the cash invoice appeared on the Open Payables report when it should not have.

·    Users are now prevented from blanking out dates when entering a Cash Invoice. Posting will set a date for any blank date in unposted cash invoices already entered.

·    The sort order of the details grid in Manual Check batch entry was incorrect in Payables 9.2B.

·    When the ‘Auto-fill vendor codes’ option is used, the behavior of the vendor finder invoked with the F5 key is now the same as when invoked by the magnifying glass.

·    The ‘Accounting Date’ field was blank in the Transactions grid in the Edit/View Vendor functions.

·    The ‘Accounting Date’ now prints on batch listings and posting journals where applicable when the option is enabled in the Company Profile. For cash invoices, it is possible to have 2 accounting dates – only the check accounting date is printed.

·    Corrected a problem encrypting the email password when the Set All Users function was used in Email Setup.

·    In Payables 9.2B, the fallback for users without their own specific email setup (created using the ‘Set All Users’ function in Email Setup) did not work.

·    In Payables 9.2B, when importing a manual check batch, the Check Number field in the imported file was ignored and instead the next check number was assigned to the transaction.

·    In Payables 9.2B, the Data Integrity Checker froze if the invoice batch with the highest batch number contained 100 or more entries (whether that batch was posted or open). This is also corrected in DataCare.

·    Entries in Archive batches could not be sorted and the message “Please complete/close open documents before proceeding” was displayed.

·    The width of the ‘MICR Encoding’ field in Edit Banks has been made wider to allow the entire value to be shown.

·    In Payables 9.2B, the Reference field was not available to be added to Manual Check batch list grid.

·    The Transaction Details screen in Edit/View Vendor functions is now sizeable to allow more room when fields are added to the grid with the Column Editor.

·    Installs a new Adagio Data Source (ADS) that prevents resource locking problems at large Adagio sites running 9.2 versions and improves application performance at these sites.

NOTE: All third-party applications from Adagio Developer Partners must use the new ADS. You must check with your Adagio consultant or the developer to confirm their application is using ADS 1.12. 66.3503 or higher. Failure to ascertain this risks corrupting data if the application is writing to the Adagio data files concurrently with Adagio modules.

·    Added a Batch Inquiry button to the toolbar.

Batch Entry and Posting

·    Archive Invoices and Manual Check Batches with full batch edit in the Archive system. Existing Recurring Batches are converted to Archive Invoices Batches.

·    In invoice batches for 9.2B, the 'Original invoice' field is above the ‘Document’ field on the entry screen. If the entry is a Credit Note or Debit Note, the first thing you want to do is enter the matching invoice. If the entry is an Invoice the program skips this field automatically. The new order of these fields makes it less likely the Document number will be left blank.

·    Tax can be calculated automatically on amounts entered on invoices and cash invoices. Added ‘Taxable purchase’ option in the Tax Type in Distribution Codes.

·    You can now recover a percentage of tax to multiple expense accounts on invoices and cash invoices. The field ‘Tax recoverable %’ has been added to Distributions. The percentage is to 5 decimals. This is useful for some Not-for-profit organizations.

·    Distribution Sets now allow you to distribute a single amount to multiple expense accounts based on a percentage rather than doing it manually. An ‘Allocation %’ field has been added to the Distribution Set Detail screen. In addition, you can specify a default Allocation Amount in the Distribution Set to be allocated for each detail based on the percentage.

·    New Open Documents file maintains a list of invoices in open invoices batches and cash invoices in manual check batches. This is used to help prevent entering duplicate invoices. When an invoice is entered for the same Document Number as a transaction in a different or the same batch a warning is displayed. This will make it more difficult to enter duplicate invoices or payments.

·    The total amount of payments in open manual check batches is tracked for the posted invoice transactions they are applied to. This amount is used to calculate the actual Remaining Amount for the invoice. The Remaining Amount is shown on manual check details. This helps prevent duplicate payment or over payment of invoices.

When BankRec creates a batch in Payables, it updates these amounts. However, payments in open BankRec batches are not reflected in these amounts.

If a System Check run is created for an invoice with applied amounts in open manual checks, the payment amount for the invoice will be the current amount minus the total payments in manual check batches. However, the Amount Remaining shown in manual check entry does not reflect payments in a system check run in progress. If a manual check is entered for an invoice already in the system check pre-check register you are required to regenerate the run before printing and posting it. For these reasons, you should not create payments using both manual check batches and system checks if you wish to use this feature.

·    The total amount and count of payments, as well as the manual check batch number and entry number of the payment (unless there have been 2 or more payments against the invoice) are maintained in posted invoice transactions. These fields can be displayed on the vendor transaction grid, used in Filters, GridView views and custom reports.

·    Batch types can have color on their forms, like GL current and next year. Current / archive invoices, current/archive manual checks, and current adjustments.

·    Added ExcelDirect on batches grids, batch entries, and batch entry details.

·    For Cash Invoices, you can enter an Invoice date that can be different from the Check date.

·    An Accounting date can be included on batch entries so that transactions can be retrieved into GL for a different period. For Cash Invoices, there is an Accounting Date for the invoice as well as the payment.

·    A Batch Total field has been added to the batch grid screens and shows a running total of all entries in the batch.

·    The Address tab in manual check batches now supports formatted vendor addresses.

·    Batch Entry Templates have been added. Templates allow you speed up entry and eliminate confusion caused by fields you do not use. Templates allow you to skip, disable or hide fields in invoice, cash and adjustment entry. Entry Templates can be by Group. Define Entry Templates using the Edit Menu.

·    Entries in batches can be sorted. You can sort by Vendor Number, Document Date, Document Number, Reference, Entry Number and the optional fields.

·    A ‘Ready to post’ status has been added to the batch status. Default settings for Entered, Retrieved or Imported batches can be set in the Company Profile. Batches written directly to Adagio Payables from other ledgers such as BankRec or PurchaseOrders will be considered to have been retrieved rather than Entered.

·    Transactions now support an Accounting Date separate from the Document Date. Documents with different accounting dates may be retrieved into Adagio Ledger to the correct period using the ‘Subledger period’ option in the ‘Retrieve Subledger Batches’ function. To use this feature, set the option ‘Allow edit of accounting date’ on the Integration tab in the Company Profile.

·    A second description has been added to batch entry.

·    Increased the size of the Description fields in batches from 30 to 40 characters.

·    Statistical Units can be entered in batches and will be posted through to Ledger 9.0A or higher (if the account tracks Statistical Units).

·    Optional fields have been added at the transaction header level. Optional batch fields are posted to the transaction file. Optional fields will flow from batches entered in related modules, such as Adagio PurchaseOrders, in future versions of BankRec.

·    Several user and date stamp fields have been added to batches. These fields are posted through to the transaction file. They are available in grids and can be shown on custom reports and in GridView.

Specification Designer and Printing Checks / EFT

·    Payables 9.2B supports multiple EFT providers. Requires Adagio EFT 9.2B to be installed unless you use Telpay. See release notes for Adagio EFT 9.2B for details.

·    Specification codes M14..17 (Man chk desc Ln1..4), M18, M19, and M20 were moved from Company Information section to new Manual Check section.

·    Added Manual Check section, with these specification codes:
   M47 Man chk Desc 2
   M48 Man chk Invoices Date
   V26..30 Check address line 1..4, Check Zip/Postal code
   V03,4,5,14,6,84 Check address line 1..6 (compressed)
   V78..83 Check address line 1..6 (formatted)
   V85 Check City, State/Province, ZIP/Postal code
   V86 Check City
   V87 Check State/Province
   V88 Check Country

·    Added to Advice body (detail) section:
   L7 Transaction desc 2

·    Added to Check Information section:
   A24 Currency code
   A25 Currency description

·    Added to Bank Information section:
   B07 Bank address line 5 (compressed)
      – was Bank Zip/Postal
   B18 Bank address line 6 (compressed)
   B19..24 Bank address line 1..6 (formatted)
   B26 Bank City
   B27 Bank State/Province
   B28 Bank Country

Reports

·    The ‘Force paperless reports?’ option available to Adagio ePrint users is now respected when printing Import/Export templates, Automation logs, and smart finder results.

·    The Adagio ePrint code %BTT (Batch Type) is now supported for Batch Listings.

·    Vendor transactions report allows summary by date range

·    Print the Aged Open Payables, Aged Overdue Payables and Vendor Transactions reports to Excel using ExcelDirect. Added an ExcelDirect button and ExcelDirect Options button on the report dialogs. Transactions from the report are exported to Excel using the selected ranges, sorts and options (except subtotals and page breaks). The resulting spreadsheet may be more useful than the export produced using Crystal depending on your requirements. Select the new ‘Enable ExcelDirect Print’ option and related settings on the Report Options tab in the Company Profile.

·    Added new include options and new formats to the Vendor Transactions report.

Miscellaneous

·    Payables now renders dialogs properly on Ultra High Resolution displays when the font size is anything other than 100% of normal on Windows 8.1 or higher. All Adagio releases dated in September 2016 and later have this problem fixed. For releases prior to this date, the utility program SetScreenForAdagio.EXE is installed in the \Softrak\System folder to correct the problem.

·    Payables 9.2B installs an updated version of the AdagioPDF driver. The updated driver name is AdagioV2PDF and will appear in Windows Control Panel, Devices and Printers. When installs are performed on January 1, 2017 or later from a Remote Desktop Services connection to Microsoft Server 2016 or from a Windows 10 station, the security warning related to the AdagioPDF printer driver no longer appears.

·    The email password for servers that require authentication is now encrypted in the file containing email settings for the ‘Direct’ email method.

Problems Fixed

·    Many fixes were made for this release which are not listed in these release notes.

·    The Aged Open Payables did not print the Original Amount in Home currency in Summary.

·    For Manual Check batches and Payment Control, the warning for exceeding maximum payment has been changed and you are now able to proceed.

·    If an invoice had been assigned a Forced status and paid, future pre-check registers would continue to select this invoice even though the current balance was zero. This is no longer the case.

·    After installing Ledger 9.2B (2016.08.10) or SysUpdater (160809), temporary files created on workstations by printing reports were not deleted in some cases, although this did not cause any problems.

·    When browsing for a path in various functions in Payables 9.2A (2016.05.24) on Windows 8 or higher, you had to select a file to select the folder. This was corrected by System Updater (2016.08.09), which is no longer required for this release of Payables.

·    The snapshot made by the System Status function (chksys.exe) did not include station log files in some cases.

·    When taking a snapshot with the System Status function (chksys.exe), the error “Snapshot is incomplete! The snapshot encountered error (1).” was encountered in some cases, indicating a file was open and could not be included in the snapshot, when in fact that may not have been the case.

·    Installs a new Adagio Data Source (ADS) that prevents resource locking problems at large Adagio sites running 9.2 versions and improves application performance at these sites.

NOTE: All third-party applications from Adagio Developer Partners must use the new ADS. You must check with your Adagio consultant or the developer to confirm their application is using ADS 1.12. 66.3503 or higher. Failure to ascertain this risks corrupting data if the application is writing to the Adagio data files concurrently with Adagio modules.

·    In Payables 9.2A if you exported vendors and browsed to any folder other than the data folder, where the output file did not already exist, then said Yes to create the file, there was an Access Violation error if you did not also include the file extension in the filename.

·    Adagio DataCare displayed the error “Unable to open data file options @P81BOPT, (1213)” when opened with a Payables 9.2A database present and Payables 8.1F or earlier had never been used with the database.

·    In Payables 9.2A, after creating a new database or converting from an earlier version, if Adagio Ledger data was not present, you could not retrieve into Ledger in another data set.

·    Enabling the ‘Use TLS/SSL’ setting in the Email Setup was not remembered.

·    Fixed a problem in Payables 9.2A where the MultiCurrency Revaluation function caused data integrity errors in some cases. Also fixed similar but different and less frequent problem that existed in 8.1F and earlier versions.

·    In Payables 9.2A, a file for retrieval in BankRec was created even though BankRec was not used. This did not cause a problem and has been corrected.

·    In Payables 9.2A, the Revaluation function was not updating the Home Equivalent amount on Prepayments.

·    Installing Payables 9.2A (2015.06.09) at a site that had not also upgraded to Receivables 9.2A, incorrectly displayed the warning “Receivables 9.1A (140723); must be at least [9.2A (140723)]” when in fact Receivables 9.1A (140723) was installed and is compatible with Payables 9.2A.

·    Corrected a problem where, after a workstation install was completed, it cycled requiring another workstation install (sometimes cycling without user intervention). This happened in isolated cases on some workstations for systems where Adagio 9.2A/B modules dated in December 2015 or later were installed for the first time at a site, depending on the workstation environment and/or the order in which upgrades and Service Packs were installed. Installing this release will also correct the problem for all other installed modules.

·    In Payables 9.2A (2015.06.09), the auto-workstation install on a new workstation that had not had vitalEsafe installed by a previous install ran again each time you started Payables. Note: the vitalEsafe web based file storage service has been discontinued and this function has been removed from Payables.

·    In Payables 9.2A, the progress bar was missing in some cases when Generating a system check run or Pre-Check Register. This could cause the program to appear to be hung and, if you attempted to close the program during this time, there was an error.

·    If after printing system checks or manual checks you said ‘Yes’ to additional forms, they could not be previewed but only printed.

·    Added new specification codes primarily for use on 1099 / 1096 forms, in particular for printing the address on Copy A (the Federal copy).

M46 Company City, State, Zip/Postal
V72 Vendor City, State, Zip/Postal

·    An Access Violation error occurred if you previewed letters, 1099s or T5018 to screen and then printed them to printer from the preview.

·    In Payables 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 vendor shows them. This has been corrected.

·    In Payables 9.2A, the Adjustment Batch Listing did not print the vendor name when printed in Detail format.

·    In Payables 9.2A, the vendor name was missing in some cases on the Invoice Posting Journal.

·    The Open Payables and Aged Open Payables reports now disable the ‘Zero balance vendors’ option when printed backdated, instead of simply ignoring the option because the vendor balance cannot be calculated as of a particular date. All vendors are therefore included without regard to balance when the report is backdated.

·    In Payables 9.2A, the Aged Open Payables report could not be printed if the ‘Calculate as of’ date used was earlier than the last clearing date.

·    In Payables 9.2A, the Aged Overdue Payables report did not report transactions that were in history.

·    In Payables 9.2A, the percentage totals on the Aged Open Payables and Aged Overdue Payables reports were rounded to the nearest whole number, even though the values are displayed to 2 decimals.

·    In Payables 9.2A, the Aged Open Payables reported Payments applied to invoices printed with the wrong home currency amount.

·    In Payables 9.2A, the Check Reconciliation report did not show the status for void checks nor where they included in the summary section at the end of the report.

·    The G/L Distribution Summary did not print on the Check Reconciliation report in Payables 9.2A.

·    In Payables 9.2A the Check Number Audit List (Checks In Progress) report showed checks that were actually already posted in some cases. In addition, the Check Type field was suppressed when it should not have been.

·    In Payables 9.2A, the Check Number Audit List report did not show the Check Type field for ‘Not Printed’.

·    In Payables 9.2A, the G/L Transaction report and the G/L Summary on the Batch Listing and Posting Journal were sorted incorrectly if you use G/L Departments, depending on the configuration of your Chart of Accounts.

·    In Payables 9.2A for single currency databases, the Tax Tracking report printed on Legal size paper, whether printed directly or from the Preview. This caused the printer to prompt for Legal pager or print on 8.5 x 11 paper with the bottom of the page cut off. The Preview also showed in Legal size. When printed to PDF, the report was compressed to fit the page but printed to 8.4 x 11 paper.

·    In Payables 9.2A, if you selected a different printer tray in the Paper Source on the report dialog when printing checks, the checks printed on the default tray rather than the selected tray. There was no problem if a different tray was specified in the printer driver.

·    After converting data for Payables 9.2A, the Send to A/J settings on the Integration tab in the Company Profile were lost and had to be re-selected. This has been corrected in the conversion. However, if you are integrated to JobCost and have already converted your data you should check the settings.

·    The Data Integrity Check (DIC) now detects vendors with a blank in the Tax Status on the Payee/PO tab. If this field was blank, it caused problems in Adagio PurchaseOrders. The DIC rebuild sets the Tax Status to the first one on file.

·    The Data Integrity Check detects and rebuilds additional errors related to discrepancies between the next batch numbers in batch status and open batch files.

·    DataCare displayed an error when opened after Payables 9.2A was installed but JobCost 8.1C was not installed.

·    Multiselect did not work in the Payment Control function in Payables 9.2A.

·    The Composite tables were missing in the Payables 9.2A data dictionary (@P92A).

·    Relaxed locking for imports. Previous versions would not allow an import if Edit Vendor or batch entry was open, or if a batch was being posted.

·    Added the option 'One detail per entry' to Import Invoices. It can be used when the 'Header fields on each record?' option is on. Use it when an import file contains multiple invoices in a row for the same vendor but an invoice number is not imported; it is generated during import. In previous versions, this would consolidate the invoices into a single invoice entry. Note that if this option is used then invoices with multiple distributions cannot be imported as they would be split into separate invoice entries. In addition, if the Invoice Number field is included in the import and it is not blank, it can be used to split multiple invoices in a row for a vendor for a batch of Invoices.

·    Added ‘Auto-generate invoice number?’ and ‘Invoice number format’ fields to import and export vendor templates.

·    In Payables 9.2A, importing fields such as ‘Advice email method’ with T/F instead of 1/0 caused the import to fail.

·    In Payables 9.2A, the EFT files for various formats / banks were rejected if the length of data in certain text fields in your vendors exceed the maximum length of the associated field for the format used. The EFT file for \\\"CIBC 1464 format CAD\\\" was rejected by the bank in all cases. There was no problem if your EFT Provider was Telpay.

·    In Payables 9.2A, the EFT file created for the ‘Montreal 80 format’ was rejected by the bank.

·    Ships ODBC Connection String utility that can be used to help troubleshoot report problems. Installs OCSTest.exe and ConnectionTesterInfo.pdf in \Softrak\System.

·    When starting Adagio 9.2A versions, the Crystal Reports Runtime (used to print reports) intermittently displayed an error such as “The program can't start because TraceLog-4-0.dll is missing from your computer.” when in fact the DLL file was present and reports did print without problem. Installing Payables 9.2A (2015.06.09) should correct this for all 9.2A modules.

·    Grids may be “banded” with a User Selectable color and banding frequency set under File | User Preferences. Filter Styles may be disabled and replaced with regular banding if desired.

·    Added Filter criteria 'Before today' and 'After today' for Floating Date Range.

·    The status bar at the bottom of the main window now shows activity of various steps when the program is starting up and the database is opening.

·    The Column Editor screen can be sized. The size is remembered by module on the workstation.

·    Supports Transport Layer Security (TLS) / Secure Socket Layer (SSL) for secure email servers when emailing check advices. Added option 'Use TLS/SSL' added to Email Setup function.

·    Updated splash screen with new Adagio logo and colors. Updated icon and toolbar button images.

Vendors

·    You can now find vendors by Document Number.

·    The Find by vendor Phone now shows formatted phone numbers.

·    Vendors now have aging buckets on the Transactions tab, similar to Receivables. They are auto-calculated without having to click a button. Note that these aging fields do not display the values determined by Calculate Vendor Aging -- exactly the same as AR, which does not show the values determined by Calculate Customer Aging. Rather, the values are strictly based on being aged by Due Date as of the session date.

·    A Find Document field and Document Type have been added to the Transactions tab in the Vendor to allow you to search for a particular document using Finder or Smart Finder.

·    Vendor and Payee address fields are formatted, including dedicated fields for City, State/Prov and Country. Addresses can also be unformatted, as may be required for international vendors. The ‘Format Address’ setting is by individual vendor and controlled by default in the Company Profile. If the option ‘North American address’ is enabled, State and Province codes will be validated for North America and the country field will be populated automatically. A final option controls whether the Home country (user specified) is displayed on printed addresses. The company address in the Company Profile may also be formatted.

·    The vendor master record has many new fields and fields have been made larger. New fields include:

Second vendor Name field.
Second Comment line
Last Maintenance User, Date and Time stamp fields available in vendor grids and finders, custom reports and in GridView.

Larger fields include:

Name increased from 30 to 40 characters
Address lines from 30 to 40
Contact from 18 to 30
Comments from 30 to 40.

·    Added Tax Group and Tax Status default fields (used when adding new vendors) to the Company Profile, Batch/Vendor tab.

·    Vendor current and history transactions are now located in a single file rather than 2 separate files. This allows all transactions to be shown on the vendor transaction grid, on a single view in GridView, or on a single custom report.

·    A ‘Both’ option has been added when viewing transactions in the Vendor to allow you to view current and historical transactions in the same grid.

·    Added an option to sort transactions in ascending or descending order by date in the edit and view vendor functions for Current, Historical transactions or both. In previous versions, transactions were always sorted ascending.

·    Added an option to sort transactions by Date or by Type/Doc No. In previous versions, transactions were always sorted by Type/Doc No.

·    Added ‘Total Forced’ and ‘Total On-Hold’ amount fields to the vendor. These fields appear on the Transactions tab in the vendor and can be useful in filters, grids, finders, GridView views and custom reports.

·    Vendors can now have multiple alerts, and alerts can be set to display in specific functions in a specific module. Options on an alert allow them to be disabled once they are displayed, or require a user to acknowledge the alert. User ID’s are stored when alerts are disabled. All alerts for a vendor can be disabled in a single tick box.

·    The vendor Notes grid in the vendor edit and view functions can be sorted to display the most recent notes at the top by right-clicking on the grid and selecting 'Sort Descending'. The selection is remembered.

Edits

·    You can now edit Control Account Sets or change a vendor’s Account Set without having to first purge all the posting journals. For Adagio MultiCurrency databases the new Account Set must have the same currency, unless the vendor has no transactions.

·    You can now edit Banks without having to first purge all the posting journals.

Batch Entry and Posting

·    You can now find vendors by Document Number in batch entry.

·    A unique, incrementing, invoice number can be auto-generated for invoice batch entries by using the %n code in the Invoice Number Format field on the Accounting tab in the vendor. A Next Invoice No. field has been added to enter/show the starting/current value. The number is up to 4 digits and is trimmed. Copy batch, copy entry, import and export vendor, import invoice batch and import manual check batch (cash invoices) are supported.

·    When the ‘Auto-assign document number’ option is enabled in the Company Profile, the document number generated for invoice and adjustment batch entries now includes the year. The format is year, batch and entry number (YY-BB-EE). This avoids potential duplicate numbers with transactions entered in previous years.

·    The Distribution field is now hidden on the invoice batch detail screen if there are no Distributions on file. This speeds entry by eliminating an extra tab key or mouse click on each detail if you do not use Distributions. The Dist. Set button is hidden on the invoice batch entry screen if there are no Distribution Sets on file.

·    Adagio JobCost users can now control the information sent to the Reference and Description fields in JobCost batches created by Payables, including vendor number, vendor description, Document Number, and Document Reference and a User Defined format. The fields ‘Send to A/J reference’ and ‘Send to A/J desc.’ have been added to the Integration tab in the Company Profile. The 'User defined' option allows you to format the fields using a combination of fields from the transaction, batch information (posting sequence, batch number, entry number), Job/Phase/Category, Time&Billing fields and free form text. Click on the field in Help for the list of codes.

·    Added the option ‘Allow posting to control account’ to the Integration tab in the Company Profile. It is disabled by default to prevent you from (accidentally) entering GL accounts used in Control Account Sets GL account during batch entry. Batch posting also checks this.

·    You can now add Vendor Name and other fields from the vendor to the batch grids using the Column Editor. The Vendor Name is included by default.

·    The Job Description and Estimate Description can be shown in the Job/Phase/Category finder in batch entry.

Ledger Interface

·    Payables 9.2A is fully compatible with the new feature in the Ledger 9.2A Retrieve Subledger Batches function that allows separation of subledger batches on retrieve by Posting Sequence or Batch Number. For earlier versions of Payables, if the subledger batch contains transactions for system checks, reversed checks, checks cleared with error, or NSF Checks, revaluations or period end clearing entries, the Retrieval file cannot be separated by Batch.

Specification Designer and Printing Checks, 1099s and  T5018s

·    Added ‘Print one check per invoice’ option to the Accounting tab in vendors. Set this option to cause the System Check Run to print one check per invoice for the vendor rather than one check paying multiple invoices.

·    You can now add Vendor Name and other fields from the vendor to the grid on the Payments tab for System Checks using the Column Editor. The Vendor Name is included by default.

·    The check specification designer has been updated to support new vendor formatted address fields and increased length of some fields. Your existing checks and other forms will print without requiring any change. However, you may want to change your existing specifications to use address formatted fields or adjust the widths of the fields on the forms.

·    The description of specification codes V02 to V06 and V14 changed from “vendor” to “check” to reflect that these codes actually print fields from checks not vendors.

·    Added new codes to the specification designer for formatted addresses and other new fields in vendors:
     Vendor address line 1..7 (compressed)                          Vendor City
     Vendor address 1..7 (formatted)                                   Vendor State/Province
     Vendor Name 1                                                            Vendor Country
     Vendor Name 2                                                            Vendor Comments 2
     Vendor Name 1 + 2                                                      Vendor I.D. number – partial

·    The new Vendor formatted codes make it easier to remove blank address lines and have the Zip/Postal Code on the same line as other fields.

·    Added new spec codes for formatted address from Company Profile:
     M27..33 Company address line 1..7 (compressed)
     M34..40 Company address 1..7 (formatted)
     M41 Company City
     M42 Company State/Province
     M43 Company Country

·    New specification codes added to show the user who printed checks, advices, 1099s and T5018 forms:
     M44, current user code
     M45, current user name

·    Add specification code "V66 Vendor I.D. number - partial" to print the last 4 digits of the Taxpayer ID Number on 1099s. The last 4 digits are printed and the rest are asterisks.

·    If a System Check Run is in progress and the EFT status is changed for a vendor, clicking the EFT/Post button will detect that a vendor status has changed and present a message stating a new payment list will be generated.

Reports

·    Added Aged Open Payables report. The report is similar to the Aged Overdue Payables report but for Open Payables. It can be aged by document date as well as due date and can be calculated as of a prior date. There is an option to include Applied Details.

·    Posting Journals can no longer be cleared after printing. This avoids accidental clearing. Posting Journals are cleared at year end. The 'Allow Post Journal Purge?' option has been removed from the Company Profile.

·    Running Period End no longer precludes the printing of the Aged Overdue Payables report or the new Aged Open Payables reports for an earlier period.

·    A new ePrint code %CDT is available to put the Calculate/Aged as of date into either the PDF filename or folder name for reports such as Open Payables and Aged Overdue Payables.

·    Added an option to print a General Ledger Distribution Summary on batch listings.

·    Added finder and smart finder on the Vendor Name on report dialogs to allow look up by name for a range of vendors.

·    The Posting Journals were changed to use a single format regardless of whether Payables is interfaced to JobCost, Time&Billing or neither. This allows the same GridView views and custom reports to be used for any AP data regardless of interfaces.

·    A Batch Description field has been added to Posting Journal records for use by custom reports or GridView.

·    The Distribution Sets Report now prints the Job/Phase/Category for Job cost type Distribution Set Details.

·    Adagio Payables’ standard reports are now created using Crystal Reports 2013, replacing the Crystal Reports 8.5 Print Engine (CRPE32.dll). The module’s management reports are now stored in \Softrak\ Payables\StandardReports. Revisions to these reports should be placed in \Softrak\ Payables\ModifiedReports. Custom reports to be added to the Reports menu should be stored in \Softrak\ Payables\CustomReports. Reports must be edited or created using Crystal Reports 2011 or 2013 and Adagio ODBC for access to the data files. Users will notice minor changes to some of the visual elements in the module and a new Print Preview window. The size and position of the Print Preview window are now remembered between sessions by user, so the Workstation Options controlling this function have been removed. Exporting to an Excel spreadsheet from the print preview window has been significantly improved. The Report Tables Drive settings and Crystal tables in the \QRASP folder are not used by version 9.2A modules.

·    An updated version of Adagio PrintTool (PT) is installed in \Softrak\PrintTool. PT allows you to print / preview custom reports without needing to run Crystal Reports itself or without placing the report on the Custom Reports menu in an Adagio module, and allows reports to be placed on the Windows desktop. PrintTool 9.2A prints custom reports created with Crystal Reports 2011 or 2013 only. Adagio ODBC must be installed to create custom reports but is not required to print custom reports. Your Adagio dealer or consultant can create custom reports for you and deploy them at your site. PT allows you to specify a report to print on the command line using the /r parameter. This allows Adagio automation batches to print custom reports (to printer – a future release of PT will allow automation batches to print custom reports to PDF). PT does not require registration with Softrak Systems but does use Adagio Lanpak licenses. Note: PT does not print reports created with Crystal Reports 8.5 for Adagio. Existing version 8.5 custom reports must be converted before they can be printed by 9.2A.

Maintenance and Miscellaneous

·    Added Delete Inactive Vendors function. The option ‘Exclude vendors with historical transactions’ allows you to delete vendors with history transactions (vendor history does not need to be purged first) or conversely use it to delete only vendors with no history. The ‘Select vendors already flagged as inactive’ option can select vendors based on the ‘Active’ flag in the vendor.

·    Added Date/Time/User Created and/or Last Maintained fields to vendor and other files, including adding batch fields from the batch status to transactions. These fields can be used in grids, finders, GridView and custom reports.

·    When revaluing your accounts payable in an Adagio MultiCurrency site, prepayments are now included in the revaluation.

·    The Data Integrity Check (DIC) saves results for the last 9 previous runs in files APWINERR01..09.dat (where .dat is your company data file extension). The current DIC information will always be in APWINERR. If you do check/rebuild/check without closing the DIC function the results are appended to the same file.

·    Adagio Checks databases can be converted to Payables, including Vendors, Banks, Distributions and Check Specifications. When creating a Payables database, if Adagio Checks database is present, it will ask if you want to convert it. A default Control Account ‘CHECKS’ and default Terms Code ‘CHTRMS’ are created. These defaults can be changed during creation. The Checks 'Default bank code' is transferred into the 'Default bank for manual checks' in Payables.

Import / Export

·    Import Vendors now allows updating the Control Account Set without having to first purge all the posting journals. The vendor balance must be zero and for multicurrency databases the new Account Set must have the same currency, unless the vendor has no transactions.

·    New export templates created for Excel format default the file extension to .XLXS rather than .XLS as in prior versions.

Problems Fixed

·    When the Transaction details for an Invoice were changed through Vendor Edit, an invalid date message would appear on tab out of the Discount Date field if it was blank.

·    When the first document in the Current transactions list is an Invoice and the Transaction details are edited to change the Document status, the Status in the list of documents did not immediately display the new Invoice Status

·    When T5018 was enabled for a vendor, if additional characters were added in the Identity Number field beyond the end of a valid GST number (which is allowed) there was a validation warning in some cases and the vendor could not be saved.

·    When viewing PDFs for Invoices created by PurchaseOrders in a vendor, if a Receipt and Invoice/Adjustment had the same vendor document number, when you viewed the Invoice/Adjustment PDF the Receipt was displayed instead.

·    When entering a GL Account / Department in a batch, validation did not work and no warning was given when you entered a Department that did not exist for an Account -- if that Department did exist for the next highest Account. For example, you had account 8000-150 and the next account in the chart is 8001-250, then entering 8000-250 did not give a warning.

·    If the ‘Calculate base for discount with tax included?’ option is enabled in the Company Profile and a credit note with tax was posted to an invoice, the discount base of the invoice was updated by the full amount of the credit note instead of the amount net of Tax.

·    For Manual Check Payments, the Maximum Payment for invoices was being ignored. The Current Balance was defaulted as the Payment Amount. If the Check date made it eligible, Discounts were calculated. Manual Checks now matches System Checks; the Payment amount is now limited to the Maximum Payment and Discounts are not calculated when the Maximum Payment is not equal to the Current Amount.

·    For Letters, the Email files created in the SOFTMAIL folder did not have the full vendor code in the PDF file name (although the attachments were correctly emailed.)

·    The Vendor Transactions and the aging reports did not include vendors if the Short Name field had an extended character (e.g. French character with accent) in the first character position.

·    The Data Integrity Check checks for and corrects information in address fields used by TelPay that may result from incorrect import of vendors when using export / import to configure vendors for Telpay EFT.

·    In some cases in the Payables 8.1F when a dataset was newly created or converted from DOS versions, the Bank files were not created properly. This caused the Banks grid to show no banks and errors when you tried to add a bank.

·    In some cases in MultiCurrency datasets, period end was not correctly updating the Period End Clearing posting journal with the clearing entries.

·    In some cases, the displayed name of the EFT provider on the EFT tab in the Company Profile did not match the format selected in the System Options tab.

From previous Payables 8.1F Hot Fixes

·    The EFT file for "CIBC 1464 format CAD" was rejected by the bank.

·    When posting batches using automation, if the 'Require batch print before posting?' option was enabled, batches that had not been printed caused the automation job to abort and no batches were posted. Batches that have been printed are now posted, unprinted batches are skipped, and the automation job does not abort. This allows the print status to be used to control which batches will be posted. In a future release of Payables, batches will be able to be marked 'Ready to Post' to control posting during automation, similar to other modules such as Ledger.

·    Adagio JobCost 8.1C users received the error "Unable to find data dictionary Phase @J81APHA, (1212)" when printing an invoice batch listing in Payables 8.1F, if JobCost 8.1A or 8.1B had not been previously installed.

·    In MultiCurrency sites, where the Open Payables or Overdue Payables report were backdated, the home amounts were incorrect even in simple cases. This has been fixed. However, in the event of multiple revaluations against partially paid invoices, it is unlikely that these reports will ever tie to the AP control account for a back dated period.

·    The T5018 form template has been updated and changed from 3-part to a 2-part. A minor change to the T5018 Summary forms templates has also been made. You will need to create a new T5018 specification file for your company database(s) using the new template and adjust as (or if) needed for correct field alignment on your printer. The sample data is not updated by the Hot Fix but you can created new sample specifications from the new templates if needed.

·    The PDF Viewer available to Adagio ePrint users in the vendor edit and inquiry functions did not show PO transactions that were Invoices posted as Invoice/Adjustments, as well as invoices posted as Receipts.

·    Adagio JobCost 8.1C users received the error "Unable to open data file @J65JOB, (1213)" when trying to create an invoice in Payables 8.1F if JobCost 8.1A or 8.1B had not been previously installed.

·    For Crystal Reports for Adagio users, the Custom Reports menu was missing in Payables 8.1F (2013.08.26) when you had custom reports in the \softrak\apwin\customrp folder.

·    In Payables 8.1F (2013.08.26), the Vendor List report printed details multiple times if the vendor had an alert containing more than one line of text.

·    Printing a report caused 'APPublicFavorite' to be inserted in the Style Finder. This caused all the styles listed below to use different colors/styles and could cause vendor styles to be incorrect.

Enhancements and revisions in Adagio Payables 8.1F (2013.08.26)

New Features

   Adagio ePrint users can view a PDF of Adagio PurchaseOrders documents from the AP and PO current/archive transaction grids in the Edit / View Vendors functions, including POs, Receipts, and Inv/Adjs . The documents open in the new Adagio PDF viewer.

   You can attach files (such as a promotional offer) to advices or letters in the email queue. Attachments are shown in a tree view on the Edit Email Entry dialog. Right-click on the tree to attach a PDF, Word, Excel or other types of files. Multi-select is supported, allowing you to add files to all receipts in the queue.

   Supports Automation when Adagio Console is installed. Automation allows you to automate many functions in Adagio modules, including posting, importing, printing reports, backup and integrity check, etc. across modules, and view, print or email the results from an automation log.

   Supports the Auto-fill GL account and department options in Ledger 9.1A.

   Locking has been relaxed while printing checks, allowing users to use certain other functions that were previously not allowed.

   New splash screen with an updated look.

   A 'Report set' button has been added to the toolbar.

   Added new expansion codes for Report Favorite filenames for Adagio ePrint users: %CMP (company name), %CNO (company number), and %EXT (data extension).

   Added new AP specific Styles for use in filters. The default Filters (used when a new database is created) have also been updated. The sample data includes new Filters that make use of the new Styles. You can recreate any of the new sample filters you find useful in your own live databases.

   A Listing button was added on the Group Setup window and prints all options or enabled options only for a range of groups.

   The Data Integrity Check results now include the version/date of the program, for example: "Adagio Payables 8.1F (130726)".

   The Help | About function now has a Consultant tab showing the contact information for your Adagio consultant if they have enabled this option at your site.

   Excel Direct can now use Windows "automation" (inter-process communication) to send data to other spreadsheet applications, the same way it interfaces to Excel, allowing all formatting to be retained in the resulting sheet. OpenOffice 3.3 or later and LibreOffice® 3.3 or later are supported. This interface must be manually enabled. The file SSI2XL.INI must exist in \softrak\system and must contain the section [Initialization] with an entry <computer name>-UseOpenOffice=1, where <computer name> is the name of the machine that this entry references. Refer to the Readme Help for further details.

Problems Fixed

   You can now view the applied transactions in the Transactions grid without using the mouse. Opening the Transaction tab puts immediate focus on the grid, so Alt-A can be used without tabbing to view a particular transaction, or use the cursor keys to highlight a different transaction.

   After creating a new vendor, other users or Adagio programs were not able to access that vendor until you closed the Edit Vendor function.

   Deleting a vendor with a P/O Balance (but no outstanding balance or transactions) is now prevented.

   Changes to the Discount Rate made from the Transactions grid when editing a vendor were not being saved unless the Discount Base / Discount date were also edited.

   If an invoice date older than 30 days from the session date was entered in a batch for a vendor with the 'Auto-generate invoice number?' option enabled, the invoice number was not regenerated using the date entered.

   When entering invoices in Payables 8.1E with JobCost 8.1C you received the error "Unable to find data dictionary Alert Functions @J81AART, (1212)" in some cases.

   Posting a Cash Invoice no longer sends zero dollar transactions to Payables account to the GL.

   Corrected a problem with sending the Time&Billing User Defined % codes from Payables to Ledger on a Manual Check (MC) cash invoice.

   Manual Check posting in Payables 8.1E was not sending information to the Description 2 field in the G/L transaction batch.

   The XML file created for T5018 electronic filing was rejected in some cases.

   Specification code G01 "G/L Acct-Job# - Dist Code" truncated the Job-Phase-Category when the full 6 characters were used.

   The Description entered when a check was reconciled did not print on the Check Reconciliation report after the reconciliation was posted (although it did print while the transaction was pending).

   Voided Manual Checks displayed in the Check Reconciliation with the cents truncated in the amount.

   The report filename codes (ex. %FYR) were not being saved in report favorites.

   The %PJN code did not work when printing the Check Reconciliation Posting Journal to a PDF file with Adagio ePrint.

   The new option 'Show description 2' for the Print/Consolidate GL Transactions report in Payables 8.1E was not working.

   Import Vendors now supports importing multiple email addresses (separated by a semicolon) in email fields.

   Importing the Next Year 1099 field for vendors did not populate the Next Year T5018 field.

   The window title in the dialog box displayed after creating an EFT file showed the wrong bank in some cases.

   When creating a new multi-currency database or enabling multi-currency you must now enter a Default Rate Type.

Enhancements and revisions in Adagio Payables 8.1E (2013.01.31)

   Added P/O Balance field on the Statistics tab in Edit/View Vendor functions . Outstanding PO's are included in the P/O Balance. The P/O Balance includes: a) all items backordered on PO's, b) all items received but not invoiced, and all items (including tax) invoiced but not processed by PO Day End.  Note: the value in this field is only correct if Adagio PurchaseOrders 8.1C is used.

   When entering a negative invoice, a negative discount base could not be entered. System Checks and Manual checks for Payments will now use the negative discount base to calculate early payment discounts.

   In Payables 8.1E, the Payment Control function would not accept a Report Group of less than 6 characters in the range.

   The warning message displayed when you enter a session date in the future or more than 30 days prior to today was changed from "Date is more than 30 days prior to, or later than, today." to "Date is more than 30 days prior to today or in the future from today.". This helps avoid confusion when the date entered is in the future but less than 30 days in the future.

   When entering multiple distributions in a batch entry for a vendor with a mix of blank Distribution Codes and Distribution Codes with a blank default expense Account/Department, on the detail for a Distribution Code, entered after a detail with a blank Distribution Code, the tab went directly to the amount, skipping the Account/Department fields.

   Entering a Check Number with 2 or more period characters in a manual check caused a floating point error message and crashed the program.

   In Payables 8.1E, the Active Users function showed only the first instance of the first module other users had open.

   In Payables 8.1E, the Email, Website, and the 2 style code fields were added to the Vendor List and Statistics report but were included in the Address section instead of the Profile section.

   Payment files created by Adagio EFT for C.I.B.C. using the "CPA Standard 005 1464 format CAD" that were previously accepted by the bank were rejected. The EFT file has been changed and is now accepted.

   In Payables 8.1E, the Open Payables report was slower than in previous versions in some cases if printed on the date of the last Period End. This has been corrected.

   Payments applied to postdated invoices were moved to history by Period End but the invoices were not. Such payments were not shown on the Open Payables report, unless it was backdated, and the therefore the report did not balance to your GL in this case.

   Manual Checks and Reversed Checks posted the source currency into the home currency field, causing the Tax Tracking report to be incorrect for multi-currency databases.

   The Purge Vendor 1099 function now clears the YTD 1099 payment total for vendors who have Process 1099s off but previously had it on, and therefore had payment totals on file. Thus if 1099s are enabled again in the future the totals will correctly start at zero.

   The Entry Date in the AP GL Disbursement file was set to the Rate Date of the invoice rather than the Document Date.

   In Payables 8.1E, the GL Distribution for transaction details showed extra details in some cases.

   In Payables 8.1E, the amount for GL Distributions for transaction was truncated to .00 cents rather than the correct figure in some cases in multi-currency databases.

Installs an updated version of the Adagio Data Source (ADS) that improves the handling of certain integrity problems in Adagio data files, minimizing the impact of damaged data. When this release of Payables is installed the Adagio System Updater (2013.01.09) is not required.

Enhancements and revisions in Adagio Payables 8.1E (2012.11.13)

New Features

   The option 'Calculate as of' option has been added to the Aged Overdue Payables report. This allows you to cut off future-dated transactions rather than aging them into current. It also allows you to print the report as it would have appeared at a date in the past. This allows the report to be reconciled to your G/L for any period, which is often a requirement when reporting to your bank or accountant. Note: to obtain the desired result on the backdated report, you must not have purged transactions from history that are required by the report for the date selected.

   The Open Payables report now allows you to select a 'Calculate balance as of date' earlier than the Last Clearing Date (set by the Period End and Year End functions). The report will be accurate providing you have not purged history past the selected date. Note: for Multi-currency sites, the Home amounts may not be correct due to revaluations and you may want to print the report for Source amounts only.

   For Canadian users, Payables tracks T5018 payment totals and prints T5018 forms for vendors who are your subcontractors. The T5018 Recipient Type in the vendor can be set to Individual, Corporation or Partnership. The S.I.N. or F.I.N. can be entered for Individuals/Partnerships. These fields are encrypted in the database and are only available in the Edit and Vendor functions to the SYS user or users belonging to a Security Group where the 'Edit Vendor SIN/FIN' option has been selected. The File T5018 Forms option in the Maintenance menu allows you to export T5018s to an XML file for electronic filing with the appropriate government department.

   Updated 1099 and 1096 templates and in sample data with changes for 2012.

   These new codes were added to the specification designer for use on T5018, 1099 and related forms:
      M25 T5018 Language  (E or F)
      M26 Company contact email
      V13 Vendor YTD 1099 /T5018 Payments (not a new field but now used for T5018s as well as 1099s)
      V23 I.D. number (DS), where "DS" means double-spaced
      V45 Vendor YTD 1099/T5018 Payments Dollars
      V46 Vendor YTD 1099/T5018 Payments Fractional Amount
      V47 Vendor I.D. number (DS)
      V48 Vendor S.I.N.
      V49 Vendor S.I.N. (DS)
      T01 # of 1099s/T5018 (not a new field but now used for T5018s as well as 1099s)
      T02 Total of 1099s/Tt018 (not a new field but now used for T5018s as well as 1099s)
      T03 T5018 ID / Account number
      T04 T5018 ID / Account number (DS)
      T05 T5018 Period ending
      T06 Total of 1099/T5018 Payments Dollars
      T06 Total of 1099/T5018 Payments Fractional Amount

   Added an Edit Report Groups function. The conversion to 8.1E scans the vendors and automatically creates the Report Groups encountered. The Report Group fields in the vendor, in ranges on reports and in the System Check run are now a finder file. The 'Verify report groups?' option has been added to the System/Report Options tab in the Company Profile. It defaults to off on conversion to 8.1E (so that the behavior is the same as in earlier versions). A Report Group report has been added.

   You can now change the Invoice Status to Forced, Hold or None from the grid on the Transactions tab in the Vendor (assuming the user is allowed access to Payment Control). Select or multi-select transactions, right click and change the status. This is faster than having to open the details screen for each transaction or use the Payment Control function. The Edit button is now available on the Transactions tab so you can view vendors using Next/Previous and then change to Edit when you want to change the transaction status.

   New fields for use by Adagio PurchaseOrders 8.1C (to be released at a later date) have been added to the vendor. These fields are only visible when PurchaseOrders 8.1C is present (they are not supported by Purchase Orders for Adagio). Send Method (Print, Fax, Email), Print Spec, Fax Spec, Email Spec and Email Cover will appear on the Payee/PO tab. The 'Receive to location' field appears on the Accounting tab.

   For legacy reasons, Adagio Payables has always made the assumption that, if the entire invoice is not paid, the invoice was likely in dispute, and subsequently set the Maximum Payment amount to 0.00 (again assuming that the remainder of the invoice would not be paid). As a result, in order to pay the invoice, you had to go into Payment Control or the transaction detail in Edit Vendor and change Maximum Amount to reflect the balance of the outstanding invoice. This behavior is now optional. The 'Set Amt Payable to Inv. Balance' option has been added to the System/Report Options tab in the Company Profile. It defaults to off on conversion to 8.1E.

   Creating a $0.00 manual check to match prepayments to invoices no longer creates $0.00 G/L transactions.

   Batch entry supports Estimate styles in finders for Adagio JobCost 8.1C.

   Batch entry supports Docket Active status and Docket Styles in finders in Adagio Time&Billing 8.1C.

   Batch entry supports the customer code options Uppercase, Auto-fill and Customer Code Format when entering Time&Billing related transactions for Clients.

   The batch entry number is now displayed in the title bar of the batch entry window. This helps you keep your place when entering transactions from a list on paper. For example, for new batch entries it displays 'Invoice Batch X, New Invoice (Entry 1)'. When editing an entry it displays 'Invoice Batch X, Invoice 123456 (Entry 1)'.

   Excel Direct button has been added for the grid in the Check Reconciliation function.

   Added the option 'Show description 2' to the Print/Consolidate GL Transactions report. Transactions with a second description take 2 lines on the report.

    Added % codes for the User Defined format to send to G/L Description 1 and G/L Description 2 on the Integration tab in the Company Profile:
      dst - Distribution
      cln - Time&Billing Client
      dkn - Time&Billing Docket
      dis - Time&Billing Disbursement
      src - Time&Billing Source Code

   Added option 'Delete vendors with history' to the Batch/Vendor tab in the Company Profile. Deselect this option if you do not want to allow vendors with history transactions to be deleted. In previous versions, vendors with no current transactions but with history could always be deleted.

   The Adagio menu now includes the module from which it was selected to allow you to quickly open another instance of the same module.

   The number of Previously Opened databases (saved by user) has been increased from 25 to 100.

   The backup function now includes open data files if you proceed after getting the message "Unable to lock data set exclusively, do you still want to perform backup?" This message is displayed when other users have Adagio programs open for the same company. The zip file will contain the complete set of files but there is no guarantee that the backup will be viable. In general, backups should only be made when there are no other users in Adagio.

   The speed of backup to zip file has been improved by approximately 25% across a LAN and 400% with local data.

   The Open Data screen can be sized horizontally to allow you to see the full data path.

   The F1 key now launches Help when no windows are open.

   The session date is now passed to GridView views (workspaces) loaded from the Inquiries menu.

   The Data Integrity Check now checks the Common Files as well as the AP files. Previously these files were only checked by DataCare.

   The Data Integrity Check (DIC) now checks History Transactions during the Application Integrity Phase. The first DIC run after upgrading to 8.1E (including DataCare) may detect errors that were not previously reported. The DIC rebuild function can add transaction matching records missing from history due to previous database problems. This can correct problems in the Aged Overdue Payables report when printed with the new option 'Calculate as of' option. See the "Upgrading to 8.1E' section in the Release Notes for important information regarding these changes.

   The Data Integrity Check now displays "Checking Index x of y" on files with multiple indexes so for large files you know it has to cycle through the records multiple times and which pass it is currently on. For example: "A/P Transactions 1234 of 45678 (Checking index 1 of 2)".

   The '1099 Vendors' filter in the sample data was updated to include the fields 1099 Type and Vendor Tax ID number. Use this filter to see at a glance who is missing a Tax ID and who might not be set up as the correct type.

   Station Logs now indicate memory information for the station or Remote Desktop Services session in these variables:

Total Memory       - total Mbytes of physical memory
Available Memory- free Mbytes of physical memory
Memory Load       - percent of memory in use.

   Station Logs now show the bitness of the application and the station OS in the variable "Environment".

Problems Fixed

   The behavior between Payables and Receivables on the Transactions grid was inconsistent. Now in the Vendor Transactions, when you press Enter and the grid has focus, the Applied Details is opened instead of the function closing, the same as for the Customer in Receivables.

   Changing the Invoice Status (Forced, Hold, None) for a transaction in the Edit Vendor function now causes the message "A new payment list will be generated, due to a change in the parameters" to be displayed in the Print/Post Checks & Advices function when you select Print/Post or print the Pre-Check Register report.

   Job Alerts did not pop up in batch entry in Payables 8.1C and 8.1D.

   An adjustment to a credit note (in current transactions) could not be posted if an invoice with the same number existed in history.

   The warning message 'Please enter a valid account' appeared in Invoice Batch Entry if User Preferences were set to ‘Auto add items’, the account finder was set to ‘Active records only’ and an account with a department was overwritten to an account with no departments by typing in the field.

   The Invoice batch entry grid size was not remembered when the entry screen was resized.

   The 8.1D (2012.08.14) Service Pack fixed a problem where a Manual Check cash invoice having multiple account distributions was rejected by TelPay However, once that fix was made it exposed another problem that existed in the product and the Telpay batch was still rejected. This has been corrected.

   If you printed a set of 1099's and 1096's, then before exiting out of the function, you printed another set, the 1099's forms printed as 1096 forms.

   The %PJN code did not work when printing the Check Register to a PDF file with Adagio ePrint.

   The Report Set detail was not picking up the default filename from the Favorite for Posting Journals.

   Changes to the order of the Sort By fields on Transaction and Analysis reports were not remembered when the 'Remember Report Settings' option was on and reverted to the default the next time the report was printed.

   The legend on the Batch Listing report now includes the 'e' code, which indicates the terms have been changed.

   Error Posting Journals were not printing in Payables 8.1D.

   The Original Amount field on the Open Payables report in Summary format printed blank.

   Aged Overdue Payables report did not do a page break on the primary sort.

   The Discount Percent field in the Current Vendor Transactions table for Crystal Reports for Adagio had the wrong number of decimals.

   The Data Integrity Check does additional checking of the Batch Control file. In previous versions, a certain type of error that prevented you from editing a batch was not detected.

    The Search tab was missing in Help.

New Features

   Added HSBC bank format for EFT add-on.

Problems Fixed

   An EFT Manual Check cash invoice having multiple account distributions was rejected by TelPay

   System Checks has been revised to work the way it did prior to the 8.1D release. Selecting ‘Take discounts if available’ will only include invoices with a ‘Discount date’ that is on or before the ‘Due date on or before’ date.

   The  EFT / TelPay sequence number was not updated in some cases when other users were in Payables at the time EFT payments were processed.

   The Company Name was not displayed in the Payables window title in 8.1D in some cases when multiple different companies were open concurrently.

   Post-dated manual checks (Cash Invoices) beyond expiry date of the Not For Resale (NFR) version are now allowed for use by Softrak business partners.

   Editing a vendor from within in batch entry used a Lanpak license when it should not have.

   If you had Payables 8.1D installed and you use Purchase Orders for Adagio, and likely only if your purchase orders data was originally created with a certain version(s) of the DOS Inventory Receipts program, the Tax Status on the Accounting tab in the vendor did not display correctly and could become set to the wrong value if you saved the vendor. If you have the problem, the Tax Status list will not show all the possible tax status values you have defined in Purchase Orders. The first tax status will not be displayed as a choice in the list. If it is there you do not have the problem.

If you have changed the field and saved the vendor, the wrong tax status has been saved. In addition, if the vendor was set to the last tax status in the list, the status displayed as the one above it. If you saved the vendor, the wrong tax status has been saved.

You should check the Tax Status of vendors changed by Payables 8.1D to ensure they are correct. To identify vendors that have been edited, use the column editor and add the field 'Last Maintenance Date' to the grid. You could also do a smart finder search or create a vendor filter to select vendors where this date is after the date you first used Payables 8.1D. If you are uncertain what the Tax Status should be for a vendor, view an existing purchase order for that vendor and note the Tax Status shown on the Details tab.

NOTE: Even if you do not have the problem described above, if you use Purchase Orders for Adagio and you installed Payables 8.1D (2012.01.14), you must read the Release Notes for (2012.01.31) and check for the problem described there (see below).

• If you use Purchase Orders for Adagio and you edited a vendor in Payables 8.1D (2012.01.14), the Tax Status on the Accounting tab displayed as blank and became corrupt if you saved the vendor. The vendor Tax Status on purchase orders created for the vendor was also blank and tax was not calculated. Note: there is no problem when vendors are edited from Purchase Orders.
  
  Purchase Orders users must install this release before using Payables 8.1D.
  
  If you have edited vendors before you installed the Hot Fix you will need to correct any vendors you edited from Payables by editing the vendor, selecting the correct Tax Status, and saving. To identify vendors having this problem, use the column editor and add the field 'I/R Tax Status' to the grid. It will display as 65535 for vendors with the problem. If you a have large number of vendors you could use the smart finder to search your vendors. To do this, add the field 'I/R Tax Status' to the smart finder grid and search for 'greater than 9'. If you are uncertain what the Tax Status should be for a vendor, view an existing purchase order for that vendor and note the Tax Status shown on the Details tab. You should correct vendors immediately after installing this version. When you save vendors with the problem, the Tax Status will be changed to zero from 65535, limiting your ability to identify vendors with the problem.

   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. Favorites can be private to the Adagio user or public for use by all users. 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.

   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 (when Adagio ePrint is used). Report Sets may be launched from a command file or a scheduled Windows task by running APWIN.exe with the parameter /R followed by the Report Set (ex. /RMonEnd). 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 month end reports.

   When Payables is integrated with Purchase Orders for Adagio, the Status field for Tax Group is now a finder that lists the descriptions of the tax statuses from the PO company profile rather than just a digit from 0-9.

   Most Access Violation (AV) errors are now recorded by module in an exception log text file. The file is located in the program folder for each module. For example: \softrak\apwin\apwin.error.log or \softrak\ledger\ledger.error.log. When any Adagio module with a date in 2012 is installed the exception log is enabled for all other modules. An AV error is a generic error that can occur in Windows applications. This occurs when a program tries to access memory that cannot be addressed, which can happen for many reasons, including software or hardware/network problems. The address, program (EXE or DLL), form, and version information contained in the log will assist Softrak in tracing a problem if the address is located in the Adagio application code.

   The System Status function can create a snapshot of detailed information about your Adagio installation and package it in a single zip file that can be sent to Softrak Technical Support or your Adagio dealer to assist them when answering questions or tracing problems. The information includes: Adagio install logs, program INI files and logs, system INI files and logs, directory listings of Adagio folders, versions and dates of all Adagio programs and system files. To create the snapshot zip file, select System Status in the Help menu, proceed when prompted and click the System Snapshot button at the top left of the Status of System screen. The zip file will be in the \softrak\system folder, located on the drive where Adagio is installed. The filename contains a date and time stamp, and is of the form AdagioSnapshotYYYYMMDD_HHMM.zip. The zip does not take any of your Adagio database files.

   The Payables program icon is more consistent with the look of other Adagio icons and the size of the "ap" letters has increased, making the icon easier to recognize at a glance.

   The Help | About screen has been redesigned and includes a link to documentation page for the module that shows New Features, What's New video and manuals.

   When Payables is opened after installing an upgrade, a dialog is displayed with a link to a short video highlighting the new features. The dialog is displayed for each user until they tick 'Don't show this message again'. The video also be viewed anytime by visiting the Softrak website. Note: the dialog also appears when Adagio is installed at a new site.

Problems Fixed

   If another user was editing a vendor and you tried to edit the same vendor, and the vendor had an alert, the alert popped up even though you are prevented from editing the vendor.

   In some cases, for check specifications where the 'Auto size field' property was enabled on the field, the Check Date field position moved slightly on each check after printing several checks.

   You could not enter a dash or other alpha characters in the Check Number (for non-printed checks) for a payment, even when the 'Alphanumeric manual check numbers?' option was on in the company profile.

   When importing vendors, a blank Distribution Code field is now permitted, allowing you to specify a default Distribution Code for some vendors but not for others.

   After changing the format for a date field set to User-specified, if you closed an import template after the change without explicitly saving it first there was no warning that a change was made and the change was lost.

   The Data Integrity Check now detects and rebuilds errors when Payment (PA) or Manual Check (MC) transactions have a Current Balance, which can be caused by rebuilding from another type of error in some cases. These transactions will be changed to a Pre-Payment (PP), which allows you to manually match the restored Invoice (IN) to the PP via a $0 manual check.

   Several minor problems and inconsistencies with other modules related to ePrint functionality in Payables have been corrected in this release. This includes some small new features. If you are using Adagio ePrint, Payables 8.1D or higher is recommended.

   Installs a new version of the Adagio Data Source (ADS) that fixes a problem where you may have received an error saying you are out of Lanpak licenses when this is not the case. The Licensed Users field on the Help | About screen in Adagio modules showed a huge and incorrect number of licenses in use when this happened. This error occurred in some cases when you edited vendors, customers or items from modules other than AP, AR or IC.

   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 Payables 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.

   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.

New Features