Windows 10 and Advanced Accounting 7i software

While previously we advised caution in moving immediately to Windows 10, many users have now done so, and with no more problems or issues than traditionally have been the case when migrating to new computers with new operating systems.

Today alone we assisted two different end users, one of whom was replacing an XP Pro PC that had crashed with a PC running Windows 10 which we successfully connected to a Windows 2003 Server (that the user wanted to continue to use, for now), along with another user that had just replaced six of their XP Pro PC's with PC's running Windows 10 Pro, and with one of the Windows 10 Pro PC's acting as "the server" or gateway PC.  We installed the accounting software on the Windows 10 "gateway" computer which went very smoothly, and then we converted all of the the user's Adv 5.1 data to the Adv 7i version, which was also completed successfully.

With any identifying information removed, here is a screen shot of the Advanced Accounting software running on one of the Windows 10 computers:

In general, we have been pleased to date with end user experiences using Windows 10 and Advanced Accounting 7i.

Whether your Windows 10 update installs completely smoothly or not is a different question, and is completely unrelated to Advanced Accounting.   Windows 10 has been known to make changes on its own: it may remove existing program icons or even change folder permissions.   So we would not recommend simply allowing this update to be installed on its own without supervision, and without also testing and especially with respect to any PC that is serving as the "server" or gateway PC where the software is actually installed, since the update may change user permissions and/or the folder's existing sharing characteristics.   Losing installed print drivers has been another problem that some users have experienced which then creates problems in viewing/printing accounting software generated reports.  So, it is not a good idea generally to let the Windows 10 update install itself when you may be unprepared to address other issues that may arise such as re-installing print drivers that may be required in order for your printers to work properly under Windows 10.

With respect to controlling updates on older PC's, see:

http://addsuminc.blogspot.com/2016/05/control-whether-your-pc-upgrades-to.html

Default printer and other settings you may need to adjust with respect to Windows:

Windows 10 default printer woes


See also:

Will Advanced Accounting 5.1 run under Windows 10?

DOS/4G error 2001 exception 0Dh

Users of legacy software that were designed to use the DOS/4G from Rational Systems, Inc. (later Tenberry Software) may experience a  general protection fault response such as the following:

This might happen on a system where the legacy package was previously working, or may be triggered when moving the software to a different/new computer.

The DOS/4G extender was designed to help allow programs access memory above 640K in the pre-Windows era.   Many different programs used the extender ranging from database applications and accounting systems to games.   With the advent of Windows memory handling, its utility largely became moot and fortunately it is normally ignored when programs are run under more modern Windows 32-bit operating systems.   Programs that were designed to use the extender however will require the presence of the DOS/4G executable (usually dos4g.exe or dos4gw.exe) or they will not load.

The issue relates to the Windows PATH that the DOS/4G extender was designed to handle.   It has a limit of 250 characters (some sources indicate 255 or 260).    

This issue is also unrelated to the specific operating system in use.  Once the path environment variable exceeds the maximum, the DOS/4G extender error 2001 will occur.   As programs are installed on, for example, an XP Pro PC, your path environment variable may start to become quite lengthy.   Or on newer PC's with pre-installed programs, the PATH length may already be lengthy to start with.    To see your current path, at a CMD line simply type:

PATH

If you want to determine its length, redirect the output to a text file, e.g.:

PATH > mypath.txt

Then retrieve the file, in this case mypath.txt, in NOTEPAD (uncheck Word wrap under Format and check on Status bar on view and you will then get a a line and column count in the status bar).

Another way to inspect your path would be under Advanced System Settings (how you get there depends on the operating system) and then Advanced and Environmental Variables.  Changing/shortening your path here however may have adverse impacts when running other programs. 

There are various potential solutions to the problem.  The simplest perhaps is to simply edit the batch file (using a line editor such as NOTEPAD or if available EDIT) that starts the application (assuming one already exists) and simply add this line before the line that calls your application:

SET PATH=

(with nothing after the equal sign). 

