Must Set User Defined Payment in PAYMENT OPT. & RECEIPT LANG
Posted: Mon Jan 27, 2014 12:04 am
Setting up a user defined payment option (the 6th item on the PAYMENT OPTIONS screen) will not print your text description on the printed receipt.
After setting up the user defined type in the PAYMENT OPTIONS, all locations in the program will use the text description you set under the Payment options, such as payment choice when closing a sale, or reviewing past sales with the VOID feature. BUT not on the printed receipt!
To get your user defined description to print on the receipt there is a second step that is not documented in the user manual.
After setting up the user defined payment type under the PAYMENT OPTIONS in the POSCONFG the second step is to go to RECEIPT LANGUAGE screen in the POSCONFG and update the USER DEFINED TENDERED field (on lower right of screen) to match the text value you set in the PAYMENT OPTIONS screen.
Sometimes I have solutions to correct problems I find in the software. And in this case, I have three that Dale may want to consider.
1. Creates tens and tens of minutes of work for Dale:
It may make sense that if a user defined type is created on PAYMENT OPTIONS screen, the program should automatically set the same value in the RECEIPT LANGUAGE setup. In that way, the program screens will match the printed receipts. And the user doesn't have to go to two different screens to "define" the custom payment.
2. Creates one minute of work for Dale:
The user manual section describing "Payment Option" should be updated to explain the complete setup of the user defined payment type.
1. Enter your text on Payment option screen for the 6th payment option.
2. Now go to the RECEIPT LANGUAGE screen and enter the same text of the USER DEFINED TENDERED field.
And then the RECEIPT LANGUAGE section should also be updated to include a warning about changing the USER DEFINED TENDERED field, if in fact the user has already created a User Defined Payment type back on the "Payment Option" screen.
3. Creates NO work for Dale:
After reading this, Dale thinks to himself, "I'll put this on the virtual 'think about it pile'." And then goes about enjoying the rest of his evening, just as if he had never read this post.
Thanks Dale!
After setting up the user defined type in the PAYMENT OPTIONS, all locations in the program will use the text description you set under the Payment options, such as payment choice when closing a sale, or reviewing past sales with the VOID feature. BUT not on the printed receipt!
To get your user defined description to print on the receipt there is a second step that is not documented in the user manual.
After setting up the user defined payment type under the PAYMENT OPTIONS in the POSCONFG the second step is to go to RECEIPT LANGUAGE screen in the POSCONFG and update the USER DEFINED TENDERED field (on lower right of screen) to match the text value you set in the PAYMENT OPTIONS screen.
Sometimes I have solutions to correct problems I find in the software. And in this case, I have three that Dale may want to consider.
1. Creates tens and tens of minutes of work for Dale:
It may make sense that if a user defined type is created on PAYMENT OPTIONS screen, the program should automatically set the same value in the RECEIPT LANGUAGE setup. In that way, the program screens will match the printed receipts. And the user doesn't have to go to two different screens to "define" the custom payment.
2. Creates one minute of work for Dale:
The user manual section describing "Payment Option" should be updated to explain the complete setup of the user defined payment type.
1. Enter your text on Payment option screen for the 6th payment option.
2. Now go to the RECEIPT LANGUAGE screen and enter the same text of the USER DEFINED TENDERED field.
And then the RECEIPT LANGUAGE section should also be updated to include a warning about changing the USER DEFINED TENDERED field, if in fact the user has already created a User Defined Payment type back on the "Payment Option" screen.
3. Creates NO work for Dale:
After reading this, Dale thinks to himself, "I'll put this on the virtual 'think about it pile'." And then goes about enjoying the rest of his evening, just as if he had never read this post.
Thanks Dale!