pageFinanceofficial - Microsoftderived - from the source, no model text

Page 1253 "Payment Application Settings"

Base Application · Microsoft.Bank.Reconciliation

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Table 1253 "Bank Pmt. Appl. Settings" (relates to)Bank Pmt. Appl. Settings

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Bank.Reconciliation · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Payment Application Settings
SourceTable Bank Pmt. Appl. Settings
PageType Card
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
General Settings Disable Suggestions for Apply Manually page Apply Man. Disable Suggestions Specifies if the suggestions should be disabled for Apply Manually page. Use this setting if the opening of Apply Manually page takes too long. from the table field
Enable Apply Immediately Rules Enable Apply Immediatelly Specifies if certain rules should be applied immediatelly. If this value is set to true, if the rule is matched, then the system will not look for alternatives for the specific line. If this value is set to false, the system will search for alternatives, resulting in a higher confidence match. from the table field
Related Party Name Matching RelatedParty Name Matching Specifies which algorithm to use to determaine related party. Set this value to disabled if your bank statements do not include the name of the related party name. from the table field
Candidate Lookback (Days) Candidate Lookback (Days) Specifies how many days back from the earliest bank statement transaction date in the journal the automatic matching searches for candidate ledger entries. A single window is applied to the whole journal. Limiting the range improves performance when there are many open entries. Set to 0 to search al… from the table field
Ledger Entries Matching Settings Enable Customer Ledger Entries Matching Cust. Ledger Entries Matching Specifies if automatic matching should be enabled for Customer Ledger Entries. from the table field
Enable Vendor Ledger Entries Matching Vendor Ledger Entries Matching Specifies if automatic matching should be enabled for Vendor Ledger Entries. from the table field
Enable Employee Ledger Entries Matching Empl. Ledger Entries Matching Specifies if automatic matching should be enabled for Employee Ledger Entries. from the table field
Enable Bank Ledger Entries Matching Bank Ledger Entries Matching Specifies if automatic matching should be enabled for Bank Ledger Entries. from the table field
Match Closing Document No. on Bank Ledger Entries Bank Ledg Closing Doc No Match Specifies if the algorithm should search Vendor and Customer Ledger Entries when matching Bank Ledger Entries. This functionality should be used only if your process requires it, otherwise it has a high performance impact. from the table field
Ledger Entries in “Apply Manually” page Show Customer Ledger Entries in “Apply Manually” page CustomerLedgerEntriesShown Specifies if Customer Ledger Entries are shown in the “Apply Manually page”.
Show Vendor Ledger Entries in “Apply Manually” page VendorLedgerEntriesShown Specifies if Vendor Ledger Entries are shown in the “Apply Manually page”.
Show Employee Ledger Entries in “Apply Manually” page EmployeeLedgerEntriesShown Specifies if Employee Ledger Entries are shown in the “Apply Manually page”.
Show Bank Ledger Entries in “Apply Manually” page BankLedgerEntriesShown Specifies if Bank Ledger Entries are shown in the “Apply Manually page”.

Triggers

OnOpenPage

Relations

Recent changes

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 Settings"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources