Projects:Bpdc/Specifications
Contents
|
Business Partner Debt Consolidation Process - Functional Specifications
Overview and Justification
Purpose
This document contains the functional specifications for the Business Partner Debt Consolidation functionality.
This feature consists in a process that allows users to automatically consolidate the outstanding payments for one or more business partners and create a debt payment for the difference of payment dues and payment received and closing all intermediary documents.
Background Information - Manually consolidating business partner debt payments in Openbravo ERP
The objective of this module can currently be achieved manually following these steps.
Assume that business partner BPA has two outstanding collection payments, one for -100 euros and one for 38.28 euros. To consolidate them:
- Navigate to the Settlement window
- Create a new settlement header accepting the default values
- Press the Create Lines From button; using BPA as a search criteria select the 2 payments above and press OK. This creates two records in the Canceled Payments tab for a total of -61.72 euros.
- Navigate to the Created Payment tabs and create a record for -61.72 euros that consolidates the two above.
- Process the settlement.
Scope
The purpose of this module is to automate the manual steps above for a number of business partners. This can be achieved by creating a new process that performs the desired actions.
Users should be able to launch this process passing the following parameters that are used to select the pending payments:
- Organization
- List of business partners to consolidate
- Bank account
- Form of payment
- Payment status
- Due date from, date to: date range for the debt payments to consider for consolidation.
- Amount from, to: range of amouts to consider for consolidation.
- Type: Receivable or Payable
It also accepts the following parameters that are intended to specify the attributes of the target payment:
- Target bank account
- Target form of payment
- Target due date
This project needs to address both the receivables and payables flows.
New definitions and acronyms
None.
Design and technical considerations
Technical considerations
Because it is necessary to invoke this process for a list of business partners, a manual window is needed to launch the process.
Users & business process description
User goals
The feature covered by this specifications automates functionality that is otherwise already available in the product and can be executed manually but in a time consuming manner. The goal of the user is to execute his tasks in a faster, more efficient and more reliable way way and this feature enables that.
User roles and personas
This project involves primarily staff from the finance department.
Specifically the impacted roles are:
- AR Staff: back office staff members that belong to the Finance function of the enterprise and that specialize in managing the receivables documents.
- AP Staff: back office staff members that belong to the Finance function of the enterprise and that specialize in managing the payables documents.
Business process definition
The business process automated by this feature is made by a single activity:
- Consolidate Business Partner Debt Payments
User Stories
First story: consolidation of receivables
On June 1st, Tim – a member of the AR Staff of Micro-toys Holding – receives an advanced payment from a customer for 100 euros. One June 2nd, Tim creates creates a sales invoice for a customer for 10 euros. One June 15th, Tim creates creates a sales invoice for a customer for 60 euros.
On June 30th, Tim runs the Business Partner Debt Consolidation process for this business partner. This results in merging the 3 payment above into a single paymen for -30 euros.
Second story: consolidation of receivables across multiple business partners
On June 1st, Tim – a member of the AR Staff of Micro-toys Holding – receives an advanced payment from a customer A for 100 euros. One June 2nd, Tim creates creates a sales invoice for customer A for 10 euros. One June 15th, Tim creates creates a sales invoice for customer A for 60 euros.
On June 5th, Tim creates a sales invoice for customer B for 75 euros. On June 25th, Time creates a sales invoice for custom B for 150 euros.
On June 30th, Tim runs the Business Partner Debt Consolidation process for both business partners. This results in merging the 3 payment above for customer A into a single payment for -30 euros for that business partner. It also results into merging the 2 payments for customer B into a single payment for 225 euros.
Fourth story: consolidation of payables
On June 1st, Alexandra – a member of the AP Staff of Micro-toys Holding – receives a purchasing invoice from supplier C for 10 euros. One June 15th, Alexandra receives a purchasing invoice from supplier C for 65 euros.
On June 30th, Alexandra runs the Business Partner Debt Consolidation process for this business partner. This results in merging the 2 payment above into a single payment for 75 euros.
Functional Requirements
Business Partner Debt Consolidation Process
| Num | Requirement | Importance | Status |
| 2.1 | A new process called Business Partner Debt Consolidation is required to process pending receivable and payables payments and consolidate them into a single one for the outstanding amount.
This process accepts the following parameters:
The process consolidates payments and, at the end displays the results, as a list of consolidated payments. | Must Have | In scope |
| 2.2 | The process is run from a manual window accessible from Financial Management / Receivables & Payables / Transactions.
See user interface for mockups. | Must Have | In scope |
| 2.3 | Once the process is complete, it is possible to review the result and drill into the newly created payments.
See user interface for mockups. | Must Have | In scope |
User Interface
The following image shows the window where users can launch the process.
(Note: this window is very similar to the Payment Report launch page and that page can be used as a model)
IMPORTANT NOTE: the above image is missing a section to specify the target parameters:
- Target form of payment (defaulted to the first value in the list)
- Target bank account (defaulted to null)
- Target due date (defaulted to current date)
The following image shows the same window after the process completion.
Technical Requirements
The server side implementation of this module uses DAL.
It also leverages the core enhancement SettlementPropertySetter provided by the Mass Advance Payment module.
License
The module required by this project is to be released under the Openbravo Public License.
Discussion Items
Open discussion items
None