Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bill task work selects wrong receivable account in multi-company context #371

gurneyalex opened this issue Jun 6, 2014 · 2 comments


Copy link

commented Jun 6, 2014

When running Bill Task Work, it is possible to create an invoice where the partner account (field account_id) is from a different company than the invoice.

This one applies to 6.1 and trunk.
It is a variant of lp:1047826.

How to reproduce:

  1. install trunk and accounting module and hr_timesheet_invoice module
  2. create 2 companies A and B with diferrent charts of account
  3. create a 3rd company M as partent of A and B
  4. set set user preferences to company M
  5. create a partner
  6. create an analytic account named Project1 for company A with invoice factor = 100%
  7. create timesheets on Project1
  8. run bill task work
  9. you get a draft invoice for company A (the account's company), this is correct
  10. if you click on the receivable account to see the details, you see it is the receivable account of company M -> this is not correct.

I'll attach a merge proposal.


This comment has been minimized.

Copy link
Contributor Author

commented Jun 6, 2014

antespi pushed a commit to Antiun/odoo that referenced this issue Nov 19, 2015
Merge pull request odoo#371 from credativUK/8.0-email_template_fix
[FIX][email_template] Generate report with relevant partner id only

This comment has been minimized.

Copy link

commented Oct 13, 2016

Dear @gurneyalex,

Thank you for reporting this issue!
At this point Odoo 6.0, 6.1 and 7.0 are no longer supported for bugsfixes anymore, which means we will no longer handle these bugs.
If you still face this issue on Odoo 8, 9 or 10 we'd like to ask you to create a new issue on how to reproduce this.
Our apologies.


@Yenthe666 Yenthe666 closed this Oct 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.