Projects:Business Partner Settlements/Functional Specification
Contents |
Business Partner Settlements - Functional Specifications
Overview
This project intends to deliver a new module to manage credit or pending payments settlements of Business Partners that are both customers and providers.
Purpose
When a Business Partner is a Customer and a Provider it is possible to have credit as both types. But it is not possible to consume a customer credit in a Payment Out document. In the same way it is not possible to mix purchase or sales invoices on a single payment document. In some scenarios when a business partner has sales and purchase invoices it is desirable to cancel both debts not needing a financial transaction.
Scope
This project will deliver a new module with a window where it will be possible to settle credit or pending payments of a business partner. The result of the settlement are Payment Ins and Payment Outs that consumes the credit or cancels the pending payments against a user defined GL Item. These generated payments have 0 total amount so they do not generate any transaction in the Financial Accounts.
Design Considerations
Dependencies
The module depends on advanced functionality of Process Definitions delivered on PR14Q3.
Functional Requirements
Business process definition
- Ability to cancel payment in and payment out credit of the same business partner.
- When the same Business Partner has available credit in Payment Ins and Payment Outs be able to select the payments with available credit so it can be matched and canceled.
- Ability to cancel sales and purchase invoices of the same business partner that are pending to pay.
- Be able to select sales and purchase invoices pending to pay that sum up the same amount in both flows so they can be canceled.
User stories
Functional requirements based on business processes
Id | Requirement | Importance |
1 | * Window Name: Business Partner Settlement
| Must have |
2 | Header Tab:
| Must have |
3 | Credit In, Credit Out, Sales Invoice and Purchase Invoice Read Only Tabs:
Displayed based on the settlement type. | Must have |
4 | Child Tabs Editable: Ability to manually add payments selecting the credit payment or the pending invoice. | Nice to have |
Id | Requirement | Importance |
1 | Process Definition with parameters:
| Must have |
2 | Payment Ins or Payment Outs grids:
When a record is selected the credit to settle is updated with the available credit and the corresponding parameter field with the total amount. | Must have |
3 | The Process checks that both amounts are the same. It creates a Payment In and a Payment Out payment canceling the selected credit payments against the settlement's GL Item. | Must have |
Id | Requirement | Importance |
1 | Process Definition with parameters:
| Must have |
2 | Sales Invoice or Sales Invoice grids:
When a record is selected the amount to settle is updated with the pending amount and the corresponding parameter field with the total amount. | Must have |
3 | The Process checks that both amounts are the same. It creates a Payment In and a Payment Out payment canceling the selected pending payments against the settlement's GL Item. | Must have |
Id | Requirement | Importance |
1 | Process Definition with parameter:
| Must have |
2 | Action Process
It should be possible to process the settlement from the Pick and Executes. Creates the needed payments using the GL Item defined in the header. | Must have |
3 | Action Cancel
It cancels the settlement by canceling the generated payments. The status is changed to Voided and it is not possible to modify it anymore. | Must have |
4 | Action Reopen
It cancels the generated payments and removes their relation to the settlement. The status is changed to Draft and it is possible to modify the selected credit or invoices to process again the settlement. |
User Interface Mockups
Add Invoices mockup