[
https://issues.apache.org/jira/browse/OFBIZ-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030905#comment-14030905
]
mz4wheeler commented on OFBIZ-5649:
-----------------------------------
I'm wondering if you "Quick Receive" the PO, that it assumes payment is made.
Is it common practice to use this, or to go though the manual process.
> 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)
--
This message was sent by Atlassian JIRA
(v6.2#6252)