Preparing To Update Counterpoint

Preparing To Update Counterpoint

Depending on your current version of NCR Counterpoint, updating to the latest version may require updating the history tables as part of the update. Depending on how much history you have kept over the years, this process can take a while to complete. It also starts from the oldest and works its way to the newest so some history may not be there as a result until the process finishes. This can take anywhere from 30 minutes to a few days or even weeks.

To prepare for this, it is recommended to purge your ticket history to only keep 3 years or so on file. I would recommend talking to your accountant as to how much they recommended you keep.

For example, I recently updated a customer with about 10 years of history. It took approximately 3 days for all the history to be updated. The time it takes also depends on other factors like Internet bandwidth, speed of the servers, as well as how “clean” the data is.

If you are planning to update your software soon, please look into purging your ticket history to help the process run a little quicker.


Regarding CCS Testimonials

Regarding CCS Testimonials

How long has it been since you read the current testimonials on our CCS website? I must admit that I have not taken time to catch up on this recently, but today I decided to schedule a few minutes to check this out. I’m glad I did; it made my day!

We serve customers from many types of companies in the U.S. and Canada – some single sites, some multiple sites. The range covers businesses such as sports stores, pet stores, gift shops, museums, nurseries, food stores, liquor stores, forest product stores, party supply stores, book stores, music stores, and many, many others.

Some of our customers have been with us for a good number of years, as we’ve been in business since 1987. Some are new, often ones who are starting their own businesses. The comments that they have offered about their experiences in using NCR’s Counterpoint and the services provided by CCS are ones you should definitely read. People who actually use the product often give information in their testimonials that will prove to you that their successes could be YOUR successes.

Log onto our website today (, click on the menu button, and then on Testimonials to follow up on my suggestion. You’ll be glad you did!


Is there a Gap in your GAAP?

Is there a Gap in your GAAP?

GAAP (Generally Accepted Accounting Practice) standards are often overlooked. Things that you should look for are:

1. Running edit lists to review transactional data before posting it in batch. – This allows you to catch any errors or omissions prior to posting.

2. Documents that you create should always have unique numbers. This would be true regardless of what area of the software that the document being created in.

Examples: POS Orders and Invoices, A/P Vouchers and Checks (paper and EFT), Payroll Checks, General Journal numbers, etc.

3. Auditing as you go – Whenever you are doing transaction input, after auditing your work, you should have another staff member review it before you post it.

4. Grouping transactions by date or period– As you are making any adjustments, make sure that all adjustments that are posted together are on the same date and/or within the same accounting period – Meaning don’t post entries dated in January with activity for February or March.

Typically, in most software applications, a document number is considered a Primary Key, so it should be considered “Unique” and would not be duplicated. However, there are some programs where it might be a Secondary key where multiples might be allowed, such as using a sequence Number, such as when using duplicate entries and historical tables such as Check History (e.g. checks, voids for the same checks, or manual payments, EFT transactions, etc.).

Just because a program might allow you to insert duplicate data, that isn’t necessarily a good thing to do

Even in situations where the programming might allow for this sort of thing, a duplicate document number might cause other issues with software functionality. -As examples.

• Unique document numbers make auditing easier. If an auditor sees a lot of duplicate documents, it may prompt the auditor to dig deeper looking for other accounting irregularities, thereby artificially extending the length of the audit. An example of this sort of this would be a local, state or federal tax audit.

• A Ticket/Invoice number exists in history multiple times – So A user runs a report on ticket #54653 without having specified a date or date range. The subsequent report returns a dozen documents created over a period of 10 years.

• Problems posting – I have seen examples where end-users have used the same invoice number dozens of times. When they try to post a new voucher using the same invoice number, the program may hang or crash while it attempting multiple times to create a “New” document for one that already existed previously. As an example, the program might be writing data for the same document into history a dozen times, and they just stop the attempts to write the new data.

The worst example of this that I have seen so far, is with one vendor that 21 manual payments on file using an invoice and check number of “SUPPLIES”

In this case, a better example of document number creation would have been to enter numbers in a format like the following: “SUPMMDDYY” (e.g. SUP042519… or Supplies for 04/25/2019), or “VendNoPrefixMM252019) (e.g. BOS042519, Bobs Office Supplies for 04/25/2019).

Check number and Invoice numbers should always be auto-assigned.

