User guide

218
Avoiding unwanted service items creating problems
Sometimes an item may be accidentally moved or changed in Accounts. When posting transactions from POS,
Accounts may have to create a new service item in the list to compensate for the changed item details that no
longer match what POS has in its database.
To avoid having a collection of unwanted items that are either not needed or doubling up, we suggest you run a
Accounts Transfer before creating an End of Day  le. The transfer veri es the items in the pending transactions in the
database and follows these rules:
If the category/item name is found, then there is no problem.•
If there is only one product with that item name found, then POS changes the category data in the transaction so •
that it now points to the new location of the item.
If the category/item name is not found, then POS looks for the item name.•
If POS  nds more than one product with the same item name and none of them match the category of the •
original transaction row, a list shows all products that have that item name and change the transaction to the
one you choose. Or you have the option of not making a choice and POS creates an error log for this transaction.
If there is no product that has that item name you can save it for the error report.•
At the end of the transfer, POS may display an error message that warns you there were some items that did not
match. You are given the choice to print a report on these items. The report shows items with No Match, No Match
– Left As Is and Successful Changes.
We strongly advise that you  x these items before running a Z-Read to create your End of Day  le, otherwise all No
Match items are created as Service Items in Accounts. Once the changes have been made, you can run another
Transfer for POS to update your transactions before running the Z-Read.