V Release Notes June 2010

Transcription

1 V Release Notes June 2010 This document details the new features that are available in CounterPoint V

2 Table of Contents New Features... 3 System... 3 Windows 7 support (32-bit only)... 3 PCI DSS-compliant passwords required... 3 Automatic tracking of login attempts... 4 PCI DSS-compliant activity logging... 4 Renumber users utility... 5 Renumbering users in a Multi-Site environment... 6 Accounting... 7 Sage BusinessWorks Installing Sage BusinessWorks MAS90 v QuickBooks Microsoft Dynamics SL v Peachtree Sage Accpac Point of Sale... 9 Sending receipts via Configuring CounterPoint to send receipts via Sending a receipt to a customer s address Adding or editing a customer address on the fly Card numbers on settlement reports Inventory View prices utility Customers Group customer changes utility Purchasing Purchasing Advice replenishment adjustments for QoH/Max qty Sending purchase orders to vendors via Printing original receivers from Received PO History Sales History Viewing full card numbers in ticket history no longer allowed Credit Cards Support for partial authorizations and full reversals Partial authorizations and full reversals for RPS/RBS Lynk Multi-Site Disabling the transmission of encrypted credit card numbers Data Interchange Option Additional fields in inventory import specifications... 20

3 CounterPoint V Release Notes 3 New Features System Windows 7 support (32-bit only) Microsoft Windows 7 is a supported operating system for use with CounterPoint V NOTE: CounterPoint can be used in 32-bit Windows 7 environments only; 64-bit environments are not supported. PCI DSS-compliant passwords required In previous versions, the use of passwords was optional, allowing merchants to decide whether to require users to enter passwords to log in to CounterPoint. In this version, the use of PCI DSS-compliant passwords is no longer optional for merchants who are processing credit card transactions. All users must log in to CounterPoint with a unique password that meets the minimum PCI DSS requirements for password length and complexity (i.e., passwords must include a combination of letters and numbers). NOTE: Passwords are not required for merchants that are not processing credit cards or for DEMO registrations. Other password settings including the number of days passwords are valid, the number of unique passwords each user must create before re-using a particular password, and the number of unsuccessful login attempts allowed before a user is locked out of CounterPoint must also meet minimum PCI DSS requirements. NOTE: If you are updating to V and you already require passwords that meet the minimum PCI DSS requirements, you will not have to take any additional action after you complete the update process. If you are updating to V and you do not currently require passwords or your password settings do not meet minimum PCI DSS requirements, you will need to take additional steps after updating to V Refer to the CounterPoint Update Guide for more information about updating to V from a previous version of CounterPoint. Refer to the PCI DSS Compliance Guide for more information about PCI DSScompliant password settings.

4 CounterPoint V Release Notes 4 Automatic tracking of login attempts Previously, if you were using passwords, you could configure CounterPoint to record login attempts for each user. In this version, to ensure compliance with PCI DSS requirements, tracking login attempts is no longer optional. All login attempts are automatically recorded in the SECURITY.LOG and SYSTEM.LOG files in the top-level CounterPoint directory (e.g., C:\SYN). As a result, the Record login attempts? setting has been removed from the Passwords window that appears when you select the Use passwords? field on the Company screen (Setup > System > Company). NOTE: Refer to the PCI DSS Compliance Guide for more information about PCI DSS requirements. PCI DSS-compliant activity logging To satisfy PCI DSS requirements, CounterPoint now automatically logs the following activity in the SECURITY.LOG file in the top-level CounterPoint directory: Access to sensitive cardholder data outside of an active transaction Changes to user records (e.g., creation, deletion, security authorization changes, password reset, account lock and/or disable) Changes to Setup > Draft capture settings Creation or deletion of store records NOTE: Refer to the PCI DSS Compliance Guide for more information about PCI DSS requirements.

