9 Replies Latest reply: Jan 14, 2011 4:30 PM by Gaurav Aggarwal RSS

Residual Payment vs. Partial Payment: Design considerations

Victor Sullivan
Currently Being Moderated

We need to decide between implementing residual payment vs. partial payment. We will be implementing payment processing.

I would like to understand why one would choose one method over another?

What is the benefit of clearing original invoice and creating a new line item for the balance (as in case of residual payments)? There is a setting that allows user to capture the original invoice date at the time of payment processing while using residual payment, which I believe makes the residual payments same as partial payments, so again, why would one choose one method over another? 

I would like to understand the benefits & limitations of each method.

How does the decision to implement a method get impacted if reason codes are to be implemented, which method would offer a better solution considering reason codes requirement?

 

Appreciate your inputs.

  • Re: Residual Payment vs. Partial Payment: Design considerations
    Gaurav Aggarwal
    Currently Being Moderated

    Residual Payment method reduces the open lines, but the disadvantage is that when you send the customer account statemet, customer might not be able to link the residual payment line with its original invoice and partial payment clearly.

     

    Using Partial Payment method, customer can see clearly what all invocie has been issued to customer and what payments he has made. But it keeps the multiple open items, untill the invoice is fully paid/ cleared.

     

    Regards,

    Gaurav

  • Re: Residual Payment vs. Partial Payment: Design considerations
    Ranjith Reddy
    Currently Being Moderated

    HI,

     

    Residual payment it clears original invoice with incoming amount and create new line item for remaining outstanding amount.

    Partial payment it leaves the original invoice amount and creates new line item for incoming amount.

     

     

    Regards,

    Ranjith

  • Re: Residual Payment vs. Partial Payment: Design considerations
    Rob Laan
    Currently Being Moderated

    Hi,

     

    Consider using residual items when the customer has apparently had the intention to pay the full amount of the invoice, but for whatever reason withheld an amount from the payment (e.g. cash discount after payment term, dispute about discounts). The residual item clearly identifies the payment deduction as a single line item. You can use the reason code to mark the item for furhter action, the dept dealing with disputes can easily identify the dispute. If you decide to write off the dispute, you always know you only need to clear this single item.

    You will have fewer open items, because with a residual item, you clear the original invoice. As remarked in an earlier post, that also means that on the statement of account, you will only have that single item, not the original invoice amount and the payment amount. That may be a downside of using residual items, depending on your situation (although the residual items always has  references to the original invoice, so it will be clear to the custome to which invoice the residual item refers to).

     

    if the the customer clearly did not have the intention of paying the full amount, or clearly paid the wrong amount (I mean, a residual item of 60% of the invoice value does not make sense to me), then consider using the partial payment.

     

    I am not aware of any differences with respect to overdue reporting, DSO etc.

     

    Regards,

     

    Rob

  • Re: Residual Payment vs. Partial Payment: Design considerations
    Rob Laan
    Currently Being Moderated

    Hi,

     

    In manual processing of incoming payments, it is of course the user who can make the decision to either make residual item, or a partial payment.

     

    In automatic processing of incoming payments:

     

    For electronic bank statements, payments that the system cannot match with open items will end up in post-processing; there the user can again choose either residual item or partial payment.

     

    For electronic payment advices, I know that there is configuration to match customer information for payment deductions in the payment advice, with you own reason codes, and that based on the information the system can create the residual items automatically. Of course, this is only relevant if your customers actually send you electronic payment advices with such information included.

     

    Regarding reason codes, you will always use reason codes with residual items; to indicate the reason for deduction for follow up in your A/R dept, and possibly to make use of the automatic write off (you can configure reason codes to automatically write off the payment deduction to some G/L account of your choosing; you would use that e.g. if the payment deduction is too small to bother).

     

    For partial payment, you could use reason codes I guess, if you want to in that way mark the item for some reporting or follow up purpose.

     

    Regards,

     

    Rob

Actions