If your application does not use a batch file then create one with the SET PATH= statement followed by the name of your application (see your icon's properties).    There are other solutions as well..

You may find that your application requires support from other folders and if so you may have to add a path or two to SET PATH= if that is the case:

SET PATH=C:\windows\system32;c:\someotherpath


Starting the application from the CMD prompt will initially help in troubleshooting  errors.



More information:

Tenberry DOS/4G and DOS/4GW FAQ

Locky ransomware on the loose

A user of a software system published by a third party for which we are the developer experienced an error message today indicating that a Codebase file used by the system was corrupt (in this case, the error was a -70 status on FILELOC.DBF, a file that our runtime executable opens on startup).

It is normally very unusual for this file to become corrupted through normal operation; it is even more unusual in this particular vertical software system since it is opened but never updated (i.e. written to).

Without seeing the system, initially we could only assume that the file probably had a bad index and needed to be rebuilt.   After going through those steps with our customer contact and discussing the need to first make a backup of the file before attempting the rebuild and also ensuring that users had exited the software, we then received a phone call indicating that while viewing the folder containing the system files including the location of the FILELOC.DBF file, he was seeing some very strange long file names with ".locky" file extensions.   We were then able to access the system, and this is what we saw:

Locky virus infestation

Realizing that the corruption of the file was in fact being caused by ransomware encryption, we terminated the remote access and advised the user to immediately contact their IT support staff.  

The LOCKY ransomware virus can apparently spread via network shares without requiring mapped network drives.  So relying on non-mapped drives will not be an effective strategy to deter its spread.  In this case, an e-mail was opened from a laptop client and the virus quickly (probably within minutes) spread to the file server via a standard UNC share (the folder above is a server folder view; the e-mail infection was not however originated from the server).

We note this March 16, 2016 report from a hospital in Kentucky similarly infected:

Hospital Declares ‘Internal State of Emergency’ After Ransomware Infection


Some helpful background on this virus is available here:

New Crypto-Ransomware Locky Uses Malicious Word Macros (Trend Micro 2/19/16)

“Locky” ransomware – what you need to know (Sophos 2/17/16)

Locky malware, lucky to avoid it (Microsoft Malware Protection Center 2/24/16 blog)

Remove Locky Ransomware and Restore .locky Encrypted Files (SensorsTechForum 2/16/16)

Blocking the Locky Ransomware Virus - Update and Tips (GreenviewData 2/25/16)


As the Microsoft blog notes, the virus is being spread in a familiar way via e-mail spam (the Trend Micro report indicates that it is disguised as an innocuous e-mail with changing headers referring to the attachment of a fake invoice contained in a Word document).  The virus reportedly can be activated by simply opening the e-mail (i.e. can be contained in the body of an e-mail) and not just by opening the attachment, although, that seems somewhat unlikely since the script that causes the infection is via a Word macro.  

As with CryptoLocker ransomware that we wrote about on October 15, 2014,  end user education is again paramount to avoid being infected.  There are indications that the virus can be triggered simply by opening up an e-mail (probably via an embedded link in an HTML-based e-mail).   So we would recommend not even opening an e-mail from either a suspicious or non-trusted source.   To say another way, you may be able to become infected not only by opening a file attachment, but also even by simply opening the e-mail itself.   Mail programs that provide an initial preview without opening the incoming mail are still likely safe.

Users should be instructed never to affirmatively respond to a query asking them to enable scripting of any kind.   Traditional anti-virus software approaches are not enough; just because your anti-virus definitions are current does not mean that you are protected.

The need to keep frequent backups also cannot be emphasized enough should an infection occur.  In this situation, the user had a backup that was only two hours old and therefore was able to almost completely recover (there were still seven corrupted files in the software system that we support that we were able to simply replace; eventually the virus would have encrypted everything, but for whatever reason decided to encrypt files with a DBF extension first, probably recognizing them as a well-known data file type).   The Codebase error returned on all seven files was a -200 which translates to "File is not a data file."

In addition you can take some steps as outlined in the links above that will help to avoid malicious scripts from being run.

Sample screen shots of some of the screen settings to consider for Adobe Reader, Fox Reader, and OpenOffice are contained below.  For Microsofit Word/Excel macro security settings, see the Microsoft Malware Protection Center blog link above.

Disabling JavaScript in Adobe Reader
Acccess via Edit --> Preferences from the reader menu

More re: Adobe Reader:

Under "Trust Manager" you may also want to uncheck "Allow opening of non-PDF file  attachments with external applications."

And, under "Security (Enhanced)" you may want to uncheck "Automatically trust sites from my Win OS security zones."

Disabling JavaScript in Foxit Reader
Access via File --> Preferences
Verify that enable safe reading mode is checked

More re: Foxit Reader:

Under "General" you may also want to uncheck "Create links from URLs." 

OpenOffice Step #1
From Tools --> Options while in any of the program options

OpenOffice Step #2
Raise the security level to very high

Extend the life of old applications with vDos

Extend the life of old applications with vDos: using vDos to run 16-bit programs 

in 64-bit environments

When attempting to run legacy programs such as versions of Advanced Accounting prior to version 6 (e.g. Advanced Accounting 3.0, 4.x, 5.0 and 5.1) under 64-bit operating systems, the following response can be expected:

Other than upgrading to a newer version of the software which is available, there are a few other solutions to this problem, most not terribly desirable.  One is to replace the existing PC with a 32-bit version of the same operating system (particularly if it is running Windows 7, 8 or 10).  That is an increasingly impractical option.  Another is to install a virtual 32-bit environment or emulator.  Typically these are fraught with a variety of technical hurdles and are still somewhat awkward to access.

Another solution is vDos.

Advanced Accounting 5.1 (DOS mode) running under Win 7 Professional 64-bit
(FRAME set to OFF - recommend to be ON however)

Background:

While most of our users either have migrated (or will soon will be) to newer Advanced Accounting versions, it can still be desirable to be able to run old programs even if they will not be getting used on a regular basis. In addition, if an older PC fails when the older version was still being routinely run, and the old software is then of necessity migrated to a 64-bit system, the old software may still needs to initially be run in order for the conversion of data from 5.1 to 7i (and soon 8) to take place, plus it may be needed to be used until that can occur.  Programmers may also have an occasional need to look at older programs in the TAS 5.1 (or prior) application development system and be able to make program changes and compile older programs from a 64-bit PC.

vDos potentially provides a solution for all of the scenarios above. It could even be used for users who would rather fight than switch, the only primary potential problem then would relate to printing. vDos however provides ample support for printing and in fact provides legacy versions with a Windows dialog box that older versions lacked.* The printing options in fact appear to be very powerful including being able to print to a PDF, but would likely require changes to individual programs in order for the output to be properly aligned and formatted correctly in general.

(*Other than the tp5win.exe mode of version 5.1.  Tp5win.exe, while 16-bit, requires a Windows installation and therefore cannot be run under vDos.)

vDos was originally provided on SourceForge and made available as freeware until recently.  Older/freeware versions as well as community support remains there:

https://sourceforge.net/projects/vdos/

General information from the publisher about the product is here:

https://www.vdos.info/index.html

The April 2015 version (the October 2015 version has a built-in expiration date) remains available for free. Starting November 1, 2015, the latest version which should be registered but can be downloaded installed without advance payment (and which is no longer 100% open source, an irrelevant  fact for most users).

https://www.vdos.info/download.html


Installing and using with older versions of Advanced Accounting:

Initial setup:  Installing vDos initially is simple. The default install folder is C:\vDos. It normally should be installed to a local drive even if the accounting (or other legacy) software is installed on a networked drive, at least for preliminary setup and testing. 
   
Folder names and any called file names should be 8.3 compliant. The location of the existing legacy software should already be in a compliant folder name. If located across a network, the user will need the normal read/write/delete rights to the folder.

The vDos software uses the C++ dynamic library link file MSVC100.DLL. If you receive a message indicating that DLL is missing, you will need to download  and install the Microsoft Visual C++ 2010 Redistributable Package currently available here:

http://www.microsoft.com/en-us/download/details.aspx?id=5555

At this point, you should be able to run the vDos software which by default calls an old DataPerfect application as a test.  Assuming that runs successfully (press F7 to exit out of that software and type the word EXIT and then press ENTER to exit the session), proceed with next section.

Configuring to run Advanced Accounting:  The vDos.exe (executable) creates its own C:\ environment or session, and relies on two files that are initially installed in the same folder as the executable, CONFIG.TXT and AUTOEXEC.TXT.  These correspond to the days when CONFIG.SYS and AUTOEXEC.BAT were in the C:\ drive of MS-DOS systems as well as early MS-Windows systems (in later versions of Windows, they were placed in C:\WINDOWS\SYSTEM32 and renamed CONFIG.NT and AUTOEXEC.NT).   The shortcut to vDos.exe will automatically process whatever is in the CONFIG.TXT file and call the program specified in AUTOEXEC.TXT as if it was a batch file.  While initially that is the most simplistic installation approach, in a multi-user environment or if you will be using vDos.exe to support more than one legacy application from the same desktop, a different and better approach would be to copy the CONFIG.TXT and the AUTOEXEC.TXT to the legacy application's folder, and then in the icon's properties, change the "Start in" folder to match that location.

Nothing needs to be added or changed to CONFIG.TXT (except see the recommended change below).  CONFIG.SYS and CONFIG.NT in the older days required a FILES=150 (typically defaulted by Microsoft as FILES=40).  vDos however does not require any FILES= statement because it is already equipped to handle a high enough number of global file handles. If you intend to print out of the legacy application, you will need to review the CONFIG.TXT to tell it how to handle printer redirection for LPT1, LPT2 and LPT3.  There are some other optional settings that can be made.  A setting in CONFIG.TXT that we would highly recommend enabling is:

FRAME = ON

Just remove the REM prior to that line in CONFIG.TXT.  Not only does this provide a standard border around the application window and therefore provides for standard window navigation, it also makes the screen behave in a more expected fashion should you attempt to move the title bar/window around with your mouse.   Without enabling FRAME=ON, the window wants to move down on the screen to the point where it becomes unusable (at least when accessed remotely).

If you are configuring vDos to run Adv 5.0 or 5.1 (but not earlier versions) or TAS 5.0 or 5.1, it is essential that you turn off the dosg4 handling.  These versions of Advanced Accounting and TAS include the setting file:

tpc50.ini

which resides in the same folder where the version 5.0 or 5.1 software is located (i.e. wherever tpc50.exe and dos4g.exe are located).

Use notepad or some other line editor to change the default from:

[dos4g-vm]
On=TRUE
etc. 

to

[dos4g-vm]
On=FALSE

and save.  When run under Windows on 32-bit PC's, Windows ignores the DOS 4G extended memory manager and uses its own memory handling, but if the dosg4g-vm section "On" key is not turned off by setting it to false as above, vDos will not be able to load the program and will return the error:

Page fault directory or table entry not present  

Next edit the AUTOEXEC.TXT file to replace the reference to the demo/test application with calls to run Advanced Accounting. vDos has a USE command that allows you to do something somewhat similar to a NET USE which is handy even if the application is stored on the local drive and not across a network.  Keep in mind that you have to move to the application relative to the C:\ session environment you will be in once vDos.exe is called. UNC paths are not normally used with legacy applications, but the vDos USE option allows you to use them in its supported USE statement.   So where servername is the Windows server or PC name where the program is installed and adv51 is the name of folder that the program is physically installed under, you might assign drive Z: (which does not have to match physical drive mappings, but is preferable) as follows in the AUTOEXEC.TXT file.

use z: \\servername\adv51

Then you would "move" to the z: drive setup after making the USE above by adding this to the next line, just like you would in a batch file:

z:

If needed, you could include "change directory" commands to move to a folder if the USE statement referred to a folder above where the software was installed, e.g.

use z: \\servername\shared

cd adv51

Note:  while not required, it is best to use the same drive letter as any existing drive map to the same folder, or to at least not use conflicting drive letters to avoid not only confusing Windows but also yourself and anyone else who is responsible for maintaining the system at a later date.   Put comments in the TXT file to explain what was done, and why.

Next use the CALL statement to either call the normal Advanced Accounting batch file or the related executable directly as outlined below.

Remove or place a REM in front of the test program:

rem CALL DPTEST\STARTDP 

and replace with:

call adv.bat

Before using adv.bat, review it in a text editor such as notepad to determine whether it has been modified to change directories or call something that should not be called in this simulated environment.  Instead of adv.bat, you could instead:

call tpc50.exe bkmenu

You could also establish SET TAS50= or PATH= values as needed.  To avoid having to type EXIT to return to the desktop, simply remove the rem before the word EXIT at the end of the AUTOEXEC.TXT file.

There is one additional property that we have found needs to be made and one that is commonly made with legacy programs:  right click on the vDos desktop icon, choose Properties, click on Advanced, click on the "Run as administrator" option to check it if not already checked, then click on the OK button and then OK again.

If you receive a:

TAS50.OVL could not be found in your default path 

it will relate to the "run as administrator" icon property above which will likely be needed even if you are logged in as administrator to the local PC.

Click on Advanced to enable Run as administrator option
The "Start in" can/should be changed to match the
location of the CONFIG.TXT and AUTOEXEC.TXT
files that tell vDos what application to run.

Conclusions:

vDos is an excellent product that we would recommend especially to bridge the gap in situations involving PC migration as well as for archival reference.  Unlike in some simulated environments, all screens and screen characters appear normally and all of the important keystroke combinations that Advanced Accounting uses (function keys, ESC, Home, End, Page Up, Page Down, booster key combinations such Alt-1, Alt-F1, Ctrl-Page Down, etc.) all appear to be properly supported.  vDos documentation claims to be capable of full multi-user access and so could be used to support live production environments (which we have not tested).  Running from across a network, it may be a little more sluggish than running from a 32-bit PC directly, but not unacceptably slow.  vDos supports some interesting printing enhancements although it may be possible to fully reap the benefits of those without some reprogramming of existing Advanced Accounting 5.1 (or prior) report layouts and related code.  Using this as the sole solution for moving forward into the 64-bit world is probably not realistic in the long term for most users: upgrading to the newer versions of the accounting software would normally be the better long term option for Advanced Accounting users.  On balance, however, vDos is highly configurable and is seemingly a very valuable tool that could have many uses.

Advanced Accounting 5.1 (DOS mode) running locally on Windows Server 2012
(FRAME set to OFF in this example - recommend to be ON however) 

Note:  our preliminary succesful testing on two different systems (Win Pro 7 64-bit and Server 2012 64-bit) was solely with the Btrieve 5.10a TSR as distributed and provided by the original publisher of Advanced Accounting 5.1, TAS Professional 5.1, and predecessor products.   An attempt was made to use a Pervasive 11 workgroup engine on a third system, but that does not appear to be possible.  While modern Pervasive engines do provide "DOS Box" support, that support appears to be unavailable when using vDos, which is instead attempting to run the application in a largely different environment; it is largely not integrated with the Windows operating system and does not therefore support DEVICE= statements in its CONFIG.TXT file, etc. 

When Arial is missing

A long-time user contacted us today about migrating their Advanced Accounting 6.x system to a newer operating system on an also newly purchase computer.  They wondered whether the newer update that is available would fix a problem with both screen and printing having become excessively small and hard to read since making that change.

The "bitness" of the operating system of course had nothing to do with this issue; it was one we haven't seen before, but which many computer users have reported experiencing:  a missing Arial font installation.

The missing font of course also impacts the way that web sites are viewed in a browser.  For example, this is what our support page looked like from the end user PC:

This above is not what it normally looks like.

When the accounting software came up, the lower portion of the Advanced Accounting license screen appeared as follows:

Note the almost unreadable text starting with the Continue button and the rest of that screen.  Entry fields within the software were also very small and hard to read.

Because it is a standard font that is normally installed with all Windows installations, the most common font used in Advanced Accounting 6 and now 7i (and this will be true with the next release as well) is Arial (although it is not the only one).   When a font that is specified by an installed program is missing (including in web pages), the operating system attempts to find the closest available match, but the results can be unpredictable.

In checking installed fonts on this PC, there was no Arial.

After installing Microsoft's European Union Expansion Font Update which includes an updated version of Arial (along with Times New Roman, Trebuchet and Verdana), the problem was immediately solved, and without the need for a reboot.

Control Panel Fonts section after installation of MS font update (Windows 7 Pro)

More Advanced Accounting payroll updates

Some years are busier than others when it comes to payroll updates and features.   This year has been more hectic than usual.

Mainly this has been due to new features such as the new e-filing option (added towards the end of 2015 and for which testing was completed in early January of this year) and better support for reporting the cost of employer sponsored health plans (added in November of last year) rather than government mandated changes. 

To ease future updates, we have also made the calculation for the additional medicare tax open-ended into the future since it appears to be here to stay.  We've also added a new feature in the PR-F FUTA/SUTA history report to allow access to PR archives to include terminated employees in that particular option.  The PR-K option has been enhanced to allow for from/to wage bracket amounts in excess of $1,000,000 (necessary to fully and properly implement California tax tables, for example). The federal tables and the tables for California and several other states have also been updated.  Some states have posted no changes.

Oregon's complex existing logic has been updated to match January 1, 2016 required changes for that state (and our new e-filing capability is available to meet their paperless filing requirement for W-2's).  The internal required logic for Massachusetts has been updated including exemption amounts; standard exemption updates have also been made for Maine, Minnesota, New Mexico, New York, North Dakota and Vermont.  Users will also need to update PR-K state tax table changes in these and potentially other states.  Rhode Island's maximum wage limit has been updated but users will still need to update PR-K state tax code RIA (for example). More state changes will be made as they are identified.

