Projects/Add Payment Window/Functional Specifications

Contents 1 Overview 1.1 Purpose 1.2 Scope 2 Design Considerations 2.1 Dependencies 3 Functional Requirements - Sales Flow 3.1 User roles & profiles 3.2 Business process definition 3.3 User Stories 3.4 Functional requirements based on business processes 3.5 User Interface Mokups 4 Functional Requirements - Purchase Flow 4.1 User roles & profiles 4.2 Business process definition 4.3 User Stories 4.4 Functional requirements based on business processes 4.5 User Interface Mokups

Overview

This document contains the functional specifications for the refactoring of the “Add Payment” window, which is intended to deliver new capabilities while adding payments against invoices and orders.

The intention of this project is to improve the “Add Payment” window that currently exists in openbravo. To achieve this "Add Payment" window needs to use the recently implemented “Parameter Windows” technology. This Implementation will allow to easily extend the functionality of the window (modularity) and provide performance improvements.

Currently the “Add Payment” popup is a manual window created in Openbravo’s legacy technology (Implement a Servlet, html for the user interface, xml...). This type of window doesn’t support modularity, so every time an extension or modification is needed the solution is to modify Openbravo Core (not recommended practice) or to duplicate it.

Furthermore the new "add payment" window provides a generic view of all the possibilities that Openbravo payments functionality offers. New "Add Payment" window need to show orders/invoices information, generated credit and g/l items information, all in the same window. Currently “Add Payment” popup does not show all of this information at the same time.

Purpose

The new “Add Payment” popup can be opened in five different windows: Sales invoice, Purchase Invoice, Payment In, Payment Out and Financial Account windows.

The goal is to create a unique popup that implements all the functionality required and at the same time and depending on the window from where it is launched displays the parameters of fields needed.

Scope

The 1st phase of this project needs to cover the improved functionality for Sales invoice, Purchase Invoice, Payment In and Payment Out windows, additionally new "Add payment" popup needs to added to sales order and purchase order windows. 1st phase phase will be implemented in 3.0PR14Q3

The 2nd phase of this project will cover that the new popup can be opened in the Financial Account window.

Having said that, it is important to remark that the new popup has to support at least every functionality supported by the old popup.

Design Considerations

Dependencies

This project depends on another two projects that are currently in development:

• Parameter Windows phase 3 project: so it is possible to display more than one grid on a parameter window and add display logics to grids among other needed features for this project. For more details please review
  http://wiki.openbravo.com/wiki/How_to_create_a_Standard_Process_Definition Parameter windows] article.

• ahd Hql Tables: so it is possible to implement grids that use as datasource hql queries. For more details review HQL Datasources How To.

Functional Requirements - Sales Flow

Withing the sales flow "Add Payment" window can be launched and used in the following windows.

• Sales Order window: Payments can be received against a sales order by using the Add Payment button.
• Sales Invoice window: Payments can be received against a sales invoice by using the Add Payment button.
• Payment in window: Customer's payments and prepayments received can be created and managed in the payment in window. The Add Details button opens the Add Payment window where the documents being paid can be selected.

User roles & profiles

Sales staff (Mary): Mary is an employee part of the sales staff. She will be the one entering sales orders transactions as required.

Sales staff (Mike): Mike is an employee part of the sales staff. He will be the one entering sales invoices and payments against invoices and/or orders.

Business process definition

F&B International Group is an enterprise from USA making business with several Business Partners: Vendors, Suppliers, Customers, etc.

Every Business Partner can have by default Payment Methods such as Check and Wire transfer; and by default Payment Terms such as Immediate, 30 days or 60 days.

Mary a member of AR (sales) staff registers the sales order that F&B requires and Mike a member of the AR (sales) staff issues a sales invoice as well as the corresponding payment-in.

'Healthy Food Supermarkets, Co is one of the customers of F&B International Group. This customer has Wire transfer as payment method and 30 days payment terms. This customer always pays 30 days after receiving an invoice.

