[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl-dev] How to handle the case of returned checks
Hello,
> Thank you for your detailed answer. The customer will probably send
> another payment for the returned check, along with a new UBL Remittance
> Advice? So we'll end up receiving 2 remittance advices for the same
> invoices, isn't it a problem?
The 2nd remittance advice has a different IssueDate so it just used to
trigger another reconciliation cycle at the Supplier side, which is what
you want (as the previous payment was failed).
You could use the "CopyIndicator" to state this is a copy (but this is
dependent af the implementation profile)
Also you could add a Note describing the reasons for resending the
remittance (for human readers).
Depending of where the issue has been raised on the banking channel you
could have different notifications.
The could be issues before or after settlement.
The banking notification to their customer (if agreed) is dependent of
many factors and use cases.
According ISO20022 a negative payment processing can be notified using a
negative CustomerPaymentStatusReport message, a
BankToCustomerDebitCreditNotification
message ('notification') or through a BankToCustomerAccountReport and/or
BankToCustomerStatement message.
My preferred choice is the Debtor/Payer should wait a positive
"CustomerPaymentStatusReport" (see ISO20022 payment initiation) before
issuing a remittance advice.
The above report notifies the payer if the payment has been successful or
not.
Of course all of these decisions and flows are not only dependent of
ISO20022 and UBL but it take to have a clear implementation profile.
Automatic reconciliation is possible and facilitated by the external
remittance practice (UBL Remittance Advice), but it takes there are
banking notifications in place (hopefully using electronic messages like
ISO20022 provides)
Hope this helps,
Roberto
>
> Eric.
>
> On 12/21/2010 9:20 AM, Roberto Cisternino wrote:
>> Hi,
>> you are in the borders of UBL.
>> When you send an UBL Remittance advice it means you have made a payment
>> initiation on the banking channel (e.g. credit transfer) so you can't do
>> nothing with UBL as it is an issue solved by the banking channel.
>>
>> UBL remittance is just an advice that is precious to have an easy and
>> complete reconciliation between payments and invoices.
>>
>> The match is quite complex as the Supplier/Invoicer (Creditor) should
>> match the following documents/messages:
>>
>> - The "Credit Transfer notification" received by the banking channel
>> containing one or more End-to-End references, the same specified into
>> the
>> UBL remittance Advice. (this is performed after the payment initiation
>> if
>> all the payment process is ok in the clearing system)
>>
>> - The "UBL Remittance Advice" received from the Buyer/Debtor (with same
>> End-to-end identifiers, see upper)
>>
>> - The Invoice/s issued against the Buyer in reference.
>> NOTE: The end-to-end identifier/s are generated by the Invoicer and
>> provided on either the Invoice header or even in the line items. Later
>> the same identifiers are asked to be used by the debtor on the
>> remittance advice and in the payment initiation.
>> The banking (clearing system) should safely transport such end-to-end
>> identifiers til the end and thus inside the Credit Transfer
>> notification.
>>
>> --
>> So, the UBL Remittance Advice playes an impotant role as it is the
>> connection between all these messages and facilitates the
>> reconciliation.
>>
>> If the Invoicer/creditor do not receives a Credit Transfer Notification
>> or
>> even receives another more specific negative response, the UBL
>> Remittance
>> will be still useful to provide somo more information on the use case,
>> but
>> payment issues are up to the banking system.
>>
>> Hope this helps,
>>
>> Best regards
>>
>> Roberto Cisternino
>>
>> JAVEST CEO
>> UBL ITLSC co-chair
>>
>>> Some payment receipts by checks from customers may not be processed by
>>> the bank for various reasons such as insufficient funds. How can we
>>> handle these cases?
>>>
>>> Would it make sense to send a remittance advice with a negative amount
>>> to the customer's accounting department?
>>>
>>> Sincerely,
>>> Eric Desgranges
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
>>> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>
>
--
* JAVEST CEO
* Document Engineering Services Ltd. - Alliance Member
* UBL Italian Localization SubCommittee (ITLSC), co-Chair
* UBL Online Community editorial board member (ubl.xml.org)
* Italian UBL Advisor
Roberto Cisternino
mobile: +39 328 2148123 begin_of_the_skype_highlighting +39
328 2148123 end_of_the_skype_highlighting
begin_of_the_skype_highlighting +39 328
2148123 end_of_the_skype_highlighting
skype: roberto.cisternino.ubl-itlsc
[UBL Technical Committee]
http://www.oasis-open.org/committees/ubl
[UBL Online Community]
http://ubl.xml.org
[UBL International Conferences]
http://www.ublconference.org
[UBL Italian Localization Subcommittee]
http://www.oasis-open.org/committees/ubl-itlsc
[Iniziativa divulgativa UBL Italia]
http://www.ubl-italia.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]