# ReOpen Ticket and Refund Ticket Behaviour

**URL:** <https://forum.sambapos.com/t/reopen-ticket-and-refund-ticket-behaviour/8091>\
**Category:** V5 Question\
**Created:** [November 12, 2015, 2:42pm UTC](https://forum.sambapos.com/t/reopen-ticket-and-refund-ticket-behaviour/8091 "2015-11-12T14:42:14Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![pauln](https://forum.sambapos.com/user_avatar/forum.sambapos.com/pauln/32/12698_2.png) [@pauln](https://forum.sambapos.com/u/pauln)\
**Post date:** [November 12, 2015, 2:42pm UTC](https://forum.sambapos.com/t/reopen-ticket-and-refund-ticket-behaviour/8091/1 "2015-11-12T14:42:14Z")

</div>

With references to:

> [@Refund Item button](http://forum.sambapos.com/t/refund-item-button/2119):
>
> This setup is originally based on the Tutorial by @emre, here: However, as discussed in that thread, I wished for an alternate method so that Accounts would reflect the correct Balances. Operational Flow: First, you will need to implement this setup, to be able to Re-open a previously-Settled Ticket: Once you have the above implemented, the setup of the Refund button is simple. Ensure your Ticket Types have the option selected for Allow Zero Priced Orders: [image] Au…

> [@Re-open Settled Ticket & Cancel Payments](http://forum.sambapos.com/t/re-open-settled-ticket-cancel-payments/1600):
>
> The short version of this originally posted here: Enable More Ticket Actions Module from Samba Market. This module enables Reopen Closed Ticket and Cancel Payments action types. Create two actions for both of these action types. These actions do not have parameters. Create “Display Ticket” action, name it Refresh Ticket. Set TicketId parameter as 0. Create an Automation Command, name it as you wish an place it somewhere suitable. Create a Rule to handle this command and call Actions Reo…

So I have implemented these and have been testing.

**Question1:** We are able to open tickets from closed Work Periods. How do we feel about this? I see no real issue as long as Work Periods are Balanced off.

**Question2:** With regards to the above (1) if we change the Payment Method i.e. Cash → CC or delete an Item it _does not effect the Work Period Report_ from that Closed Work Period. So again I assume this is by design and have no issues with this behaviour unless this is an refresh bug?

**Question3:** Looing around the method I see no way to lock a operator into the Current Work Period Only? I know as soon as we do this somebody is going to ask _“Last week you sold me this thingy and I do not want it anymore…!”_

Thoughts.

---

<div class="post-metadata">

**Author:** ![Jesse](https://forum.sambapos.com/user_avatar/forum.sambapos.com/jesse/32/61493_2.png) [@Jesse](https://forum.sambapos.com/u/Jesse)\
**Post date:** [November 12, 2015, 2:55pm UTC](https://forum.sambapos.com/t/reopen-ticket-and-refund-ticket-behaviour/8091/2 "2015-11-12T14:55:47Z")

</div>

> [@pauln](#):
>
> Question2: With regards to the above (1) if we change the Payment Method i.e. Cash -\> CC or delete an Item it does not effect the Work Period Report from that Closed Work Period. So again I assume this is by design and have no issues with this behaviour unless this is an refresh bug?

Work Period reports are derived from the database its not a stored report. So if you change anything that it uses to generate the report then it will change the report. So yes if you change the payment method then the work period report would also change to reflect that. If for some reason you tested this and it seems its not changing can you give more details and screenshots so we can see what is happening. It should not be a refresh issue because reports are not stored they are generated.

Keep in mind that if you reopen closed ticket and then you resettle its dating it for the current work period not the past work period.

---

<div class="post-metadata">

**Author:** ![emre](https://forum.sambapos.com/user_avatar/forum.sambapos.com/emre/32/39073_2.png) [@emre](https://forum.sambapos.com/u/emre)\
**Post date:** [November 12, 2015, 3:01pm UTC](https://forum.sambapos.com/t/reopen-ticket-and-refund-ticket-behaviour/8091/3 "2015-11-12T15:01:04Z")

</div>

> [@Jesse](#):
>
> Keep in mind that if you reopen closed ticket and then you resettle its dating it for the current work period not the past work period.

That is ture for V4 work period reports but I’m not sure if Custom Reports does it too.

---

<div class="post-metadata">

**Author:** ![Jesse](https://forum.sambapos.com/user_avatar/forum.sambapos.com/jesse/32/61493_2.png) [@Jesse](https://forum.sambapos.com/u/Jesse)\
**Post date:** [November 12, 2015, 3:01pm UTC](https://forum.sambapos.com/t/reopen-ticket-and-refund-ticket-behaviour/8091/4 "2015-11-12T15:01:51Z")

</div>

I might need to test that then. I was going by the logic of how it typically generates reports.

---

<div class="post-metadata">

**Author:** ![pauln](https://forum.sambapos.com/user_avatar/forum.sambapos.com/pauln/32/12698_2.png) [@pauln](https://forum.sambapos.com/u/pauln)\
**Post date:** [November 12, 2015, 3:04pm UTC](https://forum.sambapos.com/t/reopen-ticket-and-refund-ticket-behaviour/8091/5 "2015-11-12T15:04:36Z")

</div>

Yes I can not emphatically say it DID NOT update the work period but I did print the “Closed” work period, Reopened the Ticket, Deleted & Changed Stuff, and Settled. I am 95% sure the Report did not change…

That’s why I posted it here 😄 to ensure I was reading it correctly.

---

<div class="post-metadata">

**Author:** ![QMcKay](https://forum.sambapos.com/user_avatar/forum.sambapos.com/qmckay/32/27925_2.png) [@QMcKay](https://forum.sambapos.com/u/QMcKay)\
**Post date:** [November 12, 2015, 5:07pm UTC](https://forum.sambapos.com/t/reopen-ticket-and-refund-ticket-behaviour/8091/6 "2015-11-12T17:07:45Z")

</div>

Likely because, as @Jesse mentioned, when you re-settled the Ticket, it became part of the current Workperiod (date-wise), and will no longer be included in the original Workperiod.

That said, it should affect the previous report, since the Ticket was removed. Sales for that period should be decreased.

---

<div class="post-metadata">

**Author:** ![pauln](https://forum.sambapos.com/user_avatar/forum.sambapos.com/pauln/32/12698_2.png) [@pauln](https://forum.sambapos.com/u/pauln)\
**Post date:** [November 13, 2015, 2:24am UTC](https://forum.sambapos.com/t/reopen-ticket-and-refund-ticket-behaviour/8091/7 "2015-11-13T02:24:30Z")

</div>

> [@QMcKay](#):
>
> Likely because, as @kendash mentioned, when you re-settled the Ticket, it became part of the current Workperiod (date-wise), and will no longer be included in the original Workperiod.

Just for the current record: Voids & Payment Changes go into the **Old Work Period** if an old ticket is Reopened.  
Checking the Closed Work Period report all figures and payment types are updated correctly. Not sure what I broke last time but cannot reproduce where figures were not reflected in the Closed WP…

---

<div class="post-metadata">

**Author:** ![emre](https://forum.sambapos.com/user_avatar/forum.sambapos.com/emre/32/39073_2.png) [@emre](https://forum.sambapos.com/u/emre)\
**Post date:** [November 13, 2015, 11:30am UTC](https://forum.sambapos.com/t/reopen-ticket-and-refund-ticket-behaviour/8091/8 "2015-11-13T11:30:34Z")

</div>

We shouldn’t alter old tickets for any reason. Reopen ticket is the worst thing I’ve ever put into SambaPOS.

---

<div class="post-metadata">

**Author:** ![pauln](https://forum.sambapos.com/user_avatar/forum.sambapos.com/pauln/32/12698_2.png) [@pauln](https://forum.sambapos.com/u/pauln)\
**Post date:** [November 13, 2015, 1:18pm UTC](https://forum.sambapos.com/t/reopen-ticket-and-refund-ticket-behaviour/8091/9 "2015-11-13T13:18:34Z")

</div>

I would not stress about this one bit emre - it requires no further Dev work in my opinion as the function should be used **sparingly and by Administrators only**. For me I was just searching down every avenue for functions being implemented for our situation.

It really was the testing of how the Refund Button operates in this case so it has been put to bed. _“Bigger Fish to Fry”_ in Customer Accounts for me.
