tableFinanceofficial - Microsoftderived - from the source, no model text

Table 1253 "Bank Pmt. Appl. Settings"

Base Application · Microsoft.Bank.Reconciliation

Across versions

  1. BC23present
  2. BC248 fields changed, 4 fields added
  3. BC25-27unchanged
  4. BC288 fields changed
  5. BC291 fields added, 1 procedures added
  6. BC30unchanged

Neighbourhood 1 connected objects and pages

Page 1253 "Payment Application Settings" (pages and codeunits on it)Payment Application 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 · captioned “Bank Payment Application Settings” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Bank Payment Application Settings
DataClassification CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 PrimaryKey Code[20] — DataClassification SystemMetadata
3 Vendor Ledger Entries Matching Δ BC24 Δ BC28 Boolean Specifies if automatic matching should be enabled for Vendor Ledger Entries.
4 Cust. Ledger Entries Matching Δ BC24 Δ BC28 Boolean Specifies if automatic matching should be enabled for Customer Ledger Entries.
5 Bank Ledger Entries Matching Δ BC24 Δ BC28 Boolean Specifies if automatic matching should be enabled for Bank Ledger Entries.
6 RelatedParty Name Matching Δ BC24 Δ BC28 Enum “Pmt. Appl. Related Party 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. enum Enum 1253 “Pmt. Appl. Related Party Name Matching”
7 Bank Ledg Closing Doc No Match Δ BC24 Δ BC28 boolean 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.
8 Apply Man. Disable Suggestions Δ BC24 Δ BC28 boolean Specifies if the suggestions should be disabled for Apply Manually page. Use this setting if the opening of Apply Manually page takes too long.
9 Enable Apply Immediatelly Δ BC24 Δ BC28 boolean 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.
10 Empl. Ledger Entries Matching Δ BC24 Δ BC28 Boolean Specifies if automatic matching should be enabled for Employee Ledger Entries.
11 Vend Ledg Hidden In Apply Man + BC24 Boolean —
12 Cust Ledg Hidden In Apply Man + BC24 Boolean —
13 Bank Ledg Hidden In Apply Man + BC24 Boolean —
14 Empl Ledg Hidden In Apply Man + BC24 Boolean —
15 Candidate Lookback (Days) + BC29 Integer 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…

Keys

  • Key1: PrimaryKey (clustered)

Procedures

  • GetOrInsert(): Retrieves existing settings record or creates a new one with default values. Ensures settings are always available for payment application processes by using singleton pattern with default configuration for new installations.
  • GetCandidateLookbackStartDate(ReferenceDate: Date): Date + BC29: Calculates the earliest posting date to include when searching for candidate ledger entries. Returns 0D (no lower bound) when the lookback is not configured or no reference date is available.

Pages and codeunits on this table

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: "table", object_name: "Bank Pmt. Appl. Settings"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources