3.0.2 Release Notes

Incorporate into the Payroll Module the maximum limit for the withholding of Social Security tax. This change has been implemented during paycheck entry and all payroll reports updated to utilize the FICA limit defined in the tax table for any year. Paycheck entry shows all YTD amounts prior to the current check being entered or edited.

Payroll Form 940 was redesigned for the 2006 calendar year, and future calendar years. Additional lines have been added and other changes incorporated.

Payroll Form 941 (Employer’s Quarterly Federal Tax Return) was redesigned for the 2005 calendar year, and future calendar years. Additional lines have been added and other changes incorporated.

Change the 12.4% and 2.9% values on Lines 3 and 5 to the decimal format of .124 and .029.

A new IRS form developed in 2006 for depositing of FICA taxes and income taxes withheld on employees. Form 944 is used by employers instead of Form 941 if the employer is notified in writing by the IRS. Tax deposit is done annually instead of monthly, quarterly, etc.

After a paycheck has been completed but not recorded, pressing the Enter (or Tab) key through the address line will cause the program to automatically reopen the Paycheck Detail Window. If the user had entered a value in the “Other” withholding box, then this value would have moved to the “Retirement” box when the Paycheck Detail Window was reopened. (NOTE: The Paycheck values will be correct because the values for Retirement/Other are combined on one detail line with the ATIG code of “9414”.)

This has been accomplished by back figuring the percentages from the employee window when showing the detail window. If the employee has no values defined, the split values will not be maintained. The final solution will be incorporated with additional payroll changes in the next release.

On the report setup screen, the user enters the Employee’s Number. When the number is entered, the Employee’s Name should be displayed.

The grid was changed to remove columns that were not relevant to payroll. Hours and Gross Pay columns were added.

Beginning with the Net Sale Grain line, the “$/Unit” values should be derived by dividing “Dollars” by “# Unit Produced.” Currently, the dollar values are divided by “Pounds/100”.

Do not print this report for a type of livestock if no inventory, purchase, sale, death, weaning, and birth entries have been entered for that type of livestock. That is, the report is blank.

Standardize all reports and screens on use of either “Non-Farm” or “Nonfarm”, but not the use of both. It was decided to use Non-Farm and the following changes were made:

Other than the above, the term “Non-Farm” is used throughout the program.

Allow the user to enter a specific date to be printed in the heading of the ending Balance Sheet and Supporting Schedules Reports. This “date” is especially important for the ending Balance Sheet. For example, an ending inventory may have been entered on the data of August 15th to obtain a Balance Sheet report as of that date.

In the Supporting Schedules, include the “Qty Code Terms” such as Bushels, Acres, Head, with the units. Also, change the term “value” to “Amount”.

Move the page #’s as well as the date and time a report was printed to the bottom of the report.

Change the following terms:

Provide a method of recalling the last check or deposit detail for a vendor. This feature is only available during new check / deposit entry.

Pressing the plus or minus key within the check number field will increment or decrement the check number by one if the field contains a number.

If typing in a name that is not set up as a vendor but starts with a few of the first letters of a vendor that is set up in upper and lower case letters, it starts to do the quick-fill of the vendor, but the rest of the name that is then typed is in all capitals. For example, if a vendor is set up as “John Deer”” and the user is entering a check for Johnson County, then it will pick up the “John” part of John Deere but the rest of the name is in all capitals. Thus, the name will be listed on the check as “JohnSON COUNTY”.

The check / deposit amount will be retained if the payee is changed. It was always reset to zero in prior versions.

The print screen allows for the entering any range of dates, but the report does not cross fiscal years. Example: The report for transaction dates of 7/01/2006 – 12/31/07 will be identical to the report with transaction dates of 01/01/2007 – 12/31/07. Since you can not cross the fiscal year dates, then the “YTD Balance” does not make sense and is not needed. Example: A Bank Balance Summary report for the dates of 01/01/2006 to 12/31/2006 will show a balance as of 12/31/2007. If the report was processed on 2/9/2007, then the YTD Balance as of 2/9/2007 will print. But, the balance will be identical to the 12/31/2007 balance. That is, the YTD value printed is not the balance for this checking account as of 2/9/2007. Also, the **End of Report** term can be removed.

Analyzing an existing farm database will apply the new and changed code descriptions. Any new farm created will have the new and changed codes without doing the data analysis.

Changing the fiscal year on the register tab could result in an access violation being reported. The application would continue after closing the message box. This has been fixed.

Counts added for “cleared” and “un-cleared” checks and deposits.

Changing the sort view could result in un-reconciled transactions from other bank accounts to be included with the current bank account.

The new grid with additional features was introduced in Version 3.0, sometimes the grid did not show the data or would show additional fiscal years.

When setting up a new farm database and entering checks during the same session, the checks would not be displayed in the grid. It would require you to close the farm and then reopen it.

Entering new checks and then returning to the register tab grid would not always display the new checks.

Having the view set to “Show Detail” as unchecked would result in all fiscal years data to be display on application startup. It would appear to user that it was showing the wrong fiscal year when comparing the data being displayed to the fiscal year in the drop down list.

When creating a new fiscal year the loan / receivable beginning balance for the new fiscal year was not always correct. This was especially true if the same external code was used on all loan payments or receivables.