Moon Light Restaurants, Co is one of the customers of F&B International Group. This customer has Wire transfer as payment method and 15 days payment terms. This customer always pays 15 days after receiving the order. Moon Light Restaurants, Co. have restaurants in USA and Europe.

Sleep Well Hotels, Co. is one of the customers of F&B International Group. This customer has Check as payment method, and 30 days payment terms. Besides Invoice Terms is set as "Immediate". Check payment method does not deposit automatically the payment in the financial account.

F&B have business with European customers and US customers. F&B pays only european sales invoices via wire transfer and needs to have two sales price lists one in USD currency and another one in EUR currency.

User Stories

Story 1: Adding a Payment to a sales invoice with an associated sales order

• On April 1st, Mary, who is in charge of issuing sales orders, creates a new sales order with this data:
  • Organization: F&B US, Inc., Transaction Document: Standard Order, Business Partner: Healthy Food Supermarkets, Co., Invoice Terms: Immediate, Product: Pear Juice, Quantity: 100.
• On May 1st, Mike, who is in charge of issuing sales invoices, executes the process create invoices from orders, this process automatically creates the invoice from the previous order.
• On May 1st, The previous invoice is paid and Mike, who is in charge of issuing the payments, adds the payment from the invoice window. All fields of the Add Payment window are automatically populated from the Invoice.

The invoice is set as paid and it is also deposited in the financial account.

Story 2: Adding a Payment to a sales order

• On April 1st, Mary creates a new sales order with this data:
  • Organization: F&B US, Inc., Transaction Document: Standard Order, Business Partner: Moon Light Restaurants, Co., Product: Energy Drink, Quantity: 50
• On April 15st, a pre-payment of the previous sales order is received and Mike adds the payment from the sales order window. All fields of the Add Payment window are automatically populated from the Order.

Story 3: Adding a G/L Item transaction type payment

• On May 1st , F&B has a new partnership, the new partner must make a capital contribution to the company.
• On May 1st , Mike adds the payment from this capital contribution. Mike creates a new payment in with this data:
  • Organization: F&B US, Inc., Document Type: AR Receipt, Payment Method: Wire Transfer, Deposit To: Bank - Account 1 - USD.
  • Add details and in the gl/item section, adds a new gl/item with this data: Gl Item: Company capital, Received in; 200000

Story 4: Adding a Payment to a sales invoice with an associated sales order as a generated credit

• On June 1st, Mary creates a new sales order with this data:
  • Organization: F&B US, Inc., Transaction Document: Standard Order, Business Partner: Healthy Food Supermarkets, Co., Invoice Terms: Immediate, Product: Orange Juice bio, Quantity: 100
• On June 1st, Mike executes the process create invoices from orders, this process automatically creates the invoice from the previous order.
• On June 1th , Healthy Food Supermarkets, Co. pay 1000€ for some invoices of June, Mike adds the payment from the invoice. All fields of the Add Payment window are automatically populated from the Invoice, Mike changex actual payment to 1000 and leaves the remaining amount as a credit to be used later. The invoice is set as paid and it is also deposited in the financial account.

Story 5: Paying a Sales invoice with a generated credit

• On June 15st, Mary creates a new sales order with this data:
  • Organization: F&B US, Inc., Transaction Document: Standard Order, Business Partner: Healthy Food Supermarkets, Co., Invoice Terms: Immediate, Product: Lemonade, Quantity: 100
• On June 15st, Mike executes the process create invoices from orders, this process automatically creates the invoice from the previous order.
• On June 15st, Mike adds the payment from the invoice. All fields of the Add Payment window are automatically populated from the Invoice. In a credit line of credit grid Mike sets the credit amount against this invoice. The invoice is set as paid and it is also deposited in the financial account.

Story 6: Paying a Sales invoice with partial payments

• On May 1st, Mary creates a new sales order with this data:
  • Organization: F&B US, Inc., Transaction Document: Standard Order, Business Partner: Sleep Well Hotels, Co, Product: Lager Beer, Quantity: 100
• On May 1st, Mike executes the process create invoices from orders, this process automatically creates the invoice from the previous order.
• On May 1sh , Sleep Well Hotels, Co pays 100€ against this invoice. Mike adds the payment from the invoice. All fields of the Add Payment window are automatically populated from the Invoice, Mike changes the Actual Payment amount to 100. The invoice is partially paid. The invoice is not completely paid as this moment.
• On May 15sh, Sleep Well Hotels, Co paid the total outstanding amount of the invoice. Mike adds the payment from the invoice. All fields of the Add Payment window are automatically populated from the Invoice. The invoice is set as paid.

Story 7: Refunding a payment

• On June 1st, Mary creates a new sales order with this data:
  • Organization: F&B US, Inc., Transaction Document: Standard Order, Business Partner: Moon Light Restaurants, Co Product: Cherry Cola, Quantity: 100
• On June 15st, Mike executes the process create invoices from orders, this process automatically creates the invoice from the previous order.
• On June 15sh, Mike to paid this invoice will consume genereate credit, and the difference will be refund to the payment. All fields of the Add Payment window are automatically populated from the Invoice. Mike changes the amount of selected line to 100 and select the option “Refund the amount to the customer”. As a result 2 payments have been created the payment and the refund payment.

Story 8: Payment Write off

• On June 1st, Mary creates a new sales order with this data:
  • Organization: F&B US, Inc., Transaction Document: Standard Order, Business Partner: Sleep Well Hotels, Co Product: White wine, Quantity: 80
• On June 15st, Mike executes the process create invoices from orders, this process automatically creates the invoice from the previous order.
• On June 15sh, Sleep Well Hotels, Co paid 426 against this invoice, but the total amount is 426.40 as the difference is minor. Mike decides to write of the difference. Mike adds the payment from the invoice. All fields of the Add Payment window are automatically populated from the Invoice. Mike changes the Actual Payment amount to 426 and writes off the difference.

Story 9: Reactivating a payment

• On May 15sh, Mike has realized that he made a mistake in "story 6 payment. Sleep Well Hotels, Co. paid 163.9 instead of 164. Mike needs to reactivate the payment and enter the correct amount paid.
• Mike navigates to the payment in window and reactivates the payment, then Mike click on add details and modifies the actual payment in amount to 163.9 and writes off the difference.

Story 10: Multicurrency Payments

• On June 1st Mary creates a new sales order with this data:
  • Organization: F&B US, Inc., Transaction Document: Standard Order, Business Partner: Moon Light Restaurants, Co. Invoice Terms: Immediate, Product: Pear Juice, Quantity: 100 (EUR price list)
• On June 1st, Mike executes the process create invoices from orders, this process automatically creates the invoice from the previous order.
• On June 1st , The previous invoice is paid and Mike adds the payment from the invoice. All fields of the Add Payment window are automatically populated from the Invoice. Mike should check the Exchange Rate and the amount converted. The invoice is set as paid and it is also deposited in the financial account.

Story 11: Using accounting dimensions at client level

• On July 1st, F&B decide to start using accounting dimensions at client level. F&B choose to enable in header and lines project and cost center dimensions.
• On May 1th , F&B has a new partnership, the new partner must make a capital contribution to the company.
• On May 1th , Mike adds the payment from this capital contribution. Mike creates a new payment in with this data:
  • Organization: F&B US, Inc., Document Type: AR Receipt, Payment Method: Wire Transfer, Deposit To: Bank - Account 1 - USD.

Mike selects Add details and in the gl/item section adds a new gl/item with this data: Gl Item: Company capital, Received in; 200000 Mike needs then to select the corresponding project and cost center.

Story 12: Paying an invoice, adding a gl item transaction type payment and generating credit, all in the same payment

• On July 1st, Mary creates a new sales order with this data:
  • Organization: F&B US, Inc., Transaction Document: Standard Order, Business Partner: Healthy Food Supermarkets, Co., Invoice Terms: Immediate, Product: Lemonade, Quantity: 100
