Page 1252 "Payment Application Rules"
Base Application · Microsoft.Bank.Reconciliation
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Bank.Reconciliation · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Payment Application Rules |
| SourceTable | Bank Pmt. Appl. Rule |
| PageType | Worksheet |
| UsageCategory | Tasks |
| ApplicationArea | Basic, Suite |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Rules | Match Confidence | Match Confidence | Specifies your confidence in the application rule that you defined by the values in the Related Party Matched, Doc. No./Ext. Doc. No. Matched, and Amount Incl. Tolerance Matched fields on the line in the Payment Application Rules window. from the table field |
| Priority | Priority | Specifies the priority of the application rule in relation to other application rules that are defined as lines in the Payment Application Rules window. 1 represents the highest priority. from the table field | |
| Related Party Matched | Related Party Matched | Specifies how much information on the payment reconciliation journal line must match the open entry before the application rule will apply the payment to the open entry. from the table field | |
| Document No./Ext. Document No. Matched | Doc. No./Ext. Doc. No. Matched | Specifies if text on the payment reconciliation journal line must match with the value in the Document No. field or the External Document No. field on the open entry before the application rule will be used to automatically apply the payment to the open entry. from the table field | |
| Number of Entries Within Amount Tolerance Found | Amount Incl. Tolerance Matched | Specifies how many entries must match the amount including payment tolerance, before the application rule will be used to apply a payment to the open entry. from the table field | |
| Direct Debit Collection Matched | Direct Debit Collect. Matched | Specifies if the Transaction ID value on the payment reconciliation journal line must match with the value in the related Transaction ID field in the Direct Debit Collect. Entries window. from the table field | |
| Review Required | Review Required | Specifies if bank statement lines matched with this rule will be shown as recommended for review. from the table field | |
| Apply Immediatelly | Apply Immediatelly | Specifies whether to search for alternative ledger entries that this line can be applied to. If turned on, the value is applied to the first match and alternative ledger entries are not considered. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Restore Default Rules | Delete the application rules and replace them with the default rules, which control whether payments are automatically applied to open ledger entries. | |
| Advanced Settings | Opens advanced settings for configuring payment application matching. | Page 1253 “Payment Application Settings” |
Triggers
OnOpenPage
Relations
- source table Table 1252 “Bank Pmt. Appl. Rule”
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Payment Application Rules"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.