Chat Transcript - June 2007
Chat Transcript – Payment Processing
Chat Topic: Payment Processing
Date: Friday, June 1, 2007
Note: Due to technical difficulties, only the second half of this chat transcript is available.
Modified receipts
Q9: (unavailable)
A: View the article about modified receipts here:
https://mbs.microsoft.com/customersource/support/downloads/reportslibrary/rms/ModifiedReports/modifiedreports_rmsstoreoperationsreceipts.htm
Closeout on Manager computer
Q10: Reply to Q5 and A5: As clearly stated in my original questions, the registers are not the problem; I was asking about the back office (non POS machines) RMS SO MANAGER computers where we need to enter the closing amounts for the blind batches.
A: In this case you would need to change the register number on the POS machine to be the register number of the back office machine; and then run a Z report. After running the Z report, you would need to change the register number back.
Q11: I would like to know if it is possible to get a print report when you settle your batch from Manager, so when it settles it would print a report of your total batch and card type totals.
A: There is no current report which totals the batch amount. The basic EDC report will give you each transaction, batch number and amount of the transaction. Please contact support if you need a customized report.
Q12: Clarification in regards to Q5: Currently if you add a new tender the changes will go into effect after the next Z report on each register, but on SO Managers computers the 'new" tender won't show up when you try update a blind batch (i.e. closing amounts).
A: The same response I just gave applies to this as well. You would need to change the register number on the POS machine to be the register number of the back office machine; and then run a Z report in POS to close the open batch for the back-office machine. After running the Z report you would need to change the register number back on the POS machine; and would be able to go into Manager on the back-office machine and perform the blind closeout. This shouldn't be a normal occurrence but will work since you shouldn't have to do it too often.
Q13: In regard to Q10: This seems an odd way of handling this (and not documented as far as I know), not to mention the additional batches that are unnecessarily being created, which accounting doesn't like. Is there really no other way to handle this?
A: There is a Knowledge Base on this which is in the process of being published. If you run a Z report to activate your new tender as is required, you are still creating another batch. Therefore, no additional batches are being created by using this workaround. The back-office machine is actually a register; and as such needs to have a Z report run in order for the new tender type to show up. How many new tenders are you creating on a daily, monthly, yearly basis?
Tender types
Q15: We used to use Gift Certificates, but we are switching to Gift Cards. If I don't plan on accepting Gift Certificates anymore, can I delete that tender type? Or is this going to give me problems with report or in Journal - Update batch info or anywhere else?
A: Do not delete your tender types at any given time.
Q16: Can I make a tender type inactive? If I can, how? If not, please add to next release. Thank you!
A: There is not a way to make a tender type inactive; and this is a great suggestion and as such I would recommend that you enter this as a Product Suggestion: http://connect.microsoft.com/dynamics
Q17: In regards to Q13: I'm not creating new tender types on a regular basis, it's just that when I do make a change or modification I have to update about 7 Manager computers and since they where never used as POS "registers" it seems that this is a bug/unnecessary.
A: All installs of RMS must be set up as a register with the current architecture to persist all Manager functionality (settlement, blind closeout, etc...). This functionality is by design.