• On July 1st, Mike executes the process create invoices from orders, this process automatically creates the invoice from the previous order.
• On July 1th, Healthy Food Supermarkets, Co. pays 2000€ for some invoices of July and 1500€ as of a funds transfer. Mike adds a new payment from payment in window. Mike needs to change the actual payment amount to 2000 and takes the following actions:
  • Selects the invoice created in the previous step
  • Creates a new gl item line: Received in 1500€, GL item: funds transfer
  • Leaves the credit to be used later (in order to pay unpaid July invoices).

The invoice is set as paid and it is also deposited in the financial account.

Functional requirements based on business processes

Sales invoice and sales order window

All fields of the "Add Payment" window are automatically populated from the order/invoice.

• Payment Document No: Next number of the related Payment Document Sequence.
• Document Type:
• Deposit to(Financial Account): Financial Account to which the amount is going to be deposited. Defaulted to the Financial Account of the Business Partner.
• Reference No:
• Received From(Read Only) That is the Payee of the invoice. Defaulted to the Business Partner from the Invoice.
• Payment Method: Defaulted to the Payment Method of the Business Partner.
• Invoice Currency(Read Only): Currency of the Invoice.
• Currency To: Currency of the Payment to be created.
• Expected Converted(Read Only, Display Logic based on different currencies of the Sales Invoice and the Payment): Converted Expected Amount to the Payment Currency.
• Actual Converted(Display Logic based on different currencies of the Sales Invoice and the Payment): Converted Amount of the Actual Payment to the Payment Currency.
• Conversion Rate (Display Logic based on different currencies of the Sales Invoice and the Payment): Exchange Rate between the Currency of the Invoice and the Currency of the Payment.
• Expected Payment (Read Only): Total Gross Amount of the Invoice.
• Actual Payment: Total Gross Amount of the Invoice.
• Payment Date: Date of the payment event. It is used in the posting of the Payment to the general ledger. Defaulted to the Invoice Date field.

Normally the most common field to change is the "Actual Payment" received from the customer:

• In case the Actual Payment In amount is bigger than the grand total of the invoice selected, then it will be spread between the next documents pending to be paid till the whole paid amount is consumed. If there are no documents pending to be paid the system offers the options to:
  • Leave the credit to be used later which means that there will be available credit for the customer. That available credit can be used and therefore will appear on future payments as well as upon completion of new customer's invoice/s.
    • If the available credit is used:
      • The payment status of the invoice changes to Payment Complete = Yes
      • a literal such as "Invoice paid using credit:Payment Nº (Credit Payment)" is automatically populated in the description field of the invoice
      • a new payment is automatically created in the Payment In window. This payment clearly states the invoice paid in the "Description" field and the credit payment used is shown in the UsedCredit Source tab of the payment out.
    • If the available credit is not use: nothing happens, the new invoice is still not paid and the available credit amount remains the same.
  • Or Refund the amount to the customer which means that a refund payment is created besides the invoice payment in the Payment In window. A refunded payment has a negative amount which means the creation of a withdrawal transaction in the financial account instead of a deposit.
• In case the "Actual Payment In" amount is less than the grand total of the invoice selected, then the system offers the options to:
  • Leave the amount as an underpayment which implies that the remaining amount will be paid later on by the customer in a new payment.
  • or Write-off the difference which implies that:
    • the customer's invoice is set as fully paid
    • the invoice posting to the ledger settles the total customer receivable amount
    • while the payment posting to the ledger uses the Write-off account to post the amount written-off.

Field Group Sections:

• Order/Invoice:
  • Transaction Type, Values (“Orders”, “Invoices”, “Order and Invoices”): Defaulted to "Invoices".
  • Order/Invoice Grid: Order and Invoices from the Payee of the Invoice Pending to be paid. Filtered by
  • Transaction Type.
    • Payment: Total Gross Amount of the Invoice.
