Senior Citizen Discount

[Jesse]

I will look at it and get back with you

[Jesse]

I just pm’d you a fixed DB. Let me know if its what you were looking for.

[Jesse]

So others can see what I did.

@Jesse

Ok I will show you… the only changes I made were the following:

Created Account Type: VAT Accounts Moved following accounts from Sales Accounts to VAT Accounts12% VATVAT Exempted SalesVAT Sales

I then changed each Transaction Type and reversed your process…

Source is now ReceivablesCredit is now Sales

For senior discount transaction type I just put Source = Receivables and left all of the other boxes blank.

I also moved your Payment Processed Rule: Process Breakdown Document

Instead of Payment Processed I made it Ticket Closed and put constraint {TICKET STATE:Status} Equals Paid The reason for moving your Payment Processed rule is because {TICKET NO} is not available until ticket is closed. It does not actually generate ticket # until ticket is closed. It works fine if you close ticket and they pay later… but if you ring up and settle imediately it would record 0.

So by moving it to Ticket Closed and putting that constraint in… it does the same thing but it allows us to enter {TICKET NO} into document descriptions for quick sales and for traditional table sales. The constraint makes it ONLY run when payment is processed and its Paid status so you can still close ticket and customer pay later like traditional tables.

@Jesse

Actually I was wrong you will not be able to link those to the ticket like you are wanting… only calculations can do that… however for reporting… you would show them your tickets… not your transaction documents. The reason being… the reality is these are just calculations… the Transactions your refering too as linked to tickets… those are just transactions… They all are linked to the actual ticket… what is throwing you off is the Ticket Transaction showing ticket number…

[Jesse]

I did find one potential flaw. In its current state… it would allow you to select more seniors… than guests… which could result in negative numbers and not be accurate… we need to put a constraint somehow to prevent you from selecting more seniors than you have guests.

I will develop a fix for you and pm you the DB and post my fix here.

EDIT: I have developed a fix for you but I have noticed a few other bugs with the way your doing your tagging for Guest and Senior count. I need to take a break but I will figure you out a solution.

EDIT: OK got you a fix.

The only thing I did was add a constraint on your Tag Ticket so now it checks on Settle Payment if Senior Count is greater than Guest count it fires a question telling you to change the guest count.

I also added a constraint on the Ticket Closed rule to prevent documents from being made on voided orders or on closed non paid tickets.

PM’ng you a database to look at my changes

[Jesse]

Since it is Ticket Tags there is not a way to constrain it from you being able to tag it… so I had to write a constraint if it is tagged.

[younicke]

This is fantastic! Thank you very much sir. This is exactly what I wanted and I couldnt have done this ithout your help and guidance.

Again thank you very much.

[rhon23josh]

May I know how will you compute your gross and net sales when there are senior citizen discounts and vat exempts sales given? Thanks

[chair]

hi kendash may i ask if i could get a copy of this database since this is the standard procedure in our country. if its not possible can i be thought on how to implement this thanks

[Jesse]

Hello,

It has been a while since I helped him with this. I do not have a database with this setup. Most of the work was done by @younicke he took the ideas I gave him and figured out how to do it. I helped him work through a few issues

[chair]

thanks ill try to ask him if he could share his database setup .