Currently, in Accounts Payable, Processing, Void Checks After Posting, system allow voiding an AP check even if that check is already reconciled.

It is suggested that we should not allow this to happen. So we suggest to add the following Global Setup flag to AP Global Control:
Allow Voiding Reconciled AP Check?
The possible value is "Y" and "N". Default is "N". When a user try to void an AP check that has already been reconciled, system will now print proper error message in the void journal to indicate so without actually voiding it.

If user had determine a mistake was made at time of AP check reconciliation and we should allow void anyway, user can go ahead change the global setup flag to "Y" and proceed with voiding the reconcile AP check.

Proper warning message should be displayed in Global setup when user change the value to "Y". Also, during AP void check user interface, if system detect this global setup flag is set to "Y", a warning message will be given.

Elliott allows to use a variable on the Attach... field when sending a Post Office email. For example the variable InvNo will automatically attach a document with the invoice number as the file name. This is NICE. I suggest to allow multiple path in case the documents are in different folders and to allow wildcard. So instead of $InvNo$.pdf I can define $InvNo$.. For example if the invoice number is 123456, Elliott will attach 123456.DOC, 123456A.PDF etc. In addition user should be able to define different path so it can be something like M:\ELLIOTT8\DOC1\$InvNo$., M:\ELLIOTT8\DOC2\$InvNo$.,M:\ELLIOTT8\DOC3\$InvNo$.. In this example, Elliott will attache any document that has the invoice number as the first characters in the file name. If the multiple path is complicated, I think that one path is acceptable.

Many of our clients want the ability to allow multiple workers to scan into the same Work Order. We know there's a workaround by having the 2nd worker log in to the work center instead of the job, but for many of the floor workers this complicates things. Ideally the Floor Manager tells the 2nd worker to log into the work center, but in many cases things are busy and hectic, and Worker B logs in to a job worker A is in. Now A is kicked out and his time is no longer being tracked (unknown to him), and B did not even know A was in it. Additionally, many of the floor workers are just comfortable enough with Elliott to use the Work Order Processing screen. Telling them to learn when to use which screen can be difficult for many of the workers. I understand the work behind having 2 workers logged in is most likely complicated to program, but maybe an alternate solution is the following:

Create a setup option, 2nd Worker Replaces First, Y/N?

If this is set to Yes, it will function as it does now where a 2nd worker will "kick out" the first worker.

If this is set to No, ideally both workers are logged in and both their time is logged. However, a simpler option may be if a 2nd worker tries to login to the same job a pop-up appears "Operator XXXX is currently in this job, login to work center?" And then log that worker into the work center as is done now.

It will be nice to email user the credit card receipt upon the following type of credit card transactions:

Sales, Refund, Complete, Force, Void

There's no need for Pre-authorization. This feature need to be turned on through global setup in the on-line credit card processing area because not all Elliott users necessary want this feature. The default value is "N". The user who will receive the credit card receipt is determined as followings:
(1) From Sales Desk, the primary contacts on the ship-to or customers.
(2) From Order Entry Billing screen, the primary contacts on the order, if not, the primary contacts on ship-to or customers.
(3) From A/R Customer Account Summary Inquiry, the primary contact on the customer.
(4) From A/R Credit Card Trx Processing, the eContacts of the credit card owner if F7 is used. If F7 is not used, then the Primary contact of the customer.

The primary eContact of the customer principle above does not apply to miscellaneous customer.