A Vending Sales Export Contains the Same Day Twice: Remove Duplicate Data Before Comparing

A vending sales spreadsheet can show an unexpected jump when the same day’s data has been imported twice. Before celebrating the increase or changing the refill plan, check whether the report contains duplicate records. Preserve the original files and investigate the source rather than deleting rows simply because two amounts look alike.

Repeated values do not necessarily mean repeated data. Two machines can sell the same amount, and two genuine transactions can share a price. The task is to establish which record identifies the underlying event and whether the same event has been included more than once in the working report.

Preserve the source before correcting

Keep an unchanged copy of each export with its creation date, selected period and machine scope. Work on a separate reconciliation copy. Note whether the file contains individual transactions, daily totals or another level of detail. Combining different levels without recognising them can double-count activity even when the rows are not identical.

For example, a daily summary may have been appended beneath its underlying transaction list. Adding every row would then include the same activity in two forms. Alternatively, overlapping weekly exports may both contain Friday. Identify the structure of the files before applying a spreadsheet command that removes apparent duplicates automatically.

Choose a suitable comparison key

Use the source system’s transaction identifier where it is available and appropriate. For daily aggregates, the relevant combination may include machine identity, date, payment type and report definition. Confirm the meaning of the fields with the provider if necessary. Date and amount alone are usually insufficient to explain whether two rows represent the same event.

Keep corrections or reversals distinguishable from duplicate imports. A later record may intentionally change an earlier result. Do not discard it because it shares a reference without understanding how the reporting system represents amendments. Ask the provider to explain uncertain cases and retain the response with the reconciliation notes.

Correct the working report transparently

Once a duplicate import is confirmed, exclude the repeated record from the analysis while retaining an audit note showing what was removed and why. Recalculate totals and compare them with the source report for the same scope. Avoid altering the original export or the underlying payment records as part of a spreadsheet tidy-up.

When reviewing vending performance and service requirements, use the corrected figures and state the reporting period clearly. If a previous report was circulated with the inflated total, issue an identified correction. People planning stock or assessing demand need to know that the change reflects data correction rather than an actual decline in customer purchases.

Prevent the same import problem

Record which files have already been imported and define whether a new export replaces or extends the existing period. Use a repeatable check for overlapping dates and machine scope before appending data. Keep the process simple enough that a cover colleague can follow it without relying on the original spreadsheet author’s memory.

At the next reporting cycle, test the check using a small known overlap and verify that genuine separate transactions remain intact. Retain unresolved exceptions for review rather than forcing them into a clean-looking total. A reliable sales report needs both completeness and freedom from confirmed duplication; neither is achieved by deleting every row that happens to look similar.

Related guidance: Vending Sales Reports Use Different Cut-Off Times: Align the Period Before Comparing.

For help assessing your site, contact Vending-Machines.ie.