When cloning billable expenses, I’ve noticed what I believe is a bug.
The issue can be reproduced as follows:
- record an expense A and assign it to client C
- clone the previous expense, name it B, and assign it to client D
- bill expense A to client C
- expense B is now automatically assigned to the invoice of expense A
I don’t know if this is intended, but I expected another behaviour.
I tried to duplicate your problem, following your steps exactly. Expense B does, indeed, disappear from Customer D’s balance of Uninvoiced items. The
Billable Expenses register shows it as invoiced. But drilling down into
Billable Expenses from the
Summary, no assignment to any invoice is shown. And
Accounts receivable does not include it. But it does not appear on Customer C’s invoice with expense A. That fact seems a little different from what you describe, but I may just be looking in more detail than you did.
I repeated the experiment without the cloning step. That is, I simply entered the two billable expenses via separate spending transactions. Done that way, there is no problem.
So the issue definitely arises only when the expense transaction is created by cloning. This is a puzzle for @lubos.
@Tut thanks for reproducing the issue.
Billable Expenses register, Expense B is shown as invoiced. When editing Expense B in the
Billable Expenses register, in my case however, it is shown that Expense B is assigned to an incorrect invoice. It is strange that I seem to have a different result here.
Another strange thing is the following: when reassigning Expense B to the correct invoice of Customer D in the
Billable Expenses register, Expense A gets also reassigned to the same invoice of Customer D.
When entering two billable expenses separately, there is no problem.
This is definitely a bug. I will be looking into this.
This issue should be fixed in the latest version.
We are experiencing a similar problem, could it be a bug?
Would you be able to assist?
@Mariette, the bug discussed in this topic was fixed more than three years ago. If you are having a problem, you need to furnish additional information. What version number of Manager are you using? Don’t describe a problem as “similar.” Give exact details about what it is, what triggers it, etc. Illustrate the problem with screen shots.
@Tut, Thank you for the response. Please see below a detailed set out of what we are currently experiencing:
We use the clone function to capture billable supplier invoices.
We captured a billable supplier invoice by cloning a previously captured supplier invoices, which previously captured supplier invoice has been billed to client and has been paid to supplier.
When looking at billable expenses the newly captured supplier invoice now reflects as invoiced, but it has not yet been invoiced to client. see screen shot.
It indicates that the newly captured invoice was invoiced to client / customer on invoice 309, see attached screen shot
When looking at invoice 309, the newly captured invoice was in actual fact not invoiced to client. reflected on the said customer invoice is the originally captured invoices which was cloned. see screen shot
As such when we clone supplier invoices already billed to client, the newly cloned invoice automatically appears as invoiced when in actual fact it has not yet been invoiced to client. we are currently using version 19.6.22.
@Mariette, based on what you have shown so far, this behavior seems correct. When you cloned the previous purchase invoice, you literally cloned everything about it. That is, you made an exact twin. The clone has the same issue date, invoicing status, due date, and so forth. The only thing that might have changed is the purchase invoice number, if you have a form default set for automatic numbering.
So when you create a new sales invoice from the Customers tab, you get what is no longer correct information for the new situation. The solution is to properly edit the clone before clicking the Create button.
Go back to that new purchase invoice and edit it with proper information. See if that doesn’t fix things.