If you have any questions or need assistance with the creating your own document number assignment schema, please contact the CCS Retail Systems Support department.

– John

Preparing for the Holidays

Preparing for the Holidays

The weather is turning colder, the clock has returned to Standard Time, and the holiday season looms before us. Already I am seeing candy canes on display in supermarkets! This makes me wonder if you are doing the necessary preparations in your business to make sure this holiday season is well-organized and profitable.

What can you be doing right now to get ready? Here are a few suggestions to get you started:

  • Make sure your inventory is stocked sufficiently and numbers are accurate. Eliminate errors now that could cost you sales later!
  • See those products on display are all labeled. Customers find it annoying when prices aren’t readily available.
  • Add needed information on your receipts, like return policy.
  • Clean up the store and arrange displays for best customer visibility. Polish that glass front door.
  • Make sure you have on hand sufficient gift cards; these are always a favorite for holiday gift-giving!
  • Update/prepare to use your customer information to send flyers and emails to advertise holiday sales.
  • Install newer, faster hardware, like printers or scanners. Waiting until the last minute to take care of your business “tools” could become a real hassle once the season begins.
  • Make sure that your security system is up to date. Remember, this is prime time for unscrupulous scamming.
  • Arrange for new employees’ training now to avoid problems later.
  • Consistently back up all of your files in case of the unexpected, like power outages from winter storms, or malicious ransomware attacks.

We can help you with many of these preparations, (but we don’t do windows!). All it takes is a quick call to 485-672-4806, or you can email us. We’re here to help you have a great holiday season!


Passport Version 12.06 Update for July 2018

Passport Business Solutions
Passport Business Solutions

Passport Version 12.06 Update

With the release of PBS 12.06, Passport completes a major infrastructure project on field expansions begun with the version 12.05 release. Enhancements for PBS 12.06 will include:

  • Expanded field sizes for both the name and addresses in Customer, Ship-to, and Contact files.
  • Field expansions in A/R, O/E, POS and Customer Order Processing in PBS Manufacturing.
  • Professional Time & Billing fields expanded.
  • PO # expanded to 30 characters to accommodate Amazon, etc.
  • Approximately 12-14 Accounts Payable SSRS (SQL Server Reporting Services) reports have been created
  • Three new SSRS reports have been created to replace the previous standard reports for wholesale distributors.
  • Passport 12.06 includes a new runtime, version 10.2, so a fresh install will be required and the use of EZ Convert is required to migrate your existing data to the new format.

Currently, version 12.06 is being thoroughly beta tested in-house at Passport. A Limited release will begin mid-July, 2018 with general release anticipated to be available at the end of July 2018

Please consult the CCS Support department if you have any questions on the above release.

– John

The threat of Attack on Point-Of-Sale (POS) systems

The threat of Attack on Point-Of-Sale (POS) systems

In the retail world, the threat of attack on Point-Of-Sale (POS) systems is always high, as they are a prime target for the bad actors trying to get credit card information. There is always new malware being created to try to get that information. There are, however, steps that can be taken to reduce the risk, even with regards to the latest attack software.

The best thing that you can do is to isolate your servers and workstations as much as possible. In an ideal world, these would be completely isolated, and not interact with any other systems. The reality is that this is very rarely the case. With that in mind, let’s look at some things that can be done.

The first step is to make sure that your firewall is as restrictive as possible. Your POS workstations and server if needed should only be restricted to accessing what is absolutely needed. In most cases, this is only your credit card processor. In no case, should your firewall allow either the workstations or the server, unrestricted access to the internet? The firewall will eliminate the chance for drive-by downloads, or users browsing to malicious sites.

Along those lines, any computers that are used for general internet browsing, and also email, should be on a separate network. If it is not possible to implement workstations on a separate physical network, at least use a different logical network as in a different network address range. Even just the different logical network, will stop the majority of malware infections.

If remote access is needed, and it should be restricted to those cases where it truly is needed such as your support company, then it should be restricted to only those addresses that have a legitimate reason to connect. Also, any such connections should be closely monitored. One such method is to disable the remote access software, and only enable it when your support personnel is actively connecting. Of course, it is again disabled as soon as they are finished.

Those cover the basics of securing your POS system. It is a good place to start, but it is only a start. Keeping software updated, training personnel, and keeping vigilant are always key components, also.