What happened
What this says
Current to 11 Oct 26Femi Olatunji reported duplicate transaction records appearing in the data with slight differences, affecting unique client counts. Investigation confirmed duplicates; customer traced root cause to their own accounting system.
Problem: Duplicate transactions inflating counts and skewing reporting. Handling: Bethan Lister investigated and confirmed duplicates were real. After 4 days Femi identified the source: a duplicate entry in their accounting system. Customer cleaned up the source data. Watch: Data quality issues erode trust even when external in origin. First response took 15+ hours on a data quality issue.
Details
Updated 9 Oct 26Trail
- created · Femi Olatunji 3 Sep 2026 09:16Hi, we're seeing some duplicate records in the data. We're getting the same transaction twice with slight differences. This is causing issues when we try to count unique clients. Could you investigate?
- public_reply · Bethan Lister 4 Sep 2026 00:44Hi Femi, apologies for the delayed response. I've picked this up. Just so I've got this right - you're seeing duplicate transactions in the data? Can you give me an example of what you're seeing so I can investigate?
- internal_note · Bethan Lister 8 Sep 2026 10:05Reviewed data. Confirms duplicates in transaction records. Likely due to duplicate source records. Ewan to investigate root cause on our data pipeline.
- public_reply · Femi Olatunji 8 Sep 2026 13:53We found the issue on our side - our accounting system had a duplicate entry that was pulling through. We've cleaned it up. Should the duplicates be gone now from the brain?
- status_change · 20 Sep 2026 23:59