Incorrect time unit calculation when service item ends exactly at midnight
- Description of the issue: The customer has reported an erroneous time unit calculation at certain condition. So when a Service Order item ends exactly at midnight, then invoice and time units are doubled. The enterprise currently treats multi-day bookings by summing repeated daily intervals, so an end time of 00:00 on the next day doubles the hours instead of counting as one hour.
- Account name: K.M.C. Kommunikations- und Medien-Center GmbH (Estrel Congress Center)
- Region: EMEA
- Client version: 26.1
-
Steps to reproduce:
- From Main Menu go to Events
- Search for Event ID 23901 and edit it
- Go to Service Orders and edit Service Order 128903
- Go to service order item window. Verify the marked Service order item below where Start date is 15th and end date is 16th, end time is midnight 00:01, time units are 17,02 while extended charge is 170,17 which is fine.
- Now if we change the End time to 00:00 then Extended charge and time units are doubled. Refer below screenshot:
- Now if we change the midnight time from 00:00 to 00:01 everything looks fine. Check screenshot below:
- Observed results vs Expected results: The time units and extended charge should not be doubled when end time is 00:00
- What is the job the client is trying to accomplish: the client is trying to add to the system Service Order Items that end at 00:00 featuring correct data.
- Business impact if not resolved:
- Links to articles where you've looked for solutions and also other steps you've taken to research the issue: Calculations, forecasts, invoices are not correct because of this behavior if someone is not monitoring it
- Link to Zendesk ticket: https://ungerboeck.zendesk.com/agent/tickets/383346
- Local v30 URL: https://supportwebemea.ungerboeck.com/Estrel_test/
Pieter Fourie Mike Schepker Nicole Loh Satya Ram Nukala : Should I report it as a bug? Thanks!
-
Seth Halvaksz Thank you for the hints!
I tried the workaround suggested by Martin in https://documentus.zendesk.com/hc/en-us/community/posts/30309617354903 and and set the Cutoff time amount to 100, but I could still reproduce the issue.
Then I tried what suggested by Minka in https://documentus.zendesk.com/hc/en-us/community/posts/35187459593367-Booking-Rates-for-Performance-Arts-Concert-Halls?page=1 and saw that the Calendar Overlap Cutoff Time is already set to 1:00.
The booking works fine when the end time is between 0:01 and 0:59, the issue is triggered only when the end time is 0:00 sharp. -
I believe this is unfortunately a limitation in the system for supporting events that last to after midnight.
I'll ask engineering to review this and comment if there's another workaround.
-
Thanks Seth Halvaksz !
-
Francesco Torchia in our system, an end time of 00:00 is “Midnight” as in the end of the current day.
For example, a booking for a single day with a start time of 00:00 and an end time of 00:00 is a *24 hour* booking.
In your example, you have an order item 04/15/2026 0700 - 04/16/2026 0001
This is a span of 17 hours and 1 minute, e.g. less than 1 full day (if rates are per day)
If you change the end time to 0000, this becomes a time span of 17 hours + 24 hours = 41 hours, which is almost 2 days, which might be why the price is so different.
The system has always worked this way, it is not a new feature or regression.
Does this help at all?
-
Thank you, Benjamin Schwenke ! I'll inform the customer about it.
Please sign in to leave a comment.
Comments
6 comments
Date Votes