5 CounterPoint V Release Notes 5 Renumber users utility CounterPoint now includes the Renumber users utility, which allows you to change the User ID values for one or more users by specifying the Old user ID and New user ID for each user record you want to update. This utility also updates the User ID values in all associated documents and historical transactions. WARNING! NOTE: Back up your data files before using this utility. If a power failure or some other problem occurs while the utility is running, you will have to restore from your backup and run the utility again. You must post all unposted payments, customer adjustments, and cash receipts before using this utility. Select File Utilities > Special > System > Renumber users to display the Renumber users screen, as illustrated below. For each user whose User ID you want to change, enter or look up the Old user ID, and then enter the New user ID value for that user. You can press F5 to print the RENUMBER USERS report, which lists all of the users whose User ID values you are updating, including the Old user #, Name, and New user # for each. When you have specified all of the users you want to renumber, press TAB or ESC to continue. You will be prompted to confirm that you want to update the User ID values for the specified users. Select Yes from the OK to process records? prompt to start the renumbering process. NOTE: If you select No from the OK to process records? prompt, the users you specified are saved, but not processed. The next time you access the Renumber users utility, you will be prompted to load the records on file. When the renumbering process is complete, the RENUMBER USERS report prints to the printer you specify, providing a printed record of the old and new User ID values for each user you renumbered. NOTE: If you renumber the User ID you used to log in to CounterPoint, the error message User not on file - cannot continue appears when you complete the renumbering process. Click OK to close the message and quit CounterPoint, and then log in to CounterPoint again using your new User ID.

6 CounterPoint V Release Notes 6 Renumbering users in a Multi-Site environment If you are using the Renumber users utility in a Multi-Site environment, follow these steps to make sure that the same changes are made at each location: 1. Make sure that all multi-site polling is up-to-date and that you have not entered any new information for the users you are going to renumber. 2. At the Hub, select File Utilities > Special > System > Renumber users and specify the Old User ID and New user ID for each user you want to renumber. 3. Press ESC or TAB, and then select No from the OK to process records? prompt. 4. Copy the FIXUSR.DAT file in the \SYDATA subdirectory of your company directory to the corresponding directory on each satellite. 5. Select File Utilities > Special > System > Renumber users at the Hub, selecting Yes from the Keep records already on file? prompt. 6. Press ESC or TAB, select Yes from the OK to process records? prompt, and complete the renumbering process. NOTE: Repeat steps 5 and 6 at each satellite.

7 CounterPoint V Release Notes 7 Accounting Sage BusinessWorks 2010 This version includes a direct accounting interface for Sage BusinessWorks Direct interfaces for earlier versions of BusinessWorks are still supported. To define the interface, select System > Accounting > Interface, and then select BusinessWorks from the Accounting system field and 2010 from the Version field. Refer to Accounting Interface Notes in the CounterPoint Electronic Documentation for more information about defining accounting interfaces. Installing Sage BusinessWorks 2010 BusinessWorks 2010 requires Pervasive.SQL V9.6, which is only available from Sage Software. To install BusinessWorks 2010, you must first remove your existing installation of Pervasive.SQL, and then install BusinessWorks 2010 and Pervasive.SQL V9.6. NOTE: BusinessWorks 2010 is not compatible with Pervasive PSQL v10. Follow these steps to complete this process: 1. Use the Pervasive System Analyzer (Start > Programs > Pervasive System Analyzer) to delete all Pervasive.SQL components and registry settings from all of the computers on which Pervasive.SQL is installed. 2. Follow the instructions provided by Sage Software to install BusinessWorks 2009 and Pervasive.SQL V When the installation is complete, use the Pervasive Software License Administrator (Start > Programs > Pervasive.SQL > Other Utilities > License Administrator) to activate the permanent Pervasive.SQL license key provided by Sage Software. 4. If you require another Pervasive.SQL license for additional CounterPoint users, follow the instructions in Step 10 Activate Pervasive.SQL license key of the CounterPoint Installation Guide to generate and activate a permanent Pervasive.SQL key for your CounterPoint users.

