I am having a rather new and odd issue I have not seen before where I run the report and the end time in the report ends before the current time. This has been a serious issue I finally solved when clients complained why they are coming up short every night. For some reason their reports want to cut off at a time before the time the report is printed.
EDIT: Found out what is causing this @VehbiEmiroglu reading an old post of Emre, he said workperiod end time is automatically set at last ticket time. This is a huge issue for me because this restaurant is not done when the last ticket was created. For example for my case its cutting off credit card payment information done after last ticket was created. The cutoff time should be defined I guess, and the report end time should be current time if workperiod has not ended yet or virtual work period defined end time if its another date when running the report.
When I navigate to report screen I get the following:
@Jesse What is your take on this… Does it make sense to let reports automatically assume that when the last ticket was created for that work period is when the cutoff time is…
First virtual work periods do not have a cutoff time they have a start time. That is important to understand.
What do you need reported that’s missing?
Btw it’s important for readers of this to understand this is specifically about virtual work periods. If you manually end work period it will use time ended. Virtual work periods use the time of last ticket before the defined start time as a reference for reports.
This is by design. If you need it to work differently I suggest not using virtual work periods and ending them manually every night.
Payments always come after ticket created, there are other things I’m recording in tasks like tips that they are putting in after that is not showing up. I can personally really see this as an issue. But okay I guess it might just be me I have no problem going back to custom work periods. I just uncheck workperiods and put in 0 for cutoff time right?
I know it’s a typo but to not confuse anyone, with virtual Work periods you are not setting a cutoff time you are setting a start time. It designates reporting periods based on the last ticket. It starts at the time you designate in settings. So you set the time to when you want a wp to start.
That seems a pretty sketchy point to cut of, as hasa said unless you are cash/over counter only business ie no tables or cubmitted/unpaid tickets there will always be payments, order and other stuff happening after the ticket time of last ticket or period… Surely it would be ticket closed time of last ticket if not 1 minute/second before the specified opening time.
