[ 
https://issues.apache.org/jira/browse/OFBIZ-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088963#comment-14088963
 ] 

Sharan Foga commented on OFBIZ-5649:
------------------------------------

I can confirm that adding a net days payment (e.g 5 days) during purchase order 
creation also resolves the issue.

> Purchase Invoice Outstanding Amount is zero when payment to Supplier has not 
> been made
> --------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-5649
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5649
>             Project: OFBiz
>          Issue Type: Bug
>          Components: accounting
>            Reporter: Sharan Foga
>
> I have come across an issue with payments. The outstanding amount is set to 
> zero when the Purchase Invoice hasnt yet been paid so is never displayed as 
> an invoice that is due for payment.
> To replicate it the example I used was to:
> 1. Create a Purchase Order created for 2 GZ-1000 at $7.50 each to DemoSupplier
> 2. Approve the PO
> 3. Quick Receive the PO
> When you receive Purchase Order into inventory a “payment” is created under 
> the “Payment Information” section of the Purchase Order.
> The Payment is created for an amount of $15 with a status of “Not Paid”
> At receipt , the Pro Forma invoice is also created and is displayed below the 
> payment on the view order screen.
> If you click the link to the Pro Forma Invoice and look at the “Terms” 
> section which shows the “Outstanding Amount” you will see that it is now 
> showing zero. (I don’t think this is correct because you haven’t paid the 
> supplier yet! I think the Outstanding Amount on the Pro Forma invoice should 
> still be $15.)
> If you then go to Accounting Manager / Payments to locate Purchase Invoices 
> by Due Date then this invoice isnt displayed even though the Due Date is the 
> current date. I think this is because the Outstanding Amount is zero, OFBiz 
> thinks that the invoice has already been paid (when it hasn't).
> I’ve done some more testing and found the following:
> The only options that create the pro forma invoice are:
> "Quick Receive PO" and select the shipment to receive using the shipment 
> number 
> “Receive” and select the shipment to receive using the shipment number
> In both of the cases above if you don’t select the shipment number and use 
> the “No Specific Shipment” instead then only the payment is created and not 
> the invoice. So the invoice creation appears to be linked to selecting a 
> specific shipment number.
> Also if you use “Receive Inventory” from Facility Manager, this only gives 
> you the option for “No Specific Shipment” so once again the payment is 
> created but not the invoice.
> Steve added a comment with some additional details as follows.
> The issue seems to be related to the shipment creation as the invoice is 
> correctly created if the product is "service" :
> 1. If you enter purchase order for a product type "raw material" -> approve 
> the order -> the payment is created. Receive against inventory (quick or 
> complete) -> shipment created -> receive -> invoice created with outstanding 
> payment 0$ (actual issue)
> 2. If you enter purchase order for a product type "service" (in our case we 
> had to create "painting" service for our products) -> approve the order -> 
> payment AND invoice are created at the same time -> invoice is OK with 
> outstanding value of the order (ex. 15$).
> But if you create an agreement with the vendor e.g including payment in 30 
> days, the problem is solved and the outstanding payment value is the correct 
> value irrespective of the product type (Raw Material, Finished Good, Service 
> etc)
> I've re-done the tests and can confirm what Steve has highlighted is correct. 
> This seems to narrow down the issue to be to the shipment creation if the 
> product is not a service product and no agreement is linked to the purchase 
> order at creation. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to