Other programs providing for payroll capabilities often involve end user charges that on a monthly basis exceed the cost of an annual Advanced Accounting payroll update.  Our goal will be to continue to offer a feature-rich payroll module at a low cost of operation.    

More information 

New federal-state e-filing payroll interface available for Advanced Accounting

A new federal and state e-filing interface has been added to Advanced Accounting 7i's payroll module that can be used to electronically file W-2 forms with both the IRS as well as in various states.

The trend towards paperless forms has been apparent for some time.  The threshold for filing state forms in many states continues to be lowered.  Some states (Connecticut, North Carolina, Oregon, Utah, and Virginia as of the date of this post) already do not accept the filing of paper W-2 forms, i.e. the threshold is zero. Minnesota has a threshold of just ten forms.   Six states have a requirement of either 25 or in one case 26, and another seven currently have a requirement of either 50 or 51.  These numbers will continue to drop, and states with state income tax withholding that currently have a high (or no) threshold will no doubt be implementing similar requirements in the near future.

While the IRS/SSA threshold is still 250, the IRS continues to strongly encourage e-filing to improve accuracy and timeliness and we would expect that number to be significantly lowered in the not too distant future.  States such as Utah have gone paperless under the philosophy that it is a safer mode of transmitting highly sensitive information.   Many end users are increasingly wanting to file their SSA copies electronically for this same reason.

