| Last Payment Date | The payment suggestion only considers entries whose due date is before or on this date. Only entries for which no value is entered in the field On Hold are taken into account. |
| Find Payment Discounts | Indicator that the payment discount date is taken into account when searching for available payments. Instead of the field Last Due Date, the field Last Payment Discount Date is taken into account. If the option Consider Payment Discount Tolerance is activated, the Discount Tolerance is also taken into account. |
| Last Payment Discount Date | Indicator that the payment discount date is taken into account when searching for possible payments. Instead of the field Last Due Date, the field Last Cash Discount Date is taken into account. |
| Last Payment Discount Date | If the indicator Find Payment Discount is set, this field (and not the field Last Due Date) is taken into account for filtering by payment discount date. If the field is empty, the field Last Due Date is used to find the items. |
| Check Other Journal Batches | Specifies whether to exclude payments that are already included in another journal batch from new suggested payments. This helps avoid duplicate payments. |
| Use Vendor Priority | Indicator that the Priority field on the vendor card determines the order in which the vendor entries are suggested for payment. This field is available only for payment suggestions in payment journals. Payments are made until the amount in the field Available Amount (LCY) is consumed. |
| Available Amount (LCY) | Amount available for payments to vendors.
|
| Check Other Journal Batches | Specifies whether to exclude payments that are already included in another journal batch from new suggested payments. This helps avoid duplicate payments. |
| Incl. Customers with Credit | Specifies that customers with credit should be included in the payment suggestion.
Selecting this option will also include customers with a positive balance. Under normal circumstances, these customers would not appear in the payment suggestion. However, this additional option means that they can still be suggested.
Differences between "Without Reductions" and "Incl. Customers with Credit"The option Incl. Customers with Credit should not be confused with the option Without Reduction. Here are 3 examples to illustrate the differences:Example 1 - Using "Without Reductions"Customer Adatum Corporation has 3 outstanding invoices, which total € 1,200. However, there is also an open credit memo with an amount of € 200 for the same customer. If the option Without Reductions were selected, this credit memo would not be taken into account and an amount of € 1,200 would be debited when the direct debit is collected. This option can be used regardless of whether the sum of the refunds exceeds the sum of the outstanding invoices.Example 2- Using "Incl. Customers with Credit"Customer Trey Research has 3 outstanding invoices which total € 2 100. There is an open credit memo of € 3,000 for the same customer. In this case, the customer would not be included in the payment suggestion because the customer has a positive balance overall. However, if you want to include customers with credit balances in the payment suggestion (direct debit), you must activate the Incl. Customers with Credit function. However, you must note that if you do not use Summarize per Customer, the refunds must be manually removed from the payment journal, otherwise the journal cannot be posted.
|
| Incl. Vendors with Credit | Specifies that vendors with credit should be included in the payment suggestion.
When this option is selected, payments to vendors with a positive balance are also taken into account. This means that the existing credit balance with the vendor is higher than the outstanding invoices.
Differences between "Without reduction" and "Incl. Vendors with Credit"The option Incl. Vendor with Credit should not be confused with the option Without Reduction. Here are 3 examples to illustrate what the differences are:Example 1 - Using "Without Reductions"We have 3 outstanding invoices with the vendor Nod Publishers which total € 1,200. However, there is also an open credit memo with the same vendor with an amount of € 200. If the option Without Reductions were selected, this credit memo would not be taken into account and an amount of € 1 200 would be transferred. This option can be used regardless of whether the total of open credit memos exceeds the total of open invoices with the vendor.Example 2- Using "Incl. creditors with credit balance"We have 3 outstanding invoices with vendor Wide World Importers which total € 2 100,-. The same vendor has an open credit memo of € 3,000. In this case, the vendor would not be included in the payment suggestion because we have a positive balance. However, if you want to include the vendors with a credit balance in the payment suggestion, you must activate the Incl. Vendors with Credit function. Please note, however, that if you do not use Summarize per Vendor, the refunds must be manually removed from the payment journal, otherwise the journal cannot be posted.
|
| Summerize per Vendor | Indicator that the lines are summarized per vendor (and currency).
|
| Summerize per Customer | Indicator that the lines are summarized per customer (and currency).
|
| By Dimension | Select the dimensions by which you want to group the payment suggestions. It is possible for the same combination of
|
| Posting Date | Date on which the payments are posted. This field is transferred to the journal lines. |
| Consider Payment Discount Tolerance | If this field is set, the payment discount tolerance date of the entries is taken into account in the calculation, except if the field Block payment tolerance is set on the vendor/customer card. If the Use Payment Discount field is also set, the system filters not only on the payment discount date but also on the payment discount tolerance date when searching for possible (future) payments. |
| Calculate Posting Date from Applies-to-Doc. Due Date | Specifies if the due date on the purchase invoice will be used as a basis to calculate the payment posting date. |
| Applies-to-Doc. Due Date Offset | Specifies a period of time that will separate the payment posting date from the due date on the invoice. Example 1: To pay the invoice on the Friday in the week of the due date, enter CW-2D (current week minus two days). Example 2: To pay the invoice two days before the due date, enter -2D (minus two days). |
| Starting Document No. | Document number for the first line of the payment suggestion.
|
| New Doc. No. per Line | Indicates that the journal lines are numbered sequentially (starting from the number in the field Starting Document No.). |
| Bal. Account Type | Type of balancing account (G/L account, bank account).
|
| Bal. Account No. | Number of the balancing account to which the posting is to be posted.
You can enter the account number or select from a drop down list.
|
| Payment Type | Payment type for the journal lines.
The following options are available:
|
| Foreign Currency Filter | Indicator that the filter is applied to items with ISO currency codes other than 'blank' or 'EUR'. |
| Without Reductions | Indicator that entries that would reduce the amount (credit memos, refunds) are not included in the payment suggestion. |
| Customer/Vendor/Employee | In this filter pane, you can limit the results of the payment suggestion by setting filters on the customer/vendor/employee tables. You can find further information on this under Sorting, Searching, and Filtering |
| Customer Ledger Entry/Vendor Ledger Entry/Employee Ledger Entry | In this filter pane, you can limit the results of the payment suggestion by setting filters on the customer ledger entry/vendor ledger entry/employee ledger entry tables. You can find further information on this under Sorting, Searching, and Filtering |
 | Finmatics Autonomous Accounting Interface for AI-driven document processing tool by Finmatics. More information  |
