This table holds preferences per client for Manage AP Payments. |
client_KEY | int (4) | NOT NULL | Primary key, not null. The key of the client the preferences are for. |
allow_multiple_applications | bit (1) | NOT NULL | True if multiple applications are allowed in Manage AP Payments. |
allow_multiple_payments | bit (1) | NOT NULL | True if multiple payments are allowed in Manage AP Payments. |
default_payment__journal_KEY | int (4) | | Specifies the default journal key to be assigned to a payment when paying a payable. If null, the client general journal key will be filled in for the payment. |
use_due_date_as_payment_date | bit (1) | NOT NULL | Flag that is used in Manage AP Payments to know if for a client we want to use a payable due date as the date of a new pending payment to be created in Manage AP Payments to pay one or more payables. If several payables are to be paid together, the oldest due date will be used as the payment date when this flag is set true. When this flag is set false, then the payment date defaults to the AP date. |
reference_number_suffix | nvarchar (32) | NOT NULL | The default reference number suffix to be associated with the payment application. |
default__checkbook_KEY | int (4) | | Specifies the default bank account to be used when paying a payable in Manage AP Payments. This default does not override any default set for the vendor the payable is being applied for; if both defaults are set the vendor default will be used. A null value indicates that no default value is set and nothing will initially be filled in for the bank account when paying a payable. |
default_application__journal_KEY | int (4) | | Specifies the default journal key to be assigned to a payment application when paying a payable. If null, the client general journal key will be filled in for the payment application. |
use_payment_date_as_application_date | bit (1) | NOT NULL | 1 means the payment date is used as the application date; 0 means that we use AP date as the application date. |