8 CounterPoint V Release Notes 8 MAS90 v4.3 This version includes a direct accounting interface for MAS90 v4.3. Direct interfaces for earlier versions of MAS90 are still supported. To define the interface, select System > Accounting > Interface, and then select M.A.S. 90 from the Accounting system field and from the Version field. Refer to Accounting Interface Notes in the CounterPoint Electronic Documentation for more information about defining accounting interfaces. QuickBooks 2010 This version of CounterPoint includes a pre-defined export accounting interface for QuickBooks Interfaces for earlier versions of QuickBooks are still supported. To define the interface, select Setup > Accounting > Interface, select Export from the Accounting system field, select Yes from the Load-pre-defined export interface? prompt, and then select QuickBooks from the Pre-defined Export Interfaces window. Refer to Accounting Interface Notes in the CounterPoint Electronic Documentation for more information about defining accounting interfaces. Microsoft Dynamics SL v7.0 This version includes a pre-defined export interface for Microsoft Dynamics SL (formerly Solomon IV) v7.0. Interfaces for earlier versions are still supported. To define the interface, select Setup > Accounting > Interface, select Export from the Accounting system field, select Yes from the Load pre-defined export interface? prompt, and then select Dynamics SL 7.0 from the Pre-defined Export Interfaces window. Peachtree 2010 This version includes a pre-defined export interface for Peachtree Interfaces for earlier versions are still supported. To define the interface, select Setup > Accounting > Interface, select Export from the Accounting system field, select Yes from the Load pre-defined export interface? prompt, and then select Peachtree from the Pre-defined Export Interfaces window. Refer to Accounting Interface Notes in the CounterPoint Electronic Documentation for more information about defining accounting interfaces. Sage Accpac 5.6 This version includes a pre-defined export interface for Sage Accpac 5.6. Interfaces for earlier versions are still supported. To define the interface, select Setup > Accounting Interface > Interface, select Export from the Accounting system field, select Yes from the Load pre-defined export interface? prompt, and then select ACCPAC for Windows V from the Pre-defined Export Interfaces window. Refer to Accounting Interface Notes in the CounterPoint Electronic Documentation for more information about defining accounting interfaces.

9 CounterPoint V Release Notes 9 Point of Sale Sending receipts via In this version of CounterPoint, when you complete a ticket in Ticket Entry, you now have the option of sending the receipt to the customer via . This feature allows you to offer your customers a convenient service while reducing your consumption of physical supplies, including printer ink and receipt paper. Configuring CounterPoint to send receipts via To configure CounterPoint to allow you to send receipts via , you must edit the SENDMAIL.INI file in your top-level directory (e.g., C:\SYN) to include the following entries below the remarks section: Host= This entry indicates the SMTP host name for your system or provider (e.g., Host=smtp.my provider.com). From= This entry specifies the From address that will be used for receipt messages (e.g., From=mystore@my provider.com) You can also include the following optional entries in the SENDMAIL.INI file: Port= This optional setting indicates the SMTP port you are using. The default SMTP port is 25. Include this setting if you are using a different SMTP port (e.g., Port=26). ReplyTo= This setting allows you to define an optional reply to address for receipt messages (e.g., ReplyTo=Do_Not_Reply@my provider.com). CC= This setting allows you to define an optional address to which receipt messages will be close copied (e.g., CC=mystore@my provider.com) BCC= This setting allows you to define an optional address to which receipt messages will be blind close copied (e.g., BCC=mymanager@my provider.com). Thus, a valid SENDMAIL.INI file might include the following entries: Host=smtp.my provider.com From=mystore@my provider.com BCC=mystore@my provider.com WARNING! You must provide a valid SMTP host name in the SENDMAIL.INI file. When you attempt to send a receipt via in Ticket Entry, if the Host= setting does not exist or is invalid, CounterPoint will not display an error message or otherwise indicate that the attempt failed.

