Task from sale order - can invoice both

Bug #821261 reported by Kevin McMenamin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Released
Low
OpenERP R&D Addons Team 1

Bug Description

A task created from a sales order. Do some work & close the task - is now billable time. Create an invoice. Go back to the sales order and create an invoice. Effectively have invoiced for the same work twice - not good.

The two items are logically linked, so if billed via the task the sales order line should now be flagged as invoiced (and linked to the correct invoice & line). If billed via the sales order, then the quantity billed from the sale order should not be able to be billed via the task.

If qty worked <> qty on sale order should be a message at whichever is generating invoice so user can make decision on how to handle.

Tags: maintenance

Related branches

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

Hello kevin,

I have checked your bug report.
But I have one doubt on your one point.

I have create a SO (Service type product) confirmed it then the task was generated but this task doesn't like with the project So How can you generated a direct invoice for this task.

I think the only way to create a invoice though the sale order.

So Would you please provide us more information on this or provide the proper steps.

Thanks and waiting for your reply!

Changed in openobject-addons:
status: New → Incomplete
Revision history for this message
Kevin McMenamin (kevin-mcmenamin) wrote :

Amit

Firstly you make a good point about that task not being automatically linked to the project - in my view this is a gap as it requires an additional manual step for the user to do the linking - really if the SO has an analytic account that is a project, that project should be updated to the task when it is created.

Now to the bug...

You can actually create invoices from multiple sources - from a SO, from time (either linked to a task or to a project) or standalone (within the accounting area). So a SO is only one way.

For service lines created by a SO a task is created. When time is allocated against that task there is the ability to invoice for that time (e.g. see projects | invoicing | invoicing tasks work (the same function appears in multiple menus).

Have attached video to help explain.

Thanks
Kevin

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

Hello kevin,

Thanks for your reply, good explanation and excellent video.

I have faced two different problem here.
1) The analytic account from SO does not link as a project in task.
2) We can create a two different invoice for one SO, one from task and second from SO line which is described in bug report.

@RD Team:

I am confirming the first issue as a "Low" Importance and for second issue you will take the appropriate decision as a "Importance" either it's "Wishlist"(if it's feature request) or "Low".

Thanks.

Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 1 (openerp-dev-addons1)
importance: Undecided → Low
status: Incomplete → Confirmed
Jigar A. (ifixthat)
Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
Jigar A. (ifixthat) wrote :

Hello kevin, Amit,

     Thank you for Pointing the issue, we have Fixed the issue #1 "The analytic account from SO does not link as a project in task." according to comment #3 from Amit and committed the fix in branch lp:~openerp-dev/openobject-addons/trunk-bug-821261-jam and proposed it for merging in trunk-addons. And Issue #2 we are Keeping it as "Wishlist", so Kevin You can Open new bug for the same, we are closing this bug with issue1 fixed

Thanks Again.

Changed in openobject-addons:
status: In Progress → Fix Committed
tags: added: maintenance
Revision history for this message
Thibault Delavallée (OpenERP) (tde-openerp) wrote :

Merged into lp:openobject-addons at revision 5511

Changed in openobject-addons:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.