Currently we are creating credit memo, no problem. Lately, on the line, we need to specify for which item the credit is for When I enter the item, it ask for the inventory detail. For us, the item number is only a reference not inventory movement whatsoever. How can I do it ?

adding an inventory item when creating a Credit Memo will put that item back into inventory. If that is not what you want then use a non inventory item then have a custom column field to select your item to be used for reference purposes.

You could create non-inventory items that correspond to your items, and credit those. Custom field like @Israel Gonzalez suggested. OR, you could created to a location that doesn't use bins. This won't prompt for inventory detail, but will still credit the piece in to that location.

I like both ideas, thanks. Maybe it's not a credit memo. Let me take an example. It's a hardware company. They sell a product for 45$ they send the item an invoice it. Later, for some reason, the customer request 2$ back. The customer send a file will the $2 request. I need to import the file in Netsuite. As you can see, there was no inventory movement but we need to know what item has a credit, thus later we can do some analysis on that item and credit the customer on it's next purchase I think it's a credit memo. Right ?

We have the same scenario. We use @Israel Gonzalez' recommendation which is to use an item that is not inventory and use a custom field to link it to the actual inventory item credited.

OK. Let me ask. We have thousand of items, 1. do I have to create thousand of non inventory items ? 2. create 1 non inventory item for all and use it with the extra item info ?

You can do either, the second option would be the easiest as it just requires the one non inventory item and a custom line field. However, if you for some reason needed it to be a 1:1 then it would require a non-inventory item for each item and then probably a custom item field in order to have a reference between the two items.

If you're going the custom field route, then one non-inventory item, since it doens't matter. If you prefer to have a non-inventory item per Inventory item, then you don't need the custom field. I would go with one non-inventory item and a custom field.

Non of the above. How shall you make correct cost analysis of an item if you do it that way? Instead: Edit your credit memo form, or create a new one, and in the item sublist, remove the ”inventory detail” field. When you add the item. Use 0 in quantity, 0 in rate, and only use the amount field. You will get a warning like ”rate x qty does not match amount, sure u wanna continue?”. Press yes. Your inventory levels wont be effected Now all your cost and income can be inherited to the exact same item. So no need to add custom fields. No need to create made up items.

@Jesper M is it even possible to use 0 quantity for the inventory items? AFAIK, no. I hope I am wrong though because this would be easier though. I forgot to mention that in order to keep it linked to the original item (when it matters to us), we create an RMA for that inventory item, create a CM (does not affect inventory because it is the Item Receipt that does that), and close the RMA (do not create Item Receipt as there is no return anyway). @Simon

Yes. It is possible.

Great! Thanks. It's a good alternative for us. Sometimes we don't care about the units credited or the item rate, so we can use this workaround. Otherwise, we'll use the RMA-CM flow.

Ok! When you do the RMA-CM flow, you can do the item receipt but leave the ”restock?”-field on the item line empty.

Wouldn't that debit the write-off expense account and credit COGS? Although the net income will be the same anyway, we have gross profit and COGS KPIs that will be distorted because of that GL impact. And I don't think that GL impact is in accordance with IFRS/GAAP.

If you want only to have information which item is related to CM, I would try to create a new Transaction Line custom field sourcing the item list/record... ie Related Item...

@Zoran R-DATAGRAM works pretty bad in reports

What does it mean "works bad"?

You can not simply group on item level. You need case when on your custom field