Further, the complexity and ever-changing nature of these requirements both federally and on a state-to-state basis indicated that a better overall solution was needed for Advanced Accounting users.

A federal filing format option has long existed in the software and one that we have regularly updated over the years.  Originally it was referred to as the 'W-2 Electronic/Mag Media Filing" option.  We first started making significant updates to this option going back to at least as early as July of 1997.  That program was originally using the MMREF-1 format.  In tax years starting in 2007, the MMREF started to be referred to as the EFW2 format, which we continued to support through the end of 2014.

But the complications of that rather esoteric format coupled with increasing additions and requirements have made it difficult to make it a full solution even for federal-only e-filers. Further, states typically have their own separate requirements that the prior option could not satisfy.

So, in mid-December of 2014, we entered into some preliminary agreements with Nelco Solutions.  An actual interface however has not been available until now, and we are in the process of submitting test cases to validate the results (postscript: 2015 acceptance testing was completed on January 6, 2016).   We therefore anticipate that the interface will be available to users for 2015 filings, and it is being included in year end payroll updates.

Nelco specializes in W-2 and related e-filings and is an organization we have kept in touch with for well over a decade now in terms of potentially working together to come up with an effective solution for end users.   New capabilities and options will no doubt be made available to our payroll users and their employees as we go forward as a result of this collaboration.