• GL Items (Hide on Sales Invoice window):
  • GL Items Grid: Business Partner, Product, Project, Cost Center, 1st Dimension, 2nd Dimension columns displayed depending on the client configuration.
• Credit to Use:
  • Credit to Use Grid: Grid Displayed in case the Business Partner has any available credit to use to make payments.
• Totals:
  • Amount on GL Items: Amount paid on GL Items
  • Amount on Invoices/Orders: Amount Paid on Order/Invoices
  • Total: Sum of GL Items and Invoices/Order
  • There is a Difference of: Total to be Paid minus Total Paid

Payment In All fields of the Add Payment window are automatically populated from the Invoice. The payment of several document types of different vendors at the same time.

• Receiving From (Read Only): The receiver of the payment. Defaulted to the Business Partner of the Payment. This field it is not mandatory.
• Business Partner: If a business partner is not selected in the Payment Header, it is possible to filter by a business partner in the Add Payment window.
• Actual Payment In: Total Gross Amount of the Invoice.
• Transaction Type, (“Orders”, “Invoices”, “Order and Invoices”, “GL Items”): Defaulted to “Invoices”.

It is important to notice that the same payment can contain a mix of G/L items and order/s & invoice/s transactions to be paid.

Field Group Sections:

• Order/Invoice:
  • Transaction Type, Values (“Orders”, “Invoices”, “Order and Invoices”): Defaulted to "Invoices".
  • Order/Invoice Grid: Order and Invoices from the Payee of the Invoice Pending to be paid. Filtered by Transaction Type.

Payment: Total Gross Amount of the Invoice.

• GL Items:
  • GL Items Grid: Business Partner, Product, Project, Cost Center, 1st Dimension, 2nd Dimension columns displayed depending on the client configuration.
• Credit to Use:
  • Credit to Use Grid: Grid Displayed in case the Business Partner has any available credit to make payments.
• Totals:
  • Amount on GL Items: Amount paid on GL Items
  • Amount on Invoices/Orders: Amount Paid on Order/Invoices
  • Total: Sum of GL Items and Invoices/Order
  • There is a Difference of: Total to be Paid minus Total Paid

User Interface Mokups

Sales Order/Invoice

Payment In

Functional Requirements - Purchase Flow

In the purchase flow we can use the Add Payment window in following windows:

• Purchase Order window: Payment/s can be made against a purchase order by using the Add Payment button.
• Purchase Invoice window: Payment/s can be made against a purchase invoice by using the Add Payment button.
• Payment Out window': Supplier's payments and prepayments can be made and managed in the payment out window. The Add Details button opens the Add Payment window where outstanding documents to be paid can be selected.

User roles & profiles

Purchase staff (Peter): Peter is an employee part of the purchase staff. He will be the one entering purchase orders transactions as appropriate.

Purchase staff (Alice): Alice is an employee part of the purchase staff. She will be the one entering purchase transactions as appropriate.

Business process definition

Peter a member of AR (sales) staff register the sales order that F&B requires and Alice a member of the AR (sales) staff issues sales invoice as required.

Alice will be the one to register the corresponding payment-out in the system if any.

Be Soft Drinker, Inc. is one of the vendors of F&B International Group, This vendor have by default Wire transfer as payment method and their payment terms is 30 days.This customer always paid 30 days after receive of invoice.

Happy Drinks, Inc. is one of the customers of F&B International Group, This customer have by default Wire transfer as payment method and their payment terms is 30 days. This customer always paid 15 days after order.

Fruit & Bio is Life, Inc. is one of the customers of F&B International Group. This customer have by default Check as payment method, their payment terms is 30 days, and Invoice Terms: Immediate. “Check” payment method not deposit automatically the payment in the financial account.

User Stories

Story 1: Add Payment to sales invoice with associated sales order

• On April 10st, Peter, who is in charge of issuing purchase orders, create a new sales order with this data:
  • Organization: F&B US, Inc., Transaction Document: Purchase Order, Business Partner: Be Soft Drinker, Inc., Product: Plain water, Quantity: 100
