Comment 1 for bug 999756

Revision history for this message
Amit Parik (amit-parik) wrote :

Hello Janis,

You have posted this bug report for two different issue.

1st is for proforma invoice and 2nd is on multi-company behaviour you have faced the following error.

"ValidateError Error occurred while validating the field(s) company_id: Company must be the same for its related account and period."

let's first talking about your second point which is invalid because it's not a bug but it's behaviour.You can not validate the other company 's invoice (means your invoice belong to different company then your user). For that you have to use "User Preference" wizard and change the company according to you invoice. For more info and video would you please check lp: 996453, Surely which will help you.

Now comes upon your 2nd issue, As you said after the proforma invoice you can not validate it edit it. The final solution is you have to cancel the invoice, Set invoice at draft state then you can edit it and validate (But I don't think it's good process).

So As per my "Opinion" we have to check the invoice line at the time of the proforma same as a validate time. If there is not invoice line then we can not allow to proforma. For that I have provided a one use case here.

Use-Case: We have use a proforma state for holding of our invoice . After the proforma state we can print our invoice and sent this invoice to customer for the validation (Which is the real scenario). In generalise way first we have proforma invoice, print the invoice send the invoice to customer for the approval for validation. If customer gives a approval then we have to validate it.
At this time assume that we don't have a invoice line and we have sent it to customer, So it doesn't make sense ;-).

So as per the my "Opinion" we have to check invoice line at the time of proforma.
Which will also solved your 1st issue and reduce the more useless steps as I said(Set invoice at draft state then you can edit it and validate ).

I will provide a brach for it :)

Thanks for the understanding!