View source | View content page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Show collection (0 pages)
Collections help

Search

Projects:Aprmpaymentpriorities/User Documentation paymentpriorities

Contents

Introduction

The main goal of this module is to allow the distribution of either "Payments Received In" or "Paid Out" by payment priority first, and then by due date.

Openbravo currently proposes the distribution of payments plan lines received in or paid out by due date.

This module allows that the distribution algorithm of payments to be driven by the payment priority first and then by due date, by taking into account that the Payment priority will always have a higher priority than the due date.

Every payment plan has a due date, but not every payment plan will necessarily have a payment priority.

If two lines have the same priority (first sort), then they will be prioritized by due date (second sort).

Payment priorities are not mandatory and can be setup by the end-user as required by having into account that the lowest priority value means the highest priority.

Installation

Follow below steps to get Booking Control module installed in your system:

Configuration

It is now possible to define "Payment Priorities" at Client level (or Main Organization), as described below:

An example is shown below:

Highest Priority (Red color) :

Priority 1.png

Standard Priority (Blue color) :

Priority 2.png

Lowest Priority (Green color) :

Priority 3.png

Payment priorities at Organization level

It is important to remark that a specific Organization, let's say an "Organization A" which belongs to a "Main" organization, could have a different set of Payment Priorities if needed than "Main" Organization ones, by having into account that:

User Interface changes

Sales/Purchase Orders and Invoices

A new field named "Payment Priority" has been created at the application paths:

Sales Order window is shown below:

Sales order.png

Payment priority new field is not a mandatory field and besides:

Sales/Purchase Orders and Invoices Payment Plans

A new field/column named "Payment Priority" and a new button named "Update Payment Plan" has been created at the application path:

Therefore:

Sales Invoice - Payment Plan tab is shown below:

Sales invoice paymentplan.png

Update Payment Plan new window is shown below:

Update paymentplan.png

Payment Plan Lines distribution User Interface changes

Payment Plan lines distribution UI has been also modified, as shown in the screen below:

Add payment.png

As shown above, "Add Payment" grid is now showing two different colors one per each priority defined.
End-user should know the colors he has setup for each priority. In this case, the blue color placed at the top, has a higher priority that the green one, placed below.

As a summary, the payment priority is indicated by the sort order of the data set to which that payment is being applied and besides by the colour setup and linked to a specific payment priority.

User scenarios

Scenarios detailed below applied to Sales Transactions, same applies to Purchase transactions.

Sales Order/Invoice creation

End-user needs to enter Sales Orders and Sales Invoices as part of "normal" business activities for a given Business Partner (Customer)

Sales Order 50035 has a "Standard Priority" and a due date = March 20th, 2011

Sales Invoice 100033 has a "High Priority" and a due date = April 20th, 2011

Sales Invoice 100034 has a "Standard Priority" and a due date= March 22nd, 2011

Sales Invoice 100035 has a "Low Priority" and a due date = February 20th, 2011

Openbravo "standard" functionality would propose a payment distribution sort by due date, as described below:

  1. Sales Invoice 100035, due date February 20th, 2011
  2. Sales Order 50035, due date March 20th, 2011
  3. Sales Invoice 100034, due date March 22nd, 2011
  4. Sales Invoice 100033, due date April 20th, 2011

But, Payments Priorities functionality would propose a payment distribution sort by payment priority first and then by due date, as described below:

  1. Sales Invoice 100033 - "High Priority"
  2. Sales Order 50035 -"Standard Priority" - due date = March 20th, 2011
  3. Sales Invoice 100034 - "Standard Priority"- due date= March 22nd, 2011
  4. Sales Invoice 100035 - "Low Priority"

See below user scenario "Add Payment from Payment In"

Add Payment from Payment In

The end-user needs to enter a Payment received In from the Business Partner (Customer), for doing that he/she needs to navigate to the application path:
"Financial Management // Receivables & Payables // Transactions // Payment In - Header"
and follow the steps described below:

Openbravo will show sales transactions to be paid sorted first by "Payment Priority" (first sort) and then by due date (second short), as shown below:

Add paymentIn.png

A transaction with no color means it has no a payment priority linked to its corresponding payment plan.

Add Payment from Invoice

End-user needs to enter a Payment received In from the Business Partner (Customer) for the Sales Invoice 100035. This invoice has the closest due date but the lowest payment priority.

For getting that done, end-user must follow below steps:

Once there Openbravo will show us "Add Payment" distribution grid by showning the invoice which is being paid at the top, and then the rest by having into account payment priority (first sort) and due date (second short), as shown below:

Addpayment invoice.png

It is always possible to unmarked the selected invoice (in our example the invoice 100035), and select the one with highest priority, which for sure will come next (in our example 100033).

Add Payment from Financial Account

The end-user needs to enter a Payment received In from the Business Partner (Customer), from the corresponding "Financial Account"

For doing that he/she needs to navigate to the application path:
"Financial Management // Receivables & Payables // Transactions // Financial Account - Account"
and follow the steps described below:

Openbravo will show sales transactions to be paid sorted first by "Payment Priority" (first sort) and then by due date (second short), as shown below:

Addpayment financial.png

A transaction with no color means it has no a payment priority linked to its corresponding payment plan.

Retrieved from "http://wiki.openbravo.com/wiki/Projects:Aprmpaymentpriorities/User_Documentation_paymentpriorities"

This page has been accessed 813 times. This page was last modified on 8 June 2012, at 05:31. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.