We use the Inventory adjustment with reason code as Jeff describes. The
reason I wouldn't do a $0 sale is that even though it will keep track of
your COGS accurately, it will show up in your Z report as COGS for the items
that you sold for that day. I like to know at a quick glance what my sales
for the day cost me, and entering your shrinkages this way will throw this
off. By using inventory adjustments, you still get your shrinkages reported
accurately, but avoid throwing off your COGS for the days sales. If you want
to do it at POS that's fine, scan in the item, hit F2, go into the items
properties and enter your adjustment. Pick the appropriate reason code, and
Olybikes and Jason,
Olybikes, have you considered doing weekly/monthly cycle counts for a single
department? Sometimes cuts down on employee "shrinkage"
Jason, the problem you will have is that your "Inventory Adjustment"
customer doesn't show _just_
this year's COGS.
A better option might be, is to set up a Reason Code for Inventory
adjustments, then select Prompt and Require a reason code for manual
adjustments in the Reason Code Options section. Then modify the item's
quantity direct in the properties. If you are posting to QB, it will post
to the same GL account as your Physical Inventory adjustment will.
To see your cost for any timeframe, run the standard Item Movement Report
and filter on your timeframe and Adjusted <>0. This will show any items
adjusted for either.
Get Secure! - www.microsoft.com/security
You must be using Outlook Express or some other type of newsgroup reader to
Click to see the full signature.