Re: [ubl-dev] Updating payment means information for an invoice

David, Your idea is related to a suggestion we raised a while ago:

https://lists.oasis-open.org/archives/ubl-comment/201605/msg00011.html

Following review, the cttee made this suggestion:

https://issues.oasis-open.org/browse/UBL-24?filter=12972

We have adopted such an approach in our own implementation, which is 100% free/libre/open source.

I'd have to check with a colleague about our implementation details. Certainly invoices do have to get updated -- sometimes to correct errors, but also for other reasons. Structured versioning is critical so that an audit trail is not lost.

Joseph Potvin
Executive Director, Xalgorithms Foundation
Mobile: 819-593-5983
jpotvin@xalgorithms.org
https://www.xalgorithms.org

On Mon, Aug 20, 2018 at 6:32 AM, David Goodenough <david.goodenough@broadwellmanor.co.uk> wrote:

An Invoice is an immutable object once it is issued, changes such as updating individual line items or canceling out an an entire invoice are done using a credit note.

Â

But how are changes such as the destination bank account for the payment for the invoice distributed.

Â

If a supplier changes bank account then obviously all new invoices will be set up with the new bank details, but what about existing invoices? While it is unlikely that such a change would occur during the normal 30 day or so life of an outstanding payment, some payments are made over an extended period which can last for years. We (a farm) were notified that the company providing the 5 year 0% HP deal on a tractor was, 2 years into the deal, moving its bank account. We were notified by letter, which we confirmed by ringing them to make sure this was not fraudulent.

Â

We also get cases where a supplier of seed issues a set of invoices which are issued with a 3 month payment period and are bundled together before the due date and factored so that we end up paying a third party, and it was not known at the time of the invoice that this would happen (we get to choose if we want to take advantage although as it typically is a 0% deal over more like 6 months it is a bit of a no brainer). So in this case we change not only the financial account to which it is to be paid, but also due date, and the reference we give with the payment is a single reference for the whole bundle rather than individual invoice references.

Â

The Reminder document could I think not be used for this as it is supposed to be for overdue payments.

Â

However the Statement could be used for this. The Statement would list the invoices being adjusted and supply new PayeeParty and PaymentMeans/PayeeFinancialAccount. The new due date can be encoded in the PaymentTerms/PaymentDueDate object. I don't think that there is any rule that a Statement must list all outstanding Invoices/Credits/Debits, so it can be used to adjust only those invoices that need adjusting.

Â

Is this a suitable approach, or is there another solution that I have missed?

Â

David

Â

Â

Â

ubl-dev message