Further, this option simply supplements the existing payroll module and in no way replaces it.

There are typically small fees associated with submitting these filings through the interface.  We believe that users will find these fees very reasonable particularly given not only the convenience and complexity involved but also in meeting applicable federal and state requirement. 

A quick overview of the new option and import process follows:



New PR-G option:

Answer "Y" to the export file option.  Then simply continue to process W-2's including a W-3 if desired.  This includes editing informational boxes as already provided in the software.   Prior to editing that information, however, when choosing the export file option, a new screen will appear asking for verification of the submitting company name, address, phone and e-mail.  In addition, you will be asked for the folder and file name of the export file. 

The file name can have any desired extension (a CSV extension is recommended).  If the directory does not exist, the program can optionally create it.   If the file name selected exists, you will receive a warning message and will be asked if you want to overwrite (normally you would not select an existing file).  

Click on proceed to continue and then proceed to process W-2's and optionally a W-3 as normal.  At the end of the normal process and after having chosen the export file option, you will then see a (new) launch portal screen from within the software.   This screen will also repeat the full path of the file name which we suggest you either copy and paste and/or make a handwritten note.  

Before clicking anywhere on the panel in the left corner of this screen, you can if desired retrieve the CSV in a spreadsheet program for review.  Normally you would not want to make any changes to the CSV file unless there is an unusual situation involving an error that needs to be corrected prior to submission.  The file otherwise must remain in the exact same format and delimited the same way.  The CSV file naturally contains confidential employee information which should be safeguarded and not made available to others.   We suggest retaining a copy of the file however at least until the process is completed and you receive acknowledgment of your filing request.   Submitting the file through the portal however is safe.

