Roundtable Software Newsletter #33, May 5, 2005
In this issue...
|Patch 18: Viewing A/R Sales History and Cash Customer Pricing Class in Point of Sale|
This patch addresses the following:
Click Here To Download This Patch
|Unix Users: How To Get The Patch 18 Update|
|Patch 18 is also available (as Unix Patch 2) for your version 4 Unix product; to download it you'll need the login and password for the Unix Patches web page on our site. To get this information your 4.0 product must be registered. Send us an email stating the serial number of your 4.0 product and the contact name that was listed on your registration card and we'll send you the login and password. Once you have the login and password, you can go to the patches page and follow the link for Unix Patches at the top of that page, or click the link below.
Click Here To Download This Patch
|Q&A: Why does my RG report only print one line of detail?|
|I made a simple report format out of Report Generator program 2. It works from one file and doesn’t have any unusual calculations, ranges or variables on it. Yet this simple format only prints one line of detail and quits - it should print many pages of information for the thousands of records in that file. Why do I only get one line of detail printing on my RG report?
The most likely culprit is that you've put your data fields in the title section rather than the detail section. When you first start a format in RG2, the program places your cursor in the Title section. If you don't realize that's where you are and never put any fields in the detail section, you'll only get the first line of detail printing in the title section. When you are editing a format in RG program 2 you can tell what section you are in by looking on the second line of the screen in the upper left; the program displays the section and cursor position there. For example, (TITLE, 1, 50) tells you that the cursor is currently in the Title section on line 1 at column 50. You can use the arrow keys to move around in the Edit mode until you have the cursor in the desired position.
If this has happened to you, refer to page 36 of the RG section of your Book of Knowledge, 2nd edition for details on moving elements. You can easily move all the fields from the Title section to the Detail section; it is not necessary to delete and recreate them.
|Tax Table Updates|
|Idaho has recently released updated tax tables that are effective as of January 1, 2005 (even though the tables were not released until April). The state says that no retroactive adjustments are necessary but that all employers should begin using the new tables as soon as possible. These updated tables are available in the Current Tax Table patch.
In an effort to make it easier for users to obtain current tax tables, all tax table changes are incorporated into a standard patch. Formerly, this was patch 11 but can now be found at the bottom of the patch page. It is no longer a numbered patch and there is a link to it at the top of the patch page. This means that you only need to download this one patch and follow the instructions to keep your tax tables current. It also means that the tax table patch is updated every time a new tax table becomes available, so if you hear that your state is changing the way taxes are calculated, you need to check this patch. As we learn of changes we add them to this patch and record the affected states and the date the change was added.
|Q&A: How does the prompt "Are These Annual Figures" affect Payroll tax table calculations?|
|Recently we've fielded several calls concerning FICA taxes not calculating properly and the culprit has always been that the table has been set to Annual Figures=Yes rather than No. When a table is set to Annual Figures=Yes, the tax calculation takes an employee's wages for the pay period, annualizes them (multiplies them by the number of pay periods in a year) and bases the tax calculation on that annual figure rather than the amount in a given pay period. The problem comes in when the program applies limits to the calculation. When annualized, the limit is applied to the annual figures, so that employees that will exceed the limit seem to have too little withheld.
For example, the OASDI wage limit for 2005 is $90,000, which means that the maximum OASDI tax is $5,580 for the year. An employee making $1,800 per week (or an annual wage of $93,600) will exceed the limit. If the OASDI table is set to Annual Figures=No, the weekly amount is based on the weekly wages of $1,800 and calculates as $111.60. However, if the table is set to Annual Figures=Yes, the calculation is based on the annual wages of $93,600, which because it exceeds the limit, results in a weekly OASDI amount of $107.31 (the annual total of $5,580 divided by 52 weeks per year). At the end of the year, either table will have taken the proper amount, but annual tables cause the tax to be taken from every pay period, even after the employee's total wages for the year have exceeded the limit.
According to the federal government deduction calculations may be based on pay period or annualized figures. Therefore our standard FWT tables are set to Annual Figures=Yes. The Social Security Administration, however, prefers that FICA deductions not be based on annualized figures but be calculated on a pay period basis. Therefore our standard FICA table is set to Annual Figures=No. We are not aware of any hard-and-fast rule that says you must do this, but tradition, if not actual law, dictate that deductions be set up this way.
|Roundtable Software 30831 Cove Road Tavares, FL 32778-5164
(352) 253-9779 FAX: (815) 572-5446
All contents copyright © 2000-2008 Roundtable Software. All rights reserved.