That confirms what i already thought.
Although i must say that imho last payment date seems the correct method somehow,
The default workperiod reports does seem to do better with the last payment date(at least in my case).
But on the other hand it’s easy enough to change the ticket date with an action or script(as i do) (maybe pre ordering and changing date when non-pre ordering is an option for chris89?; Running tabs/re-opening tickets V5). Doing this will give you control over in which workperiod the ticket is. For the default workperiod report i already have most of the things i would like to know in my own report.
I know that everybody says that i shouldn’t use the Pre Orders for multiple days tickets, but renting out a room, pitch or bicycle is working pretty nice together with a product timer.
I just use some ‘ask question actions’ that will add products with product timers (caravan, camper, people on pitch, tourist tax, etc) and in the night I Pre Order all tickets when closing the workperiod (scripted).
This will give me a single ticket and printed bill in the end.
Starting a new workperiod I run a script that will set all pre-orders back to normal tickets and will change the ticket date.
Up till now I haven’t seen any real drawbacks, BUT I must say that for my setup i don’t really care who has made the sale, who gets tip and that kind of stuff. It’s just me and my wife operating SambaPOS from about 4 different devices (Mobile Phone, Laptop with Touch, or PC).
The Sales and Financial information in the Database is solid and that does matter 
But I’m not i a hurry for the 5.56 so take it easy