• On May 10st, Alice, who is in charge of issuing purchase invoices, create the invoice from the purchase order previous created, Mike to move faster, uses the button create lines from.
• On May 10th , The previous invoice is paid and Alice, who is in charge of issuing the payments , add the payment from the invoice. All fields of the Add Payment window are automatically populated from the Invoice. The invoice is set as paid and also is deposited in the financial account.

Story 2: Add Payment to purchase order

• On April 1st, Peter, who is in charge of issuing purchase orders, create a new purchase order with this data:
  • Organization: F&B US, Inc., Transaction Document: Purchase Order, Business Partner: Happy Drinks, Inc., Product: Rose wine, Quantity: 50
• On April 15st, payment of the previous purchase order is made and Alice, who is in charge of issuing the payments. Add the payment from the order. All fields of the Add Payment window are automatically populated from the Order.

Story 3: Add G/L Item transaction type payment

• On May 30th, F&B should paid the salaries for their employees
• On May 30th , Alice, who is in charge of issuing the payments , add the payment from one of this employees creating a new payment out with this data:
  • Organization: F&B US, Inc., Document Type: AP Payment, Payment Method: Wire Transfer, Paying From: Bank - Account 1 - USD.

Add details and in gl/item section add new gl/item with this data: Gl Item: Salaries, Paid out: 2000

Story 4: Generate credit

• On June 1st, To pay invoices in June to Be Soft Drinker, Inc. F&B generate credit of 2000€. Alice, who is in charge of issuing the payments. Alice add a payment out with this data:

• Organization: F&B US, Inc., Document Type: AP Payment, Payment Method: Wire Transfer, Paying From: Bank - Account 1 - USD.

Add details and process with the defaults values

Story 5: Purchase invoice paid with generated credit

• On June 15st, Peter, who is in charge of issuing purchase orders, create a new purchase order with this data:
  • Organization: F&B US, Inc., Transaction Document: Purchase Order, Business Partner: Be Soft Drinker, Inc., Product: Plain water, Quantity: 100
• On June 15st, Alice, who is in charge of issuing purchase invoices, create the invoice from the purchase order previous created, Mike to move faster, uses the button create lines from.
• On June 15st,, The previous invoice will be paid with the credit generated in the previous step. Alice who is in charge of issuing the payments , add the payment from the invoice. All fields of the Add Payment window are automatically populated from the Invoice, select use available credit and paid against this invoice. The invoice is set as paid and also is deposited in the financial account.

Story 6: Purchase invoice paid with partially payments

• On May 1st, Peter, who is in charge of issuing purchase orders, create a new purchase order with this data:
  • Organization: F&B US, Inc., Transaction Document: AP Invoice, Business Partner: Fruit & Bio is Life, Inc. , Product: Pineapple Juice, Quantity: 500
• On May 1st, Mike, who is in charge of issuing purchase invoices, create the invoice from the purchase order previous created, Mike to move faster, uses the button create lines from.
• On May 1st, F&B have been agreement with Fruit & Bio is Life, Inc. to pay in two equal installments the amount of the invoice. Mike who is in charge of issuing the payments, add the payment from the invoice. All fields of the Add Payment window are automatically populated from the Invoice, but Actual Payment should be changed to 187,5 (50% of the total amount). The invoice is partially paid.
• On May 15sh, The total outstanding of this invoice should be paid. Mike who is in charge of issuing the payments, add the payment from the invoice. All fields of the Add Payment window are automatically populated from the invoice. The invoice is set as paid and also is deposited in the financial account.

Functional requirements based on business processes

Purchase invoice and purchase order window

All fields of the Add Payment window are automatically populated from the Invoice.

