Product Release

Sales Totals Protected From Duplicate POS Transactions

Transactions that a POS reports more than once in the same transaction log are now detected and counted only once, so fuel and dollar sales are not inflated.

Sales figures are only as reliable as the data the point of sale sends. A bug in certain versions and configurations of some POS systems causes the same transaction to be reported more than once within a single transaction log. Counted as received, each repeated transaction inflates fuel volume, dollar sales, and every report built on them; at an affected site, the totals for the period can double.

What Is New

  • Automatic duplicate detection — each transaction received from the POS is checked against the others in the same transaction log, using the unique identifier the POS assigns to every transaction
  • Counted once — a transaction reported more than once is recorded a single time, so fuel sales, dollar sales, transaction details, exports, and the sales figures compared against tank inventory reflect what was actually sold
  • Distinct sales are never merged — the transaction type, register, ticket number, and time are compared as well as the identifier, so two different sales cannot be combined; transactions that carry no identifier are kept as received

Why It Matters

Sales totals stay consistent with the activity at the site even when the POS repeats data, so reconciliation, consignment billing, and comparisons between sites are not distorted by double counting. Duplicate detection runs automatically for every connected site and requires no action from the operator.

Operators who have been affected by duplicate transactions should contact Kii product support.

Related Features

See This in Your Own Operation

Request a walkthrough of the platform with your sites, tanks, and reporting needs in mind.