Recalculate Customer Data and the Recalculate Vendor Data functions have been further optimized in this version release.

In previous versions, the system accepts payments to invoices with dates earlier than the invoice date or payments from an open credit for which payment date is earlier than the open credit transaction date. Certain Accounts Receivable reports may generate balances that are difficult to understand.

In this version release, the Apply Payment function is enhanced to add validation to compare the apply date and transaction date. The system will not allow payments to be applied on a date earlier than the invoice date. The same validation applies to open credits. When open credits are applied, the apply date cannot be earlier than the invoice or open credit transactions.

There are a few discrepancies in the Bank Reconciliation Report which makes the report difficult to use for verification of data.

In this version release, the report is changed to correct the following information:

• Record count and total amount for Deposits In-Transit and Outstanding Checks to reflect unverified bank transactions only.
• Generate the Bank Reconciliation Report for the selected bank account regardless of the bank reconciliation status - finalized, completed, pending, or not reconciled.

In previous versions, any bank # can be used when shipping sales orders and/or generating the AR invoices.

In this version release, the system is changed to confirm that the Available in Sales Order and Receivables settings for the bank # used in the Ship Sales Order and the Generate Invoice from Shipment is marked on the bank master record; otherwise the transaction will not be processed.

In previous version releases, Create PO by Item function prompts the user to confirm if Pay Code change should affect the other line items in the Purchase Order regardless of the number of line items attached to the Purchase Order.

In this version release, the system is enhanced to suppress the message prompt if the Purchase Order has only one (1) line item. Changing the Pay Code for a Purchase Order with multiple line items will continue to bring up the message:

Do you want to change the pay code of all line items with this vendor?

Clicking "Yes" confirms that the Pay Code change applies to all line items in the Purchase Order. Clicking "No" means that the Pay Code applies to the selected line item only.

In previous versions, accessing an AP Invoice through the Amend AP Invoice function shows the System Date as the Post Date if the invoice is paid in full through Apply Prepay.

In this version release, the system is changed so that the Post Date of the AP Invoice is retained in the Amend AP Invoice function. User will need to change the Post Date if he/she needs the Post Date to follow the System Date.

In previous versions, Bill of Materials Report will include parent items that are already archived.

In this version release, the system is changed so that archived parent items are no longer included in the Bill of Materials Report.

In the previous version, the system does not allow changes on the GL Account IDs assigned to each of the earning code(s) in the following functions: Time Card/Piece Work, Apply Payroll/Payment, Post After-The-Fact Payroll, and Amend Applied Payroll.

In this version release, the system is changed to allow users to edit the GL Account IDs assigned to the earning codes when processing payroll/payment transactions. The GL Account IDs are shown in the GL distribution grid. For the Time Card/Piece Work function, the GL distribution grid is located in the Time Card Entry Tab. For the Apply Payroll/Payment, Post After-The-Fact Payroll, and Amend Applied Payroll functions, the GL Distribution Tab is added. This change allows users to use a generic earning code for multiple departments.

In the previous version, the system computes the deduction amount exclusive of the overtime hours.

In this version release, the system is enhanced to allow user to indicate whether deduction amount shall be computed inclusive or exclusive of the overtime hours. Mark the Include Overtime Hours checkbox in the Deduction Maintenance function, available only if deduction type is Rate/Work Hour, if calculation of the deduction amount on the applied payroll/payment transaction must include the overtime hours.

In the previous version, the system will not accrue holiday hours for employees that are not assigned a Holiday type earning code.

In this version release, the system is changed to require input of a default Holiday Earning Code when processing payroll/payment with non-zero holiday hours. The functions affected are Time Card/Piece Work, Apply Payroll, and Post After-The-Fact. If Holiday Earning Code is set up in the PR Module Setup, the system will use this value as the default Holiday Earning Code for the transactions. Employees who are not assigned a holiday type earning code will use the default earning code for accrual of holiday hours.

In the previous version, the system does not read the Exclude O/T Premium settings when calculating WC Wages for Overtime type earning code.

In this version release, the system is changed such that computation for WC Wages will depend on the Exclude O/T Premium settings of the Worker's Comp Group attached to the earning code.

• If Exclude O/T Premium checkbox is unmarked, WC Wages is computed as overtime hours multiplied by the overtime rate.
• If Exclude O/T Premium checkbox is marked, WC Wages is computed as overtime hours multiplied by the overtime rate, divided by the overtime factor.

In the previous version, the journal entries for accrual of earned sick leave are:

DB: PR Accrual - Sick Time Expense
CR: Accrued Payroll

In this version release, we changed the GL Account IDs for the journal entries as follows:

DB: PR Accrual - Sick Time Expense
CR: PR Accrual - Sick Time Liab-General

In the previous version, the system uses the YTD Accumulated Leave Hours to check for accrual of the leave hours. This will cause Leave Balance to exceed the Maximum Leave Hours when during the W-2/1099 Year-End Closing, Leave Balance carries an outstanding balance while YTD Accumulated Leave Hours is reset to zero.

In this version release, the system is changed to check the Leave Balance to determine if leave hours should accrue or not. Once Leave Balance reaches the Maximum Leave Hours, Leave Balance will no longer accrue. The YTD Accumulated Leave Hours does not play any role in the accrual of the leave hours.

In previous version, a new Paid Leave Code record gets the default Liability Account from the Wages Expense Account of the PR Module Setup while the Expense Account is assigned the Employer's PR Tax Account.

In this version release, the system is changed to assign the Liability and Expense Account in the PR Module Setup as default values for the Liability and Expense Account of a new Paid Leave Code record.

In the previous version, the system prints the W-4 settings (for both federal and state) below the list of deductions on all check stubs (short or long format). The W-4 settings adds 2 extra lines in the deduction details which cause the printing to span over 2 checks if the deduction detail exceeds fourteen (14) lines. This issue applies only to checks using the short stub format (i.e., 3 ½ inch stub).

In this version release, “Fed W/H” and “State W/H” setting information will no longer be printed on the short format of check stubs (which is the same behavior as that of Version 6.5). Only one computer check will be used for any employee with sixteen (16) or less deduction details. With this change, only the recommended long stub check format (e.g., Check 341L for laser) will continue to print the W-4 setting information.

Some environment uses the "strong password" policy for either Windows user account, SQL Server user account or both. In such cases, the AccountMate default password for the SQL Server user "amlogin" may not meet the special requirement.

In this version release, the system is enhanced to accept user-defined password for "amlogin". Create the AccountMate Setup Configuration File (AMSETUP.ACF) in the AccountMate application folder (e.g., C:\AMSQL7) with the line:

LOGINPWD=<password>

When the AccountMate Administrator Program is launched for the first time and the program detects that the "amlogin" user is not yet created, "amlogin" is added to the user list and assigned the password defined in the AccountMate Setup Configuration File instead of the AccountMate default password.

In the previous versions, functions that do not belong to an AccountMate module will not be available for selection in the Create AccountMate Shortcut dialog box. However, functions added to an AccountMate module are included in the function list.

In this version release, the system is enhanced to allow addition of function shortcuts for non-AccountMate modules. This means that shortcuts can be created for menu options in both AccountMate and non-AccountMate modules. Non-AccountMate modules must be added into the Module Selection Table (AMMOD). Transactions, Reports, Maintenance, and Housekeeping functions that belong to these modules must be added into the Menu Option Table (AMMENU.DBF).

A new method AfterSaveRecord is added to the Efrm class which is to be executed after a successful execution of the SaveRecord method of the Efrmtbr class. This method is used as a "hook" to isolate modification code from the standard SaveRecord code. The visual class contains no code in this new method.