• Payment Document No: Next number in Document Sequence.
• Document Type
• Take From (Financial Account): Financial Account from where the amount id going to be retrieved. Defaulted to the Financial Account of the Business Partner.
• Reference No
• To Be Paid To (Read Only): The receiver of the payment. Defaulted to the Business Partner from the Invoice.
• Payment Method: Defaulted to Payment Method of the Business Partner.
• Invoice Currency (Read Only): Currency of the Invoice.
• Currency To: Currency of the Payment to be created.
• Expected Converted (Read Only, Display Logic based on different currencies of the Sales Invoice and the Payment): Converted Expected Amount of the Expected Payment to Payments Currency.
• Actual Converted (Display Logic based on different currencies of the Sales Invoice and the Payment): Converted Amount of the Actual Payment to Payments Currency.
• Conversion Rate (Display Logic based on different currencies of the Sales Invoice and the Payment) Exchange Rate from the Currency of the Invoice and the Currency of the Payment.
• Expected Payment (Read Only): Total Gross Amount of the Invoice.
• Actual Payment: Total Gross Amount of the Invoice.
• Payment Date: Date of the payment event. It is used in the posting record of the Payment to the general ledger. Defaulted to the Invoice Date field.

Normally the most common field to change is the Actual Payment received from the customer:

• It is possible to uncheck any of the scheduled payments selected by default, in case a partial payment needs to be done against that invoice or even change the payment amount for a particular scheduled payment.

In both cases, the Expected payment field is automatically updated to the new value.

• In case of a partial payment, the difference or outstanding amount left to be paid:
  • can be left as an underpayment therefore it will paid later on by creating a a new payment
  • or it can be written-off

Field Group Sections:

• Order/Invoice:
  • Transaction Type, Values (“Orders”, “Invoices”, “Order and Invoices”): Defaulted to "Invoices".
  • Order/Invoice Grid: Order and Invoices from the Payee of the Invoice Pending to be paid. Filtered by Transaction Type.
    • Payment: Total Gross Amount of the Invoice.
• GL Items (Hide on Purchase Invoice window):
  • GL Items Grid: Business Partner, Product, Project, Cost Center, 1st Dimension, 2nd Dimension columns displayed depending on the client configuration.
• Credit to Use:
  • Credit to Use Grid: Grid Displayed in case the Business Partner has any available credit to use to make payments.
• Totals:
  • Amount on GL Items: Amount paid on GL Items
  • Amount on Invoices/Orders: Amount Paid on Order/Invoices
  • Total: Sum of GL Items and Invoices/Order
  • There is a Difference of: Total to be Paid minus Total Paid

Payment Out

All fields of the Add Payment window are automatically populated from the Invoice. The payment of several document types of different vendors at the same time.

• To Be Paid To (Read Only): The receiver of the payment. Defaulted to the *Business Partner from the Payment. It is not mandatory.
• Business Partner: If business partner is not selected in Payment Header, the this filter is displayed to filter the values in the grid.
• Actual Payment Out: Total Gross Amount of the Invoice.
• Transaction Type, (“Orders”, “Invoices”, “Order and Invoices”, “GL Items”): Defaulted to “Invoices”.

It is important to notice that the same payment can contain a mix of G/L item and order/s & invoice/s transactions to be paid.

Field Group Sections:

• Order/Invoice:
  • Transaction Type, Values (“Orders”, “Invoices”, “Order and Invoices”): Defaulted to "Invoices".
  • Order/Invoice Grid: Order and Invoices from the Payee of the Invoice Pending to be paid. Filtered by Transaction Type.
    • Payment: Total Gross Amount of the Invoice.
• GL Items:
  • GL Items Grid: Business Partner, Product, Project, Cost Center, 1st Dimension, 2nd Dimension columns displayed depending on the client configuration.
• Credit to Use:
  • Credit to Use Grid: Grid Displayed in case the Business Partner has any available credit to use to make payments.
• Totals:
  • Amount on GL Items: Amount paid on GL Items
  • Amount on Invoices/Orders: Amount Paid on Order/Invoices
  • Total: Sum of GL Items and Invoices/Order
  • There is a Difference of: Total to be Paid minus Total Paid

User Interface Mokups

Purchase order/invoice

Payment Out