Change "Credit notes" to "Gift Voucher"

Is it possible to rename “Credit Notes” in the location shown in the screenshot to “Gift vouchers”

Thanks!image

read the guide https://www.manager.io/guides/7877

Hi

that guide shows how to change the title in the report (which I have already done) but I would like to be able to change the title in the side listing as shown on the screenshot from “Credit Notes” to “Gift Vouchers”

nowhere in the guide it is mentioned that it is applicable only to reports. it was just an example where the title was changed to Travel Expense Report.

I can easily change the form title as per guide 7877 but I really want to change the title in the side listing.

can anyone tell me if this is a possibility?

Thanks

sorry i just noted you had circled the tab listing in your screenshot.
the tab names cannot be renamed by users.

thanks for that, its an unfortunate limitation. It would be good to be assign a different “display” name in these tabs

@sandpiper8, you really should not be using the Credit Notes tab to record gift vouchers. Credit Notes are meant for the reversal or partial reversal of sales invoices. See https://www.manager.io/guides/7425. They affect the Accounts receivable balance and will be applied automatically to future sales invoices, which the customer may not desire. (The customer may wish to hold the gift for future use.)

Instead use Special Accounts. See the final example in this Guide: https://www.manager.io/guides/10555.

@sandpiper8, if you are “selling” gift vouchers as implied by your 0000000%20Bug%201 then you would not use the @Tut suggested “Instead use Special Accounts. See the final example in this Guide” as that example only relates to business’s who are internally generating the “Gift Voucher” as highlighted by the guide comment “store credits given to customers”. Note: “given” not sold.

When selling gift vouchers you need to decide when you want to recognise the income, when sold or when redeemed. If you aren’t tracking inventory then when sold is okay, but if you are tracking inventory then when redeemed is best.

If tracking inventory then I would suggest this process as it eliminates the need to use Journal Entries and it fits neater into normal transaction processing.

1 - Create a BS > Liability chart of account called “Unredeemed Gift Vouchers”
2 - Now when you sell a gift voucher, the receipt is posted as:
0000000%20Bug%203a

If you number the gift vouchers, then use the description field.

3 - When the gift voucher is redeemed create a cash receipt with a contra line:

If the gift vouchers have an expiry date, then each year end you need to adjust the Unredeemed Gift Voucher account for those expired gift vouchers.

The example was only an example, not meant to be limiting. The term given refers in this case to any method by which credit is assigned to a customer. That could be via journal entry if a customer loyalty bonus has been earned. But you can still use the special accounts approach when a gift voucher is sold. When entering the sales invoice or receipt, simply enter the control account being used for the special accounts and the subaccount for the particular special account.

The amount of work is about the same either way, since a transaction must be entered to assign the credit to the customer. But the special accounts approach I described segregates balances remaining on individual gift vouchers. This is quite useful if they are not spent entirely on one purchase and makes them much easier to look up. The other approach described lumps all gift vouchers together in a single, undifferentiated balance. So you cannot tell how much is remaining on a specific voucher. Nor can you easily look up a gift voucher balance.

You can’t assign a credit to a customer (customers tab), and also assign that same credit to a separate control account.

Wrong, when entering a sales invoice you can’t select from the account dropdown a control account.

That is why this guide is flawed, it confuses and mixes up customer and cash sale terminology.
It states quite clearly ““store credits given to customers” (customers tab) yet the example provided is a Cash Sale transaction.

Furthermore, there is a significant difference in legal contractual terms between a business giving credit (loyalty programme) and a business selling credit (gift voucher).

Apparently, as you have repeatedly advise in so many other topics - just use the search feature.

Nor did I say you could or should. I suggested assigning the credit to a special account, which was the entire point here. For example, set up a control account, Gift vouchers. Create a special account for Customer ABC Gift Voucher 12345. Enter a sales invoice:

The only differences between the Guide and my example are (1) the Guide’s control account was Store credit, while mine was Gift vouchers and (2) the Guide’s special account was named only after the customer, while mine included both customer and gift voucher number.

You most certainly can, unless the account is in-built. See the above illustration. The ones you cannot select are those like Accounts receivable or Accounts payable, because they are wrapped up with hard-coded postings connected to customers and suppliers. When you create your own custom control accounts, you are not limited in that way, because there is no underlying hard-coding that might be interfered with.

No, it definitely does not. You added the words “(customers tab).” The actual Guide language is shown in the following screen shot:

The term customers was used only because the example that follows was about a store credit for a customer. So the special account was named after a customer. But nowhere is the Customers tab referenced. And the custom control account was not made up of Customers, but of special accounts. In the preceding paragraph of the Guide, there was mention of using special accounts for loans. Those special accounts might have been named after loan numbers or mortgaged properties or construction equipment purchased.

The fact is, use of special accounts for tracking gift vouchers was one of the purposes for them explicitly mentioned by @lubos when the feature was first introduced in mid-2016 (see the end of the following release note):