After launching the web portal (which you can also launch simply by copying and pasting the link provided under the clickable panel, and go to:

https://addsum.nelcoportal.com/import/gwximport


The PR-R-C option now also shows this same screen (but without the import file box) simply to provide a way to reference the portal's web site if follow-up or other action is needed, but not because the import is otherwise initiated here, as it formerly optionally was (this is is where the older EFW2 export option existed which has now been retired).

After launching the portal, either create a new account when logging in for the first time or log in with your previously established credentials. Then at the data import screen, import the same file that was created above within the accounting software (click on the Choose file option, and select the import file).

After clicking on import, unless problems were detected in the upload, you will select your filing options.  If you will only be filing federally, be sure to click on the "federal e-filing" check box.   

If wages are submitted for a state that has an e-filing option, a "State E-filing" check box option and an additional column next to each employee will appear. You can choose to file federal and state via the "a la carte services" section, or you can choose the "full" service (bundles) that also includes Nelco actually printing the employee copies and providing employees with e-mail address to the filings (requires the input of each employee's e-mail address; in a future Adv release we will be providing a more automated way to accomplish that).   So using the full/bundled service allows users to not even have to purchase W-2 forms and saves the time involved in both printing them as well as providing them to employees.

Make sure that the appropriate options are reflected on this screen.   Click on Next to review and submit your forms.

After clicking on Next from the submit forms, you simply enter your payment/card information and the process is complete.


More information:
Paperless Filing flyer (2015)

Additional operational and technical details:

If a problem is detected at the web portal import stage, those errors will be outlined as which point you can return to the import page to try again after correcting the errors (contact us 1-801-277-9240 or e-mail us at support@addsuminc.com to resolve any problems in this regard).

When filing in a given state, any required form that is required by that state will appear as part of the submission process with as many boxes already completed as possible based on the data imported.

(Postscript:  the information below about IE and Silverlight no longer applies starting in 2016)

While to initially submit and import data any of the major browsers seem to work without problems, Nelco recommends the use Internet Explorer.   When making state filings and a form has to be completed, the web portal may inform you that you need to use Internet Explorer with the free Silverlight plug-in.   This does not create any additional work should this happen since any imported data will still remain pending.  Switch to an IE browser with the Silverlight plug-in installed and log back into the portal and proceed to manage your account where you will be able to proceed with completing your submission.

In all it is an efficient and economic solution to federal and state e-filings.