From 00b79a4beceadbe2c6df04d7ba32b570fccadc59 Mon Sep 17 00:00:00 2001 From: Christopher Neugebauer Date: Mon, 25 Apr 2016 08:27:20 +1000 Subject: [PATCH] Documentation now reflects that issue #37 is solved. --- docs/payments.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/payments.rst b/docs/payments.rst index 3a2d6262..058b64bc 100644 --- a/docs/payments.rst +++ b/docs/payments.rst @@ -81,7 +81,7 @@ Calling ``update_status`` collects the ``PaymentBase`` objects that are attached When your invoice becomes ``PAID`` for the first time, if there's a cart of inventory items attached to it, that cart becomes permanently reserved -- that is, all of the items within it are no longer available for other users to purchase. If an invoice becomes ``REFUNDED``, the items in the cart are released, which means that they are available for anyone to purchase again. -(One GitHub Issue #37 is completed) If you overpay an invoice, or pay into an invoice that should not have funds attached, a credit note for the residual payments will also be issued. +If you overpay an invoice, or pay into an invoice that should not have funds attached, a credit note for the residual payments will also be issued. In general, although this means you *can* use negative payments to take an invoice into a *REFUNDED* state, it's still much more sensible to use the credit notes facility, as this makes sure that any leftover funds remain tracked in the system.