10 CounterPoint V Release Notes 10 Sending a receipt to a customer s address Once you have edited the SENDMAIL.INI file to include the Host= and From= entries, along with any optional settings you want to include, you are ready to send receipts via . When you complete a ticket in Ticket Entry, to send the receipt via , simply press F4 (or click the F4= button), enter the customer s address in the address window, and then press Enter to send the receipt. The subject of each receipt message includes the Store name and corresponding ticket number (e.g., Subject: Your Camptown Golf receipt #XXXXX). NOTE: If the customer s address is already on file, CounterPoint will use that address by default. If you specify a different address, your changes will not be saved to the corresponding customer record.

11 CounterPoint V Release Notes 11 Adding or editing a customer address on the fly In this version, when you select a customer in Ticket Entry, you can now add an address to the customer record or edit the customer s existing address on the fly. This feature allows you to easily capture a customer s address when you are entering a ticket. To add or edit a customer s address in Ticket Entry, select the customer normally, press F7 (or click the F7= button), and then enter or modify the customer s address in the address window. The address you specify is saved to the customer record for future use. NOTE: Users must be authorized to edit customer records (i.e., the Edit customer record? Point of Sale authorization in Setup > System > Users must be set to Yes) to be able to add or edit a customer s address in Ticket Entry. Card numbers on settlement reports In previous versions, CounterPoint allowed you to include full credit card numbers on settlement reports, including the SETTLEMENT EDIT LIST and the SETTLEMENT JOURNAL. In this version, to ensure compliance with PCI DSS requirements, CounterPoint no longer allows the inclusion of full card numbers on settlement reports. Card numbers that appear on settlement reports are always masked. As a result, the Settlement Journal card number method field has been removed from Setup > Point of Sale > Control. NOTE: Refer to the PCI DSS Compliance Guide for more information about PCI DSS requirements.

12 CounterPoint V Release Notes 12 Inventory View prices utility This version of CounterPoint includes the View prices utility (Inventory > View > Prices), which provides a simple way to test pricing and loyalty point calculations for your items. The View prices utility calculates what the price and loyalty points earned would be for an item entered on a ticket, based on the item number, customer number, location, quantity, unit, and effective date you specify. The View prices utility also indicates what type of price would be applied to the item (e.g., sale, contract, location-specific, and so forth). To calculate the price for an item based on specific criteria, select Inventory > View > Prices to display the View prices screen, and then specify the Item number for the item. If you are using locationspecific pricing, specify the Location for which you want to calculate the item s price. If the item is gridded, you must specify the Color / Size values for the item, which determine whether oversize pricing applies to the item. Enter the Quantity for which you want to calculate a price. This value determines whether any applicable quantity breaks are in effect. If alternate units are defined for the item, select the Unit you want to use for the price calculation. Enter the Effective date for the price calculation. This value determines whether a datedependent sale price or contract price applies to the item. Finally, you may enter or look up a specific Customer number to determine whether a customer-specific contract price applies to the item.

13 CounterPoint V Release Notes 13 When you have entered all of the necessary parameters, CounterPoint calculates the effective per-unit price for the item, based on the values you specified, and displays the result in the Calc unit price field, as illustrated below. The Price type field indicates what type of price (e.g., ITEM, SALE, CON, LOC, and so forth) applies to the item, given the parameters you specified. The View prices screen also displays other relevant price values including the Extended price, Stock unit price, Item price 1, Location price 1, and Regular price for the purpose of comparison. The Future sale prices area indicates the next three sale prices that will be in effect for the item, including the perunit price and effective date range for each. Finally, the Redeemable field indicates the number of the specified customer s loyalty points that could be applied toward the purchase of the item, while the Earned field displays the number of points that the customer would earn by purchasing the item.

14 CounterPoint V Release Notes 14 Customers Group customer changes utility This version of CounterPoint includes the Group customer changes utility, which allows you to update values in multiple customer records simultaneously. This feature allows you to easily make mass changes to customer information, without requiring you to modify numerous customer records individually. For example, you can use the Group customer changes utility to change the Tax code for all customers in a particular State or to reassign all customers in a specific Zip code to a different Zip code. You can also copy values from one customer record to a group of customer records. NOTE: This feature was released in a V Service Pack. To use the Group customer changes utility, select Customers > Utilities > Group customer changes, and then specify a value or a range of values in each of the selection criteria fields at the top of the screen to indicate which customer records you want to update. For example, enter a value in the Zip code field to select all customers with the specified ZIP Code. Similarly, you can enter or look up a Tax code to select all customers assigned to that tax code. Press F1 from each selection criteria field to set its value to All (or First and Last for the Customer range fields). From the Print/Update? field, select one of the following options: Print report With this option, when your press Enter from the Field number to change? prompt, CounterPoint generates a report that indicates which customer records will be updated, based on the selection criteria you specified. This report allows you to refine your selection criteria to update the appropriate customer records. Update custs With this option, when you press Enter from the Field number to change? prompt, CounterPoint updates the customer records that meet your selection criteria, replacing existing field values with the values you specified in the New Field Values window. Both (Print & update) With this option, when you press Enter from the Field number to change? prompt, CounterPoint generates a report that indicates the customer records that will be updated, and then replaces existing field values in those records with the values you specified in the New Field Values window.

15 CounterPoint V Release Notes 15 Once you have defined the selection criteria for the customer records you want to update, use the New Field Values window to specify new values that will replace the existing values in the selected customer records. If you wish to copy eligible field values (i.e., for the remaining fields in the New Field Values window) from an existing customer record, enter or look up the customer number in the Copy from customer field. To specify a new value to replace the values in the customer records that meet your selection criteria, enter the corresponding field number from the Field number to change? prompt, and then enter or look up the new value. If you selected a customer from the Copy from customer field, you can press F2 at each field in the New Field Values window to set the field s value to the value in the selected customer record. NOTE: You cannot specify new field values for the Commission pct or Commission method fields if you are calculating commissions based on sales rep (i.e., if the Calc commissions based on field in Setup > System > Company is set to Sales rep). To set all field values in the New Field Values window to None, press F2 from the Field number to change? prompt.

16 CounterPoint V Release Notes 16 If you wish to use defined customer profile fields as selection criteria and/or update profile field values in the selected customer records, press F1 from the Field number to change? prompt to display the screen illustrated below. This screen lists each of the customer profile fields that is defined for your company (in Setup > Customers > Control). In the Select field values column, enter or look a value for each profile field you want to use as selection criteria. In the New field values column, enter or look up the new value for each profile field that will replace existing values in the customer records that match the selection criteria you have defined. Once you have defined all new field values, press Enter from the Field number to change? prompt to print a report that lists the customer records that match your selection criteria, replace the existing values in the selected customer records with the new field values you specified, or both, depending on the Print/Update? option you selected. When all selected customer records have been updated, CounterPoint indicates how many customer records were processed, changed, and skipped, as illustrated below. Press ESC to return to the main menu.

17 CounterPoint V Release Notes 17 Purchasing Purchasing Advice replenishment adjustments for QoH/Max qty Previously, when you generated purchasing advice using the Replenishment calculation method, CounterPoint simply suggested ordering the quantity that had been sold during the specified period for each item you included on the PURCHASING ADVICE report (Purchasing > Purchase requests > Purchasing advice). In this version, when you select the Replenishment option from the Calculation method field, you can now choose to consider the current quantity on hand and/or the defined maximum quantity (or model stock, for gridded items) for each item and adjust the suggested quantity accordingly. This feature allows you to generate more accurate purchasing advice and helps to ensure that you do not order more of an item than you actually need to replenish your stock to appropriate levels. To adjust the replenishment quantity for each item on the PURCHASING ADVICE report by its current quantity on hand, its maximum quantity, or both, select the corresponding option from the Adj for field on the Purchasing advice screen. NOTE: If you do not want to adjust the replenishment quantity for each item, select Neither QOH nor Max qty from the Adj for field. If you choose to adjust replenishment quantities by quantity on hand, CounterPoint will subtract the current Qty on hand value for each item from the suggested quantity for that item when you generate the PURCHASING ADVICE report. If you choose to adjust replenishment quantities by maximum quantity, if the suggested quantity for each item is greater than its maximum quantity, CounterPoint will set the suggested quantity to the maximum quantity. If you choose to adjust replenishment quantities by both quantity on hand and maximum quantity, CounterPoint will first subtract Qty on hand values from suggested quantities, and then compare the adjusted suggested quantities to maximum quantities.

18 CounterPoint V Release Notes 18 Sending purchase orders to vendors via In this version, when you print a purchase order, you now have the option of sending the PO to a vendor via- , using the address that is on file for the vendor or an e- mail address that you specify. NOTE: This feature will be delivered in a V Service Pack. Printing original receivers from Received PO History In Purchasing > Batch printing, you can now select a single receiver or a range of receivers from Received PO History and reproduce the original receiver(s). To reproduce one or more receivers from history, select the Receivers option from the Batch print for field, and then specify the Form ID, P.O. # range, Receiver # range, Vendor # range, and other parameters for the purchase request(s) you want to print. NOTE: Reprinted receivers that were generated from allocated, merged purchase requests will not include allocation information. Further, grid information for gridded items cannot be reproduced on receivers that are printed from history. Instead, each color/size combination will appear on a reprinted receiver as if it had originally been entered on a separate line.

19 CounterPoint V Release Notes 19 Sales History Viewing full card numbers in ticket history no longer allowed In previous versions, authorized users could view full, unencrypted credit card numbers in ticket history. Each time a user viewed an unencrypted card number in ticket history, the activity was logged to the SECURITY.LOG file, providing an audit trail. In this version, to further protect sensitive cardholder information, CounterPoint no longer allows any user to view full, unencrypted credit card numbers in ticket history. As a result, the View credit card numbers? setting that authorized a user to view unencrypted card numbers has been removed from Setup > System > Users. NOTE: Credit Cards Refer to the PCI DSS Compliance Guide for more information about PCI DSS requirements. Support for partial authorizations and full reversals To better support prepaid credit and debit cards, CounterPoint can now obtain an authorization for an amount that is less than the amount due for a ticket or order via CPGateway or CPDialup. For example, if the Total for a ticket is $30.00 and the customer presents a prepaid credit card with a balance of $25.00, CounterPoint will obtain an authorization for $25.00, and then prompt the user to tender an additional payment for the remaining amount due. In addition, CounterPoint now also supports full reversals of credit card authorizations, allowing authorized credit and debit card payments to be deleted from a ticket or order before the document is complete. Partial authorizations are supported for First Data North, TSYS, and AmEx Direct transactions. Full reversals are supported for use with First Data North and TSYS. NOTE: This feature was released in a V Service Pack. Partial authorizations and full reversals for RPS/RBS Lynk In this version, partial authorizations and full reversals are now supported for use with Radiant Payment Services and RBS Lynk. NOTE: Paymentech and First Data South do not currently support partial authorizations and full reversals.

20 CounterPoint V Release Notes 20 Multi-Site Disabling the transmission of encrypted credit card numbers In CounterPoint V7.5.17, Multi-Site transmission files did not automatically include credit card numbers. However, if your Satellites communicate with your Hub via VPN, you could choose to transmit encrypted card numbers by selecting Yes from the Xmit card info? field in Setup > Multi-Site > Control. In this version, to further protect sensitive cardholder information, you no longer have the option of transmitting encrypted card number in Multi-Site transmission files under any circumstances. The Xmit card info? has been removed from Setup > Multi-Site > Control. Data Interchange Option Additional fields in inventory import specifications In this version, you can now include the Discountable? flag, Open prc? flag, Transfer unit field and Tare code field in inventory import specifications. This feature allows you to import these values when you import item records using Data Interchange > Import inventory. To add these fields to inventory import specifications, first use Setup > Data Interchange > Inventory dictionaries to add field definitions for each field you want be able to import or update.

21 CounterPoint V Release Notes 21 Next, use Setup > Data Interchange > Inventory import specs to associate the Discountable? flag, Open prc? flag, Transfer unit field, and Tare code field with the fields you defined in the corresponding inventory dictionary. Once you have defined these fields in your inventory import specs, the corresponding values will be imported when you use Data Interchange > Import inventory to import item records.