[
http://jira.undersunconsulting.com/browse/OFBIZ-796?page=all ]
Jacopo Cappellato closed OFBIZ-796:
-----------------------------------
> Re-factor invoice status codes and valid changes
> ------------------------------------------------
>
> Key: OFBIZ-796
> URL:
http://jira.undersunconsulting.com/browse/OFBIZ-796> Project: [OFBiz] Open For Business
> Type: Improvement
> Components: accounting
> Versions: SVN
> Reporter: Si Chen
> Assignee: Jira Administrator
> Fix For: SVN
>
>
> This is an issue Hans Bakker brought up from using the accounting application.
> Currently all invoices, sales (AR) or purchase (AP) go through IN_PROGRESS to READY and then to SENT or RECEIVED then to PAID and COMPLETED. READY is equivalent to "approved and finalized," and no further changes are allowed. Hans's issues are:
> 1. If a sales invoice is send out to a customer, and he is OK with the amount but
> not with the description of the item line and asks for an updated invoice.
> How should this be handled? I thought the best way is to cancel the 'send' invoice, copy the invoice,
> correct the description and send the new one with a new invoice number.
> However now i cannot cancel a sales invoice with a 'send' status.
> 2. What about a purchase invoice which is entered in the system with a 'received'
> status and the supplier informs you it was sent by mistake and you can throw
> it away. However currently i cannot cancel a 'received' purchase invoice.
> 3. If i allow a purchase invoice in the ready state then it cannot
> go to the received state because the status-changed table does not allow a
> change from ready->received... Because it assumes a purchase invoice cannot have the ready status?
> 4. the description of the 'ready' status is: 'ready to send' in the
> status table.... not really appropriate for a purchase invoice?
> Hans suggests the following possible paths for the invoice:
> sales invoice: in-progress -> ready ->send -> paid
> ->cancelled
> ->in-progress
> ->cancelled
> ->cancelled
> Purch invoice: in-progress -> ready -> received -> paid
> ->cancelled
> ->in-progress
> ->cancelled
> ->cancelled
> I think what I really need are 3 states:
> 1. When the invoice is considered final and no longer changeable, which READY is right now.
> 2. When the invoice is marked PAID
> 3. When the invoice is marked COMPLETED
> My recommendation is that we move it so that an invoice can be
> 1. IN_PROGRESS: equivalent to created and in progress, then
> 2. SENT or RECEIVED or both: not necessarily finalized but on its way, then
> 3. READY: finalized, then
> 4. PAID: paid
> 5. COMPLETED: then completed
> Along the way the invoice can be cancelled until (3) when it is marked READY, at which time it is considered no longer changeable. Also, we need to have direct IN_PROGRESS -> READY so as to avoid unnecessary status changes in quick ship entire order type processes.
> I think this would address Hans's issues. For semantics maybe we can change the description of INVOICE_READY to "Approved and Ready" rather than "Ready to Send"
> Please give us your thoughts.
> Si
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.undersunconsulting.com/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Locked
