Tracsis Travel Compensation Services (TTCS), the provider of automated Delay Repay claims management software solutions to Train Operating Companies (TOCs), has launched EXPOSURE to help minimise TOCs’ risk of exposure to fraudulent Delay Repay compensation claims across operators.
EXPOSURE is a new industry tool for detecting, investigating and preventing cross - TOC fraud in relation to Delay Repay claims. Where data sharing agreements exist, it compares multiple encrypted components of Delay Repay claims from different Train Operating Companies (TOCs) and sends real-time and retrospective alerts concerning potentially fraudulent activity for further investigation.
Speaking about the new software, TTCS’s Chief Information Officer, Lee Fortnum says: “We realised that train operators which don’t use our system for passenger Delay Repay don’t have access to our system’s advanced fraud checks benefits, such as identifying duplicates or conflicting submissions. Additionally, they have no way of identifying individuals who are potentially targeting several operators with the same intention. We knew we could design a simple, cost-effective solution and so we built EXPOSURE.”
The EXPOSURE software analyses Delay Repay claim data against a TOC’s desired risk weighting and specified thresholds, such as time of travel tolerances, and returns matches. It also creates retrospective alerts, if subsequent claims match newly created claims from other TOCs.
Sarah Dalby, Managing Director of TTCS, adds: “Raising the awareness of Delay Repay compensation amongst passengers is of upmost importance to train operators. They are required by existing and incoming franchise agreements to help increase its visibility, along with the speed of claim processing, and with that, comes an increased likelihood of fraudulent claims”.
“We’re always excited to find solutions that support operators to overcome common industry challenges and EXPOSURE is a smart one - it even alerts the TOC with its equivalent point of contact and claim reference at the other TOC involved in a query and we’ve seen nothing like it elsewhere.”