Page 1 of 1

Simple question - what is the correct way to assign DC charges to budget categories

Posted: Sun Jul 31, 2011 5:26 pm
by denlocke
In trying to figure out what is happening with our budget, I've come across some things in our MLS that is having me question the way we've been assigning expenses to budget categories, particularly those from the Distribution Center. When a DC charge shows up in the Expense report, I have been clicking on it, and in the Category window, I would choose a budget category that the expense should come out of. Is this the correct way to allocate the expense?

What is happening, is that the we are getting duplicate expenses kicked back after the change is sent. For example, we had a distribution charge of $13.00. I assigned it in this fashion to Budget:YM. Now when I look at that transaction, I see:

DC Charge $13.00 sent (original item showing up in system)
Adjustment by user (me): $0 sent
Adjustment by user (no username specified): $13 cleared
Adjustment by user (no username specified): -$13 cleared

so now when I open the original item, in the Category window I see:
Budget: YM $26
Budget: Distribution Center Charges $-13

So somehow it's doubled and now in my budget report my Expenses column of Distribution Center Charges is a positive number. I do plan on getting a hold of our Stake Finance Clerk for some training but there has been a recent changeover and I'm in limbo at the moment. Any tips in the meantime would be greatly appreciated!

Posted: Sun Jul 31, 2011 5:42 pm
by russellhltn
Is this the same bug reported in this thread?

Posted: Sun Jul 31, 2011 10:21 pm
by denlocke
RussellHltn wrote:Is this the same bug reported in this thread?

That's exactly what's been happening. Glad to know I'm not missing something simple. Thanks!

Posted: Sun Jul 31, 2011 11:00 pm
by crislapi
You might also see this thread. I'll mention I prefer to use a transfer instead of recategorizing the expense. That way, I can add a purpose to indicate what was purchased, and because it's a transfer, I don't experience any of the problems associated with this bug.