What happened
What this says
As at Fri 9 Oct 2026Delivery exceptions appeared twice for one collection, which the customer said was inflating a client's invoice total. Callum Rix found the first entry was never closed when the collection moved; the ticket closed on 26 Jul 2026.
Problem: Callum Rix reported that some delivery exceptions appeared twice for one collection, once at the original time and once at the rescheduled time.
Handling: Bethan Lister asked for the client name and collection day, and Callum confirmed the first entry was never closed when the collection moved. The ticket was marked solved on 22 Jul 2026 and closed on 26 Jul 2026, but the record does not show what BG-Demo changed.
Watch: The customer said duplicates were inflating one client's invoice total, so a repeat would affect billing.
Details
Updated 9 Oct 26Trail
- created · Callum Rix 15 Jul 2026 08:46Morning. Some delivery exceptions are showing up twice in B-Viz for the same collection, one at the original time and one at the rescheduled time. Our ops team is counting the job twice, which is inflating one client's invoice total. Is this a duplicate in the source system or something on your side? Thanks, Callum
- Public reply · Bethan Lister 15 Jul 2026 12:46Hi Callum, thanks for the detail. Just so I've got this right: the same collection shows as two exceptions, one at each time? Can you send me the client name and the day of the collection? Then check whether the second exception was raised by a driver or added at your end, and tell me what you see. Thanks, Bethan
- Public reply · Callum Rix 16 Jul 2026 11:50Hi Bethan, yes, that's it. The second entry carries the rescheduled time and was logged on the courier side. I've checked and the first entry was never closed off when the collection moved. I can send the client name separately if that helps. Thanks, Callum
- Status change · 